One “criticism”, if that is a fair word to use in this instance, of this exercise of code an application and release in 30 days that has been levelled towards a post I posted in a private forum regarding this, was that “If I were writing an application in 30 Days I wouldn’t have time to write a blog.” Sardonic replies from me there to that aside for a moment. It’s possibly about “comfort zones”.
The sector of the industry (mISV industry) I herald from traditionally tends to feature developers who really do have a problem with new ideas (not that I’m implying the person quoted above has this problem, I simply do not know that for sure). New ideas require one to move out of one’s “comfort zone”
This “30 Day’s” concept certainly requires that.
Blogging prolifically, especially using a real name, is outside of this zone for a lot of folks, let alone developers.
Blogging specifically about perils or success as pertains to a “30 Days Release or Bust” cycle is, I would expect, even more uncomfortable.
You’re putting yourself out there for the whole world to watch and make judgements.
I happen to like this whole idea and it’s fair to say I’m not as curtailed comfort zone wise as most folks. If I was I wouldn’t run for election at the Federal level in a minor party, debate elected and aspiring politicians in public forums (recorded on TV, radio and print) if I was.
But for me – it’s the chance to really break some new ground and learn something “new” in terms of:
a) Can it be done? If it turns out it can’t then what have I learned?
b) Should it be done? Harder to answer but worthy of exploration.
c) What would I do differently at the end of this adventure?
d) Can I really write an application and blog about it consistently in 30 Days as specified, if rather loosely, by this “challenge?”
e) Will the end result actually result in products that can be sold by the participants (the ultimate yard stick I should think)?
I guess that’s what the expression “putting your money where your mouth is” so to speak really means.
Now time to code…
Add in the fact that you will have a large repository of data to review when you are done. Successful or not, that is a big plus.
Lets assume for a second that you aren’t successful. Having all of this data available will make the next go-round that much better.
I’ve participated in NaNoWriMo (http://www.nanowrimo.org/) each year since 2004, and while I have never reached the magic 50K words, each year I get a little further. Also my writing gets better each time. Blogging about it in 2006 and 2007 during the process also helped.
Kevin
Kevin,
That’s interesting. Novel writing, very interesting indeed. Hoping you make that 50k sometime soon!
You are right about having a resource once having gone through this process and I hope something for others to benefit from too.
>>
If I were writing an application in 30 Days I wouldn’t have time to write a blog
>>
I worried a bit about that too. Solution: more thought, less app. (This has served me in good stead so far.)
Hi Kevin,
That’s exactly right. Even if it doesn’t work, it does provide a fantastic repository for the history of the event which we all can learn from. Doing anything quickly will lead to mistakes being made in one area or another (even if simply because you’re tired) so those mistakes can be learnt from. Blogging too is a great exercise in mental stimulation, creativity, writing style and forces you to think about what you’re doing outside of the blog. In other words, if one were to blog every day the constant “stock taking” although time consuming, would be a valuable lesson and help one to stay on track.
At least in theory!