|
Hello there, Hope you are doing good. In this week's newsletter I want to introduce you to the SOLID principles, and the fifth principle in particular - the Dependency Inversion principle. Most of the modern day programming frameworks use Dependency Injection mechanism. Fun Fact - Do you know that Dependency Injection concept has in one way evolved from the Dependency Inversion principle? Click to open the full article here I hope this content will be useful to you. Follow me on Facebook, Twitter and Instagram. I do regularly post my latest updates over there. Have a great week. Cheers Ram |
If you're starting in software engineering or an experienced professional, I post informative content around stuff I work with - Full Stack Development. Subscribe to my newsletter to receive my latest posts.
Hello there, Hope you are doing good. In this week's newsletter, I want to introduce you to the third principle of the SOLID principles: five principles describing few fundamental rules for developing arguably ideal software components which are scalable, extensible, robust and flexible - the Liskov Substitution Principle. This principle can be termed as one of the basic foundations of the Object Oriented Design languages which talks mainly about substitutions and inheritance. The principle...
Hello there, Hope you are doing good. In this week's newsletter I want to introduce you to one of the most efficient internal sorting algorithm, and discuss how to implement it - Quicksort algorithm step by step with an example and analyze time complexity. Quick Sort is an internal sorting technique which can be used to arrange a given set of unordered dataset into required order. It is the most efficient internal sorting technique, which doesn’t use any auxiliary memory (or additional space...
Hello there, Hope you are doing good. In this week's newsletter, I want to introduce you to the fourth principle of the SOLID principles - Interface Segregation. In the early stages of application development, it’s common to place all logic into a single class. As the application grows, these classes become bloated or “fat” with unrelated responsibilities. Later, when we try to extract interfaces from these classes for modularity or extension, we may end up with interfaces containing many...