Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

VS Rewrite: ROUND 2 - Post-credit Monologue animated!! Yayyy, Rewrite animation finally, les goo, y'all should watch it fr fr Rewrite by Springless (Comms Closed 3/3 Slots) #rewritesweep #execommunity #rewritesonic

fatalcubee's profile picture

Fatal Cube

1,103 subscribers

27,047 Aufrufe • vor 6 Monaten •via X (Twitter)

#rewritesweep#execommunity#rewritesonic
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Boo. [WIP] rewrite by Springless (Comms Closed 3/3 Slots) original animation/inspo ͏ ͏clown around town models by SnowyMorph on deviantart #rewrite #rewritesweep #sonicthehedgehog #b3d #animation
0:20

Boo. [WIP] rewrite by Springless (Comms Closed 3/3 Slots) original animation/inspo ͏ ͏clown around town models by SnowyMorph on deviantart #rewrite #rewritesweep #sonicthehedgehog #b3d #animation

JKBowden

247,317 Aufrufe • vor 1 Jahr

They really built up that whole “Kabir turning rogue” angle in Tiger 3’s post credit scene… only to undo it within the first 30 minutes of War 2 by revealing he’s just on a secret RAW mission. Wasted potential fr.
0:46

They really built up that whole “Kabir turning rogue” angle in Tiger 3’s post credit scene… only to undo it within the first 30 minutes of War 2 by revealing he’s just on a secret RAW mission. Wasted potential fr.

ZeMo

24,832 Aufrufe • vor 4 Monaten

Ethereum is starting from the endgame. Episode 4 of TheCoordinate is a deep dive into Lean Ethereum: a clean-slate rethink of consensus, execution, and data availability. I sat down with Justin Drake from Ethereum Foundation to unpack: > need for the rewrite, > rewrite items: post-quantum security + fast finality, > endgame finality (3-slot -> 2-slot -> maybe 1-slot), > slot anatomy, networking constraints, and the "SOL slots" meme, > real-time ZK proving changing the execution roadmap, > censorship resistance with FOSSIL, > role of L2s in the world of Lean Ethereum, > incentives across proposer, builder, prover, includer, attester. If you’re building on Ethereum or trying to understand where the base layer is headed, this one is for you. This is Episode 4 of TheCoordinate. Hope you enjoy it! ------------------------------- Timestamps: 0:00 Intro: digital intelligence needs digital institutions 0:30 The big questions: Lean Ethereum, consensus/execution, post-quantum 1:25 Why Ethereum needs an endgame mindset (and a clean-slate approach) 3:30 The two “rewrite-class” items: post-quantum security + fast finality 5:52 Beamchain → Lean Consensus → Lean Ethereum (expands beyond consensus) 6:34 ZK EVM + real-time proving within a slot → “10,000 TPS” target 10:10 “SOL slots”: pushing slot duration toward speed-of-light constraints 11:09 3-slot finality (3SF) → endgame finality (2-slot / 1-slot paths) 18:19 eFP2P: erasure-coded gossip, bandwidth efficiency, scaling blobs 26:21 FOSSIL today: inclusion lists + opening includers beyond validators 39:09 Lean VM: minimal ZKVM 51:04 XMSS explained: Merkle signatures, 2^32 leaves, statefulness tradeoff 1:00:36 Rollups: 99.9% throughput on L2s + “native rollups” 1:06:53 Economics: roles (builder/prover/includer/attester), proving costs, stake capping
1:16:31

Ethereum is starting from the endgame. Episode 4 of TheCoordinate is a deep dive into Lean Ethereum: a clean-slate rethink of consensus, execution, and data availability. I sat down with Justin Drake from Ethereum Foundation to unpack: > need for the rewrite, > rewrite items: post-quantum security + fast finality, > endgame finality (3-slot -> 2-slot -> maybe 1-slot), > slot anatomy, networking constraints, and the "SOL slots" meme, > real-time ZK proving changing the execution roadmap, > censorship resistance with FOSSIL, > role of L2s in the world of Lean Ethereum, > incentives across proposer, builder, prover, includer, attester. If you’re building on Ethereum or trying to understand where the base layer is headed, this one is for you. This is Episode 4 of TheCoordinate. Hope you enjoy it! ------------------------------- Timestamps: 0:00 Intro: digital intelligence needs digital institutions 0:30 The big questions: Lean Ethereum, consensus/execution, post-quantum 1:25 Why Ethereum needs an endgame mindset (and a clean-slate approach) 3:30 The two “rewrite-class” items: post-quantum security + fast finality 5:52 Beamchain → Lean Consensus → Lean Ethereum (expands beyond consensus) 6:34 ZK EVM + real-time proving within a slot → “10,000 TPS” target 10:10 “SOL slots”: pushing slot duration toward speed-of-light constraints 11:09 3-slot finality (3SF) → endgame finality (2-slot / 1-slot paths) 18:19 eFP2P: erasure-coded gossip, bandwidth efficiency, scaling blobs 26:21 FOSSIL today: inclusion lists + opening includers beyond validators 39:09 Lean VM: minimal ZKVM 51:04 XMSS explained: Merkle signatures, 2^32 leaves, statefulness tradeoff 1:00:36 Rollups: 99.9% throughput on L2s + “native rollups” 1:06:53 Economics: roles (builder/prover/includer/attester), proving costs, stake capping

Soubhik Deb

86,471 Aufrufe • vor 6 Monaten

The 5 biggest AI leaks are on GitHub. Free. This wasn't supposed to end up online. 1. instructkr/claw-code, 195k ⭐️ stars A clean rewrite of the leaked Claude Code CLI. Got 100k stars in one day. Nobody has ever done that on GitHub. 2. x1xhlol/system-prompts-and-models-of-ai-tools, 143k ⭐️ stars 28 coding tools, with the JSON tool schemas. Not just the prompt text, the actual list of what each agent can touch. 3. asgeirtj/system_prompts_leaks, 63k ⭐️ stars The real prompts behind Claude Opus 5, GPT-5.6, Gemini 3.5, Grok and Cursor. Claude's is 3,677 lines long. The Washington Post ran a story off this repo. 4. elder-plinius/CL4R1T4S, 47k ⭐️ stars Same thing, every big lab in one place. Updated when new models ship. 5. Piebald-AI/claude-code-system-prompts, 12.4k ⭐️ stars Claude Code's prompt pulled from compiled source. 27 tool descriptions, subagent prompts, security review logic. The best prompt engineering course ever made is 5 free repos written by people who never meant to publish them. Saved it. Most of it is publicly available, but few people know about it 👇
1:04

The 5 biggest AI leaks are on GitHub. Free. This wasn't supposed to end up online. 1. instructkr/claw-code, 195k ⭐️ stars A clean rewrite of the leaked Claude Code CLI. Got 100k stars in one day. Nobody has ever done that on GitHub. 2. x1xhlol/system-prompts-and-models-of-ai-tools, 143k ⭐️ stars 28 coding tools, with the JSON tool schemas. Not just the prompt text, the actual list of what each agent can touch. 3. asgeirtj/system_prompts_leaks, 63k ⭐️ stars The real prompts behind Claude Opus 5, GPT-5.6, Gemini 3.5, Grok and Cursor. Claude's is 3,677 lines long. The Washington Post ran a story off this repo. 4. elder-plinius/CL4R1T4S, 47k ⭐️ stars Same thing, every big lab in one place. Updated when new models ship. 5. Piebald-AI/claude-code-system-prompts, 12.4k ⭐️ stars Claude Code's prompt pulled from compiled source. 27 tool descriptions, subagent prompts, security review logic. The best prompt engineering course ever made is 5 free repos written by people who never meant to publish them. Saved it. Most of it is publicly available, but few people know about it 👇

unicode

12,437 Aufrufe • vor 20 Tagen

🎣 The Hook Skill Save this to write better hooks. What it does : (recommend watching the video on 2x speed instead⏩) Takes a brief (the brief defines the angle) Writes 3 hooks — same angle, different framing Scores each, rewrites anything weak, shows the rewrite All 3 ship as the ad set — Meta picks the winner via performance Gets better every Monday by checking what actually worked Pulls from your Memory & Context: Brand voice Audience Identity Mechanism Emotional Triggers What's won, what's flopped(Learnings) KILL list For me that's Notion — works with Obsidian, Claude Projects, MD folders Casts the person on camera before writing anything: Who she is (identity) Her age Where she is What she's doing What she's wearing What she's holding If anything's missing, the skill asks before generating Then asks one question: Would this exact person actually say this line out loud? Writes 3 hooks — same angle, different framing. One brief = one angle = three hooks. Want a different angle? Write a different brief. Opening styles in the menu: Controversy — a take that contradicts experts Bold opinion — a strong take that picks a side Raw confession — specific, emotional, hero-framed Riddle question — comedian/philosopher style only Mid-thought yapper — "Soooo my OBGYN told me…" Reaction — "This is wild —…" Dismissed quote — leads with the exact phrase someone said Stack — three things in fast sequence (brand names, power words, symptoms, body zones) Direct scene — a visible moment another person reacted to Authority declarative — when the speaker is the expert on camera THE HERO RULE — most important check. The audience is ALWAYS the hero. Protagonist mirrors the audience. Problem is ALWAYS external — hormones, doctors, biology, marketing lies Product is the tool the hero used Husband, doctor, friends are WITNESSES to her win — never the source of her validation Audience should want to BE her, not pity her Other rules every hook clears: 3-second rule — by 3 seconds of speech, the viewer is either curious or has a clear promise Vague ≠ curiosity — real curiosity from controversy, bold takes, raw confession, riddle questions. "Can you believe / Would you believe" are fake curiosity, auto-rewritten. Body/action specificity — "He stopped what he was doing" / "She noticed" / "Hasn't done that in years" → rewrite. "Staring at my butt" / "grabbed me by the waist" / "told me I look like I've been hitting the gym" → ship. Declarative beats interrogative — "He told me" > "He asked me." Always go bolder. Lead with the secret — open with what she KNOWS or HAS that no one else in the scene knows. Witness's reaction lands second as proof. Power-word stacks must be clear — three words alone is confusing. Make the category obvious (symptoms, body parts, etc.) and name what they are in the next sentence. Bridge between sentences — two sentences can't sit in a vacuum. Use a connector ("and for some reason today," "but somehow," "yet today," "— and") that references sentence 1 from inside sentence 2. Scores on 50 points. 5 dimensions, 0–10 each: Stops the scroll Creates curiosity Promises something specific Fits the brand and the person (Hero Rule lives here) Fits the format and what's winning Any dim under 8 → rewrites the hook. Shows the rewrite. Re-scores. Minimum two internal rewrite passes before anything is delivered. The first version you see is already polished. All three hooks ship as the ad set. Meta picks via performance data. Self-improving: Every Monday it pulls hooks that actually shipped Matches scores to real Meta performance Recalibrates the rubric if any dim stops predicting winners That's the whole skill. Comment HOOK and I'll send you the skill. Must be following.
8:32

🎣 The Hook Skill Save this to write better hooks. What it does : (recommend watching the video on 2x speed instead⏩) Takes a brief (the brief defines the angle) Writes 3 hooks — same angle, different framing Scores each, rewrites anything weak, shows the rewrite All 3 ship as the ad set — Meta picks the winner via performance Gets better every Monday by checking what actually worked Pulls from your Memory & Context: Brand voice Audience Identity Mechanism Emotional Triggers What's won, what's flopped(Learnings) KILL list For me that's Notion — works with Obsidian, Claude Projects, MD folders Casts the person on camera before writing anything: Who she is (identity) Her age Where she is What she's doing What she's wearing What she's holding If anything's missing, the skill asks before generating Then asks one question: Would this exact person actually say this line out loud? Writes 3 hooks — same angle, different framing. One brief = one angle = three hooks. Want a different angle? Write a different brief. Opening styles in the menu: Controversy — a take that contradicts experts Bold opinion — a strong take that picks a side Raw confession — specific, emotional, hero-framed Riddle question — comedian/philosopher style only Mid-thought yapper — "Soooo my OBGYN told me…" Reaction — "This is wild —…" Dismissed quote — leads with the exact phrase someone said Stack — three things in fast sequence (brand names, power words, symptoms, body zones) Direct scene — a visible moment another person reacted to Authority declarative — when the speaker is the expert on camera THE HERO RULE — most important check. The audience is ALWAYS the hero. Protagonist mirrors the audience. Problem is ALWAYS external — hormones, doctors, biology, marketing lies Product is the tool the hero used Husband, doctor, friends are WITNESSES to her win — never the source of her validation Audience should want to BE her, not pity her Other rules every hook clears: 3-second rule — by 3 seconds of speech, the viewer is either curious or has a clear promise Vague ≠ curiosity — real curiosity from controversy, bold takes, raw confession, riddle questions. "Can you believe / Would you believe" are fake curiosity, auto-rewritten. Body/action specificity — "He stopped what he was doing" / "She noticed" / "Hasn't done that in years" → rewrite. "Staring at my butt" / "grabbed me by the waist" / "told me I look like I've been hitting the gym" → ship. Declarative beats interrogative — "He told me" > "He asked me." Always go bolder. Lead with the secret — open with what she KNOWS or HAS that no one else in the scene knows. Witness's reaction lands second as proof. Power-word stacks must be clear — three words alone is confusing. Make the category obvious (symptoms, body parts, etc.) and name what they are in the next sentence. Bridge between sentences — two sentences can't sit in a vacuum. Use a connector ("and for some reason today," "but somehow," "yet today," "— and") that references sentence 1 from inside sentence 2. Scores on 50 points. 5 dimensions, 0–10 each: Stops the scroll Creates curiosity Promises something specific Fits the brand and the person (Hero Rule lives here) Fits the format and what's winning Any dim under 8 → rewrites the hook. Shows the rewrite. Re-scores. Minimum two internal rewrite passes before anything is delivered. The first version you see is already polished. All three hooks ship as the ad set. Meta picks via performance data. Self-improving: Every Monday it pulls hooks that actually shipped Matches scores to real Meta performance Recalibrates the rubric if any dim stops predicting winners That's the whole skill. Comment HOOK and I'll send you the skill. Must be following.

Jakob Counts | Creative Strategist

11,570 Aufrufe • vor 3 Monaten

Wow! This Changes Everything We Thought We Knew About Memory It is a groundbreaking big deal. TOU ARE MAKING GENERATIONAL MEMORIES RIGHT NOW IN EACH CELL! Scientists just found that your brain doesn’t just store memories — it stores the rules for how those memories will change in the future. A brand-new preprint from Stanford’s Greenleaf and Schnitzer labs (led by PhD student Yuxi Ke) drops a bombshell that feels like science fiction becoming reality overnight. For decades, neuroscientists have suspected that chromatin the DNA packaging material inside every cell nucleus might somehow “store” memory-related information. But what kind of information? Content? Timing? Rules? Now we have the answer! Using activity-dependent genetic tagging, fear conditioning, and single-nucleus multiome sequencing in the mouse medial prefrontal cortex (the brain’s long-term memory vault), the team tracked engram neurons for a full *month* after a memory was formed. What they discovered is electric: - One month after encoding, engram neurons have acquired a completely new chromatin landscape. - These chromatin changes are almost invisible at 7 days… but roar into existence by 28 days. - At recall, these engram cells don’t just “remember” better — they rewrite their entire transcriptional response. They preferentially fire up chromatin regulators, RNA processing machinery, and protein-turnover systems instead of simply boosting classic plasticity genes. In other words: the chromatin doesn’t just hold the memory of the past. It holds metaplastic instructions— rules that dictate how the neuron will respond the next time the memory is triggered. They call it chromatin metaplasticity. This is the “future tense of memory.” It is a massive deal 1. Memory is not just synapses. For 70+ years we’ve been obsessed with synaptic weights. This work proves the nucleus itself is a computational device that stores history-dependent rules. 2. It explains remote memory. The chromatin signature keeps maturing for weeks after the experience, perfectly matching the time course of systems consolidation into the cortex. 3. It’s energy-efficient genius. Instead of constantly maintaining memory proteins, the cell stores a silent, writable program that only activates when needed. Nature’s version of lazy evaluation. 4. It links development to adult memory. The late chromatin state is enriched for the exact same transcription-factor motifs used in embryonic development. Your adult brain is still running developmental software to lock in lifelong memories. 5. Huge therapeutic potential. If we can read or rewrite these chromatin metaplastic rules, we might one day boost failing remote memories in Alzheimer’s… or selectively dampen traumatic ones. This isn’t incremental. But a brand new layer of the memory code. And it explains WHY a person can receive memory from an organ transplant. It also explains generational traumas. Link: The future of neuroscience just got a lot more exciting and a lot more nuclear. Your chromatin is writing tomorrow’s memories today. And we finally have the first page of the instruction manual.
0:24

Wow! This Changes Everything We Thought We Knew About Memory It is a groundbreaking big deal. TOU ARE MAKING GENERATIONAL MEMORIES RIGHT NOW IN EACH CELL! Scientists just found that your brain doesn’t just store memories — it stores the rules for how those memories will change in the future. A brand-new preprint from Stanford’s Greenleaf and Schnitzer labs (led by PhD student Yuxi Ke) drops a bombshell that feels like science fiction becoming reality overnight. For decades, neuroscientists have suspected that chromatin the DNA packaging material inside every cell nucleus might somehow “store” memory-related information. But what kind of information? Content? Timing? Rules? Now we have the answer! Using activity-dependent genetic tagging, fear conditioning, and single-nucleus multiome sequencing in the mouse medial prefrontal cortex (the brain’s long-term memory vault), the team tracked engram neurons for a full *month* after a memory was formed. What they discovered is electric: - One month after encoding, engram neurons have acquired a completely new chromatin landscape. - These chromatin changes are almost invisible at 7 days… but roar into existence by 28 days. - At recall, these engram cells don’t just “remember” better — they rewrite their entire transcriptional response. They preferentially fire up chromatin regulators, RNA processing machinery, and protein-turnover systems instead of simply boosting classic plasticity genes. In other words: the chromatin doesn’t just hold the memory of the past. It holds metaplastic instructions— rules that dictate how the neuron will respond the next time the memory is triggered. They call it chromatin metaplasticity. This is the “future tense of memory.” It is a massive deal 1. Memory is not just synapses. For 70+ years we’ve been obsessed with synaptic weights. This work proves the nucleus itself is a computational device that stores history-dependent rules. 2. It explains remote memory. The chromatin signature keeps maturing for weeks after the experience, perfectly matching the time course of systems consolidation into the cortex. 3. It’s energy-efficient genius. Instead of constantly maintaining memory proteins, the cell stores a silent, writable program that only activates when needed. Nature’s version of lazy evaluation. 4. It links development to adult memory. The late chromatin state is enriched for the exact same transcription-factor motifs used in embryonic development. Your adult brain is still running developmental software to lock in lifelong memories. 5. Huge therapeutic potential. If we can read or rewrite these chromatin metaplastic rules, we might one day boost failing remote memories in Alzheimer’s… or selectively dampen traumatic ones. This isn’t incremental. But a brand new layer of the memory code. And it explains WHY a person can receive memory from an organ transplant. It also explains generational traumas. Link: The future of neuroscience just got a lot more exciting and a lot more nuclear. Your chromatin is writing tomorrow’s memories today. And we finally have the first page of the instruction manual.

Brian Roemmele

44,298 Aufrufe • vor 27 Tagen

Claude Code can ship a 45-second animated explainer ad in 30 minutes. No video editor needed, just CC + skills. Here's how I made this video for Soteri Skin 👇 1. /plan Concept Brief (Claude Code) I handwrite a concept brief, then chat with the agent to iterate on it. The agent gathers any raw materials we might need - context about the brand, product images, end card, etc. The concept brief details the concept, characters, visual style, script, etc 2. /prepare a moodboard (CC + GPT Image 2 + ElevenLabs) After reviewing the script, generate: - character reference images - voiceover samples for the characters / narrator - the storyboard (scene by scene grid) - a few keyframe scenes 3. /generate Keyframes for each scene (CC uses Nano Banana or GPT Image 2) Uses the character references from the previous step to generate keyframes for each scene. I probably should have done a round of iteration at this step – there's some character drift and the pH meter representation could have been better. 4. /animate Keyframe → Animated Clip (CC uses Fal Seedance) Generate 2-4 representative scenes first to see a preview. If it looks good, then generate everything. 5. /stitch (CC + ffmpeg + ElevenLabs) - Stitch clips together with hard cut - Add a music score + SFX - Sync clips to the VO - Add captions - Review and edit timing / pacing issues 6. /watch the final cut and review it - as a video editor for technical errors (mismatched voiceover and visuals, AI hallucinations, etc) - as a viewer (ICP). I delegate most of the review to the agent because it catches more things and keeps me out of the loop as much as possible. It also fixes any issues found in the review. That's it. This video took me 30 minutes because I have already created skills for everything I described above. Some day, this will be < 5 minutes. I just review and chat to provide direction and feedback. The skills do all the technical work. 7. /learn Extracts learnings and updates the skills. This final step is really important. It turns this process into a closed loop system that makes the next video much easier to create because all the learnings from the human-in-the-loop process get encoded into code. Skills are code too. If you want access to the skill, drop a comment, and I'll DM it to you (must be following). If you want to make AI video ads like this, DM me.
0:45

Claude Code can ship a 45-second animated explainer ad in 30 minutes. No video editor needed, just CC + skills. Here's how I made this video for Soteri Skin 👇 1. /plan Concept Brief (Claude Code) I handwrite a concept brief, then chat with the agent to iterate on it. The agent gathers any raw materials we might need - context about the brand, product images, end card, etc. The concept brief details the concept, characters, visual style, script, etc 2. /prepare a moodboard (CC + GPT Image 2 + ElevenLabs) After reviewing the script, generate: - character reference images - voiceover samples for the characters / narrator - the storyboard (scene by scene grid) - a few keyframe scenes 3. /generate Keyframes for each scene (CC uses Nano Banana or GPT Image 2) Uses the character references from the previous step to generate keyframes for each scene. I probably should have done a round of iteration at this step – there's some character drift and the pH meter representation could have been better. 4. /animate Keyframe → Animated Clip (CC uses Fal Seedance) Generate 2-4 representative scenes first to see a preview. If it looks good, then generate everything. 5. /stitch (CC + ffmpeg + ElevenLabs) - Stitch clips together with hard cut - Add a music score + SFX - Sync clips to the VO - Add captions - Review and edit timing / pacing issues 6. /watch the final cut and review it - as a video editor for technical errors (mismatched voiceover and visuals, AI hallucinations, etc) - as a viewer (ICP). I delegate most of the review to the agent because it catches more things and keeps me out of the loop as much as possible. It also fixes any issues found in the review. That's it. This video took me 30 minutes because I have already created skills for everything I described above. Some day, this will be < 5 minutes. I just review and chat to provide direction and feedback. The skills do all the technical work. 7. /learn Extracts learnings and updates the skills. This final step is really important. It turns this process into a closed loop system that makes the next video much easier to create because all the learnings from the human-in-the-loop process get encoded into code. Skills are code too. If you want access to the skill, drop a comment, and I'll DM it to you (must be following). If you want to make AI video ads like this, DM me.

Shiv

11,723 Aufrufe • vor 3 Monaten

𝐓𝐇𝐄 𝐁𝐑𝐔𝐓𝐀𝐋 𝐓𝐑𝐔𝐓𝐇 𝟗𝟗% 𝐎𝐅 𝐏𝐄𝐎𝐏𝐋𝐄 𝐈𝐆𝐍𝐎𝐑𝐄: 𝐘𝐨𝐮 𝐖𝐢𝐥𝐥 𝐍𝐞𝐯𝐞𝐫 𝐁𝐞𝐜𝐨𝐦𝐞 𝐃𝐚𝐧𝐠𝐞𝐫𝐨𝐮𝐬 𝐁𝐲 𝐂𝐨𝐥𝐥𝐞𝐜𝐭𝐢𝐧𝐠 𝐒𝐤𝐢𝐥𝐥𝐬, 𝐎𝐧𝐥𝐲 𝐁𝐲 𝐁𝐥𝐞𝐞𝐝𝐢𝐧𝐠 𝐅𝐨𝐫 𝐒𝐨𝐦𝐞𝐭𝐡𝐢𝐧𝐠 𝐓𝐡𝐚𝐭 𝐂𝐨𝐮𝐥𝐝 𝐀𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐅𝐚𝐢𝐥 𝐚𝐧𝐝 𝐋𝐞𝐚𝐯𝐞 𝐘𝐨𝐮 𝐁𝐫𝐨𝐤𝐞. Look around you right now. How many people do you know who are endlessly scrolling courses, chasing the "next big skill," the shiny new thing everyone swears will make them rich or relevant? They stack certificates, watch tutorials at 2x speed, and wait for the perfect moment when they're finally "ready." Then they stay stuck. Years pass. Nothing ships. No money comes in. No real freedom shows up. DAN KOE dropped this post I quoted, because he sees it everywhere. He's watched the cycle for years: people consuming advice like it's oxygen, but never breathing life into something of their own. He built his path the hard way, through trial, ugly failures, and constant pivots and now he's calling it out plainly. No gentle nudge. Just raw truth meant to jolt anyone still sitting on the sidelines. "Stop Chasing the 'Best' Skills. Start Building Something That Could Kill You (Metaphorically)". Here's the core of what he said: "Don't try to learn the 'best new skills'." >> Build your own thing. >> Try to sell it. >> Fail over and over again. >> Learn what it means to adapt and iterate. >> Remove your dependency from others and hunt for your own survival. You will learn the exact skills you need, and you will learn them better than anyone else." Read that last line again. It's not motivational poetry. It's mechanics. Why This Hits Different in 2026 We're drowning in information. Every feed is packed with gurus promising the fastest path: "Learn this one prompt and print money." "Master this framework in 30 days." It's seductive. It feels safe. You can tell yourself you're progressing while staying comfortable. But comfort is the enemy of real skill. DAN KOE isn't saying education is useless. He's saying passive consumption without skin in the game creates shallow knowledge. He posted this early in the year because January is when resolutions peak and most die. People declare they're finally going to learn the hot skill of 2026. By February, the dopamine fades, and they're back to scrolling. The Real Learning Loop Nobody Talks About. 1. Build something real. Not a side project you hide in Notion. Something you intend to exchange for money. 2. Put it in front of strangers and ask for money. This is where most people freeze. "What if it flops?" It will. Multiple times. That's the point. 3. Fail publicly. The sting is your teacher. Customers ghost. Refunds hit. Each failure shows you exactly what's broken. 4. Adapt fast. Tweak. Rewrite. Repackage. Test again. Iteration isn't cute, it's survival. 5. Repeat until it works. Along the way, skills stack naturally. No course can simulate that pressure. No mentor can transfer it through words. You earn it through exposure. Some will say: "But proven paths lower risk. Why reinvent the wheel?" Fair. Copying a working model can give you a head start. But even then, you still have to execute, adapt to your audience, and survive the inevitable pivots. NOTE: "Blind copying without personal ownership usually ends in mediocrity". If this post sparked something in you, anger, excitement, defensiveness, lean into it. Pick one small thing you've been avoiding launching. Make it ugly. Make it small. But make it public and try to sell it. >> Fail. >> Adapt. >> Survive. That's how you become dangerous. Not by collecting more tutorials, but by becoming the person who no longer needs them. Inspiration from DAN KOE
1:00

𝐓𝐇𝐄 𝐁𝐑𝐔𝐓𝐀𝐋 𝐓𝐑𝐔𝐓𝐇 𝟗𝟗% 𝐎𝐅 𝐏𝐄𝐎𝐏𝐋𝐄 𝐈𝐆𝐍𝐎𝐑𝐄: 𝐘𝐨𝐮 𝐖𝐢𝐥𝐥 𝐍𝐞𝐯𝐞𝐫 𝐁𝐞𝐜𝐨𝐦𝐞 𝐃𝐚𝐧𝐠𝐞𝐫𝐨𝐮𝐬 𝐁𝐲 𝐂𝐨𝐥𝐥𝐞𝐜𝐭𝐢𝐧𝐠 𝐒𝐤𝐢𝐥𝐥𝐬, 𝐎𝐧𝐥𝐲 𝐁𝐲 𝐁𝐥𝐞𝐞𝐝𝐢𝐧𝐠 𝐅𝐨𝐫 𝐒𝐨𝐦𝐞𝐭𝐡𝐢𝐧𝐠 𝐓𝐡𝐚𝐭 𝐂𝐨𝐮𝐥𝐝 𝐀𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐅𝐚𝐢𝐥 𝐚𝐧𝐝 𝐋𝐞𝐚𝐯𝐞 𝐘𝐨𝐮 𝐁𝐫𝐨𝐤𝐞. Look around you right now. How many people do you know who are endlessly scrolling courses, chasing the "next big skill," the shiny new thing everyone swears will make them rich or relevant? They stack certificates, watch tutorials at 2x speed, and wait for the perfect moment when they're finally "ready." Then they stay stuck. Years pass. Nothing ships. No money comes in. No real freedom shows up. DAN KOE dropped this post I quoted, because he sees it everywhere. He's watched the cycle for years: people consuming advice like it's oxygen, but never breathing life into something of their own. He built his path the hard way, through trial, ugly failures, and constant pivots and now he's calling it out plainly. No gentle nudge. Just raw truth meant to jolt anyone still sitting on the sidelines. "Stop Chasing the 'Best' Skills. Start Building Something That Could Kill You (Metaphorically)". Here's the core of what he said: "Don't try to learn the 'best new skills'." >> Build your own thing. >> Try to sell it. >> Fail over and over again. >> Learn what it means to adapt and iterate. >> Remove your dependency from others and hunt for your own survival. You will learn the exact skills you need, and you will learn them better than anyone else." Read that last line again. It's not motivational poetry. It's mechanics. Why This Hits Different in 2026 We're drowning in information. Every feed is packed with gurus promising the fastest path: "Learn this one prompt and print money." "Master this framework in 30 days." It's seductive. It feels safe. You can tell yourself you're progressing while staying comfortable. But comfort is the enemy of real skill. DAN KOE isn't saying education is useless. He's saying passive consumption without skin in the game creates shallow knowledge. He posted this early in the year because January is when resolutions peak and most die. People declare they're finally going to learn the hot skill of 2026. By February, the dopamine fades, and they're back to scrolling. The Real Learning Loop Nobody Talks About. 1. Build something real. Not a side project you hide in Notion. Something you intend to exchange for money. 2. Put it in front of strangers and ask for money. This is where most people freeze. "What if it flops?" It will. Multiple times. That's the point. 3. Fail publicly. The sting is your teacher. Customers ghost. Refunds hit. Each failure shows you exactly what's broken. 4. Adapt fast. Tweak. Rewrite. Repackage. Test again. Iteration isn't cute, it's survival. 5. Repeat until it works. Along the way, skills stack naturally. No course can simulate that pressure. No mentor can transfer it through words. You earn it through exposure. Some will say: "But proven paths lower risk. Why reinvent the wheel?" Fair. Copying a working model can give you a head start. But even then, you still have to execute, adapt to your audience, and survive the inevitable pivots. NOTE: "Blind copying without personal ownership usually ends in mediocrity". If this post sparked something in you, anger, excitement, defensiveness, lean into it. Pick one small thing you've been avoiding launching. Make it ugly. Make it small. But make it public and try to sell it. >> Fail. >> Adapt. >> Survive. That's how you become dangerous. Not by collecting more tutorials, but by becoming the person who no longer needs them. Inspiration from DAN KOE

C A L

44,068 Aufrufe • vor 7 Monaten

Few people care more about software performance than Casey Muratori. Give him a few minutes of your attention with this episode, and he'll convince you to learn to read Assembly (no, really, I finally started to read it, it's really not that scary, esp with an AI that can help explain the sequences). Timestamps: 00:00 Intro 05:17 Games at Microsoft 12:52 Building games 16:00 Why performance matters 27:12 Why you should learn to read assembly 30:36 Designing for optimization 42:51 How to get better at writing performant software 49:04 Understanding how the CPU works 55:53 Building games then and now 1:05:56 How game engines changed building games 1:10:48 Why new games compete with old games 1:13:25 GTA 6: why is it taking so long? 1:16:59 Casey's critique of clean code 1:21:48 Casey's take on TDD 1:24:30 What is good code? 1:27:32 What makes a good software engineer? 1:33:56 Why Casey doesn't code with AI 1:39:01 AI's impact on the game industry 1:44:43 AI and burnout 1:50:21 Why you should read papers Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • Sentry – application monitoring software considered “not bad” by millions of developers • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable Three interesting things we talked about: 1. Is performance starting to matter to businesses? Enterprise software buyers care mainly about cost, compliance, and capabilities – but not performance. Even so, there are some products gaining major popularity and market share due to their performance, such as File Pilot (next-gen file explorer) and the Blick video editor. Is the tide turning? 2. Profiler-driven performance optimization is the wrong way to optimize The standard way of optimizing is to profile the application, tweak hotspots, then check if the stats have improved. But this only finds a local minimum; Casey says every engineer he’s worked with who was a great “optimizer” began by establishing what the hardware could theoretically do, and then did not stop until they’d closed the gap to that performance level. 3. Take a grain of salt with conventional wisdom that premature optimization is the “root of all evil” Many devs use it as an excuse to delay performance optimization, but Casey says that not optimizing in time could mean that only performance hotspots can be fixed later, and not the architectural issues that create poor performance. Architect your system to be performant, or you’ll have trouble solving problems without a rewrite!
1:53:58

Few people care more about software performance than Casey Muratori. Give him a few minutes of your attention with this episode, and he'll convince you to learn to read Assembly (no, really, I finally started to read it, it's really not that scary, esp with an AI that can help explain the sequences). Timestamps: 00:00 Intro 05:17 Games at Microsoft 12:52 Building games 16:00 Why performance matters 27:12 Why you should learn to read assembly 30:36 Designing for optimization 42:51 How to get better at writing performant software 49:04 Understanding how the CPU works 55:53 Building games then and now 1:05:56 How game engines changed building games 1:10:48 Why new games compete with old games 1:13:25 GTA 6: why is it taking so long? 1:16:59 Casey's critique of clean code 1:21:48 Casey's take on TDD 1:24:30 What is good code? 1:27:32 What makes a good software engineer? 1:33:56 Why Casey doesn't code with AI 1:39:01 AI's impact on the game industry 1:44:43 AI and burnout 1:50:21 Why you should read papers Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • Sentry – application monitoring software considered “not bad” by millions of developers • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable Three interesting things we talked about: 1. Is performance starting to matter to businesses? Enterprise software buyers care mainly about cost, compliance, and capabilities – but not performance. Even so, there are some products gaining major popularity and market share due to their performance, such as File Pilot (next-gen file explorer) and the Blick video editor. Is the tide turning? 2. Profiler-driven performance optimization is the wrong way to optimize The standard way of optimizing is to profile the application, tweak hotspots, then check if the stats have improved. But this only finds a local minimum; Casey says every engineer he’s worked with who was a great “optimizer” began by establishing what the hardware could theoretically do, and then did not stop until they’d closed the gap to that performance level. 3. Take a grain of salt with conventional wisdom that premature optimization is the “root of all evil” Many devs use it as an excuse to delay performance optimization, but Casey says that not optimizing in time could mean that only performance hotspots can be fixed later, and not the architectural issues that create poor performance. Architect your system to be performant, or you’ll have trouble solving problems without a rewrite!

Gergely Orosz

97,777 Aufrufe • vor 15 Tagen

Post 🇫🇷 & 🇺🇸 🇫🇷🚨📣 #MichaelJackson Vs #Epstein … « Si les médias officiels n’étaient pas contrôlés par des pédophiles satanistes, c’est le genre de reportages qu’on verrait sur Michael Jackson » LIZ CROKIN ❤️🫡 Michael protégeait les enfants. Et Trump le savait. Il a créé NeverLand pour protéger les enfants des pédophiles comme Epstein, pas pour les abuser. Michael Jackson essayait de nous avertir… Le monde entier lui doit des excuses. 🎥 Écoutez attentivement cette vidéo 🟢 Publications INCONTOURNABLES sur Michael Jackson : 👇 1/ J’ai vu le pire, le cauchemar de la condition humaine, de l’âme humaine. Je n’aurais jamais imaginé qu’un homme ordinaire puisse être capable de tout ça.”👉 2/ En 1993, Michael Jackson a écrit une chanson intitulée Palestine Don’t Cry. Sony Records ne l’a pas laissé sortir. Plus tard la même année, il a été accusé pour la première fois d’abus sexuels sur mineur 👉 3/ “Ils n’en Ont Rien à Faire de Nous” 👉 4/ Michael Jackson essayait de nous avertir… 👉 🇺🇸🚨📣 “If the mainstream media weren’t controlled by satanic pedophiles, this is the kind of reporting we would see about Michael Jackson,” Liz Crokin❤️🫡 Michael protected children. And Donald J. Trump knew it. He created NeverLand to protect children from pedophiles like Epstein, not to abuse them. Michael Jackson was trying to warn us… The whole world owes him an apology. 🎥 Watch this video carefully. 🟢 Must-read posts on Michael Jackson: 1/ “I’ve seen the worst, the nightmare of the human condition, of the human soul…” 2/ In 1993, Michael Jackson wrote “Palestine Don’t Cry.” Sony Records didn’t release it. Later that same year, he was accused for the first time of child sexual abuse. 3/ “They don’t care about us” 4/ Michael Jackson was trying to warn us… ⚠️ 📌 (See link in the French section above 👆) 🇺🇸🦅🇫🇷 Sylvia Miami 🇫🇷🦅🇺🇸 👉 #SylviaMiami #Trump #Neverland #ProtectChildren #BritneySpears #Prince #MediaCorruption #MainstreamLies #ChildProtection #HollywoodSecrets #CelebrityScandals #JusticeForVictims
2:38

Post 🇫🇷 & 🇺🇸 🇫🇷🚨📣 #MichaelJackson Vs #Epstein … « Si les médias officiels n’étaient pas contrôlés par des pédophiles satanistes, c’est le genre de reportages qu’on verrait sur Michael Jackson » LIZ CROKIN ❤️🫡 Michael protégeait les enfants. Et Trump le savait. Il a créé NeverLand pour protéger les enfants des pédophiles comme Epstein, pas pour les abuser. Michael Jackson essayait de nous avertir… Le monde entier lui doit des excuses. 🎥 Écoutez attentivement cette vidéo 🟢 Publications INCONTOURNABLES sur Michael Jackson : 👇 1/ J’ai vu le pire, le cauchemar de la condition humaine, de l’âme humaine. Je n’aurais jamais imaginé qu’un homme ordinaire puisse être capable de tout ça.”👉 2/ En 1993, Michael Jackson a écrit une chanson intitulée Palestine Don’t Cry. Sony Records ne l’a pas laissé sortir. Plus tard la même année, il a été accusé pour la première fois d’abus sexuels sur mineur 👉 3/ “Ils n’en Ont Rien à Faire de Nous” 👉 4/ Michael Jackson essayait de nous avertir… 👉 🇺🇸🚨📣 “If the mainstream media weren’t controlled by satanic pedophiles, this is the kind of reporting we would see about Michael Jackson,” Liz Crokin❤️🫡 Michael protected children. And Donald J. Trump knew it. He created NeverLand to protect children from pedophiles like Epstein, not to abuse them. Michael Jackson was trying to warn us… The whole world owes him an apology. 🎥 Watch this video carefully. 🟢 Must-read posts on Michael Jackson: 1/ “I’ve seen the worst, the nightmare of the human condition, of the human soul…” 2/ In 1993, Michael Jackson wrote “Palestine Don’t Cry.” Sony Records didn’t release it. Later that same year, he was accused for the first time of child sexual abuse. 3/ “They don’t care about us” 4/ Michael Jackson was trying to warn us… ⚠️ 📌 (See link in the French section above 👆) 🇺🇸🦅🇫🇷 Sylvia Miami 🇫🇷🦅🇺🇸 👉 #SylviaMiami #Trump #Neverland #ProtectChildren #BritneySpears #Prince #MediaCorruption #MainstreamLies #ChildProtection #HollywoodSecrets #CelebrityScandals #JusticeForVictims

Sylvia Miami

62,733 Aufrufe • vor 7 Monaten

why did “JING JING” appear on the screen during “L.O.V.E.”? (#JanJingjing) CONTEXT 🩷 (vid 2) - jan and singto sang “L.O.V.E.” by X3 Super Gang during the university star contest scene in SOTUS ep 5. the lyrics to “L.O.V.E.” are: “oh baby, L - i look over there, but it isn’t there O - i look over here, but i can’t find it V - which way should i look to find it? E - where is this thing called love? i really want to encounter it” - notably, if we directly translate the last lyric, “อยากจะพบเจอจริง ๆ (yak-ja-phob-je-jing-jing),” word by word, it’ll be “want to encounter really.” - in other words, the pronouns are dropped in this lyric, as thai is a pro-drop language, whereas “really (jing-jing)” appears at the end of the lyric as an adverb SOTUS 10TH YEAR CONCERT 🩷 (pic 1) - combined with the current context (i.e., janjingjing as a pair), this lyric can also sound like, “i want to encounter jingjing.” therefore, it was a super smart and fun touch to have “JING JING” appear on the screen whenever jan sang this lyric while re-enacting the scene during the concert (( to note, while “really (จริง ๆ)” and “jingjing (name; จิงจิง)” sound the same, their spellings are different, as you can see. the “ๆ” in “really” is a repetition marker in thai, so jingjing sometimes types her name as “จิงๆ,” as you will see below )) 🩷 (vid 3) - as a result, the watermark clip went viral, where jan got teased on day 2 [💬: suay-jing-jing (“you’re really pretty”), but i don’t want to say too much. jingjing’s watermark was all over the screen yesterday 🦊: oh… 💬: rak-jing-jing (“love jingjing”). hashtag janjingjing] 🩷 (pic 4) - when jingjing replied to jan’s post about SOTUS 10th year concert, she referred back to this lyric, “want to encounter really (yak-ja-PHOB-JE-JING-JING)”: [🐯: ได้พบเจอจิงๆแล้วนะ (dai-PHOB-JE-JING-JING-laew-na; “you’ve finally encountered jingjing”)] - as noted above, jingjing typed her name as “จิงๆ” here instead of “จิงจิง,” which further emphasizes the wordplay SO YEAH 🤟🏻💕 (more similar wordplay involving “really” VS “jingjing” is included in the mentions ;p)
1:30

why did “JING JING” appear on the screen during “L.O.V.E.”? (#JanJingjing) CONTEXT 🩷 (vid 2) - jan and singto sang “L.O.V.E.” by X3 Super Gang during the university star contest scene in SOTUS ep 5. the lyrics to “L.O.V.E.” are: “oh baby, L - i look over there, but it isn’t there O - i look over here, but i can’t find it V - which way should i look to find it? E - where is this thing called love? i really want to encounter it” - notably, if we directly translate the last lyric, “อยากจะพบเจอจริง ๆ (yak-ja-phob-je-jing-jing),” word by word, it’ll be “want to encounter really.” - in other words, the pronouns are dropped in this lyric, as thai is a pro-drop language, whereas “really (jing-jing)” appears at the end of the lyric as an adverb SOTUS 10TH YEAR CONCERT 🩷 (pic 1) - combined with the current context (i.e., janjingjing as a pair), this lyric can also sound like, “i want to encounter jingjing.” therefore, it was a super smart and fun touch to have “JING JING” appear on the screen whenever jan sang this lyric while re-enacting the scene during the concert (( to note, while “really (จริง ๆ)” and “jingjing (name; จิงจิง)” sound the same, their spellings are different, as you can see. the “ๆ” in “really” is a repetition marker in thai, so jingjing sometimes types her name as “จิงๆ,” as you will see below )) 🩷 (vid 3) - as a result, the watermark clip went viral, where jan got teased on day 2 [💬: suay-jing-jing (“you’re really pretty”), but i don’t want to say too much. jingjing’s watermark was all over the screen yesterday 🦊: oh… 💬: rak-jing-jing (“love jingjing”). hashtag janjingjing] 🩷 (pic 4) - when jingjing replied to jan’s post about SOTUS 10th year concert, she referred back to this lyric, “want to encounter really (yak-ja-PHOB-JE-JING-JING)”: [🐯: ได้พบเจอจิงๆแล้วนะ (dai-PHOB-JE-JING-JING-laew-na; “you’ve finally encountered jingjing”)] - as noted above, jingjing typed her name as “จิงๆ” here instead of “จิงจิง,” which further emphasizes the wordplay SO YEAH 🤟🏻💕 (more similar wordplay involving “really” VS “jingjing” is included in the mentions ;p)

²²

21,334 Aufrufe • vor 10 Tagen

The largest IPO in history is not a win. It's the bell at the top. SpaceX is raising $75B at a $1.75T valuation. 3 times bigger than the previous record IPO. Bigger than the GDP of most countries. Every major index is racing to rewrite its rules to absorb it. That's a synchronized push to force trillions in passive money into one listing. At the most fragile setup for markets in two decades. Below's the convergence: Index providers aren't quietly tweaking rules in the background. They're proposing wholesale rewrites RIGHT NOW: → S&P Dow Jones reviewing the profitability requirement that stood since 2002. Up for waiver. → Nasdaq cutting seasoning windows from 90 trading days down to 15. → FTSE Russell going further. Down to 5. S&P 500 public comment window closes May 28. Potential implementation? June 8. Four days before SpaceX trades. Three of the most important benchmarks on Earth. Restructured in the same window. For the same listing. That's the setup. Here's what happens next: When you force a $1.75 trillion stock into an index, the index doesn't print new money to buy it. It sells other names to make room. Mechanical selling of NVDA, AAPL, MSFT, AMZN. The current leaders absorb forced sell-pressure the moment SPCX enters. But that's just the warmup. SpaceX is floating only 5% of its shares. Everything else stays with insiders, early investors, employees. Lockup expires in two stages: → 90 days post-IPO: early September → 180 days post-IPO: early December Look at where those dates land. September falls inside the worst statistical window in the entire 4-year cycle. May through October. 15 of the last 16 midterm election years went red in that window. September is the deep end of it. December lands right after the November midterm vote. Policy uncertainty resolves. Big money rotates fast. None of this is happening in a healthy market. This is landing on top of: → 30-year Treasury yield above 5%. Last time that showed up was July 2007. Three months before the market peak. Twelve months before Lehman. → $2 trillion AI cloud backlog where over half of demand is OpenAI and Anthropic recycling investor money back to Microsoft, Google, Amazon. → Equities at the most overvalued level in history. Not close to it. Actually there. Here is the sequence loading: June 12: SPCX prints. Forced passive buying overwhelms reality. Late June: mechanical rebalancing starts selling everything else in Nasdaq 100. Early September: first lockup expires. Insiders sell into the artificially inflated bid. October: middle of the historically worst window for stocks in midterm years. Early December: second lockup expires. Bigger wave. Four catalysts. One direction. Not a forecast. A calendar. The setup couldn't be more loaded if it tried. What do you actually do? You can't fight the IPO. SPCX will probably rip on day one. The passive bid is too mechanical to stop. But you can stop being long everything else. My system flags the exact moment the market shifts from CAUTION to DANGER. You'll be warned before it hits, like always. Many people will wish they had followed me sooner Save this post. Watch the June 8 comment window. Position accordingly.
0:28

The largest IPO in history is not a win. It's the bell at the top. SpaceX is raising $75B at a $1.75T valuation. 3 times bigger than the previous record IPO. Bigger than the GDP of most countries. Every major index is racing to rewrite its rules to absorb it. That's a synchronized push to force trillions in passive money into one listing. At the most fragile setup for markets in two decades. Below's the convergence: Index providers aren't quietly tweaking rules in the background. They're proposing wholesale rewrites RIGHT NOW: → S&P Dow Jones reviewing the profitability requirement that stood since 2002. Up for waiver. → Nasdaq cutting seasoning windows from 90 trading days down to 15. → FTSE Russell going further. Down to 5. S&P 500 public comment window closes May 28. Potential implementation? June 8. Four days before SpaceX trades. Three of the most important benchmarks on Earth. Restructured in the same window. For the same listing. That's the setup. Here's what happens next: When you force a $1.75 trillion stock into an index, the index doesn't print new money to buy it. It sells other names to make room. Mechanical selling of NVDA, AAPL, MSFT, AMZN. The current leaders absorb forced sell-pressure the moment SPCX enters. But that's just the warmup. SpaceX is floating only 5% of its shares. Everything else stays with insiders, early investors, employees. Lockup expires in two stages: → 90 days post-IPO: early September → 180 days post-IPO: early December Look at where those dates land. September falls inside the worst statistical window in the entire 4-year cycle. May through October. 15 of the last 16 midterm election years went red in that window. September is the deep end of it. December lands right after the November midterm vote. Policy uncertainty resolves. Big money rotates fast. None of this is happening in a healthy market. This is landing on top of: → 30-year Treasury yield above 5%. Last time that showed up was July 2007. Three months before the market peak. Twelve months before Lehman. → $2 trillion AI cloud backlog where over half of demand is OpenAI and Anthropic recycling investor money back to Microsoft, Google, Amazon. → Equities at the most overvalued level in history. Not close to it. Actually there. Here is the sequence loading: June 12: SPCX prints. Forced passive buying overwhelms reality. Late June: mechanical rebalancing starts selling everything else in Nasdaq 100. Early September: first lockup expires. Insiders sell into the artificially inflated bid. October: middle of the historically worst window for stocks in midterm years. Early December: second lockup expires. Bigger wave. Four catalysts. One direction. Not a forecast. A calendar. The setup couldn't be more loaded if it tried. What do you actually do? You can't fight the IPO. SPCX will probably rip on day one. The passive bid is too mechanical to stop. But you can stop being long everything else. My system flags the exact moment the market shifts from CAUTION to DANGER. You'll be warned before it hits, like always. Many people will wish they had followed me sooner Save this post. Watch the June 8 comment window. Position accordingly.

Himanshu Kumar

42,059 Aufrufe • vor 3 Monaten

Tom Crawshaw has been building automations for 9 years with $25 million in client revenue to his name. He just walked me through his Claude Code content system that's generating millions of views and tens of thousands of followers. Here's what I learned: 1. Skills beat Projects in Claude. Projects load every context file on every message and burn your token window. Skills work like a book where the LLM reads the table of contents and pulls only the chapter it needs for the job. Same context, fraction of the tokens. 2. He has a /content-create slash command that runs the entire pipeline. Voice profile, copywriting principles, hook generation, image direction. One command. He doesn't write anything from scratch anymore. 3. His voice profile auto-updates weekly. He wrote a script that hits the X API every 7 days, pulls his top-performing posts by engagement, and rewrites his voice profile based on what's actually working. The profile evolves on its own. 4. He distilled a master copywriter's entire body of work into a single markdown file. Grabbed every Alen Sultanic post he could find, dropped it into Claude, asked for the core principles, fed it into the skill. Now every post he writes runs through those principles automatically. 5. The hook generator scores 16 hooks per post against 7 criteria. Curiosity loops, specificity, sensory, credibility, voice match, and a couple of others. He never picks the #1 by default. Sometimes he splices the first line of one hook with the body of another. The taste is still his. 6. /insights is a native Claude Code command nobody talks about. It analyzes every session you've ever run and produces a full report on your usage patterns, where things break down, and prompts you can paste back into Claude to fix them. I had never heard of it. I'm running it tonight. 7. He spends most of his time on hooks and images. If those two suck, the body copy doesn't matter. Nobody reads it. 8. Image generation is never one-shot. He keeps a folder of reference images that have worked before and feeds them into Nano Banana/GPT Image 2 every time. Then he takes the 80-90% output and finishes it in Canva using "magic grab" to move logos and clean up text. Last mile is human every time. 9. The humanizer step is non-negotiable. Strip em dashes. Kill the "it's not X, it's Y" pattern. Cut the triple negatives. Cut "no fluff." He still has to remind Claude mid-session because it drifts. If you're not auditing for AI tells, you're shipping slop. 10. Wisprflow is the most important tool in his stack. Not a content tool. An everything tool. His test for whether you should be using it: do you talk faster than you type? You do. Everyone does. Bonus fact he dropped: QWERTY was designed 200 years ago to slow typing down so old typewriters wouldn't jam. We've been carrying that forward ever since. Voice is finally undoing it. This was an inside look at how a serious operator Tom is using Claude Code to run a content engine. The good, the bad, the iteration, all of it. I hope you enjoy this one as much as I did. Go watch it.
57:27

Tom Crawshaw has been building automations for 9 years with $25 million in client revenue to his name. He just walked me through his Claude Code content system that's generating millions of views and tens of thousands of followers. Here's what I learned: 1. Skills beat Projects in Claude. Projects load every context file on every message and burn your token window. Skills work like a book where the LLM reads the table of contents and pulls only the chapter it needs for the job. Same context, fraction of the tokens. 2. He has a /content-create slash command that runs the entire pipeline. Voice profile, copywriting principles, hook generation, image direction. One command. He doesn't write anything from scratch anymore. 3. His voice profile auto-updates weekly. He wrote a script that hits the X API every 7 days, pulls his top-performing posts by engagement, and rewrites his voice profile based on what's actually working. The profile evolves on its own. 4. He distilled a master copywriter's entire body of work into a single markdown file. Grabbed every Alen Sultanic post he could find, dropped it into Claude, asked for the core principles, fed it into the skill. Now every post he writes runs through those principles automatically. 5. The hook generator scores 16 hooks per post against 7 criteria. Curiosity loops, specificity, sensory, credibility, voice match, and a couple of others. He never picks the #1 by default. Sometimes he splices the first line of one hook with the body of another. The taste is still his. 6. /insights is a native Claude Code command nobody talks about. It analyzes every session you've ever run and produces a full report on your usage patterns, where things break down, and prompts you can paste back into Claude to fix them. I had never heard of it. I'm running it tonight. 7. He spends most of his time on hooks and images. If those two suck, the body copy doesn't matter. Nobody reads it. 8. Image generation is never one-shot. He keeps a folder of reference images that have worked before and feeds them into Nano Banana/GPT Image 2 every time. Then he takes the 80-90% output and finishes it in Canva using "magic grab" to move logos and clean up text. Last mile is human every time. 9. The humanizer step is non-negotiable. Strip em dashes. Kill the "it's not X, it's Y" pattern. Cut the triple negatives. Cut "no fluff." He still has to remind Claude mid-session because it drifts. If you're not auditing for AI tells, you're shipping slop. 10. Wisprflow is the most important tool in his stack. Not a content tool. An everything tool. His test for whether you should be using it: do you talk faster than you type? You do. Everyone does. Bonus fact he dropped: QWERTY was designed 200 years ago to slow typing down so old typewriters wouldn't jam. We've been carrying that forward ever since. Voice is finally undoing it. This was an inside look at how a serious operator Tom is using Claude Code to run a content engine. The good, the bad, the iteration, all of it. I hope you enjoy this one as much as I did. Go watch it.

Corey Ganim

36,518 Aufrufe • vor 4 Monaten