Create Atomic Habits to Become a Better Developer
summary
Shows how the Four Laws of Behavior Change map to concrete developer routines and the precise interventions used: implementation intentions (commute → podcasts), habit stacking (dog walk → code kata), the two-minute rule, temptation bundling (learning then coffee), habit trackers and public sharing on Slack, plus Chrome/Android blocking extensions and a habit contract commitment device. Reports measurable outcomes: better focus, a promotion, more Scala knowledge, and repeatable gains in flow and task delivery.
AI-written summary · about
chapters (12)
- 0:00Introduction and setup
- 1:50British cycling success story
- 4:00From goals to systems
- 7:50Habit formation explained
- 10:20Four rules for good habits
- 13:12Making habits attractive
- 14:36Making habits easy
- 16:47Making habits satisfying
- 18:13Breaking bad habits
- 23:08Summary of habit rules
- 25:57Key takeaways and motivation
- 27:21Q&A session
related talks
58mAgile Adoption: Building Better Habits
50mThe Effective Developer - Work Smarter, Not Harder
39mRefactor Yourself!
10mExplains 5 Steps to Get Better at Coding
31mThe Effective Developer - Work Smarter, Not Harder
41mHabits of an effective programmer
15mLearning Tips Every Developer Should Know
48mEnding Keynote: 7 Principles of Productive Software Developers