The Pieces Premise says, "To get the whole thing to do what you want, start by getting each piece of it to do what you want. It’s one of the basic underpinning of microtest TDD. It’s a hard time out there for those working on social change. I want you to know how much what […]
The Pieces Premise Read More »
I was recently asked, by two different groups, two seemingly different questions, but I gave them both the same answer: Collaboration, Complication, and Continuity. Let’s mull that situation over. Folks, this is a hard time for a person with my views about society. There is so much going wrong, in so many directions. I turn
Collaboration, Complication, Continuity Read More »
I am supposed to be shooting the next Real Programmer episode today, but I had a really good wrap-up meeting that was important, and I’m waiting for one more piece I need to send a first invoice to a new client, and I want to talk about coaching. In another part of the forest, some
Old Coach at the End of the Bar Read More »
Human, local, oriented, taken, and iterative, these are the change-harvester’s bywords. In iterative change, we not only accept the reality of gradual stepwise refinement — changing what we’ve already changed before — we actually anticipate it and take advantage of it. Before we begin: Folks, I know many are celebrating last week’s results . I
Change Harvesters Iterate Change Read More »
We’re talking about change-harvesting: human, local, oriented, taken, and iterative change. Let’s consider this adjective "taken" today, and see where we go with it. I keep saying: these muses are respite for me, and maybe for you, from more important stories. Partisan thugs seek to turn our nation into a freak show of state violence,
Change Harvesters Take Change Read More »
In our change-harvesting take, we have human, local, oriented, taken, and iterative as our attributes of successful change strategy. Let’s take up oriented: How do we reconcile our emphasis on locality against the far-away target that is our goal? Before we begin, I want to reiterate my support for those folks out in the world
Change Harvesters Orient Their Changes Read More »
We change-harvesters say human, local, oriented, taken, and iterative. We talked about human a couple of day ago, let’s take on local. A quick sketch of the idea, and a couple of cases will do, yeah? Previous Post: Change-Harvesting Emphasizes the Human I write about geekery as a kind of comforting respite from other concerns.
Change Harvesting Makes Local Changes Read More »
Human, local, oriented, taken, and iterative: this is how change-harvesting in software development approaches change in most contexts in the trade. Let’s take "human" today, and see where it leads us. Before we begin, I want to express my continued support for the protestors. They’re still out there, folks, still peaceably seeking change, and still
Change Harvesting Emphasizes The Human Read More »
To make the case for Change Harvesting as an approach, it’s important to understand that the cost of Rework Avoidance Theory isn’t imaginary or subtle, but both concrete & quite high. Geekery’s not the most important story for me right now, it’s really just comfort food. Rest, but don’t get distracted. Black lives matter. Stay
The Cost of Rework Avoidance Theory Read More »
Change-harvesting software design centers "online" brownfield development: change-centric thinking. Most older sets of design imperatives are based in "offline" greenfield development: build-centric thinking. The differences can — and should — lead to design disagreements. This week, regular like clockwork, we shoot yet another unarmed Black man in the back, and we quietly arrest a white
CHT Means Different Design Imperatives Read More »
