Note: This post is the first in a three-part series based around modeling the card game UNO [http://amzn.to/2aMn3ub] in a C# application. You may want to use the GitHub repository [https://github.com/exceptionnotfound/UnoModelingPractice] to follow along. I often find that one of the hardest things
June 2nd It went through! After all the effort the three of us put into this deal, the company we have been trying to purchase for more than a year is finally ours. They have got a great name, a wonderful team, myriad projects, and satisfied customers. And now they
I was re-reading the fantastic piece by Peter Welch called Programming Sucks [http://www.stilldrinking.org/programming-sucks], which is a classic despite it being only two years old. In the piece, Mr. Welch repeatedly demonstrates why programming (and the atmosphere surrounding it), well, sucks, which results in simultaneously hilarious and
I've lately been feeling my way around getting an actual, production-ready ASP.NET Core [http://www.asp.net/core] app developed, and one of the features I've really been digging (one of many [https://www.exceptionnotfound.net/tag/asp.net-core-1.0/]) is native support for Dependency Injection (DI). DI is
My team regularly writes ASP.NET Web API projects which have multiple consumers, and oftentimes we also write at least one of said consumers. To accomplish this, we often invoke a project layout and architecture that doesn't seem terribly obvious to newcomers to my group. I hope to better explain