1 min lesson
Communication and review-readiness
Rebuild the main list in "Communication and review-readiness", then say what each item changes.
Step 1 of 3
On a sub-100-person team where you ship senior IC from week one, the code you write in the screen is a sample of the code you'd put up for review. They read it that way.
The difference between a strong and a weak finish is rarely the algorithm. It's whether you talked in tradeoffs, named edge cases before they had to ask and left the file in a state a teammate could merge.