When Not to Refactor
There are cases where it makes sense not to touch a legacy codebase with lots of technical debt. Unlike real debt that must always be repaid, technical debt doesn't always…
There are cases where it makes sense not to touch a legacy codebase with lots of technical debt. Unlike real debt that must always be repaid, technical debt doesn't always…
If you're working at a startup, chances are things need to go very fast. Faster than business that have a steady income. A product needs to get out the door…
So you have a working piece of software but you know the quality needs to improve. The team might be saying alarming things like "we need to rewrite this entirely."…
In the land of legacy code, many teams discuss whether they should refactor the existing application or rebuild it from scratch. But the answer to this problem is more nuanced…
In any project, there quickly arises a need for what we call refactoring. This is especially true in legacy projects. But what do we mean by refactoring exactly, and why…
The monolith is an architectural pattern where the software application consists of a single executable that is deployed as a whole. It can be difficult to work with when it…
Many legacy applications are difficult to run locally, on the developer's machine. I always recommend teams make it possible to run their code locally. After automated tests, it's a powerful…
Technical debt and legacy code are closely related but not exactly the same. Legacy code is a derogatory term to indicate old code that is no longer well-maintained. Technical debt,…