I would credit my relative success (compared with many complaints I’ve read) at building software using AI as a helper to the fact that I’ve already solved the problem in my mind before I prompt the AI, and I tell it how I want the problem to be solved. Generally it’s possible to do that in English much more tersely than it is in code.
So what I’ve done is the hard (in the sense of problem difficulty) work and simply got the AI to do all the typing for me because I just can’t be arsed any more. The typing isn’t the hard part of software development: just the part that, historically, has taken up a massive chunk of my time in the domains I’ve worked it.
I’m not saying this works for everyone in every situation but, as far as I’m concerned, bring it on.
>Generally it’s possible to do that in English much more tersely than it is in code.
I really doubt this is the case for any decent amount of complexity. English is ambiguous. Programming languages exist because we don't want this ambiguity from natural languages. A sufficiently descriptive spec written in English is barely indistinguishable from just code. We've come full circle.
I would credit my relative success (compared with many complaints I’ve read) at building software using AI as a helper to the fact that I’ve already solved the problem in my mind before I prompt the AI, and I tell it how I want the problem to be solved. Generally it’s possible to do that in English much more tersely than it is in code.
So what I’ve done is the hard (in the sense of problem difficulty) work and simply got the AI to do all the typing for me because I just can’t be arsed any more. The typing isn’t the hard part of software development: just the part that, historically, has taken up a massive chunk of my time in the domains I’ve worked it.
I’m not saying this works for everyone in every situation but, as far as I’m concerned, bring it on.