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.
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.
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.
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.
Well I can also tell you that from years of trying to go straight to documentation: you rarely learn anything. Often the docs are written badly and missing usage examples, so it’s unclear how certain options work. Often the tool you’re having trouble with is one you only use once a month so by the next time you use it you’ve forgotten everything you learned.
Speaking from my experience, in most cases it’s just not worth it. In the few cases where it’s something you use every day, then sure invest some time in the docs.