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.

1

You could make this arguement for an isolated instance or two, but when do the 'bits' of time add up to too much?

JeffO
– JeffO

2011-09-29 19:13:14 +00:00
Commented Sep 29, 2011 at 19:13
From my own experience, it's actually the case for the vast majority of the projects. But I'd also guess that it comes with experience and is highly subjective :) I would be surprised if someone can give you an exact recipe (hence the 'fine line').

0x4B1D
– 0x4B1D

2011-09-29 19:26:02 +00:00
Commented Sep 29, 2011 at 19:26
@Jeff O: It is not going to be 'bits'. A 10% or 20% investment of development time in hardening is necessary because the system may outlast both the originally envisioned timeframe and your employment.

rwong
– rwong

2011-09-30 13:16:26 +00:00
Commented Sep 30, 2011 at 13:16

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 »