Probably the reference manual for HR departments everywhere…

That was a beautiful read, cheers!

We have a table with literally three columns. One is an id, another a filename and a third a path. Guess which one was picked as the primary key?

Never seen something so stupid in 28 years of computing. Including my studies.

Hahaha! We’ve an “architect” who insists he needs to be the owner on the gitlab. My colleague has been telling him to fuck off for the entire week. It reached the point that fool actually complained to our common boss… The guy is so used to working as a start-up and has no fucking clue about proper procedures. It’s terrifying that he could be in charge of anything, really.

Holy shit in so glad it’s not just me. All I have ever seen from Java seems to be NullPointerException. (Which makes sense, but still, it’s pretty funny)

“Tester, c’est douter”

Doesn’t sound too weird to me. In my experience, devs always focus too much on positive / correct inputs, as they want things to work. Which is why you need testers that will catch all the weird crazy ways people can break things. Testers shouldn’t even see the code of it can’t handle nominal cases.

The alternative is not super exciting though. My experience with NoSQL has been pretty shit so far. Might change this year as the company I’m at has a perfect case for migrating to NoSQL but I’ve been waiting for over a year for things to move forward…

Also, I had a few cases where storing JSON was super appropriate : we had a form and we wanted to store the answers. It made no sense to create tables and shit, since the form itself could change over time! Having JSON was an elegant way to store the answers. Being able to actually query the JSON via Oracle SQL was like dark magic, and my instincts were all screaming at the obvious trap, but I was rather impressed by the ability.

“Hello IT, have you tried turning it off and on again?” pause “Is it plugged in?” pause “You’re welcome”

For most devs, it’s a Jenga tower. Only fancy algorithm devs get a nice Hanoi towers setup.

For some reason it reminds me of When Sysadmins Ruled The Earth, a short story about sysadmins dealing with the apocalypse.

My entire career is based on “yeah but you’re good with computers and programming!” I just wanted to do fine arts and paint for fuck sake. And I could have made a career out of it, as history as since shown! Ah well. Maybe my kids will fare better, we’ll see.

One of my colleague is leader of the team managing our internal software systems, but also a potato farmer. Somehow.

Oh I agree! It was so annoying.

I’ve had this so often… very frustrating.

I like to think the 400 within a 200 is for “look, I managed to reply to you. But there is bad news”

More useful would be what sort of values is acceptable there. Can I use team number 2318008? Can I use team 0? If not, why not? WHY / WHY NOT is often useful.

Next 20 years? Dude, I was being taught IPv6 back in 1997, as part of my network course. It was supposed to be the future back then, and so we were trained, expecting to have to implement it wherever we’d go work.

Yeah… I didn’t end up in networks, but I sure as shit did not see it used even once in my career so far. Not a single time. It’s kinda hilarious, really.

I was taught it around 1988, most likely on a Thomson MO5 ? Or maybe it was a TO9. It was a while ago :,) I just remember the fascination watching the little pixels color themselves and experimenting with the instructions to see what we could come up with.

If you like turtles and programming, you might enjoy hearing about LOGO.
Back in the day, that was the first programming language I was taught. Years and years before I’d learn C or ASM.
You’d give instructions to a “turtle”, moving it about the screen, drawing as it did so. It was a magical experience for 9yo me.

It was called The x86 Assembly Bible and I would not have been able to do much of anything without it.