Three (low cost) ideas to improve software quality

We all know this - Software can be…. buggy. There are many reasons why software doesnt always do what it supposed to do, so how can you improve software quality without hiring expensive consultants or starting a reengineering projec.

In the heat of daily operations, there are three simple practices that often remain overlooked despite their proven impact. Today, we’re shedding light on three techniques that might not yet be part of your team’s toolkit but could transform how you work together and ship code.

1. Pair & Mob Programming: Collaborative Coding at Its Best 

Pair programming involves two developers working on the same code—one writes, the other reviews. Mob programming takes it a step further by involving a group, typically with a facilitator guiding the session. While some teams dismiss these as time-intensive, they often result in higher-quality code, faster problem-solving, and better knowledge sharing.

Why adopt it?

• Improved code quality: Continuous peer review reduces defects.

• Enhanced learning: Junior developers gain hands-on experience, and even senior developers pick up new techniques.

• Team alignment: Everyone develops a deeper understanding of the codebase.

What does it cost ? Not a dime, maybe a cup of coffee and some dedicated time in the afternoon.

2. Inner Source: Bringing Open Source Principles In-House Inner source applies open-source development principles within an organization. By opening up internal projects to contributions from across teams, you create opportunities for collaboration and innovation. And no, you don’t need to set standards and make everyone ‘Schalou’

Why adopt it?

• Breaks down silos: Teams gain visibility into each other’s work, fostering cross-functional collaboration.

• Accelerates problem-solving: Contributions from diverse perspectives often lead to faster solutions.

• Builds a stronger engineering culture: Developers feel empowered to contribute beyond their immediate projects.

What does it cost? You might want to appoint a couple of Open Source Ambassadors, showcasing positive examples of sharing culture. You might as well encourage people to set their code projects to ‘public’ and not ‘private’. Think about one thing: most code lies around in baskets of your suppliers - encourage them to contribute.

3. Trunk-Based Development: Live on the Edge (of Your Codebase) Trunk-based development involves keeping all developers working on a single branch (or trunk), with small, frequent commits and continuous integration. This practice minimizes the complexity of merging long-lived branches and helps teams deliver faster.

Why adopt it?

• Reduced merge conflicts: Short-lived work stays aligned with the main codebase.

• Faster feedback loops: Continuous integration ensures issues are caught early.

• Better deployment readiness: Frequent, incremental changes reduce the risk of large-scale failures.

What does it cost? This is no short-term goal but gradually bringing all your developers into the same code base might require some work and some helping hands. It also asks for some investments into coding culture, discipline. We dedicate a whole section in our book All Hands on Tecg.

While these practices might seem unconventional or challenging to implement initially, they’ve been shown to improve collaboration, quality, and delivery speed in organizations that adopt them. Consider experimenting with one (or all) of these techniques in your team’s workflow—you might be surprised at the results.

Join our conversation on LinkedIn:

Have you tried any of these practices? We’d love to hear about your experiences!

All the best

Sophie