After all, most delays can directly be traced to the QA department. Wise business decision!

• A bug in the code controlling the Therac-25 radiation therapy machine was directly responsible for at least five patient deaths in the 1980s when it administered excessive quantities of beta radiation.
• Radiation therapy planning software RTP/2 created by Multidata Systems International could incorrectly double the dosage of radiation depending on how the technician entered data into the machine. At least eight patients died, while another 20 received overdoses likely to cause significant health problems (November 2000).
• A Medtronic heart device was found vulnerable to remote attacks (2008-03).

https://en.wikipedia.org/wiki/List_of_software_bugs#Tracking_years

Great attention to detail!

Protip: Add a minor inconvenience to every line, like a trailing space or slightly misaligned indentation. That way the next guy who opens the file will automatically correct it, taking the git blame.

I was afraid you’d say that. That’s stupid.

Do they give a reason for why that’s ‘necessary’?

(Also it should be const userToName = (user) => user.name;)

Thanks for doing what I was too lazy to do.

I refuse to enter any club that would accept me as a member.

even property/field access is extracted out to a function

Java, the most functional programming language there is.

Same story here. I didn’t pay attention and failed basic math. Suggestion: plumber.

Correct answer: Lay off everyone. The new project will be coded solely by AI. 💯 hired.

I guess it’s easier and safer to make a string replace for each function name beforehand than hoping the compression algorithm will figure that out.

Also, as SpaceCowboy points out, comments are completely useless for the final web page. There’s no need to even compress them.

https://www.loggly.com/blog/http-status-code-diagram/

Why not POST /to/the/api?withCorrectErrorCodes?

Thanks for sharing that. My device isn’t listed, but I’d be surprised if Corsair changed how their shit works that much between devices. I’ll give it a try (it supposedly even works on Linux <3)

inefficient frameworks

I’d like to object to that. Frameworks are often built by dedicated and paid developers, so they tend to be above average in terms of efficiency. But being frameworks, they have to facilitate lots of use cases, so they also tend to be bigger than what you would write if you had 6 months to roll your own. And 36 more months to kill all the worms that got out of the can, to mangle a proverb.

Nowadays libraries are built with tree-shaking in mind, so when it’s time to deploy the app only the code that’s actually used gets bundled.

God, I hate Corsair. Not only do you need to download their garbage software to fucking turn off the RGB on a headset, you have to have it running or the RGB will turn on again!

I never said that it was impossible for a farmer to learn things outside their immediate field. Just like computer programmers often have knowledge of hardware and the general technology stack.

My point, to make it explicit to a few of the illiterates who’ve replied to my comment so far, is that it is not necessary to teach a web developer how a goddamn CPU works. They can gain nothing from that knowledge because there are at least 3 levels of abstraction between JavaScript and assembly.

You don’t teach a farmer how an internal combustion engine works. Computers are tools to software engineers. What they need to know is how to operate them, not how to maintain them.

That’s the price of specialization. Don’t ask a software engineer to troubleshoot hardware. Don’t ask a backend dev to write a frontend. Don’t ask a proctologist to look at your cough.

You simply cannot be proficient at every sub-sub-specialty. That’s why we collaborate and hand the ‘my computer gets hot’ problems to the hardware people. The alternative would be only moderately useful generalist.