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

This is an ok answer, but not the direction I was looking for, because it spends too much time assessing a piece of sample code that was written just for simplicity (and not reflective of our real code in our product). But I am curious about one comment you made - "unreliable tools". What's an unreliable tool? What tools do you recommend?

koncurrency
– koncurrency

2012-05-25 18:07:31 +00:00
Commented May 25, 2012 at 18:07
6

@koncurrency: An unreliable tool is a thing like manual memory management or writing your own synchronization where in theory it solves a problem X but in reality is so bad that you can pretty much guarantee giant mistakes and the only way it could possibly solve the problem at hand on a reasonable scale is by the massive and disproportionate investment of developer time- which is what you have right now.

DeadMG
– DeadMG

2012-05-25 18:28:53 +00:00
Commented May 25, 2012 at 18:28

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 »