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.

ugh, good move Robert. Anywhere that uses these type of dev metrics to judge devs is not a good place to be.

ozz
– ozz

2011-05-09 14:03:24 +00:00
Commented May 9, 2011 at 14:03
1

yeah, if you end up tracking any kind of metrics, someone will inevitably use them for evil.

Robert Greiner
– Robert Greiner

2011-05-09 14:14:25 +00:00
Commented May 9, 2011 at 14:14
I once read of a company that rewarded testers for bugs found, and developers for average time to fix bugs. You guessed it. Developers told testers what "bugs" to look for... once reported, they "fixed" them very quickly...

mattnz
– mattnz

2011-05-09 21:30:45 +00:00
Commented May 9, 2011 at 21:30
@mattnz yeah, usually when you have these bullcrap type metrics, the devs/testers always find a way to tilt things in their favor.

Robert Greiner
– Robert Greiner

2011-05-10 13:01:40 +00:00
Commented May 10, 2011 at 13:01

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 »