
Editing code on a remote machine? There’s a package for that. JavaScript consoles and Jupyter kernels? There’s a package for that. Syntax highlighting and code linting? There’s a package for that. One of the big draws of Atom is that it is able to be customised to suit a wide range of uses. Atom is relatively lightweight, cross-platform, open-source, with seamless git and GitHub integration, and the new Teletype package is a promising option for teaching and collaborating on code remotely. I’ve been a fan of Atom for quite a while now, and it’s usually my go-to recommendation whenever someone asks for editor suggestions.

Today I’m going to talk about my current favourites, Atom and Virtual Studio Code. I’ve tried a few different solutions, each with their own strengths and weaknesses. What I didn’t cover was how to effectively interact remotely with a large code base, where just SSH’ing in and using Vim might not cut it. Previously, I’ve written about running Jupyter notebooks on remote servers and streamlining SSH use to make remote working more convenient. Regardless of our personal circumstances, the current situation has necessitated rethinking how we work, and exploring how different tools might help to address our needs. Some may lack a suitable space at home to work comfortably, while others may simply not have an IT setup comparable to what they are used to.



For some, this has meant having to juggle family and work life for others, the sudden loss of human interaction is a very real concern. As a largely computational research group, we are incredibly fortunate in our ability to carry out most of our work remotely, and our department’s wonderful IT and administrative support staff have enabled a smooth transition to remote working.ĭespite our relatively fortunate position, working remotely isn’t always straightforward, and everybody has different home circumstances that will affect their work. The ongoing COVID-19 situation has forced us all to dramatically rethink how we work, with many industries struggling to adjust their on-site procedures to ensure the safety of workers, and many more adapting to support much of their workforce in working from home.
