Value: Why we have it Backwards
summary
Argues that software as a knowledge medium is the real product, not feature lists, and reframes QA and development to ask have we reached the most faithful reproduction of knowledge?. Gives concrete practices: dogfooding, personas, putting procedures into scripts and build systems, and capturing docs with Fitness and Doxygen. Shows that team-built tools that scratch a personal itch outperform generic features and that “green” status can hide lack of learning, so plan for planned failures and rewrites rather than rigid estimates.
AI-written summary · about
chapters (7)
- 0:00Start
- 4:48EVOLUTION
- 21:25PROGRAMMING PRACTICES
- 22:40CHANGE! TESTING PRACTICES
- 24:38CHANGE! INTER - TEAM
- 28:19CHANGE! TRACK
- 45:23CREDITS
related talks
27m'The Art of Software Development'
51mA Defence of Technical Excellence
41mA Defence of Technical Excellence
45mTaking Back "Software Engineering"
30mWhy should I write software well?
50mTactics and strategies on software development: how to reach ...
54mANTIDOGMA
33mMeasuring Developer Productivity: the good, the bad and the data
