Working with a team of SREs using LLMs to troubleshoot production issues and holy shit - the rate at which it uses that exact language and comes to completely fabricated or absurd conclusions is close to 80-90%
> Nontechnical people simply don't have any idea about what LLMs are.
We need to be very very careful here. Just like advertisements work, weather you think you're immune or not, so does AI. You might think you're spotting every red flag, but of course you think so. You can't see all the ones you missed.
Do not make the mistake of thinking that being techy somehow immunizes you from flattery. It works on you too.
> The goal is to give the answer that would have come from the training data if that question were asked.
Or more cynically, the goal is to give you the answer that makes you use the product more. Finetuning is really diverging the model from whats in the training set and towards what users "prefer".
> NT has a far better VMM than macOS does and handles OOM significantly better than macOS (and Linux, for that matter).
That's one of my great frustrations with Windows. NT is a fine kernel. The userspace on top of that is fucking terrible though.
When people compare "operating systems" they're not comparing the kernel. They're at the most technical comparing the userspace tools shipped with that kernel, and at their most general the "ethos" of the developers that build the ecosystem. The terrible experience on windows of every programing having an installer that pokes around god knows where in the registry is just as much an experience of the Windows operating system as piping curl into bash is on Linux.
Thats not true. I wrote a compositor based on xcompmgr, and there damage was widely used. It's true that it's basically pointless to do damage tracking for the final pass on gl, but damage was still useful to figure out which windows required new blurs and updated glows.
The maps can be considered metadata. The data is the points and tracks, which should be self-hostable. I have them synced locally (desktop-mobile). The setup was admittedly an absolute PITA involving shell scripting and Python.
Oh thanks but it doesn't seem to support the metro here in Spain :( Google always sees live data like real arrival time and line closures.
Even the transport company's own site doesn't show that very accurately. But they're very manipulative. For example if a train is coming soon the signs upstairs don't show it because they don't want people rushing. Google shows the real data though, not their lies.
reply