To get skeptical engineers to adopt AI, don't focus on complex coding tasks. Instead, provide tools that automate the tedious, soul-crushing "paper cut" tasks like writing unit tests, linting, and fixing design debt. This frames AI as a tool that frees them up for more enjoyable, high-impact work.

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.

The terminology for AI tools (agent, co-pilot, engineer) is not just branding; it shapes user expectations. An "engineer" implies autonomous, asynchronous problem-solving, distinct from a "co-pilot" that assists or an "agent" that performs single-shot tasks. This positioning is critical for user adoption.

In an AI-first world, an engineer's role shifts from writing feature code to building leverage. They become akin to staff engineers for AI agents, creating the systems, documentation, and automated tests (the "harness") that empower AI to produce high-quality work autonomously.

Building reliable AI agents requires a developer mindset shift. The most critical task is not writing the agent's code but creating robust evaluations ('evals') that define and verify the desired business outcome. This makes a test-driven development approach non-negotiable for enterprise AI.

Judgment Labs CEO Alex Shan argues that AI agents will first dominate domains with easily verifiable results, like coding, where a solution's correctness can be quickly checked. Progress will be slower in non-verifiable fields like law or complex drug discovery, where feedback loops are long and ambiguous.

Instead of focusing on foundational models, software engineers should target the creation of AI "agents." These are automated workflows designed to handle specific, repetitive business chores within departments like customer support, sales, or HR. This is where companies see immediate value and are willing to invest.

The debate isn't between manual coding and blindly trusting AI ("vibe coding"). A new discipline, "agentic engineering," is emerging. This involves creating new best practices, security controls, and governance for using AI agents to build software. This structured approach will replace the current era of unchecked individual developer experimentation.

The tech industry mistakenly assumes AI's rapid success in coding will replicate across all knowledge work. Coding is an ideal use case: text-based, easily verifiable, and used by technical experts. Other fields lack this perfect setup, meaning widespread AI agent adoption will be much slower.