5d ago · 14 min read · TLDR TLDR: KISS (Keep It Simple), YAGNI (You Aren't Gonna Need It), and DRY (Don't Repeat Yourself) are the three most universally applicable software engineering mantras. They share a common enemy: unnecessary complexity. 📖 The Complexity Tax Ev...
Join discussion5d ago · 10 min read · TLDR TLDR: The Single Responsibility Principle says a class should have only one reason to change. If a change in DB schema AND a change in email format both require you to edit the same class, that class has two responsibilities — and needs to be s...
Join discussion5d ago · 19 min read · TLDR TLDR: An elevator system is a textbook OOP design exercise: ElevatorCar encapsulates its stop queue, ElevatorState polymorphically handles direction changes (State Pattern), and DispatchStrategy keeps assignment algorithms swappable (Strategy P...
Join discussion5d ago · 12 min read · TLDR TLDR: The Interface Segregation Principle (ISP) states that clients should not be forced to depend on methods they don't use. Split large "fat" interfaces into smaller, role-specific ones. A RoboticDuck should not be forced to implement fly() j...
Join discussion5d ago · 11 min read · TLDR TLDR: The Open/Closed Principle (OCP) states software entities should be open for extension (add new behavior) but closed for modification (don't touch existing, tested code). This prevents new features from introducing bugs in old features. ...
Join discussion5d ago · 12 min read · TLDR TLDR: The Dependency Inversion Principle (DIP) states that high-level business logic should depend on abstractions (interfaces), not on concrete implementations (MySQL, SendGrid, etc.). This lets you swap a database or email provider without to...
Join discussionFeb 19 · 3 min read · As software developers, we often focus on making things work. But as systems grow, teams expand, and requirements change, a more important question arises: Can this code survive change? This is where design principles come into play. Design princip...
Join discussion
Feb 16 · 2 min read · SOLID principles help us design clean, scalable, and maintainable object-oriented systems.Today, I focused on the “O” — Open/Closed Principle. ⸻ 🔹 What is the Open/Closed Principle? Software entities (classes, modules, functions, etc.) should ...
Join discussion
Feb 16 · 2 min read · SOLID principles are a set of five guidelines that help us write clean, scalable, and maintainable object-oriented code.Today, I focused on the “S” — Single Responsibility Principle. 🔹 What does SRP say? A class should have only one reason to ch...
Join discussion
Feb 16 · 2 min read · Continuing my SOLID journey, today I studied the Liskov Substitution Principle (LSP) — a principle that protects systems from fragile inheritance and unexpected behavior. 🔹 What does LSP say?If S is a subtype of T, then objects of type T should be r...
Join discussion