|
PureBytes Links
Trading Reference Links
|
There is a useful lesson we can all learn from the pics Bob posted. When
I'm developing a system, I always write it as one or more indicators
first. I like to see exactly what the calcs are doing. I'll spend hours
staring at charts before I write any system code. If something doesn't
look right I start trying to find out why. Once I'm satisfied with the
visual presentation of the indicator(s), I'll convert it to a system to
see if it can make some money.
A second important lesson is to double-check the code for any EL
functions supplied by Omega. I use very few of the built-in functions.
My own versions are either more accurate or they execute faster. I'm
totally self-taught as a programmer and even I can see the major flaws
in the built-in stuff. I look at Omega's function library as code
examples, not something you would actually use for trading. Once you get
the mindset that you have to code everything yourself if you want it to
work right, life gets less stressful.
Pierre is right that you can work around almost any problem. Where he
has his head in the sand is pretending that the problems are unimportant
and the average user need not concern himself with them. But we all know
Pierre's biases - think used car salesman - so those of us who have been
around for a while take anything he says with a huge grain of salt. You
know he will never say or admit anything that is going to hurt sales.
Also, he has never been wrong about anything.... just "right in a
different way." :-)
Thanks for the valuable insights into the inner workings of TS, Bob.
--
Dennis
|