Article
Against Shiny-Object Architecture
New tools deserve evaluation, not automatic adoption or automatic rejection.
Deliver. Business. Value.
Notes from building things that had to survive first contact with customers.
What worked. What didn't. The cost of learning the difference between the two.
Field notes
Start Here
A short path through the center of the site.
Operating stance
Change is the default condition.
Good systems are not made by chasing every new surface area or flattening every disagreement into committee language. They are made by naming volatility, keeping options open where change is likely, and choosing proven mechanisms where behavior is already well-understood.
Field notes
Featured Writing
One entry that anchors the current direction of the site.
Field notes
Latest Writing
Concise notes on architecture, AI, complexity, and the work of staying intellectually honest.
Statistical Inference ≠ Judgement
Guessing is not judgement.
Using Enumeration Generators
A lab note on using a source generator to turn a small enum specification into a richer enumeration type.
Why Use an Enumeration Class?
A lab note on replacing weak enum usage with richer named values that can carry identity, behavior, and safer conversion rules.
Coverage Did Not Fix the Design. It Exposed It.
A field note on using code coverage to reveal tangled responsibilities, hidden coupling, and the real cost of a big ball of mud.
Coverage Did Not Fix the Design. It Exposed It.
A field note on using code coverage to reveal tangled responsibilities, hidden coupling, and the real cost of a big ball of mud.
Headcount Is Not Throughput
A field note on why adding another developer can slow a team down when the system and process cannot absorb more coordination.
Field notes
Active Series
Recurring threads without a heavy taxonomy.
Projects
Public repos, not private drafts.
This is the working code that is actually published: source repositories and NuGet packages, kept separate from the private-implementation lessons that live in Field Notes.