<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Wanted to say that I think Jon is exactly right. I'm lucky enough to be a part time remote freelancer in another country at the moment and the process with my client is superb because all tasks are documented, all code goes through PR review, and any questions are handled asynchronously through Slack or ticket comments. Of course I miss out a bit on the company culture and various informal discussions.<br></div>
<div><br></div>
<div>I also have a lot of experience working on-site in open plan offices where things are poorly documented and team members frequently interrupted one another to discuss things in person. I've found that often the critical knowledge accumulates to a "super" dev who knows everything by virtue of being there the longest. They end up constantly having to answer questions or become a bottleneck when they are unavailable.<br></div>
<div><br></div>
<div>Neither is perfect for every situation. A rapid prototype is probably going to benefit from a small team sitting next to each other. But for most things I think that it's purely down to process whether remote workers can be beneficial or not.<br></div>
<div><br></div>
<div>(full disclosure, I'm also looking for p/t remote or on-site Berlin work at the moment! :D)</div>
<div><br></div>
<div>Andrew<br></div>
<div>@odaeus</div>
<div><br></div>
<div><br></div>
<div>On Mon, 27 Feb 2017, at 11:52, Jon Wood wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div>My feeling from what people have said so far is that reactions to remote work, working from a different timezone, and working part time all boil down to the same questions of how one works with somebody who isn't currently sitting next to you so you can walk over and ask them questions. The answer to that in my experience is to make sure everything is properly documented - with a co-located fulltime team you can get away with building something and assuming people will come and ask you if anything needs clarifying, that's much less true if the person who built the feature is now off work until Thursday.<br></div>
<div><br></div>
<div>The nice thing is that once you have developed a culture of properly documenting everything and making sure all communication happens using mediums that can be searched you also deal with the other circumstances in which you find you can't just walk over to somebody. Holidays, maternity leave, people leaving the company. Situations in which you can't just ask somebody about their code aren't unique to companies with remote employees, they're just surfaced earlier and more frequently.<br></div>
</div>
<div><br></div>
<div defang_data-gmailquote="yes"><div dir="ltr">On Mon, 27 Feb 2017 at 10:40 Patrick Gleeson <<a href="mailto:patrick@gojimo.co.uk">patrick@gojimo.co.uk</a>> wrote:<br></div>
<blockquote defang_data-gmailquote="yes" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div dir="ltr"><div><div>Re the bit of the question about part-timers, I have to say that
the various times I've been looking for a coder I've never even
considered part-time developers. The reason being, I'm always hiring
someone to be part of a team (even when it's a teeny tiny team). When a
team of coders works together it's a very involved, collaborative
process. You can make it work if people are remote, as long as you have
good communication hygiene, but having someone who's not available 2
days a week? That really messes with the dynamic, both on a practical
level ("WhyTF did they do it like this?" / "Dunno, and we can only ask
them when they're back in on Thursday, so you'd better not touch that
class until then."), and more importantly on a psychological one: people
are tribal, and if you're not fully in the tribe you're an outsider.<br></div>
</div>
<div>Of
course, if the whole team worked part-time, with the same days off,
you'd sidestep that. But even if the feel-good factor offset some of the
lost hours, your output will still drop, and I've never worked for a company that wasn't in a desperate hurry to get stuff done....<br></div>
</div>
<div><br></div>
<div><div><br></div>
<div><div>On 27 February 2017 at 10:23, Thomas Buckley-Houston <span dir="ltr"><<a href="mailto:tom@tombh.co.uk">tom@tombh.co.uk</a>></span> wrote:<br></div>
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div>Wow Evgeny, I really appreciate the feedback. It gives me a much more<br></div>
<div> digestible perspective than, "no, sorry, not at the moment" (which is<br></div>
<div> of course a legitimate response itself).<br></div>
<div> <br></div>
<div> I should have mentioned though that all the places I'm applying<br></div>
<div> clearly express remote focuses or remote friendliness. So I totally<br></div>
<div> understand your preference for face to face, it's a basic human medium<br></div>
<div> we've evolved over millions of years. And I love your;<br></div>
<div> <span><br> > I need a person who will look at the company and figure out how to prevent half the tickets from appearing.<br> <br> </span>Also perhaps I could make clearer that I'm not just looking for short</div>
<div> term contracts. I'd love a permanent part time role, I just have no<br></div>
<div> need for the kind of money full time involves.<br></div>
<div> <br></div>
<div> Anyway, like I said, this is such a first-world problem. But still I<br></div>
<div> very much appreciate the feedback.<br></div>
<div> <br></div>
<div><div><div>_______________________________________________<br></div>
<div> Chat mailing list<br></div>
<div> <a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br></div>
<div> Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org">http://lists.lrug.org/pipermail/chat-lrug.org</a><br></div>
<div> Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br></div>
<div> List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></div>
</div>
</div>
</blockquote></div>
<div><br></div>
<div><br></div>
<div><br></div>
</div>
<div><div>-- <br></div>
<div><div dir="ltr"><div><div dir="ltr"><div style="color:rgb(136, 136, 136);font-size:12.8px;"><div dir="ltr"><p style=""><span class="size" style="font-size:12.8px"><b><span class="colour" style="color:rgb(7, 55, 99)"><span class="font" style="font-family:verdana, " sans-serif""><span class="size" style="font-size:x-small">Patrick Gleeson</span></span></span></b></span><br></p><p style=""><span class="size" style="font-size:12.8px"><span class="font" style="font-family:verdana, " sans-serif""><span class="colour" style="color:rgb(7, 55, 99)"><span class="size" style="font-size:x-small">Senior Ruby Developer</span></span></span></span><br></p><p><span class="colour" style="color:rgb(7, 55, 99)"><span class="font" style="font-family:verdana, " sans-serif""><span class="size" style="font-size:x-small">Gojimo is available on <a href="http://m.onelink.me/44374fef" style="color:rgb(17, 85, 204);">iOS</a>, <a href="http://m.onelink.me/feee4922" style="color:rgb(17, 85, 204);">Android</a> (beta) and <a href="http://app.gojimo.co/" style="color:rgb(17, 85, 204);">web</a> (beta)</span></span></span><br></p><p style=""><span class="size" style="font-size:12.8px"><span class="colour" style="color:rgb(7, 55, 99)"><span class="font" style="font-family:verdana, " sans-serif""><span class="size" style="font-size:x-small">EducationApps Ltd is a registered company in England, No. 07556427</span></span></span></span><br></p><p style=""><span class="size" style="font-size:12.8px"><span class="colour" style="color:rgb(7, 55, 99)"><span class="font" style="font-family:verdana, sans-serif"><span class="size" style="font-size:x-small">Gojimo, c/o Edspace, Block D Room 203, Hackney Community College, London N1 6HQ </span></span></span></span><br></p></div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>_______________________________________________<br></div>
<div> Chat mailing list<br></div>
<div> <a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br></div>
<div> Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org">http://lists.lrug.org/pipermail/chat-lrug.org</a><br></div>
<div> Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br></div>
<div> List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></div>
</blockquote></div>
<div><u>_______________________________________________</u><br></div>
<div>Chat mailing list<br></div>
<div><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br></div>
<div>Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org">http://lists.lrug.org/pipermail/chat-lrug.org</a><br></div>
<div>Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br></div>
<div>List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br></div>
</blockquote><div><br></div>
<div id="sig17774725"><div class="signature">-- </div>
<div class="signature">Avito Ltd</div>
<div class="signature">Company 05946211 registered in England.</div>
<div class="signature">Reg. office: 23 Hoadly Road, Cambridge, CB3 0HX</div>
</div>
<div><br></div>
</body>
</html>