That right there is complete rubbish. (Aside from the amount of energy wasted by 'AI'...)It is a waste of time or energy to write every line of codes when you can let AI first write it and go through it to perfect them. Work smarter, not harder.
People seem to think coding is just 100% writing algorithms; it isn't. You have to structure your work based on the requirements of the project. You can't tell an LLM everything it needs to do the work of a human, and if you think you can, then you shouldn't be coding anything.
If I'm writing a testing framework I have to decide whether I'm using JUnit or TestNG. I decide how to read in test config; do I use JSON, XML or properties; can they be overridden on the command line?
Am I testing web pages? Should I use Selenium? Do I support Firefox, Chrome, Edge and remote?
Am I writing API tests? Should I use RestAssured?
Am I connecting to a database to retrieve data and check changes to that data? What's the type of db? What are the tables called? What are the column names? What relevant SQL statements do I need to use to access the data?
Right, I've made those fundamental decisions. How do I tell the LLM when I'm testing a webpage that on page C clicking the "Back" link on the page (not the web browser's back button) should go to page A and not page B? How do I tell it to add five addresses with the start and end dates that I lived there over the past 20 years, but leave a five-year gap so I can see an error when I try to continue?
How do I tell it to validate a UK driving licence number without having to tell it the intricacies of that? (Like how the number always has a "9" at position 14? And how, if you're female (how do I tell it you're female?), the month number has 50 added to it, so "03" becomes "53"?) It's quicker for me to write that than for me to let an LLM write it and make me check its work.
I'm a Java developer, not a Java code checker for an LLM's output.
I started a new job three months ago. I came in and created a test framework, and expanded their automation testing from 20 tests that took 20 minutes to run, to almost 600 that run in 15 minutes.
Here's another example of why LLMs are crud. As part of my investigations into whether 'AI' would be helpful in my work, I tried to get an 'AI testing tool' to add a new test for a phone number that was changing from 555-123-4567 to 555-987-6543. It recognised there was already a test checking the phone number. It copied the existing test and added a comment, then did a global find & replace on the phone number, resulting in two tests doing exactly the same thing. And, because of the find & replace, the comment in the test said: "'AI testing tool name': Added test: Make sure phone number is changed from 555-987-6543 to 555-987-6543".
Yeah, really helpful.
If I ever interview someone with your attitude to writing code (not "codes"), you would not get the job.