3. Individuals and interactions over processes and tools.
Working software over comprehensive
documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
Agile Development
17. A class should have one, and only one,
reason to change.
Single Responsibility Principle
18. Just because you can add everything you want into your
class doesn't mean that you should.
Ask yourself whether the logic you are introducing should
live in this class or not. Using layers in your application helps a
lot. Split big classes in smaller ones, and avoid god classes.
Single Responsibility Principle