[exDM69]

One month projects sound great but with my busy schedule that would be only about 8-16 hours of butt in seat time, which isn't enough for a substantial project. I can think of some "toy" projects in that timeframe, though. And some peripheral utility projects that might be useful in the future.

I've been at my "main" side project for more than 5 years with no end in sight.

I wish I didn't have to have a day job. I'd have no issues keeping myself busy, but I'm a terrible businessman and I doubt I'd make any money.

[ggoerlich]

That's what it's all about: to get something done and learn new things instead of (or in addition to) those long running, never finished side projects. I have a long running project too, 1PPM are my side-side projects.

[exDM69]

Sounds like a good idea.

What worries me a bit in this idea is that it takes a surprising amount of time to polish a project so that it is "done". Or at least left in a state where it is easy to pick up later, by yourself or someone else.

I have tons of projects where the "beef" is mostly done but README, example code, tests, etc are lacking.

Starting a project takes surprisingly long too. Setting up a build system, test framework, CI builds etc always take much longer than I anticipate.

Keep these pitfalls in mind. Best of luck to you.

[Cyph0n]

One or two side projects is enough for me. Side side projects is taking it too far imo: there are other things I'd rather spend my time doing.

[ianai]

Can you serialize your long term project into 12 smaller ones?

[exDM69]

Yes, otherwise it would be overwhelming. I try to make bite sized subprojects so I can walk away and the project is in a shape that is easy to pick up later.