While I agree that it's a scary place to work for that doesn't see the benefits of following standards and using frameworks, here's how I'd word it: using CakePHP lets you do make the same site in far less time (at least, it does once you're used to it, maybe for the third project onwards). It's kind of like having a whole team of invisible programmers at your disposal, working for free.
It also means that if a client changes their mind about how they want the site to work (and they will if you don't put your foot down), making those changes will be almost as quick and easy as they assume it is, for once. For example, the other week a client decided to suddenly change the spec on a site that was nearly live. They wanted to change a static list of things into a fully back-office-managed list that they could add to, delete from, rename all the things on the list, and so on. Creating the table and changing a column in the database, and pretty much copying and pasting the code and changing a few variable and class names here and there took all of about maybe twenty minutes. Without CakePHP, it would have been maybe half a day's work. At least, that's how I like to feel about it, although it almost makes me feel guilty that I'm not paying the CakePHP developers an hourly rate while I work. :) Hope that helps, Zoe. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
