This week on the show, Adam and I talk about the "unhappy paths" in software design. An unhappy path - also known as a "sad path" - is anything that can go wrong during the consumption of a product. Some unhappy paths are nothing more than unanticipated edge-cases in the code while other unhappy paths are caused by poorly designed user interfaces (UI) that lack necessary constraints and affordances. But of course, it doesn't much matter why something is breaking, if our customers are unhappy, it's our job to fix it!
All that and more on this week's show:
... featuring these beautiful, beautiful people:
- Adam Tuttle → Website, Twitter, LinkedIn
- Carol Hamilton → Twitter, LinkedIn
- Tim Cunningham → Twitter, LinkedIn
- Ben Nadel (that's me) → Website, Twitter, LinkedIn
With audio editing and engineering by ZCross Media.
For the full show notes and links, visit the episode page. And, be sure to follow the show and come chat with us on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.
In this episode, one of the things that Adam and I discuss is the use of a GUID (Globally Unique ID) to help prevent accidental, double form-submissions. After the recording, I kept thinking about this approach and I wondered if I could just create a separate database table specifically for one-time use form tokens:
I like this approach because it feels like it has a clean separation of concerns without muddying-up the domain model.