When starting out with a new application, would you rather just use an existing dependency framework and risk the possible shortcomings, or would you opt to write your own which is completely adaptable and why?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When starting out with a new application, would you rather just use an existing dependency framework and risk the possible shortcomings, or would you opt to write your own which is completely adaptable and why?
IMO, our job is to solve our client’s problems, not write dependency injection (or logging, or ORM, etc) frameworks. When a suitable framework exists, in my opinion, you should always use that framework.
To add to this, if that framework is open source, then there is no excuse not to use it as you can fix any possible shortcomings.
I think that too often we lose site of our objectives. As programmers, we tend to focus on the interesting problems (writing a dependency injection framework for example) and procrastinate on the boring problems (writing yet another CRUD application for a client.) 😀