2 ms·
> 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.
by 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.