{"id":66,"date":"2006-11-14T20:49:00","date_gmt":"2006-11-14T10:49:00","guid":{"rendered":"http:\/\/www.doolwind.com\/blog\/?p=66"},"modified":"2006-11-14T20:49:00","modified_gmt":"2006-11-14T10:49:00","slug":"the-problem-with-contractors-in-software-projects","status":"publish","type":"post","link":"https:\/\/www.doolwind.com\/blog\/the-problem-with-contractors-in-software-projects\/","title":{"rendered":"The Problem With Contractors In Software Projects"},"content":{"rendered":"

<\/a>Every project I’ve worked on has had at least one contractor working on some part of it.\u00a0 I’ve worked both as a contractor and with many and I’d like to discuss a few of the problems I’ve seen.\u00a0 Some of these problems are quite subtle and I believe are often overlooked by managers of software projects.<\/p>\n

1.\u00a0 Pay difference<\/strong><\/p>\n

There’s just something about knowing that the person sitting next to you is earning twice as much (or more) than you, per hour.\u00a0 Even though contractors have to pay their own super, holidays, sick leave etc, they still often end up earning a lot more on an hourly basis.\u00a0 This builds major resentment between the contractor and the rest of the team.\u00a0 A while ago I talked about keeping programmers happy by not letting them know how much they are being billed out at, compared to how much they are receiving.\u00a0 Knowing how much more a contractor is getting paid is even worse!\u00a0 It’s basically saying that some guy who doesn’t even work at your company is more valuable than you are.\u00a0 I don’t care who you are, that hurts.<\/p>\n

2.\u00a0 Shows a lack of planning in management<\/strong><\/p>\n

Needing to hire a bunch of contractors at the end of a project (as it runs overtime and grows in budget) shows that management can’t properly plan for the future.\u00a0 They’re saying that they didn’t think that the project would run over time or budget and by the time they admit it, the only option is getting in hired help.\u00a0 It\u2019s a basic fact of all complex software development, it\u2019s generally going to run over time and budget and management needs to stay on top of this and supply enough resources as soon as the need is realized.<\/p>\n

3.\u00a0 Can’t hire good people<\/strong><\/p>\n

Unlike #2, if you have a bunch of contractors on a project for its entirety, it shows that the contractors wouldn’t dare work for your company.\u00a0 How does that make the rest of the employee’s feel?\u00a0 It makes most people I know feel like they’re stupid enough to be paid less for to do exactly the same work.\u00a0 If your company hasn\u2019t got enough incentives to make people want to work there full-time then something needs to be done.<\/p>\n

4.\u00a0 Team doesn’t work as well together<\/strong><\/p>\n

Unfortunately, your contractors will be outsiders.\u00a0 For the reasons above, the rest of the team will resent them and you can’t have good team cohesion with this resentment present.\u00a0 Thankfully, most contractors are nice, happy people (otherwise no one would hire them) which keeps the resentment from becoming personal, but it’s still there at some level.<\/p>\n

5.\u00a0 They don’t care as much about the project<\/strong><\/p>\n

On the flip side to #4, it’s hard to have as much passion or care about a project you’re simply being paid to work on.\u00a0 From monetary incentives like profit sharing down to not being part of the full company dynamic, contractors just won’t care as much as their regular employed colleagues.\u00a0 If they were passionate, they’d be an employee, living and breathing the game and the company.\u00a0 The bottom line is that contractors are mercenaries; they go to the highest bidder at the time.<\/p>\n","protected":false},"excerpt":{"rendered":"

Every project I’ve worked on has had at least one contractor working on some part of it.\u00a0 I’ve worked both as a contractor and with many and I’d like to discuss a few of the problems I’ve seen.\u00a0 Some of these problems are quite subtle and I believe are often overlooked by managers of software Read More<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"enabled":false},"version":2}},"categories":[33],"tags":[],"class_list":["post-66","post","type-post","status-publish","format-standard","hentry","category-game-development"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pgEc5-14","_links":{"self":[{"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/posts\/66","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/comments?post=66"}],"version-history":[{"count":0,"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/posts\/66\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/media?parent=66"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/categories?post=66"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.doolwind.com\/blog\/wp-json\/wp\/v2\/tags?post=66"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}