I agree with this, it is good for skillsets to cross pollinate and it makes you better at both. Another divide is development and design, those that can do tha

I agree with this, it is good for skillsets to cross pollinate and it makes you better at both. Another divide is development and design, those that can do that produce amazing products. You see this more in the gaming or interactive space but it makes you less biased and understanding of the problem points, and best parts of both verticals. Specialization over generalization is why lots of large software sucks today and small companies or startups win, they employ more generalists, design/develop crossovers and full stack product focused t-shaped employees. When teams are huge, specialized and care is removed. The chaos of more communication channels (N(N-1)/2) encourages just staying in your lane rather than viewing the big picture. Small teams with generalists are where the best products are made due to everyone going beyond their lanes/channels and viewing the big picture. I think generalization is best in startups or small groups including gaming/interactive especially with hyperfocus on a product. Making the product good in all aspects, and caring about them, from design to development, presentation to production, and especially maintenance and iterative growth. Once that is established, teams can grow and specialize, but innovation and creative growth is harder.