The Effective Developer - Work Smarter, Not Harder.
summary
Argues effectiveness beats raw efficiency and gives concrete practices: enforce team code with automatic formatting and meaningful names, run peer reviews using five social rules and the canary test with junior devs, carve weekly 1.5‑hour coding sessions and a book/video club, run quarterly 24-hour hackathons (yields ~0.7 hours/week) plus eight‑week innovation weeks (raising dedicated improvement time to ~7.7 hours/week), use a project poster and journey maps to validate problems, block daily 1–4pm deep work and rotate a single support person.
AI-written summary · about
chapters (14)
- 0:00The effective developer
- 3:08Reflecting on past habits
- 6:10Modern development landscape
- 8:04Writing team-focused code
- 14:05Effective code reviews
- 17:43Continuous learning strategies
- 25:29Mentoring and unlearning
- 29:04Experimentation in teams
- 32:42Fostering innovation
- 35:53Addressing technical debt
- 42:09Reducing meeting overhead
- 48:43Prioritizing deep work
- 53:29Understanding user problems
- 58:52Conclusion and takeaways
related talks
31mThe Effective Developer - Work Smarter, Not Harder
50mThe Effective Developer - Work Smarter, Not Harder
48mThe Effective Software Architect - Work Smarter, not Harder
01h 02m10x_productivity_for_developers_and_architects
33mMeasuring Developer Productivity: the good, the bad and the data
48mEnding Keynote: 7 Principles of Productive Software Developers
47mUnleashing Your Super-dev-powers
26mUpdate your team to be more extreme