this post was submitted on 01 Aug 2025
12 points (100.0% liked)
Programming
21903 readers
484 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Somehow that essay reminded me straight to the Guix documentation that I was working with earlier this day. So well organized and to the point. Pure joy.
And he is right in what he says that documentators should not be passive but take part in shaping their Gegenstand. Some of my best pieces of work, I wrote the docs in advance to functionality, or in parallel.
And then there is literate programming. This is the way we should write important, long-running software. I used this the first time when I took a new job and my new bosses just had managed to micro-manage their MATLAB and math expert out of the company. A few pages of critical code with probability calculus which nobody did understand. Fun stuff.
Just now I am looking at someone's code from the past twenty years. All that time working on the same stuff. Great guy. No docs. So sad.