Indeed, AI code is 90% dogshit, even now. Correctness is not "pristine". AI routinely elides newlines, as if it's playing code golf. Massive files which can clearly be refactored, etc.
Studies even show LLMs do better with smaller files, so they're even handicapping themselves.
My favorite talk from Scala Days 2026 was about baking refinement types right into the compiler.
Unlike libraries like Iron or Refined, it adds a built-in solver that verifies logic and math across multiple variables at compile time with zero runtime cost.
Moving from simple checks to full verification is how Scala's type system should evolve to constrain LLMs - AI code won't compile unless the math holds up.
🎤 Speaker spotlight: Win Wang @Winium , founder of ParaQuery, ex-Twitter distributed builds & parallel Scala compilation.
"GPUs for Type Inference and Typeclasses": we love strong types, we hate compile times. Can we throw a GPU at implicit resolution?
🗓️ Mon Oct 19 · SF · 6 days to go
🎟️ Get your ticket: https://t.co/K54RCwwkn2
#Scala #Scala3 #BayAreaScala #SFScala #SanFrancisco #ScalaSummit2026
@stevebauman I thought you were going to say that AI still needs to understand the complexity as well. Higher-level languages would presumably still give us more AI per dollar.
I love it when LLMs matter-of-factly roast their own code, as if they weren't the perpetrator. Just something funny about it.
"The data shows these lists are massively oversized relative to actual usage, wasting 98%+ of their allocated capacity..."
@trq212@Hesamation I find that Claude is really good at making easy-to-read PDFs with graphics. Better than asking it to make pedagogical code.
"Unfortunately", it's still up to us to direct the pedagogy in the output.
@philkellr I still do deep-ish technical work by having design discussions with agents. While there's wait time, do I really want to do the menial work of supervising/noting benchmarks/profiling, or do I just discuss their ramifications? I prefer the latter.
@wangzhr4 Agents sometimes also aim for "insane" (complexity, requirements). Perhaps that also maps to "low standards of how to get it done", but it requires a qualitatively different approach(es).
@fwbrasil@reggieperry Honestly, nothing wrong with that, especially when expanding to broader areas. I love learning from LLMs.
But I'd rather people be upfront about issues/catches.
But blaming your agents for a performance matrix you're endorsing outright?
@wangzhr4 I mean, we could *at least* ask the agents (directly):
1. Why is the comparison bullshit?
2. What dumb things are we doing?
I find that agents will just tell you how they screwed up.
@fwbrasil@reggieperry A CUDA agent literally made a serial queue that a single thread processed while 48k other threads just sat and waited. Amazing design.