
Latest
-
“Vibe hacking” signals seismic shift for engineering leaders
Blackhat hackers have an addition to their armoury. Here’s how engineering leaders can safeguard their systems and stay on high alert.
-
Is GitHub’s coding agent your newest junior dev?
GitHub’s new coding agent has some perks, but is still showing signs of significant growing pains. What are the current pain points?
-
From dashboard soup to observability lasagna: Building better layers
Transform chaotic dashboards into a layered observability strategy that improves reliability, streamlines incidents, and builds real on-call confidence
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.

Berlin • Nov 3 & 4, 2025
Charity Majors, Sam Newman, and Humera Noor confirmed for LeadDev Berlin! 🙌
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.

More about Software Quality
-
How demand shaping can reduce the carbon cost of our applications
Making an impact with sustainable software engineering
-
Scaling at the speed of COVID-19: lessons from the front lines of virtual healthcare
How quickly could you adapt your healthcare software to a global pandemic?
Top Software Quality Videos
-
Streamlining the management of multiple websites and apps
Prepare your team to work effectively across contexts
-
Establishing experimentation as a core part of your project workflow
Gain actionable insights from your users and improve engineering velocity
-
Living without pre-production environments
Historically when we developed large monolithic applications we had several ‘lower’ environments such as dev, test, staging, pre-prod for verifying different stages of our development life cycle. These were particularly used for manual testing – integration testing, gatekeeping, acceptance testing.
-
How simplifying software can save your engineering teams’ time
We’re conditioned to think from an early age that exciting things are the best. That attitude can extend to engineering, too.
-
Scaling performance at the scale of Slack
One of the major challenges faced by teams working on high growth product is of performance. Systems that are built for a given scale of users often fail to deliver the necessary throughput when run with orders of magnitude of load more than what they are built for. Software teams have historically resorted to a myriad set of ways in scaling performance.
-
Strategies for making impossible decisions
Being faced with an important choice that feels impossible to know the answer to is stressful! This comes up a lot when making business decisions, but also applies to technical choices (e.g. “should my company run 100% on AWS” or “is serverless a fad or a great idea?”).
-
Writing effective technical documentation
Documentation can make a big difference. Internal documentation can speed your team up and makes it easier for new engineers to get up and running. External documentation reduces time spent on support questions, and makes your product more usable.