[jgreenough]

This type of conversation begs the "put-up or shut-up answer" and if it works you get a new feature. the real trick is actually dealing with long-term support for something that might have started out as a hack. Features and short-term tests usually need to be refactored for long-term health. If you don't do the work up front be prepared to do a bit later, just make the choice consciously.

[laconian]

NOnononononono.

If it "works" superficially it will be considered good enough by management. High fives all around, the checklist is ticked off, and everybody moves on -- except for the poor developers have to maintain the mess.

Nimbleness doesn't mean creating crushing technical debt that has to be solved immediately by somebody else. :)