He walks through his thoughts and needs at different stages of the development process - a database abstraction library here, version control there - and ending up with the framework choice that faced him. Among his options were offerings by Prado, Seagull, Symfony, CakePHP and his pick - CodeIgniter.
Suddenly I got codeigniter and I was able to run a whole lot of controllers, templates and models in minutes (well not in minutes, but much less time than previous ones). A rich , pleasing to read, friendly set of documentation, a bunch of in built libraries and less autonomous control gives me full freedom over my application. It was easy to integrate my old friend smarty with it, in case it comes with it's own active record, but it gives me chance to add adoDB with it. I fall in love with code igniter soon after i realize that it comes with almost zero learning time (or i better say learning on demand)
He also mentions that, had the post been a bit more technical in nature, other factors would have been included. As it is, though, it flows a bit better this way.