Single Responsibility Principle (SOLID)
Lets go with the SOLID series from Uncle Bob! Give me a S! Yes, you got it, today we start with the Single Responsibility Principle, what does it says to us? Lets first enunciate it: There should never be more than one reason for a class to change. A reason to change, for the […]
SOLID, Object Oriented design
Yesterday I was talking with my colleague Alex at Vector Informatik GmbH and I told him that I wanted to write a post series about the SOLID principles of Uncle Bob, (Robert C. Martin), so I am going to keep my work and start it here with this post. I personally find very important to […]
Software Architecture: Service or Utility class
Last week I had a design talk with the software architect of my current project because of a code review we were performing for the offshore team. In order to encapsulate common methods to be used by a class, he wanted to use an Utility Class and I suggested to use a Service instead. I […]