3 ms·
No, it's not about stuff you know. This was posted recently, but it was so good it's worth repeating: http://blog.robertelder.org/50-interviews-with-facebook-
by TheOtherHobbes 10y ago
No, it's not about stuff you know.
This was posted recently, but it was so good it's worth repeating:
http://blog.robertelder.org/50-interviews-with-facebook-twitter-amazon-others/ http://blog.robertelder.org/50-interviews-with-facebook-twit...
The interesting point is the distinction between skill and talent.
Skill is close to competence. You can solve well-defined problems using standard tools and practices.
Talent is close to proficiency. You can not only improvise good solutions for novel problems, but you can also prioritise problems intelligently to achieve strategic goals, because you have a clear view of how the codebase fits into your business or project.
Without talent you can waste a lot of time by picking the wrong tools, or using tools in the wrong ways. Even though your code may be perfectly correct, the solution built with the code can still be completely wrong or useless.
In fact talent is somewhat orthogonal to skill. You can have an untrained version of that overview talent, but it's not so useful if it isn't grounded in skill.
When you have both, you have real proficiency - good code doing the right things to solve the right problems.
- encoderer 10y ago> Talent is close to proficiency. You can not only improvise good solutions for novel problems, but you can also prioritise problems intelligently to achieve strategic goals, because you have a clear view of how the codebase fits into your business or project. Calling that aspect talent and not just another skill is somewhat elitist I think. It can be learned. It's just another skill. (Haven't read the link.)
- mod 10y agoThat's just skill and superior skill. Both require you to know stuff. And in programming, skill is just knowing more stuff (knowing how to apply things). In other trades, skills might be swinging a hammer well or being able to chop potatoes really quickly.
- rabidrat 10y agoI think you're splitting hairs. The parent and OP are saying there is a qualitative difference, and by saying "just X and better X" you're trying to say that the difference is merely quantitative. In my experience, when someone makes a claim of qualitative difference, and someone else insists that the difference is merely quantitative, it's because the latter person has not themselves seen the quality of the difference. This applies in many fields. And that's compatible with my personal understanding here as well. As someone who has been programming for 30+ years and is generally considered proficient, I agree with the parent that the difference is qualitative. This explains a lot of the times when I look at what senior developers are doing and think "yes, that tool is generally useful, but not this time". And it gets frustrating then when they start arguing about "best practices" but I'm trying to make a larger point about "this project".
- mod 10y agoYou make a good analysis, and I don't disagree with you. The crux of my argument is more like this: Programming is a knowledge field, so any proficiency is just deeper know-how. "Stuff you know." Is that quantitative? Not exactly. I certainly don't think someone who knows 50 languages is a better programmer than someone who knows 2 languages, by virtue of the quantity. Some things are memorization: how to write a class, for instance. And some things are not: how to model a situation into an appropriately-designed class. One requires application of knowledge, I guess you could say. Qualitative. But you can't apply your knowledge of different class designs without knowing why they're appropriate. That's not purely qualitative. Am I splitting hairs? At this point, probably. I just think the arguments I responded to are poorly worded. Yours is not, and I can't disagree with it.