Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

You can call this "an excuse". Or you can call it "the boyscout principle" (leave a code base in a better state behind than you found it). Improving the code around some bug can be more effort than just fixing the bug. But when it comes to evaluating where it pays off most to refactor some code, the places where bugs were found are often excellent candidates.

Doc Brown
– Doc Brown

2022-12-12 11:06:28 +00:00
Commented Dec 12, 2022 at 11:06
... and rewriting a certain piece of code (instead of making a local fix) can affect other parts of the code base (or the behaviour) even more, so this argument is IMHO not conclusive.

Doc Brown
– Doc Brown

2022-12-12 12:21:40 +00:00
Commented Dec 12, 2022 at 12:21

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »