Lost out on $900m off a single spelling mistake - probably the most expensive spelling mistake in history.
600 karma · joined December 1, 2024
Lost out on $900m off a single spelling mistake - probably the most expensive spelling mistake in history.
Intel missed for a different reason - they didn't invest in the product space at all for decades. In terms of units they had the most market share (millions of Intel Integrated Graphics chips), but it wasn't seen as important. Bare minimum to render Windows and Office UI, nothing more.
Within a year many of these (>20%) started experiencing the "400 MHz bug" where the CPU is either intermittently or constantly stuck at 400 MHz, and the laptop starts to heat up like an oven. As far as I know there has never been any conclusive fix for this issue from Framework, or even an official debugging guide.
It really soured me on the idea of repairable laptops - what's the point of it being "repairable" if you have huge fundamental flaws in the hardware that go unfixed?
The mount is fine and speedy enough, but the underlying reads/writes turn into native NTFS reads/writes through Windows. NTFS file API is incredibly slow - high fixed overhead for initial file access.
So patterns like node_modules with many small individual files (or compiling code in general) are much much slower on Windows or WSL2 /mnt/c due to the fixed overhead adding up over a large number of files.
It's a ridiculous problem that has plagued Windows for years.
End result is that many outsourcing firms are borderline fraudulent in the way they treat their customers.
I have to regularly use Azure DevOps and the whole platform is painful, and now is rotting on the vine. I hear there is internal strife at Microsoft between Azure DevOps and GitHub products.
It would limit the blast radius, which at least is an improvement.
C# interoperability loosens guarantees (particularly immutability) that F# code normally relies on. There are surprising limits that come up in generics because of how they map to C#.
A "dumber"/vague framing will get a less insightful solution, or possibly no solution at all.
I don't even necessarily think this is a critical flaw - in general it's just the model tuning it's responses to your style of prompt. People utilize LLMs for all kinds of different tasks, and the "modes of thought" for responding to an Erdos problem versus software engineering versus a more human/soft skills topic are all very different. I think the "prompt sensitivity" issue is just coming bundled along with this general behavior.
It doesn't matter how competent the actual model is, or how long it's able to operate independently, if the harness can't handle it and drops responses. Made me think are they even using their own harness?
At least Anthropic is obviously dogfooding on Claude Code which keeps it mostly functional.