Latest
-
Keep calm and code on in the face of bugs
Bugs making their way into the system may feel like a sting to a developer. But, letting go of defensiveness can bring many advantages!
-
How to evaluate AI performance when you have no domain expertise
If you have no experience with the domain you’re working on, that’s ok. Here’s how you can beat common problems and ensure success.
-
Content sponsored by SwimmA roadmap to working with your legacy codebases
Gain expert insights on modernizing legacy systems, improving developer satisfaction, streamlining discovery, and effectively documenting complex, large-scale codebases for better productivity and collaboration.
Editor’s picks
How test coverage can improve code quality
As teams get bigger and the need for faster velocity increases, code quality can be difficult to uphold. Use these techniques from Michael Tweed, a principal software engineer at Skyscanner, to help.
That’s a wrap for LeadDev Berlin 2024!
Watch all of the talk videos from an incredible two days with a digital pass.
Essential reading
How to bake quality into your teams’ coding process
Taking code quality beyond documentation and into the fabric of your team’s work.
On our Software Quality playlist
Ways your teams can (realistically) prioritize code quality
Code matters – learn how to create a culture of quality in your organisation
Metrics – a primer, to drive precision, speed, quality & impact
As managers or senior leaders, this talk will give you a primer for leveraging metrics for the objectives you seek, outcomes you desire, and the behaviors you want to incentivize or disincentivize within your engineering organization.
A guide to creating a great code documentation culture
If your teams are struggling with code documentation, watch this on-demand webinar, where our panel of engineering leaders will discuss best practices and strategies to get started. Code documentation is often viewed as a necessary evil by development teams. There’s no doubt that mastering the art of creating…
Building a better testing culture
How can engineering leaders create a healthy testing culture with clear strategies in place?
Take back control of code quality
In this talk, Joel Chippindale shares stories from his experiences in leading engineering teams that illustrate the dynamics between team members and with stakeholders that lead teams to lose control of code quality.
That’s a wrap Berlin!
Catch-up on all the Lead Berlin 2024 talks with a digital pass.
More about Software Quality
Top Software Quality Videos
-
The benefits of delivering imperfect software
We all want to deploy the best software possible to delight our customers and please our product owners. There’s always one more feature, another performance improvement, and code we just wish we wrote better.
-
The possibility of AI-powered Javascript apps
There are many exciting things happening with AI, from which, until recently, JavaScript developers were largely shut out. But things are changing, if you can do `npm install @tensorflow/tfjs` or make an API call, you can now do AI.
-
Identifying and articulating the role of AI in your software design process
We’ve all read the articles and got excited by technologies such as machine learning, deep learning, Tensorflow, Panda and NumPy. A lot of us are also looking at how to incorporate these technologies into our toolset and in the software we are building.
-
Rejecting the black box: examining the implications and practicalities of testing AI
There’s a lot of talk nowadays about the impact that artificial intelligence (AI) will have on testing. There’s a new generation of testing tools being developed that employ AI with promises of making testing much more efficient for us.
-
Navigating front-end architecture like a Neopian
Over the past few years, I’ve gained expertise in front-end web architecture. I’ve done this work at Indiegogo, Headspace, for my open source mental health project if-me.org, and in my current role at Mailchimp.
-
Designing software to maximize developer productivity
Having worked extensively in the Shopify codebase, one of the largest rails apps in existence, I have experienced firsthand some of the downsides of working in monolithic codebases.
-
Principles for managing product quality
Keeping an application stable starts off being simple since your codebase is small, there are few points of failure, and you can easily reason about the implications of code changes.
-
Using observability to detangle and understand production
When using tens or hundreds of microservices to provide an application’s critical functionality, diagnosing what interaction between components is causing an outage can be challenging.