Growing a Junior Dev into a Beautiful Coding Butterfly
summary
Summary of concrete takeaways: six specific growth activities are recommended — seek challenge, regular code review, pair programming, take ownership and lead projects, practice deliberately, and ask for help — based on surveys that show overlap and notable disagreement (pairing polarizes, code review ranks high). An actual case documents building an Ember add-on to avoid copy‑paste and it works, boosting confidence. Advice includes when to escalate a blocker, how to run pair sessions, and treating small solo projects as responsibility for end‑to‑end outcomes.
AI-written summary · about
chapters (4)
- 0:00Start
- 7:17they think needs to change for themselves before they start identifying as mid-level?
- 11:33What is the MOST beneficial activity a manager or supervisor of a junior
- 25:16How was that different from working on a project someone else is leading?
related talks
13mGrowing Developers: Helping Junior Developers Improve & Succeed
36mHow to be a Better Junior Developer
28mPair Programming as a Mechanism for Growth
30mEquipping your team to support junior developers
31mDEAR JUNIOR DEVELOPER ME
30mForging Your Path to Senior Developer
01h 06mTeaching New Tricks – How to enhance the skills of experienced developers
39mNew Dev, Old Codebase: A Series of Mentorship Stories