Passionate developer in Java and Scala. And sometimes, something else. A few months per year, someone calls me "professor". CoFounder of Scala By The Lagoon @scalagoon
Documentation is written for the developer that is solving a problem: she probably already has an idea of what the solution should look like, and is hunting the details and the specifics of how Azure approaches that solution, and what is needed to make it work.
When learning, you have a completely different perspective, and often you don't have the general concepts needed to understand and navigate all the tools and objects. You may even need content that is not contained in the technical documentation because it is too general or simply doesn't belong there (and it will slow the developer down). That's what courses are for.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Documentation is written for the developer that is solving a problem: she probably already has an idea of what the solution should look like, and is hunting the details and the specifics of how Azure approaches that solution, and what is needed to make it work.
When learning, you have a completely different perspective, and often you don't have the general concepts needed to understand and navigate all the tools and objects. You may even need content that is not contained in the technical documentation because it is too general or simply doesn't belong there (and it will slow the developer down). That's what courses are for.