What to do with a bunch of incomplete projects?

・1 min read


I have a github account since 2012, and I always publish any code that I do personally there. The problem is that I'm don't have too much focus and I jump from project to project without finishing anything!

I always put my github account on my CV, but do you think it may impact if an interviewer realizes that most projects are incomplete? Should I keep only complete stuff?


I don't think anybody would look down on someone for having incomplete projects on their GitHub.

If they are truly projects you would never need to look at again and they don't add any value to your GitHub you can always delete them.

If you may want to reference them in future but want people to know they are not actively being worked on you could always archive them.

I would also make sure that your pinned repositories on your GitHub profile page showcase your best work as that's probably where anybody will look first. More about pinning repositories

"The problem is that I'm don't have too much focus and I jump from project to project without finishing anything!"

You may want to try working on smaller, simpler projects as they tend to be quicker and you might be able to finish them whilst you still have momentum. Nothing beats the feeling of completing a project and pushing it up somewhere for the world to see!


Well said πŸ‘
I too have a problem focusing on anything. I have tons of stuff unfinished and not even published on git yet!
I start a project on local and it just stays there!!!


I think it is normal to have old projects there. However, you can Option 1. Put them in private or delete them. Option 2. Higlight the ones you are proud of in Resume, make a commit (correction: PIN) so they stay on top.


Adding to Option 2, instead of making a minor commit to them to keep them above the others, just pin those repositories on your profile and they'll be shown on your GitHub profiles overview page.


I did not know about pinning. I learn something new and useful today. Thx


Regarding the CV, I always put the two or three projects that I want to showcase with a short explanation of what the project is about and why I created it, and I link to those specific projects, never directly to my account.

With the project links, anybody with a bit of curiosity can browse any other of my projects, of course, but I think it makes the CV a lot more focused. When I review a CV, if there is a link to a GitHub profile, most of the time I don't even bother checking it out. I'm more likely to check out a couple of linked projects with an explanation of why they are interesting.


I tend to make my unfinished projects private, since I really do have a lot of them. I think that, unless it is clear from the start that the project is just an experiment, having unfinished projects could potentially affect your image.

But that's just my opinion 😬.


Every time I switch laptops or machines, I just leave all stuff on it. And move on. I have loads of projects of finished client work, unfinished client work, try-outs and side-projects.
The last 4 years I have been using bitbucket to store all things, so now I have about 75 codebases with all kinds of stuff., big and small. That helps for future reference, but in reality I never go back.
All of the projects are private, so I won't put it on my CV. If they want, I'll show them how I'd solve a problem. I do not worry much about the interviewer, because I have a good feeling about what I can and cannot do.


I have several organizations for incomplete projects. One is called "experimental-dustbin" and includes all the projects that are incomplete. My main account only has completed projects. You can do the same thing and only have projects on your main account that you think are reasonably finished to show off.


You don't need to max out the pinned repos on your profile, either.

I have 20 repos, the vast majority are incomplete. I have 4 forks I made in case the original deletes, so I archived those. Of the remaining 16, I could put 6 on my overview, but I only picked the 4 I thought actually showcased anything of note.


I think unfinished projects is fine, everyone have them.
But especially when you are looking for jobs, it is best to pin your best work on top at least.


Merge them all into one project. I'm sure it will work out just fine. I doubt that an interviewer will be downloading and running your project. If it doesn't run, here's a good opportunity to explain the timescale and challenges you face. Done projects are dead projects anyway.


I have a folder with all my projects,complete or incomplete and i make it private,then i have another with complete projects only that i put on my protfolio


I think it may have little impact to your interview.

And in my opinion, your technical blog will be the best candidate to be put to your CV.


There's actually a tag on dev.to for this now, so I wouldn't be ashamed, just show your graveyard. ⚰️


Inconsistency kills the dreams! You must work on this part first. Later then archive your half-finished projects, because they are kind of clutter now.

Classic DEV Post from Nov 19 '18

What’s a concept you understand now, but took you forever to grasp?

I’m sure we all have plenty of answers to this one, but sometimes we forget how...

Douglas R Andreani
I'm not sure what I'm doing. But it's working
  1. Read Post πŸ€“
  2. Bookmark Post πŸ”–
  3. Profit??? πŸ€”