I recently found Opus is pretty good at consolidating very-similar-but-different codebases.
Sure, I had to tell it to so, but it trudged through and did it fairly independently… Was especially nice as refactoring test infrastructure code isn’t always very exciting…
I can’t help but think that Anthropic somehow trained on proprietary data too.
Twice, I’ve asked it about a niche almost undocumented hardware register and it told me about fields that aren’t published anywhere…
Your first response is probably that the LLM inferred from public header files or sample code — except this is a really niche thing, there is only one reference implementation published by the manufacturer, only one specification document, and neither ever mentioned these undocumented fields… And if I ask it about the source, it will claim it was an error and these things don’t exist…
A natural assumption would be that it was hallucinated — but sure doesn’t seem like it.
It all went downhill after USTAR format. Of course, BCD encoding of sizes was a choice.
I’m damn convinced cpio never took off because the CLI tool’s syntax is a horrible abomination… Picking “-i” to EXTRACT is wild. Not being able to archive a directory tree without 3rd party assistance seems a bit much, even for the UNIX philosophy…
I tried running one of the Qwen 3.8 models locally. Asked it to code a simple thing. It pontificated on its place in the universe and then asked me what I want it to actually do!
Claude would have written, documented, and unit tested the thing on the first shot…
I want to run local models, but if this is the current state, it’s hard to mentally justify the hardware expense to only get this…
why waste time say lot word, when few word do trick.
reply