It does not have to be this way. It doesn't, but it will be. :-) I worked on bug, almost full time, about a decade ago, for about a month. A single bug. I

It does not have to be this way. It doesn't, but it will be. :-) I worked on bug, almost full time, about a decade ago, for about a month. A single bug. I hadn't anticipated the bug, and didn't plan for it. I've seen teams spend months trying to hit perf targets. It's the type of thing that isn't uncommon in our industry. I'm not sure how you plan for it. What will it take for management to stop understaffing and overworking their employees? Many tmies its not understaffing. Again, I've seen teams struggle to hit perf targets. If you doubled the size of the team it wouldn't make their lives much easier. It may even make it worse. Our industry is one where you are fundamentally solving new problems (because if someone else solved it, you'd use their code). Now maybe you're saying we need to toss schedules altogether. Things are done when they're done -- and no crunch time. You do it with 40 hours/week for however long it takes. I'd love to see that dream happen to, but I honestly don't think it ever will.