4 ms·
Yep, I used to be more productive WFH when I was already acclimated on a team. When I joined a new team and it turned fully remote, my productivity dropped and
by giantg2 4y ago
Yep, I used to be more productive WFH when I was already acclimated on a team. When I joined a new team and it turned fully remote, my productivity dropped and it took me longer to come up to speed than if I were in the office.
- cmrdporcupine 4y agoHonestly, I was on a team @ Google that was doing consumer hardware. It had problems before WFH started, but it got 5X worse once we got sent home. The whole situation was highly unproductive, a combination of bad politics, but also a degraded tech stack with a pile of technical debt and a build system that took forever to finish, and then because of Google's "no source code on your laptop" policies (which they stubbornly wouldn't loosen during COVID) an additional 10 minutes to copy the binary to local and then push to device, and poor debugging tool support so the round trip was agony to test and prototype. It was just awful. And managers seemed to have no idea how to make it work. So I decided to switch teams, to something that was friendlier for remote, more cloud-based backend stuff. A team that was doing daily standups. And it was sort of better. But acculturating into a new team while remote was painful. And the work unstimulating. And the depression and tedium from being stuck at home and dealing with kids in educational and emotional crisis too much. So I just quit. Walked away from a 10 year high paying "high status" job. And I'm not the only one, friends of mine did the same thing. I suspect much of the "great resignation" was driven by the frankly irresponsible way that employers just didn't manage remote well. I wasn't happy with $work before remote, but remote + a job with some bad aspects was like pouring naptha on a fire. Getting a new (remote) job now after a few months off. I think it will be better.
- giantg2 4y agoOur company handled remote fairly well. The overall team/work organization has been poor whether remote or in office. In our case, the resignations have been driven by the fact that people leaving the company can get 1.5-2x their current salary. We have had a lot of other team member move to new teams at the same company too (hopefully I'm one of them in the next couple weeks). Good luck at the new job!
- urthor 4y ago> no source code on your laptop Cybersecurity policies and work from home has always been extraordinarily strange to me. Optical character recognition exists. Big Corp, trust me, if I wanted to steal your stuff, I'd have it already. Stop locking my laptop down, we both know that's mostly a scare tactic.
- formercoder 4y agoThe definition of “on laptop” is pretty ambiguous also
- cmrdporcupine 4y agoIt's also almost entirely arbitrary since Google lets iOS and Android app developers work off laptop (there isn't much a choice with iOS because the toolchain won't run on a gLinux workstation anyways).
- giantg2 4y agoI think the main concern is theft of the laptop. They do trust you. They don't want someone to have your drive with proprietary source, even if the drive is encrypted.
- prepend 4y agoSounds like they should fix this with better laptop encryption. There’s many cheap methods to make source code on a stolen laptop useless. Using this as an excuse may mean that the org is stupid or lies to employees. Since this is Google, I think this just means that they don’t trust employees. And that’s a bad situation. If you can’t trust employees to not do bad things with the tools required for their jobs, then it’s going to result in unhappy and unproductive people. It’s like not giving carpenters nail guns because someone killed someone.
- giantg2 4y ago"Sounds like they should fix this with better laptop encryption." I'm not aware of any security experts that share this reasoning, if the information is truly sensitive and high value. "There’s many cheap methods to make source code on a stolen laptop useless." Such as?
- Frost1x 4y agoMy opinion is that the issue arises because of expectations and formalities that occur in remote environments over in person. When I'm remote, every email I type, message I send, Jira update, commit comment, etc. are etched in stone for reference in all of perpetuity, time stamped and all. There's an unspoken expectation to be informed and expert in all things in many work environnments to avoid looking "incompetent" (which is absurd, everyone is ignorant about some things). Remote work creates a hostile environment that makes this even worse. It makes people think about if they really want to email or call this person to ask about something because they worry that not being aware or not knowing about something may come off to others as being incompetent (people are aware that certain questions and statements can show your hand of expertise). So if I happened to be half paying attention during a meeting with a client or executive, if some change in an effort occurred I happened to miss or be too busy to see, or if I'm dealing with new tech I'm not quite familiar with... I have to tread lightly. In person, you meet people, you get body language, everyone is forced to speak on demand so competency and lack thereof become very clear in conversations. Expectations relax because if the head has no idea and no one else does and everyone has to reference it, well then, I'm not doing so bad. I'm not relying on looking at their cherry picked correspondence choices. Not only that, people are then more willing to communicate with people because they become more comfortable. They build relationships and they know it's OK to show their ignorance about some specific topic and that person is going to help them out a bit, mostly off the books. Not only that, communication in general becomes less formal. If I'm at the coffee machine and see Alice there and I had some question, I can just drop it in a friendly way. My intentions are more clear from body language, am I trying to assess her or am I really just trying to get the information I need to do my part. If it's trivial it's more natural just just say hey, I don't know how to do this thing, do you? Imagine sending that in an email or scheduling a conference call. This means for teams that have already built that level of trust are at an advantage in remote. They're comfortably sending those messages to one another. They've met the person and can gauge their personality. For juniors it's probably petrifying in some cases because they want to look more skilled and knowledgable than they are because they often don't have a general understanding of the level of expectations people have of them so they want to do better and often want to make an impression. The issue is that office culture often has a whole lot of competitive elements and people are more hesitant to communicate, it brings everything to a crawl. If work environments weren't always pressuring their labor force, people would be more willing to admit ignorance and or make informal communications necessary to speed things along in a more formal and recorded context, at least that's my opinion.