Post #1722076
2026-04-27 14:18 UTC
@trentshell @jkb @jneen Even if LLMs, as they get better, create fewer bugs than humans, we’re still bottlenecked by verification and understanding. When writing code, understanding develops naturally, but with LLMs it must be done explicitly. The problem is that their default usage mode doesn’t really encourage this (which is fine for prototyping but not for production).
(One can argue that “dark factories” are the way forward, but I’m not sure how well an organization that doesn’t have knowledge about its systems will fare. It will be constrained by whatever the LLM capabilities of summarizing and modifying the system are at any given point in time, beholden to whoever produced the model. And for sure the organization won’t be able to innovate, as LLM aren’t good at extrapolating outside their training data.)
Replies (1)
-
@jneen@unstable.systems 2026-04-27 14:24
@duarte @trentshell @jkb i tend to think it's bad for prototyping as well! the point of prototyping isn't to have a fully working polished version of the thing, it is to smoke out issues early and increase your own understanding before building the real thing. llms skip all of that!