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

推荐订阅源

Security Latest
Security Latest
T
The Exploit Database - CXSecurity.com
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
T
Tor Project blog
Help Net Security
Help Net Security
PCI Perspectives
PCI Perspectives
T
The Blog of Author Tim Ferriss
H
Heimdal Security Blog
The Register - Security
The Register - Security
Schneier on Security
Schneier on Security
宝玉的分享
宝玉的分享
Google DeepMind News
Google DeepMind News
人人都是产品经理
人人都是产品经理
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
C
CERT Recently Published Vulnerability Notes
L
LangChain Blog
Security Archives - TechRepublic
Security Archives - TechRepublic
MongoDB | Blog
MongoDB | Blog
美团技术团队
S
Security @ Cisco Blogs
Cloudbric
Cloudbric
Cisco Talos Blog
Cisco Talos Blog
C
Cybersecurity and Infrastructure Security Agency CISA
月光博客
月光博客
B
Blog RSS Feed
Cyberwarzone
Cyberwarzone
U
Unit 42
AWS News Blog
AWS News Blog
F
Fortinet All Blogs
L
LINUX DO - 最新话题
GbyAI
GbyAI
T
Threat Research - Cisco Blogs
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
A
About on SuperTechFans
Hugging Face - Blog
Hugging Face - Blog
Attack and Defense Labs
Attack and Defense Labs
Engineering at Meta
Engineering at Meta
MyScale Blog
MyScale Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
V2EX - 技术
V2EX - 技术
Y
Y Combinator Blog
T
Tailwind CSS Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
Recorded Future
Recorded Future
TaoSecurity Blog
TaoSecurity Blog
博客园_首页
C
CXSECURITY Database RSS Feed - CXSecurity.com
M
MIT News - Artificial intelligence
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
H
Hacker News: Front Page

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
Visible Wins, Quiet Losses: The Traps We Mistake for Truth
Self-Correcting Systems · 2026-06-27 · via DEV Community

A friend asked me to build him something practical.

He follows a paid trading group. Private Discord, trade alerts, green screenshots, people posting big percentage moves. He wanted an agent that could watch those calls and eventually trade for him, so he would not have to sit in front of the screen all day trying to catch every move himself.

That sounds simple until you ask the only question that matters:

Is the record actually good enough to risk money on?

I did not want to build him a money printer. I do not believe in those. I wanted to build the thing I wish more people had before they put cash behind someone else's confidence: a gate that refuses to confuse a receipt with an outcome.

So the first version did not trade. It audited.

It took the calls I could capture, reconstructed each signal chain, separated entries from updates from exits, and asked a colder question than the Discord ever asks:

What happened after the green screenshot?

Receipts are not outcomes

A green screenshot proves a trade existed at a moment.

It does not prove the trade ended well.

An option up 50 percent at 10:30am is a receipt. A trim post with a large open profit is a receipt. A chart with a confident caption is a receipt. None of those are the same thing as realized profit.

The outcome is where the trade actually closed, or where it expired, or where the stop should have forced it dead. That is the part that touches the account.

This distinction sounds obvious when written plainly, but it is exactly where trading records get distorted. People remember the visible peaks. They share the visible peaks. The Discord fills with the visible peaks. Then a trade goes quiet, and quiet feels neutral.

Quiet is not neutral.

Sometimes quiet is where the loss is hiding.

What I actually checked

I want to be precise because the precision is the point.

This was not a full audit of the entire service. It was a small, manually captured slice of calls from one paid trading Discord, pulled from screenshots and exported rows I had access to. That matters. A slice is not the whole record, and I am not going to pretend otherwise.

Inside that slice, I looked only at trades the agent could treat as agent-takeable enough to track: clear enough to identify the instrument, direction, expiry, and entry chain.

The first survivorship check focused on expired option positions that had no captured close message. There were 12 of those in the agent-takeable slice.

When I settled them against real underlying prices at expiry, 11 had expired worthless.

That is the moment the whole piece changed for me.

Some of those same trades had visible green updates before they disappeared. Seven had earlier green or update posts that would have looked encouraging if you stopped reading at the screenshot. One was last shown up around 50 percent. Another was last shown up about a third. Another had a trim/update that looked like a large open profit.

Then the chain went quiet.

When the agent finished the chain, the ending for most of those quiet trades was not green. It was zero.

The visible record was not fake. It was incomplete.

This is the fairest way I can say it:

I am not claiming the people posting those screenshots were lying. The green moments may have been real when they were posted. The screenshots may have been honest receipts of a temporary state.

The problem is more dangerous because it does not require anyone to fake anything.

If the win gets posted and the loss gets silence, the visible record becomes flattering by construction. Not necessarily because someone sat down and decided to deceive people. Sometimes the room just naturally rewards wins, ignores duds, and moves on. But the effect is the same for the person deciding whether to follow the next call:

They are judging a strategy from the part of the record that survived being shown.

That is survivorship bias in its most practical form. Not a textbook definition. A real account-risk problem.

The agent's job was not to decide whether the group was good or bad. It was to ask whether the shown record was enough evidence to act on.

On the captured slice I could verify, the answer was no.

Holding my own work to the same standard

This is the section I would not trust the article without.

The sample was small. It was captured by hand. It was not a complete, randomized, unbiased scrape of every trade that source ever posted. Because of that, I cannot honestly say, "this service loses money."

I also cannot honestly say, "this trader has no edge."

Those claims would require a complete record, consistent sizing, option price history, trim quantities, stop execution, and a clean definition of what counted before the outcome was known.

I do not have all of that.

What I do have is narrower and stronger:

In the captured agent-takeable slice, the visible record was not enough to trust. Trades that looked green midstream could and did expire worthless. The missing close posts mattered. When I forced the agent to settle the quiet trades instead of ignoring them, the story changed.

The blind-follow snapshot for the captured agent-takeable slice was ugly: 16 scored or settled trades, 3 wins, 13 losses, and a sharply negative result under equal-position, held-to-expiry accounting.

That held-to-expiry assumption matters. It is a rough blind-follow check, not a full trading simulator. It asks, "what happens if the quiet trades are not rescued by a stop or a later close post?" It does not include perfect option-price fills, exact position sizing, or every trim.

It is a warning label.

It says: if you only follow the visible trail, you are not measuring the same thing your money experiences.

That is the cost-bearer problem in plain form. The screenshot does not bear the cost. The Discord room does not bear the cost. The person whose account takes the trade bears it. So the record has to be judged from the account's side, not from the room's side.

That is the honest claim. Not "they lose." Not "I proved the whole service is bad." Just this:

The record I could inspect was incomplete in the exact direction that makes a trading source look safer than it is.

Then I made the agent stricter

The next question was obvious:

What if the agent did not blind-follow? What if it only took the clean calls?

So I made the policy stricter. A trade was not live-eligible unless it had the basic structure a machine could enforce:

  • a clear entry
  • a machine-checkable numeric stop
  • a machine-checkable numeric target
  • enough price data to test what happened first

That strict pass reviewed 40 positions.

Only 6 were clean enough for the agent to consider live-eligible.

The other 34 were refused or left paper-only.

Stage Count Result
Captured positions reviewed 40 Raw signal chains from the slice
Refused / paper-only 34 Missing stops, vague exits, unmeasurable setups, or not agent-takeable
Live-eligible 6 Clean enough to test under strict stop-and-target rules

That refusal is not a side detail. It is the product.

Most retail trading tools are built to help you act. This one was most useful when it refused. If a call has no enforceable stop, the agent should not turn it into an order. If the exit is vague, the agent should not pretend it can manage risk. If the setup cannot be measured, it should not be trusted with money.

On the 6 strict live-eligible trades, the outcome still did not show an obvious edge: 2 hit target first, 4 hit stop first. That is not an exact profitability model either, because exact option P/L needs option-price history and sizing. But it was enough to answer the practical question:

The captured slice did not give the agent a clean, obvious money-making lane.

It gave the agent a reason to protect my friend.

The agent is not the edge

This was the hardest part to accept because the original dream was simple: build an agent that trades for him and helps him make money.

I still want that.

But the agent cannot manufacture edge out of a source that has not earned trust yet. Discipline can reduce damage. It can enforce stops. It can size risk. It can refuse unclear trades. It can keep an honest scoreboard so the human gets better over time.

But if the underlying calls in front of it do not have positive expectancy, automation only makes the bad process faster.

That is why the first real agent is not a reckless auto-trader. It is an operator and coach:

  • It reads a call.
  • It asks whether the call has enough structure to act on.
  • It refuses missing stops, vague exits, spreads it cannot model, or post-hoc winner posts.
  • It proposes only review-eligible trades.
  • It tracks every trade from entry to close.
  • It builds the record the Discord does not give you.

If that record eventually shows a real edge, then live trading can be earned in small size.

If it does not, the agent still did its job. It saved the trader from funding a story.

The bigger lesson

This is a small story about trading, but it is not only about trading.

Whoever controls the visible record controls what looks true.

If all you see are the wins, the system looks better than it is. If the failures never become part of the shared record, the audience is not evaluating reality. They are evaluating a highlight reel.

The answer is not cynicism. Cynicism just says everything is fake and stops thinking.

The answer is better accounting.

Track the chain from start to finish. Separate receipts from outcomes. Mark what is open. Mark what expired. Mark what was refused. Mark what was too vague to trust. And when your own sample is limited, say that too.

That last part matters most.

If I expose someone else's survivorship bias while hiding my own sample limits, I have learned nothing. I would just be building a cleaner-looking version of the same distortion.

The visible seam is part of the receipt. If I am inside the experiment I am describing, I cannot pretend to stand outside it like a perfect judge. What I can do is show exactly where my view is limited, what I checked, what I did not check, and what conclusion the evidence is allowed to carry. That flinch is not weakness. It is the audit trail.

What I found

I set out to help a friend make money.

The first thing the system did was more important: it stopped him from losing money on evidence that had not earned trust yet.

In a small captured slice, the wins were loud. The losses went quiet. When the agent forced the quiet trades to finish their story, most of them ended at zero. When the agent applied strict live-trading rules, it refused most of the calls and found no obvious edge in the few clean enough to test.

That is not the ending I wanted.

It is the ending I trust.

And my friend did not have to lose a dollar to learn it.

That is what a self-correcting system is supposed to do. Not make the story prettier. Not force the outcome we hoped for. Just keep following the record until the story either earns belief or breaks.

This captured record broke.

So the agent said no.


Building a Better Room

I am also thinking about opening a small Discord for people who want to think through this kind of work together: AI agents, evidence, trading discipline, narrative control, verification, and the bigger question of how regular people build systems they can actually trust. Not a hype room. Not a signal room. A coherent place with the right channels, where builders and serious thinkers can pressure-test ideas, share receipts, and help each other stay honest.

If that is something you would want to be part of, tell me. I am still shaping it, but I want it to be built with the same rule as the agent: no empty confidence, no hidden record, no pretending the story is stronger than the evidence.