WF Developer Competition

I don't see what the fuss is about knowing the spec beforehand, I think we can all have a gentleman's agreement that we haven't started working on the project until the project officially starts. If someone wants to write up 2 or 3 more, we can then just randomly select one on the day we're supposed to start and that should effectively limit the ability of anyone to get a jumpstart unless they take a stab at all possible options. But I can't see that happening.

@acidie: yes, everything will be open sourced within reason. Obviously don't release your DB credentials or anything similar.

@sumo: I think your idea for posting in the thread at start and stop times is good because we're all in ridiculously different timezones so coordinating a singular start time would be brutal.

If someone wants to drop in some feasible project ideas, I can turn out a few specs today and tomorrow for them and we can randomize the option on the project day(Yes, I know how to write specs).

Finally, I can most likely make Saturday work, I just won't be able to get the full 24 hours worth of work in because I offered to drive my girlfriend and her friends to a wedding like an idiot.
 


I don't understand even having a hard time frame, like 8 hours in one day.

Is there anything to win? At best it's pride, at worst no one gives a fuck.

Who is going to 'judge' it? Could I really judge someone like dchuck when I don't really know ruby or rails? Is someone that doesn't write python going to be able to look at mattseh or my code and even be able to judge what is good or bad? The basic concepts maybe, but the finer details, probably not.

I initially thought this was more or less to put out example code for particular languages so we could epeen all over it. But lets get real, 'win' or 'lose', who gives a shit?

Make it like 1-2 weeks, put something out if you want. Then we can oogle each others code in a productive manner. Maybe... Probably not. I doubt most of us are going to take the time to go through each others code.
 
I'm in, no guarantee I can even finish it though :p. I'll try my hardest, that's fo sho. Never worked with DBs before.
 
I'm fine with the RSS reader but it would be cool if we did something that would line up with the seo contest that's about to kick off.
 
You guys should do these more often. I wouldn't win, but I'd like to participate. Can't afford the time right now though. Good luck, keep the results posted.
 
So are just going to stick with the rss reader idea for now?

I'm fine with that if everyone else is. SERP checker is a bad idea, because xMarkPro comes with one built-in, so I'm basically already done if we did that.

Makes no difference to me what we're developing, and as long as it's an SaaS solution, I'm happy. Times a ticking though, so what should we do?

RSS reader, 22nd, 24 hour devel time, post a quick note here upon starting and completion? Or dchuk, did you want to bump it up a couple days to the 24th or 25th? Or if we're developing something other than the RSS reader, someone needs to come up with some specs.
 
I'm in for this most likely, probably gonna use rails too. I guess me and dchuk can compare code once we're done.

RSS reader seems good to me.
 
Text files ftw?
I could do that, but I really should learn how to use databases. lol
edit: looking at this it seems to be heavily reliant on DB (which i know nothing about), i would legit spend 24 hours learning databases lol. i'll sit this one out but it's a cool idea, wish luck for the rest of you