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 […]
Change Harvesting vs Rework Avoidance Read More »
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
Iterative User Value in Flows Read More »
The correlation principle says that our productivity is tightly correlated with the internal quality of software. The two go up together, and they go down together, and you can’t trade away the one to get more of the other. Let’s talk it over. I remind us that geekery isn’t the main story right now, though
The Correlation Principle Read More »
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
Iterative User Value Read More »
The road to hell is lined with convenient parking spaces. I said recently that we need fewer addresses and more routes. These slugs are attempts to get at what I think keeps going wrong for us — in the trade, possibly in entire culture. There are numerous systems for software development out there competing in
A Question Of Humbling Proportion Read More »
Yesterday’s irritated blurt was a matter of feels, not an attempt to offer insight or ideas. I got some queries about it, so let me wipe that slate and be a little less irritated. For now, anyway. 🙂 In geekery — in all tool use beyond a certain point, but my focus here is on
Decomposition Rage Tweet Explained Read More »
Let’s talk a little bit about showing your working code to your product person. A basic recommendation, which will seem strange and likely freak you out the first time you hear it. Look to show your new stuff every day or two. I want to address here both the how and the why. The why
Showing Code Every Day Or Two Read More »
If we’re living now and always have been in the Age of Blurgs, then our strategy might change accordingly. Before I go to some ideas from the modern we got "The Age of Blurgs", and we got "Blurgs: Try Harder Won’t Work". We need some better ideas, and the modern synthesis has some. Today I
How The Modern Synthesis Tackles Blurgs Read More »
If we’re living now and always have been in the Age of Blurgs, then our strategy might change accordingly. Before I go to some ideas from the modern synthesis that are targeted at blurgs & blurging, tho, I want to point at one thing that won’t work, and why. What won’t work is "try harder",
Blurgs: Try Harder Won’t Work Read More »
So. I dropped out of the conference scene by and large for a few years for a variety of reasons. The last couple of years I have been returning to it. I’m just home from two conferences in three weeks. I am not an extrovert, at conferences, I like to hang around with individuals or
Please Go Find Out Read More »
