Live data from Hacker News

On Being a Generalist

flaviocopes.com

91–100 of 140 posts

Re: On Being a Generalist

#91
post #35

Earlier quoted context omitted.

Indeed, and given the costs to become the very best, it's often a choice like this. Say you need to hire athletes with in experience swimming, running, and gymnastics to design some classes for your school. Would you rather hire: - 3 gold medal Olympians, each of whom have medaled in the 3 areas - 1 bronze medal Olympian who has single-handedly medaled in swimming, running, and gymnastics?

Let's not fool ourselves into thinking being bronze level is what it means to be a generalist. That's still performing at an unbelievably high level.

It’s an analogy.

Re: On Being a Generalist

#92
post #8

Often we cherish specialists quoting "Jack of all trades, master of none". Curiously enough, the full version of the original has a twist: “A jack of all trades is a master of none, but oftentimes better than a master of one." https://www.theodysseyonline.com/7-phrases-youve-been-misquo...

Just because information is conflicting and different doesn’t mean it’s truer than your first exposure.

No evidence for that etymology.

Re: On Being a Generalist

#93
post #8

Often we cherish specialists quoting "Jack of all trades, master of none". Curiously enough, the full version of the original has a twist: “A jack of all trades is a master of none, but oftentimes better than a master of one." https://www.theodysseyonline.com/7-phrases-youve-been-misquo...

I prefer "jack of all trades, master of learning".

Re: On Being a Generalist

#94
This article is wildly wrong because effort and skill is non-linear.

I can be in the 90th percentile in a handful of areas if I'm a talented generalist. The effort needed after a certain point becomes exponential.

Truly, what is the difference between a React developer and a developer who can use React well? The latter can ALSO use other things? Under this framing, who would want to be the specialist?

And also, as others have mentioned, Google strongly prefers generalists for both practical and philosophical reasons. Internal mobility is high and they're just scooping up talent because they have more work than people. They often hire into a pool that is then matched to a team later. There is a reason their primary job posting is 'Location - Software Engineer'. They can't know what you'll do, so you must be good or learnable at everything. Finally, from a philosophical standpoint, strong generalists are cross-functional within their field and that's generally valued.

Re: On Being a Generalist

#95
post #8

Often we cherish specialists quoting "Jack of all trades, master of none". Curiously enough, the full version of the original has a twist: “A jack of all trades is a master of none, but oftentimes better than a master of one." https://www.theodysseyonline.com/7-phrases-youve-been-misquo...

There is another aspect that is relevant, and that is that the effort needed to get to the 99th percentile of some ability is way larger than that to get to the 90th, and often, you can do very well with just being in the 85th. So you can become pretty good at many different (often complementary) things, in ways that likely make you way more effective than that guy who's a guru in a very specific topic. Then again, s…

Also, being somewhat skilled in many things can give you enough knowledge to know which to use and when to learn more.

Re: On Being a Generalist

#96
Knowing only React, or one programming language doesn't make you a specialist. It just means you have very little knowledge and/or experience. What's next? "if statement developer"?

Software engineering as a whole, is one specialization. Maaaybe backend vs fronted could be made into two meaningful specializations. Or "distributed systems", "game development", "financial systems" etc areas. But not one framework/ PL. Come on. :D

I don't want to bash on people who actually only know one language/framework. It's OK, it can pay your bills, etc. Maybe you also have great skills and interests in non-software areas. But just don't fool yourself thinking "I'm a React specialist".

Re: On Being a Generalist

#97
post #8

Often we cherish specialists quoting "Jack of all trades, master of none". Curiously enough, the full version of the original has a twist: “A jack of all trades is a master of none, but oftentimes better than a master of one." https://www.theodysseyonline.com/7-phrases-youve-been-misquo...

My ex liked to point out, “Curiosity killed the cat, but satisfaction brought it back.”

Re: On Being a Generalist

#98
post #96

Knowing only React, or one programming language doesn't make you a specialist. It just means you have very little knowledge and/or experience. What's next? "if statement developer"? Software engineering as a whole, is one specialization. Maaaybe backend vs fronted could be made into two meaningful specializations. Or "distributed systems", "game development", "financial systems" etc areas. But not one framework/ PL.…

You are a specialist if that's the only thing you're doing. And such a word becomes meaningful once you're doing it +3 to +5 years, IMO. I've seen a modicum of posts on HN that was something along the lines of "I've been a C++ developer for the past 12 years, how do I become a web developer?" So I guess there's something to it.

At least in some of the cases.

Re: On Being a Generalist

#99
post #8

Often we cherish specialists quoting "Jack of all trades, master of none". Curiously enough, the full version of the original has a twist: “A jack of all trades is a master of none, but oftentimes better than a master of one." https://www.theodysseyonline.com/7-phrases-youve-been-misquo...

There is another aspect that is relevant, and that is that the effort needed to get to the 99th percentile of some ability is way larger than that to get to the 90th, and often, you can do very well with just being in the 85th. So you can become pretty good at many different (often complementary) things, in ways that likely make you way more effective than that guy who's a guru in a very specific topic. Then again, s…

One of the things I treasure in a good generalist is the ability to be an informed consumer. They can think a little farther down the road about what we need from solutions and why.

Re: On Being a Generalist

#100
I thought I was generalist until I noticed that some skills I claimed to have, I hadn’t actually used in a decade or longer. Do I really still know that stuff? How many problems I had to deal with are resolved?

I think perhaps I am instead a serial specialist.

Post reply on HN