• 0 Posts
  • 10 Comments
Joined 3 years ago
cake
Cake day: July 24th, 2023

help-circle


  • reasonably well

    hmm not in my experience, if you don’t care about code-quality you can quickly prototype slop, and see if it generally works, but maintainable code? I always fall back to manual coding, and often my code is like 30% of the length of what AI generates, more readable, efficient etc.

    If you constrain it a lot, it might work reasonably, but then I often think, that instead of writing a multi-paragraph prompt, just writing the code might’ve been more effective (long-term that is).

    plan it correctly and the actual implementation of the correct plan will take no time at all.

    That’s why I don’t think AI really helps that much, because you still have to think and understand (at least if you value your product/code), and that’s what takes the most time, not typing etc.

    it‘s just different.

    Yeah it makes you dumber, because you’re tempted to not think into the problem, and reviewing code is less effective in understanding what is going on within code (IME, although I think especially nowadays it’s a valuable skill to be able to review quickly and effectively).





  • The problem though (with AI compared to humans): The human team learns, i.e. at some point they probably know what the mistake was and avoids doing it again. AI instead of humans: well maybe the next or different model will fix it maybe

    And what is very clear to me after trying to use these models, the larger the code-base the worse the AI gets, to the point of not helping at all or even being destructive. Apart from dissecting small isolatable pieces of independent code (i.e. keep the context small for the AI).

    Humans likely get slower with a larger code-base, but they (usually) don’t arrive at a point where they can’t progress any further.