All the things I learnt as a junior developer (so you don't have to)
summary
Four concrete takeaways: watch for burnout and use a mental health day before it breaks you; demand a two-way interview that shows a growth plan and mentorship; create experience by building things—dashboards, volunteering, open‑source, or a React Native app—and count hackathons as real work; act sooner rather than later if assignments stagnate (after 18 months stuck in the wrong role someone leaves and later lands at Atlassian). Specifics: invest in QA, show concrete projects, track time spent, and verify promotability paths.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:24Why this talk
- 2:37Burnout
- 5:33Take a break
- 7:29It goes both ways
- 8:32What to look out for
- 10:41What to consider
- 11:47Make your own experience
- 16:45Do something not nothing
- 19:57Why did I get rejected
- 22:59Questions
related talks
45mCareer hacks for developers
42mAsk Them Anything: Career & Life Advice for Junior & Intermediate Developers
10mCommon pitfalls of junior developers
30mEquipping your team to support junior developers
32mHow to Be Well Onboarded as a Junior Developer Who Retrained
24mElevating Young Developers: Best practices for seasoned developers on onboardings
58mBackwards Compatible- Lessons from a Quarter Century in Software
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer