Once AI coding agents reach a high performance level, objective benchmarks become less important than a developer's subjective experience. Like a warrior choosing a sword, the best tool is often the one that has the right "feel," writes code in a preferred style, and integrates seamlessly into a human workflow.

Using AI to code doesn't mean sacrificing craftsmanship. It shifts the craftsman's role from writing every line to being a director with a strong vision. The key is measuring the AI's output against that vision and ensuring each piece fits the larger puzzle correctly, not just functionally.

The most significant productivity gains come from applying AI to every stage of development, including research, planning, product marketing, and status updates. Limiting AI to just code generation misses the larger opportunity to automate the entire engineering process.

In 10 years, AI will generate vast amounts of high-quality code, similar to the leap in image generation. The developer's role will shift from writing code to curation and design, exercising intent and critical judgment to select the best output from a sea of AI-generated options.

Dr. Fei-Fei Li states she won't hire any software engineer who doesn't embrace AI collaborative tools. This isn't about the tools' perfection, but what their adoption signals: a candidate's open-mindedness, ability to grow with new toolkits, and potential to "superpower" their own work.

With AI agents automating raw code generation, an engineer's role is evolving beyond pure implementation. To stay valuable, engineers must now cultivate a deep understanding of business context and product taste to know *what* to build and *why*, not just *how*.

Treat advanced AI systems not as software with binary outcomes, but as a new employee with a unique persona. They can offer diverse, non-obvious insights and a different "chain of thought," sometimes finding issues even human experts miss and providing complementary perspectives.

The most creative use of AI isn't a single-shot generation. It's a continuous feedback loop. Designers should treat AI outputs as intermediate "throughputs"—artifacts to be edited in traditional tools and then fed back into the AI model as new inputs. This iterative remixing process is where happy accidents and true innovation occur.

The history of AI tools shows that products launching with fewer restrictions to empower individual developers (e.g., Stable Diffusion) tend to capture mindshare and adoption faster than cautious, locked-down competitors (e.g., DALL-E). Early-stage velocity trumps enterprise-grade caution.