6 ms·
I think it's jsut fine to leave such a project up, with "I've abandoned this / I learned what I wanted to from this effort". Adding a note explaining where you
by h2odragon 5y ago
I think it's jsut fine to leave such a project up, with "I've abandoned this / I learned what I wanted to from this effort". Adding a note explaining where you think its flawed and other current thoughts on the matter is good too. If you come back to it later those will help; if someone else takes it up or is just poking at it for tips; also helpful.
If you never look at it again, it may at least give someone else an answer to a question or a tip on how to solve their problem sometime.
- Delk 5y agoI'd kind of like to approach this the way I was taught to approach university programming projects years ago: shortcomings are fine if you document them, as long as you've written something that at least mostly works. Especially in learning projects, an honest effort and an awareness of potential issues should be enough, and documenting them allows a potential user to make informed decisions of their own. The worst-case scenario should be that a potential user ignores your project because it doesn't answer their needs. I don't know how companies approach these kinds of things but I think it would make sense for them to appreciate an awareness and a realistic assessment of potential issues over perfection.