"Path-focused design", of stories, architecture, code, is design that understands that we can only reach a distant City on the Hill by taking one stride-limited shipping step at a time. Sunday muse-day, comfort food for the geek in me and in you, but please remember, we don’t really just want to change code, we want […]
Path-Focused Design Read More »
Big-batch releases, coordinated and controlled by a central intelligence, fail, and fail frequently. Several aspects of this are fascinating, because of the interplay of hard mathematical reality with human frailty. Let’s take a swing. It’s Sunday muse-day, comfort food for the geekery-inclined. Enjoy, take respite, but don’t forget we want to change a lot more
Big Batch Releases Read More »
You can put all your configuration in a shared library and eliminate just about every mis-configuration in your multi-process application. It’s not free, but it’s cheap, and it kills a lot of minor pain. Let’s take a gander. It’s Sunday geek comfort-food time. I hope you enjoy it, and I also hope you remember it’s
Sharing Configurations Read More »
When large teams struggle with trunk-based development (TBD) or continuous integration/deployment (CI/CD), a good strategy is to re-orient how the teams face "backsteps", moments in our workflow where a discovery forces us to re-open a stage we thought was closed. It’s been a hard stretch for those of us seeking peace and equity. I offer
Re-Orienting Around Backsteps Read More »
A couple of days back, I tweeted about SAFe. It created some stir on the timeline, which was great, as I got to see a lot of perspectives. I want to use that tweet as an excuse to talk about something much larger. This will be a long one. 🙂 Meanwhile, I remind you, geekery’s
The standup is a short recurring meeting used to (re-)focus the team-mind on effectively moving stories through our workflow. Here’s my recommended approach to having standups be useful and brief. The general sequence is 1) address team-wide emergency issues, 2) work story-by-story, 3) distribute new work, 4) address team-wide non-emergency issues. Note that, quite often,
The ultimate making app for a shipping multi-service system is actually a one-machine monolith with a UI. If your team is experiencing the most common pains from working in a large SOA environment, the productivity payback will be enormous. It’s important for me to take a second to remind you that there’s much more to
The UI Monolith Making App Read More »
My rice’n’garlic advice, "take many more much smaller steps," can be said another way: reject any proposed path that requires a step size larger than the limit you’ve set for that particular domain of activity. Time for Sunday geek comfort. It’s meant to be respite. There are more important things than geekery, so please remember
Rice & Garlic & More Smaller Steps Read More »
Once armed with the idea of a shipping app and a making app, a whole range of possibilities open up. Among the most powerful: give your making app a UI just for making. It’s Sunday, which is geek comfort food day for me. Remember, tho, to think and feel and work outside the monitor. Please
In a data-rich environment, we can use the Builder concept to make DSL’s for our Making application. This often makes testing the hard business core of our code both faster and easier. Folks, I love sharing my geekery with you. For me, it brings much comfort. I hope, tho, you’ll join me in working for
