What the fuck did I just watch, I don't know how you managed to keep me hooked for 30 minutes in a video about ducks. Solid work man, great teachers do matter.

1:10 did he just say the inventor of null is Tony Whore?

You still need an address of the concrete observable if you need to remove the observer from the list of observers inside the observable.

46:37 Could not be more clear to explain the pull by moving to the Observer side. Thoughtful!

You teach in a nice and funny way, well done, thank you❤❤❤

As usual, beautiful explanation.💎The best I have ever seen so far.

A real teacher! I love ur videos. U really rock!!!❤

Good and funny. Christopher has a nice way of explaining difficult concepts in simple terms. I loved the video.

Marvelous explanation

It's a big difference to having WET domain logic, or trying to make DRY all helper functions possible in some "utils" package.

Excellent explanation. Period.

Excellent explanation. Period.

I just watched your intro 3 times and laughed every time. Great physical comedy. Also very informative

Yor chanell is just a treasure even in December of 2024

Hi, I just wanted to thank you, because this diagram and your approach to the subject really made me grasp those concepts I've been seeing on other channels, which are centered more towards experienced programmers than beginners like myself. Something really clicked, and now I think I'm starting to see *why* those programmers program the way they do. God bless

If we make the decision to go forward all the time possibly we can easily ship a login with a session, users, roles, permissions; but what if? It was obvious since the beginning an ABAC was going to be needed would that worth the complexity for starts?

FFS, another word salad like all the other videos on this topic

@Christopher Okhravi, what about spring singletons? Feature: Thread Safety Manual Singleton: Must ensure explicitly (e.g., static inner). Spring Singleton: Handled automatically by Spring. Feature: Ease of Use Manual Singleton: Requires boilerplate code. Spring Singleton: Simpler and more declarative. Feature: Testability Manual Singleton: Hard to mock. Spring Singleton: Can inject mocks using DI in tests. Feature: Flexibility Manual Singleton: Hard to replace or extend. Spring Singleton: Can configure beans dynamically. Do you see it as avoidable and violating best practices and principles?

Thank you man very much

How does AI change these?

Until companies see the value of experience this will never be the case. Currently companies see AI as being the experience needed by junior devs. This may seem madness until you see who are making these decisions; managers who have never coded.

Loved the lecture. You talk of covariance and contravariance but also invariance (the lack of or nullifying of variance). Are there examples of purely invariant code or are you saying use Generics, Classes or Functions to move to this state?

Although it's called the Singleton Pattern, it subtly violates the Single Responsibility Principle (SRP) as it's responsible for two things : 1. To make sure that the class has only one instance 2. To provide global point of access to it.

1926 version was removed : 1928 is a second edition

Just learned about it, it's an amazing principle

those quarking ducks

Even in 2024 its relevant. Amazing tutorial.

An hour video for one PATTERN? Yup I'm going to fail my exam.

You're an absolute legend, even from seven years ago 🥰🥰🥰

Why am I this late to the party? It's been 7 years, and I was totally unaware whole that time.

function SemiGroup(value) { this.value = value } SemiGroup.prototype.concat = function(semigroup) { if (this.constructor.name !== semigroup.constructor.name || this.constructor.prototype !== semigroup.constructor.prototype) { throw new Error('not type') } return new SemiGroup(this.value + semigroup.value) } const foo = new SemiGroup(1) const bar = new SemiGroup(5) console.log(foo.concat(bar))

Explain how in this example it provides global access!?? When I say it does it mean class?? So how a class with no global access look like?

In Swift, "MutableCollection" inherits from "Collection". Seems like .Net could solve some conceptual problems if they did the same. Well, "IMutableCollection", I suppose, since MS seems to think the name defines what something is as opposed to just looking at the AST and checking if it's an interface or a class. Remindsof them thinking i can change a file from Word to a PDF just by renaming it.

I don't understand why you wouldn't just define quack() in the superclass and overload it in any of the subclasses? Doesn't that achieve the same thing?

i can't believe this playlist was release 7 years ago , it still is so relevant in 2024.

I guess an old dog can learn new tricks. (arf, arf!)

Anyone thinking how before pointcuts might fit in? Would it be better or worse?

What would the generic Factory be in teh asteroids example? The class that AsteroidFactory and PowerupFactory would inherit from?

The best video on strategy pattern. Pure 💎

Mind-blowing, explanation. Thank you so much.

One thing I keep tripping up on.. Is an Interface a Class? Because it sounds like we're taking a class (of say, different ingredients..) and just breaking it down into its more fundamental components (ingredients) so that other sub classes can cherry-pick exactly what they need

I love your teaching pattern. And I want to learn all these patterns from this playlist.

ربنا يوفقك ويسعدك تم عندك

Now I finally understand interfaces and the Strategy Pattern ! Amazing job!!

this is the best explanation I have come across. Makes it easier to remember and easier to convey the message to fellow devs

This is avery succinct and simple explanation of when to use subtypes versus interfaces. I've never heard it expressed in those specific terms.

so contravariance === generics?

great explanation! Thanks bro.

Crazy explanation, bro! No one will forget this concept now.

What's missing is that we separate the invoker from a receiver. Therefore , we gain scalability, maintainability and reusability.