Personal Developer Productivity Tips It's the small things
summary
Advocates turning as many workflows as possible into declarative repos — docs, diagrams (use mermaid), branch protection via GitHub Actions — so configs are visible, reviewable and AI-consumable; enforce helpful errors that print current vs expected state (example: Gradle failing because JDK 17 vs required JDK 21), add version checks for Bash, and prefer better assertions or Kotlin’s power assert. Use screenshots annotated with Flameshot, keep a searchable clipboard like Mackie, map shortcuts in macOS (assign Chrome’s exact “Search tabs…” menu item), and aim for zero notification popups.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:04Everything as code mindset
- 7:01Screenshots for communication
- 8:48Clipboard history boost
- 10:37Better error messages
- 14:10Test failure messages
- 16:58PR suggestion syntax
- 18:21Search everywhere workflow
- 22:18Key repeat speed
- 24:44Asking for help
- 31:07Chat interactions
- 32:31Pair programming tools
- 33:55Productivity insights
- 35:45Open communication
- 36:05Notification strategy
related talks
48mEnding Keynote: 7 Principles of Productive Software Developers
45mSeven Principles That Will Boost Your Developer Productivity
48mPrinciples Of Effective Developers.
49mFrom Busy To Effective Developer
48mThe Effective Software Architect - Work Smarter, not Harder
50mThe Effective Developer - Work Smarter, Not Harder
41mHow to Product Being a Productive Product Engineer
41mHabits of an effective programmer