I definitely see the value in taking the time to design things correctly and making sure you're evaluating all angles — I'm not sure if it's 100% necessary to say that to do that you always need to be slow though.
I think the difference between a fast programmer and a slow programmer often isn't that the slow one is methodically designing and making everything perfect, it's that the slow one has so many more inefficiencies in their workflow.
A good and fast programmer generally knows their tools inside and out, and they're willing to learn new tools when they need to (and not dismiss them because their current setup works good enough and it's what they know).
Speed isn't an indicator of good or bad quality. I would say that both mastery and improvement of tool is more of an indicator.
I think the difference between a fast programmer and a slow programmer often isn't that the slow one is methodically designing and making everything perfect, it's that the slow one has so many more inefficiencies in their workflow.
A good and fast programmer generally knows their tools inside and out, and they're willing to learn new tools when they need to (and not dismiss them because their current setup works good enough and it's what they know).
Speed isn't an indicator of good or bad quality. I would say that both mastery and improvement of tool is more of an indicator.