Kommandos vs Scouts – different style of development
summary
Argues that the Scout rule (always leave code cleaner) fits critical-path, product-level systems that require tests, docs, CI/CD, backups and careful refactoring, while the Commandos rule (get in get out) fits quick experiments, one-off scripts and short support tasks where writing full tests or docs wastes time; gives concrete thresholds — one small rename can touch ~100 files, consultants often hand off after 3–6 months — and insists security or critical bugs get fixed immediately regardless of style.
AI-written summary · about
chapters (5)
- 0:00Introduction and motivation
- 3:26Scout Rule explained
- 10:47Commandos Rule explained
- 15:06When to use each approach
- 18:54Final advice and Q&A
related talks
51mOne Rule to Rule Them All
48mA Teacher, an Economist and a Developer Walk Into a Bar
18mHow To Review Someone's Code While Not Being A Jerk!
48mBattlefield Agility: Think Beyond Scrum
49mWhy do you have to make it so complicated?
23mDrama-Free Code Review!
01h 09mThe Well-Balanced Programmer
01h 09mPlenary: Coping With Other People's C++ Code