I’ve got several good comments on my post A good answer or a fast answer .
Among others, I’ve noticed the one from Prashant of Agile Analysis blog .
Let me quote the core of his comment:
Mind you, a dirty solution is not a wrong one – it is simply not the ideal one.It just means we take on technical debt or have a manual workaround.
I agree with his point: a dirty solution is not (necessary) a wrong one.
And as a general rule I prefer to think that making a technical debt is wrong! And … having someone in the team who’s able to decide when it’s time to make that mistake is a GREAT value.