I agree with what you say and with the meme. You say :
Modern web development is pushing hard for “full stack teams” not “full stack devs.” [...] Each person will always have their strengths and weaknesses, but together the team should be fully autonomous and productive.
And for me the key to having a full stack team is to hire people with different strengths. I've seen many occurrences of teams failing because management would only hire the same profile for every single developer, and then act all surprised because their team of SQL engineers can't make a PWA, or their Angular gurus are crashing the database.
So yeah, I think the meme is a good way to describe most developers (whether they call themselves "full stack" or not), and an ideal team would have several of those developers with different parts of the horse fully drawn, so that when you superimpose them you have a beautiful horse.
Yup, absolutely. I can see that you’ve has similar experiences on teams that I have. Creating a team is clearly not a “one size fits all” type of situation. And I’m glad that there are people out there such as yourself who are able to see the grey areas. I think that’s the main reason I chose to speak up: I’m tired of managers saying, “let’s ask the backend developers” (and other silly distinctions like that). No, they should ask the whole team. The best solution to a user’s problems might be the one that stretches across the distributed system.
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.
I agree with what you say and with the meme. You say :
And for me the key to having a full stack team is to hire people with different strengths. I've seen many occurrences of teams failing because management would only hire the same profile for every single developer, and then act all surprised because their team of SQL engineers can't make a PWA, or their Angular gurus are crashing the database.
So yeah, I think the meme is a good way to describe most developers (whether they call themselves "full stack" or not), and an ideal team would have several of those developers with different parts of the horse fully drawn, so that when you superimpose them you have a beautiful horse.
Yup, absolutely. I can see that you’ve has similar experiences on teams that I have. Creating a team is clearly not a “one size fits all” type of situation. And I’m glad that there are people out there such as yourself who are able to see the grey areas. I think that’s the main reason I chose to speak up: I’m tired of managers saying, “let’s ask the backend developers” (and other silly distinctions like that). No, they should ask the whole team. The best solution to a user’s problems might be the one that stretches across the distributed system.