Deprecated: Assigning the return value of new by reference is deprecated in /usr/www/users/vigethv2/wynnewilliams/www/wp-includes/cache.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /usr/www/users/vigethv2/wynnewilliams/www/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /usr/www/users/vigethv2/wynnewilliams/www/wp-includes/theme.php on line 507
Comments on: Rails Rumble Voting Time http://www.wynnewilliams.com/rails-rumble-voting-time/ thoughts, observations, and commentary from an entrepreneur / CEO / husband / dad / consumer / producer / fan / advisor / participant Mon, 06 Feb 2012 01:49:39 +0000 http://wordpress.org/?v=2.2.1 By: Brian Wynne Williams http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-29 Brian Wynne Williams Sat, 15 Sep 2007 14:44:27 +0000 http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-29 Yes, 75 people is pretty insane. When I was in Boulder it seemed like they managed the number pretty well and all just rolled with it. The contributing developers in the group probably numbered 8-10. I maintain that had they gone with rails they would have launched on-time and the large team size wouldn't have been scrutinized as much. Whether you can get 75 people actually contributing is another question. I do think, though, that with the right plan you can be effective with more than 4, especially if there are distinct pieces of your product that can be built in parallel (e.g., a facebook app with shared data but a separate interface from your main site). The list for DC's startup weekend is long right now -- we'll see how it gets trimmed down. The idea of running with mulitple smaller groups is certainly being considered. Yes, 75 people is pretty insane. When I was in Boulder it seemed like they managed the number pretty well and all just rolled with it. The contributing developers in the group probably numbered 8-10. I maintain that had they gone with rails they would have launched on-time and the large team size wouldn’t have been scrutinized as much. Whether you can get 75 people actually contributing is another question.

I do think, though, that with the right plan you can be effective with more than 4, especially if there are distinct pieces of your product that can be built in parallel (e.g., a facebook app with shared data but a separate interface from your main site).

The list for DC’s startup weekend is long right now — we’ll see how it gets trimmed down. The idea of running with mulitple smaller groups is certainly being considered.

]]> By: Jackson Fox http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-28 Jackson Fox Sat, 15 Sep 2007 14:30:05 +0000 http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-28 When you consider that the Boulder Startup Weekend group (1) didn't have a concept when they started, (2) had 75 people, and (3) developed their app TWICE, I think it's clearer why they had problems launching. I think that anyone looking to do a startup weekend of their own should keep in mind that trying to herd 75 people in one direction in 48-hours is going to tough. Taking a page from the Rumble and breaking in to smaller teams would probably help each team get a lot farther in the process. When you consider that the Boulder Startup Weekend group (1) didn’t have a concept when they started, (2) had 75 people, and (3) developed their app TWICE, I think it’s clearer why they had problems launching.

I think that anyone looking to do a startup weekend of their own should keep in mind that trying to herd 75 people in one direction in 48-hours is going to tough. Taking a page from the Rumble and breaking in to smaller teams would probably help each team get a lot farther in the process.

]]> By: Brian Wynne Williams http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-26 Brian Wynne Williams Fri, 14 Sep 2007 14:53:25 +0000 http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-26 I think the challenge in Boulder was as much about technology (java) as it was the team size. As I understand it, the app just didn't work when the weekend came to an end. Clearly when it comes to rapid app development, small teams and quick decisions are key to keeping deadlines. I think the challenge in Boulder was as much about technology (java) as it was the team size. As I understand it, the app just didn’t work when the weekend came to an end. Clearly when it comes to rapid app development, small teams and quick decisions are key to keeping deadlines.

]]> By: Ben http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-25 Ben Fri, 14 Sep 2007 12:07:00 +0000 http://www.wynnewilliams.com/rails-rumble-voting-time/#comment-25 You know what I found the most interesting about the Rumble? 92 teams - each of no more than 4 people, and many only a single person - *launched* their applications. A number of them (Clinton and I among them) intend to continue working on them in the future, and some (like SimpleBucket and Checkbook) are full-fledged startups. It makes the lack of a launch in Boulder even more confounding, I think. You know what I found the most interesting about the Rumble? 92 teams - each of no more than 4 people, and many only a single person - *launched* their applications. A number of them (Clinton and I among them) intend to continue working on them in the future, and some (like SimpleBucket and Checkbook) are full-fledged startups.

It makes the lack of a launch in Boulder even more confounding, I think.

]]>