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.

2

I can't conceive of doing this. If you don't fix bugs as you go along, how do you know that the new stuff you are adding isn't built on a foundation of quicksand? The more you layer on top of a system with known bugs, but deeper you'll have to dig to fix those bugs later. I guess it works for you, but it seems crazy to me.

Michael Kohne
– Michael Kohne

2011-05-15 22:59:04 +00:00
Commented May 15, 2011 at 22:59
While I respect the alternate viewpoint, choosing not to release a debugged feature seems a pretty rare hypothetical compared to needing to release a non-debugged feature. In other words, the reason features get dropped at final reviews is because they haven't had enough debugging time.

Karl Bielefeldt
– Karl Bielefeldt

2011-05-16 01:43:16 +00:00
Commented May 16, 2011 at 1:43

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 »