4 ms·

It sounds like it is promoting a siloed cogs in the machine type of work ethic. Where you are either front end or back end and no one is thinking end-to-end abo

• satyrnein 4y ago
  I think the causality runs the other way. Once the frontend had gotten so complex that it required a specialized team, solutions arose to reduce the back and forth necessary between frontend and backend teams.
• locutous 4y ago
  That's generally true for sizable companies. Small companies can and do use full stack devs. Segmentation makes some sense but the industry is lacking end to end thinking as you point out.
• adra 4y ago
  Sr enough developers who's role expands beyond a single team, architects, product managers, product owners, the list goes on for the roles of people who are often task of thinking big picture about the health and "end-to-end" picture of any given software project. Your narrow synicism makes me assume you don't work in a company that has a large dev org. People specialize and if you want to be the learn and do everything person, you'll find that you're doing less and learning more which isn't a good fit for most orgs.
  • quickthrower2 4y ago
    You are right I have worked in relatively small companies (and "bigger small" companies that were not doing web). My concern is not specialization which I think is necessary for a larger company. It is more the technical solution of "here is GraphQL now your teams don't need to talk and you don't need anyone thinking end to end". I can't believe that is helpful. I may have created a strawman though?