Comment by closeparen

I just had what should have been a one-hour task grow to consume most of my focus time for the week, due to hitting a perfect storm of internal platform bugs and getting caught in an edge case straddling the branches of a cloud migration.

Everything in software engineering is like this. You never know when you're going to stumble into a rat's nest of unexpected complexity. Should I be on the hook to pull 100 hours this week in order to maintain a normal pace on my tickets despite the snafu? Of course not, that's ridiculous. At the same time, there is no way for my skip to verify these types of stories across 100 reports.