Let's say there's a public IP change or two (which breaks dst-NAT yeah yeah, NAT is the devil, but fuck you, not everyone has IPv6 resources handy), removals of antiquated VLANs, or consolidation of multiple gateways onto one router (which would involve firewall consolidation and cleanup). To me, read receipts should only be used when there's a major change coming up, and you need to make sure that everyone that is affected has at least seen the email.Įxample time: I'm the network admin that has been tasked with making numerous drastic changes to the network for reasons beyond my paygrade. We should have an expectation that we know what needs to be done with any change.īut I think there's also a place for them, if used appropriately. Okay yeah, I can see why you're annoyed about getting read receipts as a sysadmin. I have 11 read receipts showing a series of emails I sent to him reached his inbox and were read." "The project failed because Person X failed to respond. That's their job.so I can see this as one of their tools. PMs who are on top of things can easily flip back in their notes and read back your exact utterance word for word in Status Meeting 39, at 4:32:18 PM. In that kind of environment I can see why read receipts might be one of their get out of jail free tools, regardless of reliability. The only thing they can do is nag their resources for status updates, beg their resources' bosses to get them to work on their tasks and escalate escalate escalate. If it fails it falls directly on them and they have zero ability to do anything about the outcome themselves. PMs are basically secretaries that are also 100% responsible for the project. I'm not a fan, but I can see why they do it. Working in a product development environment, I tend to see read receipts as the domain of the project manager or the micromanager who feels they need "evidence." Just stop, you're not that important, and the world does not revolve around you. So I expect an action" That's about the only outcome from a read receipt. "Now I know that you read my email, and you know that I know. I also would like to reserve the right to tell you that I didn't read your email yet, when you will most likely ask me the next time you see me.Īsking for a read receipt is like sending me a letter in the mail, and then showing up at my door to ask me if I read it, if that ever happened, you will be kicked out of my property. I will get back to you when I get back to you, if I feel the need to. The fact that I clicked on your email does not mean that I read it, processed its content, and formulated a proper response in order to reply, it is false to assume that everyone processes emails the same. ![]() If your ever send me an email with a read receipt, I am always answering NO on the matter of principle. Rant alert: sysadmin being asked for read receipts
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |