Thinking from a convo today about keeping things in static or dynamic forms -- as much as it may be tempting to make things always evolving, dynamic, etc. when you're just starting out -- the more experience I get, the more I believe in the importance of cutting stuff off and making it static (with some exceptions). Reasons to follow as unlisted thread...
1. Unless it's really, truly your life's work, you won't actually maintain/update something forever.
Reasons range from tech requirements to new interests. It's also an extraordinary burden if you think "but I must keep this thing up-to-date" and it's not tied into your everyday life's work so you feel guilty if it goes out of date. Not committing to update means if it goes out-of-date, well, it was written in 2010 and that's how it is.
2. Almost all projects require one to say "ok, done, good enough for this iteration." Otherwise it's very hard to push out the door. There may be some cases where committing to update helps you decide to release a thing, but that's pretty rare.
One example of doing that might be that I create a tutorial and say I'll update with feedback to clarify.
3. Gosh it's embarrassing sometimes to look back at things you said and realize you should've had a better picture but simply updating all the time makes it hard to track the growth and development of your ideas.
I've absolutely been known to scrub stuff from the internet when I really disagree with it now. But other times, you have to be willing to say "I was wrong, this is how my ideas have changed" vs. update it to look like you've always been where you are now.
@ronallo which one?
@ronallo ohhh yeah, I remember that tool!
@platypus I keep hoping folks will forget about it and stop using it!
code4lib.social is one server in the network