What a surprise. Ted E. has just taken it upon himself to do exactly the thing we discussed as a team the other week and said we
weren't going to do because of technical issues. But sticking with the team decision meant he was actually going to have to not just do something, but actually look at what he was doing, so compared to that trauma you can see why he felt making yet another unplanned and unannounced change to our primary database was the better way to go.
Now he's complaining that the system is throwing up error messages.
1 comment:
But of course, it's not his fault, he was simply implementing a change that was discussed as a team!
It's amazing the lengths he will go to in order to avoid having to actually do something resembling work. If only that auditor had managed to properly nail him to the wall...
Post a Comment