| The problem isn't the AI writing the code, it is the specification - I assert much of the described problems could be rectified by improved specification with no hand coding. Specification of software has been very weak for decades, and little effort has been put towards defining methadologies of specification that are both exhaustive and unambiguous. It is possible, I know because I work in an exotic niche where being exhaustive and unambiguous isnot optional - Functional Safety. Here you might spend 90% or more of your time planning what and how to code, before writing the first line. The cost - I have worked on projects where, across the duration of the project, the average production of code was less than two lines a day. But when a single error could result in the death of 100, or 300, people, then this time worth it. You can't get this kind of quality when you pivot twice a week, you need to have fairly fixed objectives. The are ways to get better outcomes that are known, but not widely applied, and they could do with some development to make them accessible. Some has been done, eg Leslie Lamport and TLA+. But, as you might have been told as a child, don't get upset that you did not get what you wanted when you failed to ask for it properly. |