> I agree that it would be interesting to do this but I can see a flaw in > the process: different CFers take different amounts of time to solve > the same problem, even using the same approach, and we'd also likely > get code that performed wildly differently. > > Of course, this is true, generally, across IT and not limited to CFers > - someone with twenty years software engineering, a CS degree and who > is fluent in half a dozen languages is going to produce radically > different results to a self-taught programmer who has used mainly one > language for even half a dozen years. > > How do you suggest mitigating that variation?
You could post a specified db schema, and actually provide the business logic in CF code and equivalent Java classes to use in the project. That would at least get rid of how long it takes to figure out how to implement the business logic. Obviously, that would bring up debate on whether that was the best way to implement. If someone needs to implement that code in a different matter, perhaps you don't log that time. It seems the main goal is to see how long it takes to implement the framework, and maybe providing the required business logic to use would help limit coding to just the framework. Just an idea (and I know there are pros and cons to this.) - Dan ....................................... : Name: Dan G. Switzer, II : : E-mail: [EMAIL PROTECTED] : : Blog: http://blog.pengoworks.com/ : :.......................................: ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
