Imagine if this whole thread worked at the same place.
Yes, what a novel idea. It's even company policy that we use auto-reply. But this @$$clown still feels the need to broadcast it.Setup auto-reply in Outlook. that will let those who try to get ahold of you know you're not around and will leave everyone else the hell alone
Co-workers? I'm self-employed. My boss is a jerk.
Mark
Personally, I HATE using auto-reply. I make it a point to never talk about my vacations or travel plans on social media, etc. for the express purpose of not advertising when I'm not home. And then my job forces me to broadcast to every spammer that happens to hit my email address that I'm not in the office (so probably on vacation and not home).
Our company prides itself on being responsive to clients, so the auto-reply is as much, if not more, for people outside of the organization than it is inside. Anyone inside can look at our Skype app and see that I haven't been at my desk for 4 days.Why do you hate it so much? Outlook gives you the option of only auto-replying to folks within your organization. Also, you don't have to specify why you're out of the office. My standard out-of-office message is "Hello and thank you for your email. I am currently out of the office with limited email access. I will respond to your message as soon as I return [sometimes I'll list the return date]".
Boom, done. You could be at home sick on the couch or in the jungles of Belize. No one knows why you're gone but at least they know you're gone and aren't left hanging.
We had one of those at the office for a while. I had to avoid the lunchroom whenever he was in there. Made me nauseous.Lady at work is possibly the loudest eater in the history of humanity.
I mean sweet Jesus close you damn mouth when you eat.
Sounds like a nat geo special on primates across from me.
And before anyone even says anything no shes not black that was not a joke I was making. We descended from apes.
Also has the most irritatingly consistent morning yogurt ritual.
Queue spoon on plastic cup.
Schhh schhh schhh eat
Schhh schhh schhh eat
Lady at work is possibly the loudest eater in the history of humanity.
I mean sweet Jesus close you damn mouth when you eat.
Sounds like a nat geo special on primates across from me.
And before anyone even says anything no shes not black that was not a joke I was making. We descended from apes.
Also has the most irritatingly consistent morning yogurt ritual.
Queue spoon on plastic cup.
Schhh schhh schhh eat
Schhh schhh schhh eat
automatic transmissions get better gas mileage than those with standard transmissions
Does she eat salad at lunch every day and attack her plate of greens like they were trying to escape?
We had one of those at the office for a while. I had to avoid the lunchroom whenever he was in there. Made me nauseous.
Hah! just found this thread... I need this outlet.
I work for a small company - about 15 employees. We hired a new guy in January straight out of college. We had interviewed 2 applicants, liked the other one better, but she accepted another offer...
It became clear within his first week that he had misrepresented his qualifications at the interview, but the consensus was that he was fresh out of school, and to let him grow into the position. One of the first things that he told me on his first day was that he was "really, really smart", which I took as a sign of someone who is not actually so. We share an office, and he talks constantly, and when he isn't talking he is whistling. I've taken to wearing large headphones when I need peace and quiet.
He doesn't take direction well, and has tried to reinvent the wheel on a myriad of issues - forgetting (or ignoring) that everyone else at the office has years of successful experience at this. He regularly bites off more than he can chew, and projects and deadlines suffer for it. He refuses to work off the shared server, preferring to save his work locally, and putting it on the server when he is "done", despite repeated requests to not do so. He is nearly always the last one in, and first one out, claiming that he is working from home through the VPN, but anything that does happen from home usually requires major revision, or he has some story about software not working for him, etc. For various reasons, I have had the pleasure of working with him on most of his projects.
We had a summer intern, and several times she came to me saying that the new guy was trying to foist his work off on her. She also told me that he claimed, as a 75% deadline was coming up on a project she was working on, that he liked to be at 100% at the 75% deadline. My reply was "he doesn't know what it feels like to be at 100% at the 75% deadline". She hinted to me that she liked the work we were doing, but wouldn't accept an offer if she had to work with this guy.
He is also an expert on just about everything (just ask him). He spent a 2 hour car ride with me one time trying to convince me that vehicles with automatic transmissions get better gas mileage than those with standard transmissions (I drive a standard, he drives an automatic). Besides saying that I didn't believe that to be the case as he first mentioned it, I just let it go. He would not drop it, and had all sorts of reasons why he was right, including something about the computers in the standard vehicles activating the brakes automatically when the gears were shifted.
Unfortunately, we are super-busy, and relatively short staffed. We cannot afford to give him the boot at the moment.
/ Rant over
He refuses to work off the shared server, preferring to save his work locally, and putting it on the server when he is "done", despite repeated requests to not do so.
Holy hell... so today he took a bunch of work that he had been working on locally, and moved it back to the server... And, in the process, he overwrote one of the documents that I had been working on, which he had not been working on. The damn thing is about two weeks out of date now.
I swear, we work for the same place. (if the staff numbers weren't drastically different). We've had guys pull the "I prefer to work on my local machine" - for various reasons, including "I don't want to mess up, if I leave a copy on the server I can mess up the local copy, and always have a backup".Holy hell... so today he took a bunch of work that he had been working on locally, and moved it back to the server... And, in the process, he overwrote one of the documents that I had been working on, which he had not been working on. The damn thing is about two weeks out of date now.
There is actually a relatively easy solution to this - but it has to be implemented by the sender. Send the email to yourself in the To: field, and use a blind carbon copy (Bcc) for everyone else. On the recipient end, it only shows that the email was sent to them, and reply all will only go back to the original sender.My only peeves are co-workers who don't know the difference between reply and reply-all and co-workers who open their office doors (thankfully we have them and not cubicals) and then have loud phone conversations.
The former bugs me because there are a couple of co-workers who consistently do this even when the original email says to please not reply-all but instead reply directly to the sender. One of them is somewhat dense but the other just thinks the world must not be deprived of her input on any question.
To the latter, shut your freakin' door! I am trying to concentrate and I don't particularly care what you and your spouse are doing this weekend.
There is actually a relatively easy solution to this - but it has to be implemented by the sender. Send the email to yourself in the To: field, and use a blind carbon copy (Bcc) for everyone else. On the recipient end, it only shows that the email was sent to them, and reply all will only go back to the original sender.
And speakerphone abuse should be punishable by death.
Agree on the use of Bcc but that would involve reversing a lifetime of my co-worker's ingrained behavior.
There is actually a relatively easy solution to this - but it has to be implemented by the sender. Send the email to yourself in the To: field, and use a blind carbon copy (Bcc) for everyone else. On the recipient end, it only shows that the email was sent to them, and reply all will only go back to the original sender.
Holy hell... so today he took a bunch of work that he had been working on locally, and moved it back to the server... And, in the process, he overwrote one of the documents that I had been working on, which he had not been working on. The damn thing is about two weeks out of date now.
Ah yes, the infamous ID-ten-T error. Or the less common variant, PEBCAK.me, while troubleshooting a customer's email problem: it's not just our program, this says you have an error in Outlook too
customer: it doesn't say error
me: if this pops up, it indicates an error with the username or password on the email server
customer: but it doesn't say, "error"
me: ...
Send the email to yourself in the To: field, and use a blind carbon copy (Bcc) for everyone else. On the recipient end, it only shows that the email was sent to them, and reply all will only go back to the original sender.
I'm glad I don't work for you.I hate bcc. I've banned it for people who report to me. It's only ever used to squeal on people, or keep managers 'secretly' in the loop.
It's the cowards way out. If you're going to be a weasel, then be a weasel. Just do it so everyone knows you're a weasel.
I hate bcc. I've banned it for people who report to me. It's only ever used to squeal on people, or keep managers 'secretly' in the loop.
It's the cowards way out. If you're going to be a weasel, then be a weasel. Just do it so everyone knows you're a weasel.
I like stuff out in the open. I like transparency.
I don't like the idea of 'lurkers' listening to my conversation without my knowledge. If I'm communicating with someone, I like to know who is in on that conversation. It's no different than a lurker on a conference call. If you want to know what's going on, step up to the plate and make yourself known. If you have an issue, address it face to face.
I try not to say anything in an email that would get me into trouble, but stuff happens. I might say something stupid if I'm upset about a situation. I'd speak differently if I knew my boss's boss was listening in.
The weasel part comes in when people use bcc to tattle on their peers. They pull a senior person into some issue being discussed to get someone in trouble. Why not just say 'Hey - I'm ccing Joe on this thread'. It's less 'weasely'.
I'll occasionally use bcc to send myself a copy of an email thread so I can archive it, but that's about it.
When everyone gets evacuated for a fire drill, and when we're all making our way back into the building a bunch of them ignore paved pathways and trample the groundcover plants.
I mean, it's a minor thing, but would it kill you go to 20 feet out of the way?
Not to mention, with a public project, you have to make sure that you provide the same exact information to all bidders. Just sent an addendum to bidders, used BCC to send the email once and make sure it was the same for all of them.I only use bcc when I am emailing outside the company. I want my boss to know what I told them but I don't want them to try cutting me out of the loop and talking directly to my boss.
I also use bcc if I am sending a proposal to several contractors as I don't want them to know who else I am bidding with and I am just too lazy to send the same email 12 times.
Enter your email address to join: