One 60ish hour week on the Death March down, another now underway. Concentration, coordination, and attention to detail are dropping. Stupid-coding-error count rising.

Next time this kind of project starts coming down the pike, I really need to stop and think about it and offer some more constructive advice. We're doing a little better this time by keeping a list of tasks and desired due dates, but we really need duration estimates for each task, and some plan for corrective action when dates are missed.

It's hard to get others on board the project management bandwagon when they have never participated in a project that was under control, by which I mean doing the things just mentioned. Especially when the project's deadline is fixed and very high profile. But really, that's all the more reason to have the development process well documented and understood, as early as possible.

Less than halfway through development by the time that testing is supposed to be underway is no way to produce quality work.