The Effective Developer - Work Smarter, Not Harder
summary
Advocates concrete habits: enforce formatting as a team with linters, run disciplined code review rules (criticize ideas not people, don’t spoon‑feed), and validate simplicity with a “canary” junior reader. Carve time to experiment—quarterly 24‑hour hackathons or company innovation weeks (MongoDB-style 40‑hour sprints twice a year) produce a few roadmap features, weed out bad ideas, and surface fixes. Send one developer to support yearly, use small experiments, and measure outcome (user impact) not just output.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:33Fixing bugs immediately
- 10:04The machine
- 13:34Simplicity over Cleverness
- 15:51code reviews
- 20:28Do you think software development is changing ?
- 20:57Podcasts Audiobooks
- 29:53Tools training
- 30:59Innovation
- 39:29What's the problem?
- 41:10As a user I want a new statistic button
related talks
31mThe Effective Developer - Work Smarter, Not Harder
01h 03mThe Effective Developer - Work Smarter, Not Harder.
48mThe Effective Software Architect - Work Smarter, not Harder
48mEnding Keynote: 7 Principles of Productive Software Developers
26mUpdate your team to be more extreme
01h 00mBuilding better developers
33mWhat it takes to become a great developer!
30mLessons Learned: A Developer's Perspective on Teaching & Learning