[tyleo]

That’s how I feel too. When I was an architect at a ~300-person company, a big chunk of my job shifted to reviews, technical design docs, and guidance. I’m getting great results by feeding context like that into Claude Code, then reviewing and steering what it produces.

It really does feel like a multiplier on me and I understand things enough to get my hands dirty where Claude struggles.

Lately I’ve been wondering if that role evolves into a more hierarchical review system: senior engineers own independent modules end-to-end, and architects focus on integration, interfaces, and overall coherence. Honestly, the best parts of our product already worked like that even before AI.

[jimbokun]

I would collapse the senior engineer and architect roles into a single role and only hire people capable of doing both.

Owning the modules requires understanding the overall architecture and how the module’s API needs to fit into it, when a new module is required, when the architecture needs to change, and how to pragmatically migrate from one design to another in a live system.

All of that is easier if everyone is capable of operating at any level from overall architecture to micro optimizations.