[tezzer]

Several do, the few times I've gone into the office and done a little problem solving with the folks who were there, we accomplished like a week of work in an hour. There's something about putting heads together that's hard to replace. Some of our folks have always been ~90% remote and that's fine, but I think they're missing out on one of the joys of engineering.

[Teknoman117]

The main thing I miss is all the ad-hoc technical discussions about work or (usually) random topics over lunch. We went out nearly every day for an hour or more and had fun conversations. I miss it dearly. With everyone using their normal lunch times for running errands or just working more, we've had very few social meetings since WFH started.

It's just so damn lonely.

[narism]

Gitlab has some good stuff about this in their handbook. You have to be really intentional about this kind of informal meeting that otherwise happens naturally in an in-person situation.

https://about.gitlab.com/company/culture/all-remote/informal...

[dzhiurgis]

IMO companies should pay less people like you as your preferences incur more costs. Alternatively you could hire a co-working hub if you prefer that, but such costs shouldn't be passed onto people who ARE able to control their emotions and work/life balance.

[tezzer]

So instead I should personally shoulder the real estate and infrastructure costs of working from home? No thanks.

[emodendroket]

Such policies could quite reasonably be construed as illegally discriminatory.

[ebrenes]

That's really regressive. My sister-in-law works for HPE and she instead got a work from home bonus added to her paycheck. Instead of having companies offload their costs to employees like some late-stage capitalist dystopia they should compensate employees for providing the infrastructure themselves.

In some jurisdictions this is actually required, if the company is to expect any level of service or availability from infrastructure on the employer's home. For example, if your personal internet fails you cannot be held liable or at fault by an employer, since they're not paying for that. And if they pay for it, then it's on them to fix it since it's the service they provided (just like it's not an employee's fault if the internet gets cut at the office).

[politician]

Are you suggesting that if people were in the office for 40 hours a week, that you would expect to get a sustained rate of 280 days worth of work done per week?

Or are you saying that given the creative thinking time alone that accumulated slowly over a period of time WFH, that the team was able to make 7 days worth of progress in one hour primarily due to the fact that everyone had plenty of time to understand the issues and the pains associated?

Are you confusing _peak_ with _sustained_ productivity?

[tezzer]

No, I'm not confusing anything. I'm stating my team made a great deal of progress when we got together in the office over a sticky problem; and attributing the progress to the random directions the conversation and problem solving effort took when we were in one room bouncing ideas off each other and poking hardware together.

[politician]

Look, I miss having whiteboard conversations too, but if throwing all of the developers into a smelly open plan mosh pit that's a 45 minute commute from home 5 days a week just for that clutch hour of collaboration, count me out. It's just not worth it.