Unlike your coworker, I _always_ have a plan. Often a dozen of them. With various pros and cons for each. But also unlike your coworker, I probably _figured ou

Unlike your coworker, I _always_ have a plan. Often a dozen of them. With various pros and cons for each. But also unlike your coworker, I probably _figured out how to do it right_ in the time given. It's pretty rare that I don't have time to do it right; it does happen (especially with extreme instances of scope creep and requirements drift), but it's rare. Which I guess is your point? The time excuse is just an excuse, and a good developer writes good code.