Welcome to the fifth (and last) post of our series dedicated to the use of SOLID principles. This one is dedicated to the Dependency Inversion Principle. So far, we have covered all the other principles:
My series dedicated to the use of SOLID principles is back, this time to talk about the interface segregation principle. For reference, here are the five principles once again.
This is the third post of a series dedicated to the use of SOLID principles at Codavel. As you remember, we're showcasing SOLID principles in the light of a “make it work, make it right, make it fast” philosophy. So, take this post with a little
This is the second post of a series dedicated to the use of SOLID principles at Codavel. Building upon the philosophy of “make it work, make it right, make it fast”, we mostly employ these principles after having an MVP. Why? An MVP will always give
At Codavel, we use SOLID principles to create a development proposition where merging becomes an almost trivial task. They allow us to take full benefit of lean strategies, with integration and build processes that are not nerve wrecking. This is
Ultimately, this article is about a strategy built of programming principles for simple code integration. It is basically our way to reduce the cost of building and integrating new features or products designed from scratch into an existing codebase.