On Jan 25, 3:42 am, "b logica" <[EMAIL PROTECTED]> wrote:
> On Jan 24, 2008 4:36 PM, Doug @ Straw Dogs <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'm a developer by heart and know I'd love to code in CakePHP.
> > However, I'm failing to see any solid business benifit in using it
> > that can help me sell it to the directors.
>
> I'm still just learning the ropes here so I don't have much to offer,
> but I do have to say that some of the terse responses here are very
> disappointing.
If that's a reference to me I don't wear a cakephp badge on my work
uniform. I view this sort of resistance in the same light as "What's
wrong with using tables for layouts?" or "I'd like you to write my new
site using AJAX instead of HTML".
>That they come from some of the very people who one
> should expect to offer the most thoughtful and cogent sales pitch for
> Cake is terrible. Telling Doug to get out of Dodge is ridiculous. Do
> you want this framework to be accepted by more people? Or do you pine
> for the good old days, when Cake was something only a very small group
> of developers worked on? I'm guessing not, and that you'd like it to
> continue gaining in popularity.
>
> Don't get me wrong: this is not a flame. From what I've seen so far,
> CakePHP is an excellently produced framework and I intend to move more
> of my existing projects to it, let alone future ones. However, I'm
> lucky in that I left the corporate scene awhile ago and answer to
> nobody but my clients. Were I still lead developer at my old company,
> I'd be looking for the same answers Doug is. Do yourselves a favour
> and give him and other devs the ammunition they need to overcome the
> corporate inertia that they face.
>
> Like it or not, CakePHP needs a bit of a sales pitch that management
> can understand.
If I ever needed to /sell/ cake I would: ask for a sample app
description, discuss the database requirements with them and define
that, and say "I'll be back when I've got something working" - go
write some sql, run bake and knock on the door in 10 minutes. Find a
db change/tweak/new requirement that is needed - run it again while
they are there - db changes now reflected in the baked app.
That isn't full of buzzwords it's ~30 minutes from "OK show me an
inventory system, with Stock, Products, Movements..." to showing
something tangible AND easy to edit AND easy to maintain.
Going from that to a finished app is a WHOLE lot faster AND
maintainable AND robust AND secure than you could achieve without
using 'just' php (or other solutions). And all that means less time
($) spent.
mi 2c,
AD
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
