Bridging The Gap Between Traders And Programmers
EasyLanguageProgrammer.org is trying to bridge the gap between traders seeking help with custom programming and the programmers.
This does not only go for Multicharts or Tradestation, but for Ninjatrader, Metatrader, eSignal and every other trading platform.
In fact what you will read within these pages is true for every programming job regardless of the language used.
Depending on your degree of programming knowledge you might reach a limit (obstacle, boundary), need help or simply
want to outsource some of the coding. Once you are clear about hiring a custom programmer, the difficult task is to hire the right one.
From experience I know that many customers tend to focus only on the monetary aspect of a project. While this certainly is a point worth noting,
it shouldn't be the only one. Probably not even the most important one to focus on. Don't get me wrong, I am not saying the most expensive programmer
is the best choice. The same logic applies here, too.
One might argue that if you want program A and two programmers can deliver it: Why not go with the cheaper one? They will be same program A. Why pay more?
When comparing two goods that are exactly alike, I would tend to agree with you. However two programmers working with the same specifications will probably
not arrive at the exact same outcome. Both programs will accomplish the same task, but there can be differences ranging from very subtle to quite noticeable.
Let me give you an example.
One programmer properly documented the source code and the other did not. Why should that even bother you if you can't program? This could become a problem
in case you want to switch to a different programmer in the future. If he (or she) should make additions or changes to the original code for you, it will take
longer for him to understand the source code. The additional time will most definitely be something you have to pay for. Maybe you know the programming language
to some extend and are able to do minor changes yourself. Then you will appreciate the time saving you experience when you are able to find your way around right away.
Don't believe uncommented source code is an exception. I have seen plenty of examples where the client paid top dollars and the code was not documented at all.
Proper documented and commented source code is almost the exception rather than the norm.
So how should the code look then? In my opinion the code should tell what is done and the comments say why it's done. If a piece of code says something clearly,
there is no need to add extensive comments for that piece. This results in code that is both easy to read and understand. Variables should have names that reflect
their purpose for example. The comments are clear and not excessive. In general I would say everything that helps understanding the code, its purpose and readability
is useful. A novel for each line of code definitely is not.