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.
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.