it’s getting to the point where I notice people say it a lot, especially IRL now for whatever reason recently.

And for clarity I’m not in research or anything, so these people just mean ‘LLM/image gen’, not utilities like OCR or (usually not) transcription.

Some have argued it’s just more efficient (which I can kind of get), while others think you’re actively hindering your intelligence somehow.

On the first point:

I’ve tried it occasionally to see how it compares to my own skill, and while it produces a functional result, it’s always very derivative work to the point where you can find things with the exact same names of other ‘public’ (but not libre) works, and often isn’t the ideal solution to what it targets. So I can see how you can get things out of it, but it never felt really that profound to me.

But for the second… isn’t this supposed to be the tool for people to do things they aren’t experienced in? If anything, you probably need to be able to understand how to write pertaining to the task so the token probabilities are biased toward writing from that area.

And even then, if all you end up doing is prompting AI, then wouldn’t you ultimately serve no purpose outside of being glorified QA?

I guess I’m trying to figure out what exactly non-users would be ‘falling behind’ in that affects them more than those who use AI?

  • ZILtoid1991@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    11 hours ago

    FOMO, and the temptation of being able to get the speed of AI without the drawbacks of “vibe coding”.

    Reality is much more nuanced.

    You can get a massive boost in your productivity if you use dependencies or just steal code, compared to writing everything from zero. I personally just reuse my own code snippets, and even started to put regularly reused code into their own libraries (next up is to make stuff for parsers).

    I also seen cases, when “AI assisted” coding had the same amount of issues as fully vibe coded stuff, as the person really wanting to cram the chatbot into their workflow did that trusted Grok too much with understanding the documentations, so he just ended up trying to implement stuff based on Grok’s summary, which was wrong at places.

    If you ask: artists also sometimes fall for this trap, though much less often.