We have something similar, the 2 days are not mandatory though, it would just be appreciated if people could make it to the office (this is just our team, other teams handle it differently).
The two days were chosen as a team and we tried to accommodate everyones needs like childcare duties or and so on.
We use the office days for collaborative tasks such as architecture reviews, peer debugging, idea brainstorming, drinking beer. And the days at home for actual implementation work, i.e. producing code. It has only been a couple of weeks and so far I believe it works quite well, we also said we will review if this is how we want to continue working in a couple of months.
So it could be the same for you, but if you as an employee cannot shape it in any way and only have to follow rules, I would be a bit suspicious.
If the drive to get people in the office is top-down, then I'd be suspicious. But if people are actually asking for it because some parts of the job are easier or just more enjoyable in person, then it might not lead to going back to the office full time.
Hybrid makes a lot of sense to me for these reasons. In person can be so much faster and simpler for heavily collaborative tasks. Five people in a conference room for an hour will accomplish more than those same 5 in a zoom call, and it's less likely for unnecessary people to be part of an in person meeting. Spending 4+ hours on Zoom/Teams calls in a day is also one of the most draining experiences I've ever had as well, full days of meetings in person are far more tolerable.
If something like this would ever come up where I work, I would start running. How would these sort of numbers even translate to something remotely related to measuring the quality or even quantity of the teams output?
I'm not writing code anymore for work, but I think engineers being replaced by the GPT-3 of coding is inevitable and happening, and ever-more-granular observability of (human) developers is just part of that process.
So you can run to a less anti-human org, but eventually we as a society are going to have to decide if humans deserve any dignity/freedom at all.
I read this book during my systems and advanced networking courses at ETH Zurich years ago. As a hard copy, it is an impressively heavy compendium of knowledge but very relevant to everyone that even remotely touches networking on a daily basis.
I remember it to be quite a pleasant read, despite being very technical and crazy long (could also be that I just like the topic).
Open Systems | Zurich, Switzerland (ONSITE) | 80%-100% | Security/Systems/Software Engineer
WFH for now due to COVID, possible afterwards but location must be within Switzerland due to banking regulatory restrictions.
Open Systems is a SD-WAN and Network Security provider that is also operating a NOC and a SOC based on the products developed by the engineering team (https://www.open-systems.com).
Currently we are looking for
- Email Security Expert to help advance our Secure Email Gateway.
- Linux Systems Engineer to bring our in-house LFS to the next level.
- Senior Frontend and Full-Stack Engineer to make the impact of our products visible.
Open Systems | Zurich, Switzerland (ONSITE) | 80%-100% | Security/Systems/Software Engineer
WFH for now due to COVID, possible afterwards but location must be within Switzerland due to banking regulatory restrictions.
Open Systems is a SD-WAN and Network Security provider that is also operating a NOC and a SOC based on the products developed by the engineering team (https://www.open-systems.com).
Currently we are looking for
- Email Security Expert to help advance our Secure Email Gateway.
- Linux Systems Engineer to bring our in-house LFS to the next level.
- Senior Frontend and Full-Stack Engineer to make the impact of our products visible.
