XP Practices + AI-Assisted Development

AI Is a Force Multiplier. Your Practices Decide What Gets Amplified.

Twenty years of Extreme Programming at BBC, Sky, EA, and Equal Experts. Now testing what happens when you combine disciplined practices with AI. Articles coming soon.

No spam, unsubscribe anytime.

What twenty years taught me

  1. Validate assumptions continuously, not once at the start. The market doesn't wait for your roadmap.
  2. Engineers who understand the business build fundamentally better software than those who work in isolation from it.
  3. Technical excellence - TDD, continuous integration, clean architecture - is what makes safe, rapid iteration possible. Without it, every change is a gamble.
  4. Real-time collaboration beats handovers. Pair programming surfaces problems in minutes that asynchronous review catches in days.
  5. The whole team owns outcomes. Not "developers ship features" and "product measures impact" - everyone owns both.
  6. Measure customer value and business outcomes. Lines of code is not progress. Velocity is not speed.

The product engineer

Traditional developers build what's specified. Product engineers shape what gets built. They combine technical expertise with customer empathy - participating in research, strategy, and design alongside implementation.

They know that architecture, testing, and deployment decisions directly impact customer experience. Every technical choice is a product choice.

This matters more with AI. When code is cheap to produce, the engineer who understands why something should exist is more valuable than the one who knows how to build it.

This is a mindset, not a role.

The feedback loop

Great products come from tight feedback loops. Each step enables the next.

Discover

Validate market assumptions before writing production code. Interviews, prototypes, MVPs. Learn what customers need, not what you assume they need.

Build safely

TDD, continuous integration, continuous delivery. When you can ship safely and frequently, you can test assumptions with confidence.

Collaborate

Strong technical foundations enable real collaboration between engineers and stakeholders. Pair, iterate, explore - together.

Ship calmly

Releases become a non-event. No drama, no all-nighters. That calm creates space for creativity and quality.

Learn

When releasing is routine, focus on what matters: learning what customers actually need. Validate quickly. Discard what doesn't work.

Compound

Each cycle builds on the last. Technical excellence makes change safe. Continuous feedback ensures you're building the right things. This is the advantage that compounds.

Stay in the loop

New articles on XP, AI-assisted development, and software craft. No spam, unsubscribe anytime.