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

GNOME Development Outline and Google Summer of Code (GSoC) 2022

  • #45 Timeout! · This Week in GNOME

    Update on what happened across the GNOME project in the week from May 20 to May 27.

  • Selected for GSoC'22

    I'm pleased to share that I'm accepted for Google Summer of Code (GSoC) 2022 under GNOME Foundation umbrella on the Pitivi project. This summer I will be updating the project from GTK3 to the latest GTK4 toolkit. To anyone that wants to be a part of GSoC, I have only one piece of advice, just go for it. Don't think if you can do it or not, don't assume failure before attempting, and don't overthink. I always felt that it is for the best of the best, and I won't be able to clear it, all the big organizations on the GSoC page overwhelmed me, but instead of making it a dream, I made it a life goal. And well, now I'm enjoying it.

Top 10 GNOME Themes for Your Ubuntu Desktop

A list of nice and clean GNOME themes with screenshots for your Ubuntu desktop in 2022 which you can download and install. Read more

lavapipe Vulkan 1.2 conformant

The software Vulkan renderer in Mesa, lavapipe, achieved official Vulkan 1.2 conformance. The non obvious entry in the table is here. Thanks to all the Mesa team who helped achieve this, Shout outs to Mike of Zink fame who drove a bunch of pieces over the line, Roland who helped review some of the funkier changes. Read more

3100 Games On The Steam Deck with Strider and Samorost 2 as Verified

While the additions are progressing, it’s been a little slower to reach the new milestone for the Steam Deck. There are now more than 3100 games validated (3120 games to be precise at the time of writing) on the Steam Deck – in two categories as usual... Read more