3 ms·
> Another theory: that for some people, hitting a problem is an excuse to stop working entirely and claim to be waiting on another team for support. Agree, but
by ok_dad 4y ago
> Another theory: that for some people, hitting a problem is an excuse to stop working entirely and claim to be waiting on another team for support.
Agree, but sometimes it isn't even the user's fault and they do things like this out of desperation or frustration.
Imagine working in a place where nothing works right, you always have to search through shit documentation to find tiny nuggets of wisdom, and everyone is always pushing to get more done in less time. Then, if you sense a chance to have a short break by throwing something over the wall to another team, you might also choose to do that rather than work even harder to try and find some missing answers for the questions you seek.
- _puk 4y agoDon't forget actually putting the work in to understand an issue, and then becoming the go to person for all problems related to X as there's no chance support will solve it in any reasonable timeframe.
- ok_dad 4y agoYup, the old "hey, X fixed it once, they can do it again" combined with "fixing this permanently will cost too much time" resulting in "X" having to repeatedly tape together the paper airplane carrying the load of a 747.