Dan Bilzerian told Joe Rogan he beat one man for $54,000,000 at poker, over 8 to 9 months. Some of poker's best players still think the money came from his father. In the video below, he tells Rogan how the games worked, and what he was on while he played. He says it started in college. He sold 3 guns for $750, turned it into $10,000 on a gambling boat, and had $187,000 at the Bellagio 3 weeks later. By 2012, he says, he was playing private heads-up games against billionaires. At one point he had $18,000,000 on the table. One hand alone, he says, was worth $14 to 15 million. The man reportedly on the other side: billionaire Alec Gores. Pros later said Gores lost over $40,000,000 to him. Doug Polk publicly asked him to prove it. His theory: the money came from Dan's father, Paul Bilzerian, a former corporate raider who went to prison. Bilzerian denies it. He says he only got a trust fund at 35, years after the poker money. Poker pro Chance Kornuth backed part of the story. He says he coached Bilzerian for the Gores game, played at $5,000/$10,000 blinds. Gores has never confirmed the numbers. Poker genius, or trust-fund kid with a great story?

took the role, gave away the franchise

try it yourself here: visual-learning.app/vision-p…

Apple's $3,499 headset never shows you the room. Everything you see is a camera picture, streamed to the screens within 12 ms. I wanted to see how that works, and found a Vision Pro you can take apart. Lift the glass, pull it into layers, turn the lenses round to face you. What it shows: > 12 cameras, 5 sensors and 6 mics feed one chip, R1. The M2 next to it just runs the apps > the 2 screens are micro-OLED, each about the size of a postage stamp, 23 million pixels between them > behind each lens a ring of infrared lights and cameras watches your eyes. Invisible in real life, drawn red here > fans pull air in underneath and push it out the top The trick: the free anatomy skill makes Claude Code write the real numbers as a small model first, then draw every part from it and check every frame in headless Chrome. Built by @elvar_official. Press the steps yourself in the first reply ↓

press the steps yourself: visual-learning.app/f1-wheel the skill is free (MIT): github.com/wheresryan22/anat…

This is f*cking insane. Every kid who watches F1 should get to play with this. An F1 wheel you can drive, pull off the car and crack open, one button press per step. I always wondered what drivers actually do with all those buttons, so I went through it myself. > through a chicane, 3 pulls on the right paddle go from 5th to 8th while the shift lights sweep green, red, blue > under braking the left paddle clicks back from 8 to 4, and one yellow button turns on the pit limiter > pull the red collar and the whole wheel slides off the column, so the driver can climb out > then it splits into layers down to the board. About 1.3 kg, mostly carbon fibre 20-25 controls on one wheel, every part drawn in code with Claude Code and the free anatomy skill. Made by @elvar_official, try it yourself in the first reply 👇 Build your own in the article below

the pause-as-feature idea is the part most people miss. without those stalls the sequence is correct but the fold breaks, so faster translation can produce a worse protein. have you tried using JEV to flag other “slow on purpose” steps in agent pipelines?

parameterized compositions are the part most people skip. without props for text, colors and format you end up regenerating the whole video every time the brand changes. how are you handling the contact sheet review in practice?

Opus 5.5 is a beast at motion design but... give it one link and it becomes a full mechanical animation studio • real 3D engines where every part is modeled and moves on its own • cinematic exploded views with smooth camera moves down to every bolt • cutaways and airflow you can follow through the whole engine I asked for a turboprop teardown. this is render #3 send this to your Claude: mechanica-atlas.vercel.app

I gave Claude Code one folder and 5 free repos. 20 minutes later I had 3 agents planning, coding and reviewing each other. someone mapped 300+ open-source agent tools on one page. most people bookmark it and never open it again. hand Claude Code one folder and 5 repos from that list, and it stops being a chatbot. it plans, splits the work between agents, remembers, runs code in a sandbox and logs every step. here's the whole stack: > make a folder called AGENTS, open Claude Code in it, add a CLAUDE.md with one rule: "plan first, run code only in the sandbox, log every step" > install Ollama, run ollama pull qwen3. a local model for the cheap subtasks. $0 per token, nothing leaves your laptop > pip install crewai, then crewai create crew research. tell Claude to give it 3 roles: planner, coder, reviewer > pip install mem0ai. now the crew remembers your project between sessions instead of starting from zero > pip install e2b-code-interpreter (free key). every piece of code the agents write runs in a sandbox, not on your machine > pip install agentops. one line in the script and you see every step, every tool call, every error 20 minutes of setup, and you have a crew instead of a chat window. all the repos: -> github.com/ollama/ollama -> github.com/crewAIInc/crewAI -> github.com/mem0ai/mem0 -> github.com/e2b-dev/E2B -> github.com/AgentOps-AI/agent… bookmark this and test asap

graphify + jev-guard is the part most people skip. without the graph you still dig through files, and without the guard it can still do something dumb. how are you keeping the folder from getting messy after a week?

the night checker is the part that actually makes it useful. without it the vault just sits there until you open the laptop again.

read-only first is the right call. deleting before you know what it was doing kills the evidence.

one project first is the only way it stays clean. dump everything in and it starts mixing old and new.

this sh*t is unreal. your second brain can work the night shift now, on Grok Bot's own computer, with your laptop closed three bots, three jobs: the collector files every link, PDF and voice note you drop into raw/ and never touches the original the writer turns it into wiki pages and links every page back to where it came from the checker wakes up on a nightly routine and hunts contradictions and stale pages → you wake up to one morning page: what came in, what changed, what looks wrong → two sources disagree: it flags you instead of quietly picking one → nothing new about a page for a month: it gets a "needs a fresh source" tag chat memory keeps summaries. files keep exactly what you wrote no page gets saved without three things: > what it says > which file proves it > the last night it was checked paste this into Grok Bot: "Build me a second brain with three bots. Collector saves every source to raw/ and never edits it. Writer keeps wiki/ updated with a source link on every page. Checker runs every night at 3am, finds contradictions and stale pages, and sends me one morning summary. Ask me before deleting or sending anything. Show me the folder structure first and wait for my ok." give it one project for a week before you hand it your whole life the full 7-step build is in the article below ↓

separating writer and reviewer is the actual fix. same context always ends up approving itself. how are you running the review subagent right now?

graphify + memory folder is the real unlock. without it you still dig through files every time.

THIS IS GETTING F*CKING DANGEROUS You can run 20 Claude Code agents at the same time and put a second model on top that checks every word they write. None of them gets away with making stuff up You open the terminal: - 20 agents reading your files at once - Every claim checked against the source before it's saved - Anything without a real quote gets sent back - Everything lands in plain markdown folders The trick is the split: Opus does the work, a cheaper Haiku only decides if the claim is actually in the source. The loop keeps running until every claim passes This used to be a week of reading. Now it's two markdown files and one prompt Same Second Brain + agent swarm setup everyone keeps sharing. Full breakdown below ↓

typed heads instead of freeform text. that’s the actual unlock.

zero errors after three passes is nasty work.