The 7 Guiding Principles for Developer Engagement
summary
Seven practical rules for developer engagement plus four bootstrap tips and a worked example The claims include that top quartile developer teams deliver 60% higher shareholder returns and that developer influence causes 35% of opportunities lost Tools and tactics are concrete: publish rough ISOs and early code, run idea storms with upvotes, push device drivers into the mainline kernel as happened with the Sputnik Linux laptop project Results reported are a product line born from a skunkworks project and measurable engagement metrics guide iteration
AI-written summary · about
chapters (6)
- 0:00Introduction
- 5:20Guiding Principles
- 6:05Outbound
- 14:05Building Developer Trust
- 14:40Bootstrap
- 17:58Summary
related talks
41mPrinciples of developer experience
31mThe Effective Developer - Work Smarter, Not Harder
19mDevelopers are all the same
34mBuilding a Culture For Developer Productivity
17mMake Work Not Suck Improving the Developer Experience
17mEnhancing Developer Experience through InnerSource and Platform Engineering
39mDeveloper Experience: How to Conquer the Hearts of Developers
32mLessons Learned from 7 Years of Running Developer Platforms