Working essays from the senior bench. Not thought leadership. Field notes — patterns we use, mistakes we have made, questions we have not finished answering.
Modular monoliths spent two years on the conference circuit. Now that the noise has died down, what does it actually look like to build one in .NET 9? A field-tested take on seams, boundaries, and the patterns that survive contact with production.
ReadWhat happens to a React codebase when state lives where it belongs — closer to where it is used, further from a single global store. A short defence of co-located state, plus three patterns to replace the things Redux was actually solving.
ReadA working pattern for building AI-augmented products. Lightweight listeners detect intent. Mid-weight workers do the routine work. A heavy reasoner is reserved for the calls that need it. Orchestration ties the three together.
ReadMost professional-services contracts pad the scope with low-confidence work to absorb risk. What happens when you bind scope at the Epic level and treat the contract as an outcome commitment? Notes from a year of doing it.
ReadThe three ways — flow, feedback, continuous learning — were articulated more than a decade ago. What does each of them look like now, after a generation of practice? An honest reread for working engineers.
ReadArchitecture decision records as a discipline. The economics of senior consulting. AI evaluation harnesses that work. Subscribe via the contact page to be notified.
Field notes, not thought leadership. Earned, not opined.