Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

I understand but having worked across multiple remote teams something tells me it's not WFH to blame, rather how it's implemented in your company.

We're doing exceptionally well and my friends from other tech shops have similar experience.



This is just "works on my machine" applied to businesses. If most businesses are struggling with remote work, saying "just get good at it" won't help - they would if they could. Fact is a lot of companies are going to be forced back to in-office because they can't stay competitive otherwise.


This just confirms what I suggested. A "works for me" situation is a clear indication of something wrong with the environment rather than the method.


I think we agree. WFH itself can work with the right environment, but I question wether certain kinds of companies are realistically capable of fostering that environment. Personally I think that if a company finds that it can't do WFH effectively, it shouldn't even be doing tech, and should contract that work out to a company that can WFH. It's like, a code smell for business.


Companies struggle with it because they're not really bought in and have a bias against it. WFH weakens control over the labor pool.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: