3 ms·
I work fully remote now too. Thoughts: - It helps that everyone is a senior dev on my current project. There's nobody on the team who needs to be handheld thro
by lordnacho 9y ago
I work fully remote now too. Thoughts:
- It helps that everyone is a senior dev on my current project. There's nobody on the team who needs to be handheld through anything. I've pretty much said "Welcome, I see you were able to build the project. Let's automate a Valgrind step in the CI pipeline". And like magic the new guy does a merge request with a Valgrind step soon after.
- Being remote also means you are effectively only looking for senior staff, because you get so many CVs, why would you go for an unproven junior guy? You also tend to think young people are slackers, or someone on your team will. The only time I worked with someone fresh from a bootcamp was because she was inexpensive. Good worker though.
- Tools: Slack, GitLab. They seem so intuitive, never met a dev who needed to be shown how they work. Slack for discussions. GitLab issues for specific issues.
- Culture: wrong personalities are magnified. When you aren't talking to someone in person there's no facial feedback. If someone says something people don't like in person, they often get the feedback from the listeners quickly and are able to change tone. Online, this is not so easy. We had one guy who was being very aggressive in technical discussions, and it annoyed people.
- Tools/Culture: some people are resistant to organising their work through issue tracking and version control. This was a huge problem at an onsite job I had years ago. If it had been remote, it would have been even more of a disaster. Part of the issue is when you write a bug report, you are implying someone has done something wrong. This is a terrible attitude. Along similar lines, if you create a goal like a milestone, you are again setting yourself up for failure if you don't reach it. What kind of people are prone think this way? Strategy quants whose job it is to deliver the magic that can't be found in any published work, and whose work is greatly affected by randomness. Now I'm sure they're not all like that, but the ones I worked with did seem to have rather fragile egos.
- Culture: Not everyone wants to work remote. One guy left because he missed the camaraderie of the office, the on/off of being in or not. Of the people who love remote, a lot have families. Then there's the ones who use it to globetrot. Those two tend to not have an on/off. They're always kinda there, kinda not.
- Culture: Meetings are drop-in, drop-out. In real life some people like being able to call a bunch of people into a room and have them stay there for questioning. I don't think I've ever met anyone who liked that. Online meetings are asynchronous. I might say something, then go to the bathroom without telling anyone, then come right back and catch up. People leave to get their kids, and you don't expect them to be right there. But coding work tends to accommodate that.