Translation: As the number of bugs per line of code is a constant depending on language and project, we will experience a world full of bugs now that LLMs generate so much more code. On the other hand, LLMs are so quick at fixing them, the number of bugs should go down.
I wonder which trend will be winning though. I personally won't bet on quality.
> Good software will be good-er. Bad software will be nightmare fuel.
We are talking about a moving target here ... they get better every few months, so I expect the super-LLMs from 2035 will write amazing code even with sloppy prompting.
I think bad software has the possibility of redemption with rewrites and re-engineering efforts. For those of us who are license locked that's probably never going to benefit us :(
Bad software, as in stateless programs, doesn't actually matter and never did. They can be replaced trivially.
The problem is the real world isn't made of stateless programs, but lots of important data in bespoke formats/schemas, and if you change the shitty software that interacts with the important data, in the wrong way, you can lose everything.
It's going to be 50% less buggy, but we're going to write 10x as much code too.
Translation: As the number of bugs per line of code is a constant depending on language and project, we will experience a world full of bugs now that LLMs generate so much more code. On the other hand, LLMs are so quick at fixing them, the number of bugs should go down.
I wonder which trend will be winning though. I personally won't bet on quality.
Good software will be good-er. Bad software will be nightmare fuel.
> Good software will be good-er. Bad software will be nightmare fuel.
We are talking about a moving target here ... they get better every few months, so I expect the super-LLMs from 2035 will write amazing code even with sloppy prompting.
I think bad software has the possibility of redemption with rewrites and re-engineering efforts. For those of us who are license locked that's probably never going to benefit us :(
bad software will be replacable.
Bad software, as in stateless programs, doesn't actually matter and never did. They can be replaced trivially.
The problem is the real world isn't made of stateless programs, but lots of important data in bespoke formats/schemas, and if you change the shitty software that interacts with the important data, in the wrong way, you can lose everything.
Time-to-fix is lower, but time-to-new-bug is also lower