Rapid prototyping as burnout antidote

I noticed a somewhat similar effect which I named "ProcrastinaBoost" (patent pending, obviously).<p>When working on a long/difficult project A, I keep one smaller but equally interesting (ROI-wise) project B on the side, and ensure I procrastinate in a time-boxed fashion on the useful project B only (vs. more classical procrastination).<p>The time-boxing ensure this stays at the hobby level, and regularly project B becomes difficult too to kick you back into project A.<p>It also gives me some times to relax and think about the issues on the other project.<p>To be used with careful time tracking of course :)<p>This removes a bit of the burn-out feeling, while still working on something that moves us along.

Yes, this really works.<p>Sort of the way some teams seem to keep a set of blog posts on the shelf, ready to go, we have a list of small tangential projects.<p>These are all three-days-to-a-week type things where we are already pretty familiar with 80-90% such that we can move through it quickly, but also get exposure to something new that we've been meaning to pick up. That combination of quick tangible progress plus learning really clears out any negativity.

This is <i>very</i> true. The only problem with this approach is that you can end up with a lots of "little fish" projects instead of making headway on your "Moby Dick" one.

I hope I'm not flagged as a spammer over this, since I tend to make this point every chance I get. Namely, how exactly do you go about rapid prototyping? I figure in all likelihood it's a bit of an art and requires a lot of experience and knowledge. I realize I may not be there yet. Still, are there any highly recommended references?<p>Books are OK, but in particular videos would help the most. Seeing how experienced programmers kick off a project could (I think) shed much light. PeepCode looks serious, but it focuses too much on one particular technology.<p>Thanks, and sorry to keep bugging with this...

This isn't startup specific! I work on projects with long development cycles, and rapid prototyping outside of work is very therapeutic. You can amplify the healing power with the right tools: in my case, Python and Git. There's nothing more satisfying than creating something in a few days, or extending an existing project to do more. Be sure to let someone know you did something! Thankfully my girlfriend listens to me babble about my minor wins, even when they sound ridiculous or incomprehensible.

There's no such thing as burnout. It's really heartache in disguise.

It absolutely works for me. It's called "strategic procrastination." It let me channel my creative energy to a different use when working in a long and difficult project. Retaining control over creative freedom is very important for motivation and avoiding burnout. The nice thing about being your own boss is that you can change the schedule anytime you want. :)

yes.