How To Be A Great Developer
summary
Claim: tech skills are really overrated and soft skills matter more for productivity and team health. Lists five concrete practices: five principles: empathy humility always be learning avoid tribalism better your community. Gives examples: chosen Java to extend neo4j because of tooling and community, warns about AngularJS 1→2 instability, remote work forces disciplined documentation and communication, recommends weekly time for learning and favors loyalty to people over brands.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:38Tech skills are overrated
- 1:46Five major principles
- 2:31Empathy
- 3:43Dont Assume
- 4:42Two Groups
- 13:03Humility
- 17:40Learning
- 20:10Be Liberal
- 23:07Technology Choices
- 29:11Avoiding Tribalism
- 29:35Building Communities
- 29:58Technology and Techniques
- 32:09Absolute Statements
- 33:21Reasonable Arguments
- 33:51Loyalty
- 35:30Sharing
- 36:28Im a supervisor
- 36:51Values
related talks
33mWhat it takes to become a great developer!
56mSoft Skills for the Developer
10mA great developer - how to be one, how to find one?
33mHow to be a great developer without being a great coder
18mThe Art and Science of Thriving Developers: 7 Key Strategies
27mEvergreen skills for software developers
41mNobody Likes Working With You
42mKeynote: Five Skills to Force Multiply Your Technical Talent