> More important than specific factual knowledge, you need two things: strong conceptual models for whatever you're doing and tacit knowledge

And the more experience with computers I get, the more I realize that there's actually not that many pure unique and mutually orthogonal _concepts_ in computer science and software engineering. Yes, a competent engineer must know, feel, live these concepts, and it takes a lot of work and exposure to crystallize them in the brain from all the libraries, books, programs, architectures one has seen. But there's not a lot of them! And once you are intimate with all of them, you can grok anything computer-related quickly and efficiently: because your brain will just wuickly find the "coordinates" of that thing in the concept space, ans that's all you'll have to understand and recall later.