Protip don't expect connectivity on Bart, it's shit. That being said I have written emails, reviewed code, and pushed to prod from my phone, while underwater.
Meanwhile I would not be able to do this on a shuttle because I get carsick.
I get really car sick and nobody can behave with the bandwidth. So I just chill out and think deep thoughts. Mostly try to avoid the commute and WFH whenever I can.
There was some hypersensitivity to that back in 2013 but it faded. You get rated on achieving your quarterly objectives and nobody gives a crap if you need to WFH as long as you are getting things done. In my experience.
It wasn't eliminating per se but to weed out the low performers and slackers. As long as you're delivering and contributing it's a non issue. I'm a two hour commute from SNV and my manager volunteered saying I can WFH anytime I want but I prefer the people to people interaction.
I wasn't able to work at all for the first few months, but now I can write the code and review them for 100% of time. At least half of people in the shuttle work during our 2.5-4 hours of daily commute.
You would think they would put bigger pipes on those buses. Some of the Bay Area shuttle commutes are insane. Lots of lost productivity there. My limited experience on the Microsoft bus in Seattle is the same. Maybe a few Mbits download/upload at best. Just good enough for email and whatever development you can do locally without requiring remoting to your VM.
comments
Meanwhile I would not be able to do this on a shuttle because I get carsick.