I should obviously not get so caught up in reading that I miss my train stop, but I often do (or I get on the wrong train). Consider, for a programmer, the obv

I should obviously not get so caught up in reading that I miss my train stop, but I often do (or I get on the wrong train). Consider, for a programmer, the obviousness of not using hardcoded values. But we do all the time, as a placeholder while we finish a bigger picture thing. We fully intend to fix it later, but we don't, until it bites us in the ass. That's just one example. Most programmers I know do things they know they shouldn't do, all the time, because it gets them through that particular moment.