> This sounds like an argument for having a single stand-up meeting instead of communication through slack and email spread throughout the day. It's an argumen

> This sounds like an argument for having a single stand-up meeting instead of communication through slack and email spread throughout the day. It's an argument for having meetings when you need them, with whoever you need them with, with no particular schedule or routine attached. > I care quite a lot what the people in my team are working on. Do you really? Or do you just want to signal that? > Otherwise why are we even a team? You are on a team because that's the unit of organization above the individual. > It's the opposite: if developers are not communicating, they're probably not cooperating with each other, which means something is very wrong. If developers need to cooperate, you have a problem that you should avoid at great cost. Of course, sometimes cooperation is unavoidable, but it's not a good thing in and of itself. Don't let anyone tell you otherwise. Aim to split up your work to require minimal cooperation. This may sound like unconventional advice, but anyone with enough experience managing developers will likely agree.