The world needs full-stack craftsmen
summary
Argument: full‑stack craftsmen who own requirements, UI, backend, deployment and tests outperform narrow specialists. Evidence: a 33‑person team with nine years of practice built Estonia’s first modern internet banking (2012) and fixed a national e‑prescriptions outage by removing intermediary services, not buying hardware. Practices and tools cited: pair programming, unit tests and JUnit, continuous integration (Jenkins) with short weekly demos. Claims: such craftsmen can be ~5× more productive and earn ~50% more than narrowly specialized peers.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:07Company history and philosophy
- 3:17IT industry conflicts
- 8:47Narrow specialization effects
- 15:53Over-specialization risks
- 21:30Full-stack craftsman role
- 30:16Building from scratch
- 36:40Agile and XP
- 44:01Startup work
- 51:39Team processes and practices
- 57:00Q&A
related talks
45mBe Fullstack, because everyone should
49mExtreme Professionalism - Software Craftsmanship.
32m"The talents we have"
22mDo We Need Software Craftsmen?
05mFull Stack Isn't Enough - The Rise of the Full Product Developer
58mStepping Outside
06mInterview to Sven Peters
38mWebmasters, Full Stack Developers and Other Legendary Creatures