Lets say I am your customer and I want to develop a mail server or a blog system.
You really give me all this words instead of offer me to at least try Zimbra and Wordpress?
You should put the client interest at top.
Anyway, this kind of decision should be taken by an architect that will not implement the solution, and not by a developer.
Even in this group I see developer that reinventing the wheel with cake and php code instead of using basic database technology which is the simple thing to do.
It does not work like that in the real world. If I am a tracks dealer and some on come to me to buy a sadan I'll tell him to go to my friend dealer hoping he will do the same when some one ask him for track.
I also saw Joomla developer that recommend Joomla where not suitable.
Sometimes not taking the job is the professional thing to do.
May advice to those how want to be treated as professional, act as one.
--
Regards,
Zaky Katalan-Ezra
QA Administrator
www.IGeneriX.com
Sites.IGeneriX.com
054-7762312
Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.You really give me all this words instead of offer me to at least try Zimbra and Wordpress?
You should put the client interest at top.
Anyway, this kind of decision should be taken by an architect that will not implement the solution, and not by a developer.
Even in this group I see developer that reinventing the wheel with cake and php code instead of using basic database technology which is the simple thing to do.
It does not work like that in the real world. If I am a tracks dealer and some on come to me to buy a sadan I'll tell him to go to my friend dealer hoping he will do the same when some one ask him for track.
I also saw Joomla developer that recommend Joomla where not suitable.
Sometimes not taking the job is the professional thing to do.
May advice to those how want to be treated as professional, act as one.
On Mon, Feb 22, 2010 at 5:33 PM, LunarDraco <mdcatc@gmail.com> wrote:
For my point of view, I want to be designing and building new code to
solve specific client problems. I do not want to be configuring
someone else's already poorly designed and implemented system and
trying to figure out how to solve problems that are created by using
said system.
So I tend to focus on those issues. I usually explain the pit falls of
using a system that is common, popular, etc.
1. You'll have no advantage over your competitors who are using the
same systems.
2. It will be bloated and have many features you don't need or in some
cases don't want and have no way to disable.
3. It will be missing those feature which your business needs that
separates you from your competitors.
4. You'll be stuck using plugins that are written which are close to
what you need but never quite get what your really need.
5. You give up your ability to request a feature and have it
implemented in a timely fashion.
6. You'll be paying to solve problems which have nothing to do with
your business just to make this popular software fit.
7. Integrating your other systems to this popular system will not
always be trivial.
We are a development group, we use solid tools, and languages that are
well known in the development community. We use patterns that are
proven for both stability, and the development time line. We use an
agile weekly cycle. You will have something to start looking at within
a week (it takes less than a day to deploy my shell site). We will
meet regularly, and identify feature priority.
We (my group) already have a bunch of common modules in place with our
starting shell (users, profiles, acl, large file managment, shoping
cart, etc.) these are all highly configurable and very easy for us to
modify as we wrote them and have the source.
My goal is to be able to have a system which can be deployed with
those things that are common to all web sites, and have a high level
of confidence in being able to easily build on top of that core those
client specific needs in as little time as possible. We have a good
base shell and we improve that shell with every site we build on top
of it. This also improves every site we've already deployed.
Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
--
Regards,
Zaky Katalan-Ezra
QA Administrator
www.IGeneriX.com
Sites.IGeneriX.com
054-7762312
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
No comments:
Post a Comment