Do You Know Da Wae
summary
Argues that team and culture beat lone “10x” coders, backed by specific practices: Tuckman’s forming–storming–norming–performing, 80% advanced beginners in the industry, and two-week iterations as a common feedback cadence. Names concrete failure modes — XA two‑phase commits fail at scale, Java XML needs escaping (bug found in review), leap second (June 30, 2012) crashed services — and says awareness, shared mental models and readable code are the real levers.
AI-written summary · about
chapters (15)
- 0:00Introduction and meta talk
- 5:21DevOps and the wall of confusion
- 11:24The importance of team and culture
- 15:40Teamwork and the 10x programmer myth
- 19:41Novice to expert skill levels
- 25:01Coupling and abstraction rules
- 31:00Truthiness and changing rules
- 37:23Iterative development and feedback loops
- 40:14Chaos versus bureaucracy spectrum
- 42:40Left brain right brain problem solving
- 45:50Readability and notation in code
- 49:41Java rules and pitfalls
- 52:52Leadership and mental models
- 55:42Design payoff and context switching
- 57:07Trust culture and vulnerability
related talks
49mExtreme Professionalism - Software Craftsmanship.
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
52mThe Developer Rhapsody
18mAgile leadership and technical mastery, a harmonious alliance
22mDo We Need Software Craftsmen?
44mUnderstanding Teams Through Systems Thinking and Stories
48mThe Effective Software Architect - Work Smarter, not Harder
25mEgoless Engineering