gruntled-worker

That's my point, we won't bother reading it. We'll let agents read it. People will eventually stop getting ticked off at this stuff.

One exception: if the model is poor or on 'low' and that leads to a crappy report. That's the equivalent of shipping performance-critical code built with -O0 in the compiler analogy.

Until ~2000, "cellphone user in public" equated with "smug asshole." We're at that icky rejection stage with AI.

Two years ago, that writeup would have been viewed as a generous gift of time to the community. Now we can't be bothered to read through it because we know where it came from, and that it's just worth $0.06 in tokens. Another reason (I think) is because we know what it portends.

In a few years, digging manually through bugs will probably be a last resort. We'll go from sneering to yawning at the reports, as another AI agent reads them and verifies the fix. Just like we ignore compiler-generated assembly code and people on their cellphones.

The Wikipedia version is simplified, but it bears mentioning that as written, it's going to be slower than the trivial version for most N's on 1983 compilers and systems. Fixed:

   register n = (count + 7) >> 3;
   switch (count - (n << 3))

Me mechanic not speak English. But he know what me mean when me say "car no go", and we best friends. So me think: why waste time, say lot word when few word do trick?

Not surprising to see the WSJ skipping the surveillance angle entirely. Aside from classic sport cars and to a lesser extent manual transmissions, I've never even heard about someone preferring old models until surveillance started rolling in.

I wish the US or EU mandated the separation of "basic driving OS" and "surveillance/infotainment/everything else OS" with the requirement that the vehicle be operable with the latter disconnected completely. It would let you avoid costly repairs when the massively overpriced spy-tablet breaks down on an old car. It would incidentally make everyone safer by not having people drive 30-year old jalopies just because they're not mobile spy stations.

California has self-driving vehicle fleets which, once municipally-owned like the older transport infrastructure eventually became, work way better than trains for almost all trip ranges up to planes. The sweet spot is when the fleet gets large enough to ban non-SDVs from urban cores, removing the need for all parking and quadrupling system throughput.

Yep. It's like rooting for a team or a rock star.

Alice is a football stats wiz. Alice is a WR Jones fan because he has an incredible 40-yd dash time and leads the league in YAC.

Bob is a WR Smith fan. Bob knows the stats are all cooked. Bob knows that if the stats weren't cooked, WR Smith would lead the league in all categories. Therefore, Bob doesn't bother with stats.

Test-drive it with an individual Pro account (5x or 20x) for a month. Download the Codex CLI client from https://github.com/openai/codex and auth it in the browser via the URL it provides. Set the model to 5.6-Sol and effort to max.

Waymo has a lead. Tesla's lead is about the same as a Roomba's.

Seriously though, if you're considering an EV, please give the traditional US/EU/JP/KR automakers a chance. Don't try to help the planet in one way while staking its heart in another.

Resource leaks, crossing non-exception-safe library/system code, CPU-specific quirks like accidentally unrestored FP/vector/control state, etc. Granted it's always been highly system-specific stuff, but that's the worst kind.

No complaints about this in particular, but code that uses setjmp/longjmp often has a risk profile that's way bigger than memory safety alone. If you're stuck with them then by all means, mitigate all you can.

Thought experiment: what if you used AI in the sort of situation where you would consider adding an external dependency? The differences between the two are obvious, but the level of delegation is not that different.

One difference is that you can (typically) keep on banging the prompt hammer until the problem stops twitching. That might make you want to delegate more.

That in turn might make you refactor the project with more, larger delegated areas. Increased delegation is one recently-added difference between programming and software engineering.

Chip fab locations have traditionally had more political than economic importance. Matrix multiplication chips and RAM have been the recent exception, while TSMC has long been the geopolitical exception. ASML's location only matters to the extent that it gets ordered not to sell to someone.

I agree with everything you wrote. I'd like to add the pyramid angle.

Fancy mansions have always been overpriced. For property prices to grow faster than inflation, the pyramid needed to grow its bottom. Supply restrictionism was the ticket. Eventually, every shack was priced mansion-like. This required extracting ever larger fractions of the incomes of renters. Some renters wisened up and bought homes (when they still could). Changing sides, they beefed up the scheme's political backing.

No one cares if mansions are expensive, but basic housing should be extremely cheap. This sounds like a handout but isn't. It's what an unadulterated market would provide. It's what the pre-1970 market used to provide.

That's not to say that markets should be left alone. It's to say that the way this particular market was "regulated" was fundamentally corrupt. We could call it negative regulation.

It's more like being regulars at the same bar. It cuts through demos. It's easier here since almost everyone is from elsewhere.

There's strange kinship and signaling in proximity. It's similar to college degrees. Working in SF - either in person or locally remote - puts people in a separate bin.

It's not just signaling. Once people move away the kinship factor fades, even when you already know them well past the signaling stage.

Look at it this way: while the upfront cost to scale up production is huge, prices are now high enough to justify it even if demand is expected to drop abruptly later on. So if you can wait 5 years for your next PC, 1TB RAM might go for what 64GB would have cost without the AI demand spike.

Granted, if you need a new system before then, you're SOL.

One thing to look out for is supply capacity curiously going offline in 2030 or whatever. That would hint at market power or collusion.

This is obviously going to happen. But sub-par and sloppy doctors are a thing too. Medicine has been using semi-intelligent systems for years that were nevertheless found to improve outcomes.

We need studies that quantify error rates from each source type, then we need to account for the fact that the artificial type will keep improving.

I'll happily train them for you but I charge by the hour, not by the token.

BTW, while we're on the topic. I don't do social media. I occasionally type up a text or post on a technical board. Maybe 98% of my textual interaction these days is with LLMs. I would not be surprised if my prose changes to resemble theirs over time. I suppose that's symbiosis for ya. It's possible that your AI-dar might get even more ineffective.

Are we positively sure that WASM will prove to be more future-proof than 640K MS-DOS or WinXP, or SNES cartridge files for that matter? On 6/23/26 there are a lot of emulators that run these. Will WASM necessarily beat them on 6/23/2051? Might be a case of xkcd 927.

auto get_xyz_position() -> std::unordered_map<std::string, double *> { ... }

I like the Andor writing and acting, but the directing has been more hit and miss. Some episodes feel more like reading a chapter from a book than watching a TV show. I wish they grabbed Alex Garcia Lopez, whose two Acolyte episodes are waaay above the rest.

We are not disassembling, we are assembling in another time direction.

Not anymore really, at least according to their preference. At a minimum, a capital T will prevent comedic errors like a head full of feathers.

https://www.npr.org/2023/01/08/1147704945/the-state-departme...

I expect to have trouble falling asleep just vicariously relating to the noise level there. Awesome project though.

"Mai" means "never" in Italian. Ain't gonna happen.