Live data from Hacker News

Ask HN: Do you regret being a generalist?

news.ycombinator.com

31–40 of 231 posts

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

#31
Isn't being a generalist what you should do on the way to becoming a domain expert?

My generation (definitely older given the replies :~) ) was sold straight onto the specialization dope. I think that smack is what's screwed the planet.

I recognized the (very, top schools) hard sell for bunkum at a very tender age. The flip side is that you don't actually become a expert much before middle age. That's also how it should be, but my second and third decades of my career were very lonely. If I would beg any sympathy for my generation's reprehensible stewardship, this might be it if I could ask without being self serving. As stands, over to you lot. Look back hard at the events in history just now being declassified. For the first time in the information era newly released history is not only relevant but crucial, because the generation born fifty and sixty years ago still living, and able to talk with you, was isolated almost entirely if not hermetically, from the rest of mankind and are, albeit well concealed by superficial wealth, personal or circumstantial to society, shitting ourselves when not freaking out angrily.

Personally I think the freaking out behaviour has been copied by the headless right rather than is actually endemic, but understanding social mimicry in traumatic stress is just another example of how much you have to figure out and filter out, similarly to plotting a course to high professional status just as any independent thinking, and the state of many professions today is that attaining independent thought is a de facto domain expert qualification.

Traumatic mimicry could be easily applied to the reinventing the DBMS from discovery of ACID (early MySQL, 00's; MongoDB, 10's) , the Russian Dolls rewriting of Windows display layers, and potentially almost any project recently enabled by putatively inexpensive compute.

Of course I'm hinting that philosophy and other non technology understanding can make being a generalist both much easier and more pleasurable, but this is a personal journey, find your reasoning where you can but remember that you're a generalist.

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

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

- Robert Heinlein

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

#33
post #29
post #24

No. The only thing I regret along my career path is being officially diagnosed with a mental illness during a hospitalization, which led me to missing work without notice, which caused me to become abruptly unemployed (and, eventually, unemployable). And despite the fact that my career ended abruptly and without warning, I regret nothing else. There is no downside to learning new things, even if they don't have immed…

I am curious about this. Are you a software engineer? Is it your condition that has prevented you from finding employment, or the stigma? Or a gap in your resume?

I used to be a DevOps. My difficulty in finding employment results from a combination of my illness's symptoms and the (now ever increasing) gap in my resume.

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

#34
Yes and no,I have done frontends, backends, cloud, devops, ux, project/program/product management, sales , product development,I helped one startup to grow from 0 to 100 and another startup from 0 to acquisition and made good money, but from a job perspective the only option to progress in my career is to start something of my own, I can't find a company who needs a person like me, so generalist is a good path if you want to start your own but specialisation is better for job growth

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

#35
No, from the perspective that it has allowed me to take on interesting projects that were otherwise impossible. In my case, by linking tools from different fields (spectroscopy, computer vision, chemistry, medicine, human systems hacking, ...) and getting something viable together. Once we demonstrate viability and need, we then build a team of specialists to flesh out the details.

Yes, in that that you have to sell yourself carefully. "I solve any problem" is not generally reassuring, because it is always an approximation, and because a specialist might see the pitfalls of a particular approach earlier. Given time you will become a specialist in whatever tool, but that needs to be built into projects or your professional development budget.

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

#36
I don't regret it at all, but finding high paying roles can be a little more difficult. Its a tradeoff though, because after a few years at a role its often seen how valuable you actually are so in bad economic times you may be the last to get cut.

I also think generalists get pushed into management at a higher frequency. Not something I am personally interested in, but I get asked yearly at least at every role I have been at.

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

#37
I"m actually in much the same situation (young SWE, generalist, interested in AI), and I find it's really beneficial especially in a startup space. My resume can seem all over the place, but I find that startups tend to prefer someone who has demonstrated the ability to learn quickly and deeply.

I've been looking for others to talk about it with, so I'd be happy to discuss further.

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

#38
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, drivers, software, across ethernet, CAN bus, config files, calibration extrinsics, closed loop controllers... etc.... being that kind of bug hunter is valued and has worked out well for me. I feel zero age discrimination in my role, despite needing 7 bits to hold my age.

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

#39
I'm also in my early 20s. I'm personally aiming for being very good at a few things with a lot of very high level background knowledge. Basically an extreme T-shape.

1) I believe that not having a clear competency will make it harder for people to place you. Your experience is a lot more legible if you're the "React guy", "C guy", "AI guy", etc.

2) Trying a bit of everything is very different from being good at everything. Is "a bit of x" useful? From what I've seen, no. It's not a unique differentiator, it's easily replicable and it doesn't provide much value. Being good at a few different things seems like a different ballgame though.

3) If you are a very broad generalist it will close a lot of doors for particular work. If you are highly specialized it will close a lot of doors for particular work as well. AI/ML for instance, seems like the kind of field that will be closed to you unless you specialize in it. On the other hand, building full products is something that seems more inaccessible to specialists.

Post reply on HN