100 % test coverage and 100 % correctness are very different things, especially if the tests are auto-generated by LLMs at a rate that is impossible to properly review.
Every coder trying to justify their jobs brings that up. And they’re all wrong.
You don’t do 100% correctness already. In terms of correctness, LLMs generating code with 100% coverage will run circles around whatever you do write today. Demonstrably.
You don’t have the winning argument you think you do. You may want to re-read the parable of John Henry.
Feel free to support the argument that something less than 100% coverage paid for at the cost of electricity instead of the cost of human labor is somehow inferior to the alternative.
There’s as big a difference between “programmer” and “computer scientist” as there is between minor league and major league professional sports athletes. The folks trudging through life who were C-average students generally don’t understand what it takes to do Grade-A work and they certainly don’t put in anywhere close to the level of effort required. If competence were in greater supply, there’d be fewer Enrons. So, let’s be serious about the real capabilities of the average journeyman coder for a minute.
And that’s before we consider the exponential rate at which LLMs are getting better at getting better.
Face it, kiddo. 100% code coverage is now the bare minimum for any new project that wants to call itself “professional grade”. Anything less is an unserious hobby project. Direct your attention at the CVE remediation list for any major project if you need help understanding why. Stare at those graphs as long as it takes for you to understand the new reality you’re living in.
Nobody mourns the out of work ice carvers that the advent of refrigeration caused. The history of automation in the automotive industry has a lot to teach anyone interested in gaining insight useful for grappling with this new technology.
If you express childishly naive ideas you can’t justify or support, don’t be shocked when the person with decades of experience clocks your inexperience with the subject they’ve spent a couple decades mastering.
Your first mistake was thinking you were an equal participant in this conversation. This is the third time I’ve said as much, yet you still persist in the delusion that what you have to say matters more than what you could be learning if you were honest about where you are in your learning.
Thank you for confirming that you’re still making incorrect assumptions.
If you understood what I wrote, you’d realize that I didn’t do the thing you’re accusing me of. You just didn’t understand what I wrote. Your misunderstanding is not my error.
100 % test coverage and 100 % correctness are very different things, especially if the tests are auto-generated by LLMs at a rate that is impossible to properly review.
Every coder trying to justify their jobs brings that up. And they’re all wrong.
You don’t do 100% correctness already. In terms of correctness, LLMs generating code with 100% coverage will run circles around whatever you do write today. Demonstrably.
You don’t have the winning argument you think you do. You may want to re-read the parable of John Henry.
I did not claim that humans without LLMs are better at any of this.
The only thing I challenged is your claim that AI generated 100 % coverage is the solution to the problem of increasingly rapid exploit discovery.
I did not even dispute that AI based tooling can be a part of the solution; just not THE solution via ONLY this one specific mechanism.
Feel free to support the argument that something less than 100% coverage paid for at the cost of electricity instead of the cost of human labor is somehow inferior to the alternative.
There’s as big a difference between “programmer” and “computer scientist” as there is between minor league and major league professional sports athletes. The folks trudging through life who were C-average students generally don’t understand what it takes to do Grade-A work and they certainly don’t put in anywhere close to the level of effort required. If competence were in greater supply, there’d be fewer Enrons. So, let’s be serious about the real capabilities of the average journeyman coder for a minute.
And that’s before we consider the exponential rate at which LLMs are getting better at getting better.
Face it, kiddo. 100% code coverage is now the bare minimum for any new project that wants to call itself “professional grade”. Anything less is an unserious hobby project. Direct your attention at the CVE remediation list for any major project if you need help understanding why. Stare at those graphs as long as it takes for you to understand the new reality you’re living in.
Nobody mourns the out of work ice carvers that the advent of refrigeration caused. The history of automation in the automotive industry has a lot to teach anyone interested in gaining insight useful for grappling with this new technology.
This is a very efficient way to completely remove the motivation of the person you were talking to to continue the discussion.
If that was your goal, congratulations on your win.
If you actually wanted to exchange ideas on a good faith basis, sorry for your loss.
If you express childishly naive ideas you can’t justify or support, don’t be shocked when the person with decades of experience clocks your inexperience with the subject they’ve spent a couple decades mastering.
Your first mistake was thinking you were an equal participant in this conversation. This is the third time I’ve said as much, yet you still persist in the delusion that what you have to say matters more than what you could be learning if you were honest about where you are in your learning.
They’re pointing out the issue is volume.
A person only hitting 60% is gonna get caught in review. A machine doing the same will get lost in a torrent
I understand what they’re pointing out. It’s the wrong thing to fixate on.
A very common cognitive bias in humans is that we tend to over-estimate our own ability and under-estimate things we have limited expeerience with.
The decision to assume I don’t understand what I’m talking about is based on incorrect assumptions about both of us.
If you understand the issue being discussed is volume, then don’t immediately cut to a different track
Thank you for confirming that you’re still making incorrect assumptions.
If you understood what I wrote, you’d realize that I didn’t do the thing you’re accusing me of. You just didn’t understand what I wrote. Your misunderstanding is not my error.