Some thinking points for service design: Principles & Best practices of REST API Design.
So via r/programming today: Modern storage is plenty fast. It is the APIs that are bad. and Anti-Patterns When Building Container Images.
Today I watched: How To Design A Good API and Why it Matters. Good talk. Favourite quote:
Inheritance violates encapsulation
Oh, and I followed on with: A Brief, Opinionated History of the API wherein (t=28:14) Bloch says it’s an API if you can answer yes to both of these:
- Does it provide a set of operations defined by their inputs and outputs?
- Does it admit reimplementation without compromising its users?
Today I discovered: Documenting APIs: A guide for technical writers and engineers.
Some tools for API documentation: Say Goodbye to Manual Documentation with these 6 tools.
This via r/programming today: A collective list of free APIs for use in software and web development.
This via r/programming today: Recommended Pagination for APIs. Keyset pagination is an approach I’ve seen recommended a fair bit lately…
Today via Lobsters: Write code that is easy to delete, not easy to extend. I think I like programmingisterrible.com.
Today I stumbled upon Microsoft REST API Guidelines.
I also must confess to a strong bias against the fashion for
reusable code. To me, “re-editable code” is much, much better
than an untouchable black box or toolkit. I could go on and on
about this. If you’re totally convinced that reusable code is
wonderful, I probably won’t be able to sway you anyway, but
you’ll never convince me that reusable code isn’t mostly a
— Donald Knuth, Interview with Andrew Binstock