A great developer - how to be one, how to find one?
summary
Argues that a great developer shows pride, helps and mentors juniors, listens to understand the problem, prioritizes expensive time, and consistently makes good judgments and reliable deliveries; recommends four developer practices: test your own code, understand before you start, keep code clean and simple, and mentor others. For hiring lists five concrete steps: anonymize CVs, standardize tests, get independent second opinions, ask open questions, and don't misrepresent the job. Warns AI could hollow out junior roles if hiring and training stop.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:26Early career perspective
- 2:39Evolving definitions
- 3:37Attributes of great developers
- 5:59Intermission
- 6:22Actionable tips for developers
- 7:29Hiring and closing thoughts
related talks
33mWhat it takes to become a great developer!
33mHow to be a great developer without being a great coder
39mHow To Be A Great Developer
33mHOW TO BE A GOOD DEVELOPER?
18mThe Art and Science of Thriving Developers: 7 Key Strategies
47mDeveloper under influence
36mHow to be a Better Junior Developer
35m10 Lessons for Growing Junior Developers