Back to feed
Dev.to
Dev.to
5/9/2026
54 ADRs in 35 days: why I write the decision before the first line of code

54 ADRs in 35 days: why I write the decision before the first line of code

Short summary

Write architecture decision records before coding, not after—it forces explicit consideration of alternatives and prevents retroactive rationalization. With Claude Code, Rembrandt achieved 54 structural decisions in 35 days. Core methodology: Phase 0 grep for duplicate patterns, use challenger agents on significant changes, and demand specific technical justifications for rejecting each alternative.

  • Pre-write ADRs before any code to avoid retroactive rationalization and enforce genuine alternatives
  • Structure: decision, rejected alternatives with technical reasons, positive/negative consequences, references
  • Three disciplines: Phase 0 grep existing ADRs, challenger agent review, and strict justification for each rejection

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more