refactor

23/09/200828/12/2014 on agile, build, design, programming, quality, refactor, testing

The cost of un-fixed bugs or Good Code on top of Bad Code

While discussing with a colleague we started talking about the costs related to not fixing a bug immediately (yes, this does mean that you have a way to immediately figure out if you introduced a bug). The reason for fixing bugs immediately is not only the cost of content switching later on when you have …

Recent Posts

  • How to “control” a software project, and why control is never achieved with planning
  • #NoBacklogs: How to never lose a good idea by keeping the Backlog short!
  • The Project Slippery Slope: why the concept of Projects lead to Waterfall, sooner or later, but inevitably…

Memory lane

I like order, here’s the categories

scrum master podcast
↑
  • Home
  • NoEstimates
  • Privacy Policy and GDPR compliance information
Proudly powered by WordPress | Theme: Fastr by Kanishk.
The ONE tool every Project Manager must have in their toolbox!
Discover a New Approach to solving the "deliver on time" problem!
FREE PDF Download of the first chapter of the book.
Learn about #NoEstimates, and start delivering your software on time!
Download chapter 1 of the book right now