Depends on your industry and where you work obviously. But I have a strict "that will do" policy. If it looks like it might work, that will do.
It won't' be well engineered, it will be buggy. But the project will be completed and released. If it makes some sales and looks like it has some traction, then I go back and visit the many (many) //todo - clean this up and refactor everything out.
Usually after a while of adding more features, hacking out nasty design decisions the best way on how to do it comes to the fore naturally.
It won't' be well engineered, it will be buggy. But the project will be completed and released. If it makes some sales and looks like it has some traction, then I go back and visit the many (many) //todo - clean this up and refactor everything out.
Usually after a while of adding more features, hacking out nasty design decisions the best way on how to do it comes to the fore naturally.