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.
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 look at the importance of error tracking solutions, their role in software quality, and how to use them effectively.
In this article we’ll take a look at a fictitious piece of technical debt from inception to resolution and examine the true cost of technical debt.
Let me introduce you to my go-to code visualization and analysis tool for .NET: NDepend. NDepend lets me see dependencies, issues, and quality over time.
Less is more. We’ve all heard it, but when it comes to software quality, it’s definitely true. Less code means more quality.
Functional Debt is the direct result of previous business decisions that causes a degraded ability to address current or future business goals.
So you’re going to start fixing some of your technical debt? Great! Just remember the one cardinal rule: Don’t break the application. Think about it — when we get to take on technical debt the business paying an opportunity cost for us to refactor code instead of making new features or even […]