When I first started working at Code Greene, I was building my PHP applications and sites the “old fashioned” way, with nothing more than a collection of common functions and a single MySQL class that I carried around with me everywhere. I have grown very accustomed to my small collection of code, and have begun to rely on it a bit (and actually almost failed the entrance test to Code Greene because I couldn’t find it). But I always built my applications from scratch, every time.
As I progressed in my PHP career (and hobbies), I noticed that I was building the same things over and over again, but only slightly different every time. This was an issue that I had noticed but never really put some serious thought into… until I started at Code Greene. My first day there, I was told to take a look at CakePHP and learn it, because it was to be the defacto PHP framework for the office. I took a quick glance at the code base and was instantly overwhelmed. There is so much stuff going on behind the scenes in Cake that it boggles the mind a bit. I went through a few online tutorials, and still felt that I knew nothing about it, let alone how to use it, but I could tell that it would either make or break my new job.
continue reading “Why we use CakePHP”
