Session
Single Responsibility Principle - misunderstood and underestimated
"Singe Responsibility Principle - a class should have only one reason to change". This definition has already been formulated in two versions by Robert C. Martin aka Uncle Bob. During reviews and coaching of teams I have observed that this architecture principle is underestimated as much as misunderstood since 2003.
The result is such classes as "UserService" with 5kLOC code.
This talk explains a UseCase and then the application / refactoring with the Single Responsibility Principle. Furthermore the new term "Single Ownership Principle" is introduced.
(Languages german or english)
Nodirbek Usmanov
Befico GmbH, IT Consultant / Founder
Berlin, Germany
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top