When Coding Shrinks, the Developer Expands
Episode 4
Episode summary
Quentin Chevrin is a front-end developer in Sonar’s billing squad. In the space of a year, he moved from GitHub Copilot completing individual lines to working mainly through Claude Code and barely opening his IDE. Yet the most interesting part of his story is not that AI writes the code. It is how Quentin has retained ownership of the design, decomposition and context while using agents to implement the work—and how that combination has widened the range of engineering problems he can solve.
In this episode, Quentin walks through his workflow from Figma and Jira to focused agent sessions, automated analysis, AI code review and human approval. We discuss why he still writes his own tickets, how he changes the agent’s freedom according to the consequences of a mistake, why fast review is becoming the new bottleneck, and how AI is helping specialists make useful contributions across the stack without pretending expertise no longer matters.
About Quentin
Quentin Chevrin is a front-end developer at Sonar, working in the billing squad on the systems that support Sonar’s products and purchasing experiences. He is also a teacher and describes himself as a naturally sceptical adopter: interested in new tools, but reluctant to follow hype before they prove useful in real work.
In this episode
- 00:20 — Introducing The Next Commit and Quentin
- 02:14 — Development at Sonar before AI
- 06:16 — From Copilot autocomplete to Claude Code in the terminal
- 10:59 — Why the technical work still begins with people and Figma
- 15:39 — Writing Jira tickets as a way to build understanding
- 20:07 — Giving an agent the context you already possess
- 22:35 — Finding the right level of detail through experimentation
- 24:36 — Repository and personal CLAUDE.md instructions
- 28:06 — Constraints, steering and the causes of code bloat
- 31:45 — Adjusting agent autonomy to the risk of the project
- 35:23 — Small changes and fresh sessions to reduce error and token cost
- 37:28 — Quentin’s commit and pull-request review process
- 39:04 — SonarQube analysis, Gitar and human review
- 41:10 — Four pull requests in a day—and review becoming the bottleneck
- 43:30 — How rapid feedback protects developer flow
- 45:14 — From front-end specialist towards a T-shaped engineer
- 48:22 — Using AI to collaborate across squads
- 49:05 — Faster onboarding and safer boldness for new joiners
- 51:48 — Quentin’s advice: use AI to ask questions, not only to write code
- 54:22 — Designing software without writing every loop and condition
- 56:42 — Why Quentin is cautiously positive about what comes next
Key ideas
- Writing a ticket is not clerical work when the act of writing creates the developer’s mental model of the feature.
- Agents are more efficient when developers supply context they already have instead of paying the agent to rediscover it.
- The appropriate level of autonomy depends on consequence: a public, shared product deserves tighter scope than an internal or personal tool.
- Small tickets, focused prompts and fresh sessions limit ambiguity and make generated changes easier to review.
- Faster implementation moves the constraint downstream. Review, coordination and product judgement become more important as pull-request volume rises.
- AI can widen a specialist’s contribution without replacing deep expertise. The result is a stronger T-shaped engineer, not an expert in everything.
- Asking an agent to explain an unfamiliar system may be more valuable for learning and onboarding than asking it to generate code.
