I have Blogged about Inoneweekend this week. Part of this was an effort to look at a small area the Information Technology side that I was interested in and to put forward some views that I personally believe about software development and project management. It may have given the impression that this was just a bunch of computer geeks gathered together to hack some code in a weekend. This was very much not the case. What Inoneweekend in Cincinnati July 11th was in reality, a hundred very talented and motivated people working to produce ONE viable company? After July 16th there are likely to be much written about this event. As you read about it I would like to give you some websites to visit. Inoneweekend will likely be compared to weekend coding efforts or to coding competitions.
I would like to first direct you to “Building Web Apps Really Fast: Why Developers are Drawn to Weekend Code-a-thons“.
This article does a good job of explaining weekend coding efforts such as
Blitzweekend, startupweekend, railsrumble, barcamp, hackday, superhappydevhouse, ventureweekend, and weekendaps to name a few.
I would also suggest you checkout the King of all coding competitions TopCoder
As you compare the above to Inoneweekend you will likely find, as I did, that all aspects of what it takes to make a startup company work was involved in this effort. Designing and Coding software was just one functional area that some of these talented people worked on. So if you hear this event being described as just another weekend coding effort, take the time to visit some of these sites and really compare Inoneweekend to some of these other efforts. I know I found it to be a unique experience.
July 18, 2008 at 3:58 pm |
Alex,
Great job capturing the differences in this event vs. coding events. My experience at InOneWeekend seemed to be that technical folks were the minority, although as we broke into sales & marketing, branding, financials, management and ops, tech, and business strategy, the tech team may have been proportionately large. In the end I believe the branding team was our largest team.
Somehow we all pulled this one off without too much dysfunction