Stage 4 · Lesson 8 of 8
Owning your mistakes
At some point you will break something: a failed , a bad , a deleted file. Say so quickly and plainly: what you did, what you see and what you have tried. Early honesty turns a mistake into a normal event and lets others help before it grows.
Many teams then write a , a short report on how the system allowed the mistake, not on who made it. Take part openly and suggest a safeguard, such as a new check or test. Teams remember how you handled a mistake far longer than the mistake itself. It is good material for your too.
Common traphiding your part and hoping nobody notices, which damages trust far more than the original error.
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
- GuideFreeGoogle Engineering Practices
Google · Intermediate
Google's guides for change authors and reviewers: small changes, good descriptions and handling comments
- BookPaidThe Missing README: A Guide for the New Software Engineer
Chris Riccomini and Dmitriy Ryaboy (No Starch Press) · Beginner · $29.99 print, $23.99 ebook
The testing, code review, delivery and on-call chapters written for a new engineer