100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace

SOLID Principles Cheat Sheet

SOLID Principles Cheat Sheet

Explains the five SOLID object-oriented design principles with concrete before-and-after code examples for each one.

2 PagesIntermediateApr 2, 2026

The Five Principles

A one-line summary of each SOLID principle.

  • S - Single Responsibility- A class should have only one reason to change, i.e. one responsibility
  • O - Open/Closed- Software entities should be open for extension but closed for modification
  • L - Liskov Substitution- Subtypes must be substitutable for their base types without altering program correctness
  • I - Interface Segregation- Clients shouldn't be forced to depend on methods or interfaces they don't use
  • D - Dependency Inversion- High-level modules should depend on abstractions, not concrete low-level implementations

Single Responsibility

Splitting a class that has more than one reason to change.

java
// Violates SRP: handles both persistence and formattingclass Report {    void generate() { /* build report data */ }    void saveToFile(String path) { /* file I/O */ }    void printToConsole() { /* formatting + printing */ }}// Follows SRP: each class has one reason to changeclass Report {    void generate() { /* build report data */ }}class ReportSaver {    void saveToFile(Report report, String path) { /* file I/O */ }}class ReportPrinter {    void printToConsole(Report report) { /* formatting */ }}

Open/Closed & Dependency Inversion

Extending behavior through an abstraction instead of editing existing code.

java
interface PaymentMethod {    void pay(double amount);}class CreditCardPayment implements PaymentMethod {    public void pay(double amount) { /* charge card */ }}class PayPalPayment implements PaymentMethod {    public void pay(double amount) { /* charge PayPal */ }}// Adding a new payment method requires no changes to Checkoutclass Checkout {    private final PaymentMethod paymentMethod;    Checkout(PaymentMethod paymentMethod) {        this.paymentMethod = paymentMethod;    }    void completeOrder(double total) {        paymentMethod.pay(total);    }}

Liskov Substitution & Interface Segregation

A subtype that breaks its parent's contract, and a fat interface split apart.

java
// Violates LSP: Square changes Rectangle's expected behaviorclass Rectangle {    protected int width, height;    void setWidth(int w) { width = w; }    void setHeight(int h) { height = h; }    int area() { return width * height; }}class Square extends Rectangle {    void setWidth(int w) { width = height = w; }  // breaks Rectangle's contract    void setHeight(int h) { width = height = h; }}// Follows ISP: split a fat interface into focused onesinterface Printer { void print(Document d); }interface Scanner { void scan(Document d); }// SimplePrinter only implements Printer, not forced to implement scan()class SimplePrinter implements Printer {    public void print(Document d) { /* ... */ }}

Dependency Inversion with a Composition Root

Wiring concrete implementations to abstractions in one place instead of letting high-level modules construct their own dependencies.

typescript
interface Logger {  log(msg: string): void;}class ConsoleLogger implements Logger {  log(msg: string) { console.log(msg); }}class OrderService {  // depends on the abstraction, injected, not `new ConsoleLogger()` inline  constructor(private logger: Logger) {}  placeOrder(id: string) {    this.logger.log(`order ${id} placed`);  }}// Composition root -- the only place that knows concrete typesconst logger: Logger = new ConsoleLogger();const service = new OrderService(logger);// Swapping to a FileLogger or NullLogger (for tests) touches only// this one wiring point, never OrderService itself.

Interface Segregation with Role Interfaces

Splitting a fat repository interface into small, role-specific interfaces so consumers depend only on what they call.

typescript
// Fat interface -- every implementer must support everythinginterface UserRepository {  findById(id: string): User;  save(u: User): void;  delete(id: string): void;  bulkImport(rows: User[]): void;  auditLog(): AuditEntry[];}// Segregated role interfacesinterface UserReader {  findById(id: string): User;}interface UserWriter {  save(u: User): void;  delete(id: string): void;}// A read-only reporting service depends only on UserReader --// a mock in tests implements one method, not five.class ReportingService {  constructor(private users: UserReader) {}}

Spotting SRP Violations via Method-Field Cohesion

A concrete technique for detecting classes with more than one reason to change before splitting them.

python
# Smell: methods cluster into two disjoint groups that never touch# the same fields -- a sign the class has two responsibilities.class InvoicePrinter:    def __init__(self, items, tax_rate):        self.items = items        self.tax_rate = tax_rate        self._connection = None          # only used by save_* methods    def subtotal(self):                  # touches: items        return sum(i.price for i in self.items)    def total(self):                     # touches: items, tax_rate        return self.subtotal() * (1 + self.tax_rate)    def save_to_db(self):                # touches: _connection only        self._connection.execute("INSERT ...")    def save_to_s3(self):                # touches: _connection only        self._connection.upload(...)# subtotal/total form one cluster (pricing logic); save_to_db/save_to_s3# form another (persistence) -- split into InvoiceCalculator and# InvoiceRepository.

LSP Beyond Types: Pre/Postcondition Contracts

Liskov substitution is violated by strengthened preconditions or weakened postconditions, not just type signatures.

java
class FileValidator {    // precondition: path must be non-null    boolean isValid(String path) {        return path != null && path.endsWith(".txt");    }}// Violates LSP: strengthens the precondition (now also requires// the file to exist on disk), which callers of the base type// don't expect and won't check for.class StrictFileValidator extends FileValidator {    boolean isValid(String path) {        return super.isValid(path) && new File(path).exists();    }}// A caller written against FileValidator that passes a path for a// not-yet-created file works with the base class but throws// unexpected behavior downstream when swapped to StrictFileValidator --// LSP requires subtypes to only weaken preconditions or strengthen// postconditions, never the reverse.

Code Smells That Map to SOLID Violations

Recognizable symptoms and which principle they typically point back to.

  • God class / God object- Usually a Single Responsibility violation: too many unrelated reasons to change live in one class
  • Long chain of if/else on type codes- Often an Open/Closed violation -- replace with polymorphism so new types don't require editing existing branches
  • instanceof / type-checking before calling a method- A common Liskov Substitution smell -- the caller shouldn't need to know the concrete subtype
  • Interface with unused method stubs (throw NotImplementedError)- Classic Interface Segregation violation -- the interface is forcing capabilities the implementer doesn't have
  • `new ConcreteClass()` sprinkled through business logic- Dependency Inversion violation -- high-level code is bound to low-level construction details
  • Shotgun surgery- A single conceptual change requires edits across many classes, often from a missing abstraction (DIP) or split responsibility (SRP)
Pro Tip

Treat SOLID as heuristics, not laws — over-applying Dependency Inversion or Interface Segregation to simple, stable code adds indirection without payoff. Apply them where change is actually expected.

Was this cheat sheet helpful?

Explore Topics

#SOLIDPrinciples#SOLIDPrinciplesCheatSheet#Programming#Intermediate#TheFivePrinciples#SingleResponsibility#Open#Closed#OOP#CheatSheet#SkillVeris

Frequently Asked Questions

21 categories · pick one to explore

Does SkillVeris have a tech blog, and what does it cover?
Yes, the SkillVeris blog has over 500 articles covering AI and machine learning, programming, web development, DevOps, cloud, security, databases and career guidance. Articles are practical and answer-first, and many use the Learn Through Hobbies approach, teaching technical concepts through cricket, music, gaming or cooking analogies. Everything is free to read.
What is the SkillVeris tech glossary and how big is it?
The SkillVeris glossary is a free reference of roughly 2,000-plus technology terms, each with a clear plain-language definition. It spans AI, programming, web, DevOps, cloud, security and database vocabulary, so whenever a lesson, article or job description uses jargon you do not recognise, the glossary gives you a fast, reliable answer.
Are the developer cheat sheets on SkillVeris free to download?
The cheat sheets are completely free to use, like everything else on SkillVeris. Each sheet condenses a language or tool into its essential syntax, commands and patterns for quick reference while coding. They are designed for rapid lookup during real work, complementing the deeper explanations found in study notes and courses.
Which programming references and cheat sheets are available?
Cheat sheets cover the platform's main domains, including programming languages, AI and ML tooling, web development, DevOps, cloud, security and databases, matching the topics of the 37 live courses. Each sheet lists related reading links and hashtags, so you can jump from a quick reference into fuller study notes or blog articles.
How do I find the meaning of a technical term quickly?
Search the SkillVeris glossary, which holds around 2,000-plus terms with concise, plain-language definitions. Each entry gets to the point in its first sentence, then links to related reading like blog posts or study notes for deeper context. It is faster and more consistent than sifting through scattered search results.
Is the SkillVeris blog good for beginners learning to code?
Yes, many blog articles are written specifically for beginners, and the Learn Through Hobbies style makes them unusually approachable: you might learn Python concepts through cricket or understand APIs through cooking. With 500-plus articles across skill levels, beginners can start with fundamentals and keep reading as they advance, entirely free.
Can cheat sheets replace full courses for learning a language?
No, cheat sheets are references, not teaching tools; they assume you already understand the concepts and just need syntax or commands fast. To actually learn a language, take a structured SkillVeris course with its 24–40 lessons and assessments, then keep the cheat sheet beside you while practising in Code Lab.
How often are new blog articles published on SkillVeris?
The blog grows regularly and already exceeds 500 articles, with new posts added as courses launch and technologies evolve. Topics track the platform's catalogue across AI, programming, web development, DevOps, cloud and security, so checking the Blog section periodically surfaces fresh tutorials, explainers and career-focused pieces, all free to read.
Does the glossary cover AI and machine learning terms?
Yes, AI and machine learning vocabulary is a major part of the roughly 2,000-plus term glossary, covering everything from foundational terms to modern concepts around LLMs, RAG and MLOps. Definitions are plain-language and answer-first, which helps when dense AI papers or course lessons throw unfamiliar jargon at you.
Are there cheat sheets for interview preparation?
Cheat sheets work well as interview-day refreshers because they compress syntax, commands and key concepts into scannable references. For dedicated preparation, combine them with the SkillVeris interview questions feature, which includes readiness scoring, plus study notes for depth. Reviewing a relevant cheat sheet just before an interview steadies recall under pressure.
Can I read the tech blog without signing up?
Yes, the blog is freely readable, and SkillVeris never charges for content. All 500-plus articles are open, covering tutorials, concept explainers and career advice. Creating a free account adds value elsewhere on the platform, like course progress tracking and certificates, but reading the blog requires no commitment at all.
How is the SkillVeris glossary different from Wikipedia?
The glossary is purpose-built for learners: definitions are short, plain-language and answer-first, sized for a quick lookup mid-lesson rather than a deep encyclopedic read. Entries also cross-link to related SkillVeris study notes, blog posts and courses, so a definition becomes a doorway into structured learning instead of a dead end.
Do blog articles use the Learn Through Hobbies method?
Many blog articles teach technical topics through hobby analogies, a hallmark of the SkillVeris blog, so you will find articles explaining programming through cricket, machine learning through music, or system design through cooking. The analogy is the teaching device; the article still delivers the real technical concept underneath.
Where can I find quick programming references while coding?
Open the SkillVeris cheat sheets, which are built exactly for that moment: compact, scannable references for syntax, commands and common patterns across languages and tools. Keep the relevant sheet in a browser tab while you work in Code Lab or your own editor, and dip into the glossary for terminology.
Is there a glossary entry for terms I meet in job descriptions?
Very likely yes, with roughly 2,000-plus terms across AI, programming, web, DevOps, cloud, security and databases, the glossary covers most jargon that appears in tech job descriptions. Decoding a listing this way helps you judge role fit honestly and prepares you to discuss those terms in interviews.
Are the blog articles written for the Indian tech audience?
The blog serves Indian learners plus a worldwide audience. Content stays globally relevant while acknowledging realities that matter in India, such as free access being essential for students and freshers, and career guidance that connects naturally to the SkillVeris jobs portal, which aggregates roles across India, UK, USA, Germany and Remote.
Can I suggest a topic for the blog or glossary?
SkillVeris content grows in response to what learners need, so feedback is welcome through the platform's support channels. If a term is missing from the glossary or a topic deserves an article, telling the team helps prioritise it. Meanwhile, the AI Mentor can answer the question immediately, 24/7, at any depth.
Do cheat sheets and glossary entries link to deeper learning?
Yes, every cheat sheet and glossary entry carries related reading links into study notes, blog articles and courses, plus concept hashtags for discovering similar content. This cross-linking means a thirty-second lookup can smoothly become a structured learning session whenever you decide you want more than a quick answer.
What makes SkillVeris programming references trustworthy?
The references are written to strict internal quality standards, kept consistent with the platform's 37 live courses, and never padded with invented statistics or hype. Definitions and cheat sheets are reviewed against the same content contracts that govern courses, and the answer-first style makes any inaccuracy easy to spot and correct.
How do the blog, glossary and cheat sheets fit into my learning routine?
Use them as satellites around your main course: read blog articles for context and motivation, hit the glossary the instant jargon appears, and keep cheat sheets open while coding. Together with study notes, Code Lab and the 24/7 AI Mentor, they turn passive reading into a complete, free learning system.

What Learners Say

Real journeys from the SkillVeris community — swipe for more.

SkillVeris taught me Python through Cricket. Now I’m building real projects and feeling confident!
Arjun S. · B.Tech Student
The best platform for hobby-based learning. Concepts finally stick.
Priya R. · Data Analyst
I went from zero coding to a portfolio of projects — all by learning through my love for gaming. Landed my first internship!
Kabir M. · CS Undergraduate
Trending Topics50 popular tags — tap to explore
Trending CoursesAll 37 free courses — tap to browse