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

And to state the point explicitly: this exercise is driving home the point that for functions with ≥ O(n), you can try to throw more/faster hardware at the problem, but you get diminishing returns in performance. 10x the compute gets you <10x the performance.

Alexander
– Alexander

2024-12-15 20:15:09 +00:00
Commented Dec 15, 2024 at 20:15
Another lesson is that the bigger the problem size, the more important a smaller big-o becomes, also compared to a faster computer or micro-optimisation.

gnasher729
– gnasher729

2024-12-23 13:48:38 +00:00
Commented Dec 23, 2024 at 13:48

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 »