Hello Everyone,
So I have been wanting to ask which is better, being a generalist developer or a specialist developer?
As a developer, would you rather be a generalist, someone who knows a lot about different types of software and can use them to get the job done? or a specialist, someone who specializes in a certain kind of software?
What do you guys think?
Also, I would appreciate it if yáll joined my online developer community on Twitter to share your articles, ask questions and share the different stuff you are learning. Here is the link
Top comments (25)
The money is in specialisation…for a short while that is, until the technology becomes obsolete (generally 5-10 years).
So my vote is generalist for long term success with a specialism that you focus on at any one time. That way when the recession hits and layoffs happen you can step into another role easily while looking for a job that utilises your specialist area.
Well for me. I will rather specialize in a favorable stack. But as time goes on. I might add more stack.
TL:DR: Both, one after the other. It doesn't matter what you start with as long as you keep learning.
I've recently learned about T-shaped skills in recruitment. It seems to be a solid approach to building your knowledge in dev - topics.
Specialising is good and necessary, but acquiring more general knowledge gets you out of your comfort zone.
I (accidentally) specialised into Web Development very early. After two years, I started looking beyond the horizon. I feel like learning Typescript made me a better Javascript developer. Also, I've learned a lot about JS Garbage Collection, its Event Loop and the Heap by studying Rust as a system language.
I don't think you can be a specialist without some element of being a generalist. Otherwise you'll probably be missing out on too many external aspects of what you're doing, or miss that bigger picture.
A generalist is usually more achievable, and flexible job wise, so I'd go that route. Plus I find it more fun to be a generalist :D
Do what interests you... If that's lots of things, great! If it's one specific area, fantastic!
Don't pigeonhole yourself. Go wherever your curiosity takes you.
Yes, this is some solid advice. I second that.
Up until today I went where things were interesting. E.g. I left my last job years ago because I played Java to the end (up to a level where I found it uninteresting) and wanted to learn more Python. So I resigned and started working in a Python shop (which btw. is turning into a Go shop, which makes it interesting to stay for a while longer). So I went down the generalist road. But not necessary.
There are clear pros:
1) You learn what you like and work with what you like
2) which keeps you motivated and with good motivation
3) your output will be better.
Don't go one way or another only because someone on the internet told you it was the right way to go.
Yup, that's a huge mistake
You can be both, specialize in one thing and then learn other things too.
I consider myself a generalist, but I specialize in Front-End particularly in Mobile UI with Flutter.
I like being a generalist because I can understand the whole development stack, I think a front end developer should know the basics of how DDBB, design process and apis work and viceversa. But then I specialize in what I'm getting paid to do, to do the best job possible, and to be able to get another job in case I get layed out at some point.
As many other comments have mentioned i think the best approach is both. You definitely want to be the go-to in a specific area. This will make you more valuable than others.
However, there should be a baseline knowledge of other concepts (maybe not initially). This will help with collaborating with others and being able to quickly adapt and learn on-the-fly.
There are boundaries of course. You don't want to spread yourself too thin in completely unrelated topics. Use your best judgement and do what you enjoy.
I'm a generalist. In my experience, specialist developers have better job security and better pay.
To me, those upsides don't compensate for the downsides — narrow focus, smaller playground, and the danger of obsolescence (such as if/when that specialized technology becomes superseded).
I have always been a generalist, not only in development. Being a generalist can open you doors which you won't find when you are too specialist. I mean when I need real deep specialist knowledge I know which persons I need to ask.
Meanwhile I own a small company with some developers and I'm sure being my kind of generalist helps me a lot there.
T-shape (already mentioned here) is a must. It allows having a basic understanding of a wide bunch of domains while keeping deep lore in a few most appropriate ones. I had to switch a few times between similar but substantially different domains. More so, I had got a case when a variant of burn-out led me to emotional detesting of the area I worked for 8 years... and rather easy move to another one saved productivity.
To begin with, especially junior, specialist, learn your field.
It's easier to get promoted and once there ask to work on other things, but then specialise in that new area.
That way you become an expert generalist.
The "full stack developer" in web parlance.
Nothing stopping you learning other tech, just don't get distracted by the shiny too much, as your general work will suffer.