3 ms·
Generally I agree that it's just not worth it to release projects and code that are unfinished or not very useful but there's often gems inside these things. H
by riskable 10y ago
Generally I agree that it's just not worth it to release projects and code that are unfinished or not very useful but there's often gems inside these things.
How many of us have struggled with something complicated and found some golden function or bit of code hidden inside some otherwise useless project that solves the problem? Even if you don't use such code it can still be incredibly useful for understanding how things work.
I often rip out the useful bits of unfinished/unreleased projects and just paste them to gist.github.com. Some of them have received comments like, "I don't know where this came from but it's exactly what I was looking for! Thank you!"
Posting your whole useless project can be helpful.
- quanticle 10y agoThe problem with releasing useless and unfinished projects is that when people are taking your github profile as your resume, they're going to be seeing a bunch of useless, half-finished projects. It doesn't make a very good first impression. For this reason, I'm increasingly moving my code off Github and onto Bitbucket. Despite having a worse UI, Bitbucket at least allows me to make private repositories for free, which means that I can make repos public if and only if I think it's ready for an interviewer to look at it.
- ch4s3 10y agoAnecdotally, as someone who occasionally I never "penalize" people for having lots of unfinished projects. If they try interesting things a lot, that's a plus.
- Allower 10y ago>How many of us have struggled with something complicated and found some golden function or bit of code hidden inside some otherwise useless project that solves the problem? Never