Revision Notes/SOLID Principles
Field Entry - SOLID Principles
Single Responsibility Principle (SRP)
A class should have only one reason to change — it should do one thing and do it well.
Field Note - Real-world Analogy
“Like job roles in a restaurant. The chef cooks, the waiter serves, the cashier handles money, the cleaner tidies up. Imagine one person doing all four jobs — they'd be constantly switching context, overloaded, and a single person quitting would break everything. Separate responsibilities keep things manageable.”
Field Observations - Key Topics Covered
SRP doesn't literally mean a class can only have one method. It means a class should be responsible for one cohesive concern. If you can describe what a class does without using the word "and", you're likely following SRP.
4 more observations inside
Sign in to read every key point in full
Ready to go deeper?
Open the complete revision note.
Sign in to read every field observation in full, including a runnable code example and side-by-side comparisons with related patterns.
Read Full Notes