After he changed something I'd revised per his instructions back to my original copy I decided I'd had enough: I revised only where I thought it improved the papers and ignored the rest.
He never said a thing.
After he changed something I'd revised per his instructions back to my original copy I decided I'd had enough: I revised only where I thought it improved the papers and ignored the rest.
He never said a thing.
There are many stories of savvy workers engaging proactively including a flaw in their work being reviewed, something small but obvious and easy to fix, so that their managers can feel involved. One that often comes up in software is an apocryphal "duck" in an unreleased attack animation for the queen-unit in Interplay's Battle Chess game.
Closely related are the appearance of changes, such as a tale that Michelangelo was pressured to "fix" the nose of his David statue, so he climbed up and knocked off a little bit of material and the superior down below was satisfied without being able to verify anything had really changed.
It was exhausting and stupid and I stuck to blogging after that. Who knows, I might have written books. But not dealing with shit like that. I can torture myself much more efficiently, TYVM.