Skip to content

The Debug Pub · AI Development Coaching

Build software with AI. Know what you're doing.

AI coding tools are great at generating code. Understanding what they've built, figuring out why it's broken, and knowing what to do next? That's another story.

Whether you're building your first app or you've been writing software for years, I'll help you get unstuck and become a better AI-assisted developer.

Bring your bugs. Stay for the beer.

Coaching for people building with Claude Code, OpenAI Codex, Cursor, GitHub Copilot and whatever comes out next week

// the problem

Your AI wrote the code. Now what?

Generating software and understanding software turn out to be different things. Sooner or later, most AI-built projects hit one of these.

  1. 01 The agent keeps making the same mistake, with total confidence, every time.
  2. 02 Fixing one problem creates three more.
  3. 03 It works on your machine. It will not deploy.
  4. 04 Nobody, including the AI, can explain how the pieces fit together.
  5. 05 Every new prompt makes the project a little more complicated.
  6. 06 You've spent three hours explaining the same thing to an AI that keeps saying it understands.

You probably don't need another AI tool. You need better judgment about the ones you already have.

// how it works

You drive. I'll navigate.

Live, remote and one-on-one, over a shared screen. Your project stays yours: your tools, your keyboard, your decisions.

  1. Step 1:Bring your project

    An application, an idea, a stubborn bug, or a workflow that isn't working. Whatever state it's in.

  2. Step 2:Work through it together

    We investigate the problem, talk through the options, and use your AI coding tools to make real progress. You're at the keyboard.

  3. Step 3:Learn to do it yourself

    You leave understanding what happened, why it mattered, and how to handle the next one without me.

// who it's for

Twenty minutes in or twenty years in.

Everyone is learning to work with a new kind of tool. The problems look surprisingly similar from either end, so the coaching adapts to you instead of sorting you into a box.

if (new_to_this)

Just starting out?

You've discovered that AI can build software. Now you're discovering that software development involves a little more than asking nicely.

We'll work on the fundamentals as they become relevant to your project. You don't need to become a computer science expert before you can build useful things.

what the code is doing · reading errors · git · databases · deploying · when to trust the AI

else

Already a developer?

You know how to build software. Getting consistent results out of AI coding agents feels like a separate discipline, and nobody handed out the manual.

We'll focus on workflows, architecture, context management, testing, and making AI-assisted development genuinely productive rather than merely fast.

task decomposition · context · agent config · review & testing · architecture

// services

On Tap

Private Coaching 60 min

One-on-one help with your project, your problems and your AI development workflow. A focused session tailored to what you know and what you're trying to do.

Happy Hour Free

A live group session where we tackle AI development questions, share what's working, and learn from each other's problems. Beginners and veterans alike.

~ · bash

$ whoami

TODO: founder name

$ cat role.txt

Staff Software Engineer

$ ls experience/

  • backend-systems/
  • go/
  • python/
  • postgresql/
  • redis/
  • kubernetes/
  • cloud-infrastructure/
  • application-architecture/
  • production-operations/
  • ai-assisted-development-workflows/

$ cat philosophy.txt

Teach people to fish. Don't fish for them.

$

Founder summary: name to be added, Staff Software Engineer. Experience in Backend systems, Go, Python, PostgreSQL, Redis, Kubernetes, Cloud infrastructure, Application architecture, Production operations, AI-assisted development workflows.

// behind the bar

AI can write your code. It can't give you experience.

I'm TODO: founder name, a Staff Software Engineer. I've spent years building backend systems and keeping them running in production, which mostly means I've watched a lot of things break and had to work out why.

That's exactly what's missing when an agent goes in circles: knowing why systems fail, how to reason about code you didn't write, and what makes something maintainable six months from now. I use AI coding tools every day. I know where they shine and where they quietly make a mess.

More about me and why I do this

// free community office hours

Happy Hour.
Debugging optional.

Got an app that's misbehaving? An agent that's going in circles? Or just curious how other people are building software with AI? Come hang out.

Free live office hours, practical discussion, and the occasional spectacular software failure. No sales pitch. No prerequisites. No actual beer required.

The format

Cost
Free
Where
Live, remote
How long
About an hour
Who
Every experience level
Bring
Questions, projects, war stories

Regular session times haven't been announced yet.

// faq

Questions from the bar

Something else on your mind? Ask me directly.

Do I need to know how to program?

No. You need a project, or an idea for one, and a willingness to poke at it. We'll pick up the concepts you need as they become relevant.

If you've never opened a terminal before, that's fine. We'll start there.

Can you help with my particular AI coding tool?

Probably. I work with Claude Code, Codex, Cursor and Copilot, and most coding agents share the same habits and failure modes. If you use something I haven't worked with, I'll say so up front. The engineering judgment carries over either way.

What if my application is a complete mess?

Then you're in good company. Most projects that come through the door are a bit of a mess. Part of the job is working out what's worth keeping, what to untangle first, and how to stop it getting worse.

Will you write the code for me?

No, and that's deliberate. Your hands stay on the keyboard and your AI tools do most of the typing. I explain, suggest, ask awkward questions and occasionally point at the screen.

If I fixed it for you, you'd be back next week with the same problem.

Can we work on an existing application?

Yes. That's the most common case. Bring what you have, in whatever state it's in.

What should I prepare before a session?

Have the project open on your machine, your AI tool ready to go, and a sentence or two about what you're trying to do and where you're stuck. Close anything containing passwords, keys or private data you don't want on screen.

Do you guarantee you'll fix my problem?

No. Some problems take longer than an hour, and some need information neither of us has yet. What you can count on: you'll understand the problem better at the end than at the start, and you'll know what to try next.

Is Happy Hour really free?

Yes. No card, no sales pitch at the end. It's a group session, so each person's problem gets a limited slice of time. If yours needs more than that, private coaching is there.

Can I book multiple sessions?

Yes, as many as are useful. Some people come once to get unstuck. Others come back as their project grows. There is no package to sign up for.

Do you work with confidential or proprietary code?

Carefully. You share your screen and stay in control of your machine. I don't need access to your repository and I don't keep copies of your code. If your employer has rules about showing code to outsiders, check them first; we can always work on a stripped-down reproduction instead.

Happy Hour is a group session, so never share confidential code there.

// last call

Still arguing with your AI?

Bring your project. Bring your questions. We'll figure out what to tackle next.

The Debug Pub

AI Development Coaching for people building software with AI, from the first app to the hundredth.

Bring your bugs. Stay for the beer.

The fine print

© 2026 The Debug Pub // written by a human, reviewed by a human, occasionally helped by an AI