This article undermines itself the second it moves from “here’s the problem” to “here’s the solution:” > Be mindful of not leaving your codebase in a broken st

This article undermines itself the second it moves from “here’s the problem” to “here’s the solution:” > Be mindful of not leaving your codebase in a broken state during this step You’re still relying on very fallible human intervention here. Even worse, often times when grouping commits post-facto you’ve forgotten some of the context of what depends on what. Ostensibly the approach presented could be better than other strategies in this regard, but that’s now how the article presents itself and it loses credibility for that.