Resolving Dependencies

Writing a loosely coupled code has become an essential skill for any professional developer. While legacy applications had a tendency to pack it all up, thus ending in one big solid block of code, modern applications take a more gradient approach as they largely rely on third-party libraries and other components. Nowadays, hardly anyone builds their own mailer, logger, router, template engine, and so on. Great deal of these components are out there, waiting to be consumed by our application through Composer. As individual components themselves are tested and maintained by various community or commercial entities, the cost of maintaining our application is significantly reduced. The overall code quality itself improves as an indirect consequence of more specialized developers addressing specific functionalities...