Scientist .NET, in a nutshell, lets you test experimental code safely without exposing errors or inaccuracy to end users.
Author: Matt Eland
In this short and sweet opinion post, I’ll rant like a crazy man on the dangers inherent in living with compiler or linter warnings (at least I’m honest).
In this article we’ll explore the use of feature branches based off of GitWorkflow to integrate features and fixes only when they are fully ready to go. While this is a less well-known workflow than others, it offers a significant degree of freedom and flexibility. We won’t be covering all […]
In this article, we’ll discuss some sources of conflicts between developers and quality assurance and the advantages of a true partnership between the two – as well as some ideas on how to get there.
In this article we’ll look at the importance of error tracking solutions, their role in software quality, and how to use them effectively.
One of the hallmarks that distinguishes a senior developer from a junior developer is the art of planning. I’m not talking resource allocation or scheduling (though those are important). I’m talking about getting a task, sitting down at the keyboard, and explicitly not coding.
In this article we’ll discuss what Roman military tactics and modern security practices have to do with protecting users from software defects.
In this article we’ll introduce genetic algorithms by teaching a squirrel how to find food and shelter, then see how different fitness functions can influence its behavior. Along the way we’ll discuss concepts of genetic algorithms, the F# programming language, and important design considerations in artificial intelligence applications.
In this article, I’ll propose a C# solution to a common testing problem with enums using a special NUnit attribute. I’ll also introduce you to a related attribute which can expand your tests.