Democratizing Frameworks Through Developer Experience
summary
Claims that better DX lowers barriers and reduces bugs and frustrated engineers, then shows work: adds M3 models support to Ember inspector, prototypes a button to Output the store in the data pane and interviews developers to validate demand, and files small maintenance PRs like deadlinks fixes across Ember data, octane guides and Mirage. Concrete outcomes: a merged inspector feature, a forthcoming PR for the store button, and multiple README examples that make onboarding and debugging measurably faster for newcomers.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:50Sarahs background
- 1:32Who am I
- 2:19LinkedIn Reach Apprenticeship
- 2:58Ember Data
- 4:31What is Developer Experience
- 5:18Metrics are notoriously hard to measure
- 5:56Sarahs current project
- 7:00Why is DX important
- 7:52Misuse
- 8:13When to contribute
- 9:21Where to contribute
- 10:57Conclusion
related talks
47mTransforming Developer Experience: A Tale of Recovery & Innovation
24mMastering Ember from the Perspective of a N00b
25mCommunication and Convention
53mLet's talk about DX, Baby!
35mAn introduction to developer experience, and the role of a documentarian
29mDX is UX
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
29mDebugging Ember With Empathy