“Not Invented Here” (NIH). This is one of the biggest hurdles developers have to overcome when reusing components, modules, functions or snippets in the production software. I’ve run across it my entire development career — developers simply do not like to use software that they don’t write and own — and of course, I’m am guilty as the next developer.
So today I’m starting out with a positive outlook and tossing out our in-house PHP Framework (FIZZI) that we’ve been using for MustFindit and replacing it with CakePHP. It’s taking too long to develop MustFindit and extending and adapting FIZZI for MustFindit’s requirements will basically kill the project.
Why CakePHP? I’ve considered Rails, Symfony and quite a few more; however, CakePHP seems like the best fit with our current technology, design and knowledge base for a MVC architecture. This is a big plus since we want to expedite development process and keep the learning curve down as much as possible.
Over the next few days, I hope to present our findings on CakePHP and if it is a viable Development Framework for PHP and our projects.