Successful microtest TDD depends on our ability to solve a goldilocks challenge: when we test our code pieces, do we isolate them too much, too little, or just right? Finding the sweet spot will mean letting go of rulesets & purity. As is my wont, let me remind you, geekery isn’t the only story going […]
TDD’s Goldilocks Challenge Read More »
Because microtest TDD is more a "way of geeking" than a technique or a received body of knowledge, building one’s faculties is a long and sometimes perilous effort. Let’s talk about learning. (I, too, feel a little relief just now, tho not as much as some, because recent events aren’t an ending, they’re the beginning
Learning TDD w/ Four Mentors Read More »
Microtest TDD is an effective change strategy because it dramatically improves our performance at comprehension, confirmation, and regression detection, all critical factors in handling change quickly & safely. I know how comparatively little geekery matters right now. Sometimes I need a break, and maybe you do, too, so I share. Black lives matter. We can
TDD As Change Strategy Read More »
I got one of those messages I sometimes get from a reader, telling me that including my politics in my muses/blogs is off-putting. As a general rule, I don’t bother to respond to these. I gain and lose followers all the time, everyone who makes content does, for all sorts of reasons, and that’s just
On Political Content Read More »
Before we can make the case that microtest TDD is an effective change strategy, there’s a few high-level aspects of it that we need to highlight. We tend to take these for granted in our case, but newcomers won’t already know them. More even than before, geekery seems irrelevant. We’re living the natural outcome of
Aspects of TDD Practice Read More »
Microtest Test-Driven Development is a strategy for change. To understand the case, we need to answer two questions: 1) Why have a strategy for change? 2) How does TDD provide one? Let’s take up the first question today. (Before we begin, I remind you of the relative unimportance of geekery to me just now. This
Why Have a Change Strategy Read More »
Today it’s microtest TDD’s Value Premise: TDD ships more value faster when that value depends on changing our branching logic safely & quickly. Let’s dig in. Before we start: geekery continues to seem largely irrelevant to me. 1 in 900 Black Americans have died of Covid. They’re still shooting unarmed men & boys in the
Today, let’s take on microtest TDD’s Correlation Premise: Internal software quality (ISQ) and productivity are directly correlated. They go up together, and they go down together. Writing about geekery these days seems idle or frivolous at times. I’ve decided to just accept it as a way to relax here and there. But don’t mistake me.
The Correlation Premise Read More »
Today, let’s talk about microtest TDD’s Judgment Premise: "We are absolutely and permanently reliant on individual humans using their individual judgment in TDD." Folks, in these times, I gain respite in thinking & writing about geekery, and I hope you do, too. But there are more important stories, and this is just a break. Stay
The Judgment Premise Read More »
Microtest TDD’s Steering Premise is quite simple, which may be why it sometimes meets furious opposition. It says "Tests and testability are first-class citizens in design." Let’s talk that over a little. As is my wont, I remind you, TDD, and even geekery, aren’t really the most pressing story around us today. It’s comfort food,
The Steering Premise Read More »
