4 ms·

The trick is finding a problem you have a passion for. That way, no matter what or how long, it won't feel like work. Your side project is the sabbatical.

• dukoid 8y ago
  The passionate part is the proof of concept. After that, you can decide between persistence and passion for the next project... :) I think keeping the scope as small and simple as possible might be even more important than passion.
• coldtea 8y ago
  The problem is that whatever the problem you're trying to solve, the parts you have a passion for are only small parts of the overall solution. It's the rest that gets you (e.g. you might like coding the backend algorithms but hate UI work). And even if you love all parts, you'll probably still hate the minutiae that goes into a finished product.
• rpeden 8y ago
  The downside to this approach is that it can kill the passion for the thing you were passionate about. Also, I've noticed that real world solutions to problems tend to include lots of schleps that are excruciatingly boring, but necessary. The longer I do this kind of work, the more strongly I believe that the people who are most likely to see a project through to completion are the ones who have the stone cold professionalism - or just plain stubbornness - to grind though the boring stuff instead of just faffing around on the bits of the problem that they're passionate about. I think a side project that's just about indulging a passion is totally fine. But a side project that is also a product that makes money will almost require lots of pieces that definitely feel like work.