Language Selection

English French German Italian Portuguese Spanish

Software developers have stopped caring about reliability

Filed under
Development

Of all the principles of software engineering which has fallen by the wayside in the modern “move fast and break things” mentality of assholes modern software developers, reliability is perhaps the most neglected, along with its cousin, robustness. Almost all software that users encounter in $CURRENTYEAR is straight-up broken, and often badly.

Honestly, it’s pretty embarassing. Consider all of the stupid little things you’ve learned how to do in order to work around broken software. Often something as simple as refreshing the page or rebooting the program to knock some sense back into it — most users can handle that. There are much stupider problems, however, and they are everywhere. Every morning, I boot, then immediately hard-reboot, my workstation, because it seems to jigger my monitors into waking up properly to do their job. On many occasions, I have used the browser dev tools to inspect a broken web page to figure out how to make it do the thing I want to do,1 usually something complicated like submitting a form properly (a solved problem since 1993).

When the average person (i.e. a non-nerd) says they “don’t get computers”, I believe them. It’s not because they’re too lazy to learn, or because they’re backwards and outdated, or can’t keep with the times. It’s because computers are hard to understand. They are enegmatic and unreliable. I know that when my phone suddenly stops delivering SMS messages mid-conversation, it’s not because I’ve been abandoned by my friend, but because I need to toggle airplane mode to reboot the modem. I know that when I middle click a link and “javascript:;” opens in a new tab, an asshole a developer wants me to left click it instead. Most people don’t understand this! You and I, dear reader, have built up an incredible amount of institutional knowledge about how to deal with broken computers. We’ve effectively had to reverse engineer half the software we’ve encountered to figure out just where to prod it to make it do the thing you asked. If you don’t have this background, then computers are a nightmare.

Read more

More in Tux Machines

Type Titlesort icon Author Replies Last Post
Story 5 open source tools for taming text Roy Schestowitz 09/07/2015 - 12:04pm
Story 5 specialized Linux distributions for computer repair Rianne Schestowitz 26/02/2015 - 1:05am
Story 5 tips every open source project manager should consider Roy Schestowitz 24/03/2016 - 10:25am
Story 6 essential non-coding careers in open source Roy Schestowitz 01/03/2016 - 10:40am
Story 6 new things Fedora 21 brings to the open source cloud Roy Schestowitz 10/01/2015 - 10:02am
Story 6 tips for adopting open source Roy Schestowitz 24/11/2014 - 10:02pm
Story 7 local governments announced to build with Code for America Roy Schestowitz 25/09/2014 - 4:11pm
Story 8 ways to contribute to open source without writing code Roy Schestowitz 01/12/2014 - 10:16pm
Story 9 reasons to use KDE Roy Schestowitz 14/04/2015 - 2:31pm
Story A beautiful, super-thin laptop that makes Fedora shine Roy Schestowitz 14/08/2015 - 11:33am