4 ms·
I don't, for the most part. The trick that I've found is to understand the underlying theory and don't sweat the individual syntaxes or design patterns. The new
by falcolas 12y ago
I don't, for the most part. The trick that I've found is to understand the underlying theory and don't sweat the individual syntaxes or design patterns. The new platforms of today have a lot in common with the platforms of yesterday. The state of the art languages of today are combining theory and technology which has existed for decades. Tomorrow's Joomla will be doing things in a way very similar to yesterday's Wordpress.
For example, if you understand event driven workflows, you'll be able to pick up react/flux, desktop UI drivers, and video game addons. If you understand continuations (and the various ways to abstract away continuations), you can grok most of Javascript (and by extension, Node.js). If you understand pointers, you'll be able to follow C (though I'd also recommend learning some Assembly as well to really understand C). Pattern matching will get you Haskell and Erlang. And if you can use Google well, everything else is a search away.
Now it is important to note that theory will never make you an immediate expert at every language and platform. However, it does let you bootstrap yourself into a language or framework quickly enough that outsiders will hardly be able to tell the difference.
I've found that once I understand the flow of a program, and ideally the theory driving that flow as well, the syntax required to express the changes you want to make to the flow is merely a few Google searches away.
Another thing to note, if you bounce around like this, you will never get true mastery over a particular language or framework. This is OK for more than 80% of the work you do, but you will end up picking up more information about one language over another - of one framework over another - simply to complete your work. Having this depth of knowledge is not even remotely a bad thing, so long as you keep sight of the bigger picture: don't let the quirks of one language or framework constrain your thinking for all languages.
- eropple 12y ago> Another thing to note, if you bounce around like this, you will never get true mastery over a particular language or framework. I think this is a bit unfair. I find myself rapidly getting to the point of expertise where other people start asking me questions, just because I didn't have to spend time going from "dumb newbie" to "intermediate"--but being able to start at "intermediate" because of the built-up knowledge of everything in my back pocket. Part of it's also that I recognize that technical mastery is mostly just being able to Google faster and better than the next guy, but still. We're short a letter in English for what I really mean, but there are I-shaped people and T-shaped people--what about U-shaped people? Building on multiple sources of knowledge to join them at the top? =)
- falcolas 12y agoThat's a fair assessment (and it mirrors my experience as well), but in the context of my comment, I consider mastery to be a level of knowledge and experience exponentially above the expertise which you refer to. Mastery of a language, to me, is an innate understanding not only of the language, but of its behavior under most circumstances. Mastery is being able to look at a core dump and be able to identify the cause as GCC exploiting undefined behavior to optimize code, and you can fix it with these keywords or compiler arguments. Mastery of a theory is not only understanding its benefits and complexity, but its shortcomings and knowing how to compensate for them. Mastery of sorting algorithms is knowing when a bubble sort is more performant than a binary sort, and knowing how to determine when to use one over the other. Mastery is the act of pushing up against the edge of all human understanding of a particular topic.