• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

Cont: Dear Users… (A thread for Sysadmin, Technical Support, and Help Desk people) Part 11

Them: "This file you sent me, the one that's named 'September 2023 Data', does it contain data from September or is it from August?"

Me: "I'll look into that and let you know".

I have no plans to reply any further.

Ever.

Did you at least look into the file to make sure that you put the September data in it and not the August data?
 
For once I have a little bit of sympathy for the questioner, I've worked with many a company that would label something September 2023 Data when it contained the data from August because the report comes out in September.
 
And it became apparent during our September board meeting that the financial reports for August we were supposed to be discussing were in some cases July’s numbers saved under a new name.
 
Did you at least look into the file to make sure that you put the September data in it and not the August data?

Every row of that spreadsheet has as its first column the date that data is for. It literally says it's September data 245,000+ times.
 
And it became apparent during our September board meeting that the financial reports for August we were supposed to be discussing were in some cases July’s numbers saved under a new name.

I don't make that kind of mistake: I delete old data before running new data, and I leave variables in stored queries commented out when I save them so I have to replace them before running it again. I am a very lazy monkey so I have long since minimized the amount of mental power I have to devote to routine tasks. I've made it so doing things wrong requires more effort than doing them correctly.
 
Ah so someone hadn't even bothered to open it before asking.

Even worse: I think they did, but didn't pay attention to anything inside it.


At a prior job I would on rare occasions, when I suspected people weren't using the files I sent them, "accidentally" send out blank files and see if anybody noticed. If they didn't respond "hey, this is empty" I knew it wasn't being used and I could stop. I don't do that at this job, it's much less of a Mickey Mouse operation generally so I feel I ought to do my best even if it's wasted sometimes.

But I still complain, hence my posts in this thread.
 
So Teams has suddenly decide it's my secretary and is automatically generated a task in my calendar anytime anyone asks me a question and I don't like this at all.

So if one of my coworkers just casually asks me if I've ever encounter this or that problem, suddenly I have a task "Have you ever encountered this problem?" that I have to mark complete.
 
So Teams has suddenly decide it's my secretary and is automatically generated a task in my calendar anytime anyone asks me a question and I don't like this at all.

So if one of my coworkers just casually asks me if I've ever encounter this or that problem, suddenly I have a task "Have you ever encountered this problem?" that I have to mark complete.

I remain against the death penalty in principle but occasionally principle has to bend to necessity.
 
So Teams has suddenly decide it's my secretary and is automatically generated a task in my calendar anytime anyone asks me a question and I don't like this at all.

So if one of my coworkers just casually asks me if I've ever encounter this or that problem, suddenly I have a task "Have you ever encountered this problem?" that I have to mark complete.

:jaw-dropp
 
So Teams has suddenly decide it's my secretary and is automatically generated a task in my calendar anytime anyone asks me a question and I don't like this at all.

So if one of my coworkers just casually asks me if I've ever encounter this or that problem, suddenly I have a task "Have you ever encountered this problem?" that I have to mark complete.

Find out who turned this feature on, and ask their manager lots of questions.
 
Every row of that spreadsheet has as its first column the date that data is for. It literally says it's September data 245,000+ times.

And you checked for a few lines that the dates were correct?

I’ve been in the computer industry for a long time and I’ve seen worse foul ups than this would require.
 
And you checked for a few lines that the dates were correct?

I’ve been in the computer industry for a long time and I’ve seen worse foul ups than this would require.

What is this, the contrarian thread? This wasn't a mistake that occurred that I missed spotting, this was a thing that was absolutely correct and an idiot didn't realize it. Yes, I check my results, and in this case it wasn't even dates: it was a date stamp reading "202309" to indicate the data was for that month. I literally inserted that value as part of the select statement. It was not possible for any row to lack it, it was not possible for any row to have any other value present.

I commend the ability of posters here to immediately doubt and contradict everything ever said by anybody but sheesh, save that **** for the Politics forum. This is a venting thread, not an "Aha! I think I can catch you out in a mistake!" thread. Particularly since it's just an anecdote for which nobody will ever hear any other side to the story, or see any evidence for anything. Christ!

And I have to say I'm a bit offended that the kneejerk reaction seems to be "TragicMonkey must be bad at his job".
 
I don’t think anything is aimed at you, Monkey. I think this is just weary grey-haired people reporting from the front. Personally I’m cynical and battle-scarred enough that I spend five minutes before every finance meeting manually adding up key columns and checking the comparatives against previous reports.
 
And I have to say I'm a bit offended that the kneejerk reaction seems to be "TragicMonkey must be bad at his job".
Oh believe me, I hear that a lot.

Uh, not about you. About my colleagues. And it's not because my colleagues are bad at their jobs, it's because the customers assume that their jobs are different from what they actually are.

We're customer service, not technicians. Callers shouldn't expect us to be technicians, because they are inevitably disappointed.
 
What is this, the contrarian thread? This wasn't a mistake that occurred that I missed spotting, this was a thing that was absolutely correct and an idiot didn't realize it.

Well that's fine but as you originally reported it, it looked like you were ripping into a coworker for not trusting the name of the file.

And I have to say I'm a bit offended that the kneejerk reaction seems to be "TragicMonkey must be bad at his job".

Well, if you didn't check the file, you would have been bad at your job. In fact, you do come across as being a bit arrogant. Somebody asked you a question and you decided you couldn't be bothered to answer them. That's quite poor.
 
Oh believe me, I hear that a lot.

Uh, not about you. About my colleagues. And it's not because my colleagues are bad at their jobs, it's because the customers assume that their jobs are different from what they actually are.

We're customer service, not technicians. Callers shouldn't expect us to be technicians, because they are inevitably disappointed.

Well we are customer service technicians and some of my coworkers inevitably disappoint, which does make them a bit bad at their jobs. Not every day can be your first day, week or year. At some point you've got to start catching on figuring things out for yourself and not needing your hand held. Sure you'll make mistakes but just learn from them is all we ask. Yet even that seems too much for some.
 

Back
Top Bottom