How being lazy became a contribution
summary
A >1000-line AsyncAPI spec requires repeated copy‑paste validation, so a nodemon-like watcher is built to auto-validate changes, using nodemon-like watcher behavior and the community asyncapi-parser to surface errors. The Studio fails to display parser error locations until the code is patched, a fix that lands as an open source contribution. The internal CLI is reimplemented with Ink for component-based UI, then the project later switches runtime to ugly for its benefits, and the watcher tooling proves effective.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:11About me
- 0:54Once upon a time...
- 1:51Problems...
- 2:16Automation is the solution
- 3:30I just fork it and take a look at the code
- 3:48My first contribution!
related talks
08mMy Journey from Contributor to a TSC Member at AsyncAPI- 08mMy Journey from Contributor to a TSC Member at AsyncAPI
30mOptimizing for Developer Delight
22mHow Contributing to AsyncAPI Tools Inspired a Career in OSS
33mWorking backwards
25mEverything You Wish To Know About The AsyncAPI Comunity
20mAutomating Governance for Asynchronous APIs
30mEmbracing uncertainties My Journey as an Open Source Contributor