I started this project almost a year ago as a busman's holiday in a previous life. What could be better than working on blogs for your day job than to come home and work some more on your own blog?
Some of the reasons why I wanted to write my blog (and literally in both senses: the words on this page and the code) was to experiment in my own sandbox where I call all the shots and get to play with all sorts of bleeding edge tech (read: “I saw this cool thing on HN and therefore I am going to use it”).
In practice, it turns out that using personal projects as a platform to learn new stuff is pretty effective, that is if you never want to get anything done. To summarize, this was my thought process:
And so you see how bikeshedding can be a pretty fun hobby.
I ditched nearly all of that in favor of rewriting and building what amounts to a 5% of a terrible Jekyll clone. That's not to say that the rampant bikeshedding wasn't good, in this case I think doing so let me touch a lot of new tech I haven't had the chance to before. Here's hoping the initial exposure will help me later. (Or kill me by allergic reaction on second exposure. The human body is a wonderful nightmare.)
In the end, what I have is much simpler (push to deploy, hell yea), and most of all it's the bare minimum.
The bare minimum is something I learned about in a previous job, mainly because it was the punchline to make fun of a 'lazy' coworker who appeared to barely do anything. (He wasn't actually lazy, by the way.) But there's some truth to it! The bare minimum is everything. Do the bare minimum in agile development, and for you serial startup addicts, I mean, entrepreneurs out there, the bare minimum (or in your parlance, “the MVP”) is what might eventually make you cashmoney.
See you soon.