I am the Fishmum. Nyn laughed at me a lot because of some French translation which rendered me the mother of the swimming pool. (It is good to see fish in chat.)
Didn't get as much transcription done as I'd hoped. This was mostly because I was still dealing with more helpdesk software shenanigans.
Did get to attend the training on some of the new various software coming down the pitch. This stuff does not fill me with the same apprehension and mild horror that the helpdesk software did.
I have three recommendations for the helpdesk software:
1) Do whatever is necessary to create a user notification for when a ticket is initially filed, even though ticket numbers are not assigned until the ticket is triaged into Issue or Request. Having the ticket number in the thingy is a bonus, not a strict user requirement, and having a receipt that it's been filed (and a copy of the text that's been filed) is still very useful.
2) Do whatever is necessary to allow the user to optionally mark a ticket as public and searchable. Because some things, like "printer is broken", "dishwasher is broken", "my user account is broken in the following hilarious ways", and "the spiders from building B seem to have followed me back to building D, and I'm not sure I like this" -- these are not things that necessarily need to remain private from your co-workers. "That tech support guy from last week was an utter shitlord and upon reflection I find I still don't want to talk to him ever again" is an example of a ticket which should remain private, and that general helpdesk staff shouldn't even be triaging.
3) The company-branded front end which y'all slapped all over this bad mofo? THAT NEEDS TO GO. The vendor's original interface has more useful information, and breaks less badly on weird screen sizes. Due to the usability issues, I see the interface through a red veil of hatred. Our company's brand images are all over that mofo. I'm viewing our company's brand images with seething resentment. I don't think you wanted me to do that.
If they changed those things, I think it would be not bad.
Purple was back in the office, more chipper than the last week or so. This is good. I don't like to see him all owwy and cranky. He finished up his stuff early-ish tonight, and popped by my cube to say goodnight (and see if I was done). The hilarity that ensued (after we reached the parking lot, where we were not run over by the white panel van) included my explanation that in fact sometimes my cleavage icon came out to play for general technical ranting. Also, Purple does not wax his chest, and the rant about a corner case bug in $PRODUCT is sort of hilarious when given while wearing an "I <3 my $PRODUCT" shirt. Which does not display cleavage.
I hope all is well with Grandmanager's dog, as he was spotted leaving work at high speed while on the phone using phrases that are often associated with dog problems.
Nora has opinions about the job market. If you're in the DC area and need a trained professional who knows how to wrangle volunteers via the internet and any other communications method you can get your hands on, and would like to overthrow capitalism in favor of worker-supported, worker-supporting sorts of work, let her know. She is awesome, and, uh, viva something.
Minions' lunch is tomorrow, and then Friday is the goodbye lunch for a teammate. I'm going to try to be awake for those things. Wish me luck.
Didn't get as much transcription done as I'd hoped. This was mostly because I was still dealing with more helpdesk software shenanigans.
Did get to attend the training on some of the new various software coming down the pitch. This stuff does not fill me with the same apprehension and mild horror that the helpdesk software did.
I have three recommendations for the helpdesk software:
1) Do whatever is necessary to create a user notification for when a ticket is initially filed, even though ticket numbers are not assigned until the ticket is triaged into Issue or Request. Having the ticket number in the thingy is a bonus, not a strict user requirement, and having a receipt that it's been filed (and a copy of the text that's been filed) is still very useful.
2) Do whatever is necessary to allow the user to optionally mark a ticket as public and searchable. Because some things, like "printer is broken", "dishwasher is broken", "my user account is broken in the following hilarious ways", and "the spiders from building B seem to have followed me back to building D, and I'm not sure I like this" -- these are not things that necessarily need to remain private from your co-workers. "That tech support guy from last week was an utter shitlord and upon reflection I find I still don't want to talk to him ever again" is an example of a ticket which should remain private, and that general helpdesk staff shouldn't even be triaging.
3) The company-branded front end which y'all slapped all over this bad mofo? THAT NEEDS TO GO. The vendor's original interface has more useful information, and breaks less badly on weird screen sizes. Due to the usability issues, I see the interface through a red veil of hatred. Our company's brand images are all over that mofo. I'm viewing our company's brand images with seething resentment. I don't think you wanted me to do that.
If they changed those things, I think it would be not bad.
Purple was back in the office, more chipper than the last week or so. This is good. I don't like to see him all owwy and cranky. He finished up his stuff early-ish tonight, and popped by my cube to say goodnight (and see if I was done). The hilarity that ensued (after we reached the parking lot, where we were not run over by the white panel van) included my explanation that in fact sometimes my cleavage icon came out to play for general technical ranting. Also, Purple does not wax his chest, and the rant about a corner case bug in $PRODUCT is sort of hilarious when given while wearing an "I <3 my $PRODUCT" shirt. Which does not display cleavage.
I hope all is well with Grandmanager's dog, as he was spotted leaving work at high speed while on the phone using phrases that are often associated with dog problems.
Nora has opinions about the job market. If you're in the DC area and need a trained professional who knows how to wrangle volunteers via the internet and any other communications method you can get your hands on, and would like to overthrow capitalism in favor of worker-supported, worker-supporting sorts of work, let her know. She is awesome, and, uh, viva something.
Minions' lunch is tomorrow, and then Friday is the goodbye lunch for a teammate. I'm going to try to be awake for those things. Wish me luck.