Release Early, Release Often

by Administrator on 2 months ago

So this blog is now alive after many years of work (in terms of time rather than man hours). I built it from scratch using Python and Flask both of which I do love.

It was one of those projects where you think "yeah, that can surely only be an hours work at most" and then it all goes nuts and you start building things you never intended to build and adding features you never imagined at the beginning. It's all reasonably trivial stuff but it was getting to the point that I had more posts I wanted to write than time to spend building the blog so I thought screw this. Lets get the minimum amount of work I need to do done to be a usable blog and release it. I can always fix it in situ. Which is what I am now doing.

Release early, release often.

It makes sense. Just get something out of the door and start using it. That's when you notice the real problems. Fix them, upgrade. I guess it works for something like this blog. It must be harder for companies, especially start-ups to do the same thing. Release too early, and be too successful and you're web server goes down and you've lost all that custom. Maybe people in that situation are more tolerant. Maybe as long as you release quickly and often enough you'll code out those problems assuming you can code out of those problems.

For now I'm happy the site is up. It has a long way to go yet from my ultimate plans for this tool but it's a start and in the mean time I can procrastinate and put my thoughts in here that are just one character too big to fit in a tweet.