July 19, 2007
Introduction to Trading Systems - Management
Over a period of years you may have designed and tested hundreds of trading ideas, some may have worked a little, some were traded for awhile, and some you chucked in the waste basket. While in the end you have one or two good systems to trade, you have spend thousands of hours in development time with very little to show for it: Hundreds of system ideas are either totally lost or are tucked deep into some database where they can’t be listed by trading idea or trading principle.
This topic discusses how you can manage your research, work, and ideas to create a valuable system development resource.
… under development …
You are invited to contribute to this topic as an author with a post (requires registration) or in the comment field below.
Filed by Herman at 11:16 am under System Management
(No Ratings Yet)
Loading ...
I recently started organizing my systems in various ways where I can get an idea from the file name what this is about.
A functioning system, regardless of origin, but verified by me, is stored in the System folder with some descriptive title, e.g. MACrossplusADX. If the system is a clear trend following system I might name it T_MACrossplusADX. T means Trend, R means Range, C means Comment, F means Filter
A seemingly functioning system, but not verified yet, and not developed by me, is filed with a S_ upfront and stored in a folder of origin (e.g. Bandy, TASC, etc.)
A system under development by me, or abandoned, is put in the the Custom folder.
Snippets of working code are filed under their appropriate folders, i.e. Exits, Auto.
I always try to put lots of descriptions in the code itself, so that I can quickly get up-to-date with what it is about. I always include where I got it from, date, author, url address and maybe some info, e.g. “can’t get it to work at this line, posted a question here about it.”
Hope this helps.