Размер видео: 1280 X 720853 X 480640 X 360
Показать панель управления
Автовоспроизведение
Автоповтор
Good Explanation with the basics..Very much informative learning video
Sir, thank you very much for the great explanation, I've leant so much in these 18 minutes 😁
Thanks Ashley 🙂
Your video is being alike daily dose... keep posting.
Thanks for the kind words Pawan. I’m glad that you are finding my videos useful 🙂
What if the protocols have the same method name and signature? Which method would you use when implementing multiple protocols
Nicely explained
thank you very much. This is such a great explanation!
Can you please make video on SOLID principles with proper examples in swift. I'm unable to find good examples of solid principles in other tutorials
Great job explaining! Subscribed!
Thanks for subscribing Christian. I’m glad that you liked it 🙂
Helped me to clear some concepts 🧑🏼💻
Thanks Mohit, I’m glad that you liked it 🙂
It was a really helpful video. Thanks a lot!!!
Thanks Prachi, Glad to hear that!
Nice!! Any specific reason for not using Xcode’s playground for demonstration?
Nothing specific, except that I was getting some issues on playground (didn’t want to speed time on those).Thanks 🙂
Thank you That was very helpful .
Thanks Palak, glad that you found the video helpful 🙂
You got a new sub
Great explanation...!
Glad you liked it!
is interfaces are same as abstraction or is there any differences in swift (just like java language has)?
Nicely explained 👌🏼
Thank you 🙂
Awesome video iCode
Awesome! Thanks man.
Thanks, glad that you liked the video 🙂
Great !!
Thanks for the video :)
Thanks Jose, glad that you liked it 🙂
love it
Thanks Marlon 🙂
instead of using three different protocol declarations for each skill set .. can we use single protocol with 3 different method declarations for each skill and making them optional .. will this be a better approach ?
what if you have more operations to perform for specific skill, which doesn’t make sense to bloat one single protocol
this would lead to fat interface problem which is mentioned in "ISP" of "solid" principles
This will break SOLID principle. Protocol should be segregated.
You missed the computed and stored properties for extensions.
Thanks for pointing it out. I’ll try to cover it in some other relevant video.
Now screen is visible properly with more clarity.
Thanks. Your feedback helps in making better content. Thank you :)
wow
Good Explanation with the basics..Very much informative learning video
Sir, thank you very much for the great explanation, I've leant so much in these 18 minutes 😁
Thanks Ashley 🙂
Your video is being alike daily dose... keep posting.
Thanks for the kind words Pawan. I’m glad that you are finding my videos useful 🙂
What if the protocols have the same method name and signature? Which method would you use when implementing multiple protocols
Nicely explained
thank you very much. This is such a great explanation!
Can you please make video on SOLID principles with proper examples in swift. I'm unable to find good examples of solid principles in other tutorials
Great job explaining! Subscribed!
Thanks for subscribing Christian. I’m glad that you liked it 🙂
Helped me to clear some concepts 🧑🏼💻
Thanks Mohit, I’m glad that you liked it 🙂
It was a really helpful video. Thanks a lot!!!
Thanks Prachi, Glad to hear that!
Nice!!
Any specific reason for not using Xcode’s playground for demonstration?
Nothing specific, except that I was getting some issues on playground (didn’t want to speed time on those).
Thanks 🙂
Thank you That was very helpful .
Thanks Palak, glad that you found the video helpful 🙂
You got a new sub
Great explanation...!
Glad you liked it!
is interfaces are same as abstraction or is there any differences in swift (just like java language has)?
Nicely explained 👌🏼
Thank you 🙂
Awesome video iCode
Awesome! Thanks man.
Thanks, glad that you liked the video 🙂
Great !!
Thanks for the video :)
Thanks Jose, glad that you liked it 🙂
love it
Thanks Marlon 🙂
instead of using three different protocol declarations for each skill set .. can we use single protocol with 3 different method declarations for each skill and making them optional .. will this be a better approach ?
what if you have more operations to perform for specific skill, which doesn’t make sense to bloat one single protocol
this would lead to fat interface problem which is mentioned in "ISP" of "solid" principles
This will break SOLID principle. Protocol should be segregated.
You missed the computed and stored properties for extensions.
Thanks for pointing it out. I’ll try to cover it in some other relevant video.
Now screen is visible properly with more clarity.
Thanks. Your feedback helps in making better content. Thank you :)
wow