Single responsibility
Description:
Each part of the code should do just one topic. If developer tries to tie more functions into one place then more chaos is introduced into the system. Also later update of app could be very difficult.
Links:
https://en.wikipedia.org/wiki/Single-responsibility_principle
Keywords:
single-responsibility principle programming
Motivation:
keep it maintainable. keep it simple. keep it expendable.
Requirements/Prerequisities:
self control
Level:
concret: specific best practice (e.g. use microservice)
Application domain:
Software engineering
Main phase:
Development: Implementation/Code/Build
Related literature:
https://www.worldcat.org/title/1003645626
In which projects do/did you use this practice?
SIMUportfolio
Software Engineer
>10 years of experiences
Masaryk University
| 1. How do you rate the potential benefit for your projects? | 5 |
| 2. How often are you using that practice? | 4 |
| 3. What is the effort to introduce the practice in your project upfront? | 5 |
| 4. What is the effort to apply the best practice in your project daily basis? | 5 |
Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)