It’s actually just obviously simply really very trivial.<p>I find the Recurse Center’s social rules inspiring:<p><a href="https://www.recurse.com/social-rules" rel="nofollow">https://www.recurse.com/social-rules</a>
"Simply" and "it's easy" also fall into this trap too. I now try to avoid them when writing technical descriptions. You think something is <i>easy</i> and <i>simple</i> doesn't mean someone else will. When they read that, then struggle, it can put people off continuing to try. That could be a lost sale for you, or it could mean someone deciding that a career choice isn't for them.
Often "Just" is... justified. At least, as a question to understand why someone is doing something the hard way.<p>As the post ends with:<p>> We should try to understand what makes it hard. And make it easier.<p>Yes, and I often do that by asking a question like "Why don't you just use [X]" i.e. Someone is saying something like<p>"Transferring files between these two servers is too hard. It keeps timing out and then I have to look to see which files have already been transferred and manually skip those. Sometimes a file is present but incomplete and finding those is even more work"<p>Why don't you just use rsync?