3 ms·
Yet we know that people join these projects. Yourdon's “Death March" covers the topic. I haven't read it in a while, but according to http://wiki.c2.com/?DeathM
by eesmith 9y ago
Yet we know that people join these projects. Yourdon's “Death March" covers the topic. I haven't read it in a while, but according to http://wiki.c2.com/?DeathMarch http://wiki.c2.com/?DeathMarch the first chapter includes "what motivates developers to join them".
Looking around now, https://www.quora.com/What-is-it-like-to-work-on-a-death-march-software-project?share=1 https://www.quora.com/What-is-it-like-to-work-on-a-death-mar... summarizes what people do in these sorts of projects: "(a) follow all orders you are given, (b) avoid being given orders if you can (i.e. don't volunteer for more work), (c) always appear busy and productive, and (d) start doing side projects (and, possibly, looking for other jobs) to stay sane. A death march project can be a great time to build unrelated skills on the clock, because there tends to be a lot of downtime due to miscommunications. ... keep quiet, always appear busy, and focus on your own career vector."
This agrees with my understanding, which is why I don't think it's such a CV death knell as you suggest.