Renaissance Architecture

A thoughtful counterpoint to cargo cult development that challenges you to build new things instead of variations on existing patterns. Invokes it when architecting features, reviewing designs, or making framework choices. The strength here is the pragmatic decision tables: when to move from SQLite to Postgres, monolith to services, local to cloud. It's opinionated about starting simple and adding complexity only when pain is measurable, not anticipated. The UI/UX section on immediate feedback and visible state is solid. Fair warning: this assumes you have the luxury of first-principles thinking. If you're building in a regulated industry or extending legacy systems, much of this won't apply.