HN user

whycombinetor

454 karma
Posts7
Comments125
View on HN

I feel obligated to warn future readers that this post contains decaying corpse imagery and is therefore not suitable for breakfast.

I find it interesting that they gave the father a funeral. So there likely was a proper eulogy given. People in that position often don't get a funeral.

I feel this way about gpt-5-nano (EOL December 2026). It seems like the open weight models have progressed a long way since these old models were released though. Deepseek V4 Flash is even cheaper than gpt-5-nano. I'm still going to pay a cloud provider to run it for me, I'm not local inference pilled yet, but I _can_ run it myself in the future if worse comes to worst.

Objectively testable evals are one thing, but how does one judge whether a new model is adequately reproducing the subjective "writing style" of an old model that you've gotten accustomed to the feel of?

Oh, didn't read that part of the news. That's great. Ability to run x64 docker images seminatively was one of the big reasons I jumped to the M1 platform when it came out and I was baffled that they would remove it.

After reading this and remembering an old hobby project, I decided to switch the deploy from a systemd service to PM2, which apparently has rolling deployments without needing Docker engine (for those of us minmaxing instance RAM).

I read the Fogbank story and recognized it immediately. Not the nuclear material. The pattern. Build capability over decades. Find a cheaper substitute. Let the human pipeline atrophy. Enjoy the savings. Then watch it all collapse when a crisis demands what you optimized away.

In defense, the substitute was the peace dividend. In software, it’s AI.

Before it was AI, the cheaper alternative was remote contract dev teams in Eastern Europe, right?

For real work I'm already on Opus full time (plan+execute). I think there's a different space for cheap-but-good-enough options for small-to-med repo hobby projects. (Not enough usage to warrant a plan.) And Opus is only ~30 tok/s while grok-code-fast-1 is ~120. So planning with Opus and executing with grok-code-fast-1 is still on the table for me - it's good at following explicitly written plans, lightning fast.

If it's between a human or an AI copywriting SEO slop, I'm happy to see an AI take that job. SEO content marketing is so painful to read once you realize you're reading it, and I have to imagine it's as painful to write if you're a technically talented writer.

Now AI is summarizing your daily progress from your commits and AI is writing the planning docs (with HITL). And version control makes it a historical record of your planning process. Keeping detailed planning docs doesn't take your whole day anymore and can be an integral part of any IC's workflow now.

Every local tree listing that I've clicked is incorrect. I'm guessing bad municipal data. But this seems useless if it's all wrong.

It sounds like AI summarization tools would be beneficial. You can just have the conversation, not fill out any forms afterward, then your partner can either watch the recording or read the AI summary of the relevant customer needs from the recording (or ask their AI agent questions about the transcript of the recording).

Are other phrases of the form "ending ____ness", where ____ is a racial qualifier, also acceptable, then? Someone using that term could similarly argue that they're not advocating for the eradication of ____ people - just the identity and behavior associated with ____ people.

It's a poor metaphor. Real tolerance necessitates intolerance - see Marcuse. What is a browser going to do, send malformed HTTP requests and name-and-shame any server who refuses to respond? Servers vs. browsers is not the same type of relationship as people vs. people.

Not to mention that the author's metaphor is implying that certain types of people are malformed.

What a bizarre bait and switch. Starts talking about browsers allowing malformed HTML and uses that to draw conclusions about allowing certain types of people.