Lot of good, actionable learnings there. I liked this one in particular.
> [26] In a transparent codebase with quick review cycles, APIs will leak implementation details unless you gate-keep.
It's tempting to make quick fixes to APIs but please take it slow. Think through existing customers as well as how could new ones will use it.
Also, something I learned while building/maintaining public APIs was to always clearly document (along with examples) the context in which an API should (ideally) be used and how it combines with other APIs to enable common use cases.
> [26] In a transparent codebase with quick review cycles, APIs will leak implementation details unless you gate-keep.
It's tempting to make quick fixes to APIs but please take it slow. Think through existing customers as well as how could new ones will use it.
Also, something I learned while building/maintaining public APIs was to always clearly document (along with examples) the context in which an API should (ideally) be used and how it combines with other APIs to enable common use cases.