Re:I used Fable to rewrite 65kLoC of Go in Rust. It cost $400
by metaltyphoon on Tuesday September 01, 2026 @05:39PM
(#49528617)
Why are you just pasting LLM answers :(? I see this constantly in Slack DMs to every day from work. It hurts
Re:I used Fable to rewrite 65kLoC of Go in Rust. It cost $400
by aka-rider on Tuesday September 01, 2026 @06:08PM
(#49528915)
This is genuinely how I write :'(
It is probably because I read tons and tons of LLM output.
Re:I used Fable to rewrite 65kLoC of Go in Rust. It cost $400
by orwin on Tuesday September 01, 2026 @06:26PM
(#49529076)
It's ok, it is slightly llm-like but not in the worst way, like it was edited after. You aren't Claude at least.
Re:I used Fable to rewrite 65kLoC of Go in Rust. It cost $400
by aka-rider on Tuesday September 01, 2026 @07:16PM
(#49529594)
>You aren't Claude at least.
I absorbed so many different models at this point :)
Thank you for the kind words.
Re:I used Fable to rewrite 65kLoC of Go in Rust. It cost $400
by tensegrist on Tuesday September 01, 2026 @06:16PM
(#49528985)
this is not llm writing. there's no need to startle at the sight of an em-dash
Agents are actively destroy QA gates in many ways, usually by cheating ("the test is buggy, not my changes" — changes the test), or just rot QA slowly by writing buggy overcomplicated tests
What works for me 10/10 is fuzzing and my own constant usage. For this project specifically (text editor), I asked LLM to create human-like fuzzing session, it sends keystrokes like: "the user is searching for a file, editing, <ordering a lizard>, saves changes".
On top of it, I run https://mutants.rs/ which is kind of tests fuzzing. It flips random switches in the app itself, and if tests are silent - they missed a bug.
The downside of this, is I usually find bugs after 1-2 hours of running. I use local Qwen to babysit these sessions, to make initial investigation, a repro case, and file a ticket.