We all know how valuable it is to keep the quality of your code high. Working on a high quality codebase is more enjoyable and enables us to deliver value much more effectively for our users and yet, time and again I hear engineers saying, “I am not allowed to spend sufficient time on code quality”.
This talk clarifies the value of maintaining a high quality codebase, gives you guidance on how to talk about this to help you get the support of your colleagues and managers for spending time on this and also outlines some key practices that will help you achieve this.
Versions of this talk
Further reading and watching
Running an Agile Principles study group [article]
How to run an study group to improve the understanding of and adoption of agile principles
Foundations to build on: Intercom’s principles for building product [article]
Des Traynor outlines some key principles for effectively developing a product and the engineering specific principles are the source of "Shape the solution" in this talk
Why not fix your technical debt? [video]
Alex Warren's insightful talk encouraging you to take control of improving your code quality
Principles behind the Agile Manifesto [article]
These 12 principles form the basis of the Agile Manifesto and I keep referring back to these when thinking about how to get the most out of agile approaches to work
Really enjoyed the talks at #londonpython last night. Will definitely be using some of the ways of talking about software quality outlined by @joelchippindale.
Questions or feedback
If you have any questions, feedback or advice that you would like to share then please don't hesitate to contact me at @joelchippindale.