4 ms·
> This suggests that this pair of people only release 1 big PR for that whole cycle I think that's a too-literal reading of the text. The way I took it, it wa
by wavemode 2y ago
> This suggests that this pair of people only release 1 big PR for that whole cycle
I think that's a too-literal reading of the text.
The way I took it, it was meant to be more of a generalization.
Yes, sometimes it really does take weeks before one can get an initial PR out on a feature, especially when working on something that is new and complex, and especially if it requires some upfront system design and/or requirements gathering.
But other times, surely, one also has the ability to pump out small PRs on a more continuous basis, when the work is more straightforward. I don't think the two possibilities are mutually exclusive.
- Kinrany 2y agoI thought that at first, but the article literally says "getting their big PR out".
- DanHulton 2y agoYeah, but again you might be being too literal. You could get a half dozen "big PRs" out in a month or so, but you'd still want to be able to just focus on "getting your (current) big PR out", you know? The important part is that you're not interrupted during your large-scale tasks, not the absolute length of those tasks.
- Kinrany 2y agoThat's fair: even if their team has a problem with PR size, this doesn't have all that much to do with the pattern the article describes.