Can Wittgenstein's Philosophical Ideas Help Build Better Software?
summary
Argues younger Wittgenstein maps language to reality and that programming exemplifies that — you can define a spoon exactly in code — then flips to older Wittgenstein: meaning is use, so teams must build shared language. Gives concrete practices: swarming and pair programming, backlog refinement, planning‑poker feedback loops, empathy, and automation to encode rules so small teams can ship. Notes practical artifacts: a role‑playing + agile framework and a tax‑data pipeline headed toward BI/ML to detect aggressive tax planning, and cites biased AI hiring tools and 4.6 team members.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:25Overview
- 4:13Who was Wittgenstein
- 7:43Bend a Spoon
- 9:07Structure of Reality
- 10:22Picture of Reality
- 11:53Constraint
- 13:18The younger Wittgenstein
- 13:46The older Wittgenstein
- 16:54Meaning of words
- 18:22Meaning of words in software
- 20:46Thinking outside our language
- 21:27The Matrix
- 22:38Devops
- 25:33Communication
- 26:22Unlearning
- 28:32Common Meaning
- 30:19More Overhead
- 31:44Reducing Complexity
- 34:44Feedback
- 36:00Empathy
- 37:44Last in Practice
- 40:49Further Reading
related talks
38mSoftware Engineering: A philosophical activity
48mA Personal Philosophy of Excellent Engineering
44mSoftware Engineering - A philosophical activity
40mLanguage Games
53mSoftware Design: Beyond Boxes & Lines
35mCraft, Engineering, and the Essence of Programming
35mEngineering for Software - How to Amplify Creativity
27m'The Art of Software Development'