Easy: Most software is done when nobody uses it any more.
If the code you wrote 10 years ago still isn’t quite done yet, you should celebrate. If someone still cares enough to consider it broken, or can think of improvements, it means that it is useful. In contrast to: finished and done with.
Yes. I’m here for the long tail, the niche communities. And what do I see? Not enough photos of houseplants! Come on, you must have some too. And to add to the list, !books@lemmy.world looks nice.
I’m still proud of my rendering of the logistic map. It was mostly just to learn more Rust, but it rendered this beatuiful picture with relatively little code. And mostly by accident, I didn’t know I would get those cool shadows!
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.