> Imagining future possibilities and implementing software to account for them are two different things.

True.

> The argument here is to validate those possibilities before acting on them.

I agree this should be done. It's not clear that was the original argument, because the same guy previously wrote:

> The number 1 issue Ive experienced with poor programmers is a belief that theyre special snowflakes who can anticipate the future.

"The future" is a not-so-special case of "the now."