Keynote Session: The Survival Guide To Being A Junior Engineer
summary
A huge refactor involving multiple teams hits a crisis when three of five engineers leave and the project is 60% complete when departures force a single remaining engineer into an accidental Project Lead. The work finishes weeks late but ships; concrete takeaways include embracing ambiguity by mapping project value to technical choices, prioritizing documentation and meeting minutes, planning timelines with buffers for holidays and resignations, batching time to reduce context switching, and quantifying and scheduling repayment of technical debt.
AI-written summary · about
chapters (6)
- 0:00The Survival Guide to Being a Junior Engineer By Fatima Taj
- 4:12Embrace the Ambiguity
- 5:47Understand Your Project Inside and Out and Its Value to the Business
- 7:34Practice Clear, Effective, and Efficient Communication!
- 10:42That Project Planning Is Complex and
- 15:00Realize That Technical Debt Might Be a Necessary Evil
related talks
34mThe 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
43mThe Joys of Managing Engineering Teams
31mKeynote Panel: Getting Hired
22mJunior Engineers Are Features, Not Bugs
30mEquipping your team to support junior developers
49mWelcome to Management - Tips and Tricks for Junior Leaders