"Quick 'n Dirty" vs. "Correct and Proper"?

A not-so Anonymous Coward enters this query: "I keep finding myself on projects where a quick and dirty solution will bring in money for the company, and a correct (ie, properly documented, well engineered, process followed, etc) solution will get us left in the dust. When the Q&D solution succeeds, I'm left trying to explain why it can't be the FINAL solution (to PHBs and Marketroids that were fully informed of the situation prior to any work getting done). Most recently, work I did in record time was used to help bring in several large contracts, and then I found myself in hot water for not having followed process et al. So, to Slashdot: is it better to do the quick thing and greatly increase the chance of $uccess now, or to do the correct thing and avoid pain later (assuming there is money to pay for the pain later)?"

Comments

Re:Not necessarily a dichotomy

[dasmegabyte]

XP is crap. Sorry, TRUE XP is crap. If you've heard of XP and think it's a good idea, do not make the mistake of reading anything about it. Just continue doing the part you heard about and thought was a good idea (like constant interaction with the customer or collaboration). Do not take the logical step and attempt to become a disciple of XP. You will either find yourself doing some of the stupidest things imaginable, or you will go insane. Visit softwarereality.com and you'll see what I mean.