<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 03:31:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chris Hartjes' Blog: So You Want To Telecommute? Part 1 - Building Trust]]></title>
      <guid>http://www.phpdeveloper.org/news/12973</guid>
      <link>http://www.phpdeveloper.org/news/12973</link>
      <description><![CDATA[<p>
As finding good, qualified local PHP developers becomes harder and harder for some companies, they're slowly realizing that they might need to look outside their area for good talent. If you're a developer and are wanting to promote yourself as someone who can work as a remote employee, you might want to <a href="http://www.littlehart.net/atthekeyboard/2009/07/29/so-you-want-to-telecommute-part-1-building-trust/">read this post</a> (the first of a series) from <i>Chris Hartjes</i> on telecommuting.
</p>
<blockquote>
My current position as a "software engineer" for <a href="http://www.xmlteam.com/">XML Team Solutions</a> is a 100% telecommuting job. [...] Now, when you have a company where none of your fellow employees works in the same city, let alone the same country, you quickly find out what the key issue really is: trust
</blockquote>
<p>
He goes on to talk about how to build up that trust, not just with the other developers on your team but with the manager you're working with to show them you're the qualified employee they think you are. He also points out one of the big hindrances some companies take issue with on not having all their people in one place - easy meetings/collaboration. 
</p>
<p>
This post was inspired by <a href="http://blog.calevans.com/2009/07/29/remote-developers/">these thoughts</a> from <i>Cal Evans</i>.
</p>]]></description>
      <pubDate>Fri, 31 Jul 2009 09:41:30 -0500</pubDate>
    </item>
  </channel>
</rss>
