Comments on: Why Pay Someone to Develop Software?

By: S-Copinger

S-Copinger — Wed, 01 Jul 2009 16:29:53 +0000

Yes, good analogy. However, it also applies across all professional services. First off, people frequently balk at the estimate/quote for a job which covers all the work and expenses of the job in one figure, yet will happily spend ten times as much piecemeal trying to do it themselves. Secondly the DIY battle-cry “how hard can it be?” – if you do not know what is involved, watching an expert it looks easy. Third, how often do people figure in to the costs the expenses involved in getting things wrong then paying to fix the problem?

(From the lawyers point of view, DIY Wills are often very profitable – sorting out the mess in the executry/probate can double or triple the legal fees)

OTOH, if you do have the skills needed, employing someone else comes under “outsourcing”, and it is a case of comparing your cost of time against the alternative. Shifting analogy slightly, you may employ an electrician to install a new light fitting at home, but it is probably a waste of money to pay someone to replace the lightbulb; however if you manage a large hotel it will be more cost effective to pay someone to change lightbulbs (among other jobs) than do it yourself.

By: Bob Keeney

Bob Keeney — Wed, 01 Jul 2009 02:23:06 +0000

OPC (Other Peoples Code). I cringe every time I get one to bid one.

Funny enough, the contractor that just finished remodeling our kitchen has similar terms for do it yourself remodelers. None of which I can print.

By: Mike Bailey

Mike Bailey — Wed, 01 Jul 2009 01:32:51 +0000

Another big advantage is that when you hire the professional software developer you are getting their experience that comes with that. Not only will the initial version get done quicker, but you can bet (if they are good) that the application will be better written using advanced software engineering techniques which will make it more expandable and easier to upgrade in the future.

Sometimes it’s amazing when you have to deal with poorly written code, just how much work is required to add in what seems like it should be a simple feature. You can avoid this hidden cost down the road if you invest to get the software done correctly.

By: Bernie Hosey

Bernie Hosey — Wed, 01 Jul 2009 00:41:48 +0000

Bob,

Your analogy is spot on and I suffer from it myself. Part of it is that I’m cheap and flawed when it comes to home improvement, but its also about control and that’s something that small businesses don’t want to give up. I.E. we’ll to it cheap and simple in-house rather than risk bringing in an outsider to possibly do it right. That trust stage in the sales process is huge. Its more than just the sale of the work, its about your client exposing a vulnerable side for you to fix.

I’d also argue that the person or developer is more important than the platform. I do a lot of SQL server VB/Access work and a good bit of my client base comes from those that started with Access because its an app that lets “mere mortals do some complex things with a database”, but eventually the company, data set, or business logic outpaces their ability. A well written Access front-end can handle millions of records and some serious business logic. It can also seriously suck when written poorly.

-Bernie