Ok, I read the article and the Cliff of Confusion is what I thought it was. Besides coding, coding, coding your own projects (which I'd prioritize), you might

Ok, I read the article and the Cliff of Confusion is what I thought it was. Besides coding, coding, coding your own projects (which I'd prioritize), you might also try answering questions on StackOverflow for your chosen stack. Don't be surprised if you're unable to do so at first, especially in burgeoning technologies with many developers competing to establish their reputations, but this (often) forces you to dig into the source code, spelunking your way through and--hopefully--learning good style and architectural practices while coding smaller solutions with a shorter path to completion versus monolithic projects. See the Node standard library, for example. (Also the recipe-type books focus on specific, more practical solutions, instead of long-form tutorials.) If that doesn't suit you, keep trying other things--there are many sort of "katas" you can do. P.S.: I thought asdfppp's (now dead) comment was helpful.