🏗️Architects Should Coach Devs, Not Gatekeep: Fitness Functions Take Over

Your architect can't review every PR anymore

Stop copying the big tech architecture playbook and expecting it to work. Architecture is a socio-technical discipline, which means your org chart and your team's history matter as much as your service diagram. Friction in a system is feedback, not just noise. When two teams keep colliding, that's usually a misalignment problem first. If you're an architect, the job is shifting from reviewer to coach. Dedicated architects on every team doesn't scale, so the move is to set clear guardrails and architectural fitness functions, then let developers make decentralized decisions inside them. For engineers, that means fewer design-review bottlenecks and more ownership, as long as the guardrails are written down and automated. The source material is blunt about where to spend senior attention: high-volatility areas get experienced engineers, while generic domains are safer to hand to probabilistic AI agents. Learning works the same way. Lectures give you a starting point, but the real knowledge comes from collaborative study, case studies, and shared experience that evolves over time.