Keeping Simple Explanations Respectful
A recent post by Sumana Harihareswara on plain language choices touched on a familiar problem: writing about complex topics in simple terms without sounding like you're talking down to the reader. The challenge is real, but there are practical ways to approach it.
Keep Some Jargon for Searchability
Stripping out every technical term can backfire. If a reader encounters a completely jargon-free explanation, they have no way to search for more information or connect what they're learning to the broader field. Including the relevant terminology — even briefly — gives the reader a hook for further exploration. It's a balance: explain the concept simply, but hand over the keywords that will let them go deeper on their own.
Make Explanations That Are Actually True
It's tempting to simplify to the point where an explanation is more of a metaphor than a fact. The problem is that a "plain language" explanation that isn't real in any useful sense doesn't help anyone. If the truth is hard to express simply, it's better to acknowledge that than to offer a story that will have to be unlearned later.
Sometimes the process reveals your own gaps in understanding. If you can't write a clear explanation, you may not know the topic as well as you thought. That's a useful signal. When the explanation is genuinely difficult, it's honest to say what you're sure about and flag what you're not.
Reserve Visual Flair for Clear Content
Fun illustrations and playful framing can make a topic feel approachable, but they only work if the actual explanation holds up. When visual elements are added to text that is still muddled, the result is confusing rather than inviting. The charm should reinforce clarity, not substitute for it. A good example of getting this right is why's poignant guide to Ruby, which pairs a distinctive, playful presentation with genuinely clear teaching. Similarly, a master's thesis that was printed as an illustrated paperback succeeded because the writing was already accessible — not because the drawings carried it.
Use Stories That Serve a Purpose
Narrative can be an effective teaching tool, especially when it falls into one of two categories. The first is a real problem you encountered, which motivates why a concept matters. The second is a literal storytelling of what happens on a system — like howdns.works, where each step in the story corresponds exactly to what occurs during a DNS query. Stories that don't fit either mold risk feeling pasted on: they add flavor without illuminating the topic or giving a reason to care about it.
Know Who You're Writing For
It helps to assume your audience knows something already. If someone is reading about a niche technical issue, they probably don't need a primer on the basics of the field. Starting from zero can feel condescending, not because you're simplifying, but because you're targeting the wrong level. Pick an audience that has some context and write to them, rather than aiming at a generic beginner.
Jokes About Complexity Are for the Already Initiated
There's a category of writing that uses extremely restricted vocabulary as a kind of comedy — like a version of Gödel's Second Incompleteness Theorem in one-syllable words. It's enjoyable, but its real audience is likely people who already understand the material. The allusions are charming only if you can decode them, and decoding them requires knowing that "math is not a load of bunk" means "Peano arithmetic is consistent." Otherwise it's just cryptic. The same applies to the XKCD Up Goer Five: delightful, not necessarily educational.
Simple explanations don't have to be condescending. The goal is to present an idea at exactly the level of complexity it requires — no more and no less. That's not dumbing anything down; it's respecting the reader's intelligence while giving them a clear path forward.
