Effective beginner practices
Beginners get good with coding agents by practicing in a domain they can judge, keeping tasks and feedback loops small, and granting the agent more autonomy only once reviewing every small step turns into rubber-stamping.
Written by
-
Benedikt Stemmildt Founder & Co-CEO
Updated:
Getting Started 2
Judgment comes first, because a beginner who cannot tell right output from wrong learns from neither. A domain you already master lets you judge the output instead of trusting it blind (When AI writes almost all code (opens in a new tab)). Sandbox the environment before you widen the loop, so the extra autonomy is safe (Vom Coder zum Dirigenten (opens in a new tab)).
Proficiency grows with deliberate practice, not exposure. The people who get the most out of the tools treat a model like a musical instrument and keep playing after the first wrong note (deliberate intentional practice (opens in a new tab)). A daily habit works: an hour of real work with the best model available, not toy questions on a faster default (Something Big Is Happening (opens in a new tab)).
The tool makes it easy to stop thinking, so effective learners put the difficulty back. Letting the agent do all the thinking is how you learn least, and durable skill needs the productive struggle of effortful work (WEF – New Economy Skills: Unlocking the Human Advantage (opens in a new tab)). Practitioners remap the accept-suggestion hotkey or disable the agent’s file-write tool to keep critical thinking alive (building scalable apps with AI (opens in a new tab)). Reviewing is a different muscle from writing: lean only on evaluation and you slowly lose the capacity to create (AI’s impact on the state of the art in software engineering (opens in a new tab)).
Plan with the agent before it codes, describe tasks concretely and start new sessions often, because performance degrades as context grows. When you lose track of what the agent is doing, revert and approach the task again (The Pragmatic Engineer - Learnings from two years of using AI tools for software engineering (opens in a new tab)).
Start here
- Deliberate practice: How beginners build judgment with familiar domains, tight feedback loops, active recall, and deliberate friction.
Related
- The learning curve: why the first weeks feel slower before the habits pay off.
- Verification literacy: how to check output a model inferred rather than compiled.
- Practitioner practices: the sequences experienced practitioners settle into.
- Security of autonomous coding agents: why a sandbox matters before you grant more autonomy.
- Prompt Engineering: how to structure a request an agent can act on.
Resources
Articles
- AI’s impact on the state of the art in software engineering in 2026 (opens in a new tab) - Eventuallymaking industry synthesis warning that leaning only on reviewing AI output erodes the capacity to write code yourself.
- Learnings from two years of using AI tools for software engineering (opens in a new tab) - The Pragmatic Engineer newsletter article with workflow habits: plan first, keep tasks small, restart sessions often, revert when lost.
- Something Big Is Happening (opens in a new tab) - LinkedIn article urging a daily hour of real work with the best available model rather than toy questions on a faster default.
- When AI writes almost all code (opens in a new tab) - The Pragmatic Engineer newsletter article on working when agents write most code, including starting in a domain you can judge.
- deliberate intentional practice (opens in a new tab) - Blog post arguing that proficiency with models comes from deliberate practice, treating a model like a musical instrument rather than quitting early.
Papers and reports
- New Economy Skills: Unlocking the Human Advantage (opens in a new tab) - World Economic Forum report on cognitive offloading, arguing durable skill needs the productive struggle of effortful work.
Talks and videos
- Vom Coder zum Dirigent - Wie ich mich selbst ersetze (opens in a new tab) - German-language code.talks 2025 talk on widening an agent’s autonomy step by step, sandboxing the environment before granting more.
- WWC25 - Vibe coding sucks! Long life to vibe coding: Hardening Applications for Production (opens in a new tab) - WeAreDevelopers talk on hardening AI-built apps, including deliberate friction such as remapping the accept key to keep thinking.
In this section
- Deliberate practice
Deliberate practice builds judgment with coding agents: start in a domain you can check, keep tasks and feedback loops small, practice daily on real work, and put friction back where the tool makes thinking optional.