The Survival Guide To Being A Junior Engineer
summary
A software refactor across multiple teams stalls when three of five engineers leave and the work is 60% done, forcing an accidental project lead to replan, account for vacation buffers like Thanksgiving, and still deliver a delayed but successful rollout; concrete tips include estimating with buffers, escalating blockers early (one experiment is lost to an outage), writing documentation as you go, treating tech debt as an intentional backlog item, and protecting focused time—expect one uninterrupted 2-hour session a day at best.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:47Who am I
- 4:06Story Time
- 7:17Key Learnings
- 7:29Embrace Ambiguity
- 18:40Communication
- 23:14Contact Switching
- 25:25Reducing Contex Switching
- 28:23Tech Debt
- 33:02Recap
- 33:31Outro
related talks
19mKeynote Session: The Survival Guide To Being A Junior Engineer
58mHow to survive and thrive as an engineering leader
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
22mJunior Engineers Are Features, Not Bugs
10mCommon pitfalls of junior developers
24mManaging Out: Strategies for Leveling Up
58m10 tips to become an awesome Technical Lead
33mJunior Engineers Are Features, Not Bugs