Webdesigner

 : 

MicroVB

My pricing varies based on the task, and what is fair for all parties involved, Generally, I give the client an option between an estimate of hours at an hourly rate, or a flat rate. Bigger projects at flat rate are usually discounted based on their size and reasonable constraints I can be comfortable working within.

When working with a new client, I will ask questions about the project, as well as find out what problem they would like to solve. Fairly often, I find that the client has an idea about an end goal, but is seeking to solve that problem less efficiently than is possible which seems to originate from a lack of expertise in the software field - and that is perfectly okay. After discovering the end problem they wish to resolve, I will try to gather some information about the business model (if I think it is applicable) such as target audience, etc. If there are existing solutions available, I inform the client so they are aware of other existing options which may work for them. While I do enjoy money, my main goal is to ensure that the client is satisfied and the code quality is secure. I prefer to have clients that return because they would like more work done, addons, new/changed features, etc., than to milk them for bug fixes which should always be free.

While I have many certifications, I don't feel those represent my knowledge well as this has been a life long journey. I started writing computer software at the very young age of 4, and for the most part, I haven't stopped, primarily due to an addiction to information. This has enabled me to work at a level beyond any certification can quantify which includes: - easily reading through messy code in most languages - understanding code in any non-abstract language (abstract languages are ASM, Brainfuck, etc) - highly adaptable. I can code with or without frameworks. I don't need a crutch to speed things up. - unbound thought - Most of the "can't be done" projects, I can do or figure out how they can be done if they are possible. I am not bound by the constraints of the "can't" mindset, however if I feel a project is not possible, it likely is not possible at all using current technology - which I am willing to work with the client to figure out a solution limited only by budget.

The types of clients I have worked is very diverse, from assisting with University projects, to Medical, Telecom, Educational, Government, and major brands.

If you are looking for someone in my domain, make sure you find someone who will care enough about your project to give you feedback, even if it means adjusting your perception of how it should be done. You will also want to open up the code. Usually if it consists of thousands of little files, it is badly written and is a sign that it will be expensive for you to make changes if you need to hire someone else to work with it. What you should be looking for, is plain English clear naming of variables, functions, and classes; fluid indentation; and minimal 3rd party library use. Generally, even if you aren't a programmer, the code should be clear enough (and commented well enough) to provide you a general idea of what that piece of codes intent is. Also, if purchasing custom work, ALWAYS get a copy of the source code. This doesn't necessarily mean the developer has to hand over all rights, but you should have at a minimum a license to modify your code if required as this allows you to bring someone else in to make changes if required. Another note, is to beware of hosted solutions as they generally hold you hostage for your data. Make sure whoever the host is, you are in control of both your domain, and can download all your content including any databases. I have seen way too many cases where a client has their database hosted with someone who doesn't given them access to the raw data which in turn can make investing in your business high risk due to you not being in control of your own data.

Some things that would be wise to consider going forward are : 1. Insisting on the pro using a specific language for your project. While some projects do require use of a specific language, most, do not require this. Restricting to a specific language reduces the number of people who are qualified to complete your project, as well as adds constraints on the creative process. Generally speaking, the only case where a specific language is required, is if existing code is to be modified or extended. Barring that, think carefully before you lock your developer down from the freedom to work with what in their experience may be a better tool for the job. 2. Question the quality. If you find a developer that claims they will do your project for this really low sum of money, consider what you are paying for. While the end result may visually look like (or close to) the end result you seek, the code that drives it is usually unstable and contains a lot of 3rd party libraries and/or superfluous code . If you are simply looking for a cheap prototype, there are developers that are skilled specifically n prototyping that you are better off paying the extra bit to, and have the peace of mind that it isn't going to barf when you present it to investors, your clients, or other. Good developers cost money, and those that do it for the love of the craft will try to work with you understanding that you may not have unlimited funds.