What Happens When You Don't Write the Code — Advice I Wish I'd Taken 10 Years Ago
summary
How to reduce lost coding time that causes burnout by using concrete practices: prepare agendas and record decisions for meetings, split work into small pull requests, model system boundaries with BPM, and allow uninterested attendees to leave. Examples of applied work include a green farm simulator, a Type 4 grammar checker, and integrations with Parcel and Redux; progress is measured by small wins such as weekly thank-you notes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:40Wasting developer time
- 6:16Developer to engineer
- 9:55Escaping regret
- 11:45Efficient meetings
- 15:41Avoid endless advice
- 17:54Big PRs need discussion
- 19:21Processes: friend or foe
- 21:08Task modeling
- 22:33Feature planning by value
- 24:17Measuring work success
- 25:22Conclusion
related talks
46mStaying Human While Coding
44mHow do you think when you're coding?
46mThe Zen of Programming. A personal journey towards writing beautiful code.
50mThe Effective Developer - Work Smarter, Not Harder
48mEnding Keynote: 7 Principles of Productive Software Developers
31mThe Effective Developer - Work Smarter, Not Harder
01h 03mThe Effective Developer - Work Smarter, Not Harder.
11mProgramming Like An Athlete