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.
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.
> 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.
> 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