News for hackers. Stuff that matters.
Re:How should I behave as a developer in a project that's he... by TeMPOraL on Wednesday May 29, 2013 @11:47AM (#5786919)
It makes sense if you're absolutely, positively sure that the project is doomed and there's not a slightest hope for it.

But even assuming this, choice (b) is only local optimization. One could consider instead doing (c) - to try as hard as possible to convince the management to shut down that project ASAP, and thus saving the company many man-hours of wasted work. The global gain will be much greater then. Of course if management is stubborn and you're still sure the project will fail, then you're back to option (b).

Re:How should I behave as a developer in a project that's he... by klibertp on Wednesday May 29, 2013 @06:22PM (#5789604)
I just today talked with friends that work for Samsung and the amount of wasted everything they told me about was staggering. I don't think that there is anything such companies couldn't waste and forget about. This makes the management stubbornness all the more probable and makes trying to save "work-hours" pointless. That's pretty scary shit, but apparently that's how it works in such companies. I don't want to ever work in such an environment.
Re:How should I behave as a developer in a project that's he... by TeMPOraL on Wednesday May 29, 2013 @06:48PM (#5789746)
Yeah, I guess it depends on the size and make-up of the company. When I was writing that comment I was imagining a small/medium sized company, doing one or two big projects at the same time. If the company is so big that it can waste everything and still go forward by its inertia, then I guess leaving promptly is the right choice.