They often go together, as you illustrate well with your comment, I agree that rote memorisation can be a bedrock foundation for any specialty, however it is no

They often go together, as you illustrate well with your comment, I agree that rote memorisation can be a bedrock foundation for any specialty, however it is not necessarily the only foundation. And the thread of my argument here is that it is not as good a foundation as a complete understanding of many topics in an interwoven fashion. An attempt at an analogy; I assume you're familiar with jQuery as that's your nickname so I'll use that. One could memorise every single API method and syntactical quirk of the framework and be rightfully considered a specialist, but this does not innately suggest that they understand the absolute multitude of concepts that are likely to be bought together in a project making use of this specialty, or how the fabric of a jQuery object might be incorporated into a larger project using a full polyglot of development languages and spanning JRuby, Java, Groovy, Scheme, Scala etc. Knowing the underlying concepts that unite them gives a person the ability to solve problems in any one specific area potentially better than someone who had simply memorised all the API documentation for the jQuery framework. Going through the rote memorisation of all these disparate things you're likely to eventually notice the patterns and ideas that they share, but in my opinion this is a backward way of doing things. Starting with patterns and ideas and fleshing out the specifics with reference documentation on a case by case basis has always been my preferred approach, it's much easier to find a base pattern and go through it's iterations than it is to simply memorise all the potential iterations of a given pattern. How easy is it to memorise a table of results on several thousand experiments demonstrating F=ma compared to simply applying F=ma several thousand times? Even more so with something that moves as fast as development; when the framework changes and your memorised documentation needs to be updated, it is much easier to understand the change from the perspective of cause and effect rather than just "here's how it was including all edge cases and implications, and here's how it is now, including all edge cases and implications."