3 ms·
It's only useful in debugging a bad situation. Larger PRs are associated with slower development velocity. However, it's not clear if that's because larger PR t
by SkyPuncher 4y ago
It's only useful in debugging a bad situation. Larger PRs are associated with slower development velocity. However, it's not clear if that's because larger PR tend to come from inexperienced developers or experienced developers are making significantly more complex changes.
Anecdata: It took me 4 weeks to write a 250 net new lines of code line PR. Normally, I'll write about 1k lines of code per week. I ended up having a tasks that significantly changed security models and required a lot of small, distributed changes.
- threeseed 4y ago> Larger PRs are associated with slower development velocity There are many reasons PRs can be large. Often it's indicative of broader issues e.g. lack of automated testing, inadequate CI/CD processes, incomplete business requirements etc.