This absolutely isn’t how humans learn. Humans learn by doing. Once you grasp the basics, you can read some documentation. Otherwise there’s not enough ground for the docs to make sense.
Once you’re comfortable with the basics by all means read the table of contents to know what you don’t know. I recommend this especially when dealing with databases, it’s amazing how many people never advance past the apprenticeship part of learning software engineering.
> This absolutely isn’t how humans learn. Humans learn by doing.
That depends on both the subject and the person. Some learn better by understanding the fundamentals first. Some subjects (in CS/SE as well) might not even be approachable without it.
The way dosco189 is using GPT is perfectly fine. They aren't letting GPT do all the work for them, they're letting it explain how concepts relate to each other, something you often will not find in the documentation.
Also documentation is, how to say, heavily styled in a sense.
If you disliked a certain teaching style before you were basically screwed. I've learned some languages purely because the documentation was fun for me personally.
100% agree. Back circa 2010-2011, Apple’s obj-c documentation held back my iOS coding career. Coming from javadocs, I just couldn’t wrap my head around apple’s style.
Once you’re comfortable with the basics by all means read the table of contents to know what you don’t know. I recommend this especially when dealing with databases, it’s amazing how many people never advance past the apprenticeship part of learning software engineering.