Live data from Hacker News

Ask HN: Do you regret being a generalist?

news.ycombinator.com

1–10 of 231 posts

Ask HN: Do you regret being a generalist?

#1
I'm a fairly young SWE in my early twenties, and I've tried a bit of everything.

Fullstack web dev, a bit of cyber security, a bit of AI, mobile apps, all kind of automation/bots/mass scraping, growth hacking, small games, low level C...

And I'm starting to wonder if I should specialize.

I've always been interested by AI, but since it's such a large/complex field, I never really took the time to dedicate myself to it completely because I'm always interested by 10 things at the same time.

I have absolutely zero doubts about my employability, but I'm afraid to regret it long term if I don't specialize in an interesting field.

Do you regret being a generalist? Have you been one in the past and then changed? In that case what do you prefer? Do you regret it?

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

#2
I don’t. And generalist is a flexible term. For my career it means frontend, or backend, team lead, or IC. There have been a few points where I thought “I don’t ever want to write browser code again” and “all I want to do is UI”. I’ve built shopping carts, government tax websites, worked in automotive, and now I build tools to manage robots. I suspect if I had been narrow in my field I wouldn’t have had the opportunities that I’ve enjoyed.

I sometimes think a narrower, deep specialization might have yielded a bigger paycheck, but overall I think I’m happier being able to explore broader fields and concepts.

As a final note I’ll say that you’ve got plenty of time to generalize and then decide to specialize. Bring in your early twenties is far more time than it feels like right now.

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

#3
Nope.

Mid thirties and being a generalist means that not only am I employable, my breadth of experience allows me to bring together things from places others would be unaware of.

I occasionally wish i was more of a specialist, but usually chalk it up to the sort of all pervading impostor syndrome that goes on in software development circles.

If someone wants to put me in a position based on my current skills where I end up becoming an expert and they pay for that time, then it will happen. Otherwise I'll just keep learning enough to be useful in dozens of smaller ways. From the browser's JS engine event handling at the bottom of Flux/Redux to how Kubernetes works and how to do useful stuff with it, to 3D printer firmware and how my drill press works.

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

#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.

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

#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?

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

#10
Being a generalist certainly makes cocktail parties more interesting. Being a little good at everything makes you more employable as well, you don't get locked into 1 niche. The T-shaped person is the ideal. You should be great at 1 thing and decent at many other things, but always keep the T-shape. Keep an identity to center your varied experiences around. It will keep the main thing and the auxiliary things interesting in tandem.
Post reply on HN