It will be interesting to see whether companies can make a hybrid model work reliably. I tend to think that combining remote with on-site leads to worse results, because it’s easy to leave the remote people out of the loop.
The one true hybrid work model for tech (in my opinion anyway) is to just have everyone meet in-person in some cadence for sprint planning/PI planning/whatever your cycle is. Everybody syncs up every so often, and then you leave everyone the fuck alone while they go work. Zoom can handle one-off meetings for pairing or other quick questions, but planning out work/carving out architecture solutions is something better done face to face.
The odds are overwhelming that you do not and will never work on the kind of problems where such a minute advantage (if it even exists, which I doubt) makes any kind of difference to the bottom line. Most business related coding is at the end of the day exceedingly trivial. Requiring any sort of on-site time is a thought that belongs in the past.
I agree most business related coding is trivial, but all of the things that a software engineer does that surround the coding are not trivial. All of the best software engineers I know recognize this, and all of the less effective ones depend on them to fill in these gaps.
Definitely this, in fact I suspect that some larger organizations that get this right might become more competitive to smaller firms than before the pandemic, simple because meeting happy people will have their opportunities to steal focus curtailed and actual work time for people will be more clearly boxed out.
That's what the theory says, but my experience disagrees. I find that when the remote workers have to be kept in the loop or the work doesn't get done/get done properly, then managers make sure they are always up to date.
I've not found that to be true in my career. Where remote work is the exception, rather than the rule, the remote employees are frequently in the dark, and often simply fail to work out. Managers can only do so much when you're missing the critical water cooler/hallway/impromptu meetings.
I've worked in remote-only environments, and (effectively) local-only, both of which worked pretty well. Local-first/remote-rarely hasn't worked.
I've not worked in anything close to 50-50, though, so perhaps that has a better shot at succeeding.
> missing the critical water cooler/hallway/impromptu meetings
Maybe that's the crux of it. I've never worked in an environment where things like that amounted to much. If one of those meetings started to become important, it would always end up with "let's find a meeting room and include Charlie and Susan and get this hashed out."
I'd go so far as to say that if that's the way a team is primarily communicating, there is something structurally wrong.
