I'm not sure that's a fair summary of the article. I just reread it: at no point does it suggest removing superfluous words in general, it's specifically about "words such as easy, painless, straightforward, trivial, simple and just", because those in particular are "jolting", "upsetting and annoying" and "infuriating". What you frame as an "aside" is in fact the first and last paragraph of the article.
> I have no idea why you'd think this implies some personal failing or that it is advice for "babies"
You're missing a level of indirection here, it's advice for people who write for people who act offended when reading "simply" in technical documentation, and I'm questioning the dynamics of that.
It's obviously fair to criticize the word choice on my part, there were obviously less incisive ways to phrase that. But then, it's the article that claims that the usage of the word "just" in the sentence (the article's example) "[then] we will just edit the users_controller.rb" is "condescending", and I think that's simply (sic) insane.
* "(Just like) Starting Over" has 'just' in the title and lyrics.
* "Just" gimme some truth.
* "I'm just a jealous guy"
Rules are meant to be broken, perhaps? Or maybe he would just cop to being lazy?
And paraphrasing: Imagine there's no absolutes. It's easy if you try.
both?
the quote i paraphrased was from hunter davies' authorised biog of the beatles
but i still think it is a good rule
Most people are comfortable making incremental improvements in all our tools and comforts in life, so why should communication (the greatest tool of all!) be any different?
We can make a knife or keyboard with a better handle, and it's called "ergonomic." Nobody claims someone being a baby for wanting that.
Meanwhile, a small suggestion to enhance how we handle communication is met with such severity and perceptual distortions, as though the ones making the suggestions are having some breathless emotional psychosis. Why?
Please reread the comment you are replying to. He’s talking about the hacker news comments.
"Stop saying how simple things are in our docs"
"Or maybe -- controversial opinion here -- people shouldn't be such babies"
If you continue reading to the next sentence, it becomes explicitly clear that he is addressing the comments here.
tbh I enjoy when documentation gives me an idea of the effort required to go trough it. is it just copy pasting commands? does it require any configuration for achieving different goal? am I supposed to handle prerequisites on my own? Is there any passage that require my attention or everything will break down the line?
now, "simple" may not be the correct wording for it, but still I wouldn't say that there's no value in indicating the effort beforehand.