# discuss #softwareengineering #cleancode

Most "God Classes" don't start as God Classes.

A class begins with a single responsibility.

Then someone adds email functionality.

Then reporting.

Then payments.

Then logging.

A year later, one class is responsible for half the application.

This is exactly why the Single Responsibility Principle (SRP) exists.

One Class.
One Responsibility.
One Reason to Change.

I've just published the first article in my SOLID Principles series, where I explain SRP using real-world examples and simple pseudocode.

Curious to hear from the community:

What's the biggest "God Class" you've ever encountered, and how did your team deal with it?

DEV Community