2 ms·

Honestly as dumb and petty as it sounds. The only goal I see to finishing software projects is to be able to say with confidence that your implementation is bet

Honestly as dumb and petty as it sounds. The only goal I see to finishing software projects is to be able to say with confidence that your implementation is better then somebody else's code or project on a technical level. To have a project as a proof of understanding. Its one thing to say, "Yes I understand how to do dec64 math." Its another to say, "Yes I understand dec64 math, here's my implementation." Its kinda stupid I know, but that's literally my frustration with not completing projects. Its petty, so I don't indulge it.

ralmeida 12y ago
That's somewhat competitive, but I wouldn't call it a problem. Maybe you should redefine what kind of projects you tackle? From your definition, you could call a project "done" by the time you implement the dec64 math library, or whatever challenge is in the project. Why don't you just release the library as open-source? This would give you a sense of accomplishment (because you did complete something), and possibly pride, if the library becomes popular. A key point is it being open-source, though: so you can focus only on releasing the "proof of concept", but letting other people focus on the details, the edge cases, and the fixes to mundane but show-stopping bugs that make the project battle-hardened, production-ready.