There is always a need for generalists. People who would otherwise identify as strictly focused on one specific thing are also really generalists, because they have had to adopt other skills to drive their specialization. Whether your workplace can subsist solely on generalists depends on how important and technical your work is.
You can tell this in a team where the core of the team, even just one key person, lives in a very narrow band of language|environment|technology. Not because they are too rigid to shift, but because they work at the very edge of what technology can provide, whether that is performance or reliability.
Most languages|environment|technologies can do neither. If you aren't very concerned about getting the most, while taking the least, out of the hardware you are running on, your work isn't that technical. If you don't have to assure bulletproof reliability because there is a reasonable belief that downtime wouldn't put anyone's life and limb in jeopardy, it probably isn't that important.
But if there are people already doing both, why aren't we building on that expertise instead of enervating the industry with rubbish fad tech?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There is always a need for generalists. People who would otherwise identify as strictly focused on one specific thing are also really generalists, because they have had to adopt other skills to drive their specialization. Whether your workplace can subsist solely on generalists depends on how important and technical your work is.
You can tell this in a team where the core of the team, even just one key person, lives in a very narrow band of language|environment|technology. Not because they are too rigid to shift, but because they work at the very edge of what technology can provide, whether that is performance or reliability.
Most languages|environment|technologies can do neither. If you aren't very concerned about getting the most, while taking the least, out of the hardware you are running on, your work isn't that technical. If you don't have to assure bulletproof reliability because there is a reasonable belief that downtime wouldn't put anyone's life and limb in jeopardy, it probably isn't that important.
But if there are people already doing both, why aren't we building on that expertise instead of enervating the industry with rubbish fad tech?