Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.
Hot-fix redeployment is a waste of time and effort at best, and often a source of further regression, Adam discusses some ready-to-use techniques that helped he and his team reduce the frequency of hot-fix deployments to almost zero.
Gil Broza explores agile values, beliefs and principles, and explains how they can be used to drive agile adoption in his book The Agile Mind-set. The book provides ideas, examples, and anecdotes that organizations can use to make a shift to agile.
James Grenning talks about why people are not doing technical practices sufficiently or well enough, TDD and unit tests, and on becoming better in discovering "bad code”.
Software developers spend time and energy on building the best possible products looking at web frameworks, using a NoSQL or SQL database, etc. There's another equally important aspect: culture. 1
Developers across the globe attend coderetreats to learn from each other and refine their software design skills, but how do they work? What do people say about them? How can we make them even better? 3
Quality Code book covers different aspects of SDLC with focus on delivering quality product. InfoQ spoke with author Stephen Vance about the book and best practices for testing applications.
In this article, author Olivier Gaudin discusses the differences between internal and external software quality and how to perform the software quality assessment using Sonar and JaCoCo tools. 2