Working backwards

on YouTube ↗33m

" summary

Designs developer APIs by showing what was built and how it behaved: an open source npm UI hits 49 PRs in 24 hours and later attracts 3,000 contributions in 39 days but the team pauses for health, NX grows to over a thousand contributors, and a new logs SDK enforces unique error codes with doc links so CLI errors become actionable. Examples include progressive adoption patterns, GitHub/Discord-driven collaboration, measurable adoption spikes, migration pain from major breaking changes, and tooling choices that enabled — and strained — real people.

AI-written summary · about

" chapters (5)

1. 0:00Introduction
2. 6:03Designing APIs for humans
3. 15:58Human contributions over agents
4. 24:13Practical tips for building
5. 32:19Building community and closing

" related talks

• 06mFrom Zero to a Top Contributor: An Open Source Success StoryAndré Wanlin · BackstageCon Europe 2024
• 41mHow the npm CLI Team Manages (Almost) 100 Open Source ProjectsLuke Karrys · OpenJS World 2023
• 23mScaling Open Source CommunitiesFelix Krause · try! Swift Tokyo 2017
• 09mOpening RemarksJeff Cross · Nx Conf 2022
• 45mPaving the adoption path of your Design System for engineersJeremias Menichelli · React Alicante 2019
• 40mPanel Discussion: Build a Community, Not a FrameworkMatteo Collina, Christian Bromann, Robin Bender Ginn · OpenJS World 2023
• 46mBuilding Developer Community One Pull Request at a TimeAlex Bulankou · Voxxed Days Singapore 2018
• 27mThe Interconnected Developer Community and the Evolution of Software ProductivityRachel Potvin · DeveloperWeek 2020