Great explanation! As I'm in my pursuit of improving my architectural skills in programming, I've found your solid series very helpful! Can’t wait for the final part!
Wow, I really stopped almost at the end of the video and took a moment to think...but..what about default implementations, since we talk about kotlin here. And then I continued the video and 2 seconds later you mentioned it :D Great video series!
Thanks for the explanations, they were really on point! A couple of suggestions: In your first example, you could have also made the FootbalScoreBoardIf implement the base Scoreboard interface. This way, your FootbalScoreboard could have implemented directly this interface instead of implementing 2 interfaces. Also, I would say you could increase the font size of your IDE editor, it really helps for those watching your code and explanations on smaller screens (or phones like in my case). Having a bigger font size for your code will also fill up the empty space in your editor during recording. Keep up the great work!
Thank you very much for your comment! So, you can definitely do that, and inherit from the base interface, and it still is valid and actually less verbose which is a good thing. The reason I did not go with inheritance is because you have to be super sure about inheriting, that the sub-interface has a IS-A relationship with its parent interface, otherwise it can cause coupling down the line. In this particular scenario of course, footballScoreboard clearly IS-A scoreboard, so it is a good fit. Also, thank you for the advice for smaller screens, I will keep it in mind in the next one! Have a great day :)
Great explanation! As I'm in my pursuit of improving my architectural skills in programming, I've found your solid series very helpful! Can’t wait for the final part!
I really appreciate it and i am glad you liked it:)
I like when you explain the history of it. subscribed!
I really appreciate it and i am glad you like it :)
Wow, I really stopped almost at the end of the video and took a moment to think...but..what about default implementations, since we talk about kotlin here. And then I continued the video and 2 seconds later you mentioned it :D Great video series!
:D
Thanks for the explanations, they were really on point!
A couple of suggestions:
In your first example, you could have also made the FootbalScoreBoardIf implement the base Scoreboard interface. This way, your FootbalScoreboard could have implemented directly this interface instead of implementing 2 interfaces.
Also, I would say you could increase the font size of your IDE editor, it really helps for those watching your code and explanations on smaller screens (or phones like in my case). Having a bigger font size for your code will also fill up the empty space in your editor during recording.
Keep up the great work!
Thank you very much for your comment!
So, you can definitely do that, and inherit from the base interface, and it still is valid and actually less verbose which is a good thing. The reason I did not go with inheritance is because you have to be super sure about inheriting, that the sub-interface has a IS-A relationship with its parent interface, otherwise it can cause coupling down the line. In this particular scenario of course, footballScoreboard clearly IS-A scoreboard, so it is a good fit.
Also, thank you for the advice for smaller screens, I will keep it in mind in the next one!
Have a great day :)
👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍👍
Very nice your didatic!
I really appreciate it, thank you :)