DEV Community

Discussion on: A generalist is born when a specialist becomes bored

Collapse
 
daedtech profile image
Erik Dietrich

Not to zoom right into a tree instead of the forest, but I'm really curious about something.

"But many developers, engineering managers and even CTOs think that generalists are a risk and that what software teams really need are specialists."

It's been a long time since I've applied for programming jobs or looked at their job descriptions, but I know that many of them these days call for "full stack" whatever. And, from what I recall, most job descriptions used to have an entire alphabet soup full of "required" and "nice-to-have" languages, frameworks, databases, etc.

I spent a number of years as an IT management consultant, so, actually talking to managers and CTOs about their org charts, job descriptions, etc. And the most en vogue thing in the mid-2010s was "T-shaped people" or "generalizing specialists" who maybe had one deep area of knowledge but then could adapt to and be plugged into any team or situation.

So I guess my question is, has there been a sea change in the last 3-4 years? Are hiring managers and leaders now saying, "I want devs that know C# and absolutely nothing else?" Like, is that some kind of software management fad, now, to look for people that have only one programming language/framework on their resume?

If so, that seems absurdly short-sighted.