PiedPipetter

Luckily my boss and colleagues all recognize Teams limitations on the idle status and we just get our work done. I’m not going to attempt to game it - but then I work when I say I’m working and the job gets done, so management isn’t breathing down our necks about idle status.

As a fed, anything plugged into a port is automatically logged and checked, and can result in a nastygram or more serious infraction. We periodically get emails about inappropriate connections - we can’t even use the USB to charge our work phones.

Then came the email that told us they knew about X instances of mouse jigglers and told us to cut it out. I wonder if managers got notified.

The problem with Team is it goes yellow when IT’S idle, not you. That was a big adjustment when we went to Teams, understanding that someone can be furiously working away at their computer while Teams is reporting yellow. You send them a message and BAM it goes green when they see the notification and read your message. Pretty ridiculous, really, since the bulk of the software is all Microsoft…why can’t Outlook tell Teams, “Hey, she’s writing an email, the icon says green, silly.”

I wrote code for industrial automation years ago (think assembly line machines). I was reviewing production code and found a stupid bug and fixed it, then reinstalled. The motors moved incorrectly - I don’t recall if that was the time it smashed glass everywhere, but “fixing” the code definitely broke the program. I could not figure out why…but due to time constraints I sadly had reinsert the bug to put the machine back in production.

Some nights that still bothers me.

I was confused by “instance instances” in the first starred note.