I can say with all sincerity, that I have been on projects like that.
And because "remote' is such an incredible afterthought, co-dev production is harmed immensely as a kind of collateral damage.
I have worked in companies that did this right, we had offices in NYC/London/Bangkok and we did everything over RT tickets+IRC, mostly because it was incredibly frictionless (yes, I know IRC and RT are not the best tools in the world, but once they were set up and everyone was in people preferred using them to taking in person meetings).
Contrast with today: we have teams in Sweden, UK, North Carolina, San Francisco and Helsinki- and we use Jira/Teams/Confluence as our "tools".... but they're so /slow/ that we have to be dragged through the coals to use them, we much prefer in-person meetings, we much prefer hashing things out over a coffee.. and thus, our co-dev is very much out of the loop, and it's "odd" (as in, not default) to include them. So what happens is we carve out bits of responsibility and we restrict immensely the communication channels.. in fact some peoples entire job is to ensure those communication channels run smoothly.. and it's still very many shades of terrible.
I want to blame the tools, but really, it's the culture, if you're more comfortable engaging over IM/Tickets w/e then it doesn't matter if you're sitting 10ft away or 100mi away.
And because "remote' is such an incredible afterthought, co-dev production is harmed immensely as a kind of collateral damage.
I have worked in companies that did this right, we had offices in NYC/London/Bangkok and we did everything over RT tickets+IRC, mostly because it was incredibly frictionless (yes, I know IRC and RT are not the best tools in the world, but once they were set up and everyone was in people preferred using them to taking in person meetings).
Contrast with today: we have teams in Sweden, UK, North Carolina, San Francisco and Helsinki- and we use Jira/Teams/Confluence as our "tools".... but they're so /slow/ that we have to be dragged through the coals to use them, we much prefer in-person meetings, we much prefer hashing things out over a coffee.. and thus, our co-dev is very much out of the loop, and it's "odd" (as in, not default) to include them. So what happens is we carve out bits of responsibility and we restrict immensely the communication channels.. in fact some peoples entire job is to ensure those communication channels run smoothly.. and it's still very many shades of terrible.
I want to blame the tools, but really, it's the culture, if you're more comfortable engaging over IM/Tickets w/e then it doesn't matter if you're sitting 10ft away or 100mi away.