• Due to ongoing issues caused by Search, it has been temporarily disabled
  • Please excuse the mess, we're moving the furniture and restructuring the forum categories
  • You may need to edit your signatures.

    When we moved to Xenfora some of the signature options didn't come over. In the old software signatures were limited by a character limit, on Xenfora there are more options and there is a character number and number of lines limit. I've set maximum number of lines to 4 and unlimited characters.

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.
 
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.

This might be a manifestation of the "packer" vs "mapper" mentality. "Packers" take in bits and pieces of information, wrap them up in paper and tie them with a string, then put it on a shelf. They are unable to relate any information to anything else because all their information is finely segmented.

"Mappers" try to integrate new information with what they already know, continually expanding their knowledge base.

One site I read estimated 80% of the population was "packer," meaning it's difficult to teach them new things. For example, they can lean about mark/copy/paste in the context of a word processor, but if you have to show them how to do it in a web browser it's like they've never heard of it before.
 
This might be a manifestation of the "packer" vs "mapper" mentality. "Packers" take in bits and pieces of information, wrap them up in paper and tie them with a string, then put it on a shelf. They are unable to relate any information to anything else because all their information is finely segmented.

"Mappers" try to integrate new information with what they already know, continually expanding their knowledge base.

One site I read estimated 80% of the population was "packer," meaning it's difficult to teach them new things. For example, they can lean about mark/copy/paste in the context of a word processor, but if you have to show them how to do it in a web browser it's like they've never heard of it before.

Sounds about right, pick up insert tab A into slot B no problem when shown but can't extend it to figure out tab J into slot K on their own.

Heck, one guy is constantly writing in his notebook, but ask him 'can you go back to your notebook and review the information we went over last week?' and it's 'nope'. He says the writing stuff down helps him remember things. Well, if that were the case I wouldn't have to ask him to try to review it, he'd remember it. At least if he had it written down in some organized fashion he could review or reference it and wouldn't have to remember it. So a waste of ink and paper for all. Even more so if what he is constantly scribbling is his treatment for a 'Dumb and Dumber: Tres Hombres' movie'
 
"Mappers" try to integrate new information with what they already know, continually expanding their knowledge base.

The longer I live, the more I think everything's connected. I never throw away old work anymore, you never know when it'll come in handy for something. Just today I got an unusual request that required quite a lot of outside-the-box thinking that would have taken me days to figure out...if I hadn't actually done something very similar last spring. I was able to take my old code, make a couple of tweaks, and use it for this new purpose. Turned a multi-day job into two or three hours.
 
The longer I live, the more I think everything's connected. I never throw away old work anymore, you never know when it'll come in handy for something. Just today I got an unusual request that required quite a lot of outside-the-box thinking that would have taken me days to figure out...if I hadn't actually done something very similar last spring. I was able to take my old code, make a couple of tweaks, and use it for this new purpose. Turned a multi-day job into two or three hours.

For that very reason, JIRA and subversion (SVN) were integrated at my last workplace.

Every piece of code that I wrote was saved in SVN, and every JIRA that caused a piece of code to be written, is preserved in JIRA.

Within JIRA there is an SVN tab on every issue, clicking on that tab, shows you an SVN link to the stored code.

It was elegantly simple, all I had to do was include the JIRA ID (or IDs) in the comments, when checking in the code.

Finding things in JIRA was incredibly simple, the searching functionality (including JQuery) was very powerful. Similarly, in SVN using tools like Tortoise SVN...
 
We just got new guidelines on staff expectations and behaviour, and I noticed one new thing, which is that mobile phones are now no longer permitted at the desk, and must be stowed in drawers or bags.

With the growing reliance on MFA, I don't think this is practical, especially in my job where I have half a dozen different systems all requiring MFA, some of which time out periodically during the day and require renewal.

I get that management doesn't want people messing around with their phones while they're supposed to be working, but it is increasingly common for the phone to be part of the work.
 
We just got new guidelines on staff expectations and behaviour, and I noticed one new thing, which is that mobile phones are now no longer permitted at the desk, and must be stowed in drawers or bags.

With the growing reliance on MFA, I don't think this is practical, especially in my job where I have half a dozen different systems all requiring MFA, some of which time out periodically during the day and require renewal.

I get that management doesn't want people messing around with their phones while they're supposed to be working, but it is increasingly common for the phone to be part of the work.

Also why the heck should someone have to use their own personnel phone for work? Recently new workers have had to set up a MFA app on their own personal phones and it has yet to work well. We work in basically a giant Faraday cage so the only cell phone access is by the customer Wi-Fi which constantly needs reactivation and new ID and passwords. Which you can't get if you can't get onto the Wi-Fi to get into your E-mail to request and get a new guest Wi-Fi ID and PW.

You want me to use a cell phone for MFA, fine you provide the phone and then make sure I have cell access wherever I need to do my job and use MFA.
 
We just got new guidelines on staff expectations and behaviour, and I noticed one new thing, which is that mobile phones are now no longer permitted at the desk, and must be stowed in drawers or bags.

With the growing reliance on MFA, I don't think this is practical, especially in my job where I have half a dozen different systems all requiring MFA, some of which time out periodically during the day and require renewal.

I've gotten multiple trouble calls to that effect "So and so insurance site or hospital portal needs to send me a code to login, but I can't have my phone out at my desk."

The best I can tell them is that's an admin/HR problem, not a technical one.
 
I've gotten multiple trouble calls to that effect "So and so insurance site or hospital portal needs to send me a code to login, but I can't have my phone out at my desk."

The best I can tell them is that's an admin/HR problem, not a technical one.

I've been meaning to post a whine/rant about SMS messaging to landline phones (mostly they just disappear with no indication of a problem with delivery) but I can almost solve this one. I have Microsoft's PhoneLink installed on my android phone and my Win 10 computer. As long as they are in Bluetooth range I get a popup with e the text message on my desktop. So I can keep my phone in my desk (pant's pocket actually). ;)
 
In a prior (and dreadful) position I had to not only carry my own personal phone for work, but I also had to have a work cell phone, and when on-call there was a separate on-call phone! It felt ridiculous, walking around with three damn phones and sometimes being on more than one at a time.
 
In theory you don't need a smartphone to receive an SMS; an older feature phone should do the trick. Still, purchasing, deploying, and supporting 8.000 feature phones would be a big and probably expensive project.

Most MFA I've seen recently aren't SMS based, they just generate a time-limited one time password through an app. The cheapest alternative are the keychain token generators like these.
 
Because the government can't afford to buy new smartphones for all ~8,000 staff.

Plus you will find that most people don't want a second phone, even just for work purposes. Seen this time and time again, a company wanting staff to have work apps/data available on their phone but people want it on their personal phones. Personally, I would rather have a company supplied second phone BUT my views are out of step with most folk.
 
Most MFA I've seen recently aren't SMS based, they just generate a time-limited one time password through an app. The cheapest alternative are the keychain token generators like these.

Had one of these yesterday, for some reason had to relog into my Gmail email account on my iPad. For verification it wanted a code from the authenticator app, the authenticator app that popped up its notification with the number, note this is the authenticator app on the same device! Someone hasn't thought this through...
 
Last edited:
Plus you will find that most people don't want a second phone, even just for work purposes. Seen this time and time again, a company wanting staff to have work apps/data available on their phone but people want it on their personal phones. Personally, I would rather have a company supplied second phone BUT my views are out of step with most folk.
I insisted on a second, company-financed phone if they wanted me to work that way. Stuffed if they were going to have access to my personal handset for any reason.
 
Because the government can't afford to buy new smartphones for all ~8,000 staff.
Then perhaps the government should reconsider it's MFA requirements. Starting with liability if their chosen MFA app causes problems on an employee's device.
 
Last edited:
I cut the difference. I get a 50 buck a month cell phone stipend (which would be enough to get a second line / phone if I wanted) and I just use Google Voice to get a second virtual phone number. I can even set it so it goes automatically to voice mail when I'm off and not on call.
 
Back
Top Bottom