Latest
-
AI-generated code sparks production confidence crisis
35% of teams won’t ship their own AI-generated code.
-
You can vibe code a demo, but what about a product?
Lessons from shipping generative AI products to production.
-
AI coding creates two kinds of debt. You’re only measuring one
Cognitive debt is the technical debt nobody is tracking.
-
In partnership with HarnessUnlocking ROI through development, release, and experimentation velocity
Learn how faster, more reliable delivery pipelines can unlock experimentation ROI, improve release confidence, and drive compounding gains across teams.
Editor’s picks
The quickly evolving role of QA
In fast-paced software development environments, the way you think about quality assurance needs to change.
New York • September 15 & 16, 2026
Cut through the hype.
Find what works at LDX3 New York
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
Using clinical science to effectively tackle code review anxiety
Uncover the science behind code review anxiety, its cognitive triggers, and actionable strategies to reduce anxiety, fostering a healthier code review culture for all developers.
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.
The festival for modern engineering leadership
New York • September 15 & 16, 2026
More about Software Quality
-
Learning to live with legacy code
It’s possible to have a large codebase that isn’t cumbersome to work with by setting a technology vision, distributing the work effectively, and tracking progress publicly.
-
A journey to tackle legacy code in online travel
Modernizing online travel experiences is a huge engineering challenge, here’s how Sabre tackled it head on.
-
6 steps to addressing legacy enterprise code
Legacy code is a fact of life, but it can’t be ignored. Here are six practical steps to identify and refactor legacy code in your organization.
-
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.
-
3 strategies for maximizing your cloud savings
As budgets get tighter, here are three surefire ways to maximize your cloud savings.
-
Architecting for profit: A blueprint for modern cloud economics
If the role of a good cloud architect is to design and build cost-effective software, is there a formula to achieve that goal every time?
-
Cost savings don’t have to impact code quality
Ahead of his talk at LeadDev West Coast in October, Plaid’s Mark Robinson discusses cloud costs and how they could be the ticket to both dollar value and improved code quality.
-
Consultative QA as a way to empower engineering teams
Consultative QA has the ability to transform your engineering team, putting the responsibility on the engineers for the quality of their work, whilst still having a level of assurance that a seasoned tester can bring.
Top Software Quality Videos
-
Why shifting left is so important for software developers
Jemiah Sius talks about how shifting left has become increasingly important in the software development industry as organizations strive to release high-quality software products more quickly and efficiently. By integrating observability, security, and testing practices earlier in the development cycle, developers can identify and address issues more effectively.
-
a11y is your MVP: Moving fast without breaking accessibility
Plum Ertz talks about how, despite the growing discussion in the industry about digital accessibility, putting those debates into action can still be challenging in today’s world of “doing more with less”.
-
Slaying the Goliath: Lessons learned from a full system re-write
Brian Genisio shares the lessons we learned from our multi-year journey, including project planning, team management, technical challenges, testing and deployment, and post-project analysis.
-
How much is that API call in the window?
Mark Robinson talks about how in recent years, cloud computing has transformed the way businesses store, manage, and analyze their data.
-
Working on software that is older than you
Sally Wahba shares her views on working on an older codebase. She will share her experience watching the codebase evolve from incorporating acquired startups, to consolidating code branches. She will share pain points that she found to be repeated after joining a younger company.
-
In partnership with Chronosphere
How Observability Can Boost Engineering Productivity
Join Chronosphere’s Field CTO, Ian Smith, to learn how cloud native observability reduces burnout and boosts engineering team productivity.
-
The dark side of standardization
Samantha Schaevitz wants you to leave this talk better equipped to decide whether embarking on a standardization project is right for your stack or organization, and how to do it in a way that avoids common pitfalls along the way.
-
Why onboarding to a company’s legacy codebase sucks, and how to make it work for your team
Shanea Leven discusses the history and context of the problems that plague codebase onboarding. And with problems come solutions such as tips and tools that make it easier for engineers to onboard a legacy codebase.