It started with my wife Nina and I deciding that it would be good for us to move to Hyderabad for three months starting Oct 2, 2016 until Jan 8, 2017 for various reasons. As I was keen on continuing work at Jukedeck, I proposed the idea of me working remotely during this period to Patrick, the COO of the company. After some deliberation and another meeting with Ed (the CEO), much to my delight, the company decided to give it a try under the condition that we would review this arrangement each month and be quick to act in case of any unexpected (negative) eventualities. I was very excited and at the same time anxious as this was the first time I ever worked remotely from home.
Before leaving London, I had a quick meeting with my team lead Kevin who was very supportive of this idea and we discussed a few things while leaving others to be dealt with as and when needed. First, we decided that I would be working from 11AM until 7PM IST instead of my usual working hours of 9:30AM to 5:30 PM BST which would (considering the 4.5 hours difference in time between Hyderabad and London) give me five hours of overlap in time with my team and three hours during which I would be by myself. We did also note that daylight savings time would set clocks in the UK one hour behind making the time difference 5.5 hours from the initial 4.5 hours but agreed to consider the option of me starting an hour later when this happens. We also agreed that I would update my team with my work every morning on the standup channel we have on Slack. If there were any brainstorming meetings, I would have the opportunity propose ideas before the meeting and again after going through the Google Doc containing the minutes of the meeting after it finishes. And I would be in touch with my team through Slack and, whenever needed, Skype. We also discussed a few worst case scenarios where, if this arrangement did not work out, I would consider switching to part-time work or even a sabbatical leave until my return to London in January.
Setting Things Up
On arrival in India, without any delay my first task was to setup an office at home. My parents, who we were living with during these three months, allowed me to use the guest room/study as my office. I had a reasonably quiet space with a big enough desk to work on. Although it went through a few changes as time went by, it essentially looked like this:
Once I got started this way, I was ready to go! In the rest of this post, I’ll write about some of the things that stand out in my memory from others that were more mundane and easy to forget.
Participating in Standups Remotely
About two weeks into my move out of London I started noticing that I was unable to keep up with what some of my teammates were working on. I realised that this was due to the fact that while I was updating everyone with my work on Slack, the reverse was not happening. I brought this up with Kevin and we decided that the simplest thing to do would be for me to attend standups via Skype. We started first with one of the team members holding a laptop during standups with a Skype session which turned out to be a bit cumbersome in addition to the poor audio/video quality. Switching to a mobile phone was less cumbersome but still didn’t help the quality. We then came to know that it was possible to send video messages over Skype and while this was not real-time, it was certainly very clear and allowed me to go over standup in my own time. So we settled with this.
I suppose the bright side of this arrangement was that standups were brief, concise and to the point. There is a tendency for standups to turn into discussions about something very specific, involving only some of the team members while others wait without necessarily knowing what the conversation is about. It certainly avoided such a situation, and I even had a couple of my team mates acknowledge this benefit to me since we started with it.
Pair Programming Remotely
I was assigned a task at one point that required pair programming with my colleague, Marco. This was the first time for both of us to take part in remote pair programming. The first alternative we tried was to use the Atom editor plugin called atom-pair. It worked, however, as this was around the time when my broadband connection quality was at its worst the editor took several minutes to update the text that Marco typed, on my screen. It was bad. We then decided to switch to a more lightweight alternative as we have our trusty Jukedeck server, Ada. The setup was the following. We both connected to Ada via SSH. Once we were in, I started a Tmux session and opened the Python source file using Vim. Marco switched users to be me (he had superuser privileges on the server so I did not have to share my password with him for this) and attached himself to the same Tmux session from his end. Despite the lag, this worked like a charm! This setup came with the added benefit that we could open any number of shells through Tmux, and also have the IPython interpreter running alongside our editor to test our changes. While doing this, we also had a Skype session open where we discussed things. We carried on for about 5 hours with this with hardly any interruptions and got quite a bit of work done.
For the first attempt, I think this went very well. And a win for the very minimal command-line approach to work that I am strongly in favour of. As an alternative to both users involved in remote pair programming using one of the users’ accounts, a dedicated pair programming account can be created on the server which has access to all the relevant source repositories and to which multiple users have access. This would help if one or both of the users engaged in pair programming do not have superuser privileges.
Making Presentations Remotely
At Jukedeck, we have what we call Lunch & Learn (L & L) sessions where a member of the team (or someone the company invites) makes a presentation about a particular topic that might benefit or be interesting to others. I volunteered to do my first L & L session on “Machine Learning at Jukedeck” on Nov 1, 2016 where I planned to go over the basics of machine learning and how we employ it to power our AI music composer. The setup was fairly basic and simple. We initiated a Skype conversation on my colleague Eliza’s laptop, and I emailed a copy of my presentation to her so that she could navigate through it while I spoke from the other end. It went on smoothly without any interruptions and the message seemed to have gone across quite well. I did answer a few questions too, but couldn’t follow a few others due to a poor signal.
I found this to be a nice way to stay in touch with everyone else in the company (apart from my team members who I was liaising with everyday regarding work) and make my presence felt. I was keen on doing another L & L remotely, however, there was not enough time for this before my return to London.
The only thing I wish had worked out better was my internet connection. Although we had a working 10 Mbps connection from BSNL (India’s National ISP), it was far from reliable. There were brief and frequent outages throughout the day on many days which was frustrating when loading webpages, pulling code changes from GitHub or working remotely via SSH on our company server. My only consolation was a patient and polite customer service, and the courteous technicians they sent forth to fix the connection. Fortunately, the worst of my connection woes lasted only during the first two weeks after which things got better.
To add to my troubles, the IP address (of my home router) from which I connected to our server in London kept changing on a daily basis, and since we had IP-based access restrictions in place I had to share my new IP every morning with Marco who would allow me to connect from it. We did this for about two weeks when we decided to simply unblock a range of IPs from which I seemed to be connecting. In contrast to this, in the UK, one’s public IP (say at home) does not seem to change over time which is what motivated this IP-based access restriction and made it possible in the first place. So now that I’m back, all those IPs are once again blocked and things are more secure once again.
Change in Working Hours
In the second month of my remote work, daylight savings time kicked in and I was one extra hour ahead of my team back in London. Kevin let me decide whether or not I would like to change when I started my day. Initially I did, so that I have the same number of overlapping hours with my team. After about two or so weeks, I found that this was not working out, mainly because I was almost completely losing the most productive part of my day – the morning hours before lunch. Plus, my day typically ended between 8-9PM and this nearly ruled out any prospects of making plans for the evening.
I decided to altogether break away from the daily 11-7 routine, and started even earlier in the morning on certain days when I didn’t anticipate much interaction with my team members. And by this time, both Kevin and I were seeing things work well and had the confidence that moving things around a bit is a minor risk to take if there was a chance of me being more productive. And it certainly didn’t make things worse!
Change of Location
It was around a month and a half after I first started working from my parents’ guest room when my cozy little home-office in the study stopped feeling as cozy. It felt isolating, and I just didn’t look forward to going in there every weekday morning. Clearly, I needed a change of environment. I’d been reading some books about remote work around that time (more on these below) and they suggested either trying out cafes or coworking spaces which would be bustling with some activity that might alleviate the feeling of isolation and lead to a healthier state-of-mind.
For a start, I moved to the dining room. This helped, as it was a bigger space and I’d see people more often than I did in the study. A friend of mine also put me in touch with one of his friends (a senior of mine from the IIIT-Hyderabad) told me of one of his batchmates who had gone on to found his own Data Science startup Predera that had an office in Hyderabad, and he was more than happy to let me work from there if I wanted to. As the office was at least a 30 minute drive away from where I was, I kept postponing my visit and ultimately didn’t end up going there but it was certainly very generous of him to keep the offer open!
What I found particularly nice about this setup was that there were very few distractions and thus it was a joy to code, review research literature and GitHub pull requests thoroughly. Furthermore, any conversation I had with my colleagues related to work was concise and to the point. I was in the quiet comfort of my home and the nature of my work which mostly involved individual work with the occasional discussion with a colleague or two was well-suited for a remote setup. Personally, I didn’t find it hard to motivate myself to stick to a work schedule and I would like to attribute this to four years of learning to do this during my PhD. I felt more often like I did justice to the work I took up because of the lack of distractions. One can almost see this as an exercise in self-discipline.
I was also able to skip the roughly 1 hour long daily commute between my home and the office, which was a noticeable change. I wouldn’t really count this a positive change as I cycle to work everyday in London and rather enjoy doing it. However, I can imagine that for someone who drives or takes the public transport to work to work this might come as a change that they would welcome. In my case, I spent the hour I saved on exercise and running in a nearby park so there was not so much difference in what I spent the time for.
And I was also reminded on several occasions during the three months, what a fantastic team at Jukedeck I was a part of! All my team members were supportive of my move, patient and creative in dealing with any glitches that arose thereof and not once showed any signs of disapproval. Kevin was very good at assigning tasks to me that were both challenging and that I could work independently on with some discussion with others in the team. This really minimised delays and feelings of anxiety in me that I wasn’t able to contribute which could have ensued otherwise.
While the experience was mostly positive, there were of course some downsides that became evident after just he first couple of weeks. As much as I did make the effort to share my input before and after the meetings, I felt a little less in control when it came to the direction in which the meetings went as this usually involved debating and persuasion which were much easier to do by being there in person. This effect would be far less pronounced if we were a fully remote company, in which case our processes would work the same for everyone. However, this wasn’t the case and while many things did work out, good communication was the biggest challenge among those that didn’t.
Physical absence from the office did feel isolating on a few occasions. I made up for this by engaging in the occasional friendly banter with colleagues over Slack and responding to their non-work related posts which helped me feel like I was still a part of what was happening in the office. It was also important to get out of the house a couple of times during the week just for some change of environment otherwise I felt locked-in. I missed all the team outings and lunches which was a very good opportunity to bond at a personal level with my teammates.
I did see myself falling behind some new developments taking place in the office, particularly those that came about during meetings that I was unable to attend due to the time-difference or poor communication between me and the team in London during the meeting. At least in my case, Skype (or Slack video chat) did not work as well as I had hoped they would. I would say the success-rate was around 40%.
Again, these downsides were not something that couldn’t be addressed but I thought it would only be fair to mention them along with the things that did work out. I’ll not speculate about how it would have turned out otherwise, but I sure was happy to be back in person to the Jukedeck office in London after three months.
If You’re Interested in Remote Work Too…
There is an excellent Hacker News post that answers several questions related to remote work, and also contains some very handy links to websites that facilitate remote work and create opportunities for those seeking to make a career out of working remotely. Here I came across two very well-written books on working remotely. The first is called “Remote: Office not Required” by the founders of 37Signals (now Basecamp) which is a company that has seemingly mastered the art of effective remote work. And the second is “The Ultimate Guide to Remote Work” by the folks at Zapier. You can even get a free PDF/MOBI copy of this book on their website. While there is some degree of (I should note, reasonable) self-marketing that went into both these books, they are definitely well worth reading for anyone wanting to get an insight into the pros and cons of remote work. Essentially, what all the different resources gathered in this Ask HN page suggest is that thanks to technology, we’re heading towards a world where remote work (at least in the tech sector) is becoming more and more feasible for those seeking a change from the 9-5 office work. It certainly gave me something to relate to, tips to follow and a feeling of being a part of a larger (but not large in an absolute sense) movement.
As much as I had my apprehensions (as I often do with many things), I think this was a fantastic experience overall – I got to spend time with my parents after nearly two years of being away in the UK busy with my PhD, meet old friends, get married to my lovely wife Nina who I must thank for insisting on moving to India for three months, and last but obviously not the least be a part of a work arrangement that was indeed something new and unique in my experience. It got me interested and researching about making a career working remotely, which is something I believe I’m likely to follow up on at some point later in my career.