Linked by Thom Holwerda on Mon 24th Sep 2018 23:02 UTC
Features, Office

I've been programming for 15 years now. Recently our industry's lack of care for efficiency, simplicity, and excellence started really getting to me, to the point of me getting depressed by my own career and the IT in general.

Modern cars work, let's say for the sake of argument, at 98% of what's physically possible with the current engine design. Modern buildings use just enough material to fulfill their function and stay safe under the given conditions. All planes converged to the optimal size/form/load and basically look the same.

Only in software, it's fine if a program runs at 1% or even 0.01% of the possible performance. Everybody just seems to be ok with it. People are often even proud about how much inefficient it is, as in "why should we worry, computers are fast enough".

A bit ranty here and there, but this entire "old man yells at cloud" article is very much music to my ears. Software is bad. We expect software to be bad. We accept that software is bad. We make excuses why software is bad. We tell people it's okay that software is bad. We say it is inevitable that software is bad.

If any other industry were as lax about quality and performance as the software industry, we'd be up in arms.

Permalink for comment 662782
To read all comments associated with this story, please click here.
Sounds good in theory, in theory.
by kwan_e on Tue 25th Sep 2018 11:21 UTC
Member since:

Until programmers start growing up and stop arguing about
- emacs vs vi
- tabs vs spaces
- brace on the same line vs brace on new line
- camelCase vs snake_case vs PascalCase

and stop creating new languages just so they can have
- a gratuitous syntax for print printf println writeln
- a gratuitous syntax for declaring variables like let var decl
- a one size fits all visual-feel* that fits only the limited experience of one programmer

just because learning their first was hard, we can never get anywhere.

It's amazing how we're still reinventing language features and development methodologies of the 60s (and no, waterfall development was never anything but a strawman for agilists and rebel scrum).

* Can hardly call it syntax, semantics, style or paradigm, since a lot of programming language developments are about solving pet peeves rather than real problems.

Edited 2018-09-25 11:27 UTC

Reply Score: 6