Conflict Resolution
Fixes for the bugs in your relationship with AI. Practical, tested habits for working with AI assistants, one resolution at a time.
Take the Break
A forced pause is a good time to do the things fast AI sessions skip: review, test and plan.Keep Shipping When the AI Can’t
Outages and limits happen. Keep the skills and the to-do list that let you work without an assistant.Mind What You Paste
Before you paste code, logs or a whole conversation into an AI tool, check for secrets, customer data and company policy.Context Is a Deliverable
A good context brief is the most underrated part of working with AI. Write it like you’d brief a new teammate.Second Opinions Done Right
Asking a second AI tool to review the first one’s work can catch real problems, if you ask the right way.Break the Retry Loop
Same change, same error, twelve times. When an AI keeps retrying a fix, change the input, not the attempt count.Budget Your Tokens
Long conversations get slower, pricier and more confused. Keep the context lean and start fresh on purpose.Know When to Take the Keyboard Back
Sometimes the fastest path is to write the fix yourself. Here’s how to recognize the moment.Match the Model to the Job
Not every task needs the most powerful model, and some tasks really do. Choose on purpose.Know Your Plan’s Limits
Context size, rate limits and feature tiers explain a lot of “bad AI” moments. Read the fine print before you blame the model.Get More From the Model You Have
Before you upgrade, upgrade your requests. Better context beats a bigger model more often than you’d think.New fixes every week. Free.
- All 9 episodes, from Episode 1 on
- Paul’s Hint of the Week: a step-by-step guide to better AI coding, every week
- All three Conflict Resolution tips for every episode
- The Weekly Commit: the new episode and a fix in your inbox each week