Uploaded October 2024 | Updated September 2026, 1 week ago
Learn more at Brilliant brilliant.org/ZoranHorvat
This link gives you a 30-day free trial and 20% off of an annual premium subscription.
This video reveals the often-overlooked issues that arise when using an anemic domain model in software development. While at first glance, an anemic model—a model where domain objects lack behavior and contain only data—might seem straightforward, it can lead to significant complications that hamper scalability, maintainability, and expressiveness in your codebase.
Throughout the video, we demonstrate how using an anemic domain model leads to long argument lists, extensive validation blocks, and a combinatorial explosion of methods. We illustrate how primitive obsession and data clumps diminish code expressiveness and increase complexity. While this video will not teach you how to develop a proper object-oriented model, it remains a valuable starting point in understanding the motives for relying on a more expressive modeling method, such as object-oriented or functional design.
6. How Far is Your Object-Oriented Code From Functional Programming? youtu.be/kVEL6DWtOeM
Watch the entire series:
1. Fat services layer youtu.be/rA_4lb8UCQo
* 2. Combinatorial explosion of methods youtu.be/g63pLbUrzjI
3. Eliminating data clumps youtu.be/k1fIRmTsQMU
4. Adding polymorphism youtu.be/jgtPwXHTdHc
5. Make Your Object Model More Object-Oriented youtu.be/vSrKCHukzqY
Download source code ► patreon.com/zoranhorvat
Enroll course *Beginning Object-Oriented Programming with C#* ► codinghelmet.com/go/beginning-oop-with-csharp
Join Discord server with topics on C# ► codinghelmet.com/go/discord
Subscribe ► youtube.com/channel/UCxsWfh8LCcn55mFB6zGBT1g?sub_confirmation=1
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
👨 About Me 👨
Hi, I’m Zoran, I have more than 20 years of experience as a software developer, architect, team lead, and more. I have been programming in C# since its inception in the early 2000s. Since 2017 I have started publishing professional video courses at Pluralsight and Udemy and by this point, there are over 100 hours of the highest-quality videos you can watch on those platforms. On my YouTube channel, you can find shorter video forms focused on clarifying practical issues in coding, design, and architecture of .NET applications.❤️
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⚡️COPYRIGHT NOTICE:
The Copyright Laws of the United States recognize a “fair use” of copyrighted content. Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our youtube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above.
Learn more at Brilliant brilliant.org/ZoranHorvat
This link gives you a 30-day free trial and 20% off of an annual premium subscription.
This video reveals the often-overlooked issues that arise when using an anemic domain model in software development. While at first glance, an anemic model—a model where domain objects lack behavior and contain only data—might seem straightforward, it can lead to significant complications that hamper scalability, maintainability, and expressiveness in your codebase.
Throughout the video, we demonstrate how using an anemic domain model leads to long argument lists, extensive validation blocks, and a combinatorial explosion of methods. We illustrate how primitive obsession and data clumps diminish code expressiveness and increase complexity. While this video will not teach you how to develop a proper object-oriented model, it remains a valuable starting point in understanding the motives for relying on a more expressive modeling method, such as object-oriented or functional design.
6. How Far is Your Object-Oriented Code From Functional Programming? youtu.be/kVEL6DWtOeM
Watch the entire series:
1. Fat services layer youtu.be/rA_4lb8UCQo
* 2. Combinatorial explosion of methods youtu.be/g63pLbUrzjI
3. Eliminating data clumps youtu.be/k1fIRmTsQMU
4. Adding polymorphism youtu.be/jgtPwXHTdHc
5. Make Your Object Model More Object-Oriented youtu.be/vSrKCHukzqY
Download source code ► patreon.com/zoranhorvat
Enroll course *Beginning Object-Oriented Programming with C#* ► codinghelmet.com/go/beginning-oop-with-csharp
Join Discord server with topics on C# ► codinghelmet.com/go/discord
Subscribe ► youtube.com/channel/UCxsWfh8LCcn55mFB6zGBT1g?sub_confirmation=1
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
👨 About Me 👨
Hi, I’m Zoran, I have more than 20 years of experience as a software developer, architect, team lead, and more. I have been programming in C# since its inception in the early 2000s. Since 2017 I have started publishing professional video courses at Pluralsight and Udemy and by this point, there are over 100 hours of the highest-quality videos you can watch on those platforms. On my YouTube channel, you can find shorter video forms focused on clarifying practical issues in coding, design, and architecture of .NET applications.❤️
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⚡️COPYRIGHT NOTICE:
The Copyright Laws of the United States recognize a “fair use” of copyrighted content. Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our youtube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above.
