Re: ...-boffin
One man's hack is another man's release code...
Iterative design. Agile development. Nimble coding.
Unfortunately, those terms are often redefined to function as justification for poor coding, lack of planning, avoidance of testing, and a general disdain for user-focused design. In short - a hack.
An anecdote along the same lines. A number of years ago I found myself having to come up with all kinds of "workarounds" and "creative hosting solutions" to fix poorly coded applications. This lasted for years, until I started calling my 'creative solutions' and 'workarounds' by the happy name of "kludges".
Calling a spade a spade was quite satisfactory, especially in the titles of Change Requests. Oh, the fun I had defending my solutions in CAB-meetings! What do you mean by "Implement kludge to ensure data integrity"?
As expected, it caused quite a bit of consternation among management - especially on the development side of the house. Although I was pressured to refrain from calling my hacks "kludges" in the end it resulted in a focus on quality among the developers.