Developers are getting more professional every day by using web design patterns to solve common problems. This session will introduce one of the less-known design patterns in the PHP world, but also one that can greatly improve the decoupling and the testability of your code: Dependency Injection. I will demonstrate how to use Dependency Injection in your projects, and I will take advantage of the PHP 5.3 new features to create a fully-featured DI container live.
By clicking this button you are declaring that you are the speaker responsible for it and a claim request will be sent to the administrator of the event.
If the claim is approved you will be able to edit the information for this talk.
Well structured as an intro to DI and why to use it, but the people who are not already using DI might not see the benefits of the DI container or be able to follow the code used to create it, which might turn them off to DI in general.
When you asked if anyone had questions midway through the talk and no one raised their hand, I had the feeling nobody wanted to admit to not being able to follow it. A lot of people seemed to be stirring about, uncomfortable. You went through it a bit fast given the amount of code and complexity, and some of the code colors were hard to see.
I had read the documentation and seen the slides before so I was able to follow, but I know the first time I saw this design pattern and the DI container it threw me for a loop.
Nice progression from simple DI to the full DIC (and some of the key benefits). What I liked about the container example was the practical use of some new features (anonymous functions, closures) in 5.3. Thank you for that.
Know of an event happening? Let us know! We love to get the word out about events the community would be interested in and you can help us spread the word!
12.Mar.2010 at 22:05 by John Kary
Well structured as an intro to DI and why to use it, but the people who are not already using DI might not see the benefits of the DI container or be able to follow the code used to create it, which might turn them off to DI in general.
When you asked if anyone had questions midway through the talk and no one raised their hand, I had the feeling nobody wanted to admit to not being able to follow it. A lot of people seemed to be stirring about, uncomfortable. You went through it a bit fast given the amount of code and complexity, and some of the code colors were hard to see.
I had read the documentation and seen the slides before so I was able to follow, but I know the first time I saw this design pattern and the DI container it threw me for a loop.