Stage 6 · Lesson 5 of 7
Owning what an AI assistant writes
You are responsible for every line you submit, whoever or whatever wrote it. Use an to explain unfamiliar code, suggest approaches or draft tests. is then your job.
Read and understand each line. Check it matches the team's patterns. Run it and test it yourself.
Take extra care with security, error handling, dependencies (outside libraries the code relies on) and anything that touches data. Reviewers quickly notice when an author cannot explain their own change. In your first year the goal is to learn, so ask the assistant to explain and quiz you, not only to write code.
Common trapsubmitting code you do not understand because it passed tests that the same assistant also wrote.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- BookFreeSoftware Engineering at Google
Titus Winters, Tom Manshreck and Hyrum Wright · Intermediate
Free online: the chapters on knowledge sharing and testing show how strong teams learn and work
- BookPaidThe Pragmatic Programmer
Hunt and Thomas · Intermediate · About $45
Habits for learning, debugging and owning your work that last a whole career
Practise
Keep handy
Also worth your time
Why learning the systems under your daily work pays off faster than chasing new tools