The Journal
Essays
Long-form writing on AI, philosophy, psychology, and systems thinking.
-
Configuration as a First-Class Architectural Concern
Configuration-related failures caused 43% of production outages across 19 systems, exceeding code bugs at 31%. Configuration deserves the same design rigor as source code.
-
Integration Architecture Is Where Good Systems Go to Die
Integration points accounted for 58% of production incidents despite representing less than 15% of total codebase. Integration is where architectural quality is tested most severely.
-
The difference between systems and processes (and why it matters for your work)
-
Event Sourcing as Organizational Memory
An event-sourced system maintained 2.8 million state changes over 3 years, enabling state reconstruction at any point in time and reducing audit preparation by 83%.
-
AI Ethics in the Supply Chain: Training Data Provenance Problem
Tracing training data lineage for 3 models revealed none could document full provenance. One model included 12 sources with no consent chain. AI has a data supply chain problem.
-
Jira Has a Philosophy Problem, Not a UX Problem
Jira attempts to be both a coordination tool and a surveillance instrument. Separating these functions reduced cycle time by 28%.
-
Estimation Is Epistemology: Confidence Intervals
Calibrated teams delivered within 15% of estimates 74% of the time versus 31% for gut-feel. The difference was self-knowledge, not technical skill.
-
Cognitive offloading and the changing shape of human expertise
-
Data Literacy Is a Leadership Competency, Not a Technical Skill
A survey of 40 executives found 28 could not explain how their key revenue metric was calculated. Data literacy is a competency for every decision-maker, not just analysts.
-
The SOPs That Survive: What Makes Them Standard
Studying 34 SOPs across 5 organizations found only 26% were followed. Surviving SOPs were practitioner-authored, under 2 pages, included decision points, and updated within 90 days.