Though the chance someone other than you dies from you taking a shit is pretty far fetched, and I'm not liking having to try to conceive of how that happens.
But a lot of activities are this way. Getting on a ladder in public could kill someone, just breathing around other people could kill someone, etc etc.
But what about monster HDMI cables?
Well, driving to work is basically that. Non zero chance someone dies.
Also, a bunch of shit is about ready to burst out because they somehow decided to use wallpaper to hold a bunch of stuff to the wall instead of putting it in a closet. But it looked fine in the moment, so decided it was good enough.
So being drunk affects how you use light/dark mode?
Based on my experience with LLM and developers I personally know, my only assumption is they don't have the skills in the first place...
In corporate world there are a lot of "developers" that actually act kind of like codegen. They just throw plausible sounding bullshit into an editor and hope for the best. Two examples:
Once asked to help a team speed something that ran slow, even by their low standards. Turned out they had made their own copy file routine instead of using the standard library one, and sucked the file into memory, expanding array 512 bytes at a time, and then wrote it out, 512 bytes at a time. I made the thing nearly instant by just making it a call to the standard library function to copy a file.
While helping with a separate problem, I noticed their solution for transferring some file with an indeterminate version number in the middle of the file name. It was a huge mess, but the most illustrative line was the line in their Java application declaring a string "ls /path/with/file|grep prefix.*.extension".....
Lots of human slop out there that AI can actually compete with.
I just don't get it, even the purportedly best models screw things up so much that I can't just leave them to the job without reviewing and fixing the mess they made... And I'm also drowning in pull requests that turn out to be broken as it proudly has "co authored by Claude" in it... Like it manages to pass their test case but it's so messed up that it's either explicitly causing problems, or had a bunch of unrelated changes randomly.
I feel like I'm being gaslit as I keep reading that there are developers that feel they successfully offloaded the task of coding.
Closest I got was a chore that had a perfect criteria "address all warnings from the build". Then let it go and iterate. Then after 50 rounds each round saying "ok should be done now, everything is taken care of, just need to do a final check". It burned though most of my monthly quota doing this task before succeeding. Then I look at the proposed change... And it just added directives to the top of every file telling the tools to disable all the warnings... This was the best opus 4.6 could do...
Now sure, I can have it tear through a short boiler plate and it notice a pattern I'm doing and tab through it. But I haven't see this "vibe" approach working at all...
Certainly they knew, but did the same people who saw that knew it wasn't supposed to be going there? Like you see millions going to a datacenter, but maybe you just assume that's normal and have no idea that they aren't being billed for it?
Closed loop is often relative.
The water in a rack, closed loop, it gets recirculated.
However, the closed loop will run through a liquid to liquid heat exchanger, and that second loop is usually going to a tower to get evaporated.
The plumbing in the rack can be very picky about water quality and want additives that would be very bad in an open loop scenario.
So you end up with people at the rack level talking about 'closed loop', but they run through a CDU that is open loop. Basically closed loop when picky about the water, moving heat to open loop where they can actually get rid of the heat effectively.
While CATL has done work and has made real world solutions, I wouldn't take their marketing material over the broader scientific consensus.
I am totally willing to buy that the market ends up between NMC and Sodium with LFP left behind despite having some advantages over sodium. Of course as solid state becomes a thing, that will be more of a factor than Na v. LFP v. NMC.
The plague of work chats now:
Here's what ChatGPT/copilot had to say:
People can ask for themselves, you answering that way adds no value. Just say you don't know.
In group chats, keep your mouth shut and let people that actually know answer. Don't drown out the actual expert answers.
And holy hell the ones that will die on the hill that they are right because chatgpt agreed with them even when they are totally wrong...