What it takes to become a great developer!
summary
Claim: maintainability matters more than architecture buzzwords, with 75% of maintenance work being adaptive or perfective and only 21% bug fixes. Recommendations include concrete tools: tests (write coverage before changing code), monitoring, structured JSON logs with request IDs and distributed trace IDs, metrics and dashboards, CI/CD, adapters to swap infrastructure, style guides and onboarding docs, and active mentoring to spread knowledge so changes stay manageable.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:39About me
- 2:37What is a great developer
- 2:51What makes good software
- 4:22What is maintenance
- 6:51What is change
- 7:22How can I support change
- 8:36Link Code
- 8:53Make it changeable
- 10:02Documentation
- 11:03Tests
- 11:46Monitoring
- 14:54Automating
- 15:28The big question
- 15:53Style
- 17:43Handbook
- 18:00Understanding
- 18:57Communication
- 19:44Learning
- 20:22Mentoring
- 21:34Conclusion
related talks
33mWhat it takes to become a great developer!
33mHow to be a great developer without being a great coder
50mThe Effective Developer - Work Smarter, Not Harder
39mHow To Be A Great Developer
10mA great developer - how to be one, how to find one?
01h 01mHabits of a Highly Effective Technical Manager
48mThe Effective Software Architect - Work Smarter, not Harder
33mHOW TO BE A GOOD DEVELOPER?