The idea would be to take one set of application requirements and then build an application using each of these techniques. Metrics like time taken to develop, lines of code, performance, etc could all be captured for each. Obviously, developing all of these applications would take a considerable amount of time. However, if many people were interested we could each take one technique each and then share our results.
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?
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
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).
