The Setup This week we are talking about the Open-Closed Principle. This principle states that a class (or method) should be open to extension and closed to modification. In other words we have to teach it new tricks without changing the actual code. “But that impossible” I hear you say. And I hope for all… Continue reading Open/Closed Principle
The Interface Is Owned by the Client
This one is a less known principle, but with great implications. It is related to the Interface Segregation Principle, as well as to the Dependency Inversion Principle. It also dictates where interfaces should live in a multiple assembly architecture. This is going to be interesting, so hang on to your keyboards. What Do You Mean?… Continue reading The Interface Is Owned by the Client
The Single Responsibility Principle
Definition According to Wikipedia the Single Responsibility Principle is a computer program principle that states that “A module should be responsible to one, and only one, actor”. Robert C. Martin, the originator of the term, expresses the principle as “A class should have only one reason to change”. In my experience as an interviewer, I… Continue reading The Single Responsibility Principle
What is a Constructor?
This article is part of the The Anatomy of a Technical Interview series. The actual question is “What is a constructor, and what role does it play inside of an object?”. Throughout my interview experience I have received a lot of answers to this question. Answers vary in shape and form, but are mostly along… Continue reading What is a Constructor?
How It All Started
This article is part of the The Anatomy of a Technical Interview series. In this series I share with you my experiences and insights that I gathered while holding technical interviews. I’ve seen my fair share of interviews while I was applying for various jobs and positions throughout my carrier. Many of them were either… Continue reading How It All Started
Softwarecraft 