How I finally understood the Single Responsibility Principle
The Intro Welcome to the first stop of a five-part road trip through SOLID . Five letters, five principles, five posts, one tiny project per post th…
Latest Web news from Tech News
The Intro Welcome to the first stop of a five-part road trip through SOLID . Five letters, five principles, five posts, one tiny project per post th…
SRP says a class should have one reason to change. That does not mean one method or one line. It means one job. If a database change, a new JSON for…
SOLID isn't really five independent principles. It's mostly two long-standing software design ideas expressed in different ways. High cohesion — kee…
According to a 2024 vFunction survey, over 50% of companies watch more than a quarter of their entire IT budget vanish into technical debt. This isn…
The Problem You're building a system that supports multiple databases — MySQL, PostgreSQL, MongoDB. Different services in your application need to c…
A real story from building a manuscript submission system at a scientific publishing company. We were building a system at a Publishing Company that…
Every time a new requirement arrives, do you find yourself opening the same function and adding another elif block? If yes, your code may be signali…
1. Hook & Problem Statement You’ve been there. You're building a Laravel application, and everything is going smoothly. You type Route::get('/or…
SINGLE RESPONSIBILITY PRINCIPLE (SRP) A class should have one, and exclusively one , reason to change. In other words, we shouldn't have a single cl…
SOLID Principles in Ruby on Rails SOLID is not a Rails or Ruby concept. It's a set of five object-oriented design principles that apply to any langu…
I've just published SRP's Vocabulary Problem: Why Every Reformulation Failed . The Single Responsibility Principle has been criticized as vague, amb…