Finally had enough of things failing because devs don't check their return values, wrote two blog posts about it:
> design the user experience to include error messages in a helpful manner
> This covers the synchronous errors, but now we have a background job that is about to make a network request. As the comic says, “oh no!”
@mikeburns I love this. Rust makes this a first-class feature too!
@mikeburns This is a really good blog post, thank you. I appreciated the discussion of the philosophy behind where to handle different kinds of errors, and the post was approachable (as someone who doesn’t work in Rails day-to-day).
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!