Bachelor's and Master's in CS from MIT. Previously, worked @ Microsoft & Zynga. Currently Co-Founder of Moesif (moesif.com), the most advanced API analytics platform.
I think it is generally hard for anyone to be good at everything. That is why have a team of people specialize in different areas makes for a stronger team.
Bachelor's and Master's in CS from MIT. Previously, worked @ Microsoft & Zynga. Currently Co-Founder of Moesif (moesif.com), the most advanced API analytics platform.
there is also an issue of business need/project needs also.
I think small projects, full stack developers is great.
For large projects, where it is just not possible for a single person to know every piece of code, (even if you are good at both backend and frontend), it is just more efficient each team member to have an area of focus.
Often times, with large teams, the teams is even further segmented by different micro services.
Yes, segmenting by domain context is a really wonderful choice and is (as you mention) the basis of microservice architecture. But separating the structure to be UI and Backend causes more harm than good in my opinion. It seems to be he opposite of domain driven design (DDD).
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 think it is generally hard for anyone to be good at everything. That is why have a team of people specialize in different areas makes for a stronger team.
Absolutely, but I think it’s important to recognize that some people want to be generalists. Myself included. :)
there is also an issue of business need/project needs also.
I think small projects, full stack developers is great.
For large projects, where it is just not possible for a single person to know every piece of code, (even if you are good at both backend and frontend), it is just more efficient each team member to have an area of focus.
Often times, with large teams, the teams is even further segmented by different micro services.
Yes, segmenting by domain context is a really wonderful choice and is (as you mention) the basis of microservice architecture. But separating the structure to be UI and Backend causes more harm than good in my opinion. It seems to be he opposite of domain driven design (DDD).