I’ve decided to do something crazy and take a three month break from any consulting work to focus on getting Unison off the ground and open sourced. For a while, Unison has been a fun side project, but I’ve wanted to give it a little more love and dedication and see where it goes. My wife and I talked it over recently and decided to timebox the crazy to three months, and I’ve also notified my clients and am wrapping up any loose ends this week. Though it would be great to find a sustainable source of funding for the project, for now I’m planning on resuming regular consulting work at the start of May, at which point Unison will revert to side project status.
I’m very much looking forward to sharing updates with you here, and I’ll open source the work as soon as it reaches a non-embarrassing state. In an effort to hold myself accountable I’d like to give a tentative roadmap here and also commit to doing at least one Unison status update post per week. I hope it will be interesting for readers of this blog to follow along!
Also, I’d be interested to hear from folks in the comments who have attempted something similar—taking time off from “real” work to try working on something experimental and/or crazy. How did it go, what did you learn? Any tips, pointers, advice, or encouragement? This is new territory for me.
With that said, here’s the tentative roadmap. The overall goal: get to a point where I can actually show a compelling demo that exercises all the Unison components. I’m calling this Milestone 0 (M0). It’s more important to me to have the “story worked out” and have the minimum viable product (MVP) for each component. Details and sophistication for each of the components can be filled in later, and I’ll only block progress on technical issues that have wide-ranging effects on overall architecture.
Looking forward to sharing updates. Stay tuned!
… at least to MVP status: