This is a personal viewpoint. It is not investment advice, not a recommendation, and not a report of results.
I came to markets with an engineer's habit. A system is not understood when I can describe the happy path. It is understood when I can say how it fails, how large the failure can be, and what I do then. That applies to software and to a position.
In a product, risk is a bad input, a missing permission, a step that cannot be undone. In a trade, risk is the payoff when the view is wrong, late, or right in a way that does not pay. Win rate is a weak summary in both places. A process can succeed often and still be badly designed if the failure is unbounded or unexamined.
I want the loss defined before I am impressed by the gain. A limit written down is different from a plan to pay attention. A backtest is a question about assumptions, not a trophy. I am building trading systems and algorithmic research for Treasure Capital (opens in a new tab), and I use Own Research for analytics and simulation. I am not publishing the rules or a result.
The same sentence covers both kinds of work. If I only describe the system when it works, I do not understand it yet.