tdd Driving code design, through tests (IV) In the context of TDD, tests that only exercise the unit level are some of the most restrictive tests you can write, especially if you are maintaining a 1-to-1 relationship between implementation code and test code.
tdd Driving code design, through tests (III) The mechanics of Test-Driven Development are pretty easy to grasp, but the addition of a couple of heuristics will really make the practice sing.
team The Debt metaphor sucks, Part 2 Not too long ago I wrote on my dissatisfaction with the 'technical debt' metaphor, to much applause and adoration. And also some browbeating.
team The Debt metaphor sucks As I was packing dirty dishes into the refrigerator and oven I found myself reflecting on my current project. "How is this frantic 'cleaning' any different than when we made questionable technical decisions to help the client make their deadlines?" I asked myself.
mocks On tests and testing Hello, gentle reader. Please allow me to rock your entire human face by dropping this truth bomb: Tests are about more than testing. "Obviously!" you yell, your riposte ringing out triumphantly against what is seemingly a rather anemic statement. The truth bomb has failed to detonate. Your entire
agile Refactoring and clarity TLDR The purpose of refactoring is to improve code clarity. Introduction I refactored some code lately and I want to talk about it. Actually, let me back up and cover a few foundational points first, because without those it's going to appear like I'm ranting. Probably because I am. But
