I think people assume the AI code goes first, but it’s not really like that.
I just busted out a half day of coding. Really impressive stuff for my standard and was just in flow with little optimisation breakthroughs popping in my head as I made it through. Output looks great, all working as expected, documented and commented my new things in case I forget them later or want to explain them to the team.
But later, I’ll probably run it through a model real quick and expect at least one change, usually around tidying things up or an opportunity to optimise a block here or there a bit more. Basically tighten up any loose screws or be pointed to big obvious things I somehow missed.
Really, I think that’s how most devs are making use of it. It can be frightening the shit LLMs come up with starting for scratch (that goes with anything), or even 60-70%. Doesn’t matter how good the prompts are, at the end of the day, it’s relying on Frankencode sourced from all over the place to apply solutions. It has no consistent and familiar, style, logic, or “accent” in its language. But if it’s got an established and detailed base, concept, and direction (such as a mostly completed chunk of code), frequently enough it’ll assist well with finding dumb shit.
It’s like a final phase thing, to get you beyond, “It seems work work well; good enough.” to “It’s definitely working well. This is done for now.”
I like to think that’s what’s going on here because anyone with even moderate developing knowledge/skill/experience totally sees just how bad LLMs are at coding.
I think people assume the AI code goes first, but it’s not really like that.
I just busted out a half day of coding. Really impressive stuff for my standard and was just in flow with little optimisation breakthroughs popping in my head as I made it through. Output looks great, all working as expected, documented and commented my new things in case I forget them later or want to explain them to the team.
But later, I’ll probably run it through a model real quick and expect at least one change, usually around tidying things up or an opportunity to optimise a block here or there a bit more. Basically tighten up any loose screws or be pointed to big obvious things I somehow missed.
Really, I think that’s how most devs are making use of it. It can be frightening the shit LLMs come up with starting for scratch (that goes with anything), or even 60-70%. Doesn’t matter how good the prompts are, at the end of the day, it’s relying on Frankencode sourced from all over the place to apply solutions. It has no consistent and familiar, style, logic, or “accent” in its language. But if it’s got an established and detailed base, concept, and direction (such as a mostly completed chunk of code), frequently enough it’ll assist well with finding dumb shit.
It’s like a final phase thing, to get you beyond, “It seems work work well; good enough.” to “It’s definitely working well. This is done for now.”
I like to think that’s what’s going on here because anyone with even moderate developing knowledge/skill/experience totally sees just how bad LLMs are at coding.