I get the whole “we don’t have to read the code anymore” Schtick from most product devs, and DHH I guess is at his core a builder / product dev whatever.
But the development of something like rails pushed forward the state of the art in ways that LLMs now replicate.
The point being like - someone has to keep writing programming languages and frameworks and libraries. Like - someone has to be thinking what the code looks like for LLMs to have patterns to match against, right?
> someone has to be thinking what the code looks like for LLMs to have patterns to match against, right?
Assuming no new paradigms on the hardware side that no longer fit into our current programming models, do they? Rails' claim to fame was eliminating "XML sit-ups" to improve the developer experience, but who cares how many "sit-ups" LLMs need to do?
At large enough scale, I suspect it'll become a problem. At the moment part of the appeal is how effortlessly models absorb menial work, but I do wonder if eventually it'll be too wasteful at large scales to sustain it. Maybe not, though.
mikgp · · focus · HN ↗
But the development of something like rails pushed forward the state of the art in ways that LLMs now replicate.
The point being like - someone has to keep writing programming languages and frameworks and libraries. Like - someone has to be thinking what the code looks like for LLMs to have patterns to match against, right?
win311fwg · · focus · HN ↗
Assuming no new paradigms on the hardware side that no longer fit into our current programming models, do they? Rails' claim to fame was eliminating "XML sit-ups" to improve the developer experience, but who cares how many "sit-ups" LLMs need to do?
steve_adams_86 · · focus · HN ↗
At large enough scale, I suspect it'll become a problem. At the moment part of the appeal is how effortlessly models absorb menial work, but I do wonder if eventually it'll be too wasteful at large scales to sustain it. Maybe not, though.