2005issue C131-14
Reader surveys as system evaluation checklists
A readers-choice ballot can serve as a map of platform categories. Editorial reading: score tools by whether they make entry, exit, and standing aside testable as one mechanical procedure, not by how often peers named them.
- Treat a readers-choice ballot as a map of evaluation categories, not as a vote on fitness for a mechanical trading system.
- Compare platforms by whether they let you test entry, exit, and abstention as one fixed procedure.
- Keep each product in its primary-purpose category, and use price-band splits only to keep the comparison field even.
- Encode data-feed delay and direct-access routing as execution constraints, because they change fill, cost, and control assumptions.
A ballot used as a design review
The ballot was assembled from an editor list plus write-in space, then completed online so readers could name products they found most useful by category. That write-in design starts from a published set and still accepts unlisted products, which reminds evaluators that the listed set is incomplete.
Editorial reading: use the ballot only as a map of evaluation categories. Rank a tool by how completely it lets you test entry, exit, and standing aside as one mechanical procedure, not by how often peers named it.
Primary purpose and even comparisons
Products were placed by primary purpose, with an explicit warning that omission from a list does not mean a product lacks features relevant to that list. A primary-purpose category keeps a product in one comparison set even when it has features that could fit other sets.
Some categories were split by cost so comparisons could be made on a more even field, including standalone analytical software bands of $500 and above, $200 to $499, and $0 to $199.
The presentation states that winners are usually dominant names in a niche, and that traders with special needs should still review lesser-known products before deciding. Editorial view: evaluation compares candidate platforms by whether they make the whole procedure testable, not by brand dominance or survey rank.
The published category map
The published category map included data feeds, brokerages, institutional and professional platforms, priced analytical software, plug-ins, artificial-intelligence software, portfolio and options tools, futures, options, and stock trading systems, training venues, and technical-analysis websites.
Stock brokerages in the ballot mixed long-standing full-service names with discount and newer firms, so the category itself is not a single execution model.
Data classes and routing constraints
Continuous-feed data was treated as one evaluation class covering both instantaneous and 15-to-30-minute delayed streams, separate from on-demand end-of-day downloads that the user initiates.
Direct-access stock routing was described as sending orders through electronic communications networks or small-order execution systems, often with lower cost on high-volume trades and more control over order flow in the absence of market makers. Direct-access futures routing was described as reaching exchange matching engines or in-pit floor systems, generally on a first-in, first-out fill basis.
Editorial view: direct-access routing changes fill, cost, and control assumptions a mechanical trading system must encode. Those constraints sit beside rule inputs and market state when the procedure issues a signal to enter, exit, or stand aside for a defined holding period.
What to score on each platform
Editorial checklist: for each category on the map, ask whether the product lets you run entry rules, exit rules, and abstention rules as one testable procedure. Score data delay, order routing, and brokerage model as execution constraints, not as popularity marks.
The presentation already says traders with special needs should review lesser-known products. Editorial addition: keep write-in and lesser-known tools in the same scoring frame as dominant names.
All readings on this track · 22 readings
- 1985Treat a shared mechanical printout as a public script
- 1988Pessimistic margin ranking for mechanical systems
- 1991From a differenced-average sketch to coded rules
- 2003Commodity enthusiasm is not a complete system
- 2005Reader surveys as system evaluation checklists
- 2008Critiquing unchanged mechanical signals in evolving markets
- 2010Read a mechanical trading system catalog as a specification checklist
- 2011Specify mechanical system signals as one testable procedure
- 2012Treat a packaged mechanical system as one inspectable procedure
- 2013Mechanical trading systems as complete signal procedures
- 2013Testable cycle rules as one procedure
- 2014Evaluate mechanical trading systems as one procedure
- 2015Mechanical trading systems as one testable procedure
- 2016Evaluating mechanical trading systems as testable procedures
- 2016Reading a systems catalog as one mechanical procedure
- 2018Mechanical systems as testable signal procedures
- 2019Treat mechanical system listings as specification audits
- 2019Match the automation stack to mechanical system constraints
- 2019Bar size as a mechanical system construction constraint
- 2020Interrogating mechanical system listings as one procedure
- 2020Mechanical systems still need emotion rules
- 2020Comfort, not theory, keeps mechanical rules in use