3 Oops, you did mention refactoring, so my original answer was wrong.
source | link

This is usually called 'refactoring'I would call these changes "technical debt payments". And it's the major reason forThat gives them the push for test driven development. Having a good test suite makes refactoring much more fearlessgravity they deserve. IfThey are changes you look upneed to make now to avoid even worse problems in the word 'refactoring' you'llfuture. No, they don't get all kinds of hitsyou anything new or shiny. You've already gotten the new and shiny thing, and there are books written about it.

The book "Refactoring: Improving the Design of Existing Code" isin the canonical text on this. There is also a website on refactoringcourse of doing it have incurred technical debt.

Refactoring canThis will also be referredencourage managers to as 'reducingthink about ways to avoid incurring the technical debt'debt in the first place. It's generally considered a vital partAdopting practices that reduce the number of any software engineering effortbugs (an important subset of which are security issues) that make it into production will then seem like a much better idea.

The wayI guess then that the sentence you give would re-phrase your statement is "Developers should test for regressions when refactoring the code-base.".

I'm actually pretty surprisedbe "When engaging in changes that the word 'Sprint' has made it into your vocabularyare technical debt payments, but notdevelopers should run regression tests to avoid incurring more technical debt in the word 'refactoring'process. But, then again, I guess I'm not surprised as the word 'Sprint' sounds like a bunch of people working very hard without reference to whether or not that work is sensible or not".

This is usually called 'refactoring'. And it's the major reason for the push for test driven development. Having a good test suite makes refactoring much more fearless. If you look up the word 'refactoring' you'll get all kinds of hits, and there are books written about it.

The book "Refactoring: Improving the Design of Existing Code" is the canonical text on this. There is also a website on refactoring.

Refactoring can also be referred to as 'reducing technical debt'. It's generally considered a vital part of any software engineering effort.

The way you would re-phrase your statement is "Developers should test for regressions when refactoring the code-base.".

I'm actually pretty surprised that the word 'Sprint' has made it into your vocabulary, but not the word 'refactoring'. But, then again, I guess I'm not surprised as the word 'Sprint' sounds like a bunch of people working very hard without reference to whether or not that work is sensible or not.

I would call these changes "technical debt payments". That gives them the gravity they deserve. They are changes you need to make now to avoid even worse problems in the future. No, they don't get you anything new or shiny. You've already gotten the new and shiny thing, and in the course of doing it have incurred technical debt.

This will also encourage managers to think about ways to avoid incurring the technical debt in the first place. Adopting practices that reduce the number of bugs (an important subset of which are security issues) that make it into production will then seem like a much better idea.

I guess then that the sentence you give would be "When engaging in changes that are technical debt payments, developers should run regression tests to avoid incurring more technical debt in the process.".

2 added 423 characters in body
source | link

This is usually called 'refactoring'. And it's the major reason for the push for test driven development. Having a good test suite makes refactoring much more fearless. If you look up the word 'refactoring' you'll get all kinds of hits, and there are books written about it.

The book "Refactoring: Improving the Design of Existing Code" is the canonical text on this. There is also a website on refactoring.

Refactoring can also be referred to as 'reducing technical debt'. It's generally considered a vital part of any software engineering effort.

The way you would re-phrase your statement is "Developers should test for regressions when refactoring the code-base.".

I'm actually pretty surprised that the word 'Sprint' has made it into your vocabulary, but not the word 'refactoring'. But, then again, I guess I'm not surprised as the word 'Sprint' sounds like a bunch of people working very hard without reference to whether or not that work is sensible or not.

This is usually called 'refactoring'. And it's the major reason for the push for test driven development. Having a good test suite makes refactoring much more fearless. If you look up the word 'refactoring' you'll get all kinds of hits, and there are books written about it.

The book "Refactoring: Improving the Design of Existing Code" is the canonical text on this. There is also a website on refactoring.

Refactoring can also be referred to as 'reducing technical debt'. It's generally considered a vital part of any software engineering effort.

This is usually called 'refactoring'. And it's the major reason for the push for test driven development. Having a good test suite makes refactoring much more fearless. If you look up the word 'refactoring' you'll get all kinds of hits, and there are books written about it.

The book "Refactoring: Improving the Design of Existing Code" is the canonical text on this. There is also a website on refactoring.

Refactoring can also be referred to as 'reducing technical debt'. It's generally considered a vital part of any software engineering effort.

The way you would re-phrase your statement is "Developers should test for regressions when refactoring the code-base.".

I'm actually pretty surprised that the word 'Sprint' has made it into your vocabulary, but not the word 'refactoring'. But, then again, I guess I'm not surprised as the word 'Sprint' sounds like a bunch of people working very hard without reference to whether or not that work is sensible or not.

1
source | link

This is usually called 'refactoring'. And it's the major reason for the push for test driven development. Having a good test suite makes refactoring much more fearless. If you look up the word 'refactoring' you'll get all kinds of hits, and there are books written about it.

The book "Refactoring: Improving the Design of Existing Code" is the canonical text on this. There is also a website on refactoring.

Refactoring can also be referred to as 'reducing technical debt'. It's generally considered a vital part of any software engineering effort.