팀의 개발 노트: 백테스트 정확도, 주문 체결, 수치 정밀도, 그리고 자동 매매 플랫폼 이면의 트레이드오프. 개발자를 위해 작성했습니다.
The engineering lessons from this series in one place: quiet failures, simulators that flatter you, precision as a domain, and constraints that delete work instead of adding it.
Three exchanges, three incompatible minimum-order rules, and a bug caused by inventing a rule that one of them never had. What precision work actually looks like in production.
Why we refuse API keys that carry withdrawal permission instead of just promising not to use it, and what that constraint removes from the system.
Two React traps that only hurt when the field holds money: the native number-input wheel footgun, and a portalled Radix popover that swallows every keystroke inside a dialog.
Three ways a backtest quietly reports a better result than reality: reading a higher-timeframe indicator before its bar closed, letting an unfinished candle repaint a signal, and silently skipping conditions it cannot replay.
Three engineering problems that turned out harder than expected: exchanges that fail quietly, floating point in order sizing, and designing around never holding user funds.
배운 것을 실전에 적용하세요.
