How to be a great developer without being a great coder
summary
Claims that you can be a great developer without being a great coder by using concrete strategies: tolerate slow technical progress, use an apprenticeship or extended bootcamp time to learn (bootcamp sections repeat), and prioritize measurable habits like write documentation, ask questions early and often. Specific tools and practices include katas and cohens, cheat sheets, tutorials, pair/mob programming, mentoring, and hosting meetups. Track outcomes by the number of mentoring sessions given, docs added, or bugs resolved rather than raw algorithm speed. Preserve sanity and trade time costs for exposure and visible contributions.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:43A little background
- 11:55Break down problems
- 28:16Double dip preferred learning styles
- 29:34Non-technical developer attributes
related talks
33mWhat it takes to become a great developer!
10mA great developer - how to be one, how to find one?
31mThe Effective Developer - Work Smarter, Not Harder
30mLessons Learned: A Developer's Perspective on Teaching & Learning
33mHow to Enhance the Skills of Experienced Developers
39mHow To Be A Great Developer
01h 00mBuilding better developers
15mThe Power of Persistence in Your Development Career