2/17/2026 at 5:14:20 PM
I really liked this part:In December 2024, during the frenzied adoption of LLM coding assistants, we became aware that such tools tended—unsurprisingly—to produce Go code in a style similar to the mass of Go code used during training, even when there were newer, better ways to express the same idea. Less obviously, the same tools often refused to use the newer ways even when directed to do so in general terms such as “always use the latest idioms of Go 1.25.” In some cases, even when explicitly told to use a feature, the model would deny that it existed. [...] To ensure that future models are trained on the latest idioms, we need to ensure that these idioms are reflected in the training data, which is to say the global corpus of open-source Go code.
by homarp
2/17/2026 at 6:10:48 PM
PHP went through a similar effort a while back to just clear out places like Stackoverflow of terrible out of date advice (e.g. posts advocating magic_quotes). LLMs make this a slightly different problem because, for the most part, once the bad advice is in the model it's never going away. In theory there's an easier to test surface around how good the advice it's giving is but trying to figure out how it got to that conclusion and correct it for any future models is arcane. It's unlikely that model trainers will submit their RC models to various communities to make sure it isn't lying about those specific topics so everything needs to happen in preparation of the next generation and relying on the hope that you've identified the bad source it originally trained on and that the model will actually prioritize training on that same, now corrected, source.by munk-a
2/17/2026 at 8:04:02 PM
This is one area where reinforcement learning can help.The way you should think of RL (both RLVR and RLHF) is the "elicitation hypothesis[1]." In pretraining, models learn their capabilities by consuming large amounts of web text. Those capabilities include producing both low and high quality outputs (as both low and high quality outputs are present in their pretraining corpora). In post training, RL doesn't teach them new skills (see E.G. the "Limits of RLVR"[2] paper). Instead, it "teaches" the models to produce the more desirable, higher-quality outputs, while suppressing the undesirable, low-quality ones.
I'm pretty sure you could design an RL task that specifically teaches models to use modern idioms, either as an explicit dataset of chosen/rejected completions (where the chosen is the new way and the rejected is the old), or as a verifiable task where the reward goes down as the number of linter errors goes up.
I wouldn't be surprised if frontier labs have datasets for this for some of the major languages and packages.
[1] https://www.interconnects.ai/p/elicitation-theory-of-post-tr...
by miki123211
2/17/2026 at 8:16:02 PM
I believe you absolutely could... as the model owner. The question is whether Go project owners can convince all the model trainers to invest in RL to fix their models and the follow up question is whether the single maintainer of some critical but obscure open source project could also convince the model trainers to commit to RL when they realize the model is horribly mistrained.In Stackoverflow data is trivial to edit and the org (previously, at least) was open to requests from maintainers to update accepted answers to provide more correct information. Editing is trivial and cheap to carry out for a database - for a model editing is possible (less easy but do-able), expensive and a potential risk to the model owner.
by munk-a
2/18/2026 at 3:02:15 PM
I know Claude will read through code from Go libraries it has imported to ensure it is doing things correctly, but I do have to wonder for other languages and those small libraries, if we'll start seeing things like AGENT_README.md a file that describes the project, then describes what functionality is where in the code, and if necessary drills on a source file by source file basis (unless it's too massive - context limits are still limits). In any regard, I could see that becoming more common. Especially if you link to said file from the README.md for the model to go to. ;)by giancarlostoro
2/18/2026 at 2:11:59 AM
I think this can be fixed more generally by biasing towards newer data in model outputs and putting more weight on authoritative sources rather than treating all data the same. So no one needs to go in and specifically single out Go code but will instead look at new examples which use features like generics from sources like Google who would follow best/better practices than the rest of the codebase.by xmprt
2/17/2026 at 9:38:45 PM
[flagged]by jpalepu
2/17/2026 at 7:25:57 PM
They're particularly bad about concurrent go code, in my experience - it's almost always tutorial-like stuff, over-simplified and missing error and edge case handling to the point that it's downright dangerous to use... but it routinely slips past review because it seems simple and simple is correct, right? Go concurrency is so easy!And then you point out issues in a review, so the author feeds it back into an LLM, and code that looks like it handles that case gets added... while also introducing a subtle data race and a rare deadlock.
Very nearly every single time. On all models.
by Groxx
2/17/2026 at 7:54:27 PM
> a subtle data race and a rare deadlockThat's a langage problem that humans face as well, which golang could stop having (see C++'s Thread Safety annotations).
by Jyaif
2/18/2026 at 10:34:36 AM
For Go, there is https://pkg.go.dev/gvisor.dev/gvisor/tools/checklocks. There are some missing things from C++ Thread Safety annotations, but those could be added.by aktau
2/17/2026 at 9:09:29 PM
Go has a pretty good race detector already, and all it (usually) takes to enable it is passing the -race flag to go build/test/run/etc.by kbolino
2/18/2026 at 12:37:23 AM
No language protects from dead lock.by Thaxll
2/18/2026 at 1:10:22 PM
I probably agree that they don't protect you from all deadlocks, but some languages protect you from some dead locks.by Jyaif
2/17/2026 at 8:43:28 PM
You should be using rust... mm kay :\by awesome_dude
2/17/2026 at 11:36:14 PM
Doing concurrency in Rust was more complex (though not overly so) than doing it in Golang was, but the fact that the compiler will outright not let me pass mutable refs to each thread does make me feel more comfortable about doing so at all.Meanwhile I copy-pasted a Python async TaskGroup example from the docs and still found that, despite using a TaskGroup which is specifically designed to await every task and only return once all are done, it returned the instant theloop was completed and tasks were created and then the program exited without having done any of the work.
Concurrency woo~
by danudey
2/18/2026 at 3:57:05 AM
The person I was replying to sounded exactly like the Rust zealots roving the internet trying to convince people to change.by awesome_dude
2/18/2026 at 6:49:01 AM
So you are trying to explain concurrency to the folks who implemented CSP in both Plan9 and Go. Interesting. I should return "cspbook.pdf" back.by anthk
2/18/2026 at 7:10:34 AM
One day, maybe today, you will learn to readby awesome_dude
2/18/2026 at 7:41:26 AM
(eval) rather than (read), then.On concurrency, Go has the bolts screwed in; it basically was 'lets reuse everything we can from Plan9 into a multiplatform language'.
by anthk
2/17/2026 at 8:10:08 PM
Good use case for Elixir. Apparently it performs best across all programming languages with LLM completions and its concurrency model is ideal too.by brightball
2/17/2026 at 9:30:02 PM
This is the exact opposite of my experience.Claude 4.6 has been excellent with Go, and truly incompetent with Elixir, to the point where I would have serious concerns about choosing Elixir for a new project.
by monooso
2/17/2026 at 9:43:13 PM
Shouldn't you have concerns picking Claude 4.6 for your next project if it produces subpar elixer code? Cheapy shot perhaps, but I have a feeling exotic languages will remain more exotic longer now that LLM aided development is becoming the norm.by hbogert
2/19/2026 at 2:38:13 AM
The specific agent is irrelevant. This is related to a broader personal opinion regarding LLMs and language choice.Before we continue, the following opinion comes with several important caveats:
1. It only applies to paid professional work. If it's a hobby project, choose whatever makes you happy.
2. It ignores the strengths and weaknesses of different languages. These may outweigh any LLM-related concerns.
3. This is my opinion today. I _think_ it will survive longer than the next LLM cycle, but who knows these days.
4. May contain nuts.
Okay, that's the ass-covering dispensed with, on to the opinion:
If the choice is between a language which is "LLM friendly" (for want of a better phrase) and one which is not, it is irresponsible to choose the latter.
by monooso
2/18/2026 at 12:01:18 AM
We've finally figured out how to spread ossification from network protocols to programming languages! \o/by majewsky
2/18/2026 at 2:18:15 AM
We live in different realities.Opus and Sonnett practically writes the same idiomatic elixir (phoenix, mind you) code that I would have written myself, with few edits.
It's scary good.
by dimitrios1
2/19/2026 at 2:40:31 AM
I envy your reality.by monooso
2/17/2026 at 5:42:43 PM
I have run into that a lot which is annoying. Even though all the code compiles because go is backwards compatible it all looks so much different. Same issue for python but in that case the API changes lead to actual breakage. For this reason I find go to be fairly great for codegen as the stability of the language is hard to compete with and the standard lib a powerful enough tool to support many many use cases.by robviren
2/17/2026 at 6:02:53 PM
The use of LLMs will lead to homogeneous, middling code.by HumblyTossed
2/17/2026 at 7:46:34 PM
Middling code should not exist. Boilerplate code should not exist. For some reason we're suddenly accepting code-gen as SOP instead of building a layer of abstraction on top of the too-onerous layer we're currently building at. Prior generations of software development would see a too-onerous layer and build tools to abstract to a higher level, this generation seems stuck in an idea that we just need tooling to generate all that junk but can continue to work at this level.by munk-a
2/17/2026 at 8:33:26 PM
But Go culture promulgates this practice of repeating boilerplate. In fact this is one of the biggest confusion points of new gophers. "I want to do a thing that seems common enough, what library are you all using to do X?". Everyone scoffs, pushes up their glasses and says, "well actually, you should just use the standard library, it's always worked just fine for me". And the new gopher is confused because they really believe that reinventing the wheel is an acceptable practice. This is what leads to using LLMs to write all that code (admittedly, it's a fine use of an LLM).by nobleach
2/17/2026 at 8:16:51 PM
LLMs have always been great at generating code that doesn't really mean anything - no architectural decisions, the same for "any" program. But only rarely does one see questions why we're needing to generating "meaningless" code in the first place.by kimixa
2/17/2026 at 8:23:14 PM
This gets to one of my core fears around the last few years of software development. A lot of companies right now are saddling their codebases with pages and pages of code that does what they need it to do but of which they have no comprehension.For a long time my motto around software development has been "optimize for maintainability" and I'm quite concerned that in a few years this habit is going to hit us like a truck in the same way the off-shoring craze did - a bunch of companies will start slowly dying off as their feature velocity slows to a crawl and a lot of products that were useful will be lost. It's not my problem, I know, but it's quite concerning.
by munk-a
2/18/2026 at 12:58:49 AM
The "LLMs shouldn't be writing code" take is starting to feel like the new "we should all just use No-Code."We’ve been trying to "build a better layer" for thirty years. From Dreamweaver to Scratch to Bubble, the goal was always the same: hide the syntax so the "logic" can shine. But it turns out, the syntax wasn't the enemy—the abstraction ceiling was.
by hackerbrother
2/18/2026 at 2:43:43 PM
Where are the amazing no-hassle, no-boilerplate tools from last generation? Or the generation before that? Give me a break: it's easy to post this but it's proven very hard to simply "pick the right abstraction for everyone".by slibhb
2/18/2026 at 12:18:11 AM
[dead]by zer00eyz
2/17/2026 at 6:52:47 PM
It does. I’ve been writing Go for long enough, and the code that LLMs output is pretty average. It’s what I would expect a mid level engineer to produce. I still write code manually for stuff I care about or where code structure matters.Maybe the best way is to do the scaffolding yourself and use LLMs to fill the blanks. That may lead to better structured code, but it doesn’t resolve the problem described above where it generates suboptimal or outdated code. Code is a form of communication and I think good code requires an understanding of how to communicate ideas clearly. LLMs have no concept of that, it’s just gluing tokens together. They litter code with useless comments while leaving the parts that need them most without.
by cedws
2/18/2026 at 12:26:56 PM
I am also of the opinion that LLMs are still pretty bad at what's called "Low level design" - that is structuring functions and classes in a project. I wonder if a rule like torvalds' "No more than 4 levels of indentation" might make them work better.by rdfc-xn-uuid
2/17/2026 at 7:32:48 PM
Do LLMs generate code similar to middling code of a given domain? Why not generate in a perfect language used only by cool and very handsome people, like Fortran, and then translate it to once the important stuff is done?by bee_rider
2/17/2026 at 8:53:55 PM
This might work if Fortran were portable, or if only one compiler were targeted.by pklausler
2/17/2026 at 9:30:59 PM
middling code, delivered within a tolerable time frame, budget, without taking excessive risk, is good enough for many real-world commercial software projects. homogeneous middling code, written by humans or extruded by machines, is arguably even a positive for the organisation: lots of organisations are more interested in delivery of software projects being predictable, or having a high bus-factor due to the fungibility of the folks (or machines) building and maintaining the code, rather than depending upon excellence.by shoo
2/17/2026 at 7:23:24 PM
You might even say that LLMs are not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.by saghm
2/18/2026 at 12:24:24 PM
This is a rob pike reference for the uninitiated: https://news.ycombinator.com/item?id=30688969by rdfc-xn-uuid
2/17/2026 at 6:24:56 PM
I'm not sure if that's a criticism or praise - I mean, most people strive for readable code.by awesome_dude
2/17/2026 at 6:28:02 PM
LLM generated code reminds me of perl's "write-only" reputation.by candiddevmike
2/17/2026 at 7:21:03 PM
Does it really? Because I see some quite fine code. The problem is assumptions, or missing side effects when the code is used, or getting stuck in a bad approach "loop" - but not code quality per se.by coldtea
2/17/2026 at 6:54:52 PM
In all honesty I've only used LLMs in anger with Go, and come away (generally speaking) happy with what it produced.by awesome_dude
2/17/2026 at 8:35:37 PM
For a few years, yeah. Eventually it will probably lead to the average quality of code being considerably higher than it was pre-LLMs.by meowface
2/17/2026 at 7:13:22 PM
[dead]by throwaway613746
2/17/2026 at 9:29:02 PM
I'd prefer we start nuking the idea of using LLMs to write code, not help it get better. Why don't you people listen to Rob Pike, this technology is not good for us. Its a stain on software and the world in general, but I get it most of ya'll yearn for slop. The masses yearn for slop.by dakolli
2/17/2026 at 10:27:42 PM
I totally agree. I read threads like this and I just can’t believe people are wasting their time with LLM’s.by throw432196
2/17/2026 at 10:38:11 PM
The masses yearn to not have to fiddle with bs for rent and foodby whattheheckheck
2/17/2026 at 6:32:11 PM
I definitely see that with C++ code Not so easy to "fix", though. Or so I think. But I do hope still, as more and more "modern" C++ code gets publishedby BiraIgnacio
2/18/2026 at 11:25:03 AM
battle of my life. several times i’ve had to update my agent instructions to prefer modern and usually better syntax to the old way of doing things. largely it’s worked well for me. i find that making the agents read release notes, and some official blog posts, helps them maintain a healthy and reasonably up-to-date instructions on writing go.by yawboakye