Blog / projects
When to shelve a project, and how to do it well
Most things people start do not ship. Stopping is a normal part of building, and doing it deliberately is better than letting a project fade away.
Signs it may be time
- You no longer want to use it yourself.
- The idea changed and the project did not.
- You are avoiding it.
- Something else matters more right now.
Shelve, do not abandon
Shelving means you decided to stop, and said so. Abandoning means you stopped answering. The first leaves a clear record and the second leaves a question mark.
Write the last entry
Explain what you built, what you learned, and why you stopped. Be honest and specific. It helps readers understand the project and helps you close the loop.
Keep what is worth keeping
- Reusable code and ideas.
- Lessons about the tools you used.
- The log itself.
You can come back
Moving a project out of shelved is just another entry. Many projects return after a break, and the history is already there.
Keep your own build log
Write numbered entries, follow other builders, and let people watch your idea become real.
Join vibFolio