SOLID Principles you won't forget again

The SOLID principles are a set of design guidelines in software engineering that aim to make code more maintainable, scalable, and easier to understand. Here's an explanation of each principle with the examples you provided:

Single Responsibility Principle (SRP)

Definition: A class should have only one reason to change.

Bad Example:

csharp
 
1public class UserService
2{
3    private EmailService _emailService = new EmailService();
4
5    public void CreateUser(string email)
6    {
7        // logic
8        _emailService.Send(email);
9    }
10}

In this example, the UserService class is responsible for both creating users and sending emails. This violates SRP because if you need to change how emails are sent (e.g., changing from SMTP to another service), it would affect the CreateUser method.

Good Example:

csharp
 
1public interface IEmailService
2{
3    void Send(string email);
4}
5
6public class EmailService : IEmailService
7{
8    public void Send(string email)
9    {
10        // implementation
11    }
12}
13
14public class UserService
15{
16    private readonly IEmailService _emailService;
17
18    public UserService(IEmailService emailService)
19    {
20        _emailService = emailService
21
22[Read the full article at DEV Community](https://dev.to/sarupy/solid-principles-you-wont-forget-again-479o)
23
24---
25
26**Want to create content about this topic?** [Use Nemati AI tools](https://nemati.ai) to generate articles, social posts, and more.