Ah. Another thread of people complaining about WFH. No software team has any reason to step foot in an office for day to day work. None. Even the DoD has switched to WFH if the code itself isn’t classified. If you’ve been on unproductive or slacking teams, it means you have bad employees or a company that isn’t run well. Good people get the job done and get results. I was on a globally distributed team, 100% WFH, years before the pandemic. We build software for satellite imagery used by governments and billion dollar companies. We met every deadline and never had any problems caused specifically because of WFH. Everyone’s work life balance was better. Happier people makes more productive people. Again, if you’ve had a problem, it’s the people, not the concept. Stop having lazy people and/or lazy management. Software development does not have tone an “everyone work 9-5 every day” job. Not in most cases. Sometimes I worked normal hours. Sometimes in the middle of the night. Sometimes 2 hours here, 4 hours there, etc. At the end of the day, as long as you show up for meetings or scrums and you’re getting the job done and meeting deliverables, who cares when or where you work? And being a new parent at that time, that flexibility was amazing. I would never work another development job again if it requires going to an office. I had an offer from AWS, I turned it down because I was WFH “for now” and then would require a 40 mile commute. They couldn’t pay me enough to do that.