The two greatest foes of every software developer are a) uncertainty and b) complexity. Over the years, we have invented many tools and methods to fight them. But eventually, we realized that uncertainty cannot be defeated and instead we learned to embrace it with ever shorter feedback cycles, "agile" methods, continuous integration, devops and Test-Driven Development.
The term dependency injection refers to a technique whereby the dependencies of one object are supplied – or injected – by another object. Instead of letting the client (the object that needs those dependencies) build or find the dependencies, the dependencies would be passed to the object. That’s the whole meaning of dependency injection – actually, a pretty simple concept. But let's have a deeper look.
While it is very interesting to learn about new software designs and architecture patterns we tend to forget that our software must be adaptable over time and this might even be more important than choosing the "right" patterns at the very beginning. Requirements for software always changed and will always change.
The PHP community has come a long way: from the early days of a templating engine for “dynamic websites”, through the adventurous years of a hacky scripting language until now. In the past ten years, we started discussing design patterns and good architecture and in general created more robust, versatile and complex applications. And with the complexity came a row of new tools and techniques, which were necessary to harness all the parts which make a sophisticated PHP application. But have we also become more professional on the infrastructural side?
You can now use Bitcoin to reserve a ticket for the webinale and the International PHP conference. „We are finally digital!“ proudly announces WebMagazin's editorial team, which is also in charge of the alignment of these two conferences. That's why we are making this huge digital step and offering a Bitcoin payment option.