Solid Principles Interview Questions - You Might Get Them
Vložit
- čas přidán 27. 07. 2024
- Learn solid principles interview questions that you can get really often. This is the core knowledge that every developer must learn and use.
TIMESTAMPS
0:00 Introduction
0:47 Single responsibility principle
2:04 Open closed principle
3:47 Liskov substitution principle
6:02 Interface segregation principle
7:59 Dependency inversion principle
► CHECK MY COURSES - monsterlessons-academy.com/co...
MOST POPULAR COURSES
► Building real project with Angular + NgRx - monsterlessons-academy.com/co...
► Building real NestJS API - monsterlessons-academy.com/co...
► Javascript interview questions - monsterlessons-academy.com/co...
► Angular Interview Questions monsterlessons-academy.com/co...
► Building real fullstack project - monsterlessons-academy.com/co...
► Mastering Git - monsterlessons-academy.com/co...
► Mastering Docker and Docker Compose - monsterlessons-academy.com/co...
► Building real project with React Hooks - monsterlessons-academy.com/co...
► Building real project with Vue + Vuex - monsterlessons-academy.com/co...
FOLLOW ME
► TWITTER - / monster_lessons
► INSTAGRAM - / monsterlessonsacademy
► TIKTOK - / monsterlessonsacademy
You are the ultimate teacher. For Real. Can't stop watching your videos. And you teach the most important things in the simplest way.
Wow thanks!
I respectfully salute you ! Thank you
Thank you
Вельмі карысныя відэа з простымі і эфектыўнымі тлумачэньнямі. Дзякуй!
Always waiting for your video , appreciate your efforts on your topics
Thanks a ton!
Can you please do a course or video on chrome dev tools ? That would really be great as not many are covering this topic. Barely some courses on udemy about this one
and that too outdated.
I will add to to the list of ideas!
Love it! Short and to the point 😄
Thanks! 😊
Hi sir.. which design principle is better in angular application
All of them. It is appliable to any language of framework
I think the example for Liskov substitution is wrong. Because we can write something like this: For the square object -> square.width = 5; square.width = 4; then the getArea method will return 16. However, for the rectangle object -> rectangle .width = 5; rectangle .width = 4 getArea method will return 20; So the same method with the same parameters returns two different results. Isn't this a violation of the LISKOV rule? Shouldn't we have a separate implementation for getArea?
This is the example which people typically use to show this principle. Most importantly that you understand why you need one or another.
I'm interested about your insights in Bun
I will add it in the list of ideas. Thank you!