News for hackers. Stuff that matters.
Re:Forced Coding by wheaties on Thursday October 08, 2009 @11:52AM (#869218)
"Why not? as nike say “just do it”, if the code has 10 bugs but is finished in half the time then you’ve done good, that gives you loads of time to fix the bugs, and more importantly you get to those moments where you realise x,y&z need to be changed much quicker. Not only that, but would you rather have a week to go and have a list of 80 bugs, or a week to go and 2 major deliverables a week overdue.."

What!? Has he never read Code Complete? I'd rather be 2 weeks overdue with no bugs than on time with 80 bugs. 80 bugs means I'm really overdue by a month...

Re:Forced Coding by avigesaa on Thursday October 08, 2009 @03:59PM (#869817)
Details, details. All middle-management cares about is whether or not the task is done. And the associated costs of your shitty code are, at least partially, shifted on to your co-workers. This gives you an even better comparative velocity! Bonus season will be good this year.
Re:Forced Coding by thwarted on Friday October 09, 2009 @05:07AM (#870914)
What's great about "done" is that there are so many interpretations of it.
Re:Forced Coding by cema on Thursday October 08, 2009 @03:42PM (#869783)
This is correct in developer's terms, but not necessarily in sales terms. Unless you manage yourself, you may get fired for choosing the first option (overdue with no bugs). Another good reason for working for yourself, I guess.