> Just because something is recent, newer, or shinier does not make it automatically better.
Sure, but that's just your strawman. It's better because learning from the mistakes of the past leads to the avoidance of some of them, which happens even in computing. While you conceptually can easily male new mistakes it's a tough sell to reject progress altogether by decree
Otherwise hard to argue more specifically since there is nothing more specific in the post when extolling the virtues of the bad old ways:
> In fact, in this particular case I’d argue that the Git email workflow is far superior to the pull request workflow for a multitude of reasons, as I have so often said in the past.
Sure, but that's just your strawman. It's better because learning from the mistakes of the past leads to the avoidance of some of them, which happens even in computing. While you conceptually can easily male new mistakes it's a tough sell to reject progress altogether by decree
Otherwise hard to argue more specifically since there is nothing more specific in the post when extolling the virtues of the bad old ways:
> In fact, in this particular case I’d argue that the Git email workflow is far superior to the pull request workflow for a multitude of reasons, as I have so often said in the past.
A link to that blog would have been nice