99 ms·
I manage a team of 20 fully remote devs, so I get to see exactly when everyone is working. When they're chatting, when they're pushing code. We don't force peop
by lordnacho 8y ago
I manage a team of 20 fully remote devs, so I get to see exactly when everyone is working. When they're chatting, when they're pushing code. We don't force people to be working at any particular time, so I'm guessing when I see them is when they want to be working.
You can tell some people are complete night owls. One guy checks in code at 3am and rarely talks to anyone until the evening. I guess he sleeps when the sun is out.
Other people are a bit more ordinary, but still it seems the most productive hours are not quite as early as when most schools or businesses tend to be open. I'd say maybe 10am is the de facto "opening time".
There's also a tendency to have a lull in chat in the early afternoon. People go off to lunch having some ideas about what to do, and then they come back and do it before dinner. Or they are in deep thinking mode and don't want to talk, and then check in the code.
Having no meeting time and no commute seems to help everyone. It gives everyone an extra work day each week, and they can spend their time when they want to. It also makes managing easier, as I don't have to chase everyone at the exact same time.
- asia777 8y agoAre you guys hiring? :P
- lordnacho 8y agoRight at this moment we're focusing on launch, don't have time to onboard anyone. If launch goes well probably.
- sytse 8y agoYou can find other fully remote companies at https://www.glassdoor.com/blog/100-percent-remote-companies/ https://www.glassdoor.com/blog/100-percent-remote-companies/ and we at GitLab are all remote as well.
- z3phyr 8y ago> One guy checks in code at 3am and rarely talks to anyone until the evening Does everyone live in the same time zone?
- lordnacho 8y agoNo, we're distributed all around the globe, TZ from Vancouver to Sydney. But I know where people are and Slack hooks tell me when someone pushes code.
- antonp 8y agoWhat are your thoughts on daily stand-ups and scrums with fully remote teams with different chronotypes. Does that work for you guys?
- lordnacho 8y agoWe just have a bot that asks you when you wake up what you're up to. It's mainly so I know what I'm interrupting if I start writing to someone, but everyone can look in the bot's channel for the same purpose. As for everyone being on different times, it's not a problem. There's always someone you can talk to, and you know what everyone else is doing. Plus there's a chat history for every project, and cards for every outstanding issue.
- GordonS 8y agoThat's a really interesting approach to the daily stand-up! I've never heard of this before, but I'm going to give it a go on my next project - would he interested to hear if anyone else has tried this?
- ncphillips 8y agoWe tried it for a while but switched back to actual stand ups. There were several reasons: 1. Stand ups aren’t status updates, they’re replaning meetings, conversation matters. 2. People stopped answering the bot. It feels like an impersonal management tool. 3. There’s no need to persist the standup output. 4. Remote workers feel more like they’re part of the team. The whole team can chit chat for a few minutes before to start the day. 5. We worked on streamlining our meetings. They are always between 8-12 minutes. Making it async. Means it might be a couple hours before you get everyone’s info, that slows down the replaning process a lot.
- fjsolwmv 8y ago1. If you are replaning (?) every day, maybe your project is in chaos and needs some real planning so people can make consistent progress without changing direction every day? 4. Everyone is forced to kill time or disrut schedule so that they can start the day at one privileged time. 5. Aren't you slowing down by waiting for a meeting to get the info? Everyone has to prepare for the meeting in advance, so waiting for the meeting is delay.
- Void_ 8y agoHow do people get anything done in 2-3 hours between 10am and lunch? I always work 7-8am to 12pm, because I need uninterrupted 4-5 hours to get really zoned in. When I come back from lunch, I'm already in a good place to go back to intense focus.
- randallsquared 8y agoThose who start working about 10am often don’t choose to completely stop work for lunch unless required to do so.
- aiisjustanif 8y agoDo you have any proof of that?
- randallsquared 8y agoNope; just personal observation.
- badsectoracula 8y agoPersonally i often start work at 10am after a breakfast, so by 12am i'm just not hungry yet.
- yabatopia 8y agoOr they have their lunch a bit later, like 2pm. You don't have to have lunch at noon.
- aoeusnth1 8y agoYep, I usually eat lunch at my desk and work straight through until a late afternoon nap.
- lordnacho 8y agoWell there are things to do that aren't deep-thinking coding. Interfacing with team members, running errands, interviewing candidates, etc.
- baxtr 8y agoWhat is your experience regarding productivity? There is the wide-held belief that remote teams are less productive than co-located ones. I have no clue if this was ever measured, but my gut tells me there could be something to it.
- freedomben 8y agoNot OP, but my experience has been that for more senior people and for projects that don't require a lot of collaboration, productivity is way higher. For junior people or projects that require lots of collaboration, the remote nature does add some overhead. Your culture matters a lot here. If your culture is one of facilitating remote communication, then it can be done without too much drag. If you have a culture where many people are in an office, and don't tend to put things in slack or a video system such as zoom, then the overhead can become huge. When working remotely full-time, I had some of the most productive days of my life, as well as some of the worst when I had to wait hours sometimes to hear back from members of my team. Highly collaborative efforts tend to suffer quite a bit in the asynchronous distributed model.
- christophilus 8y agoSame. I work for a company that is 100% remote. It’s the most productive group I’ve worked with in my career. Also the most senior, so it’s hard to say how much remote work is to credit vs median seniority. I think the remote-first culture of the company attracts self-managers who value quiet, focused work, and who have relatively good communication skills. Anyway, I never want to go back to office work after this gig.
- matthewowen 8y agoI don't know that you can separate the two: if you hire remote it's easier to hire more senior engineers.
- hinkley 8y agoHow do you defend hiring a fixer upper halfway across the country when you can get someone just as bad locally? I think though the fact that there’s friction to hiring junior people in a remote office situation should be of concern to us. There is always going to be a fresh batch of recruits and if we lose the ability to train them then who will take up that job, and what lessons will those people focus on?
- shaklee3 8y agoI think it's easier to have Stockholm syndrome when you're remote since you really want it to work. It sounds great on paper, where commute times are cut, office space is free, etc, but except for a small amount of people on a small amount of tasks, it's highly inefficient. Having face to face, knowing the person a couple offices down, and working on any collaborative tasks are far worse remotely in my experience.
- yazr 8y agoDid you need very selective hiring and mercy-less attrition to get to this team? This is obviously a sensitive topic It seems to me, FINDING the right team for remote is a lot of trial and error. (I managed a few small off shore teams and the quality really varied..)