I'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 lon

I'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.