Last time I wrote about my struggles with unfinished side projects and what I am going to do about it. Today its time to cover first fruits of success following the new action plan.
“uSite” started with one of the best type of use-cases a project can have — a personal pain. I was looking for a static site generator for my personal blog www.agilesaturday.com, but after going through some of the popular engines on www.staticgen.com I decided to create a new one. My biggest frustration with existing static site generators was the amount of documentation and conventions I needed to learn before using one (e.g. gohugo.io). I was looking more for a content transformation API. Instead of a tool which requires significant knowledge of concepts like Git, extensions, themes and data exchange types, but pretends that I still don’t know how to make a website.
My side project game is at its all time low. Maybe I am using unhealthy comparison with myself during college years when I did not need to care about grownup stuff. But only shipping a tiny, two page app per year is sad. Strange part is that I am still constantly hacking on side projects, nothing has changed there. Where are those projects now? Oh, right, they have been abandoned before reaching “shippable” state. After some retrospective on previously successful and failed projects I think I have found why this is happening.
My first blog post on AgileSaturday.com