Embrace Inconsistency to Cultivate Clarity

4min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

When faced with uncertainty or incomplete information, it is crucial to push forward, even if it means using imperfect names or solutions temporarily. This approach allows for progress despite initial confusion. It is essential to revisit and refine these choices later when more knowledge is gained. Effective library API design hinges on guessability and consistency, ensuring that elements work as intuitively expected by users. This predictability fosters a seamless development experience, as seen with systems like jQuery and certain frameworks that provide clear naming conventions. Striving for elegance and clarity in API design enhances usability, making the process more efficient and enjoyable.

Jerod is back with another “It Depends” episode! This time he’s joined by Kris Brandow from Go Time and they’re talking all things API design. What makes a good API? Is GraphQL a solid choice? Why do we do REST wrong? And WTF does HATEOAS mean, anyway?

Leave us a comment

Changelog++ members save 10 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

Neon – The fully managed serverless Postgres with a generous free tier. We separate storage and compute to offer autoscaling, branching, and bottomless storage.
Sentry – Get $100 towards your error monitoring with Sentry! Use the code changelog.
Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com
Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.