Max Heyer spent two decades writing code before realizing the real satisfaction came from decision-making, not typing. Now an architect at enum, a European sovereign cloud company, he focuses on reviewing code rather than producing it. AI coding tools have shifted his role from writer to evaluator, making him read more code than ever while spending less time on mechanical implementation.

The transition wasn't about avoiding work—it was about prioritizing higher-value activities. Heyer discovered that the fun part of coding was always the design decisions: what the system should do, how it behaves under failure, where complexity lives. AI tools compress the translation phase, allowing him to spend more time on architecture and specifications while multiple agents implement his designs.

However, this shift raises concerns about dependency on AI tooling. Heyer admits that if AI coding disappeared tomorrow, he'd likely quit coding entirely. The years of muscle memory have faded, and rebuilding them feels like a waste of time. His identity as a coder now depends on tools that could regress, potentially taking his professional self with them.

His core insight is that coding was never about typing—it was about decisions becoming reality. AI shortens that loop, but only works if the tools hold. When he notices patterns that don't fit or fake test coverage, his architectural judgment matters more than ever. The work has always been about taste: knowing when a design is bad and what assumptions will break.