Things I Wish I Knew When I Started Playing "Developer"
summary
Concrete takeaways: prioritize unit tests as a quicksave regularly habit so changes feel reversible, make code reviews a learning shortcut not a shove-it-off, treat empathy as a real tool—empathy is a wall hack—for users and colleagues, learn and name design patterns so you spot and apply the right one, experiment in other languages to see different solutions, practice rubber‑ducking and learn to say no, and remember soft skills matter—put some points into charisma for clearer, less combative communication.
AI-written summary · about
chapters (7)
- 0:00Start
- 22:14ADVERT BREAK
- 22:59TIP LEARN THE MECHANICS
- 25:26LARACASTS:// DESIGN PATTERNS
- 26:16BEST PRACTICES
- 32:48EMPATHY
- 35:03CODE REVIEWS
related talks
31mThings I Wish I Knew When I Started Playing 'Developer'
57mHard truths and soft skills: 10 pieces of advice for novice game devs
26mAll the things I learnt as a junior developer (so you don't have to)
01h 00mBuilding better developers
31mThe Effective Developer - Work Smarter, Not Harder
50mThe Effective Developer - Work Smarter, Not Harder
39mHow To Be A Great Developer
46m5 Things I Wish Someone Had Told Me About Programming Before I Started