Muses

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. But those other concerns are far more important. Black lives matter. Please help me support and empower this movement for equity and peace. Stay safe, […]

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 risking life & limb in the face of armed violence every day. Stay safe, stay strong, stay angry, stay kind. Black Lives Matter. When we

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 safe, stay strong, stay angry, stay kind. We can change this. We’re the only thing that can. The most essential aspect of the RAT (Rework

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 man carrying a long gun he has just used to kill people. Stay safe. Stay strong. Stay kind. Stay angry. Help us change this. Black

Let’s compare and contrast the RAT (Rework Avoidance Theory) model of software development with the CHT (Change Harvester Theory) model. The differences are multiple and pronounced, so this may take us a while. It is not rote for me: there are many more important things to be doing right now than geekery. I’m actively supporting my friends & family out there seeking equity in the streets. Stay safe, stay strong, stay angry, stay kind. Black lives matter. I want to

A flow app, one that steps the user through an acyclic graph, typically gathering info at each stage, can be built to provide iterative user value by gradual refinement. Let’s look at how that’s done. Before we get into it, for me, and maybe for you, too, geekery right now is not the most important story. It’s just comfort food. If you’re out there working for change today, I support you wholeheartedly. Black lives matter. Stay safe, stay strong, stay

How do we iterate user value? How can we follow the "more smaller steps" approach and still deliver a positive experience for the user? Today let’s look at some ways to approach this problem. It’s important for me to remind you that, for me and many others, working for equity in the world is far more important than geekery. I regard this as a side-story. Stay safe, stay strong, stay kind, stay angry, please, because black lives matter, and we