From Busy To Effective Developer
summary
Argues that prioritizing urgent vs important (Eisenhower) decisions prevents firefighting and that small automation wins matter: use TeamCity pre-tested commit to avoid local test waste, write Groovy scripts or simple shell hooks to automate repetitive file and photo tasks, and record Selenium flows for repeatable payment checks. Recommends mastering IDE keyboard shortcuts, running RescueTime to measure distractions, rethinking Pomodoro as a distraction detector, and learning touch typing (example claim: 50→80 wpm yields large time savings).
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:06Busy vs effective developer
- 4:59Starting the workday right
- 8:52Prioritizing tasks
- 12:47Mastering dev tools
- 18:54Automating with scripts
- 20:45Minimizing distractions
- 26:04Tracking time with RescueTime
- 27:07Learning smarter
- 28:53Breaking down tasks
- 30:21Reducing email overload
- 33:52Touch typing importance
- 36:44Choosing tech for speed
- 37:46Instant messaging tips
- 40:34Getting Things Done methodology explained
- 43:4433 folders for tasks
- 45:35Efficient meetings
- 47:22Balancing skills
- 48:47Q&A
related talks
53mOn Being an Effective Developer
58mOptimizing the Programmer: Get More Done Faster
31mThe Effective Developer - Work Smarter, Not Harder
48mEnding Keynote: 7 Principles of Productive Software Developers
35mHabits of Efficient Developers
58mTechnical Practices that Take Time but Save Time
45mSeven Principles That Will Boost Your Developer Productivity
01h 03mThe Effective Developer - Work Smarter, Not Harder.