Jan 3, 2015
2 mins read
As developers, it is our responsibility to properly take worst-case scenarios into account.
“Taking worst-case scenarios into account is something that web design does poorly, and usually not at all.”
Eric Meyer follows up on his “Inadvertent Algorithmic Cruelty” blog post. The picture of his daughter, who died last year, appeared on a party-like background of his Facebook auto-generated “Year in Review”.
I believe his statement can be extended beyond web design considerations. In my experience, all “worst-case scenarios” are poorly taken into account in our industry.
Think about security and the well-known fallacies:
Think of any “process” where users are left stranded because their situation was considered unlikely to happen and was discarded based on other fallacies:
Think about accessibility issues (motor or visual impairment). Often I can sense the manager’s conflicted feelings. See that fancy menu item that requires careful clicking and pointing? You know some people won’t be able to access it. We should do something about it. We know it’s the right thing to do. But it will at best require more time and money. So let’s not do it. Then you can look the manager in the eyes with a smirk that says: “I hope you can look at yourself in the mirror” :-)
This is when the worst-cases were not simply overlooked, then ignored when complaints started to flow in (closing your eyes won’t make this issue disappear).
Sounds a bit like Dilbert, I know.
Of course, even when you think long and hard, there is not always a perfect or even a satisfactory solution. Our job is to make sure we take the worst-case scenarios in consideration and treat them adequately, whatever that implies in our company context.