John, Jon Clausen wrote: > On May 16, 2007, at 7:03 PM, Christopher Jordan wrote: > >> Each project should be required to have a white paper of sorts >> describing the technologies used, the programming methods used, the >> time >> it took to develop, the version of CF they used (BD, Railio, Smith >> Project, whatever), anything that was super-easy implement (or just >> plain super-cool) that wouldn't have been as easy (or cool) had it >> been >> coded in another language. That super-cool thing might in fact be that >> the language allowed the developers to step outside of the CF box, >> grab >> hold of another languages technology (a COM object for instance or a >> Java Bean, or whatever) and integrate it seamlessly and without >> breaking >> a sweat! >> > > Chris, > I'm all for documentation and whitepapers. In my mind, though, > developers having fun making fun things with cool technology is the > biggie. Yeah, I didn't mean for it to sound like it would be some ninety page document analyzing everything, I meant more of a short blurb or bullet points. Something amounting to a small blog entry. You're right: if the developer's want to, then they can offer more, but they wouldn't have to. > Maybe a simple post-project survey that takes the form of a > whitepaper in display would work though. If the project team wants > to extend beyond that, they could choose that. Once it starts to > feel like work, though, some of the energy and enthusiasm gets lost > in the to-dos. > Agreed. :o)
Cheers, Chris -- http://cjordan.us ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:278397 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
