✳flâneur — a map of the web's best reading
Hyrum's Law and API Design and Management | What does it mean?
blog.axway.com · 542 words · saved by 1 readers
This article discusses Hyrum's Law and what it means for API Design and Management. Hyrum's Law is named after Google software engineer Hyrum Wright.
The promise and challenges of loose coupling One of the main aspects of APIs is that they should provide loose coupling , meaning that providers and consumers of services have more independence and autonomy to evolve than in more tightly coupled approaches. The obvious advantage of this is that it requires less time-consuming coordination, and thus providers and consumers can evolve independently. However, when providers and consumers can evolve independently, there always is the risk of breaking changes . If an API changes, do existing API consumers have to adapt and change? Or can they keep
Explore this link on the map →related reading
- Hyrum's Lawhyrumslaw.com
- The Bezos API Mandate: Amazon's Manifesto For Externalization | Nordic APIs |nordicapis.com
- Everything I know about good API designseangoedecke.com
- APIs All the Way Down - Not Boring by Packy McCormicknotboring.co
- Laws of Tech: Commoditize Your Complement · Gwern.netgwern.net
- How will API’s evolve alongside AI? - Sara Dusaradu.substack.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- The unwritten laws of software engineeringnewsletter.manager.dev
- artima - Josh Bloch on Designartima.com
- Hick’s Law: Making the choice easier for users | IxDFinteraction-design.org
- notes/books/pragmatic-programmer.md at master · pkardas/notes · GitHubgithub.com