Ego-less Programming: the Philosophy of Better Code
summary
Ego inflates design choices into unusable APIs and causes not invented here rewrites that waste months, sometimes leaving a bus factor of 1 that kills projects if one person leaves. Philosophy cues — stoic focus on what can be changed and Zen humility — combine with DevOps practices: enforced pre-commit hooks, linters and formatters, code reviews, pair programming, CI/CD, opinionated frameworks and BDD. These reduce cultural toxicity, shrink technical debt and cut waste so teams ship reliably.
AI-written summary · about
chapters (13)
- 0:00Introduction and welcome
- 1:51Defining ego in programming
- 4:32Dangers of ego in development
- 9:36Brief guide to philosophy
- 15:16Stoicism and ego control
- 17:05Glory to God alone concept
- 19:37Buddhism Zen and ego loss
- 21:24DevOps philosophy explained
- 25:22How ego disrupts DevOps
- 30:40Tools against ego issues
- 36:57Software tools for egoless code
- 42:46Tales of horror and conclusion
- 44:10Q&A session
related talks
25mEgoless Engineering
53mIntentional Code - Minimalism in a World of Dogmatic Design
45mEgo-Driven Development
50mIntentional Code - Minimalism in a World of Dogmatic Design
34mHow do our ideas about coding affect the software we create?
39mYou should stop writing code
42mTo Code is Human
05mEngineering Without Dogma: When to Ignore the Best Practices