coding

Reckless Debt versus Strategic Debt

August 25, 2012

Chris Eargle has a great article explaining that the term “technical debt” comprises both strategic debt and reckless debt: Technical debt accrues interest, and it must be paid back lest the interest payments (lost time) become too high for product maintenance and future development. If immediate business concerns outweigh future business concerns, it makes sense […]

Read the full article →

Software Analysis Paralysis

September 22, 2009

Programmers and managers are obsessed with finding the best way to solve a particular challenge. This is a good thing because that is what quality is all about. Sometimes, though, it can be taken to extremes and the project gets stuck in discussions of minutiae. I was reminded about this when I read about the Chandler […]

Read the full article →

The Twin Demons of Programmers

September 3, 2009

Two somewhat conflicting needs of programmers: Write as little code as possible. Reduce coupling as much as possible. I wonder if they can ever be achieved together entirely, but one thing that seems to be happening is that Item (2) is getting done with more and more functionality getting into the software environment (operating system, […]

Read the full article →

Bad Example for Test-Driven Development

August 13, 2009

Uncle Bob has a point with respect to “generic code and specific tests”, but the example he gives for supporting his argument (“Prime Factors Kata”) is a poor one. In fact, it supports the argument against Test-Driven Development, which is that it pays too little attention to design and that design is an after-thought of […]

Read the full article →