From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} hire a programmer or company?
Date: Sat, 26 May 2012 23:22:22 -0700 [thread overview]
Message-ID: <CAN0CFw1bafR3G0QYYyprjUv63O-ymNAORqFsR508uzwyND2hsA@mail.gmail.com> (raw)
In-Reply-To: <4FC0C217.6050302@binarywings.net>
>> 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.
>>
>> I'm sorry this is OT, but I bet you guys have some seriously good
>> insight on this.
>>
>> Thanks,
>> Grant
>>
>
> For starters, you could give us a bit more insight into the kind of
> project we are talking about. What's the expected development effort,
> what are the services you pay for (binaries, source code, testing,
> maintenance, ...)?
The project is made up of various and ongoing scripting tasks for a
relatively complex website.
> Regarding programmer vs. company, I'd say it depends on what you expect
> and pay for. If you just want it coded, then the lone programmer is
> probably as good as the company (since programming itself doesn't really
> scale well with the number of devs).
That's a really good point.
> Extensive testing, on the other hand, is something a team should do.
> Sure, the lone programmer can write you some unit tests and conduct a
> system test, but testing itself is a profession of its own and should be
> done by a second person with the relevant training.
>
> But in the end, these issues a minor. It really boils down to whom you
> trust more. Ask for references, look at their previous work, talk to
> them, etc.
Can you tell me what sort of positive and negative things to watch out for?
> All things being equal, paying 1*x instead of 2*x gives you the chance
> to pay another 1*x to a second developer if things don't work out with
> the first one. ;-)
Once I need more than one developer (which could come sooner rather
than later due to the availability of these guys) am I likely to
struggle managing them? I've read a bit about "Agile" software
development and I plan to read a lot more. Is that the way to go?
Would hiring a company make management a non-issue from my perspective?
- Grant
> Regards,
> Florian Philipp
next prev parent reply other threads:[~2012-05-27 6:24 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 [this message]
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 ` [gentoo-user] " James
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=CAN0CFw1bafR3G0QYYyprjUv63O-ymNAORqFsR508uzwyND2hsA@mail.gmail.com \
--to=emailgrant@gmail.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