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

That's exactly what prompted the rewrite in which I participated. The code was so fragile, and the cost of adding new features so high, that not rewriting was no longer an option.

Frank Shearar
– Frank Shearar

2010-09-22 13:33:47 +00:00
Commented Sep 22, 2010 at 13:33
2

I like this response, funny and true. I would like to add "quantifiably" right before "less." So many times, it's easy to make the claim, but it's important to be able to quantify the wasted time.

Kevin Hsu
– Kevin Hsu

2012-08-09 00:42:44 +00:00
Commented Aug 9, 2012 at 0:42
Having old hardware happens a lot in industrial environments.

Nikko
– Nikko

2016-06-08 09:16:18 +00:00
Commented Jun 8, 2016 at 9:16
One must not forget the opportunity cost due to fewer updates while the rewrite is in progress.

Deduplicator
– Deduplicator

2018-02-03 10:04:54 +00:00
Commented Feb 3, 2018 at 10:04

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 »