In this episode, Matt and Liam dust off a six-year-old debate about REST, conventions, and the art of building predictable APIs.
From 404 vs 403, to POSTs that aren’t quite posts, they ask:
Should your API tell the truth, or just be polite about it?
They discuss:
✔️ Why REST isn’t a standard, but a set of conventions
✔️ Whether idempotence is worth chasing
✔️ When it’s okay to break RESTful norms (and when it’s just lazy)
✔️ The surprising UX parallels between API design and toilet buttons 🚽
✔️ Why “Don’t Make Me Think” isn’t just for UI designers
Plus: BBQ fires, near-death corn, and the Dunning-Kruger effect of REST philosophy.
💡 Whether you’re team “404 means not found” or “it depends,” this one’s for you.
🍻 Tonight’s Drinks:
Matt: Laphroaig 10 Year Old (Islay, Scotland) Liam: Penfolds Bin 389 (origin unknown)
Any 👍 Likes, 📣 Shares, 🔔 Subscriptions, and ❤️ Love go a long way to helping us continue this podcast.
Cheers! 🍻