specialist

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.

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.

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.

Eitherway/Both is fine.It mostly depends on the context.Like in the past I used to be a web dev in general but now I'm mostly a gamedev but that doesn't mean I don't make website or vice versa for someone transitioning.
You can set your foot in the middle.Like a specialist but can do other stuff.
Like: an app developer who can also make websites with modern stack.
As a developer you are bound to learn newer and better technologies to be ahead in general being a guy who can do everything a bit is not good since it means you've mastered nothing.
TL:DR, Master one thing but make sure you have a glimpse of a few other stuff to give yourself a bonus 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.

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.

I would rather go for generalist. But i cant forget to specialize in one area.
GENERALIST: Freelancing, more opportunity
SPECIALISATION:

Depending on the day sometimes it's better to be a generalized specialist and sometimes it's better to be a specialized generalist 😜

I know "generalists" who can get solid jobs anywhere doing anything but I also know specialists that are practically the only person in the world that knows so-and-so DSL or legacy language and they get paid enough to live off of just by going in twice a month and pressing a few buttons (hyperbolizing but you get the point)

I think generalizing is incredibly important (to a degree) for expanding your knowledge within your specialization as it forces you to see other perspectives. For years I was exclusively a Python developer and although I became really, really good at Python I've recently been working a lot in R and this complete shift in perspective has made me an infinitely better Python programmer (and programmer in general). Likewise when I investigated and learned some C I was able to deepen my understanding of Python and again push my specialization inward while at the same time generalizing outward

Kind of a roundabout answer but I prefer a mix of both - too much generalization leads to not enough depth yet too much specialization could lead to stagnation. Seeking out new/deeper generalized experiences can infinitely improve your skills within your specialization

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

For me, I never wanted to specialize in any tech... I liked learning a lot of different things and it didn't seem worth it to focus on one thing, as it would eventually be outdated, no "new projects" would be started in that specific tech.
6 years working as a programmer, and now I feel a huge gap. It's not hard to find work, but I feel there's nothing outstanding about me. That hurts my ego a bit :P but it also makes me feel that maybe, someday, I won't be a desirable professional anymore 🤷

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.

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

"Jack of all trades, master of one" is what I generally aim for. That is, be a generalist, but go more in depth in one (or a few) directions and build some proper expertise in those areas.

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.

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.

Standards live longer than technologies so another option is to specialise at the standards level that can last a career.
Some might disagree but it has served me well for 20+ years.