The Journal
Essays
Long-form writing on AI, philosophy, psychology, and systems thinking.
-
Designing Systems That Survive Their Architects
Systems with comprehensive documentation maintained 94% operational effectiveness 12 months after architect departure, compared to 47% for systems relying on tribal knowledge.
-
Writing as Thinking: Why Technical Leaders Write
Leaders who write weekly produce 52% fewer dependency conflicts and 3x fewer reversed decisions. Writing is the thinking, not documentation of it.
-
Database Architecture Decisions Outlast Every Other Technical Choice
In 22 systems, database decisions made in the first 3 months remained the most constraining technical choice 5 to 10 years later. Only 3 ever migrated, at an average cost of 7.4 engineering months.
-
Evaluating LLMs Is the Hardest Problem in AI Engineering
Teams without systematic evaluation ship features with 3.4x higher defect rates. Building rigorous evaluation infrastructure is the hardest and most valuable AI engineering problem.
-
The Ship of Theseus and Continuous Deployment
The average application replaces 97% of its code within 5 years. The Ship of Theseus reveals that system identity is narrative continuity and purpose, not material composition.
-
Agile’s Midlife Crisis: Returning to First Principles
Teams closest to Agile's original principles had the fewest certifications and lightest processes. The industry built around Agile inverted its promise.
-
Observability for Ethical Systems: Monitoring Beyond Uptime
Adding fairness metrics to a recommendation system serving 1.2 million users revealed 3 systematic biases that traditional uptime and latency monitoring missed over 14 months.
-
Autonomous Agents Need Epistemology, Not Parameters
The bottleneck in autonomous agents is epistemic competence, not capability. Implementing uncertainty quantification reduced confidently wrong actions by 78%.
-
Designing for Composability: Building Systems From Interchangeable Parts
Systems designed for composability reduced feature development time by 41% and integration effort for new channels by 67% across 9 organizations adopting composable architecture principles.
-
Data Observability Needs Product Thinking
Standard observability caught 78% of structural failures but only 11% of semantic failures. The undetected semantic failures caused 19x more business impact.