4 ms·
As a concrete example: getting an intern’s corporate proxy set up for a build system over video chat can be quite difficult. If they change the system proxy set
by foooorsyth 3y ago
As a concrete example: getting an intern’s corporate proxy set up for a build system over video chat can be quite difficult. If they change the system proxy settings or change networks, the screen share goes out. You don’t face these day 0 mentoring issues in person.
- lowbloodsugar 3y agoOTOH optimizing for “day 0” of N seems counterproductive.
- cheriot 3y agoCompanies have a steady flow of early career people that need mentoring. It's not just one time
- dustedcodes 3y agoStill early career people are only a tiny fraction of the company’s residents to whom all the WFH culture hugely benefits and the company as a whole. Nothing is perfect, but WFH comes closer than anything I’ve in my lifetime before.
- robryan 3y agoYeah I think most people would agree that a new employees first week would usually be more productive in the office with someone sitting next to them helping.
- Phelinofist 3y agoAnd? Just reconnect the call then. Oh, and talk to your IT guys so they fix their shit
- foooorsyth 3y agoYes and if the intern who has never been behind a proxy before in their life just nuked their global proxy settings, that can be difficult. >Just have the person who doesn’t understand what they’re doing revert their network settings perfectly across N esoteric config files for shell, npm, brew, gradle, cocoapods, the system itself, the video chat client itself perhaps, etc etc etc IT departments can’t predict every build environment, and not every build environment is containerized.