Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Channels ▼


7 Best Practices for Being a Successful Remote Developer

Get to Know the Culture of the Organization

After you're hired, it doesn't mean all that's left is heads-down programming. You should continue learning as much as you can about the organization. This will help you work smarter as well as build trust with your counterparts. Most importantly, be proactive in figuring out how your client or manager operates and build off of their style of communication.

That goes for non-verbal communication, too. If team members are expected to be available via video during their shift, make sure you're available during yours. If they sing happy birthday to each other via Google Chat, then join in! If they send e-cards, do the same.

Be Complete When Asking or Answering Questions

Many times, I see emails or hear about issues where the deliverer fails to provide complete context. Without enough background, issues simply can't be acted on. When you're a remote freelancer, you can create considerable goodwill by being complete, especially if you're working a schedule that is different from HQ's or other programmers'. That way, your contacts will always have the information they need and can address things in a timely fashion, even if you're not online.

Whenever possible, include screenshots, documents, and message threads. Err on the side of over-communication rather than assuming that recipients have all the information they need.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.