Live data from Hacker News

Ask HN: Do you regret being a generalist?

news.ycombinator.com

71–80 of 231 posts

Re: Ask HN: Do you regret being a generalist?

#71
post #8
post #5

A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyse a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.

On the flip side, that’s a 50-year old quote and maybe times have changed?

Fair enough, nowadays you're probably better off writing a non-rhyming poem as opposed to a sonnet (at least if you're trying to be trendy). However I think a lot of the other skills are attainable and even worthwhile.

Re: Ask HN: Do you regret being a generalist?

#72
post #8
post #5

A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyse a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.

On the flip side, that’s a 50-year old quote and maybe times have changed?

I don’t know know if anything has changed but sometimes it feels like most people today can’t do a single one of those things. Maybe it was always an unrealistic expectation, though.

Re: Ask HN: Do you regret being a generalist?

#73
Generalists may always have a job in software, but specialists often have the interesting jobs. Everyone starts out as a generalist. Like you, I am always interested in vastly more things than I have time to properly grok.

Whether or not to be a generalist is a question of ambition and also where you are in your career. Life outcomes for generalists cluster around the median, outcomes for specialists have much higher variance. The idea of "t-shaped skills"[0] is valid and often excellent generic advice for optimizing career outcomes but it is not the right advice for everyone. I made a very intentional decision to ignore my polymath instincts and focus on just a few strategic areas when I was ~30 and it made a very noticeable difference in terms of the opportunities available to me.

It is difficult to know what you want to specialize in without generalizing first. True mastery of a domain typically requires considerable amounts of personal interest and focus, so it needs to be something you enjoy or you are unlikely to be competitive against those who do enjoy it.

An alternative, if a single specialization feels too limiting, is skill stacking i.e. specializing in two or three skills. This has more potential but requires more work. There may be only a few people in the world that can operate at the intersection of those specializations -- it can be very rewarding depending on what those specializations are. Complementary specializations can be synergistic.

Don't discount specialization happening accidentally by virtue of how your career evolves. I have a useful deep specialization that I never intended which is strictly an artifact of a truly random path dependency, not personal interest. Nonetheless, it is immensely valuable to me now because it complements other specializations I have so I maintain it.

Don't worry about it. If something is worth going deep in, you won't need anyone to tell you.

[0] https://en.wikipedia.org/wiki/T-shaped_skills

Re: Ask HN: Do you regret being a generalist?

#74
YES! :-(

I'm in my 60's. Have worked as a contractor in effectively every field of IT and taught post-grad SE courses at university. I still program in C, Javascript and Python. Can design, build and configure data centers. Know most variants of Unix and its progeny, etc, etc.

Yet ... I'm finding it very hard to get contract work post COVID. Recruiters are looking for 3-5 years experience with specific products. I demonstrably can learn fast and most of IT is old wine in new bottles with fancy labels. But that doesn't meet expectations.

If you seek intrinsic motivators, then being a generalist satisfies curiosity and yearning for knowledge. If you seek optimum employability and high salaries then being a specialist is the key. BUT a lucrative specialization now, will probably be of little value in 5-10 years time.

Re: Ask HN: Do you regret being a generalist?

#75
For me, becoming a generalist has been driven by broad curiosity across many schools of thought – not limited to just software nor even technology. I can't even imagine a world where I would have been content specializing.

One upside that hasn't been mentioned, is that not not specializing leaves more room for serendipity. I could not have followed many opportunities that have popped had I not been willing to start again as a novice.

The only, but big, downside has been that I had to quit my post-grad studies and the academia. Just the thought of pursuing a single avenue for a minimum of four years is unbearable.

Related to the above, I've also had to come to terms that I won't be one of the best in the world at anything (easily) measurable. It hasn't been easy to accept, but at the same time I've also begun to appreciate collaboration much more than competition. I believe it's also a healthier approach to life in general.

Re: Ask HN: Do you regret being a generalist?

#76

Pro tip: you're not a generalist. A big chunk of specializing is how you package/market yourself. I consider myself a "full stack employee". I've done backend, frontend, hosted live events, some sales, marketing, a dash of HR, pretty much everything. Do I write that on my LinkedIn? Heck no. A year or so ago I looked at all the experience I had, saw I had a through-line story of how I've worked on video projects over…

I have noticed that when interviewing, the more specialized technical people often look down on full stack engineers, whereas managers are more excited about it.

I consider myself full stack, but in my last role I presented myself as a frontend engineer, with some backend experience. Eventually this role just kinda expanded into both frontend and backend.

Now that I do contract work, I present myself as whatever they need, with my current contract, I was hired to do frontend, but just started looking at the backend when running into some problems or questions about the data. There's always a point where they ask you "oh, you can work on the backend too?".

Re: Ask HN: Do you regret being a generalist?

#77
I can provide perspective from both sides of the table, to add to the wonderful comments already posted.

The first few years in my career were a will-do-anything attitude. So yes, like the OP, I did a bunch of different things. A few years in, I harbored similar thoughts of feeling inadequate. A jack-of-all-trades-but-master-of-none. Especially, since I was at Google and was surrounded by the best of the best and experts/specialists in anything you could name.

My next stint was at an early stage startup (Now, as a founder, my favorite hires are generalists. Engineers who have a wide breadth of experience, a do-whatever-it-takes mindset, and ideally, a sprinkling of product/business sense. They are the first-principles thinkers. They can handle ambiguity and change without batting an eye. They will figure when/where you need a specialist.

Be proud of being a generalist.

Re: Ask HN: Do you regret being a generalist?

#78
post #45
post #18

Earlier quoted context omitted.

Why is T-shaped ideal? I’ve heard this before but it seems arbitrary. What about “W” or “U” or pick your favorite letter?

It takes a long time to get truly skilled in something. What we call an expert is really what a reasonably intelligent person can be expected to learn about a single topic within a lifetime. The gains in one area compound on themself. Given that these gains compound, you can't learn 2 things half as well. So the T-shape represents the constraint that you only have a shot at becoming an expert at 1 thing. Spend 80% of…

> you only need to read a handful of books on a single subject to know more about it than most people.

It's easier than that! Just reading (in full) the Wikipedia article about something you probably makes you more knowledgeable than 90% of the general population. Reading a whole book about it -- maybe 99%.

Re: Ask HN: Do you regret being a generalist?

#79
Every two or three years I find myself with the need of carefully planning my next steps, so that my generalist pattern does not disrupt the advancement of my career according to the criteria of my environment, this is very tough at particular moments because sometimes you have less time available to work on your broad base and on the development of specific skills that are needed for some of its corners, but I still don't regret it.

Re: Ask HN: Do you regret being a generalist?

#80

Well, I do think it is more challenging to reach the highest individual contributor pay grades as a generalist. On the other hand, being the one person in the org that understands how all the pieces play together and can debug all up and down the stack brings a lot of value and is eventually recognized. I now work in robotics, and being able to chase bugs through mechanical, sensor behavior, electrical, firmware, dri…

Lucky you! I started having problems after I overflowed 5 bits, the upgrade to 6 bits hasn't been much help.
Post reply on HN