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

"Premature optimization is sometimes bad, but not when required for good user experience" then it's not premature optimization

Carlos Campderrós
– Carlos Campderrós

2011-06-22 14:38:44 +00:00
Commented Jun 22, 2011 at 14:38
1

Sometimes you have to start optimizing lots of stuff before you have metrics on the actual bottlenecks that require optimization, else the system comes out architected wrong for post-optimization that meets schedule and performance.

hotpaw2
– hotpaw2

2011-06-22 15:31:43 +00:00
Commented Jun 22, 2011 at 15:31

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 »