Going to be that guy, even though I think this is a really nice work overall...
But the winking and "cool guy" emojis are so grating. In general, technical explanations that apologize for themselves with constant reassurances like "don't worry" and "it's actually simple" undermine their own aim.
Your job -- if you're making content for people with double digit ages -- is to make the explanation as clear as you can, not to patronize and emotionally hand-hold the reader.
No, your job is to help your reader get to the end of the text. That means writing in a way that most of your audience finds compelling, readable, and not intimidating.
Not all readers are the same, so you will fail at your job for some readers.
But few readers are emotionless automatons that need nothing but dry technical content, unless it’s a topic they are very motivated to understand.
> That means writing in a way that most of your audience finds compelling, readable, and not intimidating.
I would agree with that. And I think emojis and unnecessary reassurances subvert that goal. It's fluff, it's more to read, and if the writing isn't already clear, they don't fix the problem.
> But few readers are emotionless automatons that need nothing but dry technical content
Nothing in my post argues for dry technical content.
Bartosz Ciechanowski's superb work, which may have inspired the author, gets the balance just right without any hand-holding asides:
But the winking and "cool guy" emojis are so grating. In general, technical explanations that apologize for themselves with constant reassurances like "don't worry" and "it's actually simple" undermine their own aim.
Your job -- if you're making content for people with double digit ages -- is to make the explanation as clear as you can, not to patronize and emotionally hand-hold the reader.