Thanks very much for your comments. I wasn’t aware of the distinction between simile and metaphor. A better title could have been Figures or speech in software development, if I understand Wikipedia and Webster, although it might sound less catchy.
You’re absolutely right on writing posts. I should have proof-read my post a whole lot better. Just as with wrong metaphors, when text is grammatically ill-written, it’ll be less-understood as well.
I’ve updated my post; hopefully most of the grammar and spelling errors are gone.

Indeed we use metaphors to express emotion, to explain things. We use them to make our descriptions more vivid and alive and sometimes they are just used to entertain. But mostly intended to let you see what you hear, or give an image to what you read. A picture tells you more than a thousand words, isn’t it?

This is done by developers and non-developers. We use metaphors every day and some people use them all the time. Most metaphors are actually similes. They are used to compare things and start with ‘…. is like’ or ‘as ….. as’. Metaphors and similes are analogies. You use both in your post.

Unfortunately some analogies are ill chosen, I have to agree with you on that. We have to watch out for these ones, for they could be meant as smoke screens and do exactly the opposite.

As your spelling checker wasn’t ‘on’ as you wrote this post, typo’s were as common as Belisha beacons on zebra crossings. That’s a simile, as you can see
Quality without compromise. That applies to software development and to writing posts: experience = experienced, there = they are, time = times, ratter = rather, now = know, wetter = whether, then = than