Adoption
How teams learn to work with coding agents: where to start, how long it takes, what coaching adds, and why a rollout that leaves the team unchanged stalls.
- 13 posts, newest first
- Engineers finally get to work on the system When an agent gets it wrong, the fix is a rule, a skill or a hook rather than an edit to the code, so the engineer's job moves from working inside the system to working on it. Engineers were rarely given that job and have few criteria for doing it well, so a team has to decide what the work is judged by.
- Give every team one AI hypothesis instead of generic training Generic AI training across 300 people produces compliance, not adoption. One written hypothesis per team, tested on a retro cadence, makes the rollout correct itself.
- Find where the work piles up before you pick an AI playbook Four engineering organizations put AI on four different problems. What transfers from them is the diagnostic they all ran first: where does the work actually pile up?
- Run the migration you keep postponing as the training Train agentic engineering on the legacy migration the team has postponed for years, not on a sandbox. The team learns on its real codebase while the debt shrinks.
- When the CEO sits in the developer training AI stopped being a tooling purchase and became an investment in the environment: the harness, the context layer, the trained team, the hiring filter. A CEO doing the exercises next to their staff engineers shows the shift.
- Agentic coaching is the new agile coaching Adopting agentic engineering has the same shape as adopting agile twenty years ago: an organizational change, resistance among senior people, and the same three levers that worked the first time.
- Agentic adoption is harder than agile, because you can't fake it Agile rollouts could rename roles and keep the waterfall. Agentic engineering returns nothing on half-measures, because every gate sits upstream in architecture, context and the team.
- Most AI rollouts change the codebase and leave the team untouched In a Multitudes survey, codebase changes made up 85% of what teams changed for AI, and only 13% named a process change. In our experience, that gap is why most rollouts hit the same wall.
- Agency, not the tool, decides whether AI works for a team Skill on one axis, agency on the other: four quadrants with four very different outcomes. Give senior developers agency and the tool starts working. Strip it away and even the best reject it.
- AI makes teams faster and wears down their engineering instincts Agents speed up output while problem decomposition, debugging and code comprehension fade. The answer is to encode the team's engineering knowledge into a harness.
- Working well with coding agents takes months, not hours Experienced engineers resist agentic coding, and most people quit after a couple of hours. The value only shows once you have put in the time to learn the new skills.
- Three windows for adopting agentic coding are closing Teams that plan to adopt agentic coding in two or three years underestimate the learning curve, the talent market and the economics. Each of the three gives a reason to start the clock now.
- Five human skills that grow more valuable with AI My son asked why he should learn programming if AI will do it for him. The skills that matter most are becoming more valuable: critical thinking, empathy, language, value creation, judgment and taste.