S.O.L.I.D Design Patterns - Unity - Interface Segregation Principle

Just Here To Plug My Social Media Stuff:

[beardordie]

Well done, very clearly explained. Thank you for the video!

[choristorgarage]

That was a cool explanation for the ISP. Thanks!

[remibauduin]

Well done! Very well explained, this was interesting :)

[danielvillalba]

Very well explained, Im going for the rest of the principles, way to go!

[RichyAsecas]

I usually find myself dwelling on that sort of abstractions like in this case ICharacter, that's an interface with several properties, which shape basically an abstracted data structure — plus behaviour defined by such an interface's methods. I've never found if this is a proper way to architecture, neither another way without losing mocks capabilities, as they need interfaces — or virtual definitions, but that's kinda cumbersome and... brittle, I guess?