The 5 developers’ principles that helped me as a new father
summary
Five concrete dev rules applied to parenthood: follow SRP by splitting a user/location function into two; use the Boy Scout rule to rename vars and fix typos; apply KISS by breaking a giant invoice function into per-section functions with unit tests; practice YAGNI by removing a base repository and Prisma boilerplate; use Tell, Don’t Ask by moving close logic into the task object. Outcomes: pacifier strap instead of dozens of spares, a food spreadsheet, less mess and more sleep.
AI-written summary · about
chapters (7)
- 0:00Developer principles as new father
- 3:06Fight coupling keep code simple
- 4:13Single Responsibility Principle
- 7:25Boy Scout Rule readability
- 9:15Keep It Simple Stupid
- 11:05You Ain’t Gonna Need It
- 14:20Tell Don’t Ask conclusion
related talks
41mWhat raising 3 kids taught me about working with users
48mEnding Keynote: 7 Principles of Productive Software Developers
51mOne Rule to Rule Them All
50mThe Effective Developer - Work Smarter, Not Harder
42mThings I Wish I Knew When I Started Playing "Developer"
31mThings I Wish I Knew When I Started Playing 'Developer'
30mParenting + Programming
46mThe Zen of Programming. A personal journey towards writing beautiful code.