Truly a great essay... When I reread it a couple years ago I made the semi-serious connection to bad but all too common object oriented programming practices as

Truly a great essay... When I reread it a couple years ago I made the semi-serious connection to bad but all too common object oriented programming practices as exemplified in Yegge's http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom... Orwell says: > As I have tried to show, modern writing at its worst does not consist in picking out words for the sake of their meaning and inventing images in order to make the meaning clearer. It consists in gumming together long strips of words which have already been set in order by someone else, and making the results presentable by sheer humbug. The attraction of this way of writing is that it is easy. It is easier -- even quicker, once you have the habit -- to say In my opinion it is not an unjustifiable assumption that than to say I think. If you use ready-made phrases, you not only don't have to hunt about for the words; you also don't have to bother with the rhythms of your sentences since these phrases are generally so arranged as to be more or less euphonious. When you are composing in a hurry -- when you are dictating to a stenographer, for instance, or making a public speech -- it is natural to fall into a pretentious, Latinized style. Tags like a consideration which we should do well to bear in mind or a conclusion to which all of us would readily assent will save many a sentence from coming down with a bump. By using stale metaphors, similes, and idioms, you save much mental effort, at the cost of leaving your meaning vague, not only for your reader but for yourself. To me it's a funny, semi-serious connection. I see many Javalanders are very happy with Java, and have been for quite some time. For them it's easier, and quicker once they're in the habit, to fire up Eclipse (or IntelliJ), autocomplete and autorefactor and glue together this and that without having to think much (hey tests are green!), sling giant names and namespaces around dozens of files and directories up and down various call stacks in and out of giant systems like Spring and Hibernate, a few even try to match large programming patterns to everything... Yet still they frequently fail to convey in code just what exactly is actually happening. In many cases they just needed a few functions in a file or two with concise names that can be remembered and typed without assistance, even written faithfully on paper without having to use shorthand.