Summary

Fowler observes that developers skip the collaboration rituals they'd naturally use with human pair programmers when working with AI coding assistants, leading to a 'Frustration Loop' of generate-review-regenerate cycles. He argues the friction is not a failure of AI capability but of how we collaborate with these systems. Drawing on the parallel to onboarding and pairing with human teammates, he proposes five patterns: Knowledge Priming, Design-First Collaboration, Sensible Defaults, Context Anchoring, and Feedback Flywheel. The core reframe is treating AI as a junior teammate with infinite energy but zero context, not as a tool. Together, these patterns aim to build a shared mental model that reduces translation friction and shifts cognitive load from correction to intent.

Key Insight

The practices that make human pair programming effective—onboarding, structured design discussion, shared standards, and documented decisions—apply equally to AI collaboration and are the primary lever for reducing AI-assisted development friction.

Spicy Quotes (click to share)

• 7

  AI assistants are like junior developers with infinite energy but zero context.

• 6

  The time saved by AI-generated code is often consumed by the effort required to correct it.

• 5

  They produce what might be called 'the average of the internet' rather than code that fits a specific team's architecture and conventions.

• 6

  The work has shifted from writing to fixing, but the total effort may not have decreased.

• 2

  The cognitive load shifts from constant vigilance and correction to expressing intent and refining output.

• 2

  Developers who internalize this approach will experience AI as a force multiplier rather than a source of friction.

• 2

  When defaults exist as artifacts rather than intuition, they apply consistently regardless of who is prompting.

• 3

  This is the difference between struggling with a tool and collaborating with a capable partner.

Tone

pragmatic, pattern-oriented, measured