0
1

[–] jsprogrammer [S] 0 points 1 point (+1|-0) ago  (edited ago)

I can only work on one thing at any given moment. Almost all of my repos are prototypes or experiments. Some are complete and actively used, others may be dead ends.

Edit: Most of the repos are not abandoned. Almost all projects I either want to return to, or mine code from for other projects. The problem is that I can really only work on one project in any particular slice of time. The database isn't really an issue, I have considered all of those and I think you are right, it doesn't really matter. What matters is picking the project that will have the best impact, as I must necessarily trade off working on other projects (many of which I believe are critically important).

0
0

[–] WhiteRonin ago 

Abandoned = 2 years old with no activity.

You have to make some decisions as to what is important. I get the fact that you have a lot of ideas. I am the same way. However, because of being spread too thin nothing gets accomplished and your ideas end up being ideas.

I had to finally buckle up with one project and just work on that. What I do at work I try to implement in what I'm doing after work and vice versa try to bring back into my day job thus both goals move forward.

0
1

[–] jsprogrammer [S] 0 points 1 point (+1|-0) ago 

I don't necessarily agree with that definition. Some projects just work and don't need further code at the moment. Others are just experiments.

Maintenance and premature project selection are huge problems. Taking a path necessitates not taking others. I want to get a large view of the landscape, develop ideas, and then execute on the best. If you buckle in to the first project you start, you run a huge risk of myopia. I have been able to move many projects forward this way and now have a large stockpile to draw from. Many of the most important projects are on the verge of public usability, but I have held off so as not to be swamped by having to support something I am not ready to.