public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: {OT} hire a programmer or company?
Date: Tue, 29 May 2012 17:02:33 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120529T184443-900@post.gmane.org> (raw)
In-Reply-To: CAN0CFw2e2BWFtm72qk1T1DAiA=5s_hYH9K2MYc0tuT_aFCipQw@mail.gmail.com

Grant <emailgrant <at> gmail.com> writes:


> I'm debating whether I should hire an expert programmer for $X/hour,
> or a company of expert programmers for $2X/hour.  It makes sense from
> a financial perspective to hire programmers directly, but I wonder if
> there are benefits to hiring a really good company.

OK Grant,

Here is my suggestions:

Think about code integration/management/maintenance
of what your goals is. WHO is going to do this;
the consultant/programmer or someone in your company?

If you know or get solid references to a qualified individuals,
the direct is always better, imho.

What is your target linux distro? Flexible?
Just coding or some deep thinking about the 
server(s) processes and distributed/redundancy
or other hardware issues that will affect the 
running code and configuration?


If not direct, you can use a company and and replace the programmer
until you are satisfied with the work-product. Big companies will
often present marginally qualified folks and then move up the 
skill tree, as it is always easy for them to place top-notch
folks; so you have to be a bit demanding on the software house.


If all you have to do is fuss to the Company and they manage everything
else, 2X is the best solution. However, I've used some
pretty big houses with lots of experts and had to
'surf through' quite a few folks, until you get the one(s)
you want. It is still better than searching yourself,
unless you or somebody you trust knows someone really good.
Expert coders may charge much more, but, they get work
done faster and with a higher (easy to maintain)
degree of excellence. Often the best is the least
expensive, if you are well organized (have written a
specification of exactly what you want and expect).


hth,
James







      parent reply	other threads:[~2012-05-29 17:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26 11:26 [gentoo-user] {OT} hire a programmer or company? Grant
2012-05-26 11:44 ` Florian Philipp
2012-05-27  6:22   ` Grant
2012-05-27  8:27     ` Alan McKinnon
2012-05-27  8:51     ` Florian Philipp
2012-05-27 16:09       ` Grant
2012-05-27 16:35         ` Volker Armin Hemmann
2012-05-27 16:53           ` Grant
2012-05-27 21:18             ` Alan McKinnon
2012-05-28 15:30               ` Michael Orlitzky
2012-05-27 21:18         ` Alan McKinnon
2012-05-28 16:00           ` Grant
2012-05-28 20:50             ` Alan McKinnon
2012-05-29  8:34               ` Grant
2012-05-29 12:08                 ` Alan McKinnon
2012-05-29 17:51                   ` Grant
2012-05-29 20:10                     ` Alan McKinnon
2012-05-30  9:00                       ` Grant
2012-05-29 12:30                 ` Pandu Poluan
2012-05-29 13:58                 ` Michael Mol
2012-05-29 14:05                   ` Michael Orlitzky
2012-05-29 14:37                   ` Alan McKinnon
2012-05-29 23:52                     ` Peter Humphrey
2012-05-30  9:11               ` Grant
2012-05-30 12:57                 ` [gentoo-user] " Nicolas Sebrecht
2012-05-30 22:58                 ` [gentoo-user] " Alan McKinnon
2012-05-31  6:44                   ` Grant
2012-05-29 17:02 ` James [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20120529T184443-900@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox