A .NET and TypeScript development manager’s top 5 practices for improving software quality from 2019, in no particular order.
Tag: Technical Debt
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.
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.
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 […]
Technical debt: We all have it and every developer worth their salt wants to pay it down, but how do we actually manage this process? Implementing a Crop Rotation In my article on communicating technical debt I compared paying down technical debt to the importance of crop rotations in farming. If […]
Many developers feel that product management and executive leadership don’t “get it” when we talk about technical debt. At the same time, if you ask developers about factors vital to the long-term success of a project, paying down technical debt is high on the list. So, how can we communicate […]