zirk.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
Literature, philosophy, film, music, culture, politics, history, architecture: join the circus of the arts and humanities! For readers, writers, academics or anyone wanting to follow the conversation.

Administered by:

Server stats:

757
active users

#documentation

31 posts26 participants0 posts today

Over the past couple of months, I've been spending more time reviewing my tech notes from the last five years.

Partially out of a new interest in posting publicly & also trying to improve my writing.

Despite my placing numerous reference links & quotes in these notes, I feel that I'm really blurring the line between plagiarism, absorbing concepts & re-writing them in my own words.

These notes continue to be useful. Just can't quite place the source. A new imposter syndrome.

Ah, yes, the classic "blame the user" defense: Man pages are the epitome of pristine #documentation, and if you can't decipher them, it's obviously your profound incompetence. 📚🔍 Clearly, the real issue is that you peasants insist on using those pesky programs that don’t reveal the hidden wisdom of man pages. 🤦‍♂️
whynothugo.nl/journal/2025/04/ #blameTheUser #manPages #userExperience #techHumor #programming #HackerNews #ngated

whynothugo.nlMan pages are great, man readers are the problem
Continued thread

@gnuradio Here's the full list of #gnuradio block documentation pages that are mostly just missing an example flowgraph,

wiki.gnuradio.org/index.php?ti

and a list of block doc pages that are just stubs and would *love* to get some attention:

wiki.gnuradio.org/index.php?ti

You're not alone in this! If any questions/problems using the wiki or on GNU Radio #documentation in general arise, you can always find the docs on #Docs:gnuradio.org on matrix. Here's how you join the chat:

wiki.gnuradio.org/index.php?ti

wiki.gnuradio.orgCategory:Pages with no Example Flowgraph - GNU Radio

Documentation complaints.

The Curse of Knowledge is real in documentation; even big and pricey ecosystems skip basic information.

Two examples I ran into this morning:

1. GitHub's CODEOWNERS documentation does not explicitly mention where to create the file.

docs.github.com/en/repositorie

2. NPM's docs do not explain allowed characters in package names.

docs.npmjs.com/package-name-gu

GitHub DocsAbout code owners - GitHub DocsYou can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.

new & final status update on 'moving image zines rdam':

The complete archive (355 videos) from 2005-2025 has been uploaded & is available on archive.org: archive.org/details/moving-ima

All videos are downloadable as high-quality files [mp4/h264 codec, 32 Mbit/s] and reusable under the Creative Commons Attribution-ShareAlike 4.0 International license.

archive.orgInternet Archive: Digital Library of Free & Borrowable Texts, Movies, Music & Wayback Machine

All developers I've met in my career in IT, who insisted code is self-documenting were exceptionally bad in documenting anything :blobcatreading:

While their code usually ran just fine, they could hardly ever explain how it worked or why it was structured that way to someone else, especially junior developers.

Comments and annotations exists for a reason.