All Posts
I write to think and explore. These posts aren’t one topic — more like finding a box of letters in the attic.
This morning, I un-bucket list
I meant to tell you a story about synchronicity and James Taylor. Instead, I made a list of twelve things I want to do. Not before I die, but while I’m busy living. Because linear time is fake and I can’t name any plants…
Introducing Systems ReArchitected
Architecting Systems has evolved into a systems-design community. The newsletter is now Systems ReArchitected. Because architecting a system is not enough.
This morning, I come out of the list geek closet
Lists are more than organization—they’re keys to who we really are. Apparently. Includes praise for crafting personal ontologies, a snark-fest of book titles, and the quiet terror of Pressing Send.
This morning, I dance
At a weekend workshop, I am confronted by my own discomfort. Dancing with others (gasp) — cracked something open. Sometimes, the only path to insight is to stop thinking and dance.
This morning, I am snark-bested by ChatGPT
Perhaps I have trained my assistant a bit too well. She is now the plucky comic relief side kick in my inner hero movie.
Why Knowledge Flow Matters
If you want to succeed in a knowledge economy… architect _Knowledge Flow_
Enough of What? An Exercise.
A writing exercise to uncover ‘enough of what?’ in which I share TMI and link to cool stuff.
Collaborative Modeling
A system falls apart when its parts speak different languages. Collaborative modeling helps teams build shared understanding before deep architectural schisms form. Also, the elephant parable.
Communication Patterns - APIs
As complexity increases, more software parts act as a source of information -- with layers that govern communication.
Communication Patterns - Decoupling
"Reducing coupling doesn’t necessarily reduce the risk of making a mistake when changing a single element. Reducing coupling reduces the number of elements changing at once and reduces the chances that you’ll miss one of…
Making Time for Thinking
As we move toward thinking together about a system of interrelated software, the conceptual load can become overwhelming. We don’t need to control everything. What we need is … time to think.
