I have been remote for 10 years. The secret not to get nuts is to interact online with colleagues as often as possible. "From the employer’s perspective, you’r

I have been remote for 10 years. The secret not to get nuts is to interact online with colleagues as often as possible. "From the employer’s perspective, you’re risking burning yourself out if you work 50-60 hours a week" mmm... 50 hours is pretty common in the software industry, and being remote makes it easier not to burn out in fact because you're not losing time in commutes and in loud open spaces where you can't hear yourself coding. In any case it's quite hard to define a number of hours per weeks. Building software is done by waves. You can spend a 70h week because of a production push that goes wrong, then a very calm week. So don't take those numbers/week too seriously imo.