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.
Problem is docs are often out of date. Either old, or too new if you have to use an older version. So you can spend hours chasing your tail because what the docs and examples say works, doesn’t.
I do agree to start there, but reading the raw code if available is often times the best, and AI can do that much faster if its source available. And ofc it can be wrong in how it “thinks” it should work but so can humans when skimming quickly.
I did say “first”, as in the first place you check and not saying you never have to go elsewhere.
“often” is doing some heavy lifting here. Stack overflow and yes looking at source code are useful tools, but the vast majority of the time, the “stack overflow coders” completely eschewed the official documentation when reading it would have not only provided then the information they needed but also helped then develop an intuition for how a library worked that would have served them much better.
Of course I mostly take issue with the blog presenting the experience of a “stack overflow coder” as a universal experience when it was just the experience of incompetents.