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 »
A lot of the reasons that change fails, inside & outside technical organizations, come down to one broad statement: the people who have to make the changes are humans, and the people who want them to make the changes have not successfully taken this into account. Before we proceed: Changing a software development process
Human-less Change Fails Read More »
Sooooooo. I’m gonna write a little bit about geekery. But I do want to frame it for you a little. Geekery is not very important right now. My country is in the throes of facing down a violent uprising by uniformed militia, spurred on by parts of the government. So, geekery, no. Not important. But,
More seriously, the first piece of advice I’d give a monolith-owner about converting to microservices would be to work very hard to factor their monolith well. Interestingly, across dozens of cases, I’ve never seen that advice taken. There’s always a well-dressed person with excellent powerpoint who is happy to give a compelling case for a
The Jump to Microservices Read More »
I shipped a word processor that formatted the hard drive every 1024 saves. Must have been ’84 or ’85. I was a bright 25-year-old with about five years in the game. I was one of two programmers who wrote & maintained a suite of apps kinda like Office: spreadsheet, wp, database, plotter, such like. We
Lotta inspiration for junior geeks stuff floating around. I’m having a low productivity day today because, well, you know all of that, so I’ll take a minute nd pitch in. Do you know what I did for about twelve elapsed hours of coding time? I solved a problem. Cuz, you know, I got mad skillz,
Juniors And Seniors Read More »
Now we’ve seen these basic ideas, human, local, oriented, taken, and iterative. I want to use them in a particular way for a bit. Let’s take some practices we know we like, and work backwards, seeing if/how these "known-goods" relate to those ideas. Let’s talk about "Working By Stories" for this first one. I’ll describe
Working By Stories – A Change Harvester’s Take Read More »
TIme to take up “iterative”, the last, but by no means least, of the bywords of the change-harvesting worldview: human, local, oriented, taken, and iterative. Previous Posts in This Series Here: Human Change Local Change Oriented Change Taken Change The heart of the iterative approach is assuming change. We embrace it, we plan for it,
Iterative Change – What and Why Read More »
Human, local, oriented, taken, and iterative, those are the hallmarks of the change-harvester’s approach. This morning I want to tackle “taken”, which is about grounding the substance and approach of our changes to the situation that is already there. Want to catch up? Previous articles in the series here: Human Change Local Change Oriented Change
Taken Change – What and Why Read More »
The change-harvesting approach has these elements at its base: human, local, oriented, taken, and iterative. Today, I want to talk about what that adjective “oriented” means. Prior muses on human and local are here: Human Change: What and Why Local Change: What and Why We’ve said that leaning in to the humans in our systems
Oriented Change – What and Why Read More »
