3 ms·
> If a position is deemed able to be WFH, then the position is WFH Even for Software engineers, I see very few positions which can be fully WFH. If you are new
by RestlessMind 4y ago
> If a position is deemed able to be WFH, then the position is WFH
Even for Software engineers, I see very few positions which can be fully WFH. If you are newbie, it's better to come to office. If you are a tech-lead of a big team or above, it's better to come to office. Only the independent junior engineer role seems to be a good fit for a fully remote setup.
- temporary22 4y agoFully remote setups only work if they are truly fully remote, and if the seniors have the decency to research how to better handle the thing. Onboarding can be done remote, but the best is to schedule extensive meetings / pair programming, or even just a virtual room where the newbie can work independently but ask the senior "as in the office". Or even very clear directions on when to reach out if nothing else is possible. What happens instead that the newbie is expected to handle all the responsibility of reaching out, and when that inevitably fails the conclusion that's reached is that wfh is not for onboarding.
- RestlessMind 4y ago> if the seniors have the decency to research how to better handle the thing. Seniors typically are already overloaded with keeping the product running and backfilling for the departed colleagues (who are being replaced by the new employees). So using words like "decency" is sure to piss them off even more.
- kyleee 4y agoWhich also points to a management problem
- RestlessMind 4y agoWhy stop at management? I mean, by definition, any corporate problem is a shareholder problem since shareholders elect board, which appoints the CEO, who hires the management team who hires rest of the org...