Thank you, mrtwo, you have been really helpful. I am learning wonderful stuff here.
Quote from mrtwo:
If money isnt a constraint and you can afford hiring a few seasoned developers, I would recommend that you go Unix, that is for sure.
Make sure at least half of your development team has experience with automated trading and do the best as you can to keep it simple: overdesign will kill your performance even when working with high-caliber hardware.
Thanks. I am not there yet but I will remember this advice.
Combined with your earlier advice of making good, educated use of threads, I guess the best practice would be putting a lot of thoughts into coming up with a simple and effective design?
Now, porting from Windows to Unix isnt fun. Basically, to benefit of the Windows platform, you have to embrace it completely. Every time saving feature you use will make your code harder to port and if you just code at the 'lower common denominador' while on Windows, you might as well just give it up and stick to Unix, because it isnt worth it, at least most of times.
I think you are right, I should just stick to the good old Unix. Does any body know any good GUI sulotion for Unix development? Of course, one can always give up the luxury of GUI.
Craig, do you know any links to IDE for Unix or Java?
I would pick a platform, either one of the two and just stick to it. Cross platform development adds more risk to your project than it makes it 'safer'. As a rule, you only code with more than one platform in mind when you are required to.
Yes, that is the theory. When you are aware which OS features are safe to use on both platforms, you can code a "OS abstraction layer" to hide the specific implementations from your aplication - this way, when the time comes, you will only replace this abstraction layer and your code should, hopefully, work on a different platform
Sounds like that will require deep understanding of all the OS, not having that I thought coding in Java would be a good substitute, with the potential benefit of even porting to Mac OS 64 bit in the future...
But..
The one thing about Java is performance. Not that Java is slow as many people believe, but as any platform-neutral and memory-managed language, it demands that you write your code 'in the right way' to benefit the most from it.
I would not implement neural nets on Java or C# though.
Ooch.
I hope that helps
Peace,
MrTwo
It certainly is very helpful.
I am thinking of implementing the first very simple trading algo---just a trailing stop to watch over positions while I am away. Would Tradestation suffice for that? I read that TS can only input data to the hour? that wouldn't help real-time risk management too much.
Would anyone care to share their experience using auto algo to risk manage exit points, limit versus market orders? To what extent can you leave it to auto algo to 'position watch' so that you can be away for a few days?
Thanks for all the helpful information that you guys are contributing, I really appreciate it.