Loading video...

Video Failed to Load

Go Home

9 prompt templates. 34 hours saved per week! Not a claim from a weekend experiment. A number pulled from thirty days of logged hours running manual processes side-by-side with automated ones and measuring the gap. The eight hours of work still happen. Nothing is being skipped. Competitive scans. Email...

neil_xbt's profile picture

NeilXbt

15,934 subscribers

17,239 views • 2 months ago •via X (Twitter)

EducationScience & TechnologyFinance
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

most people spend hours describing what they want to Claude Code this guy just browsed a catalog of thousands of animated UI components, found one he liked, and hit "copy prompt" that's it. the prompt goes into Claude Code and it builds it. > 21st(.)dev - a library of community-made components built for React, Next.js, Tailwind > every component has a ready-made prompt attached > you pick the effect, copy, paste, done no describing animations from scratch. no explaining what "smooth scroll" or "hover glow" means. someone already figured out the exact prompt that produces it. gap between people who know this exists and people who don't is measured in hours per project full walkthrough in the article below
0:41

most people spend hours describing what they want to Claude Code this guy just browsed a catalog of thousands of animated UI components, found one he liked, and hit "copy prompt" that's it. the prompt goes into Claude Code and it builds it. > 21st(.)dev - a library of community-made components built for React, Next.js, Tailwind > every component has a ready-made prompt attached > you pick the effect, copy, paste, done no describing animations from scratch. no explaining what "smooth scroll" or "hover glow" means. someone already figured out the exact prompt that produces it. gap between people who know this exists and people who don't is measured in hours per project full walkthrough in the article below

monokern

64,484 views • 1 month ago

John Carmack on the importance hard work: “For decades, I worked 60 hours a week” “I was never one of the programmers who would do all-nighters or work for 20 hours straight,” programming legend John Carmack begins when asked about his work routine. “My brain generally starts turning to mush after 12 hours or so. But hard work is really important, and for decades I would work 60 hours a week. I would work 10 hours a day, 6 days a week.” He continues: “I had a little thing in the back of my head where I was almost jealous of some of the programmers who would do these marathon sessions. Like Dave Taylor, one of the guys we had at id Software, would be one of those people who would fall asleep under his desk sometimes and all the classic hacker tropes about these things. Part of me was always a little bothered that wasn’t me. I wouldn’t program 20 hours straight because I’m falling apart and not being very effective after 12 hours . . . There are people who can work on 4 hours of sleep and continue to do good work, but there’s a lot of people who just fall apart. I always try to get 8 hours of sleep . . . you can work 100 hours a week and still get 8 hours of sleep if you prioritize things correctly. But I do believe in working hard.” John disagrees with the backlash against hard work and voices support for game developer’s comment that “40 hours a week is kind of a part-time job.” “If you’re doing what you think is important work that you’re passionate about, working more gets more done. It’s really not possible to argue with that if you’ve been around the people who work with that level of intensity.” He believes people who argue that you’re less productive if you work more than 40 hours a week are misinterpreting things: “Your marginal productivity for an hour after eight hours is less than one of your peak hours, but you’re not literally getting less done. There’s a point where you start breaking things and literally going backwards, but it’s not 8-12 hours.” John illustrates this point with a fictional example: “Imagine there’s an asteroid that’s going to crash into Earth and destroy all human life. Do you want Elon Musk and the people working at SpaceX building the interceptor that’s going to deflect the asteroid clocking out at 5pm because they’re going to do worse work if they work another couple hours? It seems absurd . . . It’s the truth: working longer gets more done.” Video source: Lex Fridman (Aug 2022)
3:39

John Carmack on the importance hard work: “For decades, I worked 60 hours a week” “I was never one of the programmers who would do all-nighters or work for 20 hours straight,” programming legend John Carmack begins when asked about his work routine. “My brain generally starts turning to mush after 12 hours or so. But hard work is really important, and for decades I would work 60 hours a week. I would work 10 hours a day, 6 days a week.” He continues: “I had a little thing in the back of my head where I was almost jealous of some of the programmers who would do these marathon sessions. Like Dave Taylor, one of the guys we had at id Software, would be one of those people who would fall asleep under his desk sometimes and all the classic hacker tropes about these things. Part of me was always a little bothered that wasn’t me. I wouldn’t program 20 hours straight because I’m falling apart and not being very effective after 12 hours . . . There are people who can work on 4 hours of sleep and continue to do good work, but there’s a lot of people who just fall apart. I always try to get 8 hours of sleep . . . you can work 100 hours a week and still get 8 hours of sleep if you prioritize things correctly. But I do believe in working hard.” John disagrees with the backlash against hard work and voices support for game developer’s comment that “40 hours a week is kind of a part-time job.” “If you’re doing what you think is important work that you’re passionate about, working more gets more done. It’s really not possible to argue with that if you’ve been around the people who work with that level of intensity.” He believes people who argue that you’re less productive if you work more than 40 hours a week are misinterpreting things: “Your marginal productivity for an hour after eight hours is less than one of your peak hours, but you’re not literally getting less done. There’s a point where you start breaking things and literally going backwards, but it’s not 8-12 hours.” John illustrates this point with a fictional example: “Imagine there’s an asteroid that’s going to crash into Earth and destroy all human life. Do you want Elon Musk and the people working at SpaceX building the interceptor that’s going to deflect the asteroid clocking out at 5pm because they’re going to do worse work if they work another couple hours? It seems absurd . . . It’s the truth: working longer gets more done.” Video source: Lex Fridman (Aug 2022)

Startup Archive

240,234 views • 8 months ago

20-YEAR-OLD GUY SHOWS HOW CLAUDE API CAN TURN 500-VIEW CONTENT INTO A $40K/MONTH CLIENT WORKFLOW Not from a big agency. Not from hiring writers. Just taking the same service people sell every week and wiring Claude API into the boring middle. A topic goes in. It pulls the research, angles, outline, draft, edits, and a clean file. That is normally $500-$1,500 of freelance work per client project. The screen says around $40K/month, but the real number is the time saved. A $3K project stops being 8 hours of rewriting and becomes 45 minutes of checking before delivery. Most people use Claude to write one answer. He is showing what happens when the whole process becomes the product.
1:18

20-YEAR-OLD GUY SHOWS HOW CLAUDE API CAN TURN 500-VIEW CONTENT INTO A $40K/MONTH CLIENT WORKFLOW Not from a big agency. Not from hiring writers. Just taking the same service people sell every week and wiring Claude API into the boring middle. A topic goes in. It pulls the research, angles, outline, draft, edits, and a clean file. That is normally $500-$1,500 of freelance work per client project. The screen says around $40K/month, but the real number is the time saved. A $3K project stops being 8 hours of rewriting and becomes 45 minutes of checking before delivery. Most people use Claude to write one answer. He is showing what happens when the whole process becomes the product.

Gipp 🦅

19,254 views • 2 months ago

Boris Cherny, the creator of Claude Code at Anthropic, just explained why most people aren't getting real results from Claude in this talk he breaks down exactly how most people skipped the setup entirely: - 90% of code at Anthropic is written by Claude itself - the 14% you lose to CLAUDE.md before typing a word - lawyers, designers, and finance people are building real things with it - no CS degree. no background. nothing Boris Cherny: "Claude Code is 100% written by Claude Code, Cowork is 100% written by Claude Code" if you've been using Claude for months and never configured a single thing, you skipped the 20 steps that change everything. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below
2:15

Boris Cherny, the creator of Claude Code at Anthropic, just explained why most people aren't getting real results from Claude in this talk he breaks down exactly how most people skipped the setup entirely: - 90% of code at Anthropic is written by Claude itself - the 14% you lose to CLAUDE.md before typing a word - lawyers, designers, and finance people are building real things with it - no CS degree. no background. nothing Boris Cherny: "Claude Code is 100% written by Claude Code, Cowork is 100% written by Claude Code" if you've been using Claude for months and never configured a single thing, you skipped the 20 steps that change everything. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Khairallah AL-Awady

182,466 views • 2 months ago

SOMEONE IS CHARGING $5,000/MONTH FOR SOCIAL MEDIA CONTENT THAT CLAUDE WRITES IN 6 HOURS A WEEK no team, no office, just Claude and a scheduling app mid-market companies pay $2,000-$5,000 per month for social media management, and most of them are getting a junior freelancer posting generic content or an agency that barely touches their account one of them runs the whole thing in a weekly workflow: brief Claude on Monday, write posts Tuesday and Wednesday, schedule Thursday, pull numbers Friday another one charged three clients the same $5,000 rate before hiring a single person, that's $180,000/year running on one tool there's a prompt that makes Claude write every post in the client's exact voice by analyzing 5 examples of their existing content, 10 min per post instead of 60 you can land the first client with one outreach message, no portfolio, no case studies, just a specific offer and a 30-minute call the model is already working, the only question is whether you build it or watch someone else do it full breakdown of the workflow, the prompts, and how to find clients in the article below
0:42

SOMEONE IS CHARGING $5,000/MONTH FOR SOCIAL MEDIA CONTENT THAT CLAUDE WRITES IN 6 HOURS A WEEK no team, no office, just Claude and a scheduling app mid-market companies pay $2,000-$5,000 per month for social media management, and most of them are getting a junior freelancer posting generic content or an agency that barely touches their account one of them runs the whole thing in a weekly workflow: brief Claude on Monday, write posts Tuesday and Wednesday, schedule Thursday, pull numbers Friday another one charged three clients the same $5,000 rate before hiring a single person, that's $180,000/year running on one tool there's a prompt that makes Claude write every post in the client's exact voice by analyzing 5 examples of their existing content, 10 min per post instead of 60 you can land the first client with one outreach message, no portfolio, no case studies, just a specific offer and a 30-minute call the model is already working, the only question is whether you build it or watch someone else do it full breakdown of the workflow, the prompts, and how to find clients in the article below

Chrome

13,769 views • 2 months ago

One iPhone with iOS 18.2. A Gumroad account. $18,200 in 12 months. Apple Intelligence wrote 80% of the first drafts. The formula is simple : > AI creates the raw material > you package and price it > the internet distributes. 5 revenue streams built on free platforms. Prompt packs on Gumroad generated $6,840. A weekly newsletter on Substack brought $4,320. One ebook on Amazon KDP added $3,060. Medium articles paid $2,190. Notion templates closed the gap at $1,830. The fastest product to ship is a prompt pack. 30 to 50 tested prompts for a specific use case, $9 to $15 on Gumroad, 3 hours to build. One guide published in month 4 made $340 in 90 days from 2 hours of work.
0:58

One iPhone with iOS 18.2. A Gumroad account. $18,200 in 12 months. Apple Intelligence wrote 80% of the first drafts. The formula is simple : > AI creates the raw material > you package and price it > the internet distributes. 5 revenue streams built on free platforms. Prompt packs on Gumroad generated $6,840. A weekly newsletter on Substack brought $4,320. One ebook on Amazon KDP added $3,060. Medium articles paid $2,190. Notion templates closed the gap at $1,830. The fastest product to ship is a prompt pack. 30 to 50 tested prompts for a specific use case, $9 to $15 on Gumroad, 3 hours to build. One guide published in month 4 made $340 in 90 days from 2 hours of work.

Lummox

13,989 views • 2 months ago

Most PMs tried Claude Code for a day, didn't get instant magic, and quietly decided it wasn't for them. The PMs pulling ahead are 1500 hours in and still rebuilding their setup every single day. That's the entire gap. Not talent. Not technical background. Just whether you stayed past the awkward week where nothing works yet. Hannah runs product at Anthropic and has the highest documented Claude Code mileage of any PM I've talked to. Her advice for someone with two hours this weekend isn't "build a workflow." It's "find one task to automate so you free up six hours next week to learn." That reframe is the whole game. Most people treat AI learning as something they'll get to after the real work is done. Hannah treats freeing up time to learn AS the real work. Two hours in, six hours out. Next week you reinvest those six into deeper automations that free up fifteen. The compounding only starts if you survive the first week. And almost nobody does, because day-one Claude Code feels mediocre. Your context isn't loaded. Your skills aren't written. Your CLAUDE.md is empty. The tool is guessing about your role, your product, your standards, everything. The PMs at 1500 hours aren't smarter than the ones who quit on day two. They just didn't quit on day two. Every PM interview at a frontier AI company in 2026 is some version of "show me your setup." The honest answer for most people right now is "I tried it once." Build the hour. Then build the loop.
4:56

Most PMs tried Claude Code for a day, didn't get instant magic, and quietly decided it wasn't for them. The PMs pulling ahead are 1500 hours in and still rebuilding their setup every single day. That's the entire gap. Not talent. Not technical background. Just whether you stayed past the awkward week where nothing works yet. Hannah runs product at Anthropic and has the highest documented Claude Code mileage of any PM I've talked to. Her advice for someone with two hours this weekend isn't "build a workflow." It's "find one task to automate so you free up six hours next week to learn." That reframe is the whole game. Most people treat AI learning as something they'll get to after the real work is done. Hannah treats freeing up time to learn AS the real work. Two hours in, six hours out. Next week you reinvest those six into deeper automations that free up fifteen. The compounding only starts if you survive the first week. And almost nobody does, because day-one Claude Code feels mediocre. Your context isn't loaded. Your skills aren't written. Your CLAUDE.md is empty. The tool is guessing about your role, your product, your standards, everything. The PMs at 1500 hours aren't smarter than the ones who quit on day two. They just didn't quit on day two. Every PM interview at a frontier AI company in 2026 is some version of "show me your setup." The honest answer for most people right now is "I tried it once." Build the hour. Then build the loop.

Aakash Gupta

49,411 views • 4 months ago

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.
0:37

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

Gipp 🦅

14,871 views • 2 months ago

I built this Claude Cowork automation to handle a simple content marketing task that my team used to do daily. This frees up ~4 hours of time per week. At CoinLedger, every week we spend time repurposing pillar content (blog content) across various social networks (reddit, twitter, YouTube, IG, etc) We used to have a human + AI do this work. Now we just have AI doing it via this automation. Here's how the Claude automation works: → Scrapes any blog URL and extracts key insights → Transforms content into platform-specific posts (Reddit, Twitter, Instagram) → Automatically creates organized Google Docs for each piece → Updates our internal content tracking spreadsheet in real-time → Highlights completed tasks without any human oversight The game-changer? It runs completely in the background while I focus on higher-value strategic work. Now scale this up. All mundane, "virtual-assistant-style" work can be automated in this fashion. There is SO MUCH of this type of work in the real world. And there will be EVEN MORE of it when you can do it all for $100/mo. Here's the process you should follow: 1. Identify a simple, manual process that genuinely adds value to your company if you did it every single day 2. Build the skill / automation for Claude Code / Claude Cowork to do it 24/7 3. Refine 4. Unleash Claude 5. Repeat This could be list building for sales leads, scraping LinkedIn, identifying viral videos on TikTok that you can spin for your brand, research, and so so much more. Your imagination is the limit. But this type of work exists in all businesses. If you do this enough, you start to see why people have dozens of Claude instances running 24/7 on multiple devices. They have figured out ways for Claude to drive economically valuable work for their organizations. And now they are simply scaling up that work. Wild. This is where the world is quickly heading.
13:05

I built this Claude Cowork automation to handle a simple content marketing task that my team used to do daily. This frees up ~4 hours of time per week. At CoinLedger, every week we spend time repurposing pillar content (blog content) across various social networks (reddit, twitter, YouTube, IG, etc) We used to have a human + AI do this work. Now we just have AI doing it via this automation. Here's how the Claude automation works: → Scrapes any blog URL and extracts key insights → Transforms content into platform-specific posts (Reddit, Twitter, Instagram) → Automatically creates organized Google Docs for each piece → Updates our internal content tracking spreadsheet in real-time → Highlights completed tasks without any human oversight The game-changer? It runs completely in the background while I focus on higher-value strategic work. Now scale this up. All mundane, "virtual-assistant-style" work can be automated in this fashion. There is SO MUCH of this type of work in the real world. And there will be EVEN MORE of it when you can do it all for $100/mo. Here's the process you should follow: 1. Identify a simple, manual process that genuinely adds value to your company if you did it every single day 2. Build the skill / automation for Claude Code / Claude Cowork to do it 24/7 3. Refine 4. Unleash Claude 5. Repeat This could be list building for sales leads, scraping LinkedIn, identifying viral videos on TikTok that you can spin for your brand, research, and so so much more. Your imagination is the limit. But this type of work exists in all businesses. If you do this enough, you start to see why people have dozens of Claude instances running 24/7 on multiple devices. They have figured out ways for Claude to drive economically valuable work for their organizations. And now they are simply scaling up that work. Wild. This is where the world is quickly heading.

David Roberts

31,900 views • 6 months ago

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this
9:32

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

814,570 views • 2 months ago

A new father became so terrified of never learning anything again that he accidentally dismantled the biggest lie in education. His name is Josh Kaufman, and he wasn't a neuroscientist or a professor. He was an author working from home, running a business with his wife, with a newborn daughter who had just obliterated any concept of free time he thought he had. Around week 8 of sleep deprivation, he had the thought every parent has. I am never going to learn anything new ever again. And because he was the kind of person who responds to panic with research, he went to the library and started reading everything he could find about how humans acquire skills. He read book after book, study after study. Every single one said the same thing. 10,000 hours. He had a full-body reaction to that number. 10,000 hours is a full-time job for five years. He didn't have five years. He didn't have five hours. He had a newborn and a business and a wife who was also building a business in the same house. So he kept digging. And here is where it gets interesting. The 10,000 hour rule came from a researcher named K. Anders Ericsson at Florida State University. What Ericsson actually studied was professional athletes, world-class musicians, chess grandmasters people at the absolute tip of ultra-competitive, ultra-high-performing fields. His finding was that the people at the very top of those narrow fields had put in around 10,000 hours of deliberate practice. That is all the finding said. Then Malcolm Gladwell wrote Outliers in 2007, and the message went through a game of telephone that destroyed its meaning entirely. It takes 10,000 hours to reach the top of an ultra-competitive field became it takes 10,000 hours to become an expert, which became it takes 10,000 hours to become good at something, which became it takes 10,000 hours to learn something. That last statement is completely false. And the actual research had been showing something different the entire time. When cognitive psychologists study skill acquisition, they measure a graph that looks identical across every domain they have ever tested. At the start, performance is terrible. With a small amount of practice, it improves rapidly. Then it plateaus, and subsequent gains become much harder and slower to achieve. The steep part of that curve the jump from knowing nothing to being reasonably good happens much faster than anyone tells you. Not 10,000 hours. Not 1,000 hours. 20 hours. Kaufman tested this himself. He had always wanted to learn ukulele. He picked one up, put 20 hours of focused deliberate practice into it, and stood on a TEDx stage playing a medley of recognizable pop songs in front of a live audience. The crowd went wild. He then told them that performance was his 20th hour. But 20 hours is not just a number. There is a method inside it. The first step is to deconstruct the skill. Most things we think of as single skills are actually bundles of dozens of smaller skills. You do not need all of them. You need the ones that get you to your specific goal the fastest. In music, this means most songs use four or five chords. Learn those first. Ignore the rest until they matter. The second step is to learn just enough to self-correct. Get three to five resources books, courses, videos but do not use them as a reason to delay practice. The point of learning is not to master theory first. It is to get good enough at noticing your own mistakes that you can adjust as you go. The third step is to remove barriers to practice. Not through willpower. Through structure. If the instrument is in the case in the closet, you will not play it. If your phone is in the room, you will not focus. Kaufman was brutal about this. The environment does the work that discipline cannot sustain. The fourth step is the one that actually makes the system work. Pre-commit to 20 hours before you start. Here is why this matters. Every skill has what he called a frustration barrier. The early part of learning anything is genuinely terrible. You are incompetent and you know it. That feeling is so uncomfortable that most people quit before they ever cross to the other side of the curve. By pre-committing to 20 hours, you are making a contract with yourself to push through the frustration long enough to arrive at the part where things start clicking. The barrier to learning something new is never intellectual. It is emotional. We are afraid of feeling stupid. That fear costs most people everything they could have learned. Kaufman figured this out while holding a baby and running out of time, which is the most human possible condition for having a breakthrough. Most people are waiting for the perfect season to start. He just started. 20 hours is 45 minutes a day for a month. That is it. That is the price of going from knowing nothing to being genuinely capable at almost anything you can name. The 10,000 hour rule was never about learning. It was about becoming the best in the world. You probably do not need to be the best in the world. You just need to start.
19:26

A new father became so terrified of never learning anything again that he accidentally dismantled the biggest lie in education. His name is Josh Kaufman, and he wasn't a neuroscientist or a professor. He was an author working from home, running a business with his wife, with a newborn daughter who had just obliterated any concept of free time he thought he had. Around week 8 of sleep deprivation, he had the thought every parent has. I am never going to learn anything new ever again. And because he was the kind of person who responds to panic with research, he went to the library and started reading everything he could find about how humans acquire skills. He read book after book, study after study. Every single one said the same thing. 10,000 hours. He had a full-body reaction to that number. 10,000 hours is a full-time job for five years. He didn't have five years. He didn't have five hours. He had a newborn and a business and a wife who was also building a business in the same house. So he kept digging. And here is where it gets interesting. The 10,000 hour rule came from a researcher named K. Anders Ericsson at Florida State University. What Ericsson actually studied was professional athletes, world-class musicians, chess grandmasters people at the absolute tip of ultra-competitive, ultra-high-performing fields. His finding was that the people at the very top of those narrow fields had put in around 10,000 hours of deliberate practice. That is all the finding said. Then Malcolm Gladwell wrote Outliers in 2007, and the message went through a game of telephone that destroyed its meaning entirely. It takes 10,000 hours to reach the top of an ultra-competitive field became it takes 10,000 hours to become an expert, which became it takes 10,000 hours to become good at something, which became it takes 10,000 hours to learn something. That last statement is completely false. And the actual research had been showing something different the entire time. When cognitive psychologists study skill acquisition, they measure a graph that looks identical across every domain they have ever tested. At the start, performance is terrible. With a small amount of practice, it improves rapidly. Then it plateaus, and subsequent gains become much harder and slower to achieve. The steep part of that curve the jump from knowing nothing to being reasonably good happens much faster than anyone tells you. Not 10,000 hours. Not 1,000 hours. 20 hours. Kaufman tested this himself. He had always wanted to learn ukulele. He picked one up, put 20 hours of focused deliberate practice into it, and stood on a TEDx stage playing a medley of recognizable pop songs in front of a live audience. The crowd went wild. He then told them that performance was his 20th hour. But 20 hours is not just a number. There is a method inside it. The first step is to deconstruct the skill. Most things we think of as single skills are actually bundles of dozens of smaller skills. You do not need all of them. You need the ones that get you to your specific goal the fastest. In music, this means most songs use four or five chords. Learn those first. Ignore the rest until they matter. The second step is to learn just enough to self-correct. Get three to five resources books, courses, videos but do not use them as a reason to delay practice. The point of learning is not to master theory first. It is to get good enough at noticing your own mistakes that you can adjust as you go. The third step is to remove barriers to practice. Not through willpower. Through structure. If the instrument is in the case in the closet, you will not play it. If your phone is in the room, you will not focus. Kaufman was brutal about this. The environment does the work that discipline cannot sustain. The fourth step is the one that actually makes the system work. Pre-commit to 20 hours before you start. Here is why this matters. Every skill has what he called a frustration barrier. The early part of learning anything is genuinely terrible. You are incompetent and you know it. That feeling is so uncomfortable that most people quit before they ever cross to the other side of the curve. By pre-committing to 20 hours, you are making a contract with yourself to push through the frustration long enough to arrive at the part where things start clicking. The barrier to learning something new is never intellectual. It is emotional. We are afraid of feeling stupid. That fear costs most people everything they could have learned. Kaufman figured this out while holding a baby and running out of time, which is the most human possible condition for having a breakthrough. Most people are waiting for the perfect season to start. He just started. 20 hours is 45 minutes a day for a month. That is it. That is the price of going from knowing nothing to being genuinely capable at almost anything you can name. The 10,000 hour rule was never about learning. It was about becoming the best in the world. You probably do not need to be the best in the world. You just need to start.

Ihtesham Ali

44,762 views • 4 months ago

Fun fact: It would take the average PC roughly 138,069,000 hours or about 15,761 years to render Avatar: The Way of Water. Here’s how I worked it out: The average PC in 2024 has 6 cores. The average blade on WetaFXs renderfarm has between 16-64 cores. There is roughly 414,000 frames in the finished film, accounting for half of the film being 48fps and half being 24fps at the final runtime of 192 minutes. Each frame took an average of 20-80 hours to render on WetaFXs blades depending on shot complexity and accounting for the 4K delivery resolution. With that info, we can work out the average: We say that the average Weta blade has 40 cores (average between the 16-64 count). That gives a Weta to PC core ratio of 6.67 We also say that the average render time per frame is 50 hours (average of 20-80) Total render time for Weta: 50 hours x 414,000 frames = 20,700,000 hours To work out how long this would be on the average home PC we must multiply by the core ratio from earlier: 50 hours x 6.67 = 333.5 hours per frame Total render time on a home PC: 333.5 hours x 414,000 frames = 138,069,000 hours, which converted to years is 15,761 DISCLAIMER: This is all an educated guess done for fun based on publicly available technical information about the film and Wetas renderfarm. It does not account for any production optimizations, storage limits etc. The real number could be drastically higher. CREDITS: Video is from WetaFXs YouTube channel:
1:49

Fun fact: It would take the average PC roughly 138,069,000 hours or about 15,761 years to render Avatar: The Way of Water. Here’s how I worked it out: The average PC in 2024 has 6 cores. The average blade on WetaFXs renderfarm has between 16-64 cores. There is roughly 414,000 frames in the finished film, accounting for half of the film being 48fps and half being 24fps at the final runtime of 192 minutes. Each frame took an average of 20-80 hours to render on WetaFXs blades depending on shot complexity and accounting for the 4K delivery resolution. With that info, we can work out the average: We say that the average Weta blade has 40 cores (average between the 16-64 count). That gives a Weta to PC core ratio of 6.67 We also say that the average render time per frame is 50 hours (average of 20-80) Total render time for Weta: 50 hours x 414,000 frames = 20,700,000 hours To work out how long this would be on the average home PC we must multiply by the core ratio from earlier: 50 hours x 6.67 = 333.5 hours per frame Total render time on a home PC: 333.5 hours x 414,000 frames = 138,069,000 hours, which converted to years is 15,761 DISCLAIMER: This is all an educated guess done for fun based on publicly available technical information about the film and Wetas renderfarm. It does not account for any production optimizations, storage limits etc. The real number could be drastically higher. CREDITS: Video is from WetaFXs YouTube channel:

Rassoul Edji

37,819 views • 1 year ago

what if you could turn two hours of AI work into a week of viral content that gets 2M+ impressions/week? every morning, dan koe opens chatgpt/claude and uses them like an internal strategy team and it's paid off through millions of new followers and $$. he feeds them top-performing posts and asks for the hidden patterns like structure, rhythm, curiosity gaps, emotional payoff. from there, he builds a repeatable system that turns 2 hours of work into 7 days of content. his playbook looks like this: 1. validate fast start on twitter. write two or three high-density posts a day. when one hits, that’s your signal. expand it into a newsletter, then a youtube script, then repurpose across linkedin, instagram, threads, and shorts. 2. one source drives all one weekly newsletter becomes the foundation. one youtube video per week comes straight from that outline. the goal is not more ideas—it’s one good idea multiplied. 3. compress research with AI he drops long-form videos into claude or chatgpt and gets six hours of research condensed into a thousand words. he compares it with his own archives to find fresh angles. 4. the prompt stack after writing, he runs everything through a custom set of prompts: – a youtube title generator trained on his top 15 titles to create 30 new ones – a deep post generator that extracts paradoxes, transformation arcs, and action steps – a content idea generator that outputs 60 tweet ideas across proven formats 5. structure swapping he keeps a swipe file of viral posts and tests their structures on new ideas turning one seed into multiple posts. 6. growth loop when a post type drives followers, he doubles down for a few weeks, then moves to the next format. the algorithm shifts, but his system adapts. really cool tutorial. people charge crazy $$$ for this. i give it to you for free on The Startup Ideas Podcast (SIP) 🧃 (follow for more) thanks DAN KOE for being generous sharing your sauce. two hours a day. one system. millions of followers. really cool.
50:41

what if you could turn two hours of AI work into a week of viral content that gets 2M+ impressions/week? every morning, dan koe opens chatgpt/claude and uses them like an internal strategy team and it's paid off through millions of new followers and $$. he feeds them top-performing posts and asks for the hidden patterns like structure, rhythm, curiosity gaps, emotional payoff. from there, he builds a repeatable system that turns 2 hours of work into 7 days of content. his playbook looks like this: 1. validate fast start on twitter. write two or three high-density posts a day. when one hits, that’s your signal. expand it into a newsletter, then a youtube script, then repurpose across linkedin, instagram, threads, and shorts. 2. one source drives all one weekly newsletter becomes the foundation. one youtube video per week comes straight from that outline. the goal is not more ideas—it’s one good idea multiplied. 3. compress research with AI he drops long-form videos into claude or chatgpt and gets six hours of research condensed into a thousand words. he compares it with his own archives to find fresh angles. 4. the prompt stack after writing, he runs everything through a custom set of prompts: – a youtube title generator trained on his top 15 titles to create 30 new ones – a deep post generator that extracts paradoxes, transformation arcs, and action steps – a content idea generator that outputs 60 tweet ideas across proven formats 5. structure swapping he keeps a swipe file of viral posts and tests their structures on new ideas turning one seed into multiple posts. 6. growth loop when a post type drives followers, he doubles down for a few weeks, then moves to the next format. the algorithm shifts, but his system adapts. really cool tutorial. people charge crazy $$$ for this. i give it to you for free on The Startup Ideas Podcast (SIP) 🧃 (follow for more) thanks DAN KOE for being generous sharing your sauce. two hours a day. one system. millions of followers. really cool.

GREG ISENBERG

99,289 views • 10 months ago

🚨 SOMEONE JUST KILLED THE COACHING INDUSTRY a developer spent 22,000 hours building a Personal AI Operating System on top of Claude Code now anyone with a terminal can install it for FREE it knows your goals, remembers every decision you've made, and prepares your morning briefing while you sleep [ the numbers are insane ]: - hours of dev work in it: 22,000 - sessions logged: 6,000 - time saved per day: 2-3 hours - GitHub stars: 12,100 - skills built in: 45 - workflows wired up: 171 - safety hooks: 37 - cost to install: $0 [ the science is wild too ]: no embeddings, no vector databases, no AI magic you can't read every memory, decision, and context lives in plain markdown files you read it with cat, search it with ripgrep, version it with git 4 memory types compound over time: - work memory (active projects, open decisions) - knowledge memory (domain expertise, research) - people memory (contacts, companies, relationships) - learning memory (patterns, mistakes, what works for YOU) every complex task routes through a 7-step cycle: OBSERVE → THINK → PLAN → BUILD → EXECUTE → VERIFY → LEARN privacy is enforced by CODE, not prompts a hook called ContainmentGuard physically blocks sensitive data from being written outside designated zones [ the grift opportunity is even wilder ]: freelancers are already charging $500-2,000 per personal AI setup for executives, founders, and busy operators one person + one weekend = a consulting business that didn't exist 6 months ago every AI productivity app you're paying $30/month for is replaceable by 4 hours of setup work and this one repo REPO: 100% OPEN SOURCE, FREE
0:47

🚨 SOMEONE JUST KILLED THE COACHING INDUSTRY a developer spent 22,000 hours building a Personal AI Operating System on top of Claude Code now anyone with a terminal can install it for FREE it knows your goals, remembers every decision you've made, and prepares your morning briefing while you sleep [ the numbers are insane ]: - hours of dev work in it: 22,000 - sessions logged: 6,000 - time saved per day: 2-3 hours - GitHub stars: 12,100 - skills built in: 45 - workflows wired up: 171 - safety hooks: 37 - cost to install: $0 [ the science is wild too ]: no embeddings, no vector databases, no AI magic you can't read every memory, decision, and context lives in plain markdown files you read it with cat, search it with ripgrep, version it with git 4 memory types compound over time: - work memory (active projects, open decisions) - knowledge memory (domain expertise, research) - people memory (contacts, companies, relationships) - learning memory (patterns, mistakes, what works for YOU) every complex task routes through a 7-step cycle: OBSERVE → THINK → PLAN → BUILD → EXECUTE → VERIFY → LEARN privacy is enforced by CODE, not prompts a hook called ContainmentGuard physically blocks sensitive data from being written outside designated zones [ the grift opportunity is even wilder ]: freelancers are already charging $500-2,000 per personal AI setup for executives, founders, and busy operators one person + one weekend = a consulting business that didn't exist 6 months ago every AI productivity app you're paying $30/month for is replaceable by 4 hours of setup work and this one repo REPO: 100% OPEN SOURCE, FREE

Ronin

614,458 views • 3 months ago

Anthropic's in trouble, again. The entire Claude experience is now available at 1/6th the price. Kimi now does everything Claude does, powered by K2.6, a 1-trillion-parameter MoE model that activates only 32B parameters per token. It covers all three features Claude has (Chat, Code, and Cowork): 1) Kimi Chat runs in four modes - Instant for fast responses - Thinking for deep reasoning - Agent for multi-step execution - and Agent Swarm for parallel workloads. There's a 262K context window across all of them. 2) Kimi Code is the open-source CLI coding agent with K2.6 as the default backend. K2.6 ranked #1 on OpenRouter's programming leaderboard by weekly usage. 3) Kimi Agent is the Cowork equivalent. It generates: - full websites with database and auth - presentation decks (editable PPTX output) - spreadsheets with formulas and charts - word docs and structured research reports. On top of this, Kimi K2.6 is also trained to decompose tasks into up to 300 parallel sub-agents. This helps it retain coherence even across 4,000+ tool calls in a single run, with sessions sustaining up to 13 hours. On SWE-Bench Pro: - Kimi K2.6 → 58.6 - GPT-5.4 xhigh → 57.7 - Gemini 3.1 Pro → 54.2 - Claude Opus 4.6 → 53.4 Kimi K2.6 model is open weights and self-hostable on 4x H100s in INT4. Find the link to the HuggingFace model page in the replies!
0:41

Anthropic's in trouble, again. The entire Claude experience is now available at 1/6th the price. Kimi now does everything Claude does, powered by K2.6, a 1-trillion-parameter MoE model that activates only 32B parameters per token. It covers all three features Claude has (Chat, Code, and Cowork): 1) Kimi Chat runs in four modes - Instant for fast responses - Thinking for deep reasoning - Agent for multi-step execution - and Agent Swarm for parallel workloads. There's a 262K context window across all of them. 2) Kimi Code is the open-source CLI coding agent with K2.6 as the default backend. K2.6 ranked #1 on OpenRouter's programming leaderboard by weekly usage. 3) Kimi Agent is the Cowork equivalent. It generates: - full websites with database and auth - presentation decks (editable PPTX output) - spreadsheets with formulas and charts - word docs and structured research reports. On top of this, Kimi K2.6 is also trained to decompose tasks into up to 300 parallel sub-agents. This helps it retain coherence even across 4,000+ tool calls in a single run, with sessions sustaining up to 13 hours. On SWE-Bench Pro: - Kimi K2.6 → 58.6 - GPT-5.4 xhigh → 57.7 - Gemini 3.1 Pro → 54.2 - Claude Opus 4.6 → 53.4 Kimi K2.6 model is open weights and self-hostable on 4x H100s in INT4. Find the link to the HuggingFace model page in the replies!

Avi Chawla

110,057 views • 3 months ago

A 15-year-old American student made $23,000 in a month without leaving his room while his classmates were playing the same game he was getting paid for. He's not a programmer and never was. He just understood that Epic pays for every minute a player spends on his map - and built a tycoon where people get hooked for an hour at a time. 187,000 minutes of playtime in 30 days. One check from Epic. Claude wrote all the Verse code from his descriptions with zero lines written by hand. 10 hours of work over a weekend and the map was ready to publish. 1,000 players a day at 20 minutes each is already $5,000-15,000 a month from one map. And until end of 2026 Epic gives away 100% from direct item sales on your map on top of that. $722 million already paid out. 58 people became millionaires in 2024. And Epic just removed the only barrier that blocked everyone - now Claude writes the code.
0:46

A 15-year-old American student made $23,000 in a month without leaving his room while his classmates were playing the same game he was getting paid for. He's not a programmer and never was. He just understood that Epic pays for every minute a player spends on his map - and built a tycoon where people get hooked for an hour at a time. 187,000 minutes of playtime in 30 days. One check from Epic. Claude wrote all the Verse code from his descriptions with zero lines written by hand. 10 hours of work over a weekend and the map was ready to publish. 1,000 players a day at 20 minutes each is already $5,000-15,000 a month from one map. And until end of 2026 Epic gives away 100% from direct item sales on your map on top of that. $722 million already paid out. 58 people became millionaires in 2024. And Epic just removed the only barrier that blocked everyone - now Claude writes the code.

Sprytix

3,595,030 views • 3 months ago

Many people still spend hours crafting presentations by hand, but that’s a thing of the past for me. One automated workflow now handles everything from structure, design, and branding to delivery, all in minutes. Here’s how it works: A short form gathers the basics (audience, goal, tone, brand colors) n8n uses GPT-5 to turn that input into a clear, flowing narrative Gamma @GammaApp then builds the full presentation with visuals, layout, and style perfectly aligned with the brand no dragging elements, no fixing fonts, no formatting chaos The finished deck is automatically exported, stored, and drafted into an email for easy sharing no manual follow-ups or file searching What once required: A designer A copywriter A strategist A week of coordination Now runs quietly in the background while you focus on real work. This isn’t about making a single presentation, it’s about creating a repeatable system that scales. Perfect for: Agencies producing client decks Consultants and PMs preparing sessions Once it’s built, every new deck costs next to nothing and stays perfectly consistent.
1:34

Many people still spend hours crafting presentations by hand, but that’s a thing of the past for me. One automated workflow now handles everything from structure, design, and branding to delivery, all in minutes. Here’s how it works: A short form gathers the basics (audience, goal, tone, brand colors) n8n uses GPT-5 to turn that input into a clear, flowing narrative Gamma @GammaApp then builds the full presentation with visuals, layout, and style perfectly aligned with the brand no dragging elements, no fixing fonts, no formatting chaos The finished deck is automatically exported, stored, and drafted into an email for easy sharing no manual follow-ups or file searching What once required: A designer A copywriter A strategist A week of coordination Now runs quietly in the background while you focus on real work. This isn’t about making a single presentation, it’s about creating a repeatable system that scales. Perfect for: Agencies producing client decks Consultants and PMs preparing sessions Once it’s built, every new deck costs next to nothing and stays perfectly consistent.

SARAH

85,672 views • 8 months ago

Someone just posted the full blueprint for an AI swarm that does the job of a 200-person quant research team. Six agents. Running 24/7. Finding brand-new alpha while you sleep. Citadel needs 100 PhDs to do this. Two Sigma needs 200. This does it with six bots and one laptop. Two ways to play this - spend a weekend building your own swarm, or copy the wallet of one that's already up $2M: Boris Cherny runs Claude Code at Anthropic. Two weeks ago he said: "I don't prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops" Alpha research is just a pipeline. So instead of sitting in it, you hand each stage to its own agent: > one reads every new research paper overnight and pulls out the trade idea > one builds the features and cleans the data > one backtests it over 20 years, costs and slippage included > one runs the hard stats and kills anything overfit > one checks it still works in every market regime > one strips out plain momentum and value to see if any real edge is left Each of those six is a job a fund pays a $600,000-a-year quant to do. He runs all six for the price of an API bill. The rule that makes it work: the agent that builds a signal never gets to approve it. A separate, stronger agent tries to kill it first. Whatever survives all six by morning is real, new alpha. One trader's already running this exact swarm on Polymarket. That $2M wallet is public, every trade on-chain. The full build is in the post below - six agents, the tool that runs them, and the five mistakes that kill most people. Bookmark & read this before it's buried.
0:41

Someone just posted the full blueprint for an AI swarm that does the job of a 200-person quant research team. Six agents. Running 24/7. Finding brand-new alpha while you sleep. Citadel needs 100 PhDs to do this. Two Sigma needs 200. This does it with six bots and one laptop. Two ways to play this - spend a weekend building your own swarm, or copy the wallet of one that's already up $2M: Boris Cherny runs Claude Code at Anthropic. Two weeks ago he said: "I don't prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops" Alpha research is just a pipeline. So instead of sitting in it, you hand each stage to its own agent: > one reads every new research paper overnight and pulls out the trade idea > one builds the features and cleans the data > one backtests it over 20 years, costs and slippage included > one runs the hard stats and kills anything overfit > one checks it still works in every market regime > one strips out plain momentum and value to see if any real edge is left Each of those six is a job a fund pays a $600,000-a-year quant to do. He runs all six for the price of an API bill. The rule that makes it work: the agent that builds a signal never gets to approve it. A separate, stronger agent tries to kill it first. Whatever survives all six by morning is real, new alpha. One trader's already running this exact swarm on Polymarket. That $2M wallet is public, every trade on-chain. The full build is in the post below - six agents, the tool that runs them, and the five mistakes that kill most people. Bookmark & read this before it's buried.

cvxv666

103,698 views • 1 month ago

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below
28:49

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Morty

136,663 views • 2 months ago

Ken Griffin, founder of Citadel, the most profitable hedge fund in history, on the moment that left him "shocked and depressed" about AI: "one of our team members built an agentic AI system to recreate academic papers in finance." "we have a legion of young masters and PhDs doing this work. it takes roughly six to eight weeks to reproduce a paper." "my colleague built an AI system that would read a paper, reproduce it, verify the results, produce the results on out of sample data — in about two to three hours per paper." "this is not just a white collar job. this is a master's or PhD-level job. six weeks of work turned into two to three hours." "and then OpenAI just solved a math problem that no one had solved for eighty years." "competitive moats are being filled in at lightning speed." the founder of Citadel watching PhD-level work get compressed from six weeks to two hours. and his response wasn't to cut headcount, it was "i will take every single productivity gain i can get because with the talented people we have, we just have more to go after."
4:06

Ken Griffin, founder of Citadel, the most profitable hedge fund in history, on the moment that left him "shocked and depressed" about AI: "one of our team members built an agentic AI system to recreate academic papers in finance." "we have a legion of young masters and PhDs doing this work. it takes roughly six to eight weeks to reproduce a paper." "my colleague built an AI system that would read a paper, reproduce it, verify the results, produce the results on out of sample data — in about two to three hours per paper." "this is not just a white collar job. this is a master's or PhD-level job. six weeks of work turned into two to three hours." "and then OpenAI just solved a math problem that no one had solved for eighty years." "competitive moats are being filled in at lightning speed." the founder of Citadel watching PhD-level work get compressed from six weeks to two hours. and his response wasn't to cut headcount, it was "i will take every single productivity gain i can get because with the talented people we have, we just have more to go after."

Goshawk Trades

184,125 views • 1 month ago