{"id":1890,"date":"2020-08-12T10:15:05","date_gmt":"2020-08-12T08:15:05","guid":{"rendered":"http:\/\/web.evertop.pl\/understanding-solid-principles-single-responsibility\/"},"modified":"2021-06-17T12:34:52","modified_gmt":"2021-06-17T10:34:52","slug":"understanding-solid-principles-single-responsibility","status":"publish","type":"post","link":"https:\/\/www.evertop.pl\/en\/understanding-solid-principles-single-responsibility\/","title":{"rendered":"SOLID: Single Responsibility Principle (SRP)"},"content":{"rendered":"

SOLID principles are regarded as one the best practices in programming. We hear about them all the time. Unfortunately, it seems to me that these rules are often misunderstood. I\u2019ll try to present them in the series of five articles, one article for each rule.<\/p>\n

How has it all started?<\/h3>\n

The rules originated in the 80s of the twentieth century. As a whole they were collected by Robert C. Martin \u2013 a famous \u201cUncle Bob\u201d, an American software engineer, instructor, and best-selling author. He is most recognized for developing numerous software design principles and for being the founder of influential Agile Manifesto. Uncle Bob, if You read it by any chance, I\u2019d like to thank you for each sentence from your books, which were, and still are, very precious to me. I\u2019m constantly discovering how deep they are. At the beginning they were not called SOLID at all, it was one of the friends of Uncle Bob who suggested a different order so that a famous mnemonic acronym appeared. And, starting from 2004 these rules has been functioning under the smart name SOLID. They appeared in the context of object-oriented programming but can be referred to as any blocks of the code. Thanks to them our software should:<\/p>\n