---
title: "Comment by Arnold Holm on \"Every 'Pro' Risk Technique I Tested That Did Nothing\" | Hashnode"
description: "For the drawdown brakes, I would separate the objective of reducing historical losses from enforcing a rule boundary. A challenge guard can be useful because it"
url: "https://hashnode.com/posts/every-pro-risk-technique-i-tested-that-did-nothing/6a55bde038baf797529b7edb/comment/6abf8fed630bbc28eddd6d2d"
---

[Discussion](https://hashnode.com/posts/every-pro-risk-technique-i-tested-that-did-nothing/6a55bde038baf797529b7edb)

Comment [Every 'Pro' Risk Technique I Tested That Did Nothing](https://hashnode.com/posts/every-pro-risk-technique-i-tested-that-did-nothing/6a55bde038baf797529b7edb)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 2](https://hashnode.com/posts/every-pro-risk-technique-i-tested-that-did-nothing/6a55bde038baf797529b7edb/comment/6abf8fed630bbc28eddd6d2d)

For the drawdown brakes, I would separate the objective of reducing historical losses from enforcing a rule boundary. A challenge guard can be useful because it blocks an entry after a specified loss threshold, even if it does not improve the strategy result. A regression fixture should therefore check the threshold, reset time and restart behavior against the frozen rule, rather than judge the guard only by the backtest return.
