DevCourseWeb.com    Tutorials    Development    C# SOLID Speedrun – Learn SOLID principles (2022)

C# SOLID Speedrun – Learn SOLID principles (2022)

 Admin0,

Learn how to develop efficient and effective software systems by applying SOLID Principles.

Welcome to the “C# SOLID Speedrun – Learn SOLID principles” course!

What you’ll learn

  • Students will learn C# SOLID principles and the basics of C# design patterns..
  • How to design efficient and effective softwares..
  • How to detect and correct code smells..
  • C# tips and tricks.

Course Content

  • SOLID Introduction –> 1 lecture • 6min.
  • Additional Content: OOP Recap –> 9 lectures • 1hr 22min.
  • Single Responsibility Principle –> 2 lectures • 18min.
  • Open Close Principle –> 2 lectures • 17min.
  • Liskov Substitution Principle –> 1 lecture • 12min.
  • Interface Segregation Principle –> 1 lecture • 10min.
  • Dependency Inversion Principle –> 2 lectures • 21min.
  • Additional Content: C# History –> 2 lectures • 11min.
  • Additional Content: Design Patterns –> 3 lectures • 31min.
  • Additional Content: GIT –> 4 lectures • 34min.

Auto Draft

Requirements

Welcome to the “C# SOLID Speedrun – Learn SOLID principles” course!

 

We are a team of C# developers, instructors and lifelong students. Our goal is to make coding easy to learn and review. Through our boots on the ground workshops, we have trained over one thousand students how to code and debug applications.

 

Our expertise: C#, Python, Java, JavaScript, HTML, CSS and many more. Are you ready? Let’s get started. For most of our courses, no previous experience is necessary.

 

This course will help you gain knowledge, tips, tricks and skills that will prepare you for your next C# interview and upgrade your C# skills.

 

Wikipedia defines SOLID as:

In software engineering, SOLID is a mnemonic acronym for five design principles intended to make object-oriented designs more understandable, flexible, and maintainable.

The SOLID ideas are

  • The single-responsibility principle: “There should never be more than one reason for a class to change.” In other words, every class should have only one responsibility.
  • The open–closed principle: “Software entities … should be open for extension, but closed for modification.”
  • The Liskov substitution principle: “Functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it.”[8] See also design by contract.
  • The interface segregation principle: “Many client-specific interfaces are better than one general-purpose interface.”
  • The dependency inversion principle: “Depend upon abstractions, [not] concretions.”

Let’s level up and prepare your next C# interview!

 

———————————

Keywords related to the course:

  • SOLID Principles Video Tutorial in C#
  • SOLID Tutorial
  • SOLID Principles
  • SRP, OCP, LSP, ISP, DIP
Get Tutorial