I'm not sure you necessarily disagree with the article. He argues against the "do the simplest thing that could possibly work" principle. He basically says, don't release code that isn't properly thought through if you do something that many others will depend on. You are saying something quite similar, but you stress the importance of running usability tests _before_ releasing code as thinking alone might not be enough. I agree with that, but it's not the same as saying ship the simplest thing that _could_ possibly work. Quite the contrary.
Comments
I'm not sure you necessarily disagree with the article. He argues against the "do the simplest thing that could possibly work" principle. He basically says, don't release code that isn't properly thought through if you do something that many others will depend on. You are saying something quite similar, but you stress the importance of running usability tests _before_ releasing code as thinking alone might not be enough. I agree with that, but it's not the same as saying ship the simplest thing that _could_ possibly work. Quite the contrary.