Did you remember the episode end though? It basically ends with the robot attacking the maid. Even then they knew the dangers lmao.
(Completely side stepping the clearly prescribed ethnicity for house help part on this one though)
Did you remember the episode end though? It basically ends with the robot attacking the maid. Even then they knew the dangers lmao.
(Completely side stepping the clearly prescribed ethnicity for house help part on this one though)
That’s great, thanks for sharing! I thought of something related to this too:
"Conservatives believe individual responsibility, so in the end everyone has only one person looking out for them.
Socialists believe in collective responsibility, so you have everyone looking out for you."
I know which one I’d rather have!


Btw your import imports an import causing a cyclic dependency. Good luck <3
AI slop detected. Guitarist has weird left had ans no thumb.
Showing what’s in the cupboards & drawers is more like
ls -R
Americans miss u
I love the publisher ORLY³

On sending the information:
Microsoft bot: this issue has been marked as closed due to inactivity

Don’t forget to install the latest drivers!

As much as I’d love hating on Microsoft, I think this gross incompetence & shitty bureaucracy over malice from Microsoft. Kaginski was locked out of his account & Microsoft made it annoyingly difficult to recover. This is something I have also faced using Microsoft’s enterprise products, something we pay a lot of money for.
The bane of my existence is visiting Microsoft community posts, where “MVPs” advertise their years of experience before suggesting the most banal advice ever.

“Please Fund projects done by others, loved by all, which we can come and embrace, extend & extinguish… pretty please!”


I would kill for this lol



My man you’re half way to having hooves. You’re probably great at scaling vertical cliffs. /s


This tracks with my experience: I spent far more time double checking copilot output than trusting it. Also it almost always auto completed way too much way too often, but that could be UI/UX issue than a functional one.
However, by far the most egregious thing was that it made the most subtle but crucial errors I took hours to fix, which made me lose faith in it entirely.
For example, I had a cmake project & the AI auto completed “target_link_directories” instead of “target_link_libraries”. Looking at cmake all day & never using the *_directories keyword before I couldn’t figure out why I was getting config errors. Wasted orders of magnitude more time on finding something so trivial, compared to writing “boilerplate” code myself.
Looks like I am not alone:
Furthermore, the reliability of AI suggestions was inconsistent; developers accepted less than 44 percent of the code it generated, spending significant time reviewing and correcting these outputs.
When I did find it & fix it, something interesting happened: maybe because AI is sitting too damn low in the uncanny valley I got angry at it. If the same thing would have been done by any other dev, we’d have laughed about it. Perhaps because I’d trust a another dev (optimistically? Naïvely?) to improve & learn I’d be gentler on them. A tool built on stolen knowledge by a trillion dollar corp to create an uncaring stats machine, didn’t get much love from me.
Oh no! Not my sweets!
LLM would be great to parse all that data, but I think you miss OP’s point. AI can be useful to automate mundane jobs, i.e. jobs you can’t get away from. OP’s point in my view is verbose logs are noisey & difficult to parse, because you’re logging everything unnecessarily. If you Log interesting things and mark them with context & logging levels, Then you can dive in as deep as you need, when you need. Why add complexity (& other hazards) of AI when you can fix the root of the problem first yourself.