Engineers and engineering leaders
Folding agents into how you already build: planning-first development, capturing context, and reviewing PRs with an agent in the loop, while you stay as hands-on as you want to be.
AI coaching on your actual work.
One-on-one. Not a course.
I pair with people, from CTOs to first-time builders, to make language models and coding agents part of how they work. We work on the real thing, and you keep the workflows we build.
ScrollHow coaching works
Coaching happens on your actual work, not exercises. We pick something you need to get done, a feature, an analysis, a review, a tool you wish existed, and do it together, with me steering the process and you staying in control of the decisions.
Along the way I introduce the workflows that make agents productive: capturing your thinking as context, planning before implementing, reviewing and iterating, and using git to make checkpoints you can always return to. What sticks becomes your default way of working, not something you watched in a demo once.
The cadence fits the goal: a single working session to break through something specific, or recurring sessions over months to build capability that compounds.
The goal is that you need me less over time.
Who I coach
The starting points vary a lot. The shape of the work doesn't: your goals, your tools, your problems.
Engineers already fluent with agents
Codifying the workflows you apply by hand into skills your agents use by default, and structured reviews that catch what's hard to see from inside a project. One caught a blind spot that saved roughly two weeks.
Domain experts building their own tools
Designers, operations professionals, traders, and researchers who know exactly what the work needs. We build the tool you've been wishing existed, and you learn to maintain and extend it yourself.
People starting from zero
No coding experience needed. We start from fundamentals, how to steer models, manage context, and avoid pitfalls, and work up to building real software with an agent.
AI coaching questions
- What's the difference between coaching and upskilling?
- Upskilling is for teams: structured sessions that build understanding from first principles. Coaching is one-on-one and built around your actual work. They pair well, sessions to build shared understanding across a team, coaching to make it stick for the people who will use it most.
- Do I need coding experience?
- No. I've coached people writing their first line of code with an agent and senior engineers at big tech companies. We start from wherever you are.
- What does a session look like?
- We pair on something real you need to get done. You drive as much as you want; I steer the process, introduce workflows as they become useful, and make sure you understand what happened well enough to repeat it on your own.
- How long does coaching last?
- It varies. Sometimes a single session gets you unstuck. Some of the people I've worked with longest started with no experience and, over months of recurring sessions, now build and maintain software their organizations rely on.
- Is coaching only for individuals?
- Mostly one-on-one, but small groups with shared context work too: a founding team, a design org, an engineering pair. Past a certain size, structured upskilling sessions are usually the better fit.
Have something you've been meaning to build or figure out? Bring it to a session.