Get the Most Out of Your Remote Developers

As a business, you’re looking for the best talent wherever you can find it. What do you do when you find that talent on the other side of the globe?

If you want your remote developers to hit the ground running, here are some tips. Most of these apply whether you’re onboarding a remote developer or a new employee right in your office!

Consolidate Code Repositories

If your code is spread out of multiple repositories, time will be wasted making sure that they’re all synced properly. The new developer will discover missing pieces as they encounter build or run-time errors. Modularization is a good practice but if there rarely is a good reason to have 10 different code repositories for a single application.

Create an Onboarding Document

Once the code is synced on the developer’s machine, it’s time to build and run the application locally. It helps to have a document that explains all the dependencies that need to be set up and all the scripts that need to be run to do that.

Create Environment Setup Scripts

If you’re having each new developer go through a lot of manual steps to set up their environment, it’s probably time to create some setup scripts. These include installing programs, setting environment variables, creating configuration files, registering with partner services, etc.

Use Your Bug-Tracking System

You won’t be running into your remote developer in the hallway to ask them how the project is going so you’ll need another way to keep track. Luckily, today’s bug-tracking tools can almost eliminate the need for regular status meetings and email follow-ups. Make sure the bugs are always in order and a good remote developer will do the same so that you can just open up the tool and with quick glance see what’s pending, in-progress or blocked and track all progress in the comments and attached screenshots.

Use a Shared Wiki or OneNote

Where bug trackers fall short, a shared document or notebook can fill in the gaps. Here the team can keep up-to-date documentation that people refer to regularly, such as contact information, high-level project status, high-level project architecture, playbook instructions, onboarding instructions, references to other resources, etc.

Find the Best Talent

If you need help implementing any of these tips, we can help! Contact us and tell us about your needs!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s