This branching thing. The idea behind branching is that it provides advantages in situations where a code change is large. The idea behind non-branching is not to enter those situations. These two views seem very difficult to reconcile. I am a non-brancher. I push to head, I pull from head, I test on head, I […]
The Baseless Critique Of Living Branchlessly Read More »
I mentioned endpointing yesterday. I’m always using geepaw-isms & expecting people to know what I mean. Endpointing is over-focus on eventual destination. In s/w, it’s seeing development as a long trip to a known destination on a known map. John Winthrop, a few centuries back, used "the city on the hill" to describe an endpoint,
Endpointing vs. Next-Stepping Read More »
Of all the bad advice the geek trades inherit from over-simplified manufacturing & engineering, perhaps the worst: "avoid changing code". Take a minute, and think of all the things the trade does to avoid changing code. Virtually every element of "big design up front" policy is based in this view. Long stretches for analysis, longer
“Avoid Changing Code” Should Be Avoided Read More »
In IT work — "it puts the database on its browser skin" — we often face sooner or later the problem of the gigantic object. Some systems, especially "global monolith reboots", just start there. Others just grow and grow and insensibly slide into it over time. The problem is that there are one or a
Using Strategy & Function-Specific To Attack Large Classes Read More »
So, a friend asked me to say more about "not pairing". As so often, it triggered me to muse. Sometimes I need to not pair. Now, don’t get me wrong, I love pairing. I love it for three reasons. It makes me a better geek. That is, I learn from pairing. Pairing makes two geeks
When I Need to Not Pair Read More »
Let’s review "reversible raincoat tests." Sometimes, we build systems in which a downstream collaborator must interface with an upstream one. The two apps are by separate teams, on separate servers, developed at separate times, and still both in development. A reversible raincoat test is a script with two sides. Think in terms of a literal
Reversible Raincoat Tests Read More »
Yesterday I mused about explanation privileging, where one always reaches for one ring to rule them all in their explanations of behavior. This morning I am thinking about the reasons that happens. Don’t be alarmed, i’m not gonna suggest there’s just one reason for it every time it happens, i’m circular, every argument is circular,
On One Ring To Rule Them All? Read More »
I’m thinking of this thing called "justifcation privileging," or alternatively "explanation monism". Or even, short hand and jokily, "one ring to rule them all." One constantly sees tweets, blogs, even books, where someone boils down staggeringly complex and ill-understood processes to one factor. Today I saw "people don’t make decisions rationally, they make them emotionally."
Why Do We Seek One Ring To Rule Them All? Read More »
I can’t over-emphasize for new coaches the importance of rampant opportunism. Until you’ve established your miracle powers in a team, you won’t be able to move big levers, only small ones. Which small levers will bring you the biggest bang of trust & faith the fastest? Some possible openings: we find a bug that’s an
The First Coaching Days Read More »
Shifting certainties. This is where i’m headed these days. Without belaboring criticism, what i’m seeing is that we have a trade with a whole stack of roles and humans to fill them, and, of necessity, they have assembled a varied, sometimes compatible sometimes not, set of certainties by which they navigate. The trouble is that,
Shifting Certainties Read More »
