I don't think that not using frameworks necessarily imply "reinventing the wheel each time", as long as the organization counts with their own library of reusable code that they leverage across projects, as well as having clearly defined standards and guidelines on how to develop projects.
On Thu, Jan 29, 2009 at 5:08 AM, John Whish <[email protected]>wrote: > > 'The culture here at my work place is to use least frameworks as > possible' > > Isn't that like re-inventing the wheel each time? Surely using proven > frameworks is better than writing your own? Out of Transfer and ColdSpring, > I've had less trouble with Transfer ... and Transfer really does rock! :) > > > > > -- Oscar Arevalo http://www.oscararevalo.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
