Keynote: How to Win Friends and Reduce Tech Debt with Developer Experience
summary
Camunda runs a developer experience team of three under devrel and the CTO focusing on docs, contributor flows, community hub/forums and product-adjacent tools like SDKs and API wrappers. Engineers still write core docs while there is one technical writer for coordination. Volunteer-supported pieces regularly rot — example: a React Native API wrapper left unupdated for a year — creating surprise tech debt and lost adopters. Investing staff time to maintain SDKs, CI upgrades and contributor touchpoints prevents that debt and gains advocates.
AI-written summary · about
chapters (5)
- 0:00Intro
- 0:43Introducing Amara
- 2:39What is Developer Experience
- 10:37Developer Experience Considerations
- 17:08Conclusion
related talks
39mDeveloper Experience: How to Conquer the Hearts of Developers
17mMake Work Not Suck Improving the Developer Experience
15mKeynote: Creating a Holistic Developer Experience
17mHow to deal with technical debt in fast-paced environment
07mDeveloper Experience can drive business growth
48mDeveloper Joy – How Great Teams Get s%*t Done
12mKeynote: DX Is the New UX: How Technical Friction Impacts Business Value
26mImportance of supporting designer & developer creativity