Nitpicking terminology - are we using the right terms
summary
Argues that common buzzwords cause real mistakes and gives concrete examples: companies copy microservices in a five-person team and suffer needless complexity, one employer runs one-week sprints with no retrospectives and wastes planning time, outsourced teams force businesses to adopt Agile by fiat, and a VAT change breaks sites because someone hard-coded 22% hardcoded VAT. Distinguishes conscious technical debt from unnoticed digital rot, recommends peer code reviews, matching process (Kanban vs Scrum) to workflow, and treating teams as interdependent units.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:57Job ad
- 1:35Ninja developer
- 2:08Devops engineer
- 2:35Agile developer ??
- 2:47Nitpicking terminology are we using right terms?
- 4:27ubiquitous language
- 12:14Kanban
- 13:37Scrum
- 17:20Project manager
- 19:37Team
- 25:30Lead vs manager
- 27:49Title acceleration
- 31:43It takes 10.000 hours to master a skill
- 35:06Code reviews
- 36:02Code-Peer reviews
- 42:59Robert C Martin The Single Responsibility Principle
- 43:10DRY principle
- 50:34Architecture: software vs buildings
- 53:14Technical debt
- 54:56Digital rot
- 57:44We need to fix our terminology!!
related talks
30mHow you write matters in open source
21mAvoiding Anti-patterns in Technical Communication
38mAgile, Lean & Rugged - The Paper Edition
44mUnlearning how to write
39mWe're Agile, we don't do documentation
17mThe Technology Radar: A snapshot of Thoughtworks culture
55mThe Emperor Has No Docs
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations