Finding the Beauty in the Digital Brick
summary
Argues that software only creates value once users use it and gives concrete examples: a working embedded Linux peripheral that still runs code written in 2007, and a cautionary tale of a homegrown PHP framework that consumed its author in maintenance. Calls out cognitive pitfalls like Dunning Krueger and yak shaving, quantifies the cost as lost development and opportunity time, and recommends practical defaults — adopt mature open source, design open API contracts, and prefer cloud-agnostic architectures to shorten time-to-value.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:14Art and science of software
- 8:12Artist ego in software
- 12:51Ego pitfalls and biases
- 17:48Bike shedding and perfectionism
- 20:57Perfection versus pragmatism
- 23:26Build versus buy
- 31:26Time to value
- 34:13Future-proofing with openness
- 37:49Open source and APIs
- 43:24AI in software development
- 46:55Egoless programming
- 51:27Conclusion
related talks
43mA moment's reflection
40mBuild Better Software
44mLies we tell ourselves about developer infrastructure
34mHow do our ideas about coding affect the software we create?
39mYou should stop writing code
27mYellow Brick Code: Lessons from The Wizard of Oz on Enhancing DevEx
51mSoftware Archeology and The Code Of Doom
43mThe Dangers of Being a Web Developer