Leveling up through Code Reviews
summary
Five months of a selfmade schedule — four hours weekdays and eight hours weekends — lands a first dev job at Geocent and then seven months on the job reveals a faster route to skill growth: doing and receiving code reviews. Specific gains include catching formatting errors with ESLint and Prettier, replacing verbose loops with built in JS methods, resolving React binding debates between constructor bind arrow functions and bind in render, and avoiding bugs with propTypes and setState callbacks. Open source PRs and small review study groups provide the practice.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:45Meet Elisheba
- 1:17Elishebas story
- 2:00Technical Support Analyst
- 2:14Production Support Analyst
- 2:55First Job
- 3:10Making a Schedule
- 4:18Motivation
- 4:43Getting my first job
- 5:01Our company doesnt follow this trajectory
- 5:46What I did to get the job
- 6:32What about code reviews
- 6:50What are code reviews
- 7:09The steps
- 7:38Some companies dont do code reviews
- 8:22What can you learn from code reviews
- 9:10First Code Review
- 10:08Second Code Review
- 12:25Flowchart
- 12:56Arrow Functions
- 13:55Update State
- 14:41callback function
- 15:05vco review
- 15:59prop types overview
- 16:58dont take it personally
- 17:44its all to make you better
- 18:55be prepared
- 19:32code reviews
- 19:55opensource projects
- 20:50recap
- 21:11outro
related talks
01h 05mGetting Good (or Better) at Code Reviews
46mLevel Up Code Review: How to Get the Most Out of It
17mHow I Got 1600 Stars on GitHub in 2 months of Open Source Work
01h 01mDoes Your Codebase Spark Joy?
10mLevel up your code reviews
32mFrom Zero to Hero
53mCode Review Beyond Code Style
31mFive Habits I Learned to Climb the Career Ladder