Rice & Garlic & More Smaller Steps

My rice’n’garlic advice, "take many more much smaller steps," can be said another way: reject any proposed path that requires a step size larger than the limit you’ve set for that particular domain of activity. Time for Sunday geek comfort. It’s meant to be respite. There are more important things than geekery, so please remember to think outside the monitor. Stay strong, stay safe, stay angry, stay kind. Black Lives Matter. "Rice’n’garlic advice" is blind advice, for when people ask […]

Rice & Garlic & More Smaller Steps See Full Post

Scenario Builders

In a data-rich environment, we can use the Builder concept to make DSL’s for our Making application. This often makes testing the hard business core of our code both faster and easier. Folks, I love sharing my geekery with you. For me, it brings much comfort. I hope, tho, you’ll join me in working for change that isn’t just about code, but about the larger world. Black Lives Matter. We’ve spoken in the past about using our codebase to do

Scenario Builders See Full Post

An Early TDD Experience

HOT TIP! Click the image below to get $75 off Ted Young’s new interactive online class running March 8th-11th 2021. Use special code "GEEPAW" at checkout. Thanks! When we talk about transitioning to microtest TDD, we have to figure out how to provide the right experiences in the right order. That’s why I propose we start by getting the experience of changing a well-microtested graceful class. Folks, my ideas about changing code are thoroughly entangled with my ideas about changing

An Early TDD Experience See Full Post

Technique & Transition

HOT TIP! Click the image below to get $75 off Ted Young’s new interactive online class running March 8th-11th 2021. Use special code "GEEPAW" at checkout. Thanks! Microtest TDD is a "way of coding", not an after-market bolt-on to old-school approaches, and as a result, we have to constantly intertwine our conversation about technique with our conversation about transition. Geekery’s fun for me, and it’s comforting, but it’s not the most important story going on around us. Enjoy this thread,

Technique & Transition See Full Post

Awkward & Graceful

In microtest TDD, we describe collaborations as "awkward" or "graceful". The distinction is critical to understanding how the Steering premise and the Pieces premise work together to make TDD a productivity tool. Let’s dig in. Here in the states, it’s Black History month. I urge my friends and followers to pay attention: American history and Black history are deeply & painfully intertwined, and we won’t move on until we go through. Black Lives Matter. We talked the other day about

Awkward & Graceful See Full Post

TDD’s Goldilocks Challenge

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 on around us. I write of it for my rest & comfort, and perhaps for yours, but it’s a break from more important things. Black

TDD’s Goldilocks Challenge See Full Post

Learning TDD w/ Four Mentors

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 of a lot of work. Black Lives Matter. Stay safe, stay strong, stay angry, stay kind. Let’s keep changing this.) I want to approach the

Learning TDD w/ Four Mentors See Full Post

TDD As Change Strategy

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 fix this. We’re the only thing that can. Stay safe. Stay strong. Stay angry. Stay kind. We’ve covered a lot of ground in considering TDD

TDD As Change Strategy See Full Post

Aspects of TDD Practice

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 a politics of hatred & deceit. This content is one way I find respite, and maybe it will help you a little, but… Stay safe.

Aspects of TDD Practice See Full Post

Why Have a Change Strategy

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 is just respite. Please work for change and support the others who are doing so. Black lives matter. Stay safe, stay strong, stay angry, stay

Why Have a Change Strategy See Full Post

Scroll to Top