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

Good advice, but not an answer.

Elazar
– Elazar

2015-12-04 02:15:02 +00:00
Commented Dec 4, 2015 at 2:15
And funny, the artice you linked is basically a rant about how hard it is to rewrite a non-tdd-style code. "Those are bug fixes" that no one is aware about and there are no regression tests for them, so they are likely to reappear, or are now obsolete like the client configuration they target.

Elazar
– Elazar

2015-12-04 02:23:34 +00:00
Commented Dec 4, 2015 at 2:23
1

The only detail on the rewrite is that it is "unmaintainable", either the OP forgot what he did and is redoing it, or he is maintaining someone else's code. Either way, the article covers why rewriting is not a solution to the correct problem, because the problems were never identified.

Nelson
– Nelson

2015-12-04 02:25:36 +00:00
Commented Dec 4, 2015 at 2:25

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 »