I've yet to see the company that can make a swap from full stack to front and back end teams successfully, through choice or necessity. I've seen it as a paradigm shift based on a companies perception that you can create a better production line for software, although changed no processes to support it creating a chicken or egg scenario. I've also seen it pushed by developers that did only want to work on a part of a system after being hired as full stack. In all instances I've seen either a lack of communication or communications breakdown.
For me the frustration is that a single full stack developer can create a fully functioning feature with very little to no assistance. Splitting the teams implies you need a minimum of 2 people to deliver a feature and you gain all the complexity of the communication and the shared understanding that is required.
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've yet to see the company that can make a swap from full stack to front and back end teams successfully, through choice or necessity. I've seen it as a paradigm shift based on a companies perception that you can create a better production line for software, although changed no processes to support it creating a chicken or egg scenario. I've also seen it pushed by developers that did only want to work on a part of a system after being hired as full stack. In all instances I've seen either a lack of communication or communications breakdown.
For me the frustration is that a single full stack developer can create a fully functioning feature with very little to no assistance. Splitting the teams implies you need a minimum of 2 people to deliver a feature and you gain all the complexity of the communication and the shared understanding that is required.