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.

Thread beginning with comment 662798
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Artificial Jobs
by kwan_e on Tue 25th Sep 2018 13:19 UTC in reply to "RE: Artificial Jobs"
kwan_e
Member since:
2007-02-18

Even many people with a bachelor's degree in computer science will not understand this immediately, and quite a few won't understand how it works even after you explain what it does (it swaps the contents of 'a' and 'b' in place without using temporary storage). This isn't something that's artificially complex, it's a real technique that's used in real world embedded programming to reduce the memory usage of the code.


Not only that, but some idiots use Javascript linters that warns against any uses of bit-twiddling because it scares them.

http://docs.codeanywhere.com/preferences/analysis.html

Reply Parent Score: 0

RE[3]: Artificial Jobs
by ahferroin7 on Tue 25th Sep 2018 14:04 in reply to "RE[2]: Artificial Jobs"
ahferroin7 Member since:
2015-10-30

I can kind of get that though for some people.

Doing bitwise operations when you don't understand them is generally a bad idea, and that goes double for dynamically typed languages like Javascript because you might end up accidentally mixing types, which can lead to weird results.

I mean, I actively avoid doing bitwise stuff in my own code unless I need it for efficiency or protocol reasons, but part of that is also that I mostly use Python, and therefore have to mask everything when doing it because integers are variable width.

Reply Parent Score: 3

RE[4]: Artificial Jobs
by Megol on Tue 25th Sep 2018 20:04 in reply to "RE[3]: Artificial Jobs"
Megol Member since:
2011-04-11

I can kind of get that though for some people.

Doing bitwise operations when you don't understand them is generally a bad idea, and that goes double for dynamically typed languages like Javascript because you might end up accidentally mixing types, which can lead to weird results.

Types... In Javascript?
Bitwise operations are done on numbers. Don't know what type you want to avoid mixing with numbers given that the language have like string, number, bool, ???.

Reply Parent Score: 3