Essays
The Journal253 essays
Long-form writing on AI, philosophy, psychology, and systems thinking.
-
The Vibe Coding Trap: Engineering Fundamentals With AI
Vibe-coded projects had far more production defects than AI-augmented engineering projects. AI tools make engineering judgment the primary bottleneck.
-
The Architecture of Trust: Designing Systems People Can Rely On
Trustworthy systems share four architectural properties: predictable failure, transparent state, bounded response times, honest errors.
-
Onboarding as Knowledge Architecture
Onboarding is a system design problem. Redesigning it as knowledge architecture shortened time-to-productivity and cut new hire attrition in early months.
-
On Trusting Systems You Cannot Fully Inspect
Deploying opaque AI systems creates tension between utility and epistemic responsibility. Current interpretability explains only part of model behavior, which makes trust in AI systems a question of responsibility, not proof.
-
Prompt Patterns as Architectural Contracts
Treating prompt templates as versioned architectural contracts noticeably reduced production incidents. Prompts deserve the same engineering rigor as API specifications.
-
Feedback Loops: Control Theory to Retrospectives
Nearly every organization audited measured output, but only one had a closed-loop learning system. Measurement without correction is not feedback.
-
The Phenomenology of the 3AM Page
The Three AM page strips away organizational scaffolding and reveals the true architecture of the system and your understanding. Heidegger called it Angst.
-
Imposter Syndrome as Socratic Wisdom
Imposter syndrome is the emotional experience of Socratic wisdom without the framework to recognize it as virtue. The doubt is the competence.
-
Heidegger’s Enframing and the Jira Dashboard
The Jira dashboard enframes engineers as standing reserve. Heidegger's Gestell explains why velocity metrics conceal the most valuable engineering work.
-
API Design as Organizational Philosophy
API design reflects organizational values. REST, GraphQL, and gRPC each encode different assumptions about power, responsibility, and team relationships.