» What is the best way to learn a new technology? I'm talking about the kinds that come printed like hieroglyphics on the pages of a hefty technical tome. What's the most effective way to assimilate this information? .. to master the technology .. in order to wield its Mojo. Like a Jedi does with his lightsaber.
I read somewhere how the average programmer reads less than one technical book per year. Surprising, no?
What a difference that made! Night-n-day. Suddenly the mojo was mine. No more struggling to figure out why things werent working the way I expected.
That particular title weighed in at a respectable 650 pages. But it contained plenty of fluff. (I actually like that kind of fluff. Another big deal was learning the Unix shell .. for help with VPS server administration. Very powerful. Things that used to take hours, now take minutes.)
I must admit » this thing looks intimidating. Formidable. Daunting. Sometimes I swear it snorts at me.
But heft alone is not my only reason for dismay. Each page comes chock full of technical terms, unwieldy jargon that must be mastered if I am to have any hope of accessing the power it contains.
How I would *love* to upload the contents of this monster (.. into my brain) .. all in one shot. You know, like they do in the Matrix. But that option doesnt seem feasible. So .. we're left with the old, standard method » reading. Ugh.
This is not a mountain, I've come to understand, that cannot be surmounted by sheer enthusiasm alone. I mean, if I could stay awake for a week and power thru this thing, I would. But that aint how it works. (At least, not for me.)
In a strange, counterintuitive way, pure passion actually seems a hindrance here. Because passion brings frustration. More passion » more frustration.
What's required here is not so much passion or enthusiasm, but rather sustained, steady effort. Methodical focus. You know » the tortoise and the hare.