6 ms·
This is not a surprise to me. I think it also applies to some people who are senior and new on a project or team. Or people with a more synchronous working styl
by cmrdporcupine 4y ago
This is not a surprise to me. I think it also applies to some people who are senior and new on a project or team. Or people with a more synchronous working style. I think remote has been toxic to productivity in all sorts of companies and for all sorts of people. I think there's in general a "personality type" that does really well with remote in a certain kind of job and thrives with fairly asynchronous disconnected tasks, and on HN I think there's a bias towards seeing our whole industry that way.
But some of my best jobs were not like that. They were sitting down with people in very up close conversations and working out ambiguities and tasks. And mentoring juniors and working things through with them.
All that said, I won't be going back to in person. I'll be hunting for places that know how to make remote work, even though I don't prefer it. Because remote is still better than the 1.5 hours a day I was spending driving and the toll that was taking on my health and sanity. And most of the local employers are crappy.
So it's a real mix of stuff, we're in a transition period. It's going to take a few years for this stuff to shake out.
- giantg2 4y agoYep, 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.
- 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.
- PragmaticPulp 4y ago> I think there's in general a "personality type" that does really well with remote in a certain kind of job and thrives with fairly asynchronous disconnected tasks, and on HN I think there's a bias towards seeing our whole industry that way. Sites like HN are popular with people who prefer to socialize online and have chosen online communities to be a part of. Remote work is a natural extension of how they’ve built their online lives, which leads a lot of people to assume remote work is just natural for everyone. But it’s not. Like you said, there are a lot of personality types that do not do well at all when working remote. Discussing those people has become difficult in online spaces where people like remote work and resist any suggestion that it’s not good for everyone. This has done more harm than good to the cause, IMO, because a lot of companies and teams went head-first into remote assuming it’d be an easy win. Yet on a company-wide scale, it’s not. It requires work, and training, and mentoring, and more resources just to get back to baseline in many cases. Companies that have deluded themselves into thinking it would be easy are then caught off guard and disappointed, leading to sudden reversals of remote work policies or slow depreciation of remote teams. If we want remote to continue to grow, we need to shift the narrative away from “Its just better, period” to a more nuanced acknowledgement that it’s not for everyone and that it requires training and effort to unlock and maintain the benefits.
- cmrdporcupine 4y agoThe funny thing is that I got my "start" in programming doing things remote. Open source development, and in the 90s, IRC, MUDs/MOOs, etc. I have all sorts of collaborators and friends I've actually never met in person. And we were pretty productive. But that's not how $work went, when it went remote. All the open sores just festered and got worse. I know for a fact multiple projects delayed or faltered because of the remote move and the impact it had on productivity. And I'm sure it wasn't restricted to Google, but industry wide.
- civilized 4y agoI mostly agree with you, but we should remember that the shift to remote happened abruptly due to an unprecedented, immensely disruptive pandemic. This was not a controlled experiment where we can automatically attribute any issues that emerged after the shift to inherent flaws in remote work. That said, I think your experiences with the limitations of remote are valid and shouldn't be dismissed, although I personally am extremely committed to remote.
- ensignavenger 4y agoI wonder if it is really so much down to just personality, or if training, process changes, and better tools could largely ameliorate the differences? I have a hunch that as more work shifts remote, new ways of working will evolve.
- malfist 4y agoWhat a lot of people don't realize is offices are largely a by product of industrialization. Prior to that, most operations were either family ran and ran out of a home, or even when a company employed non-family members, they often paid piece work. So the employee would work from home, and then deliver their work to their employer and get paid per piece they produced. What's old will be new again.
- TigeriusKirk 4y agoWorking remote is a skill. It's not something you automatically know how to do, it's something you learn how to do. It takes time and effort as an individual, and more time and effort as an organization. If you don't put in that time and effort, you won't be good at it, like any other skill.
- tomtheelder 4y agoI do think a lot of it is driven by personality types, but I would attribute that more to personal need for close contact and socialization. I will never thrive in a remote environment- not because I can't manage focus or work asynchronously or anything, but because it makes me extremely depressed. It's impossible to keep my productivity up as my mental state degrades.
- cmrdporcupine 4y agoYeah it's very rough. Even having family in the house with me, I need outside socializing. Even when we were able to shift back to hybrid in-person, I'd drive in the 45 minutes get to the office and find basically nobody there. It was just as isolating, but totally pointless.
- ensignavenger 4y ago
- lettergram 4y agoI think anyone who can’t work well remote, on average, will not be your top performers anyway. What I mean by that — as a manager and one of the senior engineers, I had insight across our organization to projects and employee performance. Those who thrived being remote were those who already were the top performers. Those who were followers; who lacked discipline, failed faster and more obviously. Most software engineers produce more effort than they’re worth and skate by with meetings, “pair programming”, etc When the lockdowns started, my team at the time were some of the top performers. I had already had a remote team and we knew how to screen for it and manage it. Some things we employed - weekly syncs across team members, an always open video chat, daily stand ups amongst projects, fun days where we’d play games online, etc. The most effective thing we implemented was holding people accountable to their deliverables. People commit to their work and tell us when it’ll be done, if they fail we talk about it as a team. Team members quickly learn they must deliver and if they need help ask. We don’t delay timelines and I expected a clear “I think this will take days” if they need to delay, that’s fine, but they explain publicly and ask for help. That quickly led to discipline and we’d pair senior engineers with junior engineers to improve.
- holoduke 4y agoUtterly nonsense. How about children learning from home via a laptop? Doesn't work. Same for people who need to be trained in a new work environment. You want real interaction. You need to experience more than only sound and video in order to learn efficient. It's extremely wrong to think that good performers can always do these things from home. Not right.
- posed 4y agoI joined my company straight out of college and it was during covid peak, it was totally remote and guess what, last week my manager called me and told me that I've been promoted with a salary hike(within less than a year). If you've discipline and commitment you can make anything work. :)
- mgfist 4y ago
- xorbax 4y agoI think part of it is the 'junior' part. If you have a strong workflow and confidence with what you're doing then it's easier to be independent
- daniel-cussen 4y agoDriving is dangerous. It's no joke, you can get killed if you slip every time you go on a highway. Insanely dangerous. And more work than work itself, the commute is the worst part of people's days.
- cmrdporcupine 4y agoIt was destroying my health. But in my case it was honestly partially driven by personal choice to live rural rather than live in the town where our office was. But having made that choice at the start, 10 years in it started to become untenable. But now in theory, at least, I don't have to make that compromise.
- parksy 4y agoAs a senior developer, if working just in the office as was expected in the past I was distracted by things like a story about the weekend two colleagues are having in the background that sounds amusing, or the junior developer constantly spinning around on his chair to ask a question about something because "you're there". I always had time for that kind of thing but my productivity suffered and I was always frustrated by not getting enough done. Working from home wasn't all roses either even though I got more work done. I was already doing a balance of WFH as a contractor before covid and that was working well for me, but when covid restrictions happened and I was WFH months on end, I really started to feel the lack of human contact and socialisation. That story about the weekend was something I suddenly craved to hear. My mental state would suffer because I had no life other than sleep, screen, sleep, screen, and then my productivity would start to decline as a result of declining perspective. I think I need some social contact just to stay calibrated. Now I have a balance, a couple of days in the office, a couple of days at home, it works out well for me. I use the days in the office to catch up with the team, do any serious whiteboarding we need to do, and help out the juniors on the team with any questions they might have. I use my days at home to just crush out code with whatever music I want on in the background. As you say I think it will shake out. I know some say that people have forgotten the value of hard work and there is a push to get people back in the office full time, but I think having people in the environment that suits their productivity the best is the way forward (edit - and to circle back to the point - taking care of mental states is important to maintaining productivity).
- upupandup 4y ago> I really started to feel the lack of human contact and socialisation. Was work the only place you got this? I'm so glad I don't have these extended socializations and don't miss them the slightest. In my experience, they were all just useless banters and people trying to form hierarchies/comparisons/political interest groups. Any company that tries to move away from full WFH are holding themselves back. Given the option of working from home, most people will choose WFH. Maybe its different for a single person who doesnt have much human interaction outside of work. Even so I feel like those interactions don't necessarily degrade significantly via video chats. You cant smell them through the screen and that might be a good thing.
- upupandup 4y agoI just don't find this argument convincing. The tasks does not change because its remote, rather the costs have gone up to hire junior developers while costs to increase producitivity in existing devs have dropped significantly. Namely, github copilot, which removed a lot of "hey junior can you write a class to talk to this CRUD api" to "hey github generate snippets of boilerplate code that I can tweak to my exact needs" Lot of companies are realizing that their existing senior developers are now armed with this amazing tool and that its leading to faster turnarounds. The door appears to be closing for entry positions that used to take in high school drop outs, code bootcamp grads or single moms.
- anon2020dot00 4y agoI don't agree that copilot will hurt junior hiring; Co-pilot is just a tool that even juniors can use to make them productive even quicker. In fact, I think it will allow juniors to contribute faster and for high-school drop outs, code bootcamp grads or single moms to get hired more easily since instead of a steep learning curve, copilot allows them to quickly produce. I'd agree with the argument if there was no such thing as entropy and senior developers were a static resource that didn't depreciate but every company is going to need new blood just because the seniors are eventually going to retire or move to different companies for their own growth. The big appeal of juniors is usually low salary and willingness to work long hours and so juniors will often be attractive to companies.
- cactus2093 4y agoOne thing I haven't seen mentioned in this discussion recently is that on every single engineering team I've worked on in-person pre-pandemic, synchronous interruptions were a significant frustration. Remember how we all used to bemoan open concept offices? Every team developed some version of a rule around not coming up and tapping people on the shoulder, like setting an expectation to reach out over chat first or a headphone rule not to interrupt someone if their headphones were on. It's weird that this experience, which I know was very widespread in tech, is completely missing these days in discussions of remote vs in-office. People urging a return a to office are even explicitly bringing up the ability to come up and tap someone on the shoulder as a selling point of being in-office, ignoring the fact that most people have always hated this. As far as sitting down and working together collaboratively, I have found in the past 2 years that video calls work perfectly well for this. We've made an explicit effort to reduce the number of recurring, scheduled meetings but also to encourage more ad-hoc, collaborative meetings to work on things together synchronously. I think being an extrovert and missing the social aspect of working together in an office, is a perfectly legitimate reason to want to go back to an in-office job. In an ideal world I think every remote team should have an in-person off-site event for a couple of days every few months for purely social and team-building reasons. But I'm very skeptical about claims that you can't collaborate to get work done as well remotely because my own experience has been so different.