Well, to be honest it's kind of like that 90% of the time. You don't actually become more productive but end up cleaning trash most of the time. Anyway, the hardest part is connecting all the pieces properly and understanding how everything fits, handling edge cases, and so on. Writing the code itself is actually the easy part.

[–] SpaceNoodle@lemmy.world 18 points 2 months ago (1 children)

That's all part of writing it. Typing gibberish you don't understand or that doesn't work doesn't count.

[–] b0ber@lemmy.world 6 points 2 months ago (2 children)

Not necessarily, even before having all these models, I spent most of my time thinking rather than coding. The coding part is just the final nail, that's my approach at least.

[–] atopi@piefed.blahaj.zone 3 points 2 months ago

Isnt the thinking part of the coding?

[–] ignotum@lemmy.world 1 points 2 months ago (1 children)

Same here really, i plan the structure, then have ai throw it together, then i clean up and build off of that

I can't say i particularly miss writing the mindless boilerplate stuff

[–] IcyToes@sh.itjust.works 1 points 2 months ago (1 children)

Surely missing that process, you forget error handling. As you write, its consistently, what if this is null, what if the input is like x. There are many questions you should ask yourself and if you AI it, you'll forget.

[–] ignotum@lemmy.world 1 points 2 months ago* (last edited 2 months ago)

In my experience, the ai generate code has better error handling than code i write myself

I'm lazy so i only write if it's important (and i think of it), the AI is less lazy and often codes quite defensively in my experience