Urgent.News

What's breaking now, across thousands of outlets.

Tech

ATR Stops Without Magic Numbers: Why 2.5 ATR14 Is a Convention, Not a Law

Stop = Price ± (k × ATR14) fits in one line. The problem was never the formula — it is choosing k , and knowing what the number does and does not mean. Educational content: methodology only, no signals, no return claims. By **Mahdi Goodarzi * ( g.dev/mahdigoodarzi ), Gueta Quant — Spanish guide: gestión de riesgo con ATR .* 1. ATR is a range measure, not a probability This distinction gets lost…

The article explains that the 2.5 ATR14 stop loss is a convention, not a rule, and it should be calibrated per instrument by examining the distribution of stop-out distances. The article also discusses the trade-off of choosing a multiplier (k) and the importance of inverse sizing when it comes to position sizing. Static stops are simpler and allow for planning size in advance, while trailing stops reduce give-back but require defining a rule before the trade.

The article also emphasizes the need to check if the volatility regime matches the sample used for calibration and if stop-outs are dominated by noise rather than thesis invalidation.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Autopsy #02: Anatomy of a Memory Leak on an 8-Hour Dashboard

Incident Report A routine PR added an auto-resizing MutationObserver to the NOC telemetry table widget so column widths adjusted when live alerts streamed in.

  • 8-hour dashboard crashes due to memory leak
  • Auto-resizing MutationObserver causes leak
  • Fix requires single-token teardown with AbortController

Autopsy #03: Why One Click Triggers 14 Re-Renders and a Layout Shift

Incident Report A design-system polish PR added a compact-density toggle to the catalog filter bar, updating --row-density on :root and equalizing row heights in useLayoutEffect .

  • Compact-density toggle introduced, aimed to improve UX
  • Performance issues on production catalog pages with 2,400 DOM nodes
  • 14 re-renders and layout shifts triggered per click

More from Tuesday 17 November →