I’ve been working on this blog for months. I know, it doesn’t look like much, so how could it take so long? Well, it’s been a fallback project in between other projects. Like most developers, I’ll obsess over a particular language or framework for a brief while, and then Ill drop everything to learn about something new thats just gone and dropped a bomb in the industry. Then a little later, I realise this project has been neglected and get back on it, and the vicious circle continues.
My good mate @anthonyshort has been pushing me to launch this for ages, regardless of what stage it’s been in. We discussed that designing for yourself is hard. The toughest client/critic is yourself. You obviously want to provide a well designed and developed product, because after all, this is your craft. But I’ve found the more time you spend on it, tweaking this, tweaking that, the less likely anything will get launched. For instance, this blog has been redesigned 3 times since it’s inception, and I was considering doing it again.
Then I read this article by Matt Kersley. Matt was in a similar position as I am, stuck trying to dedicate the time to regularly work on his site. So in an attempt to force motivation he “deployed a crap version.”(His words, not mine). The idea being that with an unfinished product in the public eye, he’d have no excuse to not find the time to do something about it.
So that’s what I’ve done. It’s not an approach I’ve adopted with a project before, but I think it’s the only way I’d ever get around to giving it the attention it needs.