December 1, 2016 level13 No comments

Why I used CodeIgniter

CodeIgniter is listed among my skills and it is the framework I have been using for the last four years and so I thought I’d share on why that is and where I’ll be going moving forward. Before I started working for my previous company, the agency I worked for used WordPress for development. When I switched to my new job, I had free rein to decide what to use for web development and I wanted to move away from WordPress and get back into bespoke development. WordPress definitely has a place in the webspace and it has vastly improved from its early beginnings. and as with anything, there are pros and cons to using it. One thing I wanted to get away from was trying to fit a square peg into a round hole which is what it can feel like sometimes with WordPress which is primarily a blogging platform though certain plugins (such as Advanced Custom Fields) and other updates have improved things since then.

I started evaluating MVC frameworks such as YII, Symfony, CakePHP, and others that I can no longer recall. CodeIgniter was among them and at the time, I was new to the MVC concept and what made CodeIgniter stand out, was its ease of use for a beginner to get started. The documentation was simple and easy to work through and the framework itself is light, fast, easy to pick up, and does the job. If you’re new to MVC, OOP or just PHP in general, I would heartily recommend giving CodeIgniter a whirl and it’s definitely a good stepping stone onto other things. So CodeIgniter was the winner back then but since then, another framework has been making a name for itself and it has matured into what is quite possibly the framework of choice for a lot of developers. That framework is of course, Laravel.

What do I like about Laravel? What isn’t there to like? It does the job, it’s a delight to work with, and its very well documented. There are a number of CMS’ to choose from if you don’t want to build your own, and a number of applications that you can use such as Laravel Spark which will enable you to get your website up and running in minimal time. Watching Laracasts whether you use Laravel or not is highly recommended as it will help you become a better developer (there’s always something to learn right). You’ll also see your employment options increasing if you know Laravel as it has become a very desirable skill. As this isn’t really a post about the pros and cons of Laravel, I will stop gushing now but in conclusion, whilst I’m not abandoning CodeIgniter, or WordPress for that matter, moving forward, I’m making room for Laravel and even other frameworks that might be out there. I’m also learning Reactjs but that’s a post for another another day.

Leave a Reply

Your email address will not be published. Required fields are marked *