Development leadership must partner with the business and manage technical debt as risk in order for it to be fully understood and respected.
In this article we’ll define technical debt, its impacts, and causes and highlight some metaphors that are helpful when discussing technical debt.
So you’ve chosen to infect your codebase with God objects and enough complexity to generate hours of job security (AKA “Codethulhu”). Here’s how to succeed.
Let me tell you why you should take a good long look at F# and how it could fit into your team, the types of benefits it offers, and how it can change how you think about .NET development in general.
Scientist .NET, in a nutshell, lets you test experimental code safely without exposing errors or inaccuracy to end users.
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.