I’ve been holding onto a few ideas for software products. There’s two in particular that I would like to start building but actually starting them is the problem. I keep looking at these ideas in from the point of a finished product. What I end up visualising is a finished and polished product that has seen at least a year of development. When I do this it ends up putting me off even writing that first line of code and what I’m simply left with is an idea.

The book Rework puts it nicely:

Until you actually start making something, your brilliant idea is just that, an idea. And everyone’s got one of those.

— Rework

Ideas are nice, but so is coffee, donuts and other forms of instant gratification. They’re within easy reach and quickly consumed. Ideas require time, in fact they can take a considerable length of time and that's the part that puts me off.

Despite the many advances in software development frameworks, there’s only so much of an application that can be generated automatically, the real work lies in the taking the idea and making it into something that’s more than an idea. It doesn’t need to be a finished product, it can be a well executed feature of the product that provides some value. Once that’s built, it’s time to move onto delivering the next set of value and so on. It's about breaking the idea down into manageable features that can be shipped on a regular schedule.

Right, I’ve put it off long enough. Time for a coffee and a few hours in front of my text editor. Let’s see where we can take these ideas.