[deleted]
GPT-5.5
611–620 of 1001 posts
Re: GPT-5.5
#612> One engineer at NVIDIA who had early access to the model went as far as to say: "Losing access to GPT‑5.5 feels like I've had a limb amputated.” This quote is more sinister than I think was intended; it likely applies to all frontier coding models. As they get better, we quickly come to rely on them for coding. It's like playing a game on God Mode. Engineers become dependent; it's truly addictive. This matches my o…
LLMs upend a few centuries of labor theory. The current market is predicated on the assumption that labor is atomic and has little bargaining power (minus unions). While capital has huge bargaining power and can effectively put whatever price it wants on labor (in markets where labor is plentiful, which is most of them). What happens to a company used to extracting surplus value from labor when the labor is provided…
This is our one chance to reach the fabled post-scarcity society. If we fail at this now, we'll end up in a totalitarian cyberpunk dystopia instead.
Re: GPT-5.5
#613> One engineer at NVIDIA who had early access to the model went as far as to say: "Losing access to GPT‑5.5 feels like I've had a limb amputated.” This quote is more sinister than I think was intended; it likely applies to all frontier coding models. As they get better, we quickly come to rely on them for coding. It's like playing a game on God Mode. Engineers become dependent; it's truly addictive. This matches my o…
That's why local models are important. Of course they aren't alternative to the current frontier model, and as such you cannot easily jump from the later to the former, but they aren't that far behind either, for coding Qwen3.5-122B is comparable to what Sonnet was less than a year ago. So assuming the trend continues, if you can stop following the latest release and stick with what you're already using for 6 or 9 mo…
The cloud dependency problem goes deeper than the model layer though. Even if you run inference locally, your digital identity — your context, your applications, your behavioral history, is still custodied by whoever controls your OS.
Local models solve one layer of the dependency stack, but the custody assumption underneath it remains intact. That's the harder problem.
Re: GPT-5.5
#614Earlier quoted context omitted.
LLMs upend a few centuries of labor theory. The current market is predicated on the assumption that labor is atomic and has little bargaining power (minus unions). While capital has huge bargaining power and can effectively put whatever price it wants on labor (in markets where labor is plentiful, which is most of them). What happens to a company used to extracting surplus value from labor when the labor is provided…
I am still trying to figure out the business model of open weights. Like... it's wonderful that there are open LLMs, super happy about it, good for everyone, but why are there these? What is the advantage to their companies to release them?
Big AI labs are losing money. Open Models is making the pricing equation a lot trickier for them.
Re: GPT-5.5
#615why the stats of every AI on every release looks around the same?
Are the tests getting harder and harder so the older AIs look worst and the new ones look like they are "almost there" ?
Re: GPT-5.5
#616Earlier quoted context omitted.
Could be a great feature, can't wait to test! Tired of other models (looking at you Opus) constantly stuck mid-task lately.
Interesting, I just had opus convert a 35k loc java game to c++ overnight (root agent that orchestrated and delegated to sub agents) and woke up and it's done and works. What plan are you on? I'm starting to wonder if they're dynamically adjusting reasoning based on plan or something.
This has to be bait.
Re: GPT-5.5
#617> One engineer at NVIDIA who had early access to the model went as far as to say: "Losing access to GPT‑5.5 feels like I've had a limb amputated.” This quote is more sinister than I think was intended; it likely applies to all frontier coding models. As they get better, we quickly come to rely on them for coding. It's like playing a game on God Mode. Engineers become dependent; it's truly addictive. This matches my o…
I actually don't mind the coding part, but the information digging across the project is definitely by orders of magnitude slower if I do it on my own.
Re: GPT-5.5
#618Earlier quoted context omitted.
I’ve noticed when writing little bedtime stories that require specific research (my kids like Pokemon stories and they’ve been having an episodic “pokemon adventure” with them as the protagonists) ChatGPT has done a fantastic job of first researching the moves the pokemon have, then writing the actual story. The only mistake it consistently makes is when I summarize and move from a full context session, it thinks tha…
Gyarados is a flying type but I think it may be accurate that it can't actually fly. The only flying moves it can learn in any generation are Hurricane and Bounce (Bounce does send the user up into the air for a turn but the implication is that they've trampolined up extremely high rather than used wings to ascend)
If anything it should probably be combined water/dragon type
Re: GPT-5.5
#619Earlier quoted context omitted.
One might argue that it’s not too too different from higher level abstractions when using libraries. You get things done faster, write less code, library handles some internal state/memory management for you. Would one be uneasy about calling a library to do stuff than manually messing around with pointers and malloc()? For some, yes. For others, it’s a bit freeing as you can do more high-level architecture without g…
I see this comparison made constantly and for me it misses the mark. When you use abstractions you are still deterministically creating something you understand in depth with individual pieces you understand. When you vibe something you understand only the prompt that started it and whether or not it spits out what you were expecting. Hence feeling lost when you suddenly lose access to frontier models and take a look…
"When you use abstractions you are still deterministically creating something you understand in depth with individual pieces you understand."
I always thought the point of abstraction is that you can black-box it via an interface. Understanding it "in depth" is a distraction or obstacle to successful abstraction.
Re: GPT-5.5
#620> One engineer at NVIDIA who had early access to the model went as far as to say: "Losing access to GPT‑5.5 feels like I've had a limb amputated.” This quote is more sinister than I think was intended; it likely applies to all frontier coding models. As they get better, we quickly come to rely on them for coding. It's like playing a game on God Mode. Engineers become dependent; it's truly addictive. This matches my o…
Will the foundation for a skyscraper ever be dug with shovels again?