Building better developers
summary
Choose concrete actions not slogans: make an editor reflex by using the vim tutor or gamified vimadventures, practice tiny code katas and Project Euler problems daily, auto-run tests on save with inotify loops, and deploy a CI server but never tie developer bonuses to raw code coverage (it backfires). Study real examples like the Quake 3 inverse square root that runs about three times faster, learn when to measure what, and broaden into T-shaped skills so small, repeatable practices actually change how work gets done.
AI-written summary · about
chapters (11)
- 0:00BIG PHILOSOPHICAL QUESTIONS
- 0:42OUR SAD AVERAGE DEV
- 3:44YOUR EDITOR IS PART OF YOU
- 11:44DELIBERATE PRACTICE
- 18:08MASTER YOUR CRAFT
- 24:26MEASURE WHAT MATTERS
- 40:00NOT THE SHARPEST TOOL
- 45:00ADJUST YOUR ATTITUDE
- 47:12SPEAK OUT AND BE HEARD
- 54:13JOIN THE COMMUNITY
- 58:06ENJOY WHAT YOU DO
related talks
31mThe Effective Developer - Work Smarter, Not Harder
50mThe Effective Developer - Work Smarter, Not Harder
31mThings I Wish I Knew When I Started Playing 'Developer'
18mProgramming Workout
30mLessons Learned: A Developer's Perspective on Teaching & Learning
48mEnding Keynote: 7 Principles of Productive Software Developers
33mHow to be a great developer without being a great coder
38mFrequently Asked Questions