"If you can’t explain it to a six-year-old, you don’t understand it yourself"
(By the way, do you spot the misunderstanding of the quote? It states that you must be able to explain it to a six year old, not that you should always express yourself that way)
And Morten was surprised by the negative reactions of some of the public, as he explains in this post.
I just had to take exception, and did it in the reply that follows.
No, sorry, I cannot agree. I do concur that one should express his ideas in the simplest possible way — but not any simpler, lest the ideas get distorted.
Besides, I think simplicity is a feat one should achieve because he thinks about it — not because it’s been given a crippled tool that forces its owner to do strange stuff. In a way, that (leaving stuff out of a tool because you don’t believe in, or know about, it) is a typical approach of some brand of software design — the email application that assumes that your username will always be equal to your email address, last sighted on windows, is an example.
Not to mention the many fields of endeavour where the original Einstein’s quote is, quite simply, bullshit. Art prose. Poetry. “Serendipity”. Formulating the sentence “Swift is a Multi-paradigm (Protocol-oriented, object-oriented, functional, imperative, block structured) programming language” without bizarrely contorted and extended paraphrases (which I should be probably expressing as “weirdly restating its meaning using other words in much longer sentences” — see?). This happens because unusual words (especially when domain specific) synthesize required prior knowledge that would make expression unbearably long winded without making it any simpler, or clearer. Einstein himself wrote “covariant bidimensional tensor” when needed — how does that come out under the 1000 words rule?
Also, I find the idea that simple words enable clear expression incredibly naive — germane to the idea that good coding style is a feature of the programming language, rather than the programmer’s. Confused thought breeds confused and confusing expression, vocabulary breadth notwithstanding. (See Gargantua and Pantagruel for amusing examples)
Does all this amount to make your editor a tool apt to “dumbing down” (rather than simplifyng) communication? Yes, I am afraid it does.
And one last point. English (my second language) has accepted into its fold words that come from many other tongues: latin, french, german, indian, native american. The subset of english words that are familiar to— and therefore immediatley usable by — an Italian is widely different from the one a German — or a Jamaican — would recognise. I have the idea that this alluring diversity within linguistic unity fares rather poorly under 1,000 words rule.
And I really loved what Brian Luff said (same thread):
"... although Orwell may have said
Never use a long word when a short one will do
he clearly did not mean
Never use a long word.
As far as I know, he never said
Why use a long word when you can use a lot of short ones instead?
How many short words would I need in order to suggest that your premise is an absurd extrapolation?"
2 comments:
I don't recall writing "never, ever use complex words" anywhere. Nice post aside from that.
I'd say it's about audience. I'd never tell anyone in my family that “Swift is a Multi-paradigm (Protocol-oriented, object-oriented, functional, imperative, block structured) programming language.” I wrote the app in Swift, and I'm not even 100% sure I understand that sentence :)
I don't recall writing "never, ever use complex words" anywhere.
You didn't, in fact. And most of the jargon argument revolves, as you correctly point out, about the audience one is addressing.
When your editor is defined as a training tool to hone a particular writing skill, noone can - I think - take any exception. I am particularly fond of the parallel - drawn in the comments - with the compositional exercise of doing scales, or of creating a tune given just 4 notes, or just using whole steps.
However I believe a more fundamental problem lies (quite clearly, outside the software itself) with the apparent equation of simple expression and limited vocabulary. Of course one can produce forbidding prose by unnecessarily stacking polysyllables, desuete words and idioms (a standard lawyerly trick, I think) - and your software is a nice antidote to that.
But obscure, meaningless or confused expression can be enabled - or even enhanced - by a limited vocabulary - Valley speak like, just, like, I mean, you know? Thought so. :-). Against this, the only antidote is clarity of thought, a domain where software does not reach (yet?).
As for the Swift quote, that comes from the WP page I happened to have open at the time, and it came handy as a jargon laden example. At a second reading - as you point out - it's not a really great one at that. Protocol-oriented is quite hard to grok, and it may even be, well, bullshit, AFAIK.
Thanks for stopping by.
Post a Comment