That may be true for the given example, but it doesn't work that way for all the nuances of code that come up. For one thing because English wording has ambiguities, and for another because there are so many concerns with some cross-cutting each other that you can only break things down into atomic functions to a certain degree.

I think the overall point of the article rings very true: great VCS habits pay dividends over time regardless of how well-crafted the code itself is.