Judgment, not syntax
No language or framework lock-in. A transferable way of thinking — requirements → constraints → quality attributes → trade-offs — now applied to technology stack selection.
Writing code is disappearing; judgment is what's getting valuable. 34 architecture-thinking chapters + 26 real-system architecture maps + 6 end-to-end cases — architecture only, no syntax.
✅ Fully bilingual. All 34 tutorial chapters, 26 templates, and the first 6 cases are available in English — use the language switch (top-right) or browse
en/in the repo. Contributions welcome.
Click a category to filter, then click any card to jump to that template's architecture map.
The case track is not more templates. It is a full product walkthrough: starting architecture, quantified trigger signals, ADRs, data flow, failure fallbacks, and quick checks. 👉 Enter the case track
The new technology stack selection track (27–34) is not a framework tutorial. It teaches the architectural judgment behind language, databases, cache, APIs, deployment, observability, and AI infrastructure. 👉 Start from Chapter 27
The most valuable section of every template is "Key Decisions & Trade-offs." Try this interactive starter:
Before diving in, check your gut sense of 'architecture':
Ready? 👉 Start from Chapter 01, or browse 26 architecture maps on GitHub.