Understanding Open-Closed Principle in 3 Minutes !

preview_player
Показать описание
SOLID is an acronym for the first five object-oriented design (OOD) principles by Robert C. Martin (also known as Uncle Bob). These principles establish practices that lend to developing software with considerations for maintaining and extending as the project grows. Adopting these practices can also contribute to avoiding code smells, refactoring code, and Agile or Adaptive software development. In this tutorial, you will be introduced to Open Closed Principle and understand how it works to make you a better developer. Open Closed Principle defines that software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification. In this tutorial, you learn Open Closed Principle with a code example. Solid principle in flutter.

Build a Flutter Todo App in 1 minute using ChatGPT

ChatGPT: Here's how to get a job at Google, Meta, Tesla ...

ChatGPT generates NFTs ! New Passive Income With ChatGPT !

I Lost $XXX after OpenAI's Secret Key LEAKED !!

Web Scraping using ChatGPT | Coded by ChatGPT

Flutter ChatGPT using OpenAI's GPT-3 | Flutter Chatbot

How to Solve Vertical viewport was given unbounded height | Flutter Common Error

Installation & Configuration | Flutter Firebase Tutorial #1

Firebase RealTime Database (CRUD) | Flutter Firebase Tutorial #3

How To Create A Flutter Table Calendar In Just 5 Minutes!

Dropdown in Flutter for creating flexible, reusable user interfaces

Object-oriented Programming in Dart

Flutter Project Ideas

Flutter Package Tutorials

#objectoriented #solidprinciple #objectorienteddesign #openclosedprinciple #softwareengineering #softwaredevelopment
Рекомендации по теме
Комментарии
Автор

Hey bro, you did a great job ! Really simple and clear explanation with example.

ydab
Автор

Thank you. Perfect video explanation.💌 Hope your channel will be viral in the near future.

viethuyho
Автор

Thanks for the explanation AI but wouldn't it make more sense to implement this pattern with an interface instead of inheritance? Doing it with an interface would make the result more composable because you can implement multiple interfaces while you can only extend one parent class.

wongalongtong