News for hackers. Stuff that matters.
Re:Developers blog post: No, I won’t do it. It would not be ... by btilly on Wednesday October 06, 2010 @12:47PM (#1764710)
Then the promise has been broken, you nag them about it, and the next time you use it as why you won't do it.

Never say, "You're lying" though. Instead say, "once burned, twice shy".

Re:Developers blog post: No, I won’t do it. It would not be ... by dedward on Wednesday October 06, 2010 @11:54PM (#1766784)
If you're a good politician, that may help you push the right buttons - but unless you can show concrete business damage because of the choices made, you are still likely on the nasty end of the stick. Nobody cares whether the developers are happy with the code - they care whether the code solves their problem or not.
Re:Developers blog post: No, I won’t do it. It would not be ... by ciupicri on Wednesday October 06, 2010 @02:35PM (#1765193)
What promise? The point was that the managers won't promise anything.
Re:Developers blog post: No, I won’t do it. It would not be ... by btilly on Wednesday October 06, 2010 @03:40PM (#1765528)
What promise? The point was that the managers won't promise anything.

The promise that you'd get time to do the fix. Which didn't happen. That was how I read:

> > we'll do the quick hack, but only if we're then allowed, in the very short term, to make the fix properly.

>What happens when you're not allowed to fix/improve/refactor the hack? Sometimes developers are assigned new tasks immediately.

Re:Developers blog post: No, I won’t do it. It would not be ... by Dylanlacey on Friday October 08, 2010 @02:36AM (#1770849)
"Sometimes"? That's like saying that SOMETIMES rain is wet.