Engineering Culture
A Calm Script for Difficult Feedback
A practical guide to difficult feedback in engineering teams: how to prepare the facts, keep dignity in the room, name behavior clearly, and turn a tense conversation into a fair next step.
Writing
Blog
Deep-dives on software architecture and the way source code is structured — written to be understood by beginners, yet useful to teams shipping at scale. Diagrams, real examples, no hand-waving.
Latest articles — Page 8 of 23
Source & Architecture
Observability as a Design Choice
A practical explanation of observability as an architecture decision: why teams should design logs, metrics, traces, dashboards, and alerts into the system before production asks hard questions.
Ways of Working
Cross-Functional Teams
A practical look at cross-functional teams: why they exist, how shared outcomes reduce handoff friction, and what teams need around ownership, rituals, decision-making, specialist depth, and healthy disagreement.
Perspectives & Field Notes
The Loneliness of the Solo Developer
A reflective essay on solo development: the freedom and pressure of working alone, the missing feedback loops, and the small systems that make solo work more sustainable and less isolating.
AI & The Future
Vector Databases Explained
A beginner-friendly explanation of vector databases: how embeddings represent meaning, why similarity search helps AI products, and what teams need to handle around chunking, metadata, freshness, evaluation, and cost.
Engineering Culture
Fostering Innovation in Teams
A grounded reflection on fostering innovation in engineering teams: how psychological safety, slack, user context, small experiments, technical quality, and honest prioritization help ideas become useful change.
Source & Architecture
The Outbox Pattern
A practical explanation of the Outbox Pattern: why dual writes fail, how a transactional outbox keeps database state and events aligned, and what teams still need to handle around retries, idempotency, ordering, cleanup, and observability.
Ways of Working
OKRs for Engineering Teams
A practical guide to engineering OKRs: how to connect outcomes to delivery work, avoid task lists disguised as objectives, choose useful key results, and keep learning visible during the quarter.
Perspectives & Field Notes
Learning a New Language Every Year
A reflective essay on learning one new programming or human language each year: how unfamiliar grammar, small exercises, patience, and comparison sharpen the way we think and communicate.