My work is loosely based around IT, and I'm old enough to have had some experience of program code. I am probably the last bloke you'd want to write your code for anything, but I have an idea how some of it works. One of the things that more geeky (technically able) programmers will sometimes observe is that there can be many ways to achieve a desired result.
Whilst all of them may do what is needed, some will be more elegant and attractive than others. Some may make it easier to modify the code in the future, some may get things done faster, some more efficiently. To the person who has an eye for this knd of detail, the "raw" code behind a piece of software or even a website may be a thing of beauty or an ugly train crash, even though a casual observer or even user of the software may never even see what's below the surface.
So it is with English. There are so many ways to say things, and some of the most ugly cliches do convey a meaning. I was smirking because the bloke next to me at the coffee stall his lunchtime was one of the foremost proponents of the business cliche. He was explaing to a colleague that there was an "incredible scenario" at one of their "stores" because one of the managers had punched a colleague. He had managed to get reinstated, but various staff members were refusing to work with him. Meanwhile, another manager was "in limbo" managing two "stores" and was a bit "like a rabbit in the headlights".
This chap was making his point, but in a way I found inelegant, however since he plainly has no interest in the words he uses, I couldn't reasonably expect him to say it in any different way, nor should I. I have to accept that not everyone cares what words they use, any more than they care whether the bloke who wrote their website indented his code.
