If your work can be done in isolation and doesn't require a team to deal with any uncertainty, then by all means work fully remote. However, if your work is about innovation and collaboration, then it's going to be more effective to spend time together.
I think it's telling that you talk about 'looking at a clock'. If that's how you spend your office time, then indeed there might be something off. E.g. a controlling manager who wants their minions to be visible and on the clock.
Personally I work one or two days from home. Some team members more, a few even fully remote (but it's noticable that they are more task oriented and less included in any new concepts/roadmaps/designs/etc). The majority of the people spend the same one or two days together in the office where all kinds of formal and informal interactions happen that further the collaborative creative process.
Just have optional office hours, Slack huddles and mob sessions every few days.
Some of my engineers…
- have a open huddle for a few hours a day where anyone can drop into their project while they work
- others make use of our scheduled themed mob sessions (ie. Maintenance Mondays, deployment Thursdays). have a problem, idea or just want to hangout then come by?
- ICs & seniors are required to host at least a weekly office hour to assist juniors or teach something of their choice.
The default doesn’t always have to be return to office for a physical meet.
There’s lots of other options.
When I was a junior engineer working in-person, I was learning from senior engineers multiple times a day, not just once a week.
Also, I've run a remote work company over the pandemic. Maybe you don't feel working remotely is different, but many, many people feel more comfortable approaching someone in person vs. online. In person, you can look at someone, see if they're busy, and, if not, approach to start a conversation. Online, you can never tell if someone is available. There is always an element of rejection when it comes to approaching someone online.
That's kind of the point though. When you're together, you don't need to think about how to include others in the discussion or talk to your manager. It all happens organically.
> I’m sorry, I just don’t find that your feelings about online rejections is a good enough reason to drive into an office.
Again, this is not my personal feeling. I ran a video conferencing company that served hundreds of thousands of people over the pandemic. I'm telling you the feedback we got from our users. So, you might not be willing to drive to an office for my feelings. But if you're not willing to drive to an office for the majority of your team's feelings, you might just be an asshole?
If your primary reason for wanting to be in office is fly on the wall lurking and not wanting to feel rejected then those aren't very good reasons. Ask to be apart of solutions, groups, teams, emergency responses and projects. You'll learn 10x as much working with those co-workers to solve the problem than you would by listening to some coworkers doing it.
> So, you might not be willing to drive to an office for my feelings. But if you're not willing to drive to an office for the majority of your team's feelings, you might just be an asshole?
I work in a group of 10 developers and 0 out of 10 want to be in office, but hey, I don't mind if you want to take shots at me. I'm not against working in an office, I just want to have real reasons why it's needed.
This is the bad part -- the best stuff to learn from has been filtered out. Text is written with a specific audience in mind, and that audience generally isn't students. You can write a second document sure, but that requires dedicated tome to writing a second document, and even then, the author may not know which details are most important for the student to know
Or
Can we chat about a problem I’m having with the dev server?
Or
When do you think you’ll have free time?
Those questions are all direct and to the point. They didn’t start out with “hey, see the raiders game last night, it was crazy. My dog was so excited from all the yelling she jumped on the table and started eating the chips.”
To be clear. We were talking about reaching out to coworkers.
Also many, many people feel more comfortable approaching someone online vs. in person.
Seeing your arguments here, I'll guess that you're just more social than many people. When I was a junior, a long time ago, I learned most things by trying and studying on my own. I always learned very little from senior engineers directly. I would do a lot better by having them tell me what to look at and exploring stuff alone.
I'm not, at all. In fact, I'm very introverted. I think you're missing a number of nuances to this argument.
It's very true that some people are more comfortable approaching people online vs. in person, but that's actually an argument for in-person work. When you're in-person, you can get insight into your team and learn new things just by being around conversations. You don't need to actively participate in any way. Even if you're more comfortable approaching people online, it's still more overhead to approach people online than it is to sit at your desk literally doing nothing.
Second, saying "many, many people feel more comfortable approaching someone online vs. in person" isn't a good argument for two reasons:
1. What you're comfortable with isn't likely to be what's best overall. It's very often that you need to grow your comfort zone to grow as a person. For instance, it can feel very uncomfortable the first time you play a sport or do a hobby in front of others. It definitely feels more comfortable to stay at home. But you'll never get better that way.
2. Apparently, extroverts outnumber introverts by a large margin, so if you had to pick one method of work and apply it to the general population, then it would make sense to pick a method that favors extroverts. I'm not saying in-person working favors extroverts. I think the opposite, actually, because socializing online is harder so only those with a high social drive will actually do it. But I'm just pointing out a logical issue with that statement.
Those are distractions. Those conversations, for the most part, bring no insight and destroy my productivity. As I said, that's not how I learn. You are applying your personal perspective unto others, but what you are describing is alien to me. I learn by experimenting and exploring on my own.
It's the reason why during most of my professional life I had to drown outside noise with headphones.
> It's very often that you need to grow your comfort zone to grow as a person. For instance, it can feel very uncomfortable the first time you play a sport or do a hobby in front of others. It definitely feels more comfortable to stay at home. But you'll never get better that way.
And I got out of my comfort zone many times. Taking on projects that didn't perfectly suited my skills and having to learn new things on the run. Switching roles and finding myself having to take on responsibilities without any proper training or hand over, etc and so forth.
Having my energy and focus drained by navigating meaningless social interaction has nothing to do with "getting out of my comfort zone", but everything to do with being able to maintain the focus I need to be actually productive.
> Apparently, extroverts outnumber introverts by a large margin
I have no idea, and honestly I'm not so sure. I certainly don't think they are the majority in Software Development.
> because socializing online is harder so only those with a high social drive will actually do it. But I'm just pointing out a logical issue with that statement.
I don't need work to socialize, when I have the need for socialization. Just make friends outside of work. Find a hobby. There's plenty of people out there.
This is why I always ask my coworkers to contact me via “open” channels instead of DMs, preferably async ones like PRs (which can start w/o any code or as very rough drafts). At a well run remote company visibility like this should be even easier than having to happen to be in the right place at the right time.
Because at the same time, ICs working on critical projects shouldn’t be forced to stop every 15 minutes to answer “It’s not working” questions.
It's a matter of discipline not much of physical presence.
The article also has no data supporting it. Only feelings. It's very typical for these sort of articles.
I am a lot more productive, and even creative working from home, where I have full control of the environment I'm in and not wasting effort on social interactions. Collaboration happens effectively in a remote settings as long as the company embraces it properly.
Since we are discussing feelings about remote work, this is as valid as anything else.
My company disbanded its employee productivity research group after they started providing data to the contrary. It's not about facts, it's about forcing the peons to fall in line.
I've had many face to face conversations in a room with a whiteboard that couldn't have happened nearly as efficiently if everyone was remote.
Now I do think that the push against work from home in general has very little to do with operating efficiency (if companies cared that much about operating efficiency they wouldn't have developers working in loud open plan offices, drowning out the world around them with headphones), but the argument that there's no utility in face to face meetings is just as meritless.
When the claim is that remote work is a mistake and that its era came to an end... Yes. It's an exceptional claim, and exceptional claims demand exceptional data. Otherwise we should call it bullshit.
> but the argument that there's no utility in face to face meetings is just as meritless.
Probably. I do prefer remote work, and I favor working for companies that allow me to stay remote.
But I think there's place to companies that prefer to work in office, and people that prefer to work in the same physical space as their colleagues.
This balanced take doesn't seem to be very popular, however. I wonder why.
That is not a balanced take. In fact, it's pretty extreme.
Plenty of companies are 0% remote, plenty of companies are 100%, and plenty others are somewhere in between.
His take that 100% remote is over is bizarre and somewhat confrontational, without any data to back it up. It's plain bullshit.
I could see a nimble startup pivoting in a way that can make it work. I can also a see large businesses investing in overseas at scale. I don't see smaller or mid-size companies able to reap the same kind of benefits as easily, unless they were setup with it in mind from the start.
What’s the data to support this statement? It sounds like a feeling. Do you have data to support whether or not your teammates’ productivity are affected by you being remote?
Please, I've worked on plenty of successful new projects with a distributed team. This in-person bias is largely for people who don't know how to communicate effectively.
This position and momentum work bias is for those who don't know how to behave effectively in a superposition.
Not convinced yet, at this point it just seems to be anecdotes, and pretty nebolous ones at that. I would be open to listen to this position if it was backed up by actual examples like "So we were working on Product X and team Y struggled with remote work in that and that way." Creativity/Innovation is not something fuzzy, but something very real that will result in deadlines not met, lower morale and so on - I will start to consider Altmans et al.'s position once I hear those non-fuzzy experiences. (As someone working in a small startup doing innovative products, and collaboration being crucial).
Some of the best and most valuable insights in our process are captured in recorded IRL onsite sessions with our users. Humans put on a bit of a show when they're remotely connected and that just ruins the process because they just sort of withdraw after they say their bit. I have recordings that prove this - users spontaneously changing their minds or sharing more about how they really feel about something.
I would argue that the best creativity on a team occurs when there are actual meat-skeletons together in a room smelling each others' farts, interrupting each other, eating together, getting excited, getting pissed, whatever etc.
But you are absolutely correct that this is anecdotal and nebulous at best. In the article he mentions how this is better when the product is unclear and unformed yet.
This isn’t necessarily a remote/non-remote work problem, but I think that’s why that guy in the original article talks about the benefits of having people in the office.
That used to be my feeling as well. As much as I don't like Zuck in general; we hold our meetings in VR and for us there is no (measurable) difference from being in the office for creative work. While we really struggled on Zoom. After I tried a Quest 2, I decided to just get 15 of them for the team and it just works. Your brain (well our brains, guess there are exceptions) forgets you are not actually sitting in a room with your colleagues to the point where you actually try to physically touch them when working. It works very very well. Never setting foot in the office ever again. Don't really mind if Sam Altman thinks differently...
- capable and not just good salesmen that got into their positions due to various factors like resume-driven development, obscene levels of networking or nepotism, being in the right place at the right time — and riding that wave — etc.
- have gotten the junior-level giggles out of them — and understand that the simplest solution is the best solution; rather than something needlessly complex because:
(“it won’t scale” (i.e I’m at best bored and want to try something new, and at worst trying to shoehorn something insane to further my resume) ||
“we have to do it this way” (i.e. I read a blog post last night and want it to seem like I’m knowledgeable and not an imposter with zero critical thinking ability) ||
“this is the correct way to do it” (i.e. I’m stalling again because I cannot think of a way to provide business value other than prostelyzing various opinions and philosophies about software engineering, despite there being zero hard and objective data that what I’m saying is in anyway effective for anything more than making me seem like I know what I’m talking about))
At that point, once you have enough maturity and experience (i.e the knack for being able to adapt to circumstances by your lonesome), you do not need to collaborate. You can almost always figure it out by searching online for what is almost always a trivial, already-been-solved issue, or by going for a few walks and mulling it over in your head. If it’s a truly hard problem, you can even sit down somewhere and work it through inside your head.
The only two types of collaboration I’ve ever seen in the workplace is:
1). Someone less learned on a subject picking the brain of someone more learned (fair if the subject is complex, and not easily accessible through literature; but grating if it’s something puerile like how to use a tool — RTFM)
2). Two people brainstorming something and coming to the wrong conclusion because they’re implicitly more interested in socializing correctly than coming up with the right answer. You see this with whiteboards a lot.
For example, M$’s Roslyn a few noobs were trying to figure out what data structure to use for representing syntax nodes and the solution they come up all these years ago was utterly silly (red and green trees) — solely because they were white boarding the problem out, and trying to come to a consensus (and to keep the vibes good, maaan) rather than to find the best answer.
Both are subpar from an efficiency standpoint, but great from a career standpoint.
N.B. If it’s not already apparent, I’ve grown tired of “collaboration.” I’ve grown tired of seeing it create more problems. And I’ve grown tired of the intellectual dishonesty around it.
https://news.ycombinator.com/item?id=35767280
Remote work only makes sense when everyone has integrity, but that seems less and less likely in my experience, sadly.
Managers are people too, often struggling because they’re squashed between challenging top down directives and the needs of all their reports.
But then I have to ask - if his employers are happy enough with his work to keep him around, what is the problem there?
Keep in mind, I am also the sort of guy that doesn't rage against employers doing layoffs when they have record profits. It's a natural cycle of business.
Once you take personal feelings off the table and see it all as business relationships, everything is alright. As long as nothing illegal is being done, of course.
In SW environments, having the time to do more work is supposed to mean actually completing more projects. They hire you to "perform duties for x hours a day", not "complete x tasks/x story points per sprint", so if everyone on a team is taking a similar approach, your velocity might be half or less what it could be if everyone ended up on-site.
And working on-site does not mean people will be more productive. A lot of people are very good at giving out the impression that they are very busy day in day out even when productivity is rock bottom.
Then why hire salaried workers while tracking work via sprints?
>your velocity might be half or less what it could be if everyone ended up on-site.
This is assuming more work actually gets done in an office and that offices don't have their own set of distractions. People can also slack off in an office too, or become so distracted by others that their velocity suffers.
Measuring employee performance seems to be a continual struggle that has no relation to in-office vs remote workers. If you can't accurately measure success & value generation of remote workers, you probably also can't measure office worker's either. Just checking that someone is physically in their seat doesn't actually mean they're adding tangible value.
I think a lot of companies have poor project management & employee performance measurements, so half the time, people only have half the picture or don't know what the heck people are supposed to be doing and if that's actually getting done. That only becomes more complicated when projects are abandoned and/or requirements shift every quarter.
https://www.businessinsider.com/how-genz-working-2-remote-jo...
The other side of it, and it's complicated in the same way, is the industry collectively made a lot of bad decisions working from home in 2021, and we're paying for it now.
Or you're just a bad manager.
This sort of perspective is killing any real chance of having a productive conversation about the topic. There's a chance a person very similar to you simply disagrees with you on a very complex topic. There's pros and cons to the office and WFH alike. You clearly do well with WFH, and have good reasons for it. A junior engineer like me did not, so I have a different perspective.
The next exhaustive part of the debate (which you didn't bring up, I'm simply anticipating), is the retort that my team just didn't do WFH correctly, or that Covid was a confounding factor.
0: which is a big sacrifice, since even 2 day hybrid can mean spending tens of hours a month sitting in a car or on transit, not engaging in either productive or self-sustaining activity, and it actively limits where people can live, further propping up cities with housing supply issues due to single-family zoning and a lack of rent control.
1: Not to say this is you, but I can imagine many candidates saying "yes" / "I excel in remote and on-site" to "do you believe you'll be productive in a remote role" even if they aren't sure this is the case for them, in order to look qualified for every open position.
There are pros and cons to RTO, and benefiting your investment portfolio is one of them
When I was in my previous role one of the engineers and I would literally jump on a video call and just leave it on while we worked. If he had a question it could be asked naturally and we could also have the workplace chitchat.
One of my close friends is a firm believer in hybrid working and we discuss this a lot. I think the important thing is communicating with each other and trying to provide an environment which enables your staff to do their best work.
The complexity is added by the fact someone like myself going into the office would be less beneficial to a junior.
This is solely as the WFH preferring employee would not be in the best place to provide advice due to them feeling like they are not being given the working conditions they require.
It’s a tough balancing act.
For me, personally, I am happy to go to social meetings and make it known to everyone they can message/call me on slack anytime — even if I am offline give it a crack.
Workshops are another tool which I feel bridges the gap. Instead of forcing people to go to the office on the off chance they might have a conversation with someone, make a day of it. Provide the grounds for those conversations to happen.
As we dive deeper and the debate is opened it will be interesting to see how it all pans out but I know a lot of devs/engineers are not going to budge on this one.
I can login and out when I need to (meetings/stand ups I obviously need to factor in) which allows me to take an actual break and go somewhere with my dog when I am feeling bogged down/unproductive.
The ability to do this means that, when I return to the desk, I am refreshed and ready to tackle a problem with fresh eyes instead of glazed over and looking at a clock anxiously waiting for my time to jump on a train and commute to my home.
This rhetoric that remote work is bad for business seems to always come from people whom I suspect have an ulterior motive — usually people with investments in real estate and retail businesses which are taking a hit from the lack of lunchtime and rush hour footfall.
My manager once said to me “I hired an adult, so I don’t need to hold your hand” and this has resonated with me since. If you cannot trust your staff to do what is best for you then that is your problem for hiring the wrong people. It isn’t the problem of an entire industry.