惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
Threatpost
The Hacker News
The Hacker News
AWS News Blog
AWS News Blog
Spread Privacy
Spread Privacy
T
Tenable Blog
C
CERT Recently Published Vulnerability Notes
Cisco Talos Blog
Cisco Talos Blog
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
S
Securelist
P
Privacy & Cybersecurity Law Blog
Know Your Adversary
Know Your Adversary
T
The Exploit Database - CXSecurity.com
Latest news
Latest news
D
Darknet – Hacking Tools, Hacker News & Cyber Security
I
Intezer
F
Fortinet All Blogs
Engineering at Meta
Engineering at Meta
Simon Willison's Weblog
Simon Willison's Weblog
The Register - Security
The Register - Security
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
L
Lohrmann on Cybersecurity
C
Cyber Attacks, Cyber Crime and Cyber Security
Microsoft Azure Blog
Microsoft Azure Blog
P
Proofpoint News Feed
H
Help Net Security
T
Threat Research - Cisco Blogs
D
DataBreaches.Net
S
Schneier on Security
Cyberwarzone
Cyberwarzone
Google DeepMind News
Google DeepMind News
P
Privacy International News Feed
S
Secure Thoughts
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Recorded Future
Recorded Future
C
Cybersecurity and Infrastructure Security Agency CISA
MyScale Blog
MyScale Blog
M
MIT News - Artificial intelligence
Stack Overflow Blog
Stack Overflow Blog
IT之家
IT之家
人人都是产品经理
人人都是产品经理
NISL@THU
NISL@THU
博客园 - Franky
T
Tor Project blog
G
GRAHAM CLULEY
博客园 - 【当耐特】
Jina AI
Jina AI
Security Archives - TechRepublic
Security Archives - TechRepublic
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
A
About on SuperTechFans
Hacker News - Newest:
Hacker News - Newest: "LLM"

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
The Position Sizing Math That Keeps You in the Game
akash · 2026-05-19 · via DEV Community

Most retail traders who blow up did not blow up because their analysis was bad. They blew up because their position size was wrong for their conviction, their account, or their stop. The math to fix this is not complicated, and almost nobody who needs it has actually run it on their own account.

This is a short, practical walkthrough of the calculations that matter, written for traders who want to understand the inputs rather than just plug numbers into a calculator.

The single most important equation

For any trade, the dollar risk is:

dollar_risk = position_size × |entry_price - stop_price|

Enter fullscreen mode Exit fullscreen mode

A long of 0.1 BTC at $61,000 with a stop at $59,500 carries a dollar risk of 0.1 × $1,500 = $150. That is the amount lost if the stop hits cleanly. (In practice it can be worse, because stops slip in fast markets, but $150 is the baseline.)

The mistake almost every beginner makes is calculating position size from the asset price ("I want to buy 0.1 BTC") instead of from the dollar risk ("I want to lose at most $150 if I am wrong"). Reversing this changes everything.

The 1% rule, properly stated

The most-quoted rule in trading is "risk 1% per trade." This is good advice that is usually applied incorrectly. The full statement is:

Risk no more than 1% of total account equity on any single trade, where "risk" is the dollar distance between entry and stop, not the notional position size.

A trader with a $10,000 account using 1% sizing has $100 of risk per trade. If the stop is 2% below entry, the position can be $5,000 ($100 / 0.02). If the stop is 0.5% below entry, the position can be $20,000. Same risk, very different position sizes, dictated by where the stop is.

This is why traders who pre-define their stop end up with rational sizing automatically, and traders who pick a position size first and then "decide where to stop out later" end up with risk that varies wildly trade to trade.

Why 1% and not 2 or 5

The math behind the 1% number is about surviving losing streaks. Consider the probability of a streak of N consecutive losses:

Win rate Probability of 10 losses in a row
50% 0.098% (1 in 1,024)
60% 0.010% (1 in 9,766)
40% 0.605% (1 in 165)

Even at a 60% win rate, a 10-loss streak happens roughly once every 10,000 trades. At a 40% win rate, it happens once every 165. At 200 trades a year, that is more than once a year.

A 10-loss streak at 1% risk per trade is a 9.6% drawdown (compounding works in the trader's favor on the way down too). At 2% risk per trade, the same streak is an 18.3% drawdown. At 5% per trade, it is 40.1%. The 5% trader is one ordinary bad streak away from being psychologically destroyed; the 1% trader can shrug it off and keep going.

The 1% number is not magic. It is the largest size at which a normal losing streak does not derail traders emotionally or financially.

Adjusting for conviction (carefully)

Many traders use variable sizing: more on high-conviction setups, less on low-conviction ones. This is fine in principle and dangerous in practice.

The danger is that "conviction" is mostly post-hoc rationalization. Almost every trade feels high-conviction at the moment it is taken. Traders who scale up "when they are sure" usually end up scaling up randomly, just before the inevitable losing streak that happens at exactly the size that hurts the most.

For variable sizing to work, three things are needed:

  1. A written rubric for what makes a trade A-tier vs B-tier vs C-tier. Written before the trade. Not adjustable based on how the trader feels.
  2. A hard cap on the maximum size, no matter how high-conviction. Many disciplined discretionary traders cap at 2x their baseline.
  3. A retrospective check every month: did A-tier trades actually outperform B-tier trades? If not, the rubric is wrong and the trader should go back to flat sizing.

Most traders should run flat 1% sizing for at least their first 200 trades. The reason is not that flat sizing is optimal; it is that flat sizing protects against bad self-assessment until there is enough data to prove the rubric works.

The leverage trap

Crypto perpetuals make this all worse by inviting traders to use leverage. Leverage does not change the math above; it just changes which number blows up first.

The right way to think about leverage: it sets the maximum position size collateral can support, but actual position size should still be determined by dollar risk. Using 10x leverage on a $1,000 account does not mean a $10,000 position is appropriate. It means a $10,000 position is possible if the dollar risk calculation says so, and probably the actual position should be much smaller.

The trader who uses leverage to amplify position size beyond what dollar risk would dictate is the trader who gets liquidated, often by a wick that the exchange's liquidation engine catches before any human would have closed the position manually.

Practicing the math

This is the kind of thing that should be drilled on paper before it is done live. A few exercises:

  • Open a paper trading account with $10,000 virtual. Set a hard rule: 1% risk per trade.
  • Take 20 trades. After each, compute the dollar risk before submitting the order and write it in a journal. Refuse any trade where the size cannot fit into 1%.
  • After 20 trades, look at the spread of position sizes. They should vary widely (because stop distances vary), but dollar risk should be near-constant.
  • Then do 20 more trades that intentionally violate the rule, sizing by "what feels right." Compare drawdowns.

Hex37's position-sizer panel computes the dollar risk inline as order parameters are adjusted, which tends to make the discipline stick faster than doing the math separately in a spreadsheet. Any platform that surfaces dollar risk before submission works; the point is the habit, not the tool.

Bottom line

If there is one thing to remember: size trades by dollar risk, not by asset price or by "what feels right." Use 1% of account as the default. Pre-define the stop before entry so the calculation is honest.

This is, by a wide margin, the highest-leverage change a developing trader can make to their results. It also requires zero predictive skill. It is just arithmetic, applied honestly.


Hex37 is a paper trading platform with a built-in position sizer that computes dollar risk inline as order parameters are set. Free $10K virtual balance, realistic execution. hex37.com.