Meanwhile, I have never understood positions like this. What exactly does ideal team work look like to you? Do you collaborate with your teammates or do you all

Meanwhile, I have never understood positions like this. What exactly does ideal team work look like to you? Do you collaborate with your teammates or do you all go off and work on completely isolated tasks? Do you only share knowledge after the fact through code reviews or do you manage to spontaneously talk about how to accomplish big things before the tasks are assigned? Do you routinely communicate with your users or representatives thereof or do they spontaneously show up and let you know about the actual problems they have and how things are going? Is the application you are building so simple that you are the only person working on it otherwise why is a ratio of 1:31 an effective ratio of collaboration for you? From my perspective, well functioning teams communicate with each frequently. What's the daily, short term (spring), long term plan? Why did that last plan go well/wrong and what should we do differently? Routine meetings have a habit of becoming rote, but it is difficult to ensure such conversations are spontaneously happening between more than a couple of people. I don't want my colleagues to be surprised when they review my implementation, so we need to discuss it before I do it and vice versa. Discussing those things ahead of times also allows us to plan and prioritize more effectively. It also helps us align and build a better understanding of what we are doing. I think people are obsessed with this kind of thing because people quest for a silver bullet, but individual teams working on disparate products and problems will find different strategies more effective and require a different balance of communication. Meanwhile, most organizations will push a chosen silver bullet in the name of consistency instead of enabling teams to truly self organize.