lysdexic comments on Am I learning, or am I just prompting?

Am I learning, or am I just prompting? (techhub.iodigital.com)

submitted 2 months ago by codeinabox@programming.dev to c/programming@programming.dev

27 comments fedilink hide all child comments

Recently I gave my first ever presentation at iO. It was about what it actually feels like to be a junior developer in a world where AI is just always there. This is a write-up of that talk, including what the room said back.

[–] iamtherealwalrus@lemmy.world 0 points 2 months ago (5 children)

Is that because you didn’t bother to read the documentation before using product X, and now you encountered some issue because you used X incorrectly?

permalink

fedilink

source

parent

hideshow 5 child comments

[–] hirihit640@sh.itjust.works 5 points 2 months ago (3 children)

After years of using SO, then years of going to docs first, I've started going back to SO. It just tends to be faster. You can find a question that is 90% similar to yours, rather than piece together scattered bits of information across pages and pages of docs.

permalink

fedilink

source

parent

hideshow 3 child comments

[–] iamtherealwalrus@lemmy.world 0 points 2 months ago (2 children)

I agree you can find an answer quickly on SO. And you can find it even faster by asking an AI. But you will not have learned much, if anything, by copy/pasting the answer. As opposed to reading the documentation, which might have taught you how to solve similar issues in the future.

permalink

fedilink

source

parent

hideshow 2 child comments

[–] lysdexic@programming.dev 1 point 2 months ago

But you will not have learned much, if anything, by copy/pasting the answer.

Your ignorance is showing. The whole point of using SO to help troubleshoot problems is avoiding the troubleshooting stage and all the iterative work of cross-checking docs with parametric tests. The main deliverable of SO is not a magical code snippet but a root cause analysis on a particular failure. You end up with a nice summary of someone else's prior work troubleshooting the same issue, and a clear indication that X causes Y because of Foo.

And you do not get that by reading official docs documenting the happy flow. You'd know that if you had any relevant experience developing software.