Frequently Asked Questions
summary
Mentoring over 100 developers yields concrete answers: live coding that turns “bad code” into working code, a shell alias audit showing 953 g uses, a 10‑year vimrc with about 60 leader commands, pragmatic TDD advice (change hard‑to‑test code or accept a small untested exception), explicit pairing trade‑offs (Dvorak, caps‑lock remap), and salary guidance including that discussing pay with coworkers is legally protected. Watch if concrete workflows, numbers, and runnable examples decide you.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:20sobriety test
- 1:00everyone has a job
- 1:35how can I improve
- 2:40do plenty of struggling
- 3:30admit you dont understand something
- 4:10the important
- 5:00admitting ignorance
- 5:45whats a good heuristic
- 7:20what does this command do
- 12:00pairing with other people
- 13:05integration tests vs unit tests
- 14:05looking for a job
- 15:00meeting new people
- 17:55underpaid
- 18:40taboo
- 20:25salary discussion
- 23:10how to learn tdd
- 27:30vim tutor
- 28:20vim vs emacs
- 29:40Favorite vim tricks
- 32:50Mentors
related talks
39mNew Dev, Old Codebase: A Series of Mentorship Stories
01h 00mBuilding better developers
48mA Series of Mentoring Stories
37mNew dev, old codebase: A series of mentorship stories
31mBuilding good developers
48mHow to Talk to Developers
30mLessons Learned: A Developer's Perspective on Teaching & Learning
34mDeep End Diving: Getting Up to Speed on New Codebases