Thank you kindly for the link. I’ll have to see what this brings to the table, but it’s always nice to have options!
Thank you kindly for the link. I’ll have to see what this brings to the table, but it’s always nice to have options!
I left Monday last week after a crash had occurred in prod. Had happened during the weekend because of a colleague fumbling on the Friday. Noticed it Monday morning. Notified the boss who didn’t care much and left for his afternoon off anyway, trusting me to do what i could. Which I did. Stabilised the bleeding, explained others what they had done and what to do, how to mitigate, how to temporise till I was back, then fucked off at 5pm sharp, for one of the best romantic weeks in years. Not a one phone call or message. I had even taken my laptop just in case they were really stuck. Nothing.
Vive la France 🇫🇷 is what I’m saying.
It’s wonderful for you that you live in a world where people use something else than Outlook to read email at work.
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.
That’s a really useful answer. Thank you!
Emails are surprisingly hard to format, actually. If you want to use modern HTML, anyway.
“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.
You would be amazed!
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.
DDG since 2016 when I had to switch because I was in China. Never went back and with everything I hear about Google, I don’t plan to. Only Google thing I still have and enjoy is Maps.
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.
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.