> If you don't ever have a massive PR from a dynamite session, then you cannot ever be better than "average and plodding".
That's just cope to avoid learning how to turn a big change into a well organized patch series.
That's just cope to avoid learning how to turn a big change into a well organized patch series.
I'm not saying one shouldn't learn how to stage large changes into a mature codebase. Sometimes the overhead is very worth it, maybe most times if you're close to the profit center of a faang. But one should understand multiple ways of working, for different situations.
I'm not being snarky. I put different review standards in place for different repos on my team. Sometimes the standard is no standard. Push to main. Figure it out later.