mastodon.uno è uno dei tanti server Mastodon indipendenti che puoi usare per partecipare al fediverso.
Mastodon.Uno è la principale comunità mastodon italiana. Con 77.000 iscritti è il più grande nodo Mastodon italiano: anima ambientalista a supporto della privacy e del mondo Open Source.

Statistiche del server:

6,2K
utenti attivi

#TechDocs

0 post0 partecipanti0 post oggi
Adam Kaplan 🚌🚊🚢<p>The good news - software engineers know how to do these things, or can find help along the way!</p><p>My thoughts in detail here: <a href="https://adambkaplan.com/post/2025-03-15-docs-software-problem/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">adambkaplan.com/post/2025-03-1</span><span class="invisible">5-docs-software-problem/</span></a></p><p><a href="https://hachyderm.io/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://hachyderm.io/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://hachyderm.io/tags/writing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>writing</span></a> <a href="https://hachyderm.io/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>blog</span></a> <a href="https://hachyderm.io/tags/techdocs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>techdocs</span></a> </p><p>/end</p>
Adam Kaplan 🚌🚊🚢<p>To get our docs quality to match our code quality, we need to treat our documentation as a software design problem. Just like our code, we need to write documentation with clear goals of what problems we are trying to solve (and for whom!), a vision for our ideal end state, an understanding of the tools at our disposal, and a plan to organize our ideas.</p><p><a href="https://hachyderm.io/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://hachyderm.io/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://hachyderm.io/tags/techdocs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>techdocs</span></a> </p><p>/3</p>
Adam Kaplan 🚌🚊🚢<p>It is not surprising that most of the "bad docs" are maintained by software engineers, and unfortunately we do not apply the same rigor to our documentation as we do to our code.</p><p><a href="https://hachyderm.io/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://hachyderm.io/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://hachyderm.io/tags/techdocs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>techdocs</span></a> </p><p>/2</p>
Adam Kaplan 🚌🚊🚢<p>Lately I have been involved with open source projects that struggle with their documentation. It's easy to identify bad documentation out in the wild - many of us have an intuitive sense when a project's docs are hard to understand.</p><p><a href="https://hachyderm.io/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://hachyderm.io/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://hachyderm.io/tags/writing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>writing</span></a> <a href="https://hachyderm.io/tags/techdocs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>techdocs</span></a> </p><p>/1</p>