In-person has benefits in those situations, but whether or not it's better varies a lot based on the person and the office. I find it VERY distracting to have people talking around me. As such, I get a lot less done when in an office, because I can't concentrate as well. When you add in the other negative (commute time, in person interruptions, etc), going into an office for work can far outweigh any benefits of being around the people you work with.
I have a hard time grasping this one. Is it brainstorming ?
For things like pair programming or specification of a product, having separate screens and independent access to the same documents makes things a lot faster and efficient.
Same way meetings tend to go smoother all participants can access whatever data they need independently from the presenter, and move through the docs at their own pace.
Basically a mix of synchronous communication and access to all needed resources seems to me to perform better than IRL binding of two or more people looking at each other.
This is a part that probably varies a lot individually...I'm a slow thinker, and have a hard time reacting to fully formed ideas thrown at me thrown at me over a table. The other side coming with fully prepared for the discussion, while on the receiving end you need to do your homework realtime also doesn't help.
If it's random brainstorming it doesn't matter a lot. If it's an actually important topics, it feels like a DDOS on your brain when you actually want to take time to understand the implications. Then sure, some situations require speed, but I don't see that many of them in day to day life. "What you think about moving to X framework for our metrics ?" can probably wait for 30 min. and not be a realtime exchange.
> it's very uncomfortable to be on a zoom call for more than about 45 minutes at a time.
I've finding these meetings way more comfortable in remote...someone can be rambling for as long as they need, the effect on everyone's productivity is that much reduced. Same for people who speak very slowly actually, it's a lot less stress IMO and easier to engage when paradoxically you don't need to be 100% looking at them in the eyes.
That's the feature, not a bug. It gives the meeting initiator a better chance of steamrolling their way to approval.
Notice the difference between meetings where people share agendas and docs ahead of time vs those where you show up and they walk you through the doc.
* Remote work is better if the management has a common goal and everyone can swim towards it.
* In-person work is better if the management is adversarial or competitive with each other, or doesn't have a common goal to work towards.
In either case, it seems like the problem is management, not the work location. Am I wrong here?
EDIT: and so many of the challenges people are running into now are not new, either - companies were incentivized to make remote work work for two decades pre-Covid, and for a while pundits were all convinced that software jobs were all going away overseas as a result, but despite the salary savings the ROI just wasn't there for all but the most basic of work.
On the other hand, the projects that suffered the most were the ones where folks had less scope and autonomy. If you can't unilaterally make decisions for anything that spans more than a day, and you're forced into some ticket-oriented process where everyone has "their" task to do, communication naturally suffers. If you're all in the office, there's a bit more slack to talk quickly and informally outside your immediate silo; remotely, this takes more intentionality, so the friction imposed by your culture and process has an outsize effect.
So my conclusion has been, pretty much, the opposite: remote works better when people have real scope, independence and autonomy. If engineers and small teams can make decisions over longer time-frames, they'll have the space to adapt and work effectively. They might need somebody to set the example or foster the right habits, but it's fundamentally healthy and effective. The frictions with remote work come up when it's thrust against a less flexible culture that makes it harder for folks to adapt.
At 10+ person org sizes, most people can't have long-term scope and autonomy if the management don't know what it wants/needs, since they're just going to change their mind in a week or two. Once those decisions are made you can start delegating responsibility for execution.
The easy thing to do is to blame this all on poor management, but I think that's too pat. I think figuring out the best way to use a team of 20, 100, 1000 engineers to accomplish business goals is just an incredibly hard problem... and one that's often an ongoing, Sisyphean task, where high-bandwidth, low-latency communications are incredibly useful.
> I think figuring out the best way to use a team of 20, 100, 1000 engineers to accomplish business goals is just an incredibly hard problem...
Agreed, don't mean to downplay how difficult good management is. I think the key thing I've realized is that in a remote environment, bad management is so much more obvious and detrimental to the employee and organization. In office, if your manager doesn't communicate vision/objectives well you can always tap the shoulder of the guy next to you, or discretely pick your skip's brain in the break room. The rest of the organization can pick up the slack. But that's much harder remotely.
Remotely, I’m vastly more productive in getting coding work done. I’m sure most people would agree. But that productivity is almost erased by onboarding new hires. There are so many aspects of software engineering where it’s so much easier to be sitting next to someone, pointing at their monitor, and discussing what and why you are doing something. Instead, you need to hop on a call and awkwardly screen share on a call or write out paragraphs of text to impart the knowledge. In my experience, having such barriers to doing these things makes new hires much less likely to reach out and put themselves into the situations where they can learn, no matter how much they are told it’s ok to bother people.
To me, this is why remote works so much better at smaller companies with less bespoke tooling and legacy code. There’s no better way to learn than in person and there is a huge productivity boost when doing so. That said, personally, I’m willing to deal with the lower productivity in my work life to get the higher productivity in my real life by being able to do laundry during the day and not sit in traffic.
I think a decent middle-ground between "Document everything" and "Organically relay all information" is to just write "doc-stubs". Just a list of everything out there with no real content. It gives people a jumping off point to ask questions and lets them know what they don't know.
For example, incident handling has been lot more efficient for us with the team looking at different aspects and sharing on a call/huddle than what we often used to naturally do (involving a gaggle forming around 1 person's computer with different people offering suggestions of varying usefulness).
Demos and knowledge sharing I find also work better remote now than they used to in person now that people are used to the tooling.
I slightly prefer onboarding remote also, but that is because I'm the kind of person who gets distracted by wondering if I'm sitting too close or maybe I have not enough or too much deodorant etc.
The only thing that suffers remotely for me at this point is engagement. There's something about physically being with other people that makes their problems and desires seem more important to me, and I don't have any good hacks for giving more of a &"@$.
This feels like a tech choice issue to me. I'm constantly on calls with either slack/pop sharing where anyone can draw on the shared screen, or started coding session like in vscode where you can see each other's cursors. It... works the same for me as pointing at the screen. Just without it being awkward when it's more than 2 people getting to cram into a a small space.
For me, it's the exact opposite.
Before the pandemic, I always found the practice (and even the idea!) of "pairing" quite off-putting. You're standing behind someone, breathing in their body odor, awkwardly sweating next to each other, bending over if you want to type something... a really weird experience.
Remotely, none of those apply! You each get your own keyboard, your own screen, your own mouse. Both of you are 100% comfortable in your own environment. Using decent software helps as well, I recommend Tuple which makes sharing the mouse & keyboard seamless.
How do you feel about sitting next to someone at a bar?
Also some people wear too much deodorant.
I agree, none of this is an issue if working with clean, civilised people... a few feet away. It can quickly become uncomfortable if you're too close to each other.
I certainly don't agree at all. Home is where all the distractions are. Home is where i can drift off to make a cup of tea and end up spending an hour reading the newspaper without anyone noticing.
I think it would be useful to understand the distribution of peoples' feelings and experience about this. I have seen so many remote work enthusiasts just taking it as read that everyone prefers remote work because they do.
Or sharing a zoom session. Bonus is that I don’t have to commute to an office on another continent to engage in this second modality - more than half of my teammates are in other cities and I don’t see a benefit in the standing next to each other.
If you are talking about cost, then the only factor here is the market.
Can you please expand? I'm not understanding.
More likely is the "prestige HQ" which is deliberately made more expensive than it needs to be for status.
https://therealdeal.com/new-york/2023/06/05/jeff-blau-to-cla...
Not everyone is the same office - it’s a joke
I do security things, and it seems those folks are all gone from Twitter.
But my hypothesis is that the negatives won’t emerge for some time, at which point something bad happens and everyone will be standing around shaking their heads at how negligent it was.
Although more generally I do sympathize with the idea that most tech companies are at least a little bloated because money has so often been cheap & revenues always go up historically
I Twitter fails due to the mass layoffs it doesn't prove much either since it might be too hard to unwind a mess.
the problem is there is a ton of terrible leadership out there who want to rule by fiat, ignore their employees, and don't trust their employees (who they either directly or indirectly hired) to so their jobs.
What I found to be the best approach is one or two people already established a concept at what to make or at least the image of it, and the discussion can move to the details and implementation plan. And that doesn't need to be in person
This is exactly what I was getting at by referencing a benevolent dictatorship. When remote, it's just easier if one person is providing direction by fiat rather than trying to collect everyone's input and communally make a decision.
Yes, that's why before WHF, people really loved meetings and brainstorm sessions at work /s
In person during brainstorm discussion usually means endless time-wasting and bikeshedding.
true.
> For large companies like FAANG, I actually think they mostly fall in bucket 2
Also true most fall in the "figure it out" bucket... But here's where it gets funny: just meet in-person you say?
No, this is FAANG. You're in MTV, but the people you need to collaborate are in NYC, LAX, SEA, AUS, SFO...
So your in-person experience is you booking a room just for yourself so you can video conference all those people who also booked a room for themselves.
Because every other team is in same situation, finding a meeting room is a challenge in itself.
Take the call from your desk then?
No, this is FAANG, every building is open office layout, it'd be rude & disrespectful to your colleagues around who are busy coding.
But at the same time it's perfectly okay to just come up to your busy colleague and pester them about something, because collaboration.
I have this wild guess that if a significant number of companies cut their leases on all those monstrous office spaces that are kept being built all the time, it could hurt some people with important companies a fucking lot, and the ripple effect could prove to be immense and disastrous.
Spice must flow, and the fact that there are parties interested in those office spaces running and bringing money in has diddly to do with whether there are any actual productivity advantages of bringing the office workers back to the office or not.
For enough dough you can buy enough experts and pundits and other talking heads that will overflow the information space with thinkpieces and analyses that go either way.
Meanwhile, the only actual productivity boost is when you have a private office with a closable door within walking distance from your living place. But it’s not like anybody would give you _that,_ plebeian.
It's mind boggling to me. All I can think is that there is a lot of ego tied up in offices for some reason.
I personally prefer fully remote because I hate the distraction in the open office plan and associated pains like having to find meeting rooms, having to share restrooms with others (I admit this is just my personal pet peeve), and not being able to avoid distraction when I am in the zone for working. Most of all, I don't like the commute (I have to commute 1 hour each way, so everyday, I am spending 2 hours; when I worked from home, I started early and end up working an extra hour or two because I don't have to commute; these days, I try to arrive at 8-9am and leave by 5-6pm to beat the traffic and once I get home, I don't do any work). I consider quitting someday soon and am waiting for my wife to finish her residency and I will pull the trigger.
>No, this is FAANG, every building is open office layout, it'd be rude & disrespectful to your colleagues around who are busy coding.
Individual offices have not been the norm for everyone at large companies maybe ever? Cubicles are "better" but not that much better. (Source: I had one for years--both full-height and then shorter.) And the fact is that lots used to spend a lot more time on the phone than they generally need to today given other communication channels. When I've been in an office I absolutely make calls from my desk and everyone else does too.
I don't think this is really that common. I spent a decade in MTV on a wide variety of teams. I had VCs with people in different locations a handful of times and I never had one by myself. And getting deep focus with those people was so valuable that it was easier to just go to NYC, MUC, or SYD once a quarter than it was to jump on a call.
The downside is it’s hard to get actual coding down because of all the “collaboration”. So my ideal would be 1-2 days in office to meet and then 3-4 days to code ins peace at home.
Do you mind sharing the job title for something like this? Sounds like a dream job.
I created my own job, just with a startup. For a year I had two ostensibly full time jobs. By the end the startup wasn't doing much either and I considered going for three full time jobs.
My anecdotal evidence is different.
I've spent the last 2 years building a large, complex, and ambiguous system working almost exclusively remote, and half of it from another continent. For the first year I never met a colleague in person.
However, all this time I have been working closely with another engineer. Both of us are senior and very tenured, got good rapport and were highly aligned and motivated. We were able to execute efficiently, sometimes spending hours huddling in Slack per day.
So my feeling is that remote works in some scenarios and not others, particularly involving new or junior engineers.
Hard relate. Had my first internship WFH at Big Tech during the pandemic. I had expected work to be more on the lines of: there's always a lot of work to be done, and people will let you know about that. Instead it was the opposite, exactly as quoted above.
While it meant I had more freedom, I would have preferred if someone just doled out concrete tasks to me. I felt a bit lost. But then again, grass is greener on the other side.
> * In-person is much better if you don't know what you need to build, are trying to "figure it out as you go along", and are relying on the implicit fast feedback loop of standing next to each other.
This is why the other day I ranted about how my actual preference is in office but having a door that I can close. Realistically we shift between these two modes. In the first mode I need to reduce distractions and isolate myself. This is hard with slack and hard with an open office or cubicles. In person let's me even ignore slack as someone can knock on my door if it is urgent! But that's not all the time, so I open the door and communicate that it is collaboration and discussion phase.
I don't know why companies have become so allergic to doors. They are amazing and can let employees be in control of the chaos of work schedules. They'll know far better than anyone else if they're more productive that day/hour/minute in isolation or in collaboration. Micromanaging doesn't help, a door does.
Can you explain how some of the greatest technical research projects of our time like the internet, Linux, etc happened without a big office then?
It's clearly nonsense to suggest you have to be collaborating in-person to build big unknown things. There are thousands of examples throughout open source and more where that hasn't been the case, and millions of examples of projects from company offices that are awful.
The physical geography of the team is not an indicator of success.
while linux or git was created relatively sololy by a single person (at least at the beginning), i dont think you can call the internet a solo production.
(I don't know the history of git, maybe that too though.)
No, although there were certainly co-located or nearby individuals and teams that contributed specific chunks--certainly parts that were hardware or depended on hardware.
Stating that it’s possible is very different to stating which model might be more effective or faster.
Unfortunately we don’t have a parallel universe where torvalds lived on the same street as a bunch of other collaborators to compare
Indeed, searching for "Torvalds remote work" yields this: https://www.zdnet.com/article/pet-the-cat-own-the-bathrobe-l...
> Torvalds admits that when he started, "I worried about missing human interaction -- not just talking to people in the office and hallways, but going out to lunch etc. It turns out I never really missed it."
> "If you spend hours in online meetings from home, instead of spending hours in meetings at the office like you used to, you've just taken the worst part of office life, and brought it home, and made it even worse."
Some companies are able to add great new products over time, but I sense that it’s more common for companies to have one great play, after which they either die or merge with another to enjoy better economies of scale.
If you’re big enough and rich enough, you tend to burn a ton of money on internal research groups, but very little of what gets researched is ever a successful product. Doing this as a smaller organization is nearly impossible, which is why I think so many startups just exit rather than finding entirely new things to build.
For me, the extroverts that insist in socializing, gossiping and politicking in person make office work an unproductive nightmare.
OTOH, from personal experience working on-site hasn't really ever helped particularly well in that scenario (which I'mm all too familiar with.)
I used to work for Amzn and the management was totally idiotic about remote work. We had to go to the office to be on call for datacenters 1000kms from the office. Makes perfect sense right?
Beyond the practical scope of this point, we also find the need for mentoring (building a sustainable team).
I would say biggest benefits of in office is spontanious meet/discussion, assisting less senior coworkers etc. If I have a heavy day of work to plow through alone I avoid the office. If I need to sync or work on something with others in-person beats all the tools.
Remote Work is better if
1. You do not have home problems that you will end up focusing on when you are there - so if you are single and do not own your home, or you have a great relationship and you do own your home but there are no problems the remote work is probably better. But just like being in an office and going into a private room can help productivity if you have problems with home life going to office to work can help with productivity.
2. Remote work is much better if you are a person who is motivated by love of what you are doing and you actually love what you are doing, if you start to not love what you are doing but you have not left the company yet etc. there can be some slight loss of productivity, not because intentionally goofing off so much but because like #1 above working remotely makes it harder to get focused on something one does for money and not love if you are a love focused worker.
ok but I know from my own experience that #2 can be really different. And really I don't understand how anyone could doubt it - in the office if you are unmotivated you have a limited range of things you can do to pass the time. at home there is no limitation.
At some point in the office it becomes reasonable to just do the work and get it over with.
Not sure why this needs to be repeatedly brought up.. I mean it is called "home office" for a reason. If you don't have a real one, remote can suffer.. no surprise.
Not sure why you think a home office is going to solve marital problems or other issues that going into an office and being around other people might allow you to not focus on.
Aside from that then we can add inability to get a home office made to the list of things that can affect whether or not remote work is a good solution
Yes, even in "work office" that focus is not guaranteed, but even there martial problems or other issues will hit me. So yeah, still not sure why we need to bring this explicitly up again in discussion after discussion. You need a reasonable office to work, offices can suck - orthogonal to if home/remote/company.
> add inability to get a home office made to the list of things that can affect whether or not remote work is a good solution
Again, no-brainer, no home office no good solution? shrug
Probably because the reality of remote working was set by the pandemic, which forced a huge number of people to switch to remote work. Remote workers with a proper home office suddenly were, and I think continue to be, a minority.
I’m much more productive working from home; my only qualms are that team cohesion and sense of shared mission seems lower than it has at in-person jobs I’ve had. That may not even be causal.
Remote Work is better if
1. You prefer remote work
This always gets to be such a dogmatic discussion that will to someone claiming anyone who likes working in an office has no social life.
It’s just a preference. Remote work is not overall objectively better than office work (but you can create a set of goals for which this is true). Office work is not the right choice (but you can create a set of goals for which this is true).
There are jobs where in-person is just better, full stop. Remote can be accommodated, but it is not always exclusively about what the employee prefers.
Well yeah a surgeon should be working in person, you got me there.
If you want to work in an office go work in one. Join a co-working space or if there is sufficient momentum have everyone who wants an office join the same one in your area.
But don’t force it on everyone. Let people choose. That’s the thing I hate about these conversations is it should just be personal choice for the individual. Make async practices and communication better and re-tool the culture if need be, but remote first thinking benefits office workers too.
I think “let people choose” is the right idea at the “choose your job” or sometimes “choose your team” level.
Some of them are
- Async communication. Embracing long form writing is huge here, as is dropping the expectation of "now" in regards to getting responses.
- Holistic documentation & discussions. Processes, cultural values (and what they really mean and are expected to be followed specifically) and really just about anything meant to be repeated over and over should be documented at length, and reviewed consistently. This useful to everyone and has the added benefit of storing historical context and discussion
- Work in the open, whenever appropriate. If people can see whats going on, they can see things that traditionally are the "in between" things. Engineers already do this (PRs come to mind) in alot of ways, but this should extend to decision making as well, whenever reasonably possible. This facilitates the above points too.
- For socialization, its important that people have several avenues to get to know their co-workers. I think this one is possibly the least understand part of it, but its more than just "random lunch with co-workers if you join this channel!" there are ways to do remote team building exercises, to setup meaningful interactions between teams and departments etc. For instance, a positive thing I've seen people do with remote first around this is having product and engineering have Q&A with each other once every 2 weeks to just talk about stuff, it doesn't have to be related to what is going on right now. It can even be non work related if that is fitting to the people at the time, but it exists to just share things with each other, talk through ideas etc.
Unfortunately, these are things that aren't common in the work place currently. Most companies that have remote workers right now haven't moved beyond the "message eagerly or start a call" phase.
But if that's not the situation at the team/company level, you need to either figure out some compromise approach (like getting a co-working space or even just picking up some non-work social activities) or move on to an environment more in keeping with your preferences. At some point, if a situation just isn't to your liking, you should probably stop hitting your head against the wall.
Of course if your spouse also works from home, it's important to have a home with more than a single room. Not everybody has that luxury.
In my experience(i have worked from branch offices most my career) the differentiating factor is literacy, ie how comfortable/confident are the organization with recorded text vs private spoken word and the more the organization writes the more effective the remote staff will be.
And one of the side effect of a written culture is that a lot of the informal conventions/conversations become formal structure so the same level of top down planning can look very differently based on weather the culture for disseminating it is literate or oral.
I'm curious how often anyone actually finds this situation to happen and improve the feedback loop. I feel like it's more of an illusion of productivity then actual productivity because it's a pile of constant interruptions.
Like the given example with Meta doesn't seem like it would be better in-person, it sounds broken regardless.
Similarly, what career stage one is in? Young workers who are in 0-1, and to certain extent 1-10, remote really does not work.
The FAANG I work for now similarly has lots of 0-1, 1-10 type work (at least for my team), and a fully remote team. It works fine too.
The part about more junior employees is _more_ valid, though we had no problem on boarding juniors in either of those two situations.
Ultimately whether remote work is successful depends on whether the people doing the work have sufficient self-discipline to get the job done, and whether the hypothetical office alternative is set up for success. Most offices are not remotely set up for success, but optimize instead for middle management (toxin or cancer? [1]) being able to view their fifedoms.
[1]: https://www.talkfrom.com/video?name=leadership-without-manag...
She left there in 2011, after rising through the ranks to the level of division director.
They did almost all their business over email and Skype, because at the time, Skype was still the best voice/video conferencing software available without dedicated hardware.
If it was possible then for a small group of non-tech-focused people, it's certainly possible now, over a decade later and with an entire pandemic forcing the rapid improvement of all sorts of remote-work technology. That doesn't mean it's for everyone, but boldly stating that it's a "non-starter" is just unsupportable.
That just sounds like poor leadership to me. If you've got a holistic sense of what needs to be done, please share it with the people who need to be doing it.
That, or cut it up into concrete chunks and tell people to build that. But telling people to "figure it out" and then not sharing the overall vision, sounds incredibly dysfunctional to me.
People who have been in the industry and with a company for a long time largely have a network and don't really have problems connecting with people. (And at larger companies that network is often pretty distributed anyway.)
But the--admittedly not universal--consensus is that new folks struggle with onboarding and generally making progress in their careers. And even coming into an office doesn't really help if their managers and more senior co-workers are mostly not there. It's certainly hard for me to imagine graduating school and working remotely.
If you start raising future generations to be, you know, adults, instead of mentally stunting them into being eternal teens well into their 30s, and companies make an effort not to have a horrible onboarding and rely on 3 year tenures (and paradoxically do nothing to keep said employees that long), the problem is far less prevalent. Heck, most CS students are expected to do far more complex things at school without any assistance these days.
And with many travel budgets so squeezed at the moment (and COVID of course), you have teams with people who have never met anyone else on their team in-person in their whole multiyear tenure with the company. And to your point about short tenures, maybe they never will. If I'm honest, even though I've been around for ages, I'm less connected with co-workers than I've been in the past.
Once upon a time, it was considered the norm to find a job where you were, because you lived in a community that was part of your support system. Over the course of the last century, this norm eroded and was replaced with the norm of moving to wherever you got a job. More recently, the situation deteriorated even further, with the disappearance of the "job for life" assumptions that were prevalent in the mid-to-late 20th century, in favor of an expectation of changing jobs every 2-5 years—with a high chance every single time that you'd have to move.
One inevitable result of all this is the aforementioned splintering of local communities. Changing the employment norms so that a much higher percentage of people never need to move to work in person at a job would make it much easier to begin to restore local communities, and provide a much better chance of good socialization outside of work.
Now, there are caveats. This still relies on people not working too many hours, and while it would still help for the people who do work in person, and move in order to do so (those communities existing and being more prominent, and sustained by the people who stick around, makes it much easier for others to find them, too, even if they'll have to keep finding new ones every few years), it doesn't help them quite as much as the ones who can stay and grow their place in the community over many years.
I'm not gonna pretend that every project had 100% coverage and up-to-date documentation, but you should overcome fear of appearing weak/dumb and just ask a question, not even waiting for the next daily meetup. If culture is good enough, people are gonna realize it isn't you dumb, but docs and processes suck ass and will do something about it, maybe even asking you to participate. If not, just leave when the next offer lines up, I did that once when people straight up refused answering to my questions directly, and instead nagging that I didn't ask them properly.
Building up network is obviously more reliable when meeting in person, but it doesn't defeat the idea of getting to know each other through daily interactions, retros, 1-1s, whatever. And moreover if you appear professional and capable in eyes of colleagues by getting shit done, they're would want at least keep in touch
I restarted my software career doing remote work. I didn't have a problem finding things to do because my responsibilities were clear (read: I had a good manager) and I was self-taught so I already had a muscle for seeking knowledge on my own.
I suspect that remote work success is highly influenced by an equation involving how good your manager is and how much you innately know about what things your role is responsible for which can be propped up or replaced by seniority. I also suspect that new grads don't have muscles for finding/seeking internal and external information on their own, which feels powerless. There's ways to solve all these things without treating all of these folks the same.
Frankly, I think these are all the problems you and I relate to, but what's really solved for the business by returning to an office isn't productivity or happiness. It's a real estate problem.
I suspect the people on here who like to hate on managers either have a bad one or just don't realize how much crap they're being shielded from--a lot of which is inevitable in a large organization (where you can't tell everyone "hey figure it out on your own").
Some managers are given wide latitude in controlling their teams work. Some managers execute on that, others don't.
Some managers are given a lot of control over hiring. Some execute on that, other don't.
Some managers are given wide latitude over reviews. Some managers execute on that while others don't.
The reason managers are perceived to be less useful in tech usually, in my experience, boils down to where they spend their time and political capital. They either spend it on their team and enabling them or on themselves and enabling themselves. All of the above are ways that could go either way and the feeling is generally an accumulation of those decisions over time. I guess I could surmise that there's just a lot of "bad" managers in tech, but I don't think that's a useful sentiment without knowing why.
There is huge overhead to in person work and the benefits are wildly oversold.
IMHO a professional software developer in a company with good management/clear direction will thrive in a remote work scenario.
The only reason big corporations have a chance of pulling this off is the overall state of the economy. Once we see recovery their RTO antics will fail if the shift is not completely done.
* Remote work is much better if you know what you're building and "just" need to execute.
* In-person is much better if you don't know what you need to build, are trying to "figure it out as you go along", and are relying on the implicit fast feedback loop of standing next to each other.
Obvious, right? But I think what I've realize is the dimension of "we know what we need to do" is actually pretty much orthogonal to the product, size of the company, tenure of the employees, etc. I've been in early stage startups with no PMF that nonetheless have strong product-centric leadership who can set down an unambiguous vision for what they believe needs to be done. And I've been in startups that have PMF yet have no vision, and everyone is standing around in their remote offices twiddling their thumbs on "what to build next".
For large companies like FAANG, I actually think they mostly fall in bucket 2. I worked at Meta remotely for a year. My instructions when I joined were something like "Yeah so just talk to a bunch of people and look for opportunities to contribute". WTF? No wonder remote is not working well for them. You had to go 5-6 layers up the reporting chain to find anyone with any sort of holistic sense of what needed to be done, and they were not exactly empowered to share that vision lest it conflict with someone elses.
TL;DR I think remote work is well set up for companies with leadership that resembles a benevolent dictatorship. I think if you are all-remote and your leadership is effectively "managerial" in nature, NGMI.