To prevent the very same mistakes I see online marketers making over and over once again, there are a few things you need to understand before you hire that eLance, Scriptlance, or RentACoder software application designer.
Law 1: Your software needs to be created in small actions.
It’s more expensive that way, however a minimum of you can get your version 1.0 out with the basic features. Once you have that base simply pay the programmer on a case-by-case basis depending upon which SMALL function you want to include.
Get your version 1.0 working, totally error-free, tested, and SELLING with the site live before adding features for version 1.1, 1.2, 2.0, and so on. When you proceed to these newer variations ensure it is all mistake complimentary and selling on your website before continuing.
After the initial variation has been composed you will know exactly what you’re paying for.
Keeping it easy allows you to be very specific about what you desire your script to do without overwhelming the programmer with details.
Small steps also suggest any modifications to your software application project will take place fairly rapidly. If they don’t, you can ditch an undependable programmer without losing months of time.
Law 2: Programming will cost you cash.
From time to time some man I used to do programs for however haven’t had time for in a while informs me about a developer in India, or Russia or some other place who invested a day writing a script and everything cost him a grand total of … 6 dollars.
Then I take a look at the script and it appears like about $6 worth of work to me.
There is no reason to go ultra-cheap on the cash you put into producing your software. Your only expense is the cost of having it established, everything after that is pure profit.
A (print) book publisher will pay an ex-President countless dollars for a ghostwriter to produce an autobiography, due to the fact that as soon as the real text is composed, the publishing company can start manufacturing books for a dollar or more and offer it at $29.95. It’s the very same concept here, most of the expenditures will come now instead of later.
Law 3: Most developers understand “diddly” about marketing.
Sorry. It’s simply a fact. The majority of these people have been developing the precise same script over and over … generally bad ones like a traffic exchange or dating script. Be client and explain split-testing, double opt-in or whatever needs to be explained and if the developer can’t comprehend those concepts simply opt for someone else.
Law 4: The code needs to be well documented (remarks in the code), that method you can come back to it.
If you discover a problem with your program a year from now, even the initial developer will be unaware UNLESS there are remarks within the source code explaining very plainly what every function and block of code is expected to do.
Law 5: Your developers need to speak decent English.
Not that Indian dialect of English either, real English. This is certainly not the time to lose anything in translation. Plus if everything’s in another language how can you potentially change to another programmer if you require to later?
Law 6: You will often capture stuff the programmer didn’t.
There is a genuine thing called Programmer’s Immunity. Essentially it says that the “typical” user will have more computer issues than a programmer, due to the fact that a programmer is utilized to making things work (work-arounds). This implies every as soon as in a while, your programmer will subconsciously miss out on bugs that are glaringly apparent to you.
Don’t get upset, just let the developer learn about the issue, and what exact actions need to be carried out to recreate the error.
You will need to check the program yourself. You will likewise need to send the program out to beta testers to make sure others can use the software application without issues AND you need to discover if the program can be used without instructions by somebody who has actually never seen the software application prior to.
The installation instructions require to be worded as simply as possible, without a great deal of legalese or technical terms.
Law 7: (For web-based apps) use HTML design templates.
The majority of programmers I’ve seen are shitty designers. In this manner you can alter the way the script appears and even hire out a professional designer.
You need the programmer to utilize an extremely simple design template system.
In PHP this would be something like FastTemplate, where there is a simple “tag” in the HTML like or %firstName%. There are other bad design template scripts for PHP such as Smarty, which draws due to the fact that it embeds PHP code in the templates. You ‘d have the same issue utilizing regular PHP. The entire point of having design templates are to separate the code from the appearance.
Law 8: If you can afford it, get a code inspector.
This is a developer you know to be great however maybe too costly to compose the entire script, who can take a glance at the code after every release to make sure the program is “good enough” … not perfect but sellable.
Your inspector is just searching for HUGE problems in the program or script like the usage of gotos or globals, or possibly your freelancer is using a database but hasn’t normalized it correctly or forgot to add indeces where they are required to keep the database quick.
Law 9: Stay away from GPL, open source, and re-used code AT ALL COSTS!
This is a big deal. Make it clear you do not desire code reused from other scripts. Certainly if the coder uses parts of another person’s script you are in offense of copyright laws.
On the other hand there is complimentary software out there called GPL (GNU Public License) which is free to use however only if you make the source code of your entire software available also. That is definitely NOT what you desire.
Law 10: Your software will break in time.
This is just a reality. If you’re having some desktop software application produced in C++ the code might not compile properly on a various compiler in a few years. Some software application composed in variation 1.0 of Microsoft’s. NET runtime already breaks when you run it on computers with version 1.1 (argh!).
Do not even get me began about PHP. When PHP launches brand-new variations the new methods of doing things are not always in reverse suitable. Depending on which modules or security patches an offered web host has installed, specific things may not work too. That’s life.