<story><title>Just Simply – Stop saying how simple things are in our docs</title><url>https://justsimply.dev/</url></story><parent_chain><item><author>sametmax</author><text>It&amp;#x27;s a more and more popular opinion:&lt;p&gt;- Why not tell people to &amp;quot;simply&amp;quot; use pyenv, poetry or anaconda (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bitecode.substack.com&amp;#x2F;p&amp;#x2F;why-not-tell-people-to-simply-use&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bitecode.substack.com&amp;#x2F;p&amp;#x2F;why-not-tell-people-to-simpl...&lt;/a&gt;)&lt;p&gt;- Don’t use the word ‘simply’ (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;jameshfisher.com&amp;#x2F;2017&amp;#x2F;02&amp;#x2F;22&amp;#x2F;dont-use-simply&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;jameshfisher.com&amp;#x2F;2017&amp;#x2F;02&amp;#x2F;22&amp;#x2F;dont-use-simply&amp;#x2F;&lt;/a&gt;)&lt;p&gt;- Stop using ‘simply’ in tech instructions (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.parkersoftware.com&amp;#x2F;blog&amp;#x2F;stop-using-simply-in-tech-instructions&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.parkersoftware.com&amp;#x2F;blog&amp;#x2F;stop-using-simply-in-tec...&lt;/a&gt;)&lt;p&gt;- Don’t say “simply” in your documentation (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.knowledgeowl.com&amp;#x2F;blog&amp;#x2F;posts&amp;#x2F;dont-say-simply-jim-fisher&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.knowledgeowl.com&amp;#x2F;blog&amp;#x2F;posts&amp;#x2F;dont-say-simply-jim-...&lt;/a&gt;)&lt;p&gt;And I strongly agree. It can be so discouraging to fail at something you should &amp;quot;simply&amp;quot; do.&lt;p&gt;But to be fair to the technical writers, it&amp;#x27;s easy to write that way without noticing, even after proof reading. This should be automatized by writing tools.&lt;p&gt;Also, while it&amp;#x27;s mildly irritating, there are worse things in life.&lt;p&gt;Yet as the first link about the python ecosystems notes, it usually hides a bigger problem: many devs are too good to be helpful.</text></item></parent_chain><comment><author>wdfx</author><text>Similarly, one should never state that something is &amp;quot;obvious&amp;quot;.&lt;p&gt;I catch myself sometimes starting a sentence with &amp;quot;Obviously,&amp;quot; and usually stop myself at that point and restart.</text></comment>
<story><title>Just Simply – Stop saying how simple things are in our docs</title><url>https://justsimply.dev/</url></story><parent_chain><item><author>sametmax</author><text>It&amp;#x27;s a more and more popular opinion:&lt;p&gt;- Why not tell people to &amp;quot;simply&amp;quot; use pyenv, poetry or anaconda (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bitecode.substack.com&amp;#x2F;p&amp;#x2F;why-not-tell-people-to-simply-use&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bitecode.substack.com&amp;#x2F;p&amp;#x2F;why-not-tell-people-to-simpl...&lt;/a&gt;)&lt;p&gt;- Don’t use the word ‘simply’ (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;jameshfisher.com&amp;#x2F;2017&amp;#x2F;02&amp;#x2F;22&amp;#x2F;dont-use-simply&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;jameshfisher.com&amp;#x2F;2017&amp;#x2F;02&amp;#x2F;22&amp;#x2F;dont-use-simply&amp;#x2F;&lt;/a&gt;)&lt;p&gt;- Stop using ‘simply’ in tech instructions (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.parkersoftware.com&amp;#x2F;blog&amp;#x2F;stop-using-simply-in-tech-instructions&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.parkersoftware.com&amp;#x2F;blog&amp;#x2F;stop-using-simply-in-tec...&lt;/a&gt;)&lt;p&gt;- Don’t say “simply” in your documentation (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.knowledgeowl.com&amp;#x2F;blog&amp;#x2F;posts&amp;#x2F;dont-say-simply-jim-fisher&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.knowledgeowl.com&amp;#x2F;blog&amp;#x2F;posts&amp;#x2F;dont-say-simply-jim-...&lt;/a&gt;)&lt;p&gt;And I strongly agree. It can be so discouraging to fail at something you should &amp;quot;simply&amp;quot; do.&lt;p&gt;But to be fair to the technical writers, it&amp;#x27;s easy to write that way without noticing, even after proof reading. This should be automatized by writing tools.&lt;p&gt;Also, while it&amp;#x27;s mildly irritating, there are worse things in life.&lt;p&gt;Yet as the first link about the python ecosystems notes, it usually hides a bigger problem: many devs are too good to be helpful.</text></item></parent_chain><comment><author>kqr</author><text>I remember reading one of those and it made a huge impression on me. I&amp;#x27;ve followed it ever since and taught others to do the same. As far as I can tell, it has only been met with appreciation.&lt;p&gt;That said, sometimes I find myself trying to write around &amp;quot;simple&amp;quot; when I really mean &amp;quot;less complex&amp;quot;, and I have to remind myself that what I really want to avoid is implying &amp;quot;easy&amp;quot;, not &amp;quot;relatively less complex&amp;quot;.</text></comment>