It is on the sense that Windows admins are the ones that like to buy this kind of shit and use it. It’s not on the sense that Windows was broken somehow.

Well, “don’t have self-upgrading shit on your production environment” also applies.

As in “if you brought something like this, there’s a problem with you”.

I’m just not sure what the middle guy would be saying

“I hate inheritance! I hate inheritance! I hate inheritance! I hate inheritance!”

But well, inheritance goes brrrrrr.

“Log” is the name of the place you write your tracing information into.

Let me introduce you to syslogd.

But well, it’s probably overkill, and you almost certainly just need to log on a shared volume.

The sheer number of people that do not expect a joke on this community… (Really, if you are trying to learn how to program pay attention to the one without the Humor on the name, not here.)

Well, I guess nobody expects.

That *++ operator from C is indeed confusing.

Reminds me of the goes-to operator: --> that you can use as:

while(i --> 0) {

This evaluates to NaN for some reason:

'10' % 0

Since JS doesn’t really differentiate strings from numbers, except on the places it does, it makes sense to make sure you are working with numbers.

(+x) % 2 == 0

If you forget for a second it’s Javascript, the language will turn back and bite you.

The letter you want after the P is an H.

Don’t you people have a development environment?

To be fair, I could say the same, but is probably a biased sample.

I have other red flags, like only distributing on docker, that I’ve tried, and tried again, and found that it’s a sign of a badly run project. But I can’t state any confidence on the discord based rule, because I’ve never tried to make any run.

This leads to the long names that senior programmers make fun of.

Hum… The notation that I’ve seen people making fun of is one where the long names encode the exact same information that C types can handle for you and nothing else. But YMMV.

Anyway, I don’t think any naming convention can save you after somebody goes over your entire codebase converting things without care for the semantics. If you are lucky, it’s one of the lazy people that do that, and you will “only” have to revise tens of thousands of lines to fix it. If you are unlucky, the same person will helpfully adjust the names for you too.

That kind of code usually is written on a restricted dialect of C.

C is not a language that allows for that kind of safety practice even on the fully-featured version.

The problem is, how do you fix it if you can’t make it break?

The worst thing is when somebody comes to you saying “yeah, I had this problem yesterday, but it’s working now”.

AWS and Azure are services, not libraries; Elasticsearch is mostly open source; and DynamoDB, well, how many people use it again?