#interfaces#solid#dependencyinjection
13K subscribers • 1 video on Hallway
Intermediate. Assumes working knowledge.
1.8K views7 years ago2 recommendations
Software designProgramming languagesDesign patternsSoftware architectureC# and .NET
Shiv Kumar argues against the over-use of interfaces in C# and explains why concrete classes are often a better choice.
Program to Interface and not implementation - this statement has been completely misunderstood. As a result, folks have an interface backing every class in their system. That's just insane. In this video I debunk multiple stated virtues of interfaces and make a case for using classes instead. Along the way I also include the history of interfaces and certain languages where interfaces do provide some of the stated benefits. In C# however, there's not much difference if any. See if I'm able to convince you not to use Interfaces More articles and Programming With Intent chapters: matlus.com/ Programming With Intent: matlus.com/pwi/ Read the article: matlus.com/writing/interfaces-no-thank-you/What people say. Recommended by developers looking to avoid over-engineering and unnecessary dependency injection boilerplate.
u/laDoucheein r/dotnet • Recommends
On “In search of the (at least damn near)perfect application architecture...”
u/entityadamin r/dotnet • Recommends
On “Why are c# developers obsessed with interfaces?”