Pretty sensible advice for dealing with long hours over an extended period, but I was confused by the use of the term "death march" which in terms of software development is known as an anti-pattern:
I think the author of the article used it intentionally. The premise of the article is that sometimes developers find themselves having to or choosing to do a death march despite knowing it's unsustainable long-term, and there are ways to make the death march more productive and mitigate the negative effects.
http://en.wikipedia.org/wiki/Death_march_(project_management...