I am a programmer hobbyist (self learnt), and once in a while I like to make games and interactive scripts (nowadays mostly in JavaScript for its ease).

Sometimes I start long projects that end up being forgotten because of other things I have to do.

Sometimes a project gets really big (say, 3000 lines is a huge deal to me).

My code is mostly uncommented, unorganized, and unoptimised and some of my projects are never finished.


  • What do programmers (or teams), do with such projects ?
  • Is there a recommended practice regarding this issue in the "real world"?

closed as too broad by gnat, user40980, GlenH7, Wayne Molina, amon Aug 10 '14 at 15:01

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Document your code and put it on GitHub. You never know, it may help someone someday. – Umut Seven Aug 7 '14 at 5:34
  • You can organize your projects into what is almost done, half done, barely started. Then you can choose to share what is almost done so that people can learn and make better what you have. You might learn something from them too, but this might be hard as there might be disagreement when something is proposed. Good luck. – InformedA Aug 7 '14 at 6:47

I have a simple counter question for you: what do you want to do with those?

Personally, my take on this is if it's a hobby, you should do only what is fun for you. Nothing else. If it spells work for you, or a big time investment, then just forget about it.

You should not think of these projects as a sort of failure in any way. I have dozens, maybe hundreds of these things lying around or already discarded, and I don't worry about that for even a millisecond. As opposed to you, I am a professional developer, so these are my practice playgrounds. I toy around with new technology, interesting ideas, etc. and I never plan to make a huge kick-ass game out of it that hundreds or thousands of players will play. If you keep your naivety under control and start your projects without having such a dream, then not finishing it all up is perfectly fine. If you want something to show for the time you spent on this hobby, then you should maybe switch from games to graphic demos, i.e. switch to something with a much much shorter time-frame needed for its completion. But as you already learned - getting those last 5% done takes about as long as the first 95% took.

Finally, if you have any plans to turn this hobby into a career, then don't throw away the code. Just let it rest. Come back to your old code after a year or two for a very instructive experience. It will show you how much better you got in the meantime - the typical reaction to one's old code is "oh my.. did I really write code like that once?". And if you take the project on again, you'll get some valuable experience with regards to developing with legacy code bases. By the time you will have forgotten all of the intricate details, all of your great design plans. Your documentation may be outdated and your dependencies may no longer be available, etc etc. in short: you got yourself the real world deal. Be warned though: this is not even remotely as fun as writing your own stuff from scratch, so I'd only advise to go down that rabbithole if you want to get farther than it just being a hobby.

In summary: stop worrying. Adjust your view of what you want to get out of the hobby and accept the consequences.


You can first do us a favor and stop writing big, hard-coded, uncommented, 3k lines of code. Some of us (myself) like to code for fun and are willing to continue the project, if you just post it up on GitHub for the community.

  • 2
    "stop writing big, hard-coded, uncommented" code -- this advice is based on quite a shaky assumption. We only have OP words for it, but reality may turn out opposite, see Impostor syndrome: "Despite external evidence of their competence, those with the syndrome remain convinced that they are frauds and do not deserve the success they have achieved" – gnat Aug 7 '14 at 9:51

Not the answer you're looking for? Browse other questions tagged or ask your own question.