however the lack of practical examples to go with it made it a bit difficult when i tried some code work
Anthony’s teaching style isn’t coding an actual project from start to finish (though in the later chapters, he may do a simple application walk-through, a very simple bare-bones application again just to review the concepts).
His style is more: Introduce and explain a concept, explain that concept using the simplest demo code, Run and step into the code line by line, explaining how it works, and using the code’s output as proof that the concept works the way he explained it.
I find the side-trip “Asides” he have in his course to be very helpful and important (where he explains a term, or phrase, or a “big word”) before he tackles the main concept he wants to explain.
Sometimes I have to replay a chapter several times, to really get it. Sometimes I have to skip a chapter, and just come back later to it to take a break.
And of course, having your editor open and going along and trying out the same concepts ingrain into your head what he’s trying to explain. Also helps if you do “what if I do this” in your own code… and experiment.
Personally, I find other instructor’s style of coding a project from start to finish to be boring… not unless the project he’s building is also the same project I need to build, then I can just copy his code… and therefore, I’m not learning as much. I feel like a monkey just copying… then when it’s time to code my own project, It’s hard to get started.