Short version rephrasing of the rule: put a prototype into production.
You can see how it is obviously bad.
Typically cleaning up a dirty version is VERY hard. Takes much more time than rewriting assuming you wrote proper functional tests.
Likewise you cannot make a truly wrong design really fast without redoing it.
I would flip the rule on the head: design so that it can be made fast, is easy to get right, therefore will work.
Now if you have the experience to know beforehand what abstractions you need because you've done this many times, of course you can start cleaner; you do things dirty when you're unsure of what abstractions you might need and don't want to get hung up in trying to invent an abstraction before you know you need it.
It is usually better to just write it out and discuss instead of following through based only on your own gut, however good it is.
Make it work is the dirty version, always comes first without thought of proper factoring or abstractions. Once working and under test, it's much easier to then make it right, which is factoring out duplication and fixing up the code to be clean and well factored. Then and only then if something is too slow and a profiler shows a problem do you make it faster.