I was confused about the bridge pattern but now it's 100% clear ! thanks

Very good explained. This is the best explantation I found in three languages :D

In the first scenario I would do: 1. Make the different book types into regular classes instead of abstract. This because there's no added technical functionality specific to Autobiography for instance. Each of the book types serves as a final "template". 2. GetBookContent() is semantically identical in all book types and should be up one level like Publish() in IBook. So as mentioned at 3:01 you wouldn't need 3 new classes whenever you want to publish a book, but 3 objects.

Thank you! Very useful!!

I like these kind of videos! Very resourcefull

I love your explanation

Nice. Clean explanation

Thank you!

It’s funny that you had the phone call during the video

Fantastic video!

Very useful video, congrats

how it is different from strategy pattern?

Man, I really love your videos. I will set up a Paypal Acc just to be able to say thanks and donate

Well I did not understand the whole point of creating extra interfaces. May be I did not understand the example you are trying to explain. Will watch this video a few more times before it makes sense to me.

I feel this video was quite a bit rushed for the content, and as such the example wasn't really as effective in explaining the pattern. I understand you know the content very well but as an explanation video you need to meet your audience needs too.

Please do not code the data as a class for the example. No one codes this way; it only confuses people.