And here's his response to the gist: https://gist.github.com/2838490#gistcomment-356060
What we need is a new acronym (well, maybe somebody has probably already coined it, but whatever) YPNGTNI: You're Probably Not Going To Need It.
As long as the code is easy to refactor - and in this case, it's a piece of cake - I think you should err on the side of YAGNI.
There need be no real danger of it ever becoming a drudge, for any processes that
are quite mechanical may be turned over to the machine itself.