this post was submitted on 29 Jan 2026
46 points (97.9% liked)
Programming
25249 readers
626 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
Well the problem is trying to attach the concept of "done" to a bitstream. You can release it, but then the release is "done", not the software. You can evaluate software only in a specific cultural context, where it can be useful or not. Software is more similar to a law than to a fabricated pencil. Laws are updated and re-interpreted as the culture around them evolves, and they are "done" when the culture is done.
I like this quote:
In other words, a factory product is "done" when it passes QA. You can try to apply the same productivity mentality to software (or to laws) but it just doesn't make sense, because those are instructions how to do things, and not products to be consumed. It's not a factory product, it's a living cultural process.