Most teams don’t realize this, but their biggest bottleneck isn’t architecture, tech stack, or even legacy code.
It’s pull requests.
If you read about trunk-based development, you’ll see the same advice repeated everywhere: small changes, frequent merges, fast feedback. Sounds simple. Almost obvious.
And yet — in reality — most teams are nowhere near that.
I’ve personally seen pull requests sitting open for months. Not days. Not weeks. Months.
At one point, we had a pull request in our team that was open for more than six months .
Six .
Months .
At that point, it’s no longer a pull request. It’s a parallel universe.
Below this link you can read first article about Trunk-Based Development
https://codecraftdiary.com/2026/04/04/trunk-based-development-why-most-teams-think-they-use-it-but-dont/
The Hidden Cost of Large Pull Requests
Let’s be precise about what’s happening here.
A large pull request is not just “a bit harder to review”.…