I'm dealing with two instances of developer laziness (or stupidity).
The proximate cause of my annoyance this morning comes from les espèces d'idiots at Eurostar who included local references to images in a confirmation email template. In non-technical terms, they put the images they want displayed on an email behind their own firewall, so they only show up when you look at the email behind their own firewall. So, some idiot developer, tasked with creating a confirmation email, put images on it that worked for him (because he was inside the firewall) but didn't have the mental faculties to predict that no one else would see them. Somehow this got past Eurostar's QA as well—presumably because they, too, are behind the firewall.
This set up a flaw in Microsoft Outlook that will render the program mostly unusable until I get rid of the email using my phone. Because Outlook is too stupid to realize that, if it can't download an image from a particular local path because the path is not mappable, then it should still try all the other images on that path one at a time, blocking the UI thread as it goes. This means, for each image on the Eurostar email, I see something like this:
See how the URL doesn't begin with "http://" but instead begins with a double backslash ("\\")? Yeah, that's a local path to some server at the company who designed the email. Great work, guys. And great work, Outlook, for forcing users to wait for all the images to download before returning control of the UI. Because why wouldn't we want to stop everything in order to see the Eurostar corporate logo?