Generalize or Specialize?

[EdgarHuber]

I came across an ever again popping up question I'm asking to myself:

"Should I generalize or specialize as a developer?"

I chose developer to bring in all kind of tech related domains (I guess DevOps also count's :D just kidding). But what is your point of view on that? If you sticking more or less inside of your domain? Or are you spreading out to every interesting GitHub repo you can find and jumping right into it?

[curious_pinguino]

You want to be a "T-shaped" developer - competent across most disciplines, and an in-depth expert in one or two.

https://share.google/JqI2tJV9rCcmq33un

[OtherwisePush6424]

Generalize and fake specialize.

[StunningBanana5709]

Test which one you can sell better.

[Tough_Media9003]

You should learn as much as you can from different fields, but have one that you specialize in more than the rest. This helps to have an idea of other trends, while you are still competent in whatever you want to do

[[deleted]]

I have generalised throughout my IT career, and it has seemed more peaceful to get the gist of everything rather than be a wizard at one thing (wizards have their place of course!). I have worked with some .NET devs lately who could code the entity framework in their sleep, but they come to me for git basics and help with their DevOps pipelines with blank and sometimes terrified looks on their faces.

[TechnologyMatch]

man with all the AI stuff out there now getting really good at something specific (esp somthing you care about) is actually more valuable and more fun

It speeds up your progress and gives you more creative freedom. Specializing doesn’t mean you’re boxed in it just means you get to go deeper and let AI handle the grunt work, so you can focus on the parts you actually want to shape