Somehow this really drives home how unhealthy that shit looks. Not that I've ever seen a human drink it, but it still feels like humans consume so much garbage food anyways (especially those that would drink this stuff voluntarily), that it doesn't make much of a difference in the end.

Meanwhile, this monkey eats healthy foods his whole life, so a gulp of colored sugar water with extra chemicals just feels much worse in comparison.

Certainly doesn't look very strait either...

Has he considered sending a message to the guy directly rather than posting about it on social media?

Ah yeah, that seems to be it. When I drop my keys in the right place, it goes into suspend. If I lift them back off afterwards, it wakes back up.

Neat. 🙃

Yeah, management wants us to use AI at $DAYJOB and one of the strategies we've considered for lessening its negative impact on productivity, is to always put generated code into an entirely separate commit.

Because it will guess design decisions at random while generating, and you want to know afterwards whether a design decision was made by the randomizer or by something with intelligence. Much like you want to know whether a design decision was made by the senior (then you should think twice about overriding this decision) or by the intern that knows none of the project context.

We haven't actually started doing these separate commits, because it's cumbersome in other ways, but yeah, deliberately obfuscating whether the randomizer was involved, that robs you of that information even more.

Yeah, that's my biggest worry. I always have to hold colleagues to the basics of programming standards as soon as they start using AI for a task, since it is easier to generate a second implementation of something we already have in the codebase, rather than extending the existing implementation.

But that was pretty much always true. We still did not slap another implementation onto the side, because it's horrible for maintenance, as you now need to always adjust two (or more) implementations when requirements change.
And it's horrible for debugging problems, because parts of the codebase will then behave subtly different from other parts. This also means usability is worse, as users expect consistency.

And the worst part is that they don't even have an answer to those concerns. They know that it's going to bite us into the ass in the near future. They're on a sugar high, because adding features is quick, while looking away from the codebase getting incredibly fat just as quickly.

And when it comes to actually maintaining that generated code, they'll be the hardest to motivate, because that isn't as fun as just slapping a feature onto the side, nor do they feel responsible for the code, because they don't know any better how it actually works. Nevermind that they're also less sharp in general, because they've outsourced thinking.

Oh yeah, I was kind of playing devil's advocate. It is certainly also cursed in many ways...

trance

"Physical AI" is also what they've started calling robots...

Was gonna say "dynamosaur" as a joke, then figured there's gotta be an anime with that name.

Turns out the T-rex would've almost been called that: https://en.wikipedia.org/wiki/Specimens_of_Tyrannosaurus#Dynamosaurus:_NHMUK_R7994

Hmm, that is kind of cool, in that you can have text on all 4 sides and it's still generally readable. Not really possible for vertical panels...

Today, I noticed that my glasses case sticks to my work laptop like a magnet.
I played around with it for a few seconds, then the thought struck me, that it might be my glasses case that's magnetic, and I might be fucking up the electronics or the HDD or something by holding it close to my laptop. Pulled away real quick then. 😅

I did try with my keys later, and well, turns out that it's my work laptop that's magnetic, so I guess, I wasn't fucking anything up after all...