What it takes to become a great developer!
summary
Claims that greatness comes from specific skills not languages and that maintainability drives value, backed by a cited split: 75% adaptive/perfective vs 21% corrective. Recommends concrete practices: clean code, automated tests and CI pipelines, monitoring with trace IDs, metrics for live business insight, automation of deployments, and lightweight docs (API, setup, architecture). Advocates organizational tools that work: company style guides (example: Stargate), internal handbooks, buddy programs and active mentorship to spread context and reduce future maintenance costs.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:36About Christian
- 2:15What is a good developer
- 3:10What is good software
- 4:16What makes software good
- 4:44Maintainability
- 6:52Change
- 7:40Clean Code
- 10:01Changeable
- 10:53Documentation
- 12:05Test
- 12:21Monitoring
- 14:17Automation
- 14:48Good software
- 15:33What makes a great developer
- 18:01Internal Handbook
- 18:27Social Skills
- 20:23Communication
- 21:30Learning
- 24:11Summary
related talks
23mWhat it takes to become a great developer!
10mA great developer - how to be one, how to find one?
39mHow To Be A Great Developer
33mHow to be a great developer without being a great coder
49mExtreme Professionalism - Software Craftsmanship.
18mThe Art and Science of Thriving Developers: 7 Key Strategies
50mThe Effective Developer - Work Smarter, Not Harder
31mThe Effective Developer - Work Smarter, Not Harder