Archive for February, 2009

On Pricing Your Services

Friday, February 27th, 2009

This is a post sparked by an article over at Blogsessive about cheap custom design services. It’s an interesting read with some food for thought for those of us who can’t design our own websites, but mostly this is in reply to one minuscule part of the post: pricing.

He says there is no such thing as a bargain when dealing with professional design services. I disagree.

If you take a look at MNPHoppal’s pricing scheme, for example, we do a base of $250 for a website, with copywriting, logo design, link building, and SEO costing more. A typical static-content, 10-page website with some information about the company and a sales pitch would run about $500.

I can afford to live off of this type of income because (a) I get more clients due to my bargain prices (there are more people attracted by cheap than there are put off by it) and (b) our living expenses are $450 and food. Thus, three clients a month will more than pay our living expenses, and it only takes a couple days to put together a static website like that (not including the back-and-forth of “Do you like it?”).

This is not to say an all-in-one, all-inclusive charge is a good way to do business. On the contrary, MNP Hoppal uses a sliding scale which adjusts based on the amount of work involved or how many of my skills it takes. For example, if I have a difficult client which requires a lot of customization of a pre-packaged CMS like Drupal, custom logo design in a particular format, and much back-and-forth of “do you like this?” “No,” then I’ll obviously charge them much more than the $250 base price.

Another argument against low prices is that you’re selling yourself short.

However, I tend to err on the side of lower prices, as I feel like I’m ripping off people when I overcharge for my services, as most of the work involved I learned how to do two weeks into learning PHP. Mind you the debugging skills have taken years to polish and the eye for design can only be honed through hours upon hours of scrutinizing other peoples’ websites.

Learning PHP: From Scratch vs. Frameworks

Friday, February 13th, 2009

Right now, many people are looking to create dynamic websites based heavily on databases, user input, and content management. One of a few ways to go about this task is to use PHP. PHP, both functional and object-oriented, is a great language for this due to easy integration with MySQL databases, simple syntax, and the abundance of help available.

For those learning PHP, however, there is a choice to be made: Should one go about learning it from scratch, or should one learn to use a framework instead?

There are many pros and cons to each method of learning. Let’s look at them.

From Scratch

First, the pros:

  • Good way to truly get a grasp on what is happening “under the hood”
  • Gives complete control over operations to programmer
  • Learn to truly program by solving simple problems yourself before getting into complex situations

Now, the cons:

  • Takes a lot of time
  • Repeat a lot of already-written code
  • Can be frustrating when simple things don’t work

Learning PHP from scratch is good because it really teaches a coder the bare bones, skeletal intricacies of a language (this doesn’t just apply to PHP). You will run into problems – minor and major – and solving small issues on your own is a great way to prepare yourself for the major glitches and logic flaws that will come up later in your career.

Learning PHP from scratch is ideally suited to a person who plans to continue a career in software development, but can be a huge investment for a small payout to a person who only plans to write one or two websites.

Frameworks

The pros:

  • Much faster and simpler than learning from scratch
  • Most basic coding is readily available

And the cons:

  • Limited amount of support available
  • Can run into major issues later without proper preparation
  • Doesn’t teach the basics of the language
  • Can be overly complex for simple tasks

Learning a framework is a great step in a person’s career, but for the beginner who plans to get into PHP seriously, it’s probably not the best solution. You see, using a framework is best suited for somebody who already knows the details about a language and simply needs a faster turnaround for websites. However, CakePHP and Zend are not necessarily suited to the novice developer, as they tend to be a bit too complex for simple problems.

Either way you go about learning PHP, as long as there is plenty of support available and you have a lot of patience, all problems can be overcome. I encourage learning from scratch, but frameworks can also be difficult to pick up if you don’t begin using them early on. I have personally run into this problem.