Opening Keynote: Code Blindness
summary
Argues that organizations suffer from code blindness: layers of management ignore the actual codebase, rely on staffing metrics, or gamify numbers like test coverage. Shows stages from total ignorance to metric gaming to qualitative diagrams and lifecycle management, warns about runaway technical debt and recommends monitoring repo signals (mentions using flog and metrics foo for complexity), making conscious kills of low-value features, and allocating people by code knowledge so rewrites or replacements become practical decisions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:32Agile Software Development
- 9:32Ignorance
- 10:46Metrics
- 13:45qualitatively assessing
- 16:13Lifecycle management
- 17:59Integration
- 21:41Technical Debt
- 27:28Three Ideas
- 29:29Questions Comments
