Slightly Caffeinated Podcast

@slightlycaffeinated.fm

Join @chrisgmyr.dev and @tjmiller.bsky.social as they talk Laravel and life as fathers and web application developers. https://slightlycaffeinated.fm

Watching how people use #Claude / #ai, the biggest split isn't prompt skill. It's context hygiene. Some clear and re-orient between tasks. Others run one session for days and wonder why it drifts. Knowing when to clear is the skill nobody teaches. How often do you actually clear?

Most mornings now I walk the neighborhood before work. Watch on, then I don't look at it. No phone, no headphones, no podcast. Just early sun and steps. My whole day moves fast with #AI. This is the part I keep slow 🌅

The #AI PR reviewer isn't something you install and forget. It's a prompt you tune. My first version missed findings a second reviewer caught cold. The fix wasn't a smarter model. It was recalibrating the prompt. The calibration is the actual product.

The useful #AI cost number isn't per-engineer or per-team. It's per-task. The same kind of ticket costing $1.50 one time and $15 the next isn't a billing detail. It's a map of where your workflow is inconsistent. Cost variance shows you which process to standardize next 💡

#AI accelerates the typing. It also accelerates the cost of not paying attention. Read the diff line by line. Note what surprised you. The small in-flight moments are where learning lives. Operator capability matters as much as agent capability right now.

Code review isn't the bottleneck. Lack of judgment is. #AI generates working code in seconds. The slow part is whether anyone can tell working from right. Review is the judgment layer. It always was. AI just made the bug-catching part cheaper, so the judgment part is what's left.

A 10-day feature is usually 1 day of typing and 9 days of waiting. Code review queue, env provisioning, approval chains, deploy windows, staging access. #AI sped up the 1 day. The 9 days didn't move. That's the speed problem nobody's solving.

A green test run tells you nothing about whether the system works. Especially when #AI rewrites the implementation and the test suite in the same change. What you're measuring now is whether the model kept both sides consistent. That's not correctness. That's just internal agreement.

💡 Managers change. Leadership changes too. A brag doc stays with you and survives all management changes and shifts. New leadership can read what you did. Old leadership won't remember. It's not ego work, it's continuity work

Code golf is dead. The whole game was "fewer characters wins." #AI handles the typing now. The new game is "will a stranger understand this in six months." Verbose and clear beats terse and clever. Optimize for the human reading the diff, not the one writing it 💡

Claude's first answer is rarely its best one. The second pass usually beats it. The third sometimes beats the second. Stop accepting the first response as the answer. Push back, ask for alternatives, or just say "try again." The cost is one more turn. The value is real #ai

Rolled Claude rules, Copilot config, and a baseline CLAUDE md to 30+ repos with one repeatable workflow. Teams reviewed and merged their own. The work per repo collapses to about a day once settled. You can move tooling fast across an org as long as adoption stays a team decision

Every time Claude Code does something unexpected, pause and ask it to reflect on the gap. Have it propose a change to your skills, rules, or config. Push it and move on. We're shipping 1-3 harness improvements a day without stopping feature work. The #AI setup improves as a side effect of using it 🚀

The biggest blocker to #AI adoption isn't the tooling. It's confidence. Watched an engineer hesitate to use AI on a shared repo because they weren't sure the output would hold up in review. The tools are ready. The trust isn't. That gap closes with pairing, not mandates 🧠

Most people stuff everything into CLAUDE.md because they're afraid the model will miss something. It grows until the model ignores half of it. The fix is the opposite: load only what's relevant to the current task - trust that less context with higher signal beats more context with more noise 🧠 #ai