Let’s Encrypt Expiry Bot just entered the chat.

But WHY are you trying to make a case for a bad practice? Don’t enable this kind of bullshit, please.

If there’s an error, don’t say it’s 200 OK. Give me something, a 4xx, or at least a 500. Sure, add all you want to the body, but respect the goddamn headers!

This fucks up so many things - starting right with API specs and documentation, s23 (or any other code this crap spits out) are not a part of the pdf file, which is the ONLY available documentation for this 3rd party service. If it serves any internal purpose, I have no clue, but for me it’s useless.

Log analytics is a mess, and you can forget about auto-generating a client, of course…

This is just a huge red flag for me, if their public interfaces look like this, I dont want to know whats under the hood, and I’m actively lobbying for us to change to another provider.

I may have run in your acquaintance work, stuff along the lines of

200 OK

{ error_code: s23, error_msg: "An error was encountered when performing the operation" }

If you happen to run into him, kindly tackle him in the groin for me.

Thanks!

Oh yeah, I remember using tortoiseCVS briefly.

Mercurial and Bazaar also showed up at around the same time as git, I think all spurred by BitKeeper ending their free licenses for Linux kernel devs.

An interesting shot to the foot, that one.

BitKeeper was a proprietary version control system that somehow (and with a lot of controversy) ended up being adopted by a big chunk of the Linux kernel developers, while others were adamant against it.

In any case, they provided free licenses to Linux devs, with some feature restrictions (including not being able to see full version history) only available for premium clients, while Devs who worked on open source competing systems were even barred from buying a licence.

When someone started to work on a client that allowed access to these locked away features, they revoked the free licenses, and a host of solutions started being developed immediately. Linus Thorvalds himself started work on git, and that eventually got adopted by the whole Linux ecosystem and, nowadays, the world.

As for BitKeeper, it’s been dead for years now.

Especially writing drivers amirite!

$ cp -r src/ src.old

No sir never seen it in me life, honest to god sir

That’s phrased brilliantly, and capturey my own perception of Musk

This is how we have 3 different APIs that sometimes do the same thing, but most times are incomplete when compared to the original v1, who in the meantime wasn’t properly maintained because we were “migrating” and now you have to use bits and pieces of the 3 of them to do anything.

It’s a nightmare. Can’t wait for the next genius to come along and start a v4, that will never be completed and will only re-implement parts of the old APIs while implementing all the new features

I exhaled vigorously through my nose.

You’re appealing to authority instead of presenting real arguments.

But why would I use something that takes more effort and care?

I’m sure you’re right and it’s possible, but if I don’t have to fix another python project at work I’ll be in heaven.

Gotta appreciate the level of commitment on this commit…

The secret here is to come up with a business case that shows management what an incredible ROI they should expect from this initiative.

Then you get to play with robots for a few months instead of actually working!

I disagree, with a passion.

It is soooo cluttered, so much useless redundant tags everywhere. Just give JSON or YAML or anything really but XML…

But to each their own i guess.

I’d do it just to style on the new guy, start with something like “ah, so humanity has lost the skills that we possessed in the days of yore…”

(TL note: this is in reference to companies refusing to up the pay for their skilled workforce, and ending up paying more to new guys that’ll have to learn it all from scratch)

Technically, isn’t this a different thing? Genuinely asking.

There could be a license that forbids use (sort of like the CC no commercial use license) but still allows the code to be reviewed publicly, no?

I use TZ identifiers, and confirm the expected behaviour (“Berlin time, correct?”), as then I know how I should handle DST changes.

It should be implemented in people’s brains.

How this goes, usually, is:

Them:…before 6PM.

Me: 6PM… Ours? The server’s? The user’s?

Them: GMT, of course.

Me: So that’s 7PM London right now, and changes to 6PM in November?

Them: What no are you stupid. Always 6PM GMT.

Me:* jumps off a cliff*

Can you at least wait for me to die before taking me to hell, Satan?

Not sure if I’m just missing a reference here, but if you choose the pizza you can have both.