News for hackers. Stuff that matters.
Re:Coding Horror: How to Motivate Programmers by edw519 on Saturday May 23, 2009 @02:07PM (#623668)
"Nothing motivates like having another programmer tell you they're rewriting your code because it sucks."

Wrong. This doesn't motivate. It just pisses me off.

Re:Coding Horror: How to Motivate Programmers by babo on Saturday May 23, 2009 @03:09PM (#623735)
What if there is an error or bottleneck which really counts? To say "it sucks" is rude and a very wrong way to tell but sometimes a fresh eye founds real things in code and it's a bad policy not to tell. Most of the people take it as piss off for sure but still...
Re:Coding Horror: How to Motivate Programmers by pm on Saturday May 23, 2009 @03:04PM (#623730)
Presumably, they should tell you you should rewrite your code because it sucks?
Re:Coding Horror: How to Motivate Programmers by edw519 on Saturday May 23, 2009 @04:33PM (#623801)
No.

Presumably:

1. My code doesn't suck (with rare exceptions). I know that. Why don't they?

2. What is the definition of "sucks"? Doesn't meet some other requirement that no one has agreed upon. Doesn't meet some other requirement that hasn't been identified? Has bugs? Runs slow? Is indented 2 spaces instead of 3?

3. Even if the code did suck, that doesn't automatically mean it should be rewritten.

4. Even if it should be rewritten, that doesn't mean he should do it.

5. They should learn better people skills. If they were looking for trouble, they found it.

Re:Coding Horror: How to Motivate Programmers by pm on Saturday May 23, 2009 @10:44PM (#624054)
Indeed, all salient points.