| My favourite example is one team writing the internal compliance reports for some regulation that was repealed long ago, but the internal requirement persisted because… nobody cared enough to even check if it’s still needed or not. As a random example of this kind of thing: I saw a manager spend a month manually tallying up the disk usage on a fully virtualised storage array… VM by VM, volume by volume. Not realising that as a consequence of the layers abstractions, the resulting numbers will be totally meaningless. I.e.: an empty 2 TB volume might need only a couple of gigabytes on the array… or the full 2 TB if someone had accidentally “full” formatted it… except that deduplication was enabled across volumes, so… who knows!? The only number that mattered was the post-dedup allocated block count which the storage array conveniently provided on the status screen. At the time it was 1%, which translates to “don’t worry about it”. He worried about it. Spent weeks and weeks with Excel tallying up the total, getting nonsense, trying again, over and over. You see, two decades earlier, storage arrays didn’t dedup, VMware was not a thing, and there wasn’t a nice neat little percentage that they array itself could report. You had to tally up each volume in each server, it was the only way. So a policy was written that it’s someone’s job to go do this every six months or whatever. So this guy followed the policy. He tallied things up. Like a meat robot following the last instruction left by a deceased master. It was depressing to watch. |