logoNEURAL COOK
SearchAll PostsTagsNotesAuthor
instagramtwitterfacebookyoutubelinkedinmailgithubrss
Copyright © 2026 All rights reserved.
•
VIKI
Built with Vikramaditya Singh
Built with
VIKI - A posts created with Next.js and Tailwind.css
About
Composition, Asociation & Aggregation
Database locking / atomic updates
The Four Pillars of OOP
60-Day LLD & Machine Coding Mastery Roadmap
Class Design
Advanced Class Design & Robust Architecture
Clean Code
Don't Repeat Yourself (DRY) Principle
Keep it Simple, Stupid (KISS) Principle
You Aren't Gonna Need It (YAGNI) Principle
Design Patterns
Design pattern
Problems
Design a Library Management System (LMS)
Design a Parking Lot
Vending Machine
SOLID
D : Dependency Inversion
I : The Interface Segregation Principle
The SOLID Foundation
L : The Liskov Substitution Principle
O : The Open/Closed Principle
S : The Single Responsibility Principle
UML
UML Activity Diagrams: Modeling Process and Workflow
UML Class Diagrams: Static Structure Modeling
Unified Modeling Language (UML): Comprehensive Guide
UML Sequence Diagrams: Modeling Dynamic Interactions
Use Case Diagrams: Functional Requirement Modeling
Low Level Design›solid

The SOLID Foundation

Modern class design is governed by the SOLID acronym, which provides a roadmap for preparing for change:

  1. S - Single Responsibility: One class, one reason to change.
  2. O - Open/Closed: Extend behavior without modifying source code.
  3. L - Liskov Substitution: Derived classes must be perfectly swappable for their base classes.
  4. I - Interface Segregation: Don't force a class to implement methods it doesn't use.
  5. D - Dependency Inversion: Depend on abstractions (interfaces), not concrete implementations.
PreviousI : The Interface Segregation PrincipleNextL : The Liskov Substitution Principle