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

3

You need to be very careful 'reusign large swaths of code', this can lead to unused legacy code and poor code structure. Refactoring is a better solution in my opinion.

mrwooster
– mrwooster

2011-01-14 13:49:16 +00:00
Commented Jan 14, 2011 at 13:49
1

Agreed. Part of that statement should be interpreted as 'refactor' into your 'new' project. That is, if you have indeed already committed on that drastic path. As mentioned by others, this is an extreme rarity that should almost never be done.

Dan McGrath
– Dan McGrath

2011-01-14 13:57:13 +00:00
Commented Jan 14, 2011 at 13:57
1

+1. Also, the rewrite will take time, during which maintenance will have to be done, but the same changes will need to be done on both code bases.

Larry Coleman
– Larry Coleman

2011-01-14 14:12:25 +00:00
Commented Jan 14, 2011 at 14:12

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 »