Every trader I know starts journaling in a spreadsheet, and every one of them abandons it within a month. Not because journaling is useless, but because the spreadsheet can't answer the questions that actually matter: "which of my rules costs me the most money?" or "am I cutting winners too early?" A flat sheet of rows can't tell you. Tools like RizeTrade solve this with a proper data model, and in this post I'll walk through how to design one yourself. The problem is almost always the data model. If you design the schema well up front, the hard reports fall out of it for free. Here's how I'd structure it. * Start with the trade, but don't overload it * The instinct is to make one giant trades table with fifty columns. Resist it. A trade has a small core of facts: CREATE TABLE trades ( id BIGSERIAL PRIMARY KEY , symbol TEXT NOT NULL , side TEXT NOT NULL CHECK ( side IN ( 'long' , 'short' )), entry_price NUMERIC NOT NULL , exit_price NUMERIC , quantity NUMERIC NOT NULL , entry_at TIMESTAMPTZ NOT NULL , exit_at TIMESTAMPTZ , stop_loss NUMERIC , take_profit NUMERIC , commission NUMERIC DEFAULT 0 , strategy_id BIGINT REFERENCES strategies ( id ) ); Everything else (emotions, notes, screenshots, rule checks) hangs off this in separate tables. That separation is what lets you slice the data later without schema migrations every time you want a new report. * R multiples belong in the model, not the UI * The single most useful number in trading isn't dollar P&L. It's the R multiple: profit or loss expressed in units of the risk you planned to take. A +2R win and a +2R win are comparable across a $500 account and a $50,000 account; two dollar figures aren't. Planned risk is defined the moment you enter, by your stop: planned_risk_per_unit = |entry_price - stop_loss| planned_R = (exit_price - entry_price) / planned_risk_per_unit (for longs) Store the stop at entry time. If you only record the realized exit, you lose the ability to detect stop loss violations, which is the who

Hi HN! I built hidetext.sh — a way to share text, code, and files through links the server can't read. How it works: your browser generates a random key and encrypts everything locally (NaCl secretbox, XSalsa20-Poly1305). Only ciphertext is uploaded. The key goes into the URL fragment — the part after # — which browsers never send to servers. The link carries the key, my server stores the locked box, and the two only meet in a browser. A design detail I'm fairly happy with: burn-after-read doesn

The best developer tools share one quality: you forget you are using them. Think about it. Your IDE fades into the background when you are in flow. Your terminal becomes muscle memory. These tools are invisible because they match your mental model so perfectly that there is zero friction between thought and action. This is exactly what online developer utilities should aspire to. The Problem with Fragmented DevTools Most developers have a bookmarks folder full of single-purpose websites: One for JSON formatting One for timestamp conversion One for Base64 encoding One for URL decoding Every switch between these tabs is a context loss. Every tool has a slightly different UI, different copy-paste format, different quirks. The Invisible Toolkit Opennomos Json (opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y) consolidates timestamp conversion, JSON formatting, and Base64 encoding into a single workspace. No install. No accounts. No pricing tiers. Just open a tab and work. This is the north star for developer tools: make them so simple that the user never has to think about the tool itself — they only think about their actual task. The Trend Is Clear We have seen this pattern across the dev ecosystem: GitHub Codespaces made local IDE setup invisible Vercel made deployment invisible Replit made runtime environment invisible The next frontier is utility tools. The sooner they become invisible, the better. Try it: opennomos.com/en/project/01KJ850Z7PNGXHXESBM68HE12Y Part of the Nomos Build-in-Public series.

Spotify's Release Radar can now deliver more personalized music recommendations.

https://www.nytimes.com/2026/07/10/climate/fcc-space-mirror.... https://www.pcmag.com/news/fcc-approves-reflect-orbitals-gia...

It's unclear how the planet avoided its star's bloated red giant stage.

Is paying a reasonable price for colorful cardboard too much to ask?

Hi, friends! Welcome to Installer No. 135, your guide to the best and Verge-iest stuff in the world. (If you're new here, welcome, crank the AC, and also you can read all the old editions at the Installer homepage.) This week, I've been reading about cold plunges and Colson Whitehead and the food truck mafia, […]

Roleplaying games are often defined by excess. Storylines that span dozens of hours, side quests so big they could be their own game, massive worlds that require complex maps to explore, and casts so big you start forgetting character names. That's part of what makes these games feel like epic adventures, but it can also […]

submitted by /u/Sankra [link] [留言]

Our weekly roundup of the best new indie games is here.

For the first time since 1995, the Bureau of Land Management is rewriting its grazing regulations.

The AquaSense X brings self-cleaning technology to pool robots for the first time, but is it worth nearly twice the price of Beatbot’s flagship cleaner?

The Skylight has become the informational and organizational hub of my household. My touchscreen-native kids have also gained more agency over our family activities.