We will be talking about the single responsibility principle. We are taught in various courses and books that SRP is important and it's the first thing that you have to do when you want to write good quality code. Despite this, nobody seems to agree on what a piece of code that respects the single responsibility principle should look like. This is what we will be discussing today, how to recognize clean code, and how to bring our code in line (with examples).

1. Single responsibility
principle
Episode IV

2. What is SRP?

3. Is SRP only for OOP?

4. SRP is not simple

5. So how can we make it simple?

6. Naming things

7. Explicit variable names

8. Explicit function names

9. Functions that have side effects…

10. Should be clearly labeled

11. If you can’t tell what it does…

12. What does SRP code look like?

13. Is this SRP code?

14. Is this SRP code?

15. Is this SRP code?

16. Is this SRP code?

17. Is this SRP code?

18. Is this SRP code?

19. Is this SRP code?

20. Questions?