My favorite quote from Mark Twain is “I didn’t have time to write a short letter, so I wrote a long one instead”. Indeed, brevity and clarity actually take time and analysis. I find this to be very true when writing requirements or documentation. Some of the worst requirements I’ve read have been extremely wordy and unnecessarily over-technical or jargon-heavy when it could have been explained in plain language. As usual, it very much depends on the target audience.
I think constraints essentially force you to reevaluate the thing from base principles because you add a condition that’s incompatible with the default way of doing things.
I think this is also why hackathons work: You can’t afford the bikeshedding we often do to avoid the hard work because you need to ship something by a deadline 1/500th of most of your normal deadlines, so all of your effort is concentrated into what moves the core work forward.
What gets proven in hackathons often become features, products, or companies later - even if they’re things that would be ruled out in any planning meeting because they seem too hard/laborious.
I'd say a lot of the value in "explain it to me like I'm ten" is just expending more time and effort in explaining something. People of all ages respond to engaging writing and clever analogies, and that tends to accompany the style of writing for a younger or broader audience.
The blog post isn't directed at 10-year-olds. In fact, you're pulling a phrase from a paragraph that's describing exactly how you should not speak when talking to a 10-year-old.
> The simplest constraint for anyone trying to explain a complex topic is to accept the request to “explain it to me like I’m 10 years old”. What’s packed into that request is, vividly exaggerated, the reminder that what seems obvious to an expert is often incomprehensible to the listener. Technical jargon and fusillades of acronyms are often used to convey an explanation that has been denuded of all the foundations and context that might allow it to make sense.
It might be helpful to note that this article was written for the FT (as he mentions at the very bottom.) While it aphoristically may make a “pre out of you and me,” I presume neither the author, nor the subscribership of FT _are_ indeed (or wish to be) constrained to the language of a typical 10-year-old. Presumably the same would apply to the readership of HN.
We don’t know if the author _can_ explain it like we’re ten, but I think we can be reasonably certain they understandably chose not to.
Good thing they never claimed to be writing in that style then. Not sure what you're working yourself up over here. Authors are allowed to write about a method of writing without having to apply it themselves.
I think that the author is doing it deliberately, to put the reader in the shoes of someone who has a hard time understanding some of the words, and reinforce his point.
As a non-native English speaker there are 4 words in this article that I had to look up, which is significantly higher than a typical article from HN frontpage (usually it's 0, occasionally 1).
If anyone curious, the words are: pellucid, fusillades, pram (idk, why I never heard it. I knew the word "stroller", of course, but I never thought about different kinds of strollers), octogenarian (this one I could have guessed from Latin roots and context, was lazy).
> If you are reading this column you definitely aren’t a typical 10-year-old, but the image of the bewildered 10-year-old gives the expert an anchor to help them slow down and simplify [0]
I think this is also why hackathons work: You can’t afford the bikeshedding we often do to avoid the hard work because you need to ship something by a deadline 1/500th of most of your normal deadlines, so all of your effort is concentrated into what moves the core work forward.
What gets proven in hackathons often become features, products, or companies later - even if they’re things that would be ruled out in any planning meeting because they seem too hard/laborious.
Fusillades? No ten year old knows that word.
> The simplest constraint for anyone trying to explain a complex topic is to accept the request to “explain it to me like I’m 10 years old”. What’s packed into that request is, vividly exaggerated, the reminder that what seems obvious to an expert is often incomprehensible to the listener. Technical jargon and fusillades of acronyms are often used to convey an explanation that has been denuded of all the foundations and context that might allow it to make sense.
We don’t know if the author _can_ explain it like we’re ten, but I think we can be reasonably certain they understandably chose not to.
As a non-native English speaker there are 4 words in this article that I had to look up, which is significantly higher than a typical article from HN frontpage (usually it's 0, occasionally 1).
If anyone curious, the words are: pellucid, fusillades, pram (idk, why I never heard it. I knew the word "stroller", of course, but I never thought about different kinds of strollers), octogenarian (this one I could have guessed from Latin roots and context, was lazy).
Fusillades specifically was unfamiliar but I inferred if from context and knowing fusilier.
Why would you think that?
> If you are reading this column you definitely aren’t a typical 10-year-old, but the image of the bewildered 10-year-old gives the expert an anchor to help them slow down and simplify [0]
[0] TFA