Skip to content
Home » Improving Software Practice

Improving Software Practice

People create software, not tools. Not even AI tools.

Good software practice and craftsmanship begin with simple techniques leading to better, more effective and more supportable code. Good design practice, good architecture and good testing methodologies pay immediate dividends in terms of fewer outages and improved customer experience.

It pays to consider how tools are deployed and integrated into your development pipeline helps to avoid them becoming “process traps” where time and effort (and enthusiasm) is lost.

I help you identify the bottlenecks in your development practice, using my QUEST framework to help us focus on the right areas:

  • Quality (is everyone’s responsibility and is the most important)
  • Unrestricted (freedom to do what you want to do)
  • End-User (everything we build is for the customer)
  • Simplicity (architecture, design and code)
  • Team (collaboration at its heart – mindful development, pair programming, mob programming)

Rather than relying on processes or tools, let’s ensure that the whole organisation understands that when it comes to building quality software it takes discipline and commitment to make great software, together.