This is exactly the mistake from http://lesswrong.com/lw/ix/say_not_complexity/

I'm not sure it is. That's about claims of the form "Doing X needs complexity, so if we shovel in enough complexity we'll get X", whereas Gram_Stone is saying something more like "It looks like no simple model will do X, so any that does X will necessarily turn out to be complex".

The lesson from "Say not Complexity" is not that it's untrue that complexity is needed. It is that to assume at the beginning we need "complexity" or "messiness", is not a good heuristic to use when looking for solutions. You want to aim at simplicity, and make sure that every step that takes you farther from it is well justified. Debating beforehand whether the solution is going to turn out to be complex or not is not very useful.

In this sense, I see this as the same mistake.