Yeah. That’s (arguably) the background scenario to Asimov’s book “The Naked Sun” https://en.m.wikipedia.org/wiki/The_Naked_Sun
Edit: Ooh, Django already gave a cooler link to the same: https://discuss.tchncs.de/comment/10729278
Yeah. That’s (arguably) the background scenario to Asimov’s book “The Naked Sun” https://en.m.wikipedia.org/wiki/The_Naked_Sun
Edit: Ooh, Django already gave a cooler link to the same: https://discuss.tchncs.de/comment/10729278
AIs are going to commit virtual seppuku after a few days.
Yes. And that’s our best case scenario. Worst case is a wildly incompetent, but still effective form of SkyNet.
Yep. I’m old, cranky, and prone to broad statements to get reactions.
That said, for any of you all that love inheritance, I’m judging you so hard. So hard. Very judged. I probably hate your code, and your friends’ code, and your last teacher’s code. Especially your last teacher’s code.
Interfaces are great.
Inheritance is often a sign that the previous developer didn’t understand interfaces.
He died of XML factory injection pattern exposure.
Nyeeeh!
Python reimplemented the same dep management wheels 5x each, and I have no idea what common stacks look like anymore, but every time I encounter Python projects, something is always broken.
We need just one more complete re-engineering of the packaging standard. We promise to get it right, this time. No take-backs.
Exactly.
I’ve followed that guidance faithfully, for decades, and…now I’m a JavaScript expert.
READY.
Rock and stone!
Yeah! Gotta find those Long Term Stable (LTSL) life partners!
This is how I feel every time I see an overpowered “prototype” weapon in a video game that works better than the standard version.
Agreed!
There’s is a bit of clever game design in Deep Rock Galactic, which I hope catches on:
The default load out for new players is almost unarguably the best possible load-out, for that class, in the game.
As players progress, they can unlock more entertaining while objectively worse equipment, to amuse and challenge themselves.
And, I mean, of course we do. It’s hilarious because some truly challenging gameplay emerges.
And when it’s kicking my butt, I at least realize I chose that challenge for myself. I had the option to bring the good equipment that I started with, after all.
And it puts new players on more even footing with veterans. I tend to make easy missions with newbie friends harder on myself by bringing truly silly equipment load outs. It usually turns out fine, and when it goes badly for me, they feel good for rescuing a veteran. Or it goes sideways and I apologize and make slightly better equip choices for the next try.
Exactly. And configured by 5000 lines of brittle XML.
these are the trade-offs you make when burning out your team is more important than quality.
Yep.
Many directors and CIOs know exactly where they stand regardin the classic value proposition: deliver something trivial before next quarterly earnings statements - at the low easy cost of losing all organizational understanding of the code base.
Yeah. Haha! To be more fair, the top character in this chart should be trying to figure it out by feel, while crunched under a desk, and getting blasted by line noise.
These are excellent.
I need to add Perl.
Perl is a honey bee. You are unassuming and pragmatic. You fill every niche. Your buzzing carries meaning, but only to other bees. In theory, your ecosystem niche is filled by many competing solutions that are more fit to purpose. But somehow we all know in our hearts that if you disappear, all life on the planet will probably die soon after.
Lunchtime, doubly so!