Writing
I started writing to think, not to publish. A post is usually me trying to work out whether an idea holds up when I write it down. Sometimes it does not and I learn something. Sometimes it does and it becomes the seed of a white paper. Some of the white papers eventually became a book. I am not sure that is a writing strategy. It is just what happened.
I have been at this for a short time and I am still figuring it out. What I do know is that if you want to understand something deeply you have to force yourself to write about it and build it. The writing makes the thinking visible. The building makes the thinking honest. The published artifact is almost a bonus. The real value is in what you learned getting there.
Mastering Software Architecture for the AI Era
This is where the C-DAD thinking lives. Posts about contract-driven development, AI-native architecture, what it actually takes to make software organizations ready for agentic systems, and the patterns that keep showing up when that goes wrong. The writing here tends to be more conceptual. It is me trying to figure out what the next version of software architecture looks like when AI agents are a real part of the system.
The Rise of Device-Independent Architecture
This is where the UMA thinking lives. Posts about WebAssembly, portable systems, device-independent architecture, and what it means to design software that runs where it makes sense instead of where the stack happens to put it. The writing here tends to be more technical. It is me working through the ideas that ended up in the book and the companion repository.
Software Architecture Radar
A monthly publication of 10 architecture signals worth paying attention to. Curated from the knowledge graph behind the published work and reviewed each month. Each issue includes a short editorial note on what the signals point to collectively, followed by the ten items.