Comment by jdw64

10 days ago

I think GPT writes code the best. How well will it write in version 5.6? It gives me chills.

Recently, I went head-to-head with GPT on nearly 2,000 lines of code, and GPT's solution was superior and faster. I even referenced multiple codebases on GitHub while trying, but they were incomparable to GPT.

So using GPT brings both fear and excitement.

The fear comes from realizing that this level of code is now the average for most people. The excitement comes from knowing that I can now study and learn at this level too.

I'm really looking forward to seeing how much more advanced the code will be with the upgrade to 5.6.

I am on the opposite camp. Open models are starting to perform better. GPT 5.5 keeps on messing things up.

On the contrary, pi + glm + DeepSeek… bliss.

Fable was a different kind of beast though. Rip.

  • Every time I use opus these days I go shut up... you are not fable.. Hard to imagine how just three days with it changed how I saw LLM use.

    • Yes, I've just come to the end of implementing all the planning I did while Fable was available. And nothing now comes close to creating plans that could be coded and just worked like it did.

      On a large C codebase, Claude hallucinates constantly, and GPT 5.5 gets there are with a lot of help, but still gets things wrong.

    • I'm reluctantly starting to feel grateful that I went camping right over the window that Fable was out.

  • GPT-5.5 has been really hard to beat imho. I've spent $$$ on Opus, Deepseek v4 Pro and recently started to dogfood GLM-5.2 (which is not bad) but I cannot really trust any of them (almost blind) like I can trust GPT-5.5. It gives me tremendous confidence. I cannot say the same for any of the others I mentioned.

  • Yeah, Opus/GPT need multiple rounds of reviews from each other to get to clean auto review. Fable was like, it is done and indeed… crickets in bot comments. ‘No issues’ galore.

  • >> I am on the opposite camp. Open models are starting to perform better. GPT 5.5 keeps on messing things up.

    I'm working in a 600k+ LoC codebase that has complex domain-specific logic and lots of moving parts. I find that Codex 5.5 is pretty good at surgical fixes, but does not go out of its way to explore and figure out what those surgical fixes might break. So I only use it to work on parts of the system that are pretty isolated from everything else so that risk of regression is small.

    • I'm trying not to be the "you're holding it wrong" guy, but ... have you just tried telling it to explore the codebase for things it might break?

  • Ditto on GLM 5.2 + DeepSeek V4 Flash combo.

    For most important work (complex, cross-domain inquiries etc.), I still rely on Codex GPT 5.5 though.

Purely subjective, but I tend to prefer reading Opus 4.8 output over GPT 5.5 code, even when the latter can have a higher overall ceiling. The former is just a bit more convenient to review.

> I think GPT writes code the best. How well will it write in version 5.6? It gives me chills.

Heard this exact sentence multiple times a few months ago about Opus 4.6, then 4.7 and 4.8 were considered a disappointment and today people miss "the good old times of 4.6" (referring to a few weeks of February 2026).

Very fascinating to look at all of this unfolding.

  • Reading this thread makes me feel like I'm taking crazy pills. The folks on this train in my team do not produce anything significant that we can rely on or use. A lot of hollow prototypes that join the prototype graveyard and code that needs extra scrutiny on critical areas ultimately leading to taking longer.

    It's a shame, they were smart and productive engineers. Now? I guess everyone is just all-in on the slot machine.

    • This split in what different people or groups get out of LLMs is pervasive and really interesting. In the beginning I was dismissive of those with bad experience with a "you are holding the tool wrong" smugness. But as I read more and more experience, I see all combos and I now know my initial knee jerk conclusion was clearly wrong. There are newbie programmers getting good or bad results as well as experienced developers getting either flip of the coin. I don't know what to conclude. I really want to know what are the lines that explain these very different outcomes. Is it the types of problems being solved? The harnesses? The programming languages? FWIW, my experience has been that among my cohorts of mid to deeply experienced developers working in the domain of experimental physics, all have leveled up various degrees after adopting Sonnet and Opus level LLMs using claude code CLI in Python, C++ and web tech, small scale scripts up to multi-package novel system develop and green field as well as incremental development and code maintenance.

      2 replies →

I'm suspect on how much of a coding advance it will be.

Seems odd that their announcement has zero coding benchmarks, with the closest related thing being terminal bench.

  • They claim extreme performance on ExploitBench, which Mythos was touted as being incredible at. https://x.com/OpenAI/status/2070555278576439306

    • My guess is that it's same base model as 5.5, but with additional post-training to improve and benchmaxx on a few things like that.

      If they really thought it was competitive with Mythos/Fable across the board, then why wouldn't they release a broader set of benchmarks, and why price it day 1 at 1/2 the cost of Fable?

      5 replies →

  • Tracking model performance on Artificial Analysis makes me think these models are constantly optimized/tuned in some way or another. GPT 5.5 was scoring in the mid 60's when it was first released, now it's almost 10 points higher.

  • Maybe I'll know once I try it? Honestly, for small functions or methods, I don't think there's a huge difference between models. But the larger the code gets, the more noticeable the difference seems to be.

    Personally, I think this kind of coding experience varies from person to person

  • sadly with all the labs benchmaxxing I feel like you just have to try the model for a while to really evaluate how good it is, especially for each individual use case

Is it possible for you to provide examples? What were you trying to solve? What was your solution and why was GPT's solution superior and faster?

  • Not trying to be mean but it's likely the case that OP is not evaluating this properly, either due to a lack of skill or a lack of objectivity

Codex 5.4/5.5 has been great for me as well compared to Claude Opus.

I've been mostly using it for Godot/GDScript code reviews, rubber duckying, asking it for better ideas for naming stuff (one of the hardest problems in programing)

I still can't trust it for generating code for entire files/classes/projects, because it's still icky, creating unnecessary variables and functions, using multiple `if`s instead of `and` or `or`, but it's good enough for generating Mac/iOS apps for my personal use in SwiftUI because fuck trying to keep up with Apple's documentation, or even migrating ancient Visual Basic stuff I made as a kid up to SwiftUI :)

> So using GPT brings both fear and excitement.

Only excitement for me. I've never been more productive, not because I ask AI to make something for me, but it helps me make what I was already going to, but better and quicker.

AI like any other tool could help smart people be smarter and dumb people be dumber, rather kinda like Toklien's Ring: You could be Sauron or you could be Bilbo or Frodo, or you could be Gollum :)

  • For me in Game dev, codex has a habit of checking every argument for null and then silently early exiting the methods when true. I have explicit instructions for it not to do this - but it still does. I haven't done any c# outside game dev but I have no idea why people would want their programs to silently fail.

    • Same; I explicitly added an instruction in AGENTS.md to tell it that sometimes it's better to crash if something crucial is missing at runtime, but it keeps insisting on checking for null references and other invalid values.

      It's better if I don't let it generate code and just use it for reviewing my code.

I have long felt like "out of the box", I really dislike gpt's coding style. It seems really verbose and likely to write way too much error handling and wordy comments and worse at finding existing functionality to reuse rather than writing everything from scratch. This has been relatively easy to mitigate with prompting, but I still find it annoying.

YMMV I guess!

  • I think you could be right. I do use excessive error-handling code and verbose comments — that's true.

    But most of my time is spent on delivery, and the biggest problem with delivery is that if a bug occurs during runtime, the client curses me out. So to me, GPT code feels meticulous.

    Open source contributors might be different. Most of them write code after long periods of deliberation. They take their brightest ideas and put them into open source. Those pieces of code are probably the best answers those programmers can give.

    But for someone like me, who works primarily on delivery, we mostly plug in proven patterns and focus on getting things done. 'It works' and 'it's beautiful' are different terms, after all. In that sense, I highly value the meticulousness of GPT code — the very thing you called verbose. Because even if it's inefficient, at least it runs, and it catches and wraps around far more of the parts where things break.

    Given a month, I could probably write code at GPT's level, at least to some degree. The problem is the difference between one hour and one month. At its core, AI code is still based on training data.

    • You don't want to handle errors in all the leaves of the system the way AIs have a tendency to, because you very rarely have the right context that deep in the stack to actually handle the error in an intelligent way. So what they end up doing (IMO) is actually hiding problems deep in the stack, in this effort to avoid a visible crash.

      I think it's very similar to the tendency to write too much from scratch and reuse too little, in both cases what is necessary is a broader view of how the whole system fits together, rather than only the specific method / file / module being written.

      2 replies →

> I even referenced multiple code bases on GitHub

Well, GPT referenced every GitHub code base, no wonder it won! :)

I prompted Codex 5.5 to one shot something where I wanted the design to have a pluggable decision module. I gave it a few examples of the kinds of inputs and actions I expected. I did not constrain it beyond that high level of what I wanted. The design it came up with was very good. Easily on par with what any senior engineer at big tech would. And cleanly decoupled in a way that would make future refactoring simple. I was damn impressed.

I haven't tried the latest Codex but I switched from GPT to Claude because I think Claude writes much better Code. GPT's code ends up way more verbose/complex/overengineered than it needs to be.

How do you judge what is a good or bad thing to learn from a LLM? So you don't have to unlearn the bad bits later

  • When I searched for papers on using LLMs, I found that typically, you can have an LLM generate code and then ask it to find GitHub projects similar to that code. Then you can learn by looking at the pull requests and seeing how they structure things In the old days, if I wanted to understand why memory offsets, padding techniques, or data layout structures were written a certain way, I had to stare at a senior programmer's code all day or wait for them to reply. But LLMs, while they do flatter me, explain things at a level I can actually understand. And LLMs don't get annoyed.

  • There's a lot of tacit knowledge in programming.

    -Why do you cut API boundaries this way? -Why do you change the order of struct fields? -Why do you deliberately insert padding?

    Most of it depends on the background and context. Sometimes you add it, sometimes you don't. To understand this tacit knowledge, you need access to senior developers. But their attitude often depends on how promising the student is and what background they come from. On top of that, you don't have to rely on the respondent's mood, authority, or availability.

    Programming is fundamentally a field that requires seniors. In my case, I had no such seniors at all. I learned to code by buying codebases from failed companies and studying them. My first job didn't hire me as an employee—they hired me as the CEO of a subcontracting company (because that was structurally more advantageous for the contract). So I wasn't given the patience to learn programming fundamentals gradually. I had to pay penalties if I failed. Most of the projects I worked on were the kind where failure meant bankruptcy for me. Naturally, there was no one to teach me.

    Most of my knowledge comes from reverse-engineering the code I purchased.

    People say LLM code contains falsehoods, but commercially sold code has always had falsehoods too. Honestly, if we're just talking ratios, LLM code has fewer falsehoods.

    In that sense, I still think it's a matter of context. If LLM code is false, was human code ever really true? LLMs do lie. They generate plenty of incorrect code. But humans do the same thing. If a problem comes up, you just look it up then and there. For me, LLMs and humans aren't all that different.

No offense but have you considered the strong possibility that you’re just not good at what you do? I am occassionally pleased but mostly annoyed or disappointed… but never getting anything close to chills. That sounds downright weird.

  • You're not wrong. But programming isn't something only talented people do.

    • Really? That doesn't line up with this forum.

      As a non-software engineer reading this forum it sounds like everyone is basically von Neumann working on Operator algebras and Lattice theory.

      I assumed that is why the view of LLMs is so negative on here. While Claude seems kind of amazing to me I am not a genius working on Lattice theory like most people here.

      1 reply →

  • Another strong possibility is that you might be working on something that’s not very prevanlent in the training set.

    Even the choice of programming language matters, e.g. Java or Javascript vs some niche one.

  • No offense but have you considered the strong possibility that you're just holding it wrong? You're entitled to your opinion, but OP is hardly the first person to say something like this and is surrounded by tons of folks saying the exact same thing. Just because it sounds weird to you, doesn't mean it's not true.

    • Idk, all the great programmers I've come to respect are of the opinion that the code it outputs, while often useful, is not high quality. Likewise, all of the influencers and "thought leaders" I have seen on social media who I did not have a high opinion of previous to 2022, have all become AI influencers and make these kinds of claims. So while it's possible that the great programmers are not capable of using this tool effectively, I doubt that is the case, seeing as the mythical 10x productivity improvements have not materialised.

      3 replies →

    • Everyone saying it is in the "not as good as they think they are" camp is the very obvious explanation.