Skip to main content
Architecture

The Architecture Decision Nobody Writes Down

December 20, 20259 min read
ArchitectureDocumentationADRDecision MakingBest Practices
Share:

Six months ago, I chose Supabase over Firebase for Nexural. I had good reasons — PostgreSQL, row-level security, self-hostable. But I almost forgot those reasons. The only thing that saved me from re-evaluating the same decision (and wasting a week) was a markdown file I wrote in 15 minutes.

The Problem

Every engineering team has this conversation:

"Why do we use RabbitMQ instead of Kafka?" "I think Dave chose it. Dave left 8 months ago." "..." "Should we switch to Kafka?"

And now you're spending a sprint re-evaluating a decision that was already evaluated. The institutional knowledge walked out the door.

Architecture Decision Records (ADRs)

An ADR is a short document that captures a significant decision. Mine are dead simple:

\\

Related reading

All posts →
Jason Teixeira
Written by
Jason Teixeira
Founder, Sage Ideas Studio
More about Jason →

Want to see this in action?

Check out the projects and case studies behind these articles.

livebuild 29be8ec2026-06-11 06:38Z
// solo studio// no analytics resold// every commit human-reviewed