Edit - Academia 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

Thanks for your perspective. It's a little ironic, this coming up now, after we butted heads over almost this very topic a couple weeks ago. (FWIW, the conversation with the go-between was a big part of what I had in mind when I was arguing with you then.) I think you're right about letting it go. I skimmed the paper, and it's fine. Not very good, IMO, but nothing obviously wrong. They used an algorithm that I developed. The worst I can say about it is that they didn't cite the paper that inspired the algorithm, but the algorithm wasn't directly based on the other paper; it was more like ...
– Nobody
Commented Sep 15, 2021 at 18:55
1

... "That's an interesting approach, but I don't think it's quite right. Here's how I would do it instead."
– Nobody
Commented Sep 15, 2021 at 18:56

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**
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 »