For the future of the project, it's important that class files are laid out in a way that they are easy to read and modify and do consistently. We do this to avoid “spaghetti code” that does not give developers a good feeling about the stability of the project. In this article, I will show exactly how I format code classes. In this article, I will show exactly how I format code classes by example.
I am pleased to announce the new release (v2022.6.11.14) of Spargine on November 14th, 2022, my open-source projects, and NuGet packages for .NET 6 & 7. I have added new classes, methods, benchmarks, and unit tests! I use these in all the projects I work on, including many in production!
This article shows how to use the DotNetTips.Utility.Standard.Tester NuGet package to generate random data for use in unit and benchmark testing.
For the first time, I will be on the live show On .NET Live, on August 22nd, 2022 at 9 am PST. I'm so excited to chat about two of my favorite subjects, code quality, and code performance! This is going to be fun.
The dotNetDave For Those About to Code: Worldwide Tour will be at the Code Quality Conference 2022 on August 19th. Last year we had over 72K software engineers watch the conference and I hope you will watch it this year to learn how to rock your code to release quality applications and services that meet your user's needs.
In this article, I’m going to discuss new extension methods and show examples for validating data. In much of the code we write, we validate the state of a variable. In many cases, we use this to change program flow. These methods that I will describe make this very easy along with some added features.
For my work moving Spargine to .NET 6, I have completely rewritten the Spargine methods to validate method parameters. In this release, these methods have been changed to allow fluent validation.
The dotNetDave For Those About to Code: Worldwide Tour will be at the Philly Code Camp in Philadelphia, PA on March 4th. I hope you will join me at this meeting.
Let’s face it, no software engineers like fixing bugs in code. Since no software is perfect, they are going to happen. They are a fact of life for software engineers. Sometimes, it feels like we are playing the game Whack-A-Mole where no matter how many we fix, more will pop up.
Lets face it, none of us write perfect code all the time! Especially since there are many ways to write the code to achieve its purpose. The best way to make sure the code is the best it can be is by asking someone to review it!
dotNetTips.com 
You must be logged in to post a comment.