• 3 Posts
  • 723 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • “I’m at the grocery, back in 20”

    The policy around remote workers in my unionized heavy-privacy job is that when you’re away from the desk it’s fine; no one wanted to know your bathroom schedule when you were in the office, and no one wants to know now. Grabbing lunch, getting coffee, anything that can occur at the office without leaving, no one cares.

    For fire safety and especially for the “bad things happen while you’re by yourself” policy that started after someone fainted in a small windowless basement office long ago, when you’re actually stepping out you must announce the punch-out and punch-in after. It’s a pain, because they do watch and bitch, but meh:

    Meghan: grabbing lunch.  back in 10
    Dave:  yeah, me too
    Meghan:  back
    Roger:  Off to the doc
    Millie:  where's Dave?  
    Robert: do we gotta start the Wellness Check?
    Allison: nah, but I'll call him in a sec.  Policy.
    Dave:  wait.  I'm back.  Don't call the cops.
    Allison:  Dude.  
    Dave:  Sorry.  I'll pay the doughnut penalty
    Allison:  ha!  Okay, going for a walk while the sun's out
    Millie:  Enjoy! 
    Millie:  Grabbing the mail.  5 min
    Millie:  back
    Allison: back.  Beautiful out there.
    Roger:  back
    

    Etc. our ‘social’ channel is a lot of that shit. And yeah, the policy says an escalating wellness check after a reasonable time.

    Keep in mind, this is a Union job. It’s an IT job but the subject matter is heavy-privacy and heavy-policy. Think like a gov HMO or similar deal where we have a lot of accountability and massive protocols. The day before covid they were a “fuck no you’ll never work from home, come in if you have a patch run at 0500 Saturday, hippie” kind of place where they derived value from seeing your ass in a chair. On covid day one it was “run for the hills, go now, take what you can justify needing (keyboards, laptops, screens) and don’t come back onsite unless you have paperwork. Just fuck off, right now”, a complete about-face that’s now enshrined in the contract.

    In short, we did it; and if that group of dysfunctional stuffyshirt managers can cope with remote workers - some couldn’t, and like a reverse Dead Sea Effect, the worst of the bunch bailed and the good managers stayed - then I hold out hope that a lot of our sector of desk-and-screen workers can migrate en-masse home and stay there. They came a long way from where they were, and they hammered out a union-compatible workflow for remote work that actually makes sense. Maybe it’s a unicorn, and I hope it’s got legs, as we’re generally happier. And while union shit always has lower pay for the same work - sorry but true - the perks of choosing your environment makes it better.

    I will now accept questions.



  • have a group chat and never use DMs so people can see and chime in

    Can confirm - the group chat sucked, especially for us (2002 skype) when it was voice chat, so we often kept non-crucial stuff to the tail end of work hour too, so there was 45 min out of an hour for work before a burst of chatter. That’s supposed to have jibed with some kind of workflow pattern, and it worked … well enough.

    That, and you need some watercooler time. The current job has it only once a week, but we all come to meetings early and chat for 10 min while everyone else files in. Get some human time in.


  • So essentially you’re saying that communication falls apart and you don’t have the correct tools for remote work.

    I worked remotely starting in 2002, as I relocated from the NYC area shortly after 9/11 to get out of the region. My doc said “breathing issues in the tri-state area? World Trade Center Syndrome. Can you just move?” and I was done. I was on an H1B anyway, so I had no established ties. I was the youngest of a small group of remote coders, and they reallocated my time so that I worked on the same work as an existing remote team. Work was work.

    In 2002, our ‘correct tools’ was a pair of headphones and skype: we ran skype all day. It was on, it was connected in a conf call, but all mics were muted among the 7 of us who were in the work group. Have a question, you’d either type it out or just unmute, ask the group - yeah, nothing more granular - and discuss it, and then go back on mute.

    (I actually had a TV running in the office for background noise, as I couldn’t do the silence; and even the w98se sound system mixed it well enough to hide the background slush of the call)

    It worked well. The existing remotes had a good culture and allowed for a water cooler around a coffee time and lunch time so you could stay and be social, and everyone adapted to the equivalent of someone gophering periodically and chatting over the partition. The company had a strong policy against open pit environments, and they actually worried there’d be too many on the call, but the team was great.

    We were working on AT&T Fucking Unix. Tell me again how you didn’t have the tools when Skype and a 2002 USA broadband connection was the only thing we added to our workflow and we coded a secure OS for secure workloads. When I abandoned my visa/PR efforts and moved back home, I did it over a couple days off and had a rudimentary office ready to go in my home country immediately after.