Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Subscribe
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
SOLID Design Principles
Rating: 4.5 out of 5(122 ratings)
2,606 students

SOLID Design Principles

Learn Craftsmanship of the Software -- How to write the code in maintainable, reusable and extensible way
Created byGulshan Bajaj
Last updated 7/2024
English
English [Auto],

What you'll learn

  • SOLID Design Principles
  • Singleton Design Principles
  • Open Closed Principle
  • Liskov Substitution Principle
  • Interface Segregation Principle
  • Dependency Inversion Principle

Course content

1 section • 7 lectures • 45m total length

  • Introduction9:54

    Explore the five solid design principles—single responsibility, open-closed, substitution, interface segregation, and dependency inversion—to structure software, improve understandability, maintainability, and reusability across modules.

  • Single Responsibility Principle8:18

    The single responsibility principle requires a class to have a single reason to change for one actor; splitting do work, report work, and see work into separate classes improves maintainability.

  • Open Closed Principle4:29

    The open closed principle states software should be open for extension but closed for modification; abstract vehicle classes enable new sports vehicle types without changing code, reducing testing and maintenance.

  • Liskov Substitution Principle8:46

    Discover the Liskov substitution principle by examining a rectangle–square example; learn to extend inheritance without altering parent behavior, avoid new exceptions, and keep client code agnostic to concrete types.

  • Interface Segregation Principle5:02

    Explore the interface segregation principle by splitting a two-method mic interface into separate record and play interfaces, improving reusability and reducing recompilation across languages.

  • Dependency Inversion Principle8:20

    Apply the dependency inversion principle by having the application, a high-level module, depend on a service interface instead of a concrete low-level service, enabling flexible implementations.

  • Next Steps0:15

Requirements

  • Any object oriented programming langugage

Description

Clean code is actually Craftsmanship.

Writing a clean code requires knowledge and work. For writing clean code, we need to know the common mistakes which we may leave behind and the best practices which we should follow.


This course covers how to use good comments, when to use them, how to name the variables in the programs, how to design the functions and classes based on the software design principles e.g. Single Responsibility Principle, Open Closed Principle and Dependency Inversion Principle etc.

Learning how to write clean code requires your effort, time and a good intention of understanding its importance. You will enjoy and appreciate this course if you agree that the professional code you write serves some purpose to the society. It is used by your users, your customers, the software maintenance team and the testing team. Your code is written once and is maintained for years. A clean, properly arranged and easily maintainable code can easily serve this purpose.

Writing a clean code requires you to be a smart programmer. In programming smartness is not writing code which nobody can understand, rather it is in writing such a self explanatory code, which is easily understandable by others. Clarity is the King!

If you agree on the above, I promise that you will enjoy all the material covered in this course and you will find it worth your time and effort!

Let me invite you to start this journey on writing a clean code, a better code, a professional code. Let's get started.


Who this course is for:

  • Software Developers
  • Students

Report abuse