Arguments in Pull Requests

The asynchronous discussion in pull requests could have been solved earlier if the team had a more collaborative approach.

Don't get me wrong, a pull request is a collaborative task as well. You propose some code changes to merge in to the main branch and a colleague is checking your proposition to see if it is a solution that will benefit the product. But I'm a fan of wroking together to solve the problem, not just after the proposition of merging has been made. But rather during the development phase.

I know this is not a controversial take, but on the majority of the places I've worked, the developers work on a task/pbi alone in a silo. Then let a developer from another silo review the code.

I just needed to get this out. I might change my mind tomorrow, who knows?