> When I develop a feature, I usually follow these steps: 1 Make it work: a mandatory, crappy implementation that gets the job done. 2 Make it right: a nic

> When I develop a feature, I usually follow these steps: 1 Make it work: a mandatory, crappy implementation that gets the job done. 2 Make it right: a nice-to-have step, improving code maintainability and reusability. 3 Make it fast: by this point, I’m already moving on to the next class or method, driven by the need for speed. What does #2 mean to you? Why not cut it out for speed?