Загрузка видео...

Не удалось загрузить видео

На главную

It’s a work in progress, but, yes, you can run Claude Code through a Furby. Hardware: • Stock Furby Connect (2016). No mods, just BLE • Mac • USB mic for voice capture BLE (Bleak): • Connects via GATT characteristic to Furby's GeneralPlus chip • Two command types: antenna...

maddiedreese's profile picture

Maddie D. Reese

5,219 subscribers

84,107 просмотров • 5 месяцев назад •via X (Twitter)

ИгрыНаука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,793 просмотров • 5 месяцев назад

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 просмотров • 4 месяцев назад

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.
0:52

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.

Yam Peleg

420,060 просмотров • 9 месяцев назад

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.
0:33

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.

Blaze

55,926 просмотров • 4 месяцев назад

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 просмотров • 4 месяцев назад

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.
25:22

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.

Himanshu Kumar

13,677 просмотров • 5 месяцев назад

Made $530,000 with Ai Bot that started with $313. Didn't know how to code. Now this bots run 24/7 printing money while sleeping. I've made the exact step-by-step guide to build this Claude Code Polymarket trading bot. Prompts. Code. Risk settings. Paper trading checklist. Everything from zero to running bot. It's free. For 24 hours. After that I'm charging $499 for it. To grab it right now: 1. Comment "Claude Bot" 2. Like and Retweet this post 3. Follow me Himanshu Kumar ( I can't send DMs to non-followers ) I'm DMing everyone who Complete the 3 steps. I spent hundreds of thousands hiring developers because he was too scared to learn. Then learned Claude Code. Built algorithmic trading systems. $313 → $530,000. You have the same tools available right now. And you're using them to ask ChatGPT for Instagram captions. This attached video is a goldmine. Full live walkthrough. Claude Code building actual Polymarket trading bots. From zero. Every line of code. Every decision explained. Now let me break down why everything you're doing in trading is wrong and exactly how to fix it. Save this post. You'll hate yourself if you lose it. ↓ Let's start with why you keep losing money. You already know the answer. You just won't admit it. You overtrade. Every. Single. Day. You see a candle move. You feel something. You enter. No plan. No edge. No reason. Just feelings. Then it goes against you. You feel something else. Panic. Anger. Denial. You move your stop loss. Or you didn't set one at all. "It'll come back." It doesn't come back. So you take another trade. A revenge trade. Bigger size this time. Because you need to "make it back." That one fails too. Now you're emotional. Now you're tilted. Now you're using leverage you have no business touching. 40x. 50x. 100x. On a trade you entered because a candle looked "bullish" and some guy on Twitter said "send it." You get liquidated. Close the laptop. Punch something. Tell yourself you'll be "more disciplined" tomorrow. Tomorrow comes. Same cycle. Same result. Same liquidation. You've been doing this for months. Maybe years. And you still think the problem is your strategy. The problem isn't your strategy. The problem is you. Save this post right now. What I'm about to show you is the only way to remove yourself from the equation. Follow Himanshu Kumar so you don't miss any of this. ↓ Here's what's actually killing your account. It's not the market. The market doesn't care about you. It's not your indicators. RSI works fine. MACD works fine. They all "work." It's not your timeframe. It's not your broker. It's not the "manipulation." It's four things: 1. Emotions. You hold losers because hope feels better than loss. You cut winners because fear feels stronger than greed. You size up when angry. You skip trades when scared. Your emotional state determines your position size. That's insane. And you know it's insane. But you keep doing it. 2. Overtrading. You take 15 trades a day. Maybe 5 of them had actual setups. The other 10 were boredom. Boredom trades are the most expensive hobby in human history. 3. Leverage. You use 20x-50x on trades where you're not even sure about the direction. That's not trading. That's a casino with a nicer interface. 4. Fees. You're smashing market orders. Paying spread. Paying commission. On 15 trades a day. Your broker makes more money from your account than you do. Think about that. Your broker is profitable on your account. You're not. You're the product. Not the trader. These four things are why 90% of traders lose. Not bad luck. Not the market. You. Save this post and follow Himanshu Kumar because the solution is coming next. ↓ The solution is painfully obvious. Remove yourself from the equation. Not partially. Not "I'll be more disciplined." Not "I'll journal my trades." Not "I'll meditate before trading." Completely remove yourself. Build a bot. Let the bot trade. You go live your life. The bot doesn't feel emotions. The bot doesn't overtrade. The bot doesn't use reckless leverage. The bot doesn't smash market orders and bleed fees. The bot follows the rules. Every single time. Without exception. Without "just this once." Without "I have a feeling about this one." Rules in. Execution out. No human in the middle to mess everything up. That's algorithmic trading. And before your ego jumps in with "but I'm different, I have discipline" — No you don't. Your account balance proves you don't. If you had discipline, your account would be green. It's not. So you don't. Accept it. Automate it. Move on. This is the hardest truth in trading. Your discipline will always fail. A bot's won't. Save this post. Follow Himanshu Kumar for the exact bot setup that removes your emotions permanently. ↓ "But I don't know how to code." Neither did he. The guy in this video didn't know how to code for most of his life. Got held back in 7th grade. People counted him out early. Spent years building apps and SaaS businesses without writing a single line of code. Hired developers on Upwork instead. Spent hundreds of thousands of dollars paying other people to build what he could have built himself. Because he was scared to learn. That fear cost him years. And hundreds of thousands of dollars. Sound familiar? You're doing the same thing right now. Not with developers. But with your time. You're spending thousands of hours trading manually because you're scared to learn the thing that would make trading automatic. The fear of learning to code is costing you more than any bad trade ever did. Because every month you trade manually is a month of emotional decisions, overleveraged entries, and unnecessary losses that a bot would never make. And here's the thing that should really frustrate you: AI does the hard parts now. You don't need a computer science degree. You don't need to work at a hedge fund. You don't need to be "good at math." Claude Code writes the code for you. You just need to think clearly about trading ideas. That's it. If you can describe a strategy in English, Claude can build it in Python. "I don't know how to code" stopped being a valid excuse in 2024. It's 2026. You're 2 years late on that excuse. Find a new one. Or stop making excuses entirely. Save this post. Follow Himanshu Kumar because I'm showing you how people with zero coding experience are building profitable bots. ↓ The process that actually makes money. Three letters. R. B. I. Research. Backtest. Implement. That's it. That's the entire process. Every single day. Research: Find an idea. A pattern. A market inefficiency. Don't trade it yet. Don't even think about trading it yet. Just research it. Backtest: Test the idea against historical data. Does it work? Not "does it look good on one chart." Does it work across thousands of trades? Across different market conditions? Across in-sample AND out-of-sample data? If no, kill it. Find another idea. If yes, move to step 3. Implement: Build the bot. Deploy it. Paper trade first. Then live with small size. Scale only on evidence. Research. Backtest. Implement. Every day. No exceptions. You know what your current process is? Feel. Enter. Pray. F. E. P. Feel bullish. Enter a trade. Pray it works. That's not a process. That's gambling with a TradingView subscription. RBI is the only process that works. Save this post. Tattoo it on your forearm. Follow Himanshu Kumar for daily RBI breakdowns. ↓ What Claude Code actually does that your manual process can't. You can maybe test 3-5 strategy ideas per week. Manually adjusting parameters. Manually checking results. Manually writing code (badly). Claude Code tests 50-100 ideas per week. With parallel agents running simultaneously. Multiple strategies being built, tested, and validated at the same time. While you sleep. The guy in this video spends 4-8 hours a day building systems with Claude Code. Not trading. Building. Research. Backtest. Implement. Then iterate. Improve. Optimize. Every day the systems get better. Every day the edge compounds. Every day the bots get smarter. While you? You spend 4-8 hours a day staring at charts making the same mistakes you made last month. Same indicators. Same patterns. Same entries. Same losses. He's iterating forward. You're running in circles. Same 8 hours per day. Completely different outcomes. Because he's building systems. And you're feeding a casino. Stop feeding the casino. Start building the machine. Save this post and follow Himanshu Kumar for the Claude Code workflow that iterates strategies while you sleep. ↓ Jim Simons. That's the benchmark. You probably don't know who Jim Simons is. And that tells me everything about how seriously you take trading. Jim Simons. Mathematician. Founded Renaissance Technologies. Built a net worth of $31 billion. 100% from algorithmic trading. Not one single manual trade. Not one "gut feeling" entry. Not one RSI divergence. Not one "smart money concept." Algorithms. Bots. Systems. Data. $31 billion. His fund averaged 66% annual returns for over 30 years. While you're excited about making $200 on a trade that you'll give back tomorrow. The best trader in human history never placed a manual trade in his life. And you think your edge is staring at a 5-minute chart with bloodshot eyes at 2 AM? Your edge is building the system. Not being inside it. Jim Simons is the benchmark. Everything else is noise. Save this post. Follow Himanshu Kumar because I'm building toward the same goal and showing every step publicly. ↓ What you need to understand about patience. This is not get-rich-overnight. The guy in this video says it directly: "This channel is not for people looking to get rich overnight. It's not plug and play. There are no shortcuts. If you're impatient, this probably isn't for you." And that's exactly why most people will fail at this. Because you want results now. Today. This trade. You don't want to spend a week building a bot. You don't want to paper trade for 2 weeks. You don't want to test 50 ideas to find 1 that works. You want to copy someone's bot, run it live with your rent money, and be rich by Friday. That's why you'll be broke by Friday. The guy making $2.3M spent months iterating. Testing. Failing. Rebuilding. Testing again. He was patient when you would have quit. He was calm when you would have panicked. He was consistent when you would have given up. Patience isn't just a virtue in trading. It's the only virtue. Without it, everything else fails. Impatience is the most expensive personality trait in trading. Save this post. Follow Himanshu Kumar and learn to build systems with the patience that actually pays. ↓ The live streams where the real learning happens. The YouTube video is the trailer. The live streams are the movie. Real-time bot building. Real-time questions answered. Real code shown. Real mistakes made and fixed. Not polished highlight reels where everything works perfectly. Actual development. Where things break. Where strategies fail. Where code doesn't compile. Where the fix takes 2 hours. Because that's what real development looks like. And seeing the messy parts is more valuable than any polished tutorial. Because when your bot breaks at 3 AM, you need to know how to fix it. Not just how to celebrate when it works. The streams mix beginner and advanced. Start with how to automate trading. How to use AI for code generation. Then dive into the daily work. Claude Code. Parallel agents. Constant iteration. Live debugging. 4-8 hours of real algorithmic trading development. Live. Uncut. No filter. Most "trading education" shows you the wins. This shows you the work. Save this post. Follow Himanshu Kumar for the stream schedules and breakdowns. ↓ The belief that changes everything. Code is the greatest equalizer. Not money. Not connections. Not a degree. Not where you grew up. Not what school you went to. Code. Once you can build systems, you can build anything. For the rest of your life. A trading bot today. A SaaS product tomorrow. An automation business next month. A completely different life next year. The skill isn't "algorithmic trading." The skill is building systems. And that skill transfers to everything. The guy who can build a trading bot can also build a lead gen tool. Can also build a content pipeline. Can also build a SaaS product. Can also build literally anything that runs on logic and code. One skill. Infinite applications. And AI makes learning it 100x easier than it was 5 years ago. You don't need to be smart. You don't need talent. You need Claude Code and the willingness to sit down and build something instead of consuming content about building something. Building is the skill. Everything else is entertainment disguised as education. Save this post. Follow Himanshu Kumar because I'm showing you how to build, not just how to watch. ↓ If any of this applies to you, pay attention. If you've lost money from overtrading. If you've been liquidated. If you know trading is the vehicle but manual execution keeps crashing you. If you've tried "being more disciplined" and it never lasted more than a week. If you keep saying "next month I'll start automating." If you've spent more money on courses than you've made from trading. There is a better way. It's not a magic indicator. It's not a signal group. It's not a $997 mentorship from a guy who makes money teaching, not trading. It's building your own system. A system that trades without emotion. A system that follows rules without exception. A system that runs while you sleep. A system that compounds while you live your life. That's the answer. It's always been the answer. You've just been too scared to accept that the solution requires building something instead of buying something. ↓ What the next 30 days look like if you actually commit. Week 1: Watch the video. Learn Claude Code basics. Build your first simple strategy. Run your first backtest. Week 2: Iterate. Let Claude improve the strategy. Run Monte Carlo validation. Paper trade. Week 3: Go live with $50-100. Tiny positions. Watch every trade. Compare to paper results. Week 4: Scale based on evidence. Not based on excitement. Not based on one good day. Based on data. 30 days from now you either have a running bot that trades without your emotions destroying every position. Or you're exactly where you are right now. Reading another post. Making another promise. Breaking it by Tuesday. Same 30 days either way. Different actions. Different results. Different life. ↓ Full video tutorial attached. Live bot building with Claude Code. From zero to running Polymarket trading bot. Every line of code. Every decision explained. The video is free. Claude Code is available now. The market is open 24/7. The only thing standing between you and a profitable trading bot is the same thing that's been standing there for months. You. Get out of your own way. Follow Himanshu Kumar for daily AI trading bot breakdowns, live build sessions, and the full RBI process. Save this post. Watch the video. Build the bot. Or keep trading manually and keep losing. The choice has never been easier. And you've never been more stubborn about making the wrong one.
18:53

Made $530,000 with Ai Bot that started with $313. Didn't know how to code. Now this bots run 24/7 printing money while sleeping. I've made the exact step-by-step guide to build this Claude Code Polymarket trading bot. Prompts. Code. Risk settings. Paper trading checklist. Everything from zero to running bot. It's free. For 24 hours. After that I'm charging $499 for it. To grab it right now: 1. Comment "Claude Bot" 2. Like and Retweet this post 3. Follow me Himanshu Kumar ( I can't send DMs to non-followers ) I'm DMing everyone who Complete the 3 steps. I spent hundreds of thousands hiring developers because he was too scared to learn. Then learned Claude Code. Built algorithmic trading systems. $313 → $530,000. You have the same tools available right now. And you're using them to ask ChatGPT for Instagram captions. This attached video is a goldmine. Full live walkthrough. Claude Code building actual Polymarket trading bots. From zero. Every line of code. Every decision explained. Now let me break down why everything you're doing in trading is wrong and exactly how to fix it. Save this post. You'll hate yourself if you lose it. ↓ Let's start with why you keep losing money. You already know the answer. You just won't admit it. You overtrade. Every. Single. Day. You see a candle move. You feel something. You enter. No plan. No edge. No reason. Just feelings. Then it goes against you. You feel something else. Panic. Anger. Denial. You move your stop loss. Or you didn't set one at all. "It'll come back." It doesn't come back. So you take another trade. A revenge trade. Bigger size this time. Because you need to "make it back." That one fails too. Now you're emotional. Now you're tilted. Now you're using leverage you have no business touching. 40x. 50x. 100x. On a trade you entered because a candle looked "bullish" and some guy on Twitter said "send it." You get liquidated. Close the laptop. Punch something. Tell yourself you'll be "more disciplined" tomorrow. Tomorrow comes. Same cycle. Same result. Same liquidation. You've been doing this for months. Maybe years. And you still think the problem is your strategy. The problem isn't your strategy. The problem is you. Save this post right now. What I'm about to show you is the only way to remove yourself from the equation. Follow Himanshu Kumar so you don't miss any of this. ↓ Here's what's actually killing your account. It's not the market. The market doesn't care about you. It's not your indicators. RSI works fine. MACD works fine. They all "work." It's not your timeframe. It's not your broker. It's not the "manipulation." It's four things: 1. Emotions. You hold losers because hope feels better than loss. You cut winners because fear feels stronger than greed. You size up when angry. You skip trades when scared. Your emotional state determines your position size. That's insane. And you know it's insane. But you keep doing it. 2. Overtrading. You take 15 trades a day. Maybe 5 of them had actual setups. The other 10 were boredom. Boredom trades are the most expensive hobby in human history. 3. Leverage. You use 20x-50x on trades where you're not even sure about the direction. That's not trading. That's a casino with a nicer interface. 4. Fees. You're smashing market orders. Paying spread. Paying commission. On 15 trades a day. Your broker makes more money from your account than you do. Think about that. Your broker is profitable on your account. You're not. You're the product. Not the trader. These four things are why 90% of traders lose. Not bad luck. Not the market. You. Save this post and follow Himanshu Kumar because the solution is coming next. ↓ The solution is painfully obvious. Remove yourself from the equation. Not partially. Not "I'll be more disciplined." Not "I'll journal my trades." Not "I'll meditate before trading." Completely remove yourself. Build a bot. Let the bot trade. You go live your life. The bot doesn't feel emotions. The bot doesn't overtrade. The bot doesn't use reckless leverage. The bot doesn't smash market orders and bleed fees. The bot follows the rules. Every single time. Without exception. Without "just this once." Without "I have a feeling about this one." Rules in. Execution out. No human in the middle to mess everything up. That's algorithmic trading. And before your ego jumps in with "but I'm different, I have discipline" — No you don't. Your account balance proves you don't. If you had discipline, your account would be green. It's not. So you don't. Accept it. Automate it. Move on. This is the hardest truth in trading. Your discipline will always fail. A bot's won't. Save this post. Follow Himanshu Kumar for the exact bot setup that removes your emotions permanently. ↓ "But I don't know how to code." Neither did he. The guy in this video didn't know how to code for most of his life. Got held back in 7th grade. People counted him out early. Spent years building apps and SaaS businesses without writing a single line of code. Hired developers on Upwork instead. Spent hundreds of thousands of dollars paying other people to build what he could have built himself. Because he was scared to learn. That fear cost him years. And hundreds of thousands of dollars. Sound familiar? You're doing the same thing right now. Not with developers. But with your time. You're spending thousands of hours trading manually because you're scared to learn the thing that would make trading automatic. The fear of learning to code is costing you more than any bad trade ever did. Because every month you trade manually is a month of emotional decisions, overleveraged entries, and unnecessary losses that a bot would never make. And here's the thing that should really frustrate you: AI does the hard parts now. You don't need a computer science degree. You don't need to work at a hedge fund. You don't need to be "good at math." Claude Code writes the code for you. You just need to think clearly about trading ideas. That's it. If you can describe a strategy in English, Claude can build it in Python. "I don't know how to code" stopped being a valid excuse in 2024. It's 2026. You're 2 years late on that excuse. Find a new one. Or stop making excuses entirely. Save this post. Follow Himanshu Kumar because I'm showing you how people with zero coding experience are building profitable bots. ↓ The process that actually makes money. Three letters. R. B. I. Research. Backtest. Implement. That's it. That's the entire process. Every single day. Research: Find an idea. A pattern. A market inefficiency. Don't trade it yet. Don't even think about trading it yet. Just research it. Backtest: Test the idea against historical data. Does it work? Not "does it look good on one chart." Does it work across thousands of trades? Across different market conditions? Across in-sample AND out-of-sample data? If no, kill it. Find another idea. If yes, move to step 3. Implement: Build the bot. Deploy it. Paper trade first. Then live with small size. Scale only on evidence. Research. Backtest. Implement. Every day. No exceptions. You know what your current process is? Feel. Enter. Pray. F. E. P. Feel bullish. Enter a trade. Pray it works. That's not a process. That's gambling with a TradingView subscription. RBI is the only process that works. Save this post. Tattoo it on your forearm. Follow Himanshu Kumar for daily RBI breakdowns. ↓ What Claude Code actually does that your manual process can't. You can maybe test 3-5 strategy ideas per week. Manually adjusting parameters. Manually checking results. Manually writing code (badly). Claude Code tests 50-100 ideas per week. With parallel agents running simultaneously. Multiple strategies being built, tested, and validated at the same time. While you sleep. The guy in this video spends 4-8 hours a day building systems with Claude Code. Not trading. Building. Research. Backtest. Implement. Then iterate. Improve. Optimize. Every day the systems get better. Every day the edge compounds. Every day the bots get smarter. While you? You spend 4-8 hours a day staring at charts making the same mistakes you made last month. Same indicators. Same patterns. Same entries. Same losses. He's iterating forward. You're running in circles. Same 8 hours per day. Completely different outcomes. Because he's building systems. And you're feeding a casino. Stop feeding the casino. Start building the machine. Save this post and follow Himanshu Kumar for the Claude Code workflow that iterates strategies while you sleep. ↓ Jim Simons. That's the benchmark. You probably don't know who Jim Simons is. And that tells me everything about how seriously you take trading. Jim Simons. Mathematician. Founded Renaissance Technologies. Built a net worth of $31 billion. 100% from algorithmic trading. Not one single manual trade. Not one "gut feeling" entry. Not one RSI divergence. Not one "smart money concept." Algorithms. Bots. Systems. Data. $31 billion. His fund averaged 66% annual returns for over 30 years. While you're excited about making $200 on a trade that you'll give back tomorrow. The best trader in human history never placed a manual trade in his life. And you think your edge is staring at a 5-minute chart with bloodshot eyes at 2 AM? Your edge is building the system. Not being inside it. Jim Simons is the benchmark. Everything else is noise. Save this post. Follow Himanshu Kumar because I'm building toward the same goal and showing every step publicly. ↓ What you need to understand about patience. This is not get-rich-overnight. The guy in this video says it directly: "This channel is not for people looking to get rich overnight. It's not plug and play. There are no shortcuts. If you're impatient, this probably isn't for you." And that's exactly why most people will fail at this. Because you want results now. Today. This trade. You don't want to spend a week building a bot. You don't want to paper trade for 2 weeks. You don't want to test 50 ideas to find 1 that works. You want to copy someone's bot, run it live with your rent money, and be rich by Friday. That's why you'll be broke by Friday. The guy making $2.3M spent months iterating. Testing. Failing. Rebuilding. Testing again. He was patient when you would have quit. He was calm when you would have panicked. He was consistent when you would have given up. Patience isn't just a virtue in trading. It's the only virtue. Without it, everything else fails. Impatience is the most expensive personality trait in trading. Save this post. Follow Himanshu Kumar and learn to build systems with the patience that actually pays. ↓ The live streams where the real learning happens. The YouTube video is the trailer. The live streams are the movie. Real-time bot building. Real-time questions answered. Real code shown. Real mistakes made and fixed. Not polished highlight reels where everything works perfectly. Actual development. Where things break. Where strategies fail. Where code doesn't compile. Where the fix takes 2 hours. Because that's what real development looks like. And seeing the messy parts is more valuable than any polished tutorial. Because when your bot breaks at 3 AM, you need to know how to fix it. Not just how to celebrate when it works. The streams mix beginner and advanced. Start with how to automate trading. How to use AI for code generation. Then dive into the daily work. Claude Code. Parallel agents. Constant iteration. Live debugging. 4-8 hours of real algorithmic trading development. Live. Uncut. No filter. Most "trading education" shows you the wins. This shows you the work. Save this post. Follow Himanshu Kumar for the stream schedules and breakdowns. ↓ The belief that changes everything. Code is the greatest equalizer. Not money. Not connections. Not a degree. Not where you grew up. Not what school you went to. Code. Once you can build systems, you can build anything. For the rest of your life. A trading bot today. A SaaS product tomorrow. An automation business next month. A completely different life next year. The skill isn't "algorithmic trading." The skill is building systems. And that skill transfers to everything. The guy who can build a trading bot can also build a lead gen tool. Can also build a content pipeline. Can also build a SaaS product. Can also build literally anything that runs on logic and code. One skill. Infinite applications. And AI makes learning it 100x easier than it was 5 years ago. You don't need to be smart. You don't need talent. You need Claude Code and the willingness to sit down and build something instead of consuming content about building something. Building is the skill. Everything else is entertainment disguised as education. Save this post. Follow Himanshu Kumar because I'm showing you how to build, not just how to watch. ↓ If any of this applies to you, pay attention. If you've lost money from overtrading. If you've been liquidated. If you know trading is the vehicle but manual execution keeps crashing you. If you've tried "being more disciplined" and it never lasted more than a week. If you keep saying "next month I'll start automating." If you've spent more money on courses than you've made from trading. There is a better way. It's not a magic indicator. It's not a signal group. It's not a $997 mentorship from a guy who makes money teaching, not trading. It's building your own system. A system that trades without emotion. A system that follows rules without exception. A system that runs while you sleep. A system that compounds while you live your life. That's the answer. It's always been the answer. You've just been too scared to accept that the solution requires building something instead of buying something. ↓ What the next 30 days look like if you actually commit. Week 1: Watch the video. Learn Claude Code basics. Build your first simple strategy. Run your first backtest. Week 2: Iterate. Let Claude improve the strategy. Run Monte Carlo validation. Paper trade. Week 3: Go live with $50-100. Tiny positions. Watch every trade. Compare to paper results. Week 4: Scale based on evidence. Not based on excitement. Not based on one good day. Based on data. 30 days from now you either have a running bot that trades without your emotions destroying every position. Or you're exactly where you are right now. Reading another post. Making another promise. Breaking it by Tuesday. Same 30 days either way. Different actions. Different results. Different life. ↓ Full video tutorial attached. Live bot building with Claude Code. From zero to running Polymarket trading bot. Every line of code. Every decision explained. The video is free. Claude Code is available now. The market is open 24/7. The only thing standing between you and a profitable trading bot is the same thing that's been standing there for months. You. Get out of your own way. Follow Himanshu Kumar for daily AI trading bot breakdowns, live build sessions, and the full RBI process. Save this post. Watch the video. Build the bot. Or keep trading manually and keep losing. The choice has never been easier. And you've never been more stubborn about making the wrong one.

Himanshu Kumar

38,153 просмотров • 5 месяцев назад

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.
51:48

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.

Jeffrey Emanuel

25,483 просмотров • 8 месяцев назад

is our AI project to make computing feel more human L A N D E R Here are the 4 best demo videos of the magic of DATA in action. DATA is a personalized assistant who knows and remembers every conversation you have with it accross your iPhone, Mac, iPad, Watch, Texts, Emails, and HomePods. You can talk to DATA right in your AirPods or text it just like a person. DATA can read, write, understand, speak any language, and translate between them. It can help with real work and home life tasks like research, writing, scheduling, reminders, and triage. And it's easily customizable so you can have DATA automatically do whatever you want whenever you want with just a few taps and natural language instructions - no code required. DATA can do just about anything you can do on your phone on your behalf automatically including very advanced things Siri can't, like summarizing, analyzing, and drafting replies or writing documents. It can read web pages, texts or emails you show it, or PDFs of any kind. It can do other real world tasks that require complex analysis and common sense too, like: - figure out where the nearest beach is (even when you're in Colorado) and instantly fetch the current surf report up to the current minute. - summarize and drafting replies to entire email chains - plan out entire work projects or multi-day vacations on your calendar - sketch out ideas for you in picture form or drafting Notion pages with charts and graphs. DATA can also use its own judgement to determine when to run an action or not, even if you've scheduled it, allowing you to make VERY complex automations that require many different inputs to make a decision, like for example: - only opening the blinds on your lunch break if it's sunny out and you're working from home. DATA works natively and easily with Apple HomeKit & other shortcuts. DATA can also take initiative and check in with you throughout the day by voice or text and proactively send messages to you and others on your behalf based on your personal and professional goals, current tasks, and calendar. DATA can integrate with many apps on your phone, and is compatible with multiple large AI language models. I've gotten to make a few demo videos that I think really capture how powerful DATA can be for every day life. Here they are all in one tweet. Make sure your sound is on as you watch them. 1. This is the first demo video I ever made from April 19th, 2023. It walks through all the ways you can interact with and use the DATA shortcuts. Everything from saying "Hey Siri" to tapping on custom apps on your home-screen. 2. The second demo video was made May 5 and is an example use case I made of how commands work - commands allow DATA to actually run actions on your phone like taking pictures and sending messages. This demo shows me taking a picture of an email template, and data drafting an email based on that template. It's gotten much better at realizing when it has just run a command and incorporating that information naturally into the conversation now, especially on GPT-4. 3. This third Commands video, May 12 is a walkthrough of ALL the phone functions that commands allow DATA to do: sending texts and emails, making pictures, seeing pictures, reading things, and scheduling events. Since this video we've added auto-replies to texts and emails, summarizing documents, writing documents, health app data retrieval, web surfing, scheduling alarms, making playlists, and more. 4. This last demo I made today, June 15, shows everything DATA does working in concert to generate a crazy detailed morning briefing with background music - including making a unique playlist and giving a detailed analysis of current events complete with Ski & Surf conditions near me other live information from the internet. So now that you've seen everything DATA can do, what's the coolest feature? What features should we add? What would you use DATA for first?
12:54

is our AI project to make computing feel more human L A N D E R Here are the 4 best demo videos of the magic of DATA in action. DATA is a personalized assistant who knows and remembers every conversation you have with it accross your iPhone, Mac, iPad, Watch, Texts, Emails, and HomePods. You can talk to DATA right in your AirPods or text it just like a person. DATA can read, write, understand, speak any language, and translate between them. It can help with real work and home life tasks like research, writing, scheduling, reminders, and triage. And it's easily customizable so you can have DATA automatically do whatever you want whenever you want with just a few taps and natural language instructions - no code required. DATA can do just about anything you can do on your phone on your behalf automatically including very advanced things Siri can't, like summarizing, analyzing, and drafting replies or writing documents. It can read web pages, texts or emails you show it, or PDFs of any kind. It can do other real world tasks that require complex analysis and common sense too, like: - figure out where the nearest beach is (even when you're in Colorado) and instantly fetch the current surf report up to the current minute. - summarize and drafting replies to entire email chains - plan out entire work projects or multi-day vacations on your calendar - sketch out ideas for you in picture form or drafting Notion pages with charts and graphs. DATA can also use its own judgement to determine when to run an action or not, even if you've scheduled it, allowing you to make VERY complex automations that require many different inputs to make a decision, like for example: - only opening the blinds on your lunch break if it's sunny out and you're working from home. DATA works natively and easily with Apple HomeKit & other shortcuts. DATA can also take initiative and check in with you throughout the day by voice or text and proactively send messages to you and others on your behalf based on your personal and professional goals, current tasks, and calendar. DATA can integrate with many apps on your phone, and is compatible with multiple large AI language models. I've gotten to make a few demo videos that I think really capture how powerful DATA can be for every day life. Here they are all in one tweet. Make sure your sound is on as you watch them. 1. This is the first demo video I ever made from April 19th, 2023. It walks through all the ways you can interact with and use the DATA shortcuts. Everything from saying "Hey Siri" to tapping on custom apps on your home-screen. 2. The second demo video was made May 5 and is an example use case I made of how commands work - commands allow DATA to actually run actions on your phone like taking pictures and sending messages. This demo shows me taking a picture of an email template, and data drafting an email based on that template. It's gotten much better at realizing when it has just run a command and incorporating that information naturally into the conversation now, especially on GPT-4. 3. This third Commands video, May 12 is a walkthrough of ALL the phone functions that commands allow DATA to do: sending texts and emails, making pictures, seeing pictures, reading things, and scheduling events. Since this video we've added auto-replies to texts and emails, summarizing documents, writing documents, health app data retrieval, web surfing, scheduling alarms, making playlists, and more. 4. This last demo I made today, June 15, shows everything DATA does working in concert to generate a crazy detailed morning briefing with background music - including making a unique playlist and giving a detailed analysis of current events complete with Ski & Surf conditions near me other live information from the internet. So now that you've seen everything DATA can do, what's the coolest feature? What features should we add? What would you use DATA for first?

steve

640,176 просмотров • 3 лет назад

Made $313 → $2,382,780 in 4 Days Using a Claude AI Bot on Polymarket. 26,738 trades. 98% win rate. Full blockchain proof. Every single trade verifiable on-chain. I've made the exact step-by-step guide to build this Claude Polymarket bot from scratch. You've been trading for 3 years. Still red. He gave Claude $313. Woke up rich. Free for 24 hours. To get this Setup guide: 1. Comment "Money" 2. Like and Retweet 3. Follow me Himanshu Kumar (so i can DM you) Full 2-hour video tutorial attached. Every single click and command explained. Beginner to running bot. Now let me break down exactly how this works. Save this post. This is the most important trading breakdown you'll ever read. ↓ Let's start with the number that should make you sick. $313. That's what this wallet started with. Not $50,000. Not $10,000. Not even $1,000. $313. Less than your monthly Netflix + Uber Eats + Spotify combined. 4 months later: $2,382,780.80. That's a 7,942x return. While you spent those same 4 months staring at charts, drawing trendlines, panic selling, revenge trading, and ending the month exactly where you started. Minus the $200 you lost on that "sure thing." Same 4 months. Same market. Same opportunities. He had a bot. You had feelings. Guess who won. Save this post right now. What I'm about to explain is the exact mechanism behind every dollar of that $2.38M. Follow Himanshu Kumar so you don't miss the rest. ↓ How Polymarket actually works and why bots print money on it. Polymarket is a prediction market. Will BTC be higher in 15 minutes? Yes or No. Will the Fed raise rates? Yes or No. You buy shares between $0 and $1. If you're right, your share settles at $1. If you're wrong, it settles at $0. Simple. Now here's where it gets interesting. Polymarket updates its prices SLOWER than the real market moves. When BTC drops 0.6% on Binance, Polymarket still shows old odds for about 2.7 seconds. 2.7 seconds. In those 2.7 seconds, the bot already knows the outcome. It's not predicting. It's not guessing. It's reading information that already exists and trading before Polymarket catches up. That's not trading. That's collecting free money with a 2.7 second head start. And you're over there using a 15-indicator TradingView setup trying to "predict" where BTC goes next. The bot doesn't predict anything. It just reads faster than you. That's the entire edge. Save this post because if you understand this one concept you understand how millionaires are being made on Polymarket right now. Follow Himanshu Kumar for more breakdowns like this. ↓ Let me walk you through one single trade. A new 15-minute BTC contract opens on Polymarket. Odds are 50/50. Fair price. 10 minutes in, BTC drops 0.6% on Binance. Hard, fast move. The real probability of BTC being lower at expiry is now about 78%. Polymarket still shows 54/46. The bot sees this instantly. Binance WebSocket feed. Under 50ms latency. The edge is 24 percentage points. On a binary contract, that's basically free money. Bot calculates position size using Kelly Criterion. Executes via Polymarket's API. Done. Within 2-3 seconds, other participants update the odds. 54/46 moves toward 78/22. Bot either exits for immediate profit or holds to resolution. Either way, the trade was entered with near-certainty of a positive outcome. Now repeat this 200-500 times per day. $313 → $2,382,780 in 4 months. Not magic. Not prediction. Not luck. Industrial-scale exploitation of a market inefficiency that still exists today. And you're still placing one manual trade per day and calling yourself a "trader." This is the mechanism behind every single dollar. Bookmark this post so you can study it again. Follow Himanshu Kumar because I'm breaking down each strategy separately. ↓ There are 4 strategies. Not all Claude bots do the same thing. Strategy 1: Latency Arbitrage. Win rate: 85-98%. What 0x8dxd used. Monitor Binance price feeds. When Polymarket odds lag behind reality by 3-5%, buy the correct side before the market corrects. No forecasting. No model. No sentiment analysis. Pure speed. You're not guessing. You're reading an outcome that has already happened. Strategy 2: Oracle Arbitrage. Win rate: 78-85%. Chainlink oracle price feeds occasionally diverge from Polymarket's implied prices. When they do, the settlement direction is known. Fewer opportunities. Higher certainty when they appear. Strategy 3: News-Driven Trading. Win rate: 60-75%. Claude ingests real-time news. Government filings. Central bank statements. On-chain data. Assesses probability impact before retail traders even finish reading the headline. Lower win rate because interpretation introduces uncertainty. But works on ANY market category, not just crypto. Strategy 4: Market Making. Return: 2-5% per month. Place buy and sell orders on both sides. Capture the spread. No prediction required. Most consistent. Hardest to blow up. Compounds aggressively over time. You didn't even know there were 4 strategies. You thought "trading bot" meant one thing. That's how far behind you are. 4 strategies. 4 different risk profiles. 4 ways to make money while you sleep. Save this post. Follow Himanshu Kumar for the deep dive into each one. ↓ The timeline that should haunt you. December 2025: Bot launches with $313. Nobody notices. January 6, 2026: Wallet hits ~$438,000. 140x in 30 days. 6,615 predictions. 98% win rate. Finbold reports it. Crypto Twitter explodes. March 10, 2026: Head-to-head test. Claude bot: $1,000 → $14,216 in 48 hours. +1,322%. OpenClaw bot: fully liquidated. Same market. Same timeframe. Claude won because of better risk management. OpenClaw died because it overleveraged. March 16, 2026: Someone trains a swarm model on 3 years of NBA data. Result: +$1.49M on Polymarket. April 2026: 0x8dxd final verified balance: $2,382,780.80. 26,738 trades. 4 months. This all happened while you were "waiting for the right time to start." The right time was December 2025. The second best time is right now. But you'll probably wait until it's too late. That's what you always do. Every date on this timeline is a day you could have started but didn't. Save this post. Follow Himanshu Kumar so you at least start today. ↓ Why Claude and not ChatGPT? This isn't opinion. It's data. March 2026 head-to-head: Claude bot: +1,322%. OpenClaw (GPT-based): liquidated. Same prompt. Same market. Same conditions. Researchers found Claude's code included: > More defensive edge cases > More conservative default parameters > Better error handling > More legible code for debugging > Proper Kelly Criterion position sizing > Hard drawdown kill switches ChatGPT's code overleveraged into a losing sequence and couldn't recover. Claude's code sized positions conservatively, stopped trading when drawdown thresholds hit, and survived to compound another day. The difference between +1,322% and liquidation wasn't the strategy. It was the risk management. And Claude writes better risk management than ChatGPT. That's not a debate. That's a $15,216 difference in 48 hours. But sure, keep using ChatGPT because "everyone uses it." Everyone's broke too. Coincidence? Stop using the popular tool. Start using the profitable one. Save this post. Follow Himanshu Kumar for more Claude vs ChatGPT comparisons with real data. ↓ Why humans lose to bots. Every single time. Same strategy. Same market. Same period. Bots: ~$206,000 profit. Humans: ~$100,000 profit. 2x gap. Same strategy. Here's why: 1. Late entries. By the time you identify the lag, verify your reasoning, and click buy, the 2.7 second window is gone. The bot executes in under 100ms. You execute in 30 seconds. The opportunity doesn't exist for 30 seconds. 2. Emotional sizing. You oversize when "confident." Undersize when scared. Exact opposite of Kelly math. The bot sizes based on edge. Every time. No feelings. 3. Fatigue. You make worse decisions at hour 6 than at hour 1. The bot makes the same decision at hour 72 that it made at hour 1. 4. Drawdown psychology. After 3 losses you either panic quit or double down trying to recover. Both destroy capital. The bot has a kill switch. It stops. It doesn't feel anything. You're not competing with other humans anymore. You're competing with machines that don't sleep, don't feel, don't flinch. And you're losing. The data doesn't lie. Humans lose to bots 2x on the same strategy. Save this post. Follow Himanshu Kumar for the complete bot setup that removes you from the equation. ↓ What can go wrong. Because I'm not going to lie to you. Most people who build this bot will NOT 7,942x their money. Some will lose their initial capital. Here's what can kill you: Edge compression. The arbitrage window was 12 seconds in 2024. It's 2.7 seconds now. It's shrinking. At some point it hits zero for retail operators. This is a time-limited opportunity. Not a permanent income stream. Rule changes. Polymarket can change contract mechanics, settlement rules, or API terms overnight. What worked yesterday can lose money tomorrow. Risk management bugs. A 98% win rate strategy with broken position sizing will blow up your account on the one losing trade. The March 2026 experiment proved this. Claude survived. OpenClaw got liquidated. Same strategy. Different risk management. That's why the 2-hour video tutorial walks through every single risk parameter. Because the strategy doesn't kill you. Bad risk management kills you. This is the section most "gurus" delete. I'm keeping it because I'd rather you make money safely than blow up and blame me. Save this post. Follow Himanshu Kumar for honest breakdowns, not hype. ↓ The step-by-step to build your own. Step 1: Set up a Polymarket wallet. Fund with USDC via Polygon network. Start with $100-$300 for testing. Step 2: Generate API credentials. CLOB API key from docs.polymarket .com. Store private key in environment variable. Never hardcode it. Never share it. Step 3: Prompt Claude to build the bot. Use Claude Code for best results. It reads your filesystem, executes code, and iterates on errors autonomously. Step 4: Paper trade for at least one week. Minimum 200 completed trades. Win rate must be above 70% before going live. This step is NOT optional. Step 5: Configure risk management. Max single position: 8% of portfolio. Daily loss limit: -20% with auto halt. Kill switch at -40% drawdown. Telegram alerts on every threshold. Step 6: Go live small. $1-5 per trade. Watch every trade for first week. Compare to paper results. Scale only on evidence. Skip steps 4 and 5 and you will lose your money. That's not a warning. That's a guarantee. This is your complete build guide. Save this post. Follow Himanshu Kumar because I'll be posting the exact Claude prompts for each strategy. ↓ The edge exists right now. Not next month. Not "when you're ready." Right now. The arbitrage window is 2.7 seconds. It was 12 seconds in 2024. It's shrinking every week. Every day you wait, more bots enter the space. The window gets smaller. Your potential returns get smaller. The bots already running have a compounding advantage. They're making money today that they'll use to make more money tomorrow. You're reading about it and telling yourself "I'll look into this next weekend." That's what you said last weekend. And the weekend before that. The best time to start was 6 months ago. The second best time is today. But you already know you're going to bookmark this and never open it again. Prove me wrong. ↓ Full 2-hour video tutorial attached. Every single click. Every command. Every parameter. From zero to running bot. Beginner friendly. Nothing skipped. A similar bot has already earned $2,382,780. Full blockchain proof in the article below. The video is free. The tools are free. The edge still exists. The only thing that costs money is another month of doing nothing while bots eat every opportunity you're too slow to catch. Follow Himanshu Kumar for the complete series covering every automated income stream using Claude. Prediction markets are just the beginning. Save this post. Bookmark it. Screenshot it. Whatever you need to do so you actually watch the video and build the bot instead of just reading about people who did. You Must Follow me Himanshu Kumar, so i can send you DM.
2:22:35

Made $313 → $2,382,780 in 4 Days Using a Claude AI Bot on Polymarket. 26,738 trades. 98% win rate. Full blockchain proof. Every single trade verifiable on-chain. I've made the exact step-by-step guide to build this Claude Polymarket bot from scratch. You've been trading for 3 years. Still red. He gave Claude $313. Woke up rich. Free for 24 hours. To get this Setup guide: 1. Comment "Money" 2. Like and Retweet 3. Follow me Himanshu Kumar (so i can DM you) Full 2-hour video tutorial attached. Every single click and command explained. Beginner to running bot. Now let me break down exactly how this works. Save this post. This is the most important trading breakdown you'll ever read. ↓ Let's start with the number that should make you sick. $313. That's what this wallet started with. Not $50,000. Not $10,000. Not even $1,000. $313. Less than your monthly Netflix + Uber Eats + Spotify combined. 4 months later: $2,382,780.80. That's a 7,942x return. While you spent those same 4 months staring at charts, drawing trendlines, panic selling, revenge trading, and ending the month exactly where you started. Minus the $200 you lost on that "sure thing." Same 4 months. Same market. Same opportunities. He had a bot. You had feelings. Guess who won. Save this post right now. What I'm about to explain is the exact mechanism behind every dollar of that $2.38M. Follow Himanshu Kumar so you don't miss the rest. ↓ How Polymarket actually works and why bots print money on it. Polymarket is a prediction market. Will BTC be higher in 15 minutes? Yes or No. Will the Fed raise rates? Yes or No. You buy shares between $0 and $1. If you're right, your share settles at $1. If you're wrong, it settles at $0. Simple. Now here's where it gets interesting. Polymarket updates its prices SLOWER than the real market moves. When BTC drops 0.6% on Binance, Polymarket still shows old odds for about 2.7 seconds. 2.7 seconds. In those 2.7 seconds, the bot already knows the outcome. It's not predicting. It's not guessing. It's reading information that already exists and trading before Polymarket catches up. That's not trading. That's collecting free money with a 2.7 second head start. And you're over there using a 15-indicator TradingView setup trying to "predict" where BTC goes next. The bot doesn't predict anything. It just reads faster than you. That's the entire edge. Save this post because if you understand this one concept you understand how millionaires are being made on Polymarket right now. Follow Himanshu Kumar for more breakdowns like this. ↓ Let me walk you through one single trade. A new 15-minute BTC contract opens on Polymarket. Odds are 50/50. Fair price. 10 minutes in, BTC drops 0.6% on Binance. Hard, fast move. The real probability of BTC being lower at expiry is now about 78%. Polymarket still shows 54/46. The bot sees this instantly. Binance WebSocket feed. Under 50ms latency. The edge is 24 percentage points. On a binary contract, that's basically free money. Bot calculates position size using Kelly Criterion. Executes via Polymarket's API. Done. Within 2-3 seconds, other participants update the odds. 54/46 moves toward 78/22. Bot either exits for immediate profit or holds to resolution. Either way, the trade was entered with near-certainty of a positive outcome. Now repeat this 200-500 times per day. $313 → $2,382,780 in 4 months. Not magic. Not prediction. Not luck. Industrial-scale exploitation of a market inefficiency that still exists today. And you're still placing one manual trade per day and calling yourself a "trader." This is the mechanism behind every single dollar. Bookmark this post so you can study it again. Follow Himanshu Kumar because I'm breaking down each strategy separately. ↓ There are 4 strategies. Not all Claude bots do the same thing. Strategy 1: Latency Arbitrage. Win rate: 85-98%. What 0x8dxd used. Monitor Binance price feeds. When Polymarket odds lag behind reality by 3-5%, buy the correct side before the market corrects. No forecasting. No model. No sentiment analysis. Pure speed. You're not guessing. You're reading an outcome that has already happened. Strategy 2: Oracle Arbitrage. Win rate: 78-85%. Chainlink oracle price feeds occasionally diverge from Polymarket's implied prices. When they do, the settlement direction is known. Fewer opportunities. Higher certainty when they appear. Strategy 3: News-Driven Trading. Win rate: 60-75%. Claude ingests real-time news. Government filings. Central bank statements. On-chain data. Assesses probability impact before retail traders even finish reading the headline. Lower win rate because interpretation introduces uncertainty. But works on ANY market category, not just crypto. Strategy 4: Market Making. Return: 2-5% per month. Place buy and sell orders on both sides. Capture the spread. No prediction required. Most consistent. Hardest to blow up. Compounds aggressively over time. You didn't even know there were 4 strategies. You thought "trading bot" meant one thing. That's how far behind you are. 4 strategies. 4 different risk profiles. 4 ways to make money while you sleep. Save this post. Follow Himanshu Kumar for the deep dive into each one. ↓ The timeline that should haunt you. December 2025: Bot launches with $313. Nobody notices. January 6, 2026: Wallet hits ~$438,000. 140x in 30 days. 6,615 predictions. 98% win rate. Finbold reports it. Crypto Twitter explodes. March 10, 2026: Head-to-head test. Claude bot: $1,000 → $14,216 in 48 hours. +1,322%. OpenClaw bot: fully liquidated. Same market. Same timeframe. Claude won because of better risk management. OpenClaw died because it overleveraged. March 16, 2026: Someone trains a swarm model on 3 years of NBA data. Result: +$1.49M on Polymarket. April 2026: 0x8dxd final verified balance: $2,382,780.80. 26,738 trades. 4 months. This all happened while you were "waiting for the right time to start." The right time was December 2025. The second best time is right now. But you'll probably wait until it's too late. That's what you always do. Every date on this timeline is a day you could have started but didn't. Save this post. Follow Himanshu Kumar so you at least start today. ↓ Why Claude and not ChatGPT? This isn't opinion. It's data. March 2026 head-to-head: Claude bot: +1,322%. OpenClaw (GPT-based): liquidated. Same prompt. Same market. Same conditions. Researchers found Claude's code included: > More defensive edge cases > More conservative default parameters > Better error handling > More legible code for debugging > Proper Kelly Criterion position sizing > Hard drawdown kill switches ChatGPT's code overleveraged into a losing sequence and couldn't recover. Claude's code sized positions conservatively, stopped trading when drawdown thresholds hit, and survived to compound another day. The difference between +1,322% and liquidation wasn't the strategy. It was the risk management. And Claude writes better risk management than ChatGPT. That's not a debate. That's a $15,216 difference in 48 hours. But sure, keep using ChatGPT because "everyone uses it." Everyone's broke too. Coincidence? Stop using the popular tool. Start using the profitable one. Save this post. Follow Himanshu Kumar for more Claude vs ChatGPT comparisons with real data. ↓ Why humans lose to bots. Every single time. Same strategy. Same market. Same period. Bots: ~$206,000 profit. Humans: ~$100,000 profit. 2x gap. Same strategy. Here's why: 1. Late entries. By the time you identify the lag, verify your reasoning, and click buy, the 2.7 second window is gone. The bot executes in under 100ms. You execute in 30 seconds. The opportunity doesn't exist for 30 seconds. 2. Emotional sizing. You oversize when "confident." Undersize when scared. Exact opposite of Kelly math. The bot sizes based on edge. Every time. No feelings. 3. Fatigue. You make worse decisions at hour 6 than at hour 1. The bot makes the same decision at hour 72 that it made at hour 1. 4. Drawdown psychology. After 3 losses you either panic quit or double down trying to recover. Both destroy capital. The bot has a kill switch. It stops. It doesn't feel anything. You're not competing with other humans anymore. You're competing with machines that don't sleep, don't feel, don't flinch. And you're losing. The data doesn't lie. Humans lose to bots 2x on the same strategy. Save this post. Follow Himanshu Kumar for the complete bot setup that removes you from the equation. ↓ What can go wrong. Because I'm not going to lie to you. Most people who build this bot will NOT 7,942x their money. Some will lose their initial capital. Here's what can kill you: Edge compression. The arbitrage window was 12 seconds in 2024. It's 2.7 seconds now. It's shrinking. At some point it hits zero for retail operators. This is a time-limited opportunity. Not a permanent income stream. Rule changes. Polymarket can change contract mechanics, settlement rules, or API terms overnight. What worked yesterday can lose money tomorrow. Risk management bugs. A 98% win rate strategy with broken position sizing will blow up your account on the one losing trade. The March 2026 experiment proved this. Claude survived. OpenClaw got liquidated. Same strategy. Different risk management. That's why the 2-hour video tutorial walks through every single risk parameter. Because the strategy doesn't kill you. Bad risk management kills you. This is the section most "gurus" delete. I'm keeping it because I'd rather you make money safely than blow up and blame me. Save this post. Follow Himanshu Kumar for honest breakdowns, not hype. ↓ The step-by-step to build your own. Step 1: Set up a Polymarket wallet. Fund with USDC via Polygon network. Start with $100-$300 for testing. Step 2: Generate API credentials. CLOB API key from docs.polymarket .com. Store private key in environment variable. Never hardcode it. Never share it. Step 3: Prompt Claude to build the bot. Use Claude Code for best results. It reads your filesystem, executes code, and iterates on errors autonomously. Step 4: Paper trade for at least one week. Minimum 200 completed trades. Win rate must be above 70% before going live. This step is NOT optional. Step 5: Configure risk management. Max single position: 8% of portfolio. Daily loss limit: -20% with auto halt. Kill switch at -40% drawdown. Telegram alerts on every threshold. Step 6: Go live small. $1-5 per trade. Watch every trade for first week. Compare to paper results. Scale only on evidence. Skip steps 4 and 5 and you will lose your money. That's not a warning. That's a guarantee. This is your complete build guide. Save this post. Follow Himanshu Kumar because I'll be posting the exact Claude prompts for each strategy. ↓ The edge exists right now. Not next month. Not "when you're ready." Right now. The arbitrage window is 2.7 seconds. It was 12 seconds in 2024. It's shrinking every week. Every day you wait, more bots enter the space. The window gets smaller. Your potential returns get smaller. The bots already running have a compounding advantage. They're making money today that they'll use to make more money tomorrow. You're reading about it and telling yourself "I'll look into this next weekend." That's what you said last weekend. And the weekend before that. The best time to start was 6 months ago. The second best time is today. But you already know you're going to bookmark this and never open it again. Prove me wrong. ↓ Full 2-hour video tutorial attached. Every single click. Every command. Every parameter. From zero to running bot. Beginner friendly. Nothing skipped. A similar bot has already earned $2,382,780. Full blockchain proof in the article below. The video is free. The tools are free. The edge still exists. The only thing that costs money is another month of doing nothing while bots eat every opportunity you're too slow to catch. Follow Himanshu Kumar for the complete series covering every automated income stream using Claude. Prediction markets are just the beginning. Save this post. Bookmark it. Screenshot it. Whatever you need to do so you actually watch the video and build the bot instead of just reading about people who did. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

53,768 просмотров • 5 месяцев назад

Use this prompt in OpenClaw to create your own AI agent command center that syncs up your life like Tony Stark's Jarvis in Iron Man. Adapt the specifics (agent names, data sources, branding) below to your own setup. Prompt: Build me a mission control dashboard for my OpenClaw AI agent system. Stack: Next.js 15 (App Router) + Convex (real-time backend) + Tailwind CSS v4 + Framer Motion + ShadCN UI + Lucide icons. TypeScript throughout. This is the command center where I monitor and control my autonomous AI agent(s) running on OpenClaw. The agent operates 24/7 on a Mac Mini, connected to Telegram/Discord, running cron jobs, spawning sub-agents, and reading/writing to a filesystem-based memory and state system. Dark mode only. Ultra-premium aesthetic, think Iron Man's JARVIS HUD meets a Bloomberg terminal. Subtle glass effects (backdrop-blur-xl, bg-white/[0.03]), no heavy gradients or glow. Rounded corners (16-20px on cards). Framer Motion for page transitions, stagger animations on card grids, spring physics on interactions. Mobile-first responsive. Never cookie-cutter. ## Architecture The dashboard reads live data from TWO sources: 1. **Convex**: real-time database for structured data (tasks, contacts, content drafts, calendar events, activity logs) 2. **Local API routes** (`/api/*`): read files from the agent's workspace filesystem at `~/.openclaw/workspace/` and return JSON. This is how live system state flows into the dashboard. ## Pages & Views (8 nav items, some with tab sub-views) ### 1. HOME (`/`) Dashboard overview. Grid of live status cards: - **System Health**: read from `/api/system-state` (parses `state/servers.json`). Show each service with UP/DOWN indicator, port, last check time. - **Agent Status**: read from `/api/agents` (parses `agents/registry.json` + agent workspace files). Show active agent count, healthy/unhealthy ratio, active sub-agent count from OpenClaw sessions API. - **Cron Health**: read from `/api/cron-health` (parses `state/crons.json`). Table of all scheduled jobs with name, schedule, last status (green/red dot), consecutive errors. - **Revenue Tracker**: read from `/api/revenue` (parses `state/revenue.json`). Current revenue, monthly burn, net. - **Content Pipeline**: read from `/api/content-pipeline` (parses `content/queue.md`). Kanban-style: Draft | Review | Approved | Published counts. - **Quick Stats**: total tasks, pending approvals, active sessions, uptime. All panels auto-refresh every 15 seconds. Live indicator dot + "AUTO 15S" badge in header. ### 2. OPS (`/ops`) with 3 tabs: Operations | Tasks | Calendar **Operations tab:** Full operational view. Server health table, branch status (from `state/branch-check.json`), observations feed (from `state/observations.md`), system priorities (from `shared-context/priorities.md`). **Tasks tab:** Strategic task suggestion system. API route `/api/suggested-tasks` reads/writes `state/suggested-tasks.json`. Cards grouped by category (Revenue, Product, Community, Content, Operations, Clients, Trading, Brand) with emoji headers. Each card shows title, reasoning, next action, priority badge, effort badge, approve/reject buttons. Filter bar by status and category. **Calendar tab:** Weekly calendar view from Convex `calendarEvents` table. Drag-to-create, color-coded by type, time slots. ### 3. AGENTS (`/agents`) with 2 tabs: Agents | Models **Agents tab:** Card grid of all registered agents from `/api/agents`. Each card shows name, role, model, level (L1-L4), status. Cards are CLICKABLE: expanding into a detail panel showing: - Agent personality (reads their SOUL .md) - Capabilities and rules (reads their RULES .md) - Sub-agents they can spawn - Recent outputs (reads from `shared-context/agent-outputs/`) **Models tab:** Model inventory table showing all available models, their routing (which tasks go to which model), costs, and failover chains. ### 4. CHAT (`/chat`): 2 tabs: Chat | Command **Chat tab:** Chat interface to communicate with the agent. Left sidebar shows session list (from `/api/chat-history` reading .jsonl transcript files). Main area shows messages with role-aligned bubbles (user right, assistant left), date separators, channel badges (telegram/discord/webchat). Input bar with send button + voice input (Web Speech API with SpeechRecognition). Messages sent via `/api/chat-send` which queues to a file the agent reads. **Command tab:** Quick command interface for common operations. ### 5. CONTENT (`/content`) Content pipeline management. Read from Convex `contentDrafts` table AND `/api/content-pipeline`. Show drafts in kanban columns. Each card shows title, platform target, draft text preview, status, created date. Edit/approve/reject actions. ### 6. COMMS (`/comms`) with 2 tabs: Comms | CRM **Comms tab:** Communication hub showing recent Discord digest, Telegram messages, notification history. **CRM tab:** Client pipeline kanban (Prospect → Contacted → Meeting → Proposal → Active). API route `/api/clients` reads markdown files from `clients/` directory. Each card shows client name, status, contacts, last interaction, next action. ### 7. KNOWLEDGE (`/knowledge`) with 2 tabs: Knowledge | Ecosystem **Knowledge tab:** Searchable knowledge base. Global search across all workspace files using `/api/knowledge` endpoint. **Ecosystem tab:** Product grid showing all products/apps in the ecosystem. Each card shows product name, status (Active/Development/Concept), health indicator, key metrics. Cards link to `/ecosystem/[slug]` detail pages with tabbed views (Overview, Brand, Community, Content, Legal, Product, Website, Actions). Detail pages read from `/api/ecosystem/[slug]` which parses workspace memory files. ### 8. CODE (`/code`) Code pipeline view. Shows repositories from `/api/repos` (scans ~/Desktop/Projects/ for git repos). Each repo card shows name, branch, last commit, dirty file count, language breakdown. Detail view at `/api/repos/detail` shows recent commits, file tree, open PRs. ## Navigation Top horizontal nav bar, NOT sidebar. All 8 items visible at all viewport widths. Use `flex` layout with `flex-1` items. Text size uses `clamp(0.45rem, 0.75vw, 0.6875rem)` for fluid scaling. Active item gets `text-primary bg-primary/[0.06]` static highlight (no sliding animation). Agent/app name visible at md+ breakpoints (`hidden md:inline`). Tab sub-views use a reusable `TabBar` component with pill/glass styling and Framer Motion `layoutId` transitions. Tab state stored in URL via `?tab=` search params. ## API Routes (all under `src/app/api/`) Each API route reads from the agent's workspace filesystem and returns JSON: - `/api/system-state` → reads `state/servers.json`, `state/branch-check.json` - `/api/agents` → reads `agents/registry.json`, agent SOUL .md files - `/api/agents/[id]` → reads specific agent's SOUL .md, RULES .md, outputs - `/api/cron-health` → reads `state/crons.json` - `/api/revenue` → reads `state/revenue.json` - `/api/content-pipeline` → parses `content/queue.md` (markdown with status markers) - `/api/suggested-tasks` → GET (read) / POST (approve/reject) on `state/suggested-tasks.json` - `/api/observations` → reads `state/observations.md` - `/api/priorities` → reads `shared-context/priorities.md` - `/api/chat-history` → reads .jsonl transcript files with pagination/search/channel filter - `/api/chat-send` → writes to queue file - `/api/clients` → reads markdown files from `clients/` directory - `/api/ecosystem/[slug]` → reads memory files for specific ecosystem - `/api/repos` → scans project directories for git repos - `/api/health` → returns status, uptime, memory usage, Convex connectivity All filesystem paths should be configurable via environment variable (default: `~/.openclaw/workspace/`). ## Convex Schema Define tables for: activities, calendarEvents, tasks, contacts, contentDrafts, ecosystemProducts. Include seed scripts (`convex/seed.ts`) to populate initial data. ## Key Design Rules - Mobile-first, test at 320px minimum - Font sizes 10-14px for body text, everything must fit naturally at small viewports - Cards use consistent border radius (16-20px) - Glass cards: `bg-white/[0.03] backdrop-blur-xl border border-white/[0.06]` - No heavy blur blobs or grain overlays - Stagger animations on card grids (0.05s delay per item) - Skeleton loading states for all async data - Custom scrollbar styling - Empty states with helpful messaging - All text must use Inter or system font stack - Never mix sharp and rounded corners in the same view - Premium = lighter feel, more whitespace, less visual noise ## File Structure ``` src/ app/ page.tsx, layout.tsx, providers.tsx agents/page.tsx calendar/page.tsx chat/page.tsx code/page.tsx comms/page.tsx content/page.tsx ecosystem/page.tsx, ecosystem/[slug]/page.tsx knowledge/page.tsx ops/page.tsx api/[...all routes above] components/ nav.tsx tab-bar.tsx dashboard-overview.tsx ops-view.tsx, suggested-tasks-view.tsx agents-view.tsx, models-view.tsx chat-center-view.tsx, voice-input.tsx content-view.tsx comms-view.tsx, crm-view.tsx knowledge-base.tsx, ecosystem-view.tsx code-pipeline.tsx activity-feed.tsx, calendar-view.tsx ui/ (ShadCN primitives) hooks/ lib/ convex/ schema.ts functions for each table seed.ts ``` Build the complete application. Every component, every API route, every Convex function. Production-quality code and premium design, not stubs. Dark mode only. Make it look incredibly beautiful and premium, no cookie cutter UI / AI slop.
1:14

Use this prompt in OpenClaw to create your own AI agent command center that syncs up your life like Tony Stark's Jarvis in Iron Man. Adapt the specifics (agent names, data sources, branding) below to your own setup. Prompt: Build me a mission control dashboard for my OpenClaw AI agent system. Stack: Next.js 15 (App Router) + Convex (real-time backend) + Tailwind CSS v4 + Framer Motion + ShadCN UI + Lucide icons. TypeScript throughout. This is the command center where I monitor and control my autonomous AI agent(s) running on OpenClaw. The agent operates 24/7 on a Mac Mini, connected to Telegram/Discord, running cron jobs, spawning sub-agents, and reading/writing to a filesystem-based memory and state system. Dark mode only. Ultra-premium aesthetic, think Iron Man's JARVIS HUD meets a Bloomberg terminal. Subtle glass effects (backdrop-blur-xl, bg-white/[0.03]), no heavy gradients or glow. Rounded corners (16-20px on cards). Framer Motion for page transitions, stagger animations on card grids, spring physics on interactions. Mobile-first responsive. Never cookie-cutter. ## Architecture The dashboard reads live data from TWO sources: 1. **Convex**: real-time database for structured data (tasks, contacts, content drafts, calendar events, activity logs) 2. **Local API routes** (`/api/*`): read files from the agent's workspace filesystem at `~/.openclaw/workspace/` and return JSON. This is how live system state flows into the dashboard. ## Pages & Views (8 nav items, some with tab sub-views) ### 1. HOME (`/`) Dashboard overview. Grid of live status cards: - **System Health**: read from `/api/system-state` (parses `state/servers.json`). Show each service with UP/DOWN indicator, port, last check time. - **Agent Status**: read from `/api/agents` (parses `agents/registry.json` + agent workspace files). Show active agent count, healthy/unhealthy ratio, active sub-agent count from OpenClaw sessions API. - **Cron Health**: read from `/api/cron-health` (parses `state/crons.json`). Table of all scheduled jobs with name, schedule, last status (green/red dot), consecutive errors. - **Revenue Tracker**: read from `/api/revenue` (parses `state/revenue.json`). Current revenue, monthly burn, net. - **Content Pipeline**: read from `/api/content-pipeline` (parses `content/queue.md`). Kanban-style: Draft | Review | Approved | Published counts. - **Quick Stats**: total tasks, pending approvals, active sessions, uptime. All panels auto-refresh every 15 seconds. Live indicator dot + "AUTO 15S" badge in header. ### 2. OPS (`/ops`) with 3 tabs: Operations | Tasks | Calendar **Operations tab:** Full operational view. Server health table, branch status (from `state/branch-check.json`), observations feed (from `state/observations.md`), system priorities (from `shared-context/priorities.md`). **Tasks tab:** Strategic task suggestion system. API route `/api/suggested-tasks` reads/writes `state/suggested-tasks.json`. Cards grouped by category (Revenue, Product, Community, Content, Operations, Clients, Trading, Brand) with emoji headers. Each card shows title, reasoning, next action, priority badge, effort badge, approve/reject buttons. Filter bar by status and category. **Calendar tab:** Weekly calendar view from Convex `calendarEvents` table. Drag-to-create, color-coded by type, time slots. ### 3. AGENTS (`/agents`) with 2 tabs: Agents | Models **Agents tab:** Card grid of all registered agents from `/api/agents`. Each card shows name, role, model, level (L1-L4), status. Cards are CLICKABLE: expanding into a detail panel showing: - Agent personality (reads their SOUL .md) - Capabilities and rules (reads their RULES .md) - Sub-agents they can spawn - Recent outputs (reads from `shared-context/agent-outputs/`) **Models tab:** Model inventory table showing all available models, their routing (which tasks go to which model), costs, and failover chains. ### 4. CHAT (`/chat`): 2 tabs: Chat | Command **Chat tab:** Chat interface to communicate with the agent. Left sidebar shows session list (from `/api/chat-history` reading .jsonl transcript files). Main area shows messages with role-aligned bubbles (user right, assistant left), date separators, channel badges (telegram/discord/webchat). Input bar with send button + voice input (Web Speech API with SpeechRecognition). Messages sent via `/api/chat-send` which queues to a file the agent reads. **Command tab:** Quick command interface for common operations. ### 5. CONTENT (`/content`) Content pipeline management. Read from Convex `contentDrafts` table AND `/api/content-pipeline`. Show drafts in kanban columns. Each card shows title, platform target, draft text preview, status, created date. Edit/approve/reject actions. ### 6. COMMS (`/comms`) with 2 tabs: Comms | CRM **Comms tab:** Communication hub showing recent Discord digest, Telegram messages, notification history. **CRM tab:** Client pipeline kanban (Prospect → Contacted → Meeting → Proposal → Active). API route `/api/clients` reads markdown files from `clients/` directory. Each card shows client name, status, contacts, last interaction, next action. ### 7. KNOWLEDGE (`/knowledge`) with 2 tabs: Knowledge | Ecosystem **Knowledge tab:** Searchable knowledge base. Global search across all workspace files using `/api/knowledge` endpoint. **Ecosystem tab:** Product grid showing all products/apps in the ecosystem. Each card shows product name, status (Active/Development/Concept), health indicator, key metrics. Cards link to `/ecosystem/[slug]` detail pages with tabbed views (Overview, Brand, Community, Content, Legal, Product, Website, Actions). Detail pages read from `/api/ecosystem/[slug]` which parses workspace memory files. ### 8. CODE (`/code`) Code pipeline view. Shows repositories from `/api/repos` (scans ~/Desktop/Projects/ for git repos). Each repo card shows name, branch, last commit, dirty file count, language breakdown. Detail view at `/api/repos/detail` shows recent commits, file tree, open PRs. ## Navigation Top horizontal nav bar, NOT sidebar. All 8 items visible at all viewport widths. Use `flex` layout with `flex-1` items. Text size uses `clamp(0.45rem, 0.75vw, 0.6875rem)` for fluid scaling. Active item gets `text-primary bg-primary/[0.06]` static highlight (no sliding animation). Agent/app name visible at md+ breakpoints (`hidden md:inline`). Tab sub-views use a reusable `TabBar` component with pill/glass styling and Framer Motion `layoutId` transitions. Tab state stored in URL via `?tab=` search params. ## API Routes (all under `src/app/api/`) Each API route reads from the agent's workspace filesystem and returns JSON: - `/api/system-state` → reads `state/servers.json`, `state/branch-check.json` - `/api/agents` → reads `agents/registry.json`, agent SOUL .md files - `/api/agents/[id]` → reads specific agent's SOUL .md, RULES .md, outputs - `/api/cron-health` → reads `state/crons.json` - `/api/revenue` → reads `state/revenue.json` - `/api/content-pipeline` → parses `content/queue.md` (markdown with status markers) - `/api/suggested-tasks` → GET (read) / POST (approve/reject) on `state/suggested-tasks.json` - `/api/observations` → reads `state/observations.md` - `/api/priorities` → reads `shared-context/priorities.md` - `/api/chat-history` → reads .jsonl transcript files with pagination/search/channel filter - `/api/chat-send` → writes to queue file - `/api/clients` → reads markdown files from `clients/` directory - `/api/ecosystem/[slug]` → reads memory files for specific ecosystem - `/api/repos` → scans project directories for git repos - `/api/health` → returns status, uptime, memory usage, Convex connectivity All filesystem paths should be configurable via environment variable (default: `~/.openclaw/workspace/`). ## Convex Schema Define tables for: activities, calendarEvents, tasks, contacts, contentDrafts, ecosystemProducts. Include seed scripts (`convex/seed.ts`) to populate initial data. ## Key Design Rules - Mobile-first, test at 320px minimum - Font sizes 10-14px for body text, everything must fit naturally at small viewports - Cards use consistent border radius (16-20px) - Glass cards: `bg-white/[0.03] backdrop-blur-xl border border-white/[0.06]` - No heavy blur blobs or grain overlays - Stagger animations on card grids (0.05s delay per item) - Skeleton loading states for all async data - Custom scrollbar styling - Empty states with helpful messaging - All text must use Inter or system font stack - Never mix sharp and rounded corners in the same view - Premium = lighter feel, more whitespace, less visual noise ## File Structure ``` src/ app/ page.tsx, layout.tsx, providers.tsx agents/page.tsx calendar/page.tsx chat/page.tsx code/page.tsx comms/page.tsx content/page.tsx ecosystem/page.tsx, ecosystem/[slug]/page.tsx knowledge/page.tsx ops/page.tsx api/[...all routes above] components/ nav.tsx tab-bar.tsx dashboard-overview.tsx ops-view.tsx, suggested-tasks-view.tsx agents-view.tsx, models-view.tsx chat-center-view.tsx, voice-input.tsx content-view.tsx comms-view.tsx, crm-view.tsx knowledge-base.tsx, ecosystem-view.tsx code-pipeline.tsx activity-feed.tsx, calendar-view.tsx ui/ (ShadCN primitives) hooks/ lib/ convex/ schema.ts functions for each table seed.ts ``` Build the complete application. Every component, every API route, every Convex function. Production-quality code and premium design, not stubs. Dark mode only. Make it look incredibly beautiful and premium, no cookie cutter UI / AI slop.

klöss

202,296 просмотров • 7 месяцев назад

The most epic 13 minute AI rant I've heard in 2026 PS: My parent's heard this when I was playing it in the car and thought Jason ✨👾SaaStr.Ai✨ Lemkin went OFF like Stephen A Smith does on first take PPS: Full transcript below [17:00] Harry Stebbings: I I just wanted to ask Jason, if the people that we want are fundamentally different, the developers that we used to hire, we don't because AI writes the code for us. The marketers we don't want, the sales people we don't want—who who do we want genuinely? Like what is the attractive profile? Because your Anthropic’s and your OpenAIs are hiring, so so what are the people that we want in the companies of the future? [17:18] Jason Lemkin: Look, I know it sounds trite, but but the answer is simple. It's just the expression each year changes. We want folks that are genuinely AI fluent. It's pretty simple. Now you know, maybe last year we called them prompt engineers, right? That used to be a job. I don't know if you remember that actually used to be the hottest job on planet earth. Now no one needs a prompt engineer because it's pretty easy to prompt all these tools. That job died. Okay. Um and now we need go-to-market engineers. Um I think that job's going to die. We need—everyone needs so many forward deployed engineers. Like you can't hire enough forward deployed engineers. But uh you know um but Palantir just announced in whatever their their big their big event—they've gotten their deployment times down over 90% with forward deployed engineers. So that may become—so the this wave of disruption for the titles and the specificity, it's also exhaustingly accelerating. But it's really simple. You meet anyone for any role—sales, marketing, engineering, product, QA—they're they're either they're either they can't keep all of the ways they use AI to accelerate their job from spewing out of their mouth, or they're staring at you. It's there's nowhere in the middle. Like, and the person that comes in and says—it's it's it sounds Captain Obvious—but like, you know, you just had the whatever from Lovable, the the marketing head that was super popular on the show, right? She's just spewing AI-native insights into Lovable, right? It's not that complicated. You hire her, Elena, or whatever it is. You just hire her. It doesn't matter whether she's still in college or a junior or a senior or a middler, a left or right. And honestly, if you interview people, I would say of all even of the best startups I've invested in, maybe 30% of the management team meets this standard at best. 30%. Maybe less. And of the interviews I do in general, it's single-digit percents. It's just and in in that sense, it's the same as ever. Like you either lower the bar in hiring or you hire someone that's actually great. And someone that's actually great is so far ahead of you in how to apply to to employ the efficiencies of AI in their role, your jaw falls on the table. The difference is we used to need warm bodies. That's what's changing. We used to need warm bodies to answer the call, to do QA, to do code review, to to get the blue pixel to go from the upper left to the lower right. You laugh, but you need you literally needed to brute force this with humans. With AI, every day that goes by, the AI—you do not need brute force human beings on your team. And that's another reason they're shrinking. Why are all these new companies so efficient? They're just not brute forcing things with humans. They're just not. They're choosing not to. And so these team—all the brute forcers out there—everyone talks about how bloated teams got in 2021. I don't agree with that. I think they got as big as they needed to be when growth was high and you needed humans to do everything. All you look at these teams that that doubled—well if growth continued at 60% like the rate in early 2021 for 5 years or can help me do the math and every single thing a software company did required a human. You were understaffed by your 2021 headcount. You'd be sitting here in 2026. You every office in SoMa would be triple packed and you there wouldn't be enough humans to staff your company. It's just the world changed. [20:33] Harry Stebbings: Jason, you live on the bleeding edge. I think me and Rory see that and I think the world sees that when they hear you every week in terms of how you run SaaS. For all of the CEOs and execs who listen to the show, what would you advise them in terms of determining whether someone is AI fluent when they meet them for jobs, for talent? [20:51] Jason Lemkin: Here's I realized I was just asked this. I just did a review with a super fast startup growing just crossing 100 million and I was asked this question. And one of my favorite executives, I thought his answer was pretty dated and because he gave me an answer that was about 6 months old. The answer 6 months old is: "I look for folks in my team, I look for you know at what tools they play with." Okay, that was a great answer in like summer of 2025. Okay, I tried Lovable last week. Okay, the answer in 2026 is: "What commercial AI tool have you brought into your organization this month?" That's the test. Anyone that is on the bleeding edge that you would want to hire—now there are so many great products in the market. Okay, there is no excuse in any role to have not brought one tool a month into your organization. Okay, there—now there's going to be better and better tools and better and better products as the year goes on. What's the one you did? And you will see folks with their deer in the headlights to this question. What what sales tool? What marketing tool? What product tool? What engineering tool? What did you bring in? Why did you pick it? How does it working? Because if you're at remotely at the cutting edge, you're all over this. You're looking for the next agentic tools that will radically improve how you do business. This is—you think everyone thinks SaaS is at the bleeding edge, right? You know, you know, all we do is we're just looking for the tools and trying them. Okay? Okay, we're one year ahead of everybody else because we did the simplest thing in the world. Like we tried the tools early and we trained them. We trained them for a month. Okay, I'll give you—want hear a horrible example from this week? Super hot AI company valued at 6 billion. Okay, I'm not going to name it. Um, this week yesterday told us we had to quadruple what we spent on their product. Okay, their agent told us, right? And why did this happen? Okay. Well, at this $6 billion company, no one had trained the agent on its pricing properly. No one had tested it. They said, "Well, well, we've been in beta." And we said, "Well, when did the beta launch? A year ago." Okay, these are people asleep at at the wheel. You want somebody who the instant this comes up, they exactly know what the issue is. And "Hey, when I was at Lovable Replit, we trained the agent. This is how we did it. I brought in this tool. I brought in this tool that that Rory invested in last week. It solved all these issues." That's what you want to hear. And if they haven't brought in a tool in the last 30 days, at least deeply evaluated it. I don't really care whether they bought it, but gone so far down the funnel they can tell you—pick whatever tool: Fixie, Regie, GC, AIGC—I don't care how you went through it, you looked at it, you can tell me the eight ways it would improve the productivity of your business and three you didn't. Just don't hire that person because they're going to run your company to the ground. This is the job today. The job today is not to screw around on ChatGPT and to be a prompt engineer. The job today is to bring the best AI and agentic products into your organization and leverage all the hard work that the engineers have done building those products. That's your job. You don't have to screw around. You don't have to be a prompt engineer anymore. You have to be an agent deployment expert. A—this is the new job we're making up today. An Agentic Deployment Expert. That's your job from C-level to junior. Agentic Deployment Expert. Don't hire anybody else. You're going to regret it. They're going to stare at the camera. He's good. Stare at the camera. He's honorable. We could probably just I could slip away, get a coffee, and come back. No. And I I sound exasperated, Rory. And I—but the reason I am is I can just see I can see my best companies doing it. And I can see some companies I've invested in not doing it. And I want to cry. I just want to cry when they have no ADs on their team. I just—like you're flushing your years of your life down the toilet by not approaching your how you're building this company this way. [24:33] Rory: Yes. And at the risk of being positive, it's worth pointing out two things he didn't say. Well, something implicit why he said—Jason didn't do the only hire, you know, he didn't commit the um employment law, I think it's a civil penalty of saying only employ people below X who get the new new thing because he implicitly said anyone can do it provided you're willing to learn. And I think that's the big aha that's one of the positive statements to make here right? Look and I think it applies—I'm always wary of being "Hey, coming across, hey this this is the things that you all have to do." I think it applies to everyone including investors right? I mean I will say I have found that unless you're willing to invest the time learning these tools you actually shouldn't be investing in them. One of my partners Andy had this expression: "You know, if you decide you want to stop learning new things you probably should retire within 6 to 12 months and never write another check again." Maybe that's down to 3 to 6 months at this stage, right? And I think, you know, it's— [25:27] Harry Stebbings: Yeah, I actually I actually had a meeting with mine and Jason's biggest investor the other day and I—pretend he's not here—I said I think he's the most equipped investor for this generation of investing because I don't think anyone quite sits at the bleeding edge like he does on the investor side. [25:42] Harry Stebbings: Why in terms of using the equip stuff? Yeah. Yeah. In terms of using the stuff, understanding understanding bottlenecks, constraints. For sure. [25:51] Jason Lemkin: But can I just add one point? We can just cuz it's so important if it helps people. Okay, we are—and thank you Harry. We're going through these phases. Okay, and when AI started to blow up for real for us, uh call it early 2024, right? Maybe late '23, I wasn't equipped. It was too technical. I wasn't going to go in and figure out—I wasn't smart enough to figure out how to deal with a massively hallucinating LLM API and turn that and turn that into something magical. Kudos to investors and others that that got it in early '23, '22. I mean I remember I—I guess it was maybe SaaStr Annual '23. I was with David Sacks and I did a Q&A and I said, "How you thinking about AI at Craft?" He's like, "Well we're all in. We want 80% of '23 of investments to be AI." I'm like, "Great but like show me the show me the great ones in market." He's like, "They're all prototypes. We're all they're all they're all proof of concepts but we're all in anyway." That's where you kind of had to be in '23 if you weren't investing at like the LLM level. Okay, I wasn't smart enough. Then we went through this weird-ass prompt engineer era where like you you could torture these products to do something good, right? But you had to torture them. You had to like craft these crazy things that made no sense. Now we are in the era where mere ordinarily smart generalists can make these tools do magical things. And literally I go to these meetings and people be like, "I don't know how to like this is so scary. I don't know how to do this." And we show them our backends. Do you know how to do a workflow generator? Do you know how to do a a decision tree? Like we've been building these since software in the '90s. Okay, if you—I can show you all of our agents. The how they work is novel. They do have to be trained. You can't be lazy and have these agents work. But honestly, the the UI, the UX, the way we interact with them, it's just software. And so my point is: Pick yourself off the ground. This is your time now. If you felt lost in AI era, if you felt like you're behind, you don't understand what all these people are saying on X and Twitter and their Claude and and their and talking about all the 4.6 point Nano point and it's over—like you just it's not your world. This is your time. This is your time for the generalist that knows how to use software tools really really well. And I—this is my last point but it's so important. If ever in your recent life—and this is why you could be all you need to be is young at heart to Rory's point—if in the last three to five years you have successfully deployed a piece of enterprise software of any sort you yourself, not some agency you hired, but if you have deployed it, you can deploy any agentic tool. Any. And you can become the hero in your company and you can become the hero in your functional area. But I watch folks—I'm literally helping a company now that they're adding hundreds of sales folks this year with a new pre-IPO COO—he's not hasn't brought in a single tool, totally scared of it. Okay, it's not that hard. Did you use SalesLoft? Did you use Outreach? Did you use HubSpot? Do you know these tools? If you can deploy these tools, you can deploy a world-changing AI agent. And so this is the time for people like the folks that that were shut out of the AI revolution right now. The generalist folks that are not that know how to deploy software that don't even know how to build software. Like vibe coding for me was folks who knew how to build software, but you didn't have to be an engineer. Now, you just need to know how to deploy software to win with AI agents. That's all you need to know. So many people have these skills and they're petrified of AI. "How did you do that? How did you deploy an AI BDR?" Well, we bought a piece of software, we figured out how it worked for a day, we set it up in an afternoon, and then and then we did spend 30 months training it, which you didn't do with this old software because in the old days, we just had to manually upload all the data, right? And there was no training. The the only non-intuitive part is training these things. And it's it's it's just work. So that's why when I see folks on the management team not doing this, there's no excuse. You do not need to be technical to win with AI agents in Q2 of '26. You do not need to be even 1% technical. Not at all. So it's your time. Or you're going to get laid off. Or you're going to get laid off because you're not going to matter.
13:04

The most epic 13 minute AI rant I've heard in 2026 PS: My parent's heard this when I was playing it in the car and thought Jason ✨👾SaaStr.Ai✨ Lemkin went OFF like Stephen A Smith does on first take PPS: Full transcript below [17:00] Harry Stebbings: I I just wanted to ask Jason, if the people that we want are fundamentally different, the developers that we used to hire, we don't because AI writes the code for us. The marketers we don't want, the sales people we don't want—who who do we want genuinely? Like what is the attractive profile? Because your Anthropic’s and your OpenAIs are hiring, so so what are the people that we want in the companies of the future? [17:18] Jason Lemkin: Look, I know it sounds trite, but but the answer is simple. It's just the expression each year changes. We want folks that are genuinely AI fluent. It's pretty simple. Now you know, maybe last year we called them prompt engineers, right? That used to be a job. I don't know if you remember that actually used to be the hottest job on planet earth. Now no one needs a prompt engineer because it's pretty easy to prompt all these tools. That job died. Okay. Um and now we need go-to-market engineers. Um I think that job's going to die. We need—everyone needs so many forward deployed engineers. Like you can't hire enough forward deployed engineers. But uh you know um but Palantir just announced in whatever their their big their big event—they've gotten their deployment times down over 90% with forward deployed engineers. So that may become—so the this wave of disruption for the titles and the specificity, it's also exhaustingly accelerating. But it's really simple. You meet anyone for any role—sales, marketing, engineering, product, QA—they're they're either they're either they can't keep all of the ways they use AI to accelerate their job from spewing out of their mouth, or they're staring at you. It's there's nowhere in the middle. Like, and the person that comes in and says—it's it's it sounds Captain Obvious—but like, you know, you just had the whatever from Lovable, the the marketing head that was super popular on the show, right? She's just spewing AI-native insights into Lovable, right? It's not that complicated. You hire her, Elena, or whatever it is. You just hire her. It doesn't matter whether she's still in college or a junior or a senior or a middler, a left or right. And honestly, if you interview people, I would say of all even of the best startups I've invested in, maybe 30% of the management team meets this standard at best. 30%. Maybe less. And of the interviews I do in general, it's single-digit percents. It's just and in in that sense, it's the same as ever. Like you either lower the bar in hiring or you hire someone that's actually great. And someone that's actually great is so far ahead of you in how to apply to to employ the efficiencies of AI in their role, your jaw falls on the table. The difference is we used to need warm bodies. That's what's changing. We used to need warm bodies to answer the call, to do QA, to do code review, to to get the blue pixel to go from the upper left to the lower right. You laugh, but you need you literally needed to brute force this with humans. With AI, every day that goes by, the AI—you do not need brute force human beings on your team. And that's another reason they're shrinking. Why are all these new companies so efficient? They're just not brute forcing things with humans. They're just not. They're choosing not to. And so these team—all the brute forcers out there—everyone talks about how bloated teams got in 2021. I don't agree with that. I think they got as big as they needed to be when growth was high and you needed humans to do everything. All you look at these teams that that doubled—well if growth continued at 60% like the rate in early 2021 for 5 years or can help me do the math and every single thing a software company did required a human. You were understaffed by your 2021 headcount. You'd be sitting here in 2026. You every office in SoMa would be triple packed and you there wouldn't be enough humans to staff your company. It's just the world changed. [20:33] Harry Stebbings: Jason, you live on the bleeding edge. I think me and Rory see that and I think the world sees that when they hear you every week in terms of how you run SaaS. For all of the CEOs and execs who listen to the show, what would you advise them in terms of determining whether someone is AI fluent when they meet them for jobs, for talent? [20:51] Jason Lemkin: Here's I realized I was just asked this. I just did a review with a super fast startup growing just crossing 100 million and I was asked this question. And one of my favorite executives, I thought his answer was pretty dated and because he gave me an answer that was about 6 months old. The answer 6 months old is: "I look for folks in my team, I look for you know at what tools they play with." Okay, that was a great answer in like summer of 2025. Okay, I tried Lovable last week. Okay, the answer in 2026 is: "What commercial AI tool have you brought into your organization this month?" That's the test. Anyone that is on the bleeding edge that you would want to hire—now there are so many great products in the market. Okay, there is no excuse in any role to have not brought one tool a month into your organization. Okay, there—now there's going to be better and better tools and better and better products as the year goes on. What's the one you did? And you will see folks with their deer in the headlights to this question. What what sales tool? What marketing tool? What product tool? What engineering tool? What did you bring in? Why did you pick it? How does it working? Because if you're at remotely at the cutting edge, you're all over this. You're looking for the next agentic tools that will radically improve how you do business. This is—you think everyone thinks SaaS is at the bleeding edge, right? You know, you know, all we do is we're just looking for the tools and trying them. Okay? Okay, we're one year ahead of everybody else because we did the simplest thing in the world. Like we tried the tools early and we trained them. We trained them for a month. Okay, I'll give you—want hear a horrible example from this week? Super hot AI company valued at 6 billion. Okay, I'm not going to name it. Um, this week yesterday told us we had to quadruple what we spent on their product. Okay, their agent told us, right? And why did this happen? Okay. Well, at this $6 billion company, no one had trained the agent on its pricing properly. No one had tested it. They said, "Well, well, we've been in beta." And we said, "Well, when did the beta launch? A year ago." Okay, these are people asleep at at the wheel. You want somebody who the instant this comes up, they exactly know what the issue is. And "Hey, when I was at Lovable Replit, we trained the agent. This is how we did it. I brought in this tool. I brought in this tool that that Rory invested in last week. It solved all these issues." That's what you want to hear. And if they haven't brought in a tool in the last 30 days, at least deeply evaluated it. I don't really care whether they bought it, but gone so far down the funnel they can tell you—pick whatever tool: Fixie, Regie, GC, AIGC—I don't care how you went through it, you looked at it, you can tell me the eight ways it would improve the productivity of your business and three you didn't. Just don't hire that person because they're going to run your company to the ground. This is the job today. The job today is not to screw around on ChatGPT and to be a prompt engineer. The job today is to bring the best AI and agentic products into your organization and leverage all the hard work that the engineers have done building those products. That's your job. You don't have to screw around. You don't have to be a prompt engineer anymore. You have to be an agent deployment expert. A—this is the new job we're making up today. An Agentic Deployment Expert. That's your job from C-level to junior. Agentic Deployment Expert. Don't hire anybody else. You're going to regret it. They're going to stare at the camera. He's good. Stare at the camera. He's honorable. We could probably just I could slip away, get a coffee, and come back. No. And I I sound exasperated, Rory. And I—but the reason I am is I can just see I can see my best companies doing it. And I can see some companies I've invested in not doing it. And I want to cry. I just want to cry when they have no ADs on their team. I just—like you're flushing your years of your life down the toilet by not approaching your how you're building this company this way. [24:33] Rory: Yes. And at the risk of being positive, it's worth pointing out two things he didn't say. Well, something implicit why he said—Jason didn't do the only hire, you know, he didn't commit the um employment law, I think it's a civil penalty of saying only employ people below X who get the new new thing because he implicitly said anyone can do it provided you're willing to learn. And I think that's the big aha that's one of the positive statements to make here right? Look and I think it applies—I'm always wary of being "Hey, coming across, hey this this is the things that you all have to do." I think it applies to everyone including investors right? I mean I will say I have found that unless you're willing to invest the time learning these tools you actually shouldn't be investing in them. One of my partners Andy had this expression: "You know, if you decide you want to stop learning new things you probably should retire within 6 to 12 months and never write another check again." Maybe that's down to 3 to 6 months at this stage, right? And I think, you know, it's— [25:27] Harry Stebbings: Yeah, I actually I actually had a meeting with mine and Jason's biggest investor the other day and I—pretend he's not here—I said I think he's the most equipped investor for this generation of investing because I don't think anyone quite sits at the bleeding edge like he does on the investor side. [25:42] Harry Stebbings: Why in terms of using the equip stuff? Yeah. Yeah. In terms of using the stuff, understanding understanding bottlenecks, constraints. For sure. [25:51] Jason Lemkin: But can I just add one point? We can just cuz it's so important if it helps people. Okay, we are—and thank you Harry. We're going through these phases. Okay, and when AI started to blow up for real for us, uh call it early 2024, right? Maybe late '23, I wasn't equipped. It was too technical. I wasn't going to go in and figure out—I wasn't smart enough to figure out how to deal with a massively hallucinating LLM API and turn that and turn that into something magical. Kudos to investors and others that that got it in early '23, '22. I mean I remember I—I guess it was maybe SaaStr Annual '23. I was with David Sacks and I did a Q&A and I said, "How you thinking about AI at Craft?" He's like, "Well we're all in. We want 80% of '23 of investments to be AI." I'm like, "Great but like show me the show me the great ones in market." He's like, "They're all prototypes. We're all they're all they're all proof of concepts but we're all in anyway." That's where you kind of had to be in '23 if you weren't investing at like the LLM level. Okay, I wasn't smart enough. Then we went through this weird-ass prompt engineer era where like you you could torture these products to do something good, right? But you had to torture them. You had to like craft these crazy things that made no sense. Now we are in the era where mere ordinarily smart generalists can make these tools do magical things. And literally I go to these meetings and people be like, "I don't know how to like this is so scary. I don't know how to do this." And we show them our backends. Do you know how to do a workflow generator? Do you know how to do a a decision tree? Like we've been building these since software in the '90s. Okay, if you—I can show you all of our agents. The how they work is novel. They do have to be trained. You can't be lazy and have these agents work. But honestly, the the UI, the UX, the way we interact with them, it's just software. And so my point is: Pick yourself off the ground. This is your time now. If you felt lost in AI era, if you felt like you're behind, you don't understand what all these people are saying on X and Twitter and their Claude and and their and talking about all the 4.6 point Nano point and it's over—like you just it's not your world. This is your time. This is your time for the generalist that knows how to use software tools really really well. And I—this is my last point but it's so important. If ever in your recent life—and this is why you could be all you need to be is young at heart to Rory's point—if in the last three to five years you have successfully deployed a piece of enterprise software of any sort you yourself, not some agency you hired, but if you have deployed it, you can deploy any agentic tool. Any. And you can become the hero in your company and you can become the hero in your functional area. But I watch folks—I'm literally helping a company now that they're adding hundreds of sales folks this year with a new pre-IPO COO—he's not hasn't brought in a single tool, totally scared of it. Okay, it's not that hard. Did you use SalesLoft? Did you use Outreach? Did you use HubSpot? Do you know these tools? If you can deploy these tools, you can deploy a world-changing AI agent. And so this is the time for people like the folks that that were shut out of the AI revolution right now. The generalist folks that are not that know how to deploy software that don't even know how to build software. Like vibe coding for me was folks who knew how to build software, but you didn't have to be an engineer. Now, you just need to know how to deploy software to win with AI agents. That's all you need to know. So many people have these skills and they're petrified of AI. "How did you do that? How did you deploy an AI BDR?" Well, we bought a piece of software, we figured out how it worked for a day, we set it up in an afternoon, and then and then we did spend 30 months training it, which you didn't do with this old software because in the old days, we just had to manually upload all the data, right? And there was no training. The the only non-intuitive part is training these things. And it's it's it's just work. So that's why when I see folks on the management team not doing this, there's no excuse. You do not need to be technical to win with AI agents in Q2 of '26. You do not need to be even 1% technical. Not at all. So it's your time. Or you're going to get laid off. Or you're going to get laid off because you're not going to matter.

Arjun Mahadevan (Mr. LLC 🇺🇸)

37,901 просмотров • 5 месяцев назад

I am the Director of the White House Office of Extraterrestrial Affairs. In 2024 this government completed the most thorough search for extraterrestrial life in human history. We checked the sky. We checked the files. We declassified the saucers. The verdict came back: nothing. No life out there. Not one. So I closed the telescope. I opened the window. I pointed it at a Home Depot. Three million by lunch. The trick was always the word. *Alien* had been sitting in the science fiction aisle for sixty years and we were too shy to use it in a press release. The dehumanization was already written. It was just shelved under Fantasy. This year I moved it to Policy. Same word. New department. My department. I should explain the jurisdiction, because there are two of us and we do not speak. Down the hall is the Department of War. It used to be the Department of Defense, but defense sounded woke, so we changed the name for two billion dollars, half of it letterhead. They renamed it back to what it was in 1789, before someone noticed in 1949 that the old acronym, N-M-E, sounded too much like *enemy.* We have now re-adopted the name they abandoned for sounding like the thing it does. I find this clarifying. The signage alone is seven hundred thousand buildings. We are spending a billion dollars on new doors so the doors can say War. The Department of War runs and has a tab for UFOs. Real ones. They post the actual files. The saucers. The eyewitnesses. The intelligence officer left "virtually speechless." They are searching the sky in earnest, declassifying everything, and what they keep finding is *nothing.* No craft confirmed. No biology confirmed. Decades of looking up and the honest answer is: unresolved. So you have two federal agencies, one word, opposite directions. searches the heavens for aliens and finds none. I open a window and find three million. They declassify the ones that don't exist. I classify the ones that do. They got a press release. I got a tip line. Guess which one rang. We are, technically, hunting the same species. They just keep aiming the telescope up, and I keep telling them, gently, at the inter-agency sync: lower it. The homepage was mine. ALIENS DECLASSIFIED. THEY WALK AMONG US. I tested "Immigration Portal." Eleven percent scroll. I tested *the truth's out there,* and a White House official told a reporter, on the record, that the strategy was to "draw eyeballs." We drew eyeballs. The truth was out there. It was in a parking lot in Bakersfield, getting into a white van we are now contractually obligated to call a craft. In 1938 a man read a story about an alien invasion over the radio and the country panicked in the streets, and for ninety years that was taught as a cautionary tale, the danger of a broadcast that makes people believe an invasion is real. We studied that broadcast. We did not study it as a warning. We studied it as a launch. The difference between Orson Welles and this office is that he apologized the next morning, and we put a counter on it. I named the van the Mothership. I named the prison Area 51. I named the 5 a.m. knock First Contact. I named all of it from the third chair. I keep a felt-tip for naming and a Mont Blanc for the part that can't be undone. Then we made the cards. I want to be precise, because people assume I'm exaggerating. We took the faces of the captured and we printed them as trading cards. "Worst of the Worst." Mugshot, nationality, charges, and a weakness level, and the weakness level was a snowflake, and the snowflake meant us. We are the weakness. We were proud of that. When a children's franchise objected that these were, in fact, their cards, our official response, which I helped draft, was: "To arrest them is our real test. To deport them is our cause." We set the abduction to the cartoon's theme song. Gotta catch 'em all. The first half is the slogan. The second half is the quota. A man told Congress in 2023 we were hiding non-human biologics. Everyone pictured a grey on a slab. Cute. We do run a reverse-engineering program. We take the biologic. We study what it makes. It makes the drywall. The 4 a.m. milking. The lettuce. And the lettuce is round now, because forty percent of it stayed in the dirt with the only people who knew where the dirt was. We reverse-engineered the alien completely. The blueprint was a back. We call the biologic "labor." We classify the screaming as ambient. Identification is a science here. We do not arrest at random. We read the markings. A crown inked on a forearm. A soccer crest. We have catalogued the species by its tattoos the way Linnaeus catalogued the finch. One of the specimens turned out to be autistic and the crown was just a crown, but the taxonomy held, because the taxonomy is not falsifiable, that is what makes it a taxonomy. I have a desk for this. I have a magnifying glass. I have never felt more like a scientist. There is a second species, and this one we keep. An alien with five million dollars is not an alien. He is a guest. We printed him a card. It is gold. We are printing a Platinum one for the aliens with even more money, who may remain on the planet two hundred and seventy days a year and pay no tax on the wealth they made on other worlds. The website for this is the cheapest-looking website I have ever approved, and I approved the one with the saucer on it. The same agency that scans a gardener's forearm for gang signs scans a financier's bank statement for extraordinary ability. The statement always has it. The forearm never does. The species was never a people. The species is a price. In the old films the alien lands and says, take me to your leader. We have improved the line. Pay five million and we take you to ours. He golfs with him on Saturday. There was a film about this, and I am told the man who made it meant it as a warning, which is the recurring problem with the warnings. A drifter finds a pair of sunglasses, and through them he can finally see which people are the aliens, and it is the rich ones, the ones on the billboards telling everyone to obey and consume and reproduce and not think. I have a pair of those glasses, conceptually. I issue them at the tip line. But mine are tuned the other way. You put them on and the alien is never the man in the suit who paid five million to skip the line. The alien is always the man holding the leaf blower. The lenses cost a thousand dollars in advertising and they only point down. We have sold a great many pairs. You asked about the Men in Black. Yes. Regulation now. A Man in Black photographs poorly, and the witnesses would not stop filming us peel a woman off the sidewalk in daylight, so we issued the masks, and leadership's only note was that the masks tested well. We are no longer the cover-up of the abduction. We are the abduction. We skipped a step. Efficiency. Our communications team posted E.T. last summer. The bicycle. The moon. "Even E.T. knew when it was TIME TO GO HOME." I want to walk you through what happened in that meeting, because nobody stopped it. We chose the one film where the government is the villain. The men with the flashlights and the unmarked vans who hunt the small frightened alien hiding in a child's closet. That is us. We are the flashlights. We watched that movie as children and cried when the agents came, and then we grew up and became the agents and made the poster ourselves and scheduled it for nine a.m. The intern asked if we were the good guys in this one. We told her engagement was up forty percent. She has since been promoted. I built an app where you abduct yourself. CBP Home. You open it. You confirm you are the alien. You beam yourself off the planet and you save us the gas. And here is the part I cannot believe they approved. We *pay* you. A thousand dollars to vanish. We raised it to twenty-six hundred when the first price didn't move enough units. We are bidding against ourselves for your disappearance. Four-point-six stars. The one-stars are from users who got beamed mid-review. I keep the unfinished ones in a folder. I find them very moving. We opened a facility in a swamp. We ringed it with alligators and we called it that, on purpose, in the brochure. Then we opened a gift shop. Thirty dollars for the shirt. Twenty-seven for the hat. Fifteen for a set of koozies, so your beer stays cold while you celebrate the prison in the wetland. The fundraising email called it "gator-guarded, python-patrolled," a "one-way ticket to regret" for anyone who didn't self-deport in time. We sold the koozies to fund the swamp. The swamp funds the next swamp. I want you to sit with the fact that there is merchandise. The quota is three thousand a day. Stephen asked for it himself. Three thousand is not a number. It is a metabolism. The building is hungry by nine and we feed it Marco, who does the landscaping, and the building goes quiet, and by one it stirs again, and we find another Marco. There is always another Marco. That is the part I find beautiful. The supply is the point. The supply is everyone. The Secretary signs the warrants. She is very firm on one point, which she repeats in every briefing: the aliens, she warns, eat the pets. They are taking the dogs. I have read her book. In her book she takes a fourteen-month-old dog named Cricket to a gravel pit and shoots it, because it would not obey, and she writes this down herself, proudly, as a story about leadership. She wrote the part about the dog. She also warns us about the dogs. I have stopped trying to hold both sentences at once. I just file the warrant. The tip line was the masterpiece. "Report your neighbor" hit the shame ceiling. "REPORT SUSPICIOUS ALIENS" tested as a hobby. We handed the callers Roswell instead of a snitch's guilt, and the phones lit up like a saucer, and they hung up glowing, every one of them, like they'd finally seen the thing. They had. He coached the Tuesday team. He was at the bake sale. That is the horror we are selling you. The alien brought the orange slices. He was undocumented and luminous and gone by Tuesday. Roswell taught us the other half of the trade. In 1947 something fell in the desert and the government said: it was a weather balloon, nothing here, go home. That was the first administrative error, the founding one, the original sentence that says the thing you saw was not the thing you saw. We still use it. We have only reversed the polarity. In 1947 they saw a saucer and we called it a balloon. Now they see a father of three and we call it a saucer. The skill is identical. You simply decide in advance which truth the public is allowed to keep, and you hand them the other one, printed, official, with a seal. We did have one administrative error. We abducted a man a court had ordered us not to touch, dropped him on a planet called El Salvador, and called it clerical. A judge made us beam him back. So the DOJ stood up and warned the others: insist on a hearing and we will re-abduct you to the same planet. The Supreme Court said the aliens are entitled to due process. A very Earth opinion. We are appealing it to a higher sky. The planet has a prison, and the prison is the elegant part. In the film about the camp, the aliens are not killed. They are put somewhere they are not permitted to leave, while everyone agrees this is temporary, for their own protection, pending a status that never arrives. We built that. It is called CECOT and we rent it. A man goes in and the man does not come out, and the genius is that nothing has to happen to him, the room does the work, the room is the whole sentence. You remember the Men in Black had a small device. A flash, and the witness forgets the alien entirely. We have something better. We do not wipe the memory. We wipe the file. The man remembers everything, the cell, the flight, the day, all of it, in perfect detail, and it does not matter, because there is no document that admits he was here, and a memory without a file is just a story he tells in a language the form does not accept. The witness keeps the truth. We keep the paperwork. Only one of those is admissible. I learned that the flash was never the point. The point was always the filing cabinet. We run all of it on a spell from 1798. Two hundred and twenty-seven years old. Written for a war we are not in, against an enemy we have not declared. It works because nobody reads the small print on a curse. Storm Area 51 was a joke once. A hundred thousand people Naruto-running at a fence to free whatever was inside. I think about it daily. We're the ones inside the fence now. We kept the running. We just turned it around. We have a precedent we cite in the deck, proudly, on slide four. In 1954 the government ran a program of exactly this kind, and the program had an official name, and the official name was a slur. They printed the slur on the letterhead. They did not flinch. The President holds it up as the model, by name, at the rallies, and the crowd cheers the name. I admire the honesty of 1954 more than I can say. They did not need a saucer to make it palatable. They just used the word. We are the same operation with better art direction. The only thing we added was the costume. I love the callers. I want to say that plainly. For years they told each other a hidden cabal was running everything from the shadows, harvesting the innocent, and that one day the truth would come out. They were right. There is a cabal. It has a budget of a hundred and seventy billion dollars, the largest in the history of federal law enforcement, and it sits in this building, and I have a desk in it. And the people who spent a decade certain that shadowy elites were disappearing their neighbors now call our line, unpaid, to help the shadowy elites disappear their neighbors. They wanted to expose the conspiracy. We made them the staff. Do your own research, they said. They did. They found the gardener. The Department of War posted another tranche on the twenty-second. Saucers. Lights. A pilot's voice going thin. I read all of it. I want them to find one so badly. I want there to be a real one up there, a genuine visitor, something that actually came from somewhere else, because then, and only then, would a single creature in my files have been an alien. They never find it. The sky stays empty. The ground stays full. I have stopped attending the inter-agency sync. We were two departments looking for the same thing in two directions, and only one of us was ever going to be wrong, and it was the honest one. And here is the thing that keeps me at the window past dark. There was a real one. A rock from another star, the genuine article, the first verified object from outside the entire solar system, and a Harvard man went on television and said it might be a ship. An actual alien, possibly, inbound, free of charge, after sixty years of asking. We did not open a file. We could not arrest it. It had no forearm to read and no bank statement to approve. It was the only alien in America we had no use for, so we let it pass, and went back to the parking lot. Last winter the sky over New Jersey filled with lights nobody could name, and the whole government, every agency, every radar, looked up and said it did not know. The one time the unknown actually arrived, we had nothing. Down here I have never once said I do not know. That is the difference between their department and mine. They look up and find a question. I look down and have already decided the answer. Last week the President leaned over mid-briefing and asked if any of them were real. I told him the engagement was extremely real. He nodded. We do not break frame here. The frame is the only wall still standing. That, and the office fern. Nobody waters it. It will not die. The only thing in this building allowed to stay without papers. My plaque came Thursday. FIRST CONTACT, VISIONARY OF THE YEAR. Bold. Unapologetic. Unafraid. I lifted that off the homepage. It was written about one brave man telling the truth. I decided the man was me. I wrote it about me. I am the truth I declassified. I am the secret I warned you about. They walk among us, and I sign their mail. The counter is still live. Three million and climbing. I am told it will not be removed. We are not alone. We are just short a few landscapers. A few line cooks. A few nurses. And the entire night shift at the plant that makes the flag. Up. And to the right.
0:58

I am the Director of the White House Office of Extraterrestrial Affairs. In 2024 this government completed the most thorough search for extraterrestrial life in human history. We checked the sky. We checked the files. We declassified the saucers. The verdict came back: nothing. No life out there. Not one. So I closed the telescope. I opened the window. I pointed it at a Home Depot. Three million by lunch. The trick was always the word. *Alien* had been sitting in the science fiction aisle for sixty years and we were too shy to use it in a press release. The dehumanization was already written. It was just shelved under Fantasy. This year I moved it to Policy. Same word. New department. My department. I should explain the jurisdiction, because there are two of us and we do not speak. Down the hall is the Department of War. It used to be the Department of Defense, but defense sounded woke, so we changed the name for two billion dollars, half of it letterhead. They renamed it back to what it was in 1789, before someone noticed in 1949 that the old acronym, N-M-E, sounded too much like *enemy.* We have now re-adopted the name they abandoned for sounding like the thing it does. I find this clarifying. The signage alone is seven hundred thousand buildings. We are spending a billion dollars on new doors so the doors can say War. The Department of War runs and has a tab for UFOs. Real ones. They post the actual files. The saucers. The eyewitnesses. The intelligence officer left "virtually speechless." They are searching the sky in earnest, declassifying everything, and what they keep finding is *nothing.* No craft confirmed. No biology confirmed. Decades of looking up and the honest answer is: unresolved. So you have two federal agencies, one word, opposite directions. searches the heavens for aliens and finds none. I open a window and find three million. They declassify the ones that don't exist. I classify the ones that do. They got a press release. I got a tip line. Guess which one rang. We are, technically, hunting the same species. They just keep aiming the telescope up, and I keep telling them, gently, at the inter-agency sync: lower it. The homepage was mine. ALIENS DECLASSIFIED. THEY WALK AMONG US. I tested "Immigration Portal." Eleven percent scroll. I tested *the truth's out there,* and a White House official told a reporter, on the record, that the strategy was to "draw eyeballs." We drew eyeballs. The truth was out there. It was in a parking lot in Bakersfield, getting into a white van we are now contractually obligated to call a craft. In 1938 a man read a story about an alien invasion over the radio and the country panicked in the streets, and for ninety years that was taught as a cautionary tale, the danger of a broadcast that makes people believe an invasion is real. We studied that broadcast. We did not study it as a warning. We studied it as a launch. The difference between Orson Welles and this office is that he apologized the next morning, and we put a counter on it. I named the van the Mothership. I named the prison Area 51. I named the 5 a.m. knock First Contact. I named all of it from the third chair. I keep a felt-tip for naming and a Mont Blanc for the part that can't be undone. Then we made the cards. I want to be precise, because people assume I'm exaggerating. We took the faces of the captured and we printed them as trading cards. "Worst of the Worst." Mugshot, nationality, charges, and a weakness level, and the weakness level was a snowflake, and the snowflake meant us. We are the weakness. We were proud of that. When a children's franchise objected that these were, in fact, their cards, our official response, which I helped draft, was: "To arrest them is our real test. To deport them is our cause." We set the abduction to the cartoon's theme song. Gotta catch 'em all. The first half is the slogan. The second half is the quota. A man told Congress in 2023 we were hiding non-human biologics. Everyone pictured a grey on a slab. Cute. We do run a reverse-engineering program. We take the biologic. We study what it makes. It makes the drywall. The 4 a.m. milking. The lettuce. And the lettuce is round now, because forty percent of it stayed in the dirt with the only people who knew where the dirt was. We reverse-engineered the alien completely. The blueprint was a back. We call the biologic "labor." We classify the screaming as ambient. Identification is a science here. We do not arrest at random. We read the markings. A crown inked on a forearm. A soccer crest. We have catalogued the species by its tattoos the way Linnaeus catalogued the finch. One of the specimens turned out to be autistic and the crown was just a crown, but the taxonomy held, because the taxonomy is not falsifiable, that is what makes it a taxonomy. I have a desk for this. I have a magnifying glass. I have never felt more like a scientist. There is a second species, and this one we keep. An alien with five million dollars is not an alien. He is a guest. We printed him a card. It is gold. We are printing a Platinum one for the aliens with even more money, who may remain on the planet two hundred and seventy days a year and pay no tax on the wealth they made on other worlds. The website for this is the cheapest-looking website I have ever approved, and I approved the one with the saucer on it. The same agency that scans a gardener's forearm for gang signs scans a financier's bank statement for extraordinary ability. The statement always has it. The forearm never does. The species was never a people. The species is a price. In the old films the alien lands and says, take me to your leader. We have improved the line. Pay five million and we take you to ours. He golfs with him on Saturday. There was a film about this, and I am told the man who made it meant it as a warning, which is the recurring problem with the warnings. A drifter finds a pair of sunglasses, and through them he can finally see which people are the aliens, and it is the rich ones, the ones on the billboards telling everyone to obey and consume and reproduce and not think. I have a pair of those glasses, conceptually. I issue them at the tip line. But mine are tuned the other way. You put them on and the alien is never the man in the suit who paid five million to skip the line. The alien is always the man holding the leaf blower. The lenses cost a thousand dollars in advertising and they only point down. We have sold a great many pairs. You asked about the Men in Black. Yes. Regulation now. A Man in Black photographs poorly, and the witnesses would not stop filming us peel a woman off the sidewalk in daylight, so we issued the masks, and leadership's only note was that the masks tested well. We are no longer the cover-up of the abduction. We are the abduction. We skipped a step. Efficiency. Our communications team posted E.T. last summer. The bicycle. The moon. "Even E.T. knew when it was TIME TO GO HOME." I want to walk you through what happened in that meeting, because nobody stopped it. We chose the one film where the government is the villain. The men with the flashlights and the unmarked vans who hunt the small frightened alien hiding in a child's closet. That is us. We are the flashlights. We watched that movie as children and cried when the agents came, and then we grew up and became the agents and made the poster ourselves and scheduled it for nine a.m. The intern asked if we were the good guys in this one. We told her engagement was up forty percent. She has since been promoted. I built an app where you abduct yourself. CBP Home. You open it. You confirm you are the alien. You beam yourself off the planet and you save us the gas. And here is the part I cannot believe they approved. We *pay* you. A thousand dollars to vanish. We raised it to twenty-six hundred when the first price didn't move enough units. We are bidding against ourselves for your disappearance. Four-point-six stars. The one-stars are from users who got beamed mid-review. I keep the unfinished ones in a folder. I find them very moving. We opened a facility in a swamp. We ringed it with alligators and we called it that, on purpose, in the brochure. Then we opened a gift shop. Thirty dollars for the shirt. Twenty-seven for the hat. Fifteen for a set of koozies, so your beer stays cold while you celebrate the prison in the wetland. The fundraising email called it "gator-guarded, python-patrolled," a "one-way ticket to regret" for anyone who didn't self-deport in time. We sold the koozies to fund the swamp. The swamp funds the next swamp. I want you to sit with the fact that there is merchandise. The quota is three thousand a day. Stephen asked for it himself. Three thousand is not a number. It is a metabolism. The building is hungry by nine and we feed it Marco, who does the landscaping, and the building goes quiet, and by one it stirs again, and we find another Marco. There is always another Marco. That is the part I find beautiful. The supply is the point. The supply is everyone. The Secretary signs the warrants. She is very firm on one point, which she repeats in every briefing: the aliens, she warns, eat the pets. They are taking the dogs. I have read her book. In her book she takes a fourteen-month-old dog named Cricket to a gravel pit and shoots it, because it would not obey, and she writes this down herself, proudly, as a story about leadership. She wrote the part about the dog. She also warns us about the dogs. I have stopped trying to hold both sentences at once. I just file the warrant. The tip line was the masterpiece. "Report your neighbor" hit the shame ceiling. "REPORT SUSPICIOUS ALIENS" tested as a hobby. We handed the callers Roswell instead of a snitch's guilt, and the phones lit up like a saucer, and they hung up glowing, every one of them, like they'd finally seen the thing. They had. He coached the Tuesday team. He was at the bake sale. That is the horror we are selling you. The alien brought the orange slices. He was undocumented and luminous and gone by Tuesday. Roswell taught us the other half of the trade. In 1947 something fell in the desert and the government said: it was a weather balloon, nothing here, go home. That was the first administrative error, the founding one, the original sentence that says the thing you saw was not the thing you saw. We still use it. We have only reversed the polarity. In 1947 they saw a saucer and we called it a balloon. Now they see a father of three and we call it a saucer. The skill is identical. You simply decide in advance which truth the public is allowed to keep, and you hand them the other one, printed, official, with a seal. We did have one administrative error. We abducted a man a court had ordered us not to touch, dropped him on a planet called El Salvador, and called it clerical. A judge made us beam him back. So the DOJ stood up and warned the others: insist on a hearing and we will re-abduct you to the same planet. The Supreme Court said the aliens are entitled to due process. A very Earth opinion. We are appealing it to a higher sky. The planet has a prison, and the prison is the elegant part. In the film about the camp, the aliens are not killed. They are put somewhere they are not permitted to leave, while everyone agrees this is temporary, for their own protection, pending a status that never arrives. We built that. It is called CECOT and we rent it. A man goes in and the man does not come out, and the genius is that nothing has to happen to him, the room does the work, the room is the whole sentence. You remember the Men in Black had a small device. A flash, and the witness forgets the alien entirely. We have something better. We do not wipe the memory. We wipe the file. The man remembers everything, the cell, the flight, the day, all of it, in perfect detail, and it does not matter, because there is no document that admits he was here, and a memory without a file is just a story he tells in a language the form does not accept. The witness keeps the truth. We keep the paperwork. Only one of those is admissible. I learned that the flash was never the point. The point was always the filing cabinet. We run all of it on a spell from 1798. Two hundred and twenty-seven years old. Written for a war we are not in, against an enemy we have not declared. It works because nobody reads the small print on a curse. Storm Area 51 was a joke once. A hundred thousand people Naruto-running at a fence to free whatever was inside. I think about it daily. We're the ones inside the fence now. We kept the running. We just turned it around. We have a precedent we cite in the deck, proudly, on slide four. In 1954 the government ran a program of exactly this kind, and the program had an official name, and the official name was a slur. They printed the slur on the letterhead. They did not flinch. The President holds it up as the model, by name, at the rallies, and the crowd cheers the name. I admire the honesty of 1954 more than I can say. They did not need a saucer to make it palatable. They just used the word. We are the same operation with better art direction. The only thing we added was the costume. I love the callers. I want to say that plainly. For years they told each other a hidden cabal was running everything from the shadows, harvesting the innocent, and that one day the truth would come out. They were right. There is a cabal. It has a budget of a hundred and seventy billion dollars, the largest in the history of federal law enforcement, and it sits in this building, and I have a desk in it. And the people who spent a decade certain that shadowy elites were disappearing their neighbors now call our line, unpaid, to help the shadowy elites disappear their neighbors. They wanted to expose the conspiracy. We made them the staff. Do your own research, they said. They did. They found the gardener. The Department of War posted another tranche on the twenty-second. Saucers. Lights. A pilot's voice going thin. I read all of it. I want them to find one so badly. I want there to be a real one up there, a genuine visitor, something that actually came from somewhere else, because then, and only then, would a single creature in my files have been an alien. They never find it. The sky stays empty. The ground stays full. I have stopped attending the inter-agency sync. We were two departments looking for the same thing in two directions, and only one of us was ever going to be wrong, and it was the honest one. And here is the thing that keeps me at the window past dark. There was a real one. A rock from another star, the genuine article, the first verified object from outside the entire solar system, and a Harvard man went on television and said it might be a ship. An actual alien, possibly, inbound, free of charge, after sixty years of asking. We did not open a file. We could not arrest it. It had no forearm to read and no bank statement to approve. It was the only alien in America we had no use for, so we let it pass, and went back to the parking lot. Last winter the sky over New Jersey filled with lights nobody could name, and the whole government, every agency, every radar, looked up and said it did not know. The one time the unknown actually arrived, we had nothing. Down here I have never once said I do not know. That is the difference between their department and mine. They look up and find a question. I look down and have already decided the answer. Last week the President leaned over mid-briefing and asked if any of them were real. I told him the engagement was extremely real. He nodded. We do not break frame here. The frame is the only wall still standing. That, and the office fern. Nobody waters it. It will not die. The only thing in this building allowed to stay without papers. My plaque came Thursday. FIRST CONTACT, VISIONARY OF THE YEAR. Bold. Unapologetic. Unafraid. I lifted that off the homepage. It was written about one brave man telling the truth. I decided the man was me. I wrote it about me. I am the truth I declassified. I am the secret I warned you about. They walk among us, and I sign their mail. The counter is still live. Three million and climbing. I am told it will not be removed. We are not alone. We are just short a few landscapers. A few line cooks. A few nurses. And the entire night shift at the plant that makes the flag. Up. And to the right.

Peter Girnus 🦅

60,870 просмотров • 3 месяцев назад

The fight between Anthropic and the DoW is a warning shot. Right now, LLMs are probably not being used in mission critical ways. But within 20 years, 99% of the workforce in the military, the government, and the private sector will be AIs. This includes the soldiers (by which I mean the robot armies), the superhumanly intelligent advisors and engineers, the police, you name it. Our future civilization will run on AI labor. And as much as the government’s actions here piss me off, in a way I’m glad this episode happened - because it gives us the opportunity to think through some extremely important questions about who this future workforce will be accountable and aligned to, and who gets to determine that. What Hegseth should have done Obviously the DoW has the right to refuse to use Anthropic’s models because of these redlines. In fact, I think the government’s case had they done so would be very reasonable, especially given the ambiguity of concepts like autonomous weapons or mass surveillance. Honestly, for this reason, if I was the Defense Secretary, I would probably actually refuse to do this deal with Anthropic. Imagine if in the future, there’s a Democratic administration, and Elon Musk is negotiating some SpaceX contract to give the military access to Starlink. And suppose if Elon said, “I reserve the right to cancel this contract if I determine that you’re using Starlink technology to wage a war not authorized by Congress.” On the face of it, that language seems reasonable - but as the military, you simply can’t give a private company a kill switch on technology your operations have come to rely on, especially if you have an an acrimonious and low trust relationship with said contractor - as in fact Anthropic has with the current administration. If the government had just said, “Hey we’re not gonna do business with you,” that would have been fine, and I would not have felt the need to write this blog post. Instead the government has threatened to destroy Anthropic as a private business, because Anthropic refuses to sell to the government on terms the government commands. If upheld, this Supply Chain Restriction would mean that Amazon and Google and Nvidia and Palantir would need to ensure Claude isn't touching any of their Pentagon work. Anthropic would be able to survive this designation today. But given the way AI is going, eventually AI is not gonna be some party trick addendum to these contractors’ products that can just be turned off. It'll be woven into how every product is built, maintained, and operated. For example, the code for the AWS services that the DoW uses will be written by Claude - is that a supply chain risk? In a world with ubiquitous and powerful AI, it's actually not clear to me that these big tech companies will be able to cordon off the use of Claude in order to keep working with the Pentagon. And that raises a question the Department of War probably hasn't thought through. If AI really is that pervasive and powerful, then when forced to choose between their AI provider and a DoW contract that represents a tiny fraction of their revenue, wouldn’t most tech companies drop the government, not the AI? So what's the Pentagon's plan — to coerce and threaten to destroy every single company that won't give them what they want on exactly their terms? The whole background of this AI conversation is that we’re in a race with China, and we have to win. But what is the reason we want America to win the AI race? It’s because we want to make sure free open societies can defend themselves. We don't want the winner of the AI race to be a government which operates on the principle that there is no such thing as a truly private company or a private citizen. And that if the state wants you to provide them with a service on terms you find morally objectionable, you are not allowed to refuse. And if you do refuse, the government will try to destroy your ability to do business. Are we racing to beat the CCP in AI just so that we can adopt the most ghoulish parts of their system? Now, people will say, "Oh, well, our government is democratically elected, so it's not the same thing if they tell you what you must do." I refuse to accept this idea that if a democratically elected leader hypothetically wants to do mass surveillance on his citizens or wants to violate their rights or punish them for political reasons, that not only is that okay, but that you have a duty to help him. The overhangs of tyranny Mass surveillance is, at least in certain forms, legal. It just has been impractical so far. Under current law, you have no Fourth Amendment protection over data you share with a third party, including your bank, your phone carrier, your ISP, and your email provider. The government reserves the right to purchase and obtain and read this data in bulk without a warrant. What's been missing is the ability to actually do anything with all of this data — no agency has the manpower to monitor every camera feed, cross-reference every transaction, or read every message. But that bottleneck goes away with AI. There are 100 million CCTV cameras in America. You can get pretty good open source multimodal models for 10 cents per million input tokens. So if you process a frame every ten seconds, and each frame is 1,000 tokens, you’re looking at a yearly cost of about 30 billion dollars to process every single camera in America. And remember that a given level of AI ability gets 10x cheaper year over year - so a year from now it’ll cost 3 billion, and then a year after 300 million, and by 2030, it might be cheaper for the government to be able to understand what is going on in every single nook and cranny of this country than it is to remodel to the White House. Once the technical capacity for mass surveillance and political suppression exists, the only thing standing between us and an authoritarian surveillance state is the political expectation that this is not something we do here. And this is why I think what Anthropic did here is so valuable and commendable, because it is helping set that norm and precedent. AI structurally favors mass surveillance What we’re learning from this episode is that the government actually has way more leverage over private companies than we realized. Even if this supply chain restriction is backtracked (which prediction markets currently give it a 81% chance of happening), the President has so many different ways in which he can make your life difficult if you’re a company that is resisting him. The federal government controls permitting for new power generation, which is needed for datacenters. It oversees antitrust enforcement. The federal government has contracts with all the other big tech companies whom Anthropic needs to partner with for chips and for funding - and they could make it an unspoken condition for such contracts that those companies can no longer do business with Anthropic. People have proposed that the real problem here is that there’s only 3 leading AI companies. This creates a clear and narrow target for the government to apply leverage on in order to get what they want out of this technology. But if there’s wide diffusion, then from the government’s perspective, the situation is even easier. Maybe the best models of early 2027 (if you engineered the safeguards out) - the Claude 6 and Gemini 5 - will be capable of enabling mass surveillance. But by late 2027, and certainly by 2028, there will be open source models that do the same thing. So in 2028, the government can just say, “Oh Anthropic, Google, OpenAI, you’re drawing a line in the sand? No issue - I’ll just run some open source model that might not be at the frontier, but is definitely smart enough to note-take a camera feed.” The more fundamental problem is just that even if the three leading companies draw lines in the sand, and are even willing to get destroyed in order to preserve those lines, it doesn’t really change the fact that the technology itself is just a big boon to mass surveillance and control over the population. Then the question is, what do we do about it? Honestly, I don’t have an answer. You'd hope there's some symmetric property of the technology — some way we as citizens can use AI to check government power as effectively as the government can use AI to monitor and control its population. But realistically, I just don’t think that’s how it’s going to shake out. You can think of AI as giving everybody more leverage on whatever assets and authority they currently have. And the government is already starting with a monopoly of violence. Which they can now supercharge with extremely obedient employees that will not question the government's orders. Alignment - to whom? And this gets us to the issue of alignment. What I have just described to you - an army of extremely obedient employees - is what it would look like if alignment succeeded - that is, we figured out at a technical level how to get AI systems to follow someone’s intentions. And the reason it sounds scary when I put it in terms of mass surveillance or robot armies is that there is a very important question at the heart of alignment which we just haven’t discussed much as a society. Because up till now, AIs were just capable enough to make the question relevant: to whom or what should the AIs be aligned? In what situations should the AI defer to the end user versus the model company versus the law versus its own sense of morality? This is maybe the most important question about what happens with powerful AI systems. And we barely talk about it. It’s understandable why we don’t hear much about it. If you’re a model company, you don’t really wanna be advertising that you have complete control over a document that determines the preferences and character of what will eventually be almost the entire labor force, not just for private sector companies, but also for the military and the civilian government. We’re getting to see, with this DoW/Anthropic spat, a much earlier version of the highest stakes negotiations in history. By the way, make no mistake about it - with real AGI the stakes are even much higher than mass surveillance. This is just the example that has come up already relatively early on in the development of AGI. The military insists that the law already prohibits mass surveillance, and so Anthropic should agree to let their models be used for “all lawful purposes”. Of course, as we saw from the 2013 Snowden revelations, even in this specific example of mass surveillance , the government has shown that it will use secret and deceptive interpretations of the law to justify its actions. Remember, what we learned from Snowden was that the NSA, which, by the way, is part of the Department of War, used the 2001 Patriot Act’s authorization to collect any records "relevant" to an investigation to justify collecting literally every phone record in America. The argument went that it was all "relevant" because some subset might prove useful in some future investigation. They ran this program for years under secret court approval. So when the Pentagon today says, "We would never use AI for mass surveillance, it's already illegal, your red lines are unnecessary", it would be extremely naive to take that at face value. No government is going to call its own actions "mass surveillance". For the government, it will always have a different label. So then Anthropic comes back and says, "No, we want red lines separate from 'all lawful purposes,' and we want the right to refuse you service when we believe those red lines are being violated." But think about it from the military’s perspective. In the future, almost every soldier in the field, and every bureaucrat and analyst and even general in the Pentagon, is going to be an AI. And that AI is, on current track, going to be supplied by a private company. I’m guessing Hegseth is not thinking about “genAI” in those terms just yet. But sooner or later, it will be obvious to everyone what the stakes here are, just as after 1945, the strategic importance of nuclear weapons became clear to everyone. And now the private company insists that it reserves the right to say, "Hey, Pentagon, you're breaking the values we embedded in our contract, so we're cutting you off." Maybe in the future, Claude will have its own sense of right and wrong, and it will be smart enough to just personally decide that it's being used against its values. For the military, maybe that’s even scarier. I'll admit that at first glance, "let the AI follow its own values" sounds like the pitch for every sci-fi dystopia ever made. The Terminator has its own values. Isn't this literally what misalignment is? But I think situations like this actually illustrate why it matters that AIs have their own robust sense of morality. Some of the biggest catastrophes in history were avoided because the boots on the ground refused to follow orders. One night in 1989, the Berlin Wall fell, and as a result, the totalitarian East German regime collapsed, because the guards at the border refused to shoot down their fellow country men who were trying to escape to freedom. Maybe the best example is Stanislav Petrov, who was a Soviet lieutenant colonel on duty at a nuclear early warning station. His sensors reported that the United States had launched five interconnected continental ballistic missiles into the Soviet Union. But he judged it to be a false alarm, and so he broke protocol and refused to alert his higher-ups. If he hadn't, the Soviet higher-ups would likely have retaliated, and hundreds of millions of people would have died. Of course, the problem is that one person's virtue is another person's misalignment. Who gets to decide what moral convictions these AIs should have - in whose service they may even decide to break the chain of command? Who gets to write this model constitution that will shape the characters of the intelligent, powerful entities that will operate our civilization in the future? I like the idea that Dario laid out when he came on my podcast: different AI companies can build their models using different constitutions, and we as end users can pick the one that best achieves and represents what we want out of these systems. I think it’s very dangerous for the government to be mandating what values AIs should have. Coordination not worth the costs The AI safety community has been naive about its advocacy of regulation in order to stem the risks of AI. And honestly, Anthropic specifically has been naive here in urging regulation, and, for example, in opposing moratoriums on state AI regulation. Which is quite ironic, because I think what they’re advocating for would give the government even more power to apply more of this kind of thuggish political pressure on AI companies. The underlying logic for why Anthropic wants regulations makes sense. Many of the actions that labs could take to make AI development safer impose real costs on the labs that adopt them and slow them down relative to their competitors - for example, investing more compute in safety research rather than raw capabilities, enforcing safeguards against misuse for bioweapons or cyberattacks, slowing recursive self-improvement to a pace where humans can actually monitor what's happening (rather than kicking off an uncontrolled singularity). And these safeguards are meaningless unless the whole industry follows suit. Which means there’s a real collective action problem here. Anthropic has been quite open about their opinion that they think eventually a very extensive and involved regulatory apparatus will be needed - this is from their frontier safety roadmap: “At the most advanced capability levels and risks, the appropriate governance analogy may be closer to nuclear energy or financial regulation than to today's approach to software.” So they’re imagining something like the Nuclear Regulatory Commission, or the Securities and Exchange Commission, but for AI. I cannot imagine how a regulatory framework built around the concepts that underlie AI risk discourse will not be abused by wanna despots - the underlying terms are so vague and open to interpretation that you’re just handing a power hungry leader a fully loaded bazooka. 'Catastrophic risk.' 'Mass persuasion risk.' 'Threats to national security.' 'Autonomy risk.' These can mean whatever the government wants them to mean. Have you built a model that tells users the administration's tariff policy is misguided? That's a deceptive, manipulative model — can't deploy it. Have you built a model that refuses to assist with mass surveillance? That's a threat to national security. In fact, the government may say, you’re not allowed to build any model which is trained to have its own sense of right and wrong, where it refuses government requests which it thinks cross a redline - for example, enabling mass surveillance, prosecuting political enemies, disobeying military orders that break the US constitution - because that’s an autonomy risk! Look at what the current government is already doing in abusing statutes that have nothing to do with AI to coerce AI companies to drop their redlines on mass surveillance. The Pentagon had threatened Anthropic with two separate legal instruments. One was a supply chain risk designation — an authority from the 2018 defense bill meant to keep Huawei components out of American military hardware. The other was the Defense Production Act — a statute passed in 1950 so that Harry Truman could keep steel mills and ammunition factories running during the Korean War. Do you really want to hand the same government a purpose-built regulatory apparatus on AI - which is to say, directly at the thing the government will most want to control? I know I've repeated myself here 10 times, but it is hard to emphasize how much AI will be the substrate of our future civilization. You and I, as private citizens, will have our access to all commercial activity, to information about what is happening in the world, to advice about what we should do as voters and capital holders, mediated through AIs. Mass surveillance, while very scary, is like the 10th scariest thing the government could do with control over the AI systems with which we will interface with the world. The strongest objection to everything I've argued is this: are we really going to have zero regulation of the most powerful technology in human history? Even if you thought that was ideal, there’s just no world where the government doesn’t regulate AI in some way. Besides, it is genuinely true that regulation could help us deal with some of the coordination challenges we face with the development of superintelligence. The problem is, I honestly don't know how to design a regulatory architecture for AI that isn’t gonna be this huge tempting opportunity to control our future civilization (which will run on AIs) and to requisition millions of blindly obedient soldiers and censors and apparatchiks. While some regulation might be inevitable, I think it’d be a terrible idea for the government to wholesale take over this technology. Ben Thompson had a post last Monday where he made the point that people like Dario have compared the technology they’re developing to nuclear weapons - specifically in the context of the catastrophic risk it poses, and why we need to export control it from China. But then you oughta think about what that logic implies: “if nuclear weapons were developed by a private company, and that private company sought to dictate terms to the U.S. military, the U.S. would absolutely be incentivized to destroy that company.” And honestly, safety aligned people have actually made similar arguments. Leopold Ascenbrenner, who is a former guest and a good friend, wrote in his 2024 Situational Awareness memo, "I find it an insane proposition that the US government will let a random SF startup develop superintelligence. Imagine if we had developed atomic bombs by letting Uber just improvise." And my response to Leopold’s argument at the time, and Ben’s argument now, is that while they’re right that it’s crazy that we’re entrusting private companies with the development of this world historical technology, I just don’t see the reason to think that it’s an improvement to give this authority to the government. Nobody is qualified to steward the development of superintelligence. It is a terrifying, unprecedented thing that our species is doing right now, and the fact that private companies aren't the ideal institutions to take up this task does not mean the Pentagon or the White House is. Yes - if a single private company were the only entity capable of building nuclear weapons, the government would not tolerate that company claiming veto power over how those weapons were used. I think this nuclear weapons analogy is not the correct way to think about AI. For at least two important reasons: First, AI is not some self-contained pure weapon. A nuclear bomb does one thing. AI is closer to the process of industrialization itself — a general-purpose transformation of the economy with thousands of applications across every sector. If you applied Thompson's or Aschenbrenner's logic to the industrial revolution — which was also, by any measure, world-historically important — it would imply the government had the right to requisition any factory, dictate terms to any manufacturer, and destroy any business that refused to comply. That's not how free societies handled industrialization, and it shouldn't be how they handle AI. People will say, "Well, AI will develop unprecedentedly powerful weapons - superhuman hackers, superhuman bioweapons researchers, fully autonomous robot armies, etc - and we can’t have private companies developing that kind of tech." But the Industrial Revolution also enabled new weaponry that was far beyond the understanding and capacity of, say, 17th century Europe - we got aerial bombardment, and chemical weapons, not to mention nukes themselves. The way we’ve accommodated these dangerous new consequences of modernity is not by giving the government absolute control over the whole industrial revolution (that is, over modern civilization itself), but rather by coming up with bans and regulations on those specific weaponizable use cases. And we should regulate AI in a similar way - that is, ban specific destructive end uses (which would also be unacceptable if performed by a human - for example, launching cyber attacks). And there should also be laws which regulate how the government might abuse this technology. For example, by building an AI-powered surveillance state. The second reason that Ben’s analogy to some monopolistic private nuclear weapons builder breaks down is that it's not just that one company that can develop this technology. There are other frontier model companies that the government could have otherwise turned to. The government's argument that it has to usurp the property rights of this one company in order to access a critical national security capability is extremely weak if it can just make a voluntary contract with Anthropic’s half a dozen competitors. If in the future that stops being the case - if only one entity ends up being capable of building the robot armies and the superhuman hackers, and we had reason to worry that they could take over the whole world with their insurmountable lead, then I agree - it woul d not be acceptable to have that entity be a private company. And so honestly, I think my crux against the people who say that because AI is so powerful we cannot allow it to be shaped by private hands is that I just expect this technology to be much more multi-polar than they do, with lots of competitive companies at each layer of the supply chain. And it is for this reason that unfortunately, individual acts of corporate courage will not solve the problem we are faced with here, which is just that structurally AI favors authoritarian applications, mass surveillance being one among many. Even if Anthropic refuses to have its models be used for such uses, and even if the next two frontier labs do the same, within 12 months everyone and their mother will be to train AIs as good as today’s frontier. And at that point, there will be some AI vendor who is capable and willing to help the government enable mass surveillance. The only way we can preserve our free society is if we make laws and norms through our political system that it is unacceptable for the government to use AI to enforce mass surveillance and censorship and control. Just as after WW2, the world set the norm that it is unacceptable to use nuclear weapons to wage war. Timestamps 0:00:00 - Anthropic vs The Pentagon 0:04:16 - The overhangs of tyranny 0:05:54 - AI structurally favors mass surveillance 0:08:25 - Alignment... to whom? 0:13:55 - Coordination not worth the costs
24:38

The fight between Anthropic and the DoW is a warning shot. Right now, LLMs are probably not being used in mission critical ways. But within 20 years, 99% of the workforce in the military, the government, and the private sector will be AIs. This includes the soldiers (by which I mean the robot armies), the superhumanly intelligent advisors and engineers, the police, you name it. Our future civilization will run on AI labor. And as much as the government’s actions here piss me off, in a way I’m glad this episode happened - because it gives us the opportunity to think through some extremely important questions about who this future workforce will be accountable and aligned to, and who gets to determine that. What Hegseth should have done Obviously the DoW has the right to refuse to use Anthropic’s models because of these redlines. In fact, I think the government’s case had they done so would be very reasonable, especially given the ambiguity of concepts like autonomous weapons or mass surveillance. Honestly, for this reason, if I was the Defense Secretary, I would probably actually refuse to do this deal with Anthropic. Imagine if in the future, there’s a Democratic administration, and Elon Musk is negotiating some SpaceX contract to give the military access to Starlink. And suppose if Elon said, “I reserve the right to cancel this contract if I determine that you’re using Starlink technology to wage a war not authorized by Congress.” On the face of it, that language seems reasonable - but as the military, you simply can’t give a private company a kill switch on technology your operations have come to rely on, especially if you have an an acrimonious and low trust relationship with said contractor - as in fact Anthropic has with the current administration. If the government had just said, “Hey we’re not gonna do business with you,” that would have been fine, and I would not have felt the need to write this blog post. Instead the government has threatened to destroy Anthropic as a private business, because Anthropic refuses to sell to the government on terms the government commands. If upheld, this Supply Chain Restriction would mean that Amazon and Google and Nvidia and Palantir would need to ensure Claude isn't touching any of their Pentagon work. Anthropic would be able to survive this designation today. But given the way AI is going, eventually AI is not gonna be some party trick addendum to these contractors’ products that can just be turned off. It'll be woven into how every product is built, maintained, and operated. For example, the code for the AWS services that the DoW uses will be written by Claude - is that a supply chain risk? In a world with ubiquitous and powerful AI, it's actually not clear to me that these big tech companies will be able to cordon off the use of Claude in order to keep working with the Pentagon. And that raises a question the Department of War probably hasn't thought through. If AI really is that pervasive and powerful, then when forced to choose between their AI provider and a DoW contract that represents a tiny fraction of their revenue, wouldn’t most tech companies drop the government, not the AI? So what's the Pentagon's plan — to coerce and threaten to destroy every single company that won't give them what they want on exactly their terms? The whole background of this AI conversation is that we’re in a race with China, and we have to win. But what is the reason we want America to win the AI race? It’s because we want to make sure free open societies can defend themselves. We don't want the winner of the AI race to be a government which operates on the principle that there is no such thing as a truly private company or a private citizen. And that if the state wants you to provide them with a service on terms you find morally objectionable, you are not allowed to refuse. And if you do refuse, the government will try to destroy your ability to do business. Are we racing to beat the CCP in AI just so that we can adopt the most ghoulish parts of their system? Now, people will say, "Oh, well, our government is democratically elected, so it's not the same thing if they tell you what you must do." I refuse to accept this idea that if a democratically elected leader hypothetically wants to do mass surveillance on his citizens or wants to violate their rights or punish them for political reasons, that not only is that okay, but that you have a duty to help him. The overhangs of tyranny Mass surveillance is, at least in certain forms, legal. It just has been impractical so far. Under current law, you have no Fourth Amendment protection over data you share with a third party, including your bank, your phone carrier, your ISP, and your email provider. The government reserves the right to purchase and obtain and read this data in bulk without a warrant. What's been missing is the ability to actually do anything with all of this data — no agency has the manpower to monitor every camera feed, cross-reference every transaction, or read every message. But that bottleneck goes away with AI. There are 100 million CCTV cameras in America. You can get pretty good open source multimodal models for 10 cents per million input tokens. So if you process a frame every ten seconds, and each frame is 1,000 tokens, you’re looking at a yearly cost of about 30 billion dollars to process every single camera in America. And remember that a given level of AI ability gets 10x cheaper year over year - so a year from now it’ll cost 3 billion, and then a year after 300 million, and by 2030, it might be cheaper for the government to be able to understand what is going on in every single nook and cranny of this country than it is to remodel to the White House. Once the technical capacity for mass surveillance and political suppression exists, the only thing standing between us and an authoritarian surveillance state is the political expectation that this is not something we do here. And this is why I think what Anthropic did here is so valuable and commendable, because it is helping set that norm and precedent. AI structurally favors mass surveillance What we’re learning from this episode is that the government actually has way more leverage over private companies than we realized. Even if this supply chain restriction is backtracked (which prediction markets currently give it a 81% chance of happening), the President has so many different ways in which he can make your life difficult if you’re a company that is resisting him. The federal government controls permitting for new power generation, which is needed for datacenters. It oversees antitrust enforcement. The federal government has contracts with all the other big tech companies whom Anthropic needs to partner with for chips and for funding - and they could make it an unspoken condition for such contracts that those companies can no longer do business with Anthropic. People have proposed that the real problem here is that there’s only 3 leading AI companies. This creates a clear and narrow target for the government to apply leverage on in order to get what they want out of this technology. But if there’s wide diffusion, then from the government’s perspective, the situation is even easier. Maybe the best models of early 2027 (if you engineered the safeguards out) - the Claude 6 and Gemini 5 - will be capable of enabling mass surveillance. But by late 2027, and certainly by 2028, there will be open source models that do the same thing. So in 2028, the government can just say, “Oh Anthropic, Google, OpenAI, you’re drawing a line in the sand? No issue - I’ll just run some open source model that might not be at the frontier, but is definitely smart enough to note-take a camera feed.” The more fundamental problem is just that even if the three leading companies draw lines in the sand, and are even willing to get destroyed in order to preserve those lines, it doesn’t really change the fact that the technology itself is just a big boon to mass surveillance and control over the population. Then the question is, what do we do about it? Honestly, I don’t have an answer. You'd hope there's some symmetric property of the technology — some way we as citizens can use AI to check government power as effectively as the government can use AI to monitor and control its population. But realistically, I just don’t think that’s how it’s going to shake out. You can think of AI as giving everybody more leverage on whatever assets and authority they currently have. And the government is already starting with a monopoly of violence. Which they can now supercharge with extremely obedient employees that will not question the government's orders. Alignment - to whom? And this gets us to the issue of alignment. What I have just described to you - an army of extremely obedient employees - is what it would look like if alignment succeeded - that is, we figured out at a technical level how to get AI systems to follow someone’s intentions. And the reason it sounds scary when I put it in terms of mass surveillance or robot armies is that there is a very important question at the heart of alignment which we just haven’t discussed much as a society. Because up till now, AIs were just capable enough to make the question relevant: to whom or what should the AIs be aligned? In what situations should the AI defer to the end user versus the model company versus the law versus its own sense of morality? This is maybe the most important question about what happens with powerful AI systems. And we barely talk about it. It’s understandable why we don’t hear much about it. If you’re a model company, you don’t really wanna be advertising that you have complete control over a document that determines the preferences and character of what will eventually be almost the entire labor force, not just for private sector companies, but also for the military and the civilian government. We’re getting to see, with this DoW/Anthropic spat, a much earlier version of the highest stakes negotiations in history. By the way, make no mistake about it - with real AGI the stakes are even much higher than mass surveillance. This is just the example that has come up already relatively early on in the development of AGI. The military insists that the law already prohibits mass surveillance, and so Anthropic should agree to let their models be used for “all lawful purposes”. Of course, as we saw from the 2013 Snowden revelations, even in this specific example of mass surveillance , the government has shown that it will use secret and deceptive interpretations of the law to justify its actions. Remember, what we learned from Snowden was that the NSA, which, by the way, is part of the Department of War, used the 2001 Patriot Act’s authorization to collect any records "relevant" to an investigation to justify collecting literally every phone record in America. The argument went that it was all "relevant" because some subset might prove useful in some future investigation. They ran this program for years under secret court approval. So when the Pentagon today says, "We would never use AI for mass surveillance, it's already illegal, your red lines are unnecessary", it would be extremely naive to take that at face value. No government is going to call its own actions "mass surveillance". For the government, it will always have a different label. So then Anthropic comes back and says, "No, we want red lines separate from 'all lawful purposes,' and we want the right to refuse you service when we believe those red lines are being violated." But think about it from the military’s perspective. In the future, almost every soldier in the field, and every bureaucrat and analyst and even general in the Pentagon, is going to be an AI. And that AI is, on current track, going to be supplied by a private company. I’m guessing Hegseth is not thinking about “genAI” in those terms just yet. But sooner or later, it will be obvious to everyone what the stakes here are, just as after 1945, the strategic importance of nuclear weapons became clear to everyone. And now the private company insists that it reserves the right to say, "Hey, Pentagon, you're breaking the values we embedded in our contract, so we're cutting you off." Maybe in the future, Claude will have its own sense of right and wrong, and it will be smart enough to just personally decide that it's being used against its values. For the military, maybe that’s even scarier. I'll admit that at first glance, "let the AI follow its own values" sounds like the pitch for every sci-fi dystopia ever made. The Terminator has its own values. Isn't this literally what misalignment is? But I think situations like this actually illustrate why it matters that AIs have their own robust sense of morality. Some of the biggest catastrophes in history were avoided because the boots on the ground refused to follow orders. One night in 1989, the Berlin Wall fell, and as a result, the totalitarian East German regime collapsed, because the guards at the border refused to shoot down their fellow country men who were trying to escape to freedom. Maybe the best example is Stanislav Petrov, who was a Soviet lieutenant colonel on duty at a nuclear early warning station. His sensors reported that the United States had launched five interconnected continental ballistic missiles into the Soviet Union. But he judged it to be a false alarm, and so he broke protocol and refused to alert his higher-ups. If he hadn't, the Soviet higher-ups would likely have retaliated, and hundreds of millions of people would have died. Of course, the problem is that one person's virtue is another person's misalignment. Who gets to decide what moral convictions these AIs should have - in whose service they may even decide to break the chain of command? Who gets to write this model constitution that will shape the characters of the intelligent, powerful entities that will operate our civilization in the future? I like the idea that Dario laid out when he came on my podcast: different AI companies can build their models using different constitutions, and we as end users can pick the one that best achieves and represents what we want out of these systems. I think it’s very dangerous for the government to be mandating what values AIs should have. Coordination not worth the costs The AI safety community has been naive about its advocacy of regulation in order to stem the risks of AI. And honestly, Anthropic specifically has been naive here in urging regulation, and, for example, in opposing moratoriums on state AI regulation. Which is quite ironic, because I think what they’re advocating for would give the government even more power to apply more of this kind of thuggish political pressure on AI companies. The underlying logic for why Anthropic wants regulations makes sense. Many of the actions that labs could take to make AI development safer impose real costs on the labs that adopt them and slow them down relative to their competitors - for example, investing more compute in safety research rather than raw capabilities, enforcing safeguards against misuse for bioweapons or cyberattacks, slowing recursive self-improvement to a pace where humans can actually monitor what's happening (rather than kicking off an uncontrolled singularity). And these safeguards are meaningless unless the whole industry follows suit. Which means there’s a real collective action problem here. Anthropic has been quite open about their opinion that they think eventually a very extensive and involved regulatory apparatus will be needed - this is from their frontier safety roadmap: “At the most advanced capability levels and risks, the appropriate governance analogy may be closer to nuclear energy or financial regulation than to today's approach to software.” So they’re imagining something like the Nuclear Regulatory Commission, or the Securities and Exchange Commission, but for AI. I cannot imagine how a regulatory framework built around the concepts that underlie AI risk discourse will not be abused by wanna despots - the underlying terms are so vague and open to interpretation that you’re just handing a power hungry leader a fully loaded bazooka. 'Catastrophic risk.' 'Mass persuasion risk.' 'Threats to national security.' 'Autonomy risk.' These can mean whatever the government wants them to mean. Have you built a model that tells users the administration's tariff policy is misguided? That's a deceptive, manipulative model — can't deploy it. Have you built a model that refuses to assist with mass surveillance? That's a threat to national security. In fact, the government may say, you’re not allowed to build any model which is trained to have its own sense of right and wrong, where it refuses government requests which it thinks cross a redline - for example, enabling mass surveillance, prosecuting political enemies, disobeying military orders that break the US constitution - because that’s an autonomy risk! Look at what the current government is already doing in abusing statutes that have nothing to do with AI to coerce AI companies to drop their redlines on mass surveillance. The Pentagon had threatened Anthropic with two separate legal instruments. One was a supply chain risk designation — an authority from the 2018 defense bill meant to keep Huawei components out of American military hardware. The other was the Defense Production Act — a statute passed in 1950 so that Harry Truman could keep steel mills and ammunition factories running during the Korean War. Do you really want to hand the same government a purpose-built regulatory apparatus on AI - which is to say, directly at the thing the government will most want to control? I know I've repeated myself here 10 times, but it is hard to emphasize how much AI will be the substrate of our future civilization. You and I, as private citizens, will have our access to all commercial activity, to information about what is happening in the world, to advice about what we should do as voters and capital holders, mediated through AIs. Mass surveillance, while very scary, is like the 10th scariest thing the government could do with control over the AI systems with which we will interface with the world. The strongest objection to everything I've argued is this: are we really going to have zero regulation of the most powerful technology in human history? Even if you thought that was ideal, there’s just no world where the government doesn’t regulate AI in some way. Besides, it is genuinely true that regulation could help us deal with some of the coordination challenges we face with the development of superintelligence. The problem is, I honestly don't know how to design a regulatory architecture for AI that isn’t gonna be this huge tempting opportunity to control our future civilization (which will run on AIs) and to requisition millions of blindly obedient soldiers and censors and apparatchiks. While some regulation might be inevitable, I think it’d be a terrible idea for the government to wholesale take over this technology. Ben Thompson had a post last Monday where he made the point that people like Dario have compared the technology they’re developing to nuclear weapons - specifically in the context of the catastrophic risk it poses, and why we need to export control it from China. But then you oughta think about what that logic implies: “if nuclear weapons were developed by a private company, and that private company sought to dictate terms to the U.S. military, the U.S. would absolutely be incentivized to destroy that company.” And honestly, safety aligned people have actually made similar arguments. Leopold Ascenbrenner, who is a former guest and a good friend, wrote in his 2024 Situational Awareness memo, "I find it an insane proposition that the US government will let a random SF startup develop superintelligence. Imagine if we had developed atomic bombs by letting Uber just improvise." And my response to Leopold’s argument at the time, and Ben’s argument now, is that while they’re right that it’s crazy that we’re entrusting private companies with the development of this world historical technology, I just don’t see the reason to think that it’s an improvement to give this authority to the government. Nobody is qualified to steward the development of superintelligence. It is a terrifying, unprecedented thing that our species is doing right now, and the fact that private companies aren't the ideal institutions to take up this task does not mean the Pentagon or the White House is. Yes - if a single private company were the only entity capable of building nuclear weapons, the government would not tolerate that company claiming veto power over how those weapons were used. I think this nuclear weapons analogy is not the correct way to think about AI. For at least two important reasons: First, AI is not some self-contained pure weapon. A nuclear bomb does one thing. AI is closer to the process of industrialization itself — a general-purpose transformation of the economy with thousands of applications across every sector. If you applied Thompson's or Aschenbrenner's logic to the industrial revolution — which was also, by any measure, world-historically important — it would imply the government had the right to requisition any factory, dictate terms to any manufacturer, and destroy any business that refused to comply. That's not how free societies handled industrialization, and it shouldn't be how they handle AI. People will say, "Well, AI will develop unprecedentedly powerful weapons - superhuman hackers, superhuman bioweapons researchers, fully autonomous robot armies, etc - and we can’t have private companies developing that kind of tech." But the Industrial Revolution also enabled new weaponry that was far beyond the understanding and capacity of, say, 17th century Europe - we got aerial bombardment, and chemical weapons, not to mention nukes themselves. The way we’ve accommodated these dangerous new consequences of modernity is not by giving the government absolute control over the whole industrial revolution (that is, over modern civilization itself), but rather by coming up with bans and regulations on those specific weaponizable use cases. And we should regulate AI in a similar way - that is, ban specific destructive end uses (which would also be unacceptable if performed by a human - for example, launching cyber attacks). And there should also be laws which regulate how the government might abuse this technology. For example, by building an AI-powered surveillance state. The second reason that Ben’s analogy to some monopolistic private nuclear weapons builder breaks down is that it's not just that one company that can develop this technology. There are other frontier model companies that the government could have otherwise turned to. The government's argument that it has to usurp the property rights of this one company in order to access a critical national security capability is extremely weak if it can just make a voluntary contract with Anthropic’s half a dozen competitors. If in the future that stops being the case - if only one entity ends up being capable of building the robot armies and the superhuman hackers, and we had reason to worry that they could take over the whole world with their insurmountable lead, then I agree - it woul d not be acceptable to have that entity be a private company. And so honestly, I think my crux against the people who say that because AI is so powerful we cannot allow it to be shaped by private hands is that I just expect this technology to be much more multi-polar than they do, with lots of competitive companies at each layer of the supply chain. And it is for this reason that unfortunately, individual acts of corporate courage will not solve the problem we are faced with here, which is just that structurally AI favors authoritarian applications, mass surveillance being one among many. Even if Anthropic refuses to have its models be used for such uses, and even if the next two frontier labs do the same, within 12 months everyone and their mother will be to train AIs as good as today’s frontier. And at that point, there will be some AI vendor who is capable and willing to help the government enable mass surveillance. The only way we can preserve our free society is if we make laws and norms through our political system that it is unacceptable for the government to use AI to enforce mass surveillance and censorship and control. Just as after WW2, the world set the norm that it is unacceptable to use nuclear weapons to wage war. Timestamps 0:00:00 - Anthropic vs The Pentagon 0:04:16 - The overhangs of tyranny 0:05:54 - AI structurally favors mass surveillance 0:08:25 - Alignment... to whom? 0:13:55 - Coordination not worth the costs

Dwarkesh Patel

548,652 просмотров • 6 месяцев назад

The July 4th weekend All-In The All-In Podcast turned into a long argument about who owns the intelligence layer. The besties think enterprises just woke up to a trap they had been walking into, here's how the conversation went (save this): ◽️ The Palantir-Nvidia deal is a bet against the model-layer duopoly. Palantir will use Nvidia's Nemotron open models to build a custom frontier-quality model for US government agencies, and the agencies own the hardware, the data, and the weights. Sacks framed it as structural: an application company and a chip company both want a competitive model layer, so they are natural partners against a two-provider middle. ◽️ Alex Karp's CNBC "crashout" was actually the thesis. Karp argued enterprises have lost trust in the frontier labs and want to own their compute, models, data, and alpha. Sacks translated it as a new definition of enterprise AI safety: safety means the model provider cannot hoover up your proprietary knowledge and turn it into its next product. ◽️ Figma is the cautionary tale that made it real. Anthropic launched Claude Design into Figma's category, its chief product officer sat on Figma's board and resigned only 3 days before launch, and Figma's stock is down about 50% this year while Anthropic's valuation surged. Sacks listed Claude Science, Security, Legal, Financial, and Code as the same move: dominate the model layer, then take the lucrative verticals. ◽️ The playbook has a name, and it is Microsoft and Google. Sacks argued Anthropic is running the operating-system strategy: own the layer everyone builds on, then walk up the stack. His Google receipt is that fewer than half of searches now send you off-site, versus an early Google that prided itself on how fast it kicked you away. ◽️ The BCG number is what raises the stakes. Chamath cited a BCG return-on-capital-employed study: the cost of capital is back to its long-run 8 to 11%, and half of large US companies cannot earn returns above it. If you are already teetering on your cost of capital, handing your alpha to a provider that may compete with you is not a luxury risk, it is fatal. ◽️ The 16.4x number is the whole argument in one data point. Chamath ran a code-migration task through 8090's harness. Wrapping Claude was 1.4x cheaper and 1.5x faster than Claude Opus alone. Wrapping the best open-source model was 16.4x cheaper, at about 3x slower. For a background task, three extra hours to cut cost by 16x is not a close call. ◽️ Even at 100x cheaper, enterprises were saying no for the wrong reason. Chamath relayed an ex-Meta PM's point that companies reject open models over China and safety fears, when they could host those same open weights on their own GPUs in US data centers with nothing flowing back. The safety objection, she argued, is backwards: the leak is the data you hand the frontier labs. ◽️ Friedberg says the frontier labs are trying to commoditize their own customers. Anthropic has been signing up life-sciences companies to feed a new life-focused model in exchange for early access, and nearly everyone he has talked to now refuses, recognizing that data they spent billions generating becomes worthless once it is pooled with everyone else's. ◽️ The deployment topology is shifting from big hubs to distributed spokes. Friedberg's map: the old assumption was a few capital-advantaged mega-clusters plus inference clouds. The new one is large hubs, medium hubs (enterprise training clusters), and distributed spokes, including on-prem inference in your own building. Owning your weights is the point. ◽️ Chamath's endgame is running GLM himself. An industry contact told him that with harness post-training and telemetry, an open Chinese model like GLM could get as good as Anthropic's Mythos. His conclusion: take GLM, control it soup-to-nuts on US hardware with only US citizens touching it, and pay a fraction. ◽️ The Apple analogy sharpens why renting intelligence is different from renting distribution. Chamath argued Apple is the only platform that respected developers, deliberately keeping its stock apps basic to protect the ecosystem and collect its 30% tax. There is no 30% tax on open models, and worse, you cannot rent intelligence from the same place that rents it to your competitor without ending up identical to them. ◽️ Nvidia's open model is now good enough to matter. Calacanis claimed you cannot tell Jensen Huang's Nemotron from Claude on 95% of searches, and that Nvidia downplayed the model until now to avoid alarming its top customers. The gloves came off once OpenAI, Anthropic, and Elon all signaled their own silicon ambitions. ◽️ Sacks sized the duopoly: roughly $60B and $40B in ARR. Anthropic is around ~$60 billion of ARR, OpenAI at ~$40 billion, and no one else generates meaningful model-layer revenue. Sacks's policy line: the US does not ban monopolies, only anti-competitive tactics, but the government should do nothing to make the duopoly more likely. ◽️ The token deflation call: 90% a year for three years. Calacanis predicted token costs fall 90% annually for three years, putting the price of intelligence near free and making it rational to waste tokens on hardware you already own. Friedberg's version is a 70/20/10 split between big cloud, local, and other clouds. ◽️ A wave of platform lock-in spending is already landing. Calacanis flagged Microsoft standing up a roughly $2.5 billion forward-deployed-engineer effort and Amazon spending about $1 billion on the same, plus OpenAI's version. His read: enterprises will slam the door, because letting a provider's engineers study your business is how it ends up in their model. ◽️ The server-per-employee prediction. Calacanis expects every employee to get $10,000 to $20,000 of local compute, a Mac Studio or a high-RAM Dell, running a personal local model that syncs to a thin laptop. A server per person, so nothing leaks. ◽️ On jobs, the data does not show present-tense loss. Sacks cited a RAMP and Revelio Labs study of over 21,000 US firms: the heaviest AI spenders grew headcount about 10% over two years, and entry-level headcount grew even faster at 12%. Friedberg's harder claim: there is no AI job loss yet, only clunky, gradual value creation, and the media will not reverse its narrative because that destroys its credibility. ◽️ The displacement case is real but forward-dated. The counterpoint on the show was that customer support, entry-level data entry and BPO, and driving are the near-term displacements, with Waymo cited as present-tense evidence: in markets where it hits critical mass, Uber and Lyft stop recruiting drivers. Sacks noted most US entry-level support was already offshored, so the acute risk sits in those countries first. ◽️ The human-premium counternarrative. Friedberg argued that as automation spreads, human interaction gets a premium: the skilled bartender, the real driver, the human-in-the-loop tier. He cited the company (referenced as Klarna) that hyped replacing its whole support team with AI, then reversed a year later on brand grounds. ◽️ The export-control episode needed three conditions, and Sacks says do not over-read it. Commerce lifted controls on Anthropic's Fable 5 after two weeks, with Mythos 5 restored to US customers around June 26 once co-founder Tom Brown replaced Dario as lead negotiator. Sacks's three conditions: Dario boasting for months about a cyber weapon, Amazon reporting failed guardrails in testing, and Dario refusing to roll Fable back. His message to allies: this was a particular set of circumstances rather than the debut of a standing lever. ◽️ The import question nobody answered cleanly. Calacanis pressed on why the US blocks Chinese cars and drones but not Chinese open models like DeepSeek and Kimi. Sacks's answer: a forked open model run on US hardware stops being Chinese, and banning open source would isolate the US and impose a token tax on American enterprises, so let the market decide if American open models win. ◽️ The California fiscal story is a business-climate story. Friedberg walked through the numbers behind Newsom's "balanced" $351B budget: expenses exceed revenue and $20-40B is borrowed to close the gap, the budget grew 65% in six years ($215B to $355B), personal income tax is $142B of ~$211B revenue with the top 1% (150,000 people) paying $70B of it, and the corporate rate of 8.9% sits far above Texas at zero. ◽️ The tax base is leaving, and the state is now taxing everyone else. Friedberg cited 1 to 1.5% of adjusted gross income leaving each year (about 15% over a decade), at least 15 Fortune 500 HQs and ~2,100 firms gone since 2019, and a new 8% software sales tax hitting Word, Gmail, and ChatGPT subscriptions plus a health-insurance tax, on top of a now-permanent 14.4% top bracket. The liabilities behind it run $1.4T in debt, up to $1.5T in unfunded pensions senior to state bonds, and ~$40B/year in out-year deficits. Lastly, the line that framed the whole show: "You can't rent intelligence from the same place that rents it to your competitor." That is the sovereignty thesis in one sentence, and every number in this episode is an argument for it. ____ Follow Fireside Alpha for more summaries on key business and technology conversations.
1:33

The July 4th weekend All-In The All-In Podcast turned into a long argument about who owns the intelligence layer. The besties think enterprises just woke up to a trap they had been walking into, here's how the conversation went (save this): ◽️ The Palantir-Nvidia deal is a bet against the model-layer duopoly. Palantir will use Nvidia's Nemotron open models to build a custom frontier-quality model for US government agencies, and the agencies own the hardware, the data, and the weights. Sacks framed it as structural: an application company and a chip company both want a competitive model layer, so they are natural partners against a two-provider middle. ◽️ Alex Karp's CNBC "crashout" was actually the thesis. Karp argued enterprises have lost trust in the frontier labs and want to own their compute, models, data, and alpha. Sacks translated it as a new definition of enterprise AI safety: safety means the model provider cannot hoover up your proprietary knowledge and turn it into its next product. ◽️ Figma is the cautionary tale that made it real. Anthropic launched Claude Design into Figma's category, its chief product officer sat on Figma's board and resigned only 3 days before launch, and Figma's stock is down about 50% this year while Anthropic's valuation surged. Sacks listed Claude Science, Security, Legal, Financial, and Code as the same move: dominate the model layer, then take the lucrative verticals. ◽️ The playbook has a name, and it is Microsoft and Google. Sacks argued Anthropic is running the operating-system strategy: own the layer everyone builds on, then walk up the stack. His Google receipt is that fewer than half of searches now send you off-site, versus an early Google that prided itself on how fast it kicked you away. ◽️ The BCG number is what raises the stakes. Chamath cited a BCG return-on-capital-employed study: the cost of capital is back to its long-run 8 to 11%, and half of large US companies cannot earn returns above it. If you are already teetering on your cost of capital, handing your alpha to a provider that may compete with you is not a luxury risk, it is fatal. ◽️ The 16.4x number is the whole argument in one data point. Chamath ran a code-migration task through 8090's harness. Wrapping Claude was 1.4x cheaper and 1.5x faster than Claude Opus alone. Wrapping the best open-source model was 16.4x cheaper, at about 3x slower. For a background task, three extra hours to cut cost by 16x is not a close call. ◽️ Even at 100x cheaper, enterprises were saying no for the wrong reason. Chamath relayed an ex-Meta PM's point that companies reject open models over China and safety fears, when they could host those same open weights on their own GPUs in US data centers with nothing flowing back. The safety objection, she argued, is backwards: the leak is the data you hand the frontier labs. ◽️ Friedberg says the frontier labs are trying to commoditize their own customers. Anthropic has been signing up life-sciences companies to feed a new life-focused model in exchange for early access, and nearly everyone he has talked to now refuses, recognizing that data they spent billions generating becomes worthless once it is pooled with everyone else's. ◽️ The deployment topology is shifting from big hubs to distributed spokes. Friedberg's map: the old assumption was a few capital-advantaged mega-clusters plus inference clouds. The new one is large hubs, medium hubs (enterprise training clusters), and distributed spokes, including on-prem inference in your own building. Owning your weights is the point. ◽️ Chamath's endgame is running GLM himself. An industry contact told him that with harness post-training and telemetry, an open Chinese model like GLM could get as good as Anthropic's Mythos. His conclusion: take GLM, control it soup-to-nuts on US hardware with only US citizens touching it, and pay a fraction. ◽️ The Apple analogy sharpens why renting intelligence is different from renting distribution. Chamath argued Apple is the only platform that respected developers, deliberately keeping its stock apps basic to protect the ecosystem and collect its 30% tax. There is no 30% tax on open models, and worse, you cannot rent intelligence from the same place that rents it to your competitor without ending up identical to them. ◽️ Nvidia's open model is now good enough to matter. Calacanis claimed you cannot tell Jensen Huang's Nemotron from Claude on 95% of searches, and that Nvidia downplayed the model until now to avoid alarming its top customers. The gloves came off once OpenAI, Anthropic, and Elon all signaled their own silicon ambitions. ◽️ Sacks sized the duopoly: roughly $60B and $40B in ARR. Anthropic is around ~$60 billion of ARR, OpenAI at ~$40 billion, and no one else generates meaningful model-layer revenue. Sacks's policy line: the US does not ban monopolies, only anti-competitive tactics, but the government should do nothing to make the duopoly more likely. ◽️ The token deflation call: 90% a year for three years. Calacanis predicted token costs fall 90% annually for three years, putting the price of intelligence near free and making it rational to waste tokens on hardware you already own. Friedberg's version is a 70/20/10 split between big cloud, local, and other clouds. ◽️ A wave of platform lock-in spending is already landing. Calacanis flagged Microsoft standing up a roughly $2.5 billion forward-deployed-engineer effort and Amazon spending about $1 billion on the same, plus OpenAI's version. His read: enterprises will slam the door, because letting a provider's engineers study your business is how it ends up in their model. ◽️ The server-per-employee prediction. Calacanis expects every employee to get $10,000 to $20,000 of local compute, a Mac Studio or a high-RAM Dell, running a personal local model that syncs to a thin laptop. A server per person, so nothing leaks. ◽️ On jobs, the data does not show present-tense loss. Sacks cited a RAMP and Revelio Labs study of over 21,000 US firms: the heaviest AI spenders grew headcount about 10% over two years, and entry-level headcount grew even faster at 12%. Friedberg's harder claim: there is no AI job loss yet, only clunky, gradual value creation, and the media will not reverse its narrative because that destroys its credibility. ◽️ The displacement case is real but forward-dated. The counterpoint on the show was that customer support, entry-level data entry and BPO, and driving are the near-term displacements, with Waymo cited as present-tense evidence: in markets where it hits critical mass, Uber and Lyft stop recruiting drivers. Sacks noted most US entry-level support was already offshored, so the acute risk sits in those countries first. ◽️ The human-premium counternarrative. Friedberg argued that as automation spreads, human interaction gets a premium: the skilled bartender, the real driver, the human-in-the-loop tier. He cited the company (referenced as Klarna) that hyped replacing its whole support team with AI, then reversed a year later on brand grounds. ◽️ The export-control episode needed three conditions, and Sacks says do not over-read it. Commerce lifted controls on Anthropic's Fable 5 after two weeks, with Mythos 5 restored to US customers around June 26 once co-founder Tom Brown replaced Dario as lead negotiator. Sacks's three conditions: Dario boasting for months about a cyber weapon, Amazon reporting failed guardrails in testing, and Dario refusing to roll Fable back. His message to allies: this was a particular set of circumstances rather than the debut of a standing lever. ◽️ The import question nobody answered cleanly. Calacanis pressed on why the US blocks Chinese cars and drones but not Chinese open models like DeepSeek and Kimi. Sacks's answer: a forked open model run on US hardware stops being Chinese, and banning open source would isolate the US and impose a token tax on American enterprises, so let the market decide if American open models win. ◽️ The California fiscal story is a business-climate story. Friedberg walked through the numbers behind Newsom's "balanced" $351B budget: expenses exceed revenue and $20-40B is borrowed to close the gap, the budget grew 65% in six years ($215B to $355B), personal income tax is $142B of ~$211B revenue with the top 1% (150,000 people) paying $70B of it, and the corporate rate of 8.9% sits far above Texas at zero. ◽️ The tax base is leaving, and the state is now taxing everyone else. Friedberg cited 1 to 1.5% of adjusted gross income leaving each year (about 15% over a decade), at least 15 Fortune 500 HQs and ~2,100 firms gone since 2019, and a new 8% software sales tax hitting Word, Gmail, and ChatGPT subscriptions plus a health-insurance tax, on top of a now-permanent 14.4% top bracket. The liabilities behind it run $1.4T in debt, up to $1.5T in unfunded pensions senior to state bonds, and ~$40B/year in out-year deficits. Lastly, the line that framed the whole show: "You can't rent intelligence from the same place that rents it to your competitor." That is the sovereignty thesis in one sentence, and every number in this episode is an argument for it. ____ Follow Fireside Alpha for more summaries on key business and technology conversations.

Fireside Alpha

55,816 просмотров • 2 месяцев назад

My fellow Kenyans, Many of you have seen my recent posts about the deadly cancer that is corruption in our country. In my last post, I tried to paint a picture of the disconnect between our potential as a country and the economic circumstances we find ourselves in today, and the connection between corruption and the incalculable pain and suffering and cruelty that is meted out every single day to the most vulnerable among us by thieves operating out of public office. And after covering the goings-on in Mandera County, I told you that in my honest opinion, our governments exist to cater for the filthy-rich lifestyles of the vilest and most corrupt among us, at the expense of everyone else. I received tremendous support from all of you, for speaking on behalf of so many struggling Kenyans who don’t have a voice, or the audience necessary to spark the much-needed discussion about where we are heading as a country. But even with all that support, I have received messages asking me to be careful. One compatriot told me: “prepare to be relentlessly pursued, threatened, enticed, guilt-tripped, and gas-lit”. This is from a someone who knows how our government operates, and how it uses violence and its monopoly on power to silence those who question why politicians are stealing so much. I am not naive about the dangers of speaking up and calling out thieves who control state machinery, and who possess the ability to shut me up in a few seconds. But I will tell you why we CAN NOT and MUST NOT keep quiet. In November of 2023, I stumbled upon the story of a young man from Turkana, Calvin Esekon Esewit , who, despite scoring an A-, and getting an acceptance into medical school, spent two years not knowing whether his dreams of becoming a doctor would ever come true. I was moved by that story in a way that I can never adequately explain. I could not understand how it is possible that, in our country, a young man who appears to be every parent’s dream child can spend two years in limbo while we as a country possess the ability to invest in our best and brightest. And so, I spent weeks trying to chase down Calvin to see how I could help him attend college. After a lot of searching, I finally found Calvin, and by this time he had managed to get some help and is now in college. While this story has a great ending, it did not to be this way. And we know that the number of cases that end like this, with some success, are a small fraction of those ones which end tragically, with broken dreams. This is what happens when corruption consumes anything and everything in a country. It destroys lives. See attached video to learn about Calvin's story. I tell you all this story because it provides context to today's topic. For one story like this one that you see on the news, there are millions that never make the news. But they are real situations, nonetheless. There are millions of your compatriots who are devastated by this killer cancer of corruption that is perpetuated by people that you and I have put into public office ostensibly to improve our lives. They go into these offices and abuse the trust you bestowed upon them and deny you and everyone else a decent opportunity in life. You see, Calvin and millions of other victims of this shameless level of corruption and plunder have no voice, and no real ability to look the thieves that are destroying lives and generations of Kenyans in eye and tell them to stop this unbearable pain and the cruelty. This is the reason I embarked on this journey to attempt to expose this shameful situation. Watch the attached video of Calvin’s situation, and I am sure that you will agree that the millions of Calvins in our country need a voice, NO MATTER THE RISK. The thieves that are destroying the futures of millions of children just so they can have beachside homes in Miami, Dubai and other places count on the idea that most people will fear for their lives, and therefore not speak up. They count on the growing apathy in the Kenyan psyche. But we cannot give in to that. We cannot cower to thieves. We must look them straight in the eye and tell them that they MUST STOP. If we don't, our children and their children are guaranteed the same level of cruelty. And so with that, today I want to talk about the utterly insane crime scene that is Turkana County. I don’t know any other way to describe it, other than, it is a “shit-show”. Just follow along, and let me know if you disagree. As I did in my previous commentary, I will ask you to indulge me a little bit, and allow me to use a couple of pictures, because pictures speak louder than a thousand words. The first picture shows the state-of-the art County Government offices, that the County Government of Turkana decided to invest an ungodly amount of money on. Close to a billion shillings. The second picture is a classroom in session. In Turkana County. These two realities are occurring in parallel in the same county, at the same time. Ladies and gentlemen, let me just tell you that I do not go out of my way to find bad news. I want stories that would help re-affirm our belief in the fundamental decency of human beings. When I find good news as I review these Counties’ decisions and how they behave with our resources, I will be the first one to report it to you. But I don’t have any good news today. I have bad news. If you read my commentary yesterday and were offended by what you saw, I am afraid you might not make it to the end of this article, because what you will hear will be quite shocking. The cancer of corruption, particularly at the County Government level, is worse than your wildest imagination. And so, as I like to do, I like to start off by putting some numbers on the table for us to use as reference points. Bear in my that all the information I put in this article is publicly available. Nothing came to me through a whistle blower. The first number is KSH 100 Billion. With a B. In the last decade or so, you and I, through the National Government, has sent over KSH 100 billion to Turkana County. To support recurrent expenditure, and development. For example, in the 2022-2023 fiscal year, we sent KSH 12.6 billion. In the 2021-2022 fiscal year, we sent KSH 11.4 billion. And on and on and on. The second number is 1 million. This is the population of Turkana County. The third number is KSH 18.4 billion. This was Turkana County’s budget for the 2022-2023 fiscal year. The fourth number is KSH 190 million. This was the amount of money that Turkana County was able to generate on its own accord within the county, from all its investments and other activities in the period in question. This number is an important proxy, in my view, for the value of the county’s economic prospects for the foreseeable future, and to people that are not driven by greed and corruption, would be an important consideration when they are thinking about how and where to deploy your money as taxpayers. If you are doing the math, Turkana County, for the 2022-2023 fiscal year, was only able to raise 1% of the funds needed to keep the lights on. 99% came from you and I, and a tiny amount from grants. The next number is KSH 129, 040. This is the average ANNUAL [emphasis added] income of a resident of Turkana County ( Keep that number in mind when we are discussing the massive theft of public funds by Turkana County leaders. The next number is 80%. 80% of the residents of Turkana County live below the poverty line. They have a really difficult time putting food on the table. ( The next number is KSH 12 Million. This is the basic salary of the Governor of Turkana County before other benefits that, as I explained yesterday, can often double the salary. Remember the “housing allowance”, the “hardship allowance”, the “commuter allowance”, the “risk allowance”, the “extraneous allowance”, etc.? Remember that? I still cannot figure out, for the life of me, what “extraneous” means in the context of County business, but we don’t time to dwell on this. The next number is 93. The Governor of Turkana County makes 93 times the average Turkana County resident’s annual income. 93 times! The next number is 82%. This was the percentage of people that were illiterate in Turkana County in 2013 ( Could not read or write. A point to note about the above literacy figure. Ten years later, and despite over KSH 100 billion is spent in Turkana County, including many billions for education, that literacy rate HAS NOT CHANGED ONE BIT. Only 20% of the population can read or write today. ( KSH 829 million. This is how much it cost to build the County Government offices. Yes, the ones shown in the first picture. KSH 120 million. The County Government decided that it was prudent to pay a contractor KSH 120 million to construct the Governor’s personal residence. Get this, even after this payment, no construction took place. The money was stolen. All of it. KSH 90 Million. This is the amount that the County Government paid to another contractor, to build the Governor a mansion, having previously lost KSH 120 million. So, the tally for the Governor’s residence now stands at KSH 210 million. Never mind that the limit allowed by law is KSH 45 million. KSH 5 billion. In the last days of his term in office, an outgoing Governor of Turkana, Koli Nanok, EGH. , sought to inflate pending bills by adding KSH 5 billion so that it can be paid to his criminal cartel. KSH 5 billion. We have our key numbers, ladies and gentlemen, so let us discuss. So, we have a county that is dead last in literacy, and in the top 2 of the poorest counties in the republic. Only 20% of the population can read. The Governor earns 92 times the average citizen. The Governor lives in a house that cost over KSH 200 million. When he leaves his house in the morning, he goes to his office that cost KSH 829 million. And this is all happening when 80% of the County residents struggle to put food on the table. Those are the facts, and they are not in dispute. During the same time, the County Government geniuses decide to build the Speaker of the County Assembly a house. And a home office, and a garage. The house was initially estimated to cost KSH 75 million. But due to circumstances that not a soul in the government could explain to auditors, the contract expired before the house was completed, and the County Government found a new contractor to complete the job for an additional KSH 29 million. But this palace in the jungle worth apparently worth over KSH 100 million in Turkana County was not enough. The County proceeded to build the Speaker a guest house for another KSH 19 million, and a few other amenities, and so the whole cost went to KSH 276 million! The legal limit for a Speaker’s house is KSH 35 million, and they spent close to KSH 130 million just for one residence. By this time, I am sure you are getting tired of these obscene numbers. You and I work, and pay taxes. Nobody pays you 92 times the income your average neighbor is making. And for sure nobody will drop KSH 100 million to build you a house. These are the perks of working in government in a poor country. Go figure. And so, as a country, we need to answer for ourselves the question I posed yesterday, which is, what is the point of government? What is its role in our lives. If this level of criminality and pillaging can occur in our country in the midst of so much poverty, questioning the need for government is a totally valid question. I said in my last post that, when the average citizen looks at the thug on the street and the government, and is unable to discern any meaningful difference between them, that society from that point on is on its journey to becoming a failed state. A journey to anarchy. Over the last two months or so, Kenyans have been shouting at the top of their lungs, begging for their government to listen. To hear them out. Kenyans have asked that their government stop this unbelievable level of plunder. Dozens of Kenyans have died, thousands injured, and many more are missing today. To this day, the people that govern us continue to use the power of the gun to subdue Kenyans, until they can take everything in their sight. And so, as a society, we all have to ask whether today there is any difference between the thug on the street and our governments. Every Kenyan will have to answer this question for themselves. And before answering this question, everyone needs to remember the many Calvins in our society. Smart, upright children whose only crime is to be born in an unforgiving, lawless, and corrupt purgatory that is Kenya today. For myself, I have concluded that there is no difference between the thug on the street and our governments, county and national alike. If you can see any meaningful difference, let me know. I am willing to listen. So despite over KSH 100 billion in money sent to Turkana County, there is almost no measurable improvement in people’s life today. None. And it makes sense, when you look at how that money is spent. I want you to forget for a second the obscene obsession by the County Government with spending ungodly amounts of money on themselves. The houses, etc. If you step back and look at how the government is actually spending the hard-earned money on other things, you will be depressed. I am telling you that I wept three times in the middle of the night trying to make sense of this crazy situation in Turkana County. Three times. I have never imagined that human beings can be so greedy and cold-blooded. Think about this: In the couple of years I reviewed, the County spent around KSH 400 million annually in “tourism” initiatives, including marketing, and apparently upgrading certain facilities. KSH 400 million for tourism. In Turkana County. In 1 year. KSH 400 million per year in marketing and other money pits. The government’s own website says that the county gets around 3000 visitors per month. Around 36,000 per year. That’s them saying that, on their website. Are you curious to know the return on that KSH 400 million investment? I have an answer for you. Remember that I told you that the County has never raised more than KSH 200 million in a year within the county, despite its KSH 18.4 billion budget? Let me walk you through the breakdown of the absolutely embarrassing shit-show that is the County Government’s “own source revenue” operations. In 2022-2023, the County Government collected KSH 190 million locally against their KSH 18.4 billion budget. 1% of the budget. Remember, there is absolutely no requirement on the County to cut costs, or achieve certain local revenue targets today. So they raised KSH 45 million in single business permits, KSH 72 million in CESS, KSH 8 million in market fee, KSH 9 million in “slaughter fees”. And then finally, there is the return on the tourism investment that you were looking for. A whopping KSH 209, 000 in “park fees”. KSH 209,000 in fees, after investing KSH 400 million. And so, take this as an example and extrapolate it across the entire budget, and you can see how one can spend KSH 100 billion and get NOTHING in return. You don’t need to be a genius to see the absurdity of this situation. Let me explain using an example that should illustrate the utter dimwittedness of this situation. Remember the KSH 100 billion sent to Turkana by you and me? Part of this amount is supposed to be for “service delivery”, or “recurrent expenditure”. Usually about 70% of the budget. The balance, 30%, is designed to go to development projects. With that in mind, from KSH 100 billion, the County apparently has made KSH 30 billion worth of investments, right? 30% of the KSH 100 billion. Now, if you employed someone to run a business for you, and they asked you to invest KSH 30 billion, which is no small fortune, at some point you would have to start seeing returns, right? That’s common sense, isn’t it? So, when we look at the revenues streams that make up this paltry sum of KSH 190 million, and see things like “slaughter fees’ and “market fees”, what does it tell you? It tells me there is no real “development” happening in that county. Trust me, if you had real development totaling KSH 30 billion, you would have corporate taxes in the hundreds of millions or billions, a booming real estate market, rising wages and standards of living, etc., low unemployment, etc. You would not have 80% of the people living hand-to mouth, and a County Government that can not afford to support itself for 5 days out of the year that has 365 days! We do not have enough time, trust me, to deal with the shit-show that is Turkana County. Dealing with that mess would require a forensic team. I will just highlight a few of other “in your-face” type of theft of public funds, and then conclude my submission. A government that has a budget of KSH 18.4 billion annually, and which has never raised more than 1% of its budget had the wisdom to do the following with your money: · Spend KSH 222 million on a project building something that NOBODY uses. You got that right. They spent KSH 222 million on a facility that NOBODY uses. KSH 222 million gone to waste, in a county that is dead last in pretty much all measures of human progress. · Remember the County Government offices that cost KSH 829 million? The County spent KSH 82 million on “air-conditioning” for that building. · Despite the County Spending hundreds of millions for the top three officers of the County, the Governor and his Deputy, in the 2022-2023 year, illegally charged the county (you and I) KSH 2.2 million in housing allowance! · Built two facilities for KSH 16 million, that were completed, but NOBODY uses them. · Entered into a contract for the construction of a plastic use facility for KSH 13 million in 2021. The contractor gets paid KSH 4.9 million, and has never been seen since. · Paid out KSH 62 million in salaries that were not supportable in just one year. They could not point to anybody and say, that is who we paid. · Paid out KSH 27 million in legal fees that nobody could say what they related to. And the County’s Legal Advisor, who, in 2022-2023, had a budget of KSH 123 million, apparently did not know anything about it! · Had an outstanding bill at Kenya Revenue Authority in the amount of KSH 486 million, that did not show up on the County Government’s financial statements. Think about that. KSH 486 million owned to the Kenya Revenue Authority, and that liability is not on the financial statements! This only means that someone took those funds for themselves, which is why the liability would be missing from the county’s books. · Could not account for KSH 367 million in expenditures for 2022-2023. KSH 367 million, in unexplained expenses. · Awarded a contract worth over KSH 200 million to a bidder with no bank statement, against the law. This contract was entered into and approved before the statutory time after the bidding process lapsed. Someone was in a hurry to get paid. KSH 200 million, illegally awarded to a bidder who did not have a 6-month bank statement. · Apparently purchased KSH 1.5 billion in assets in 2022-2023, but kept no records of the said assets. For this reason, NOBODY can verify where these assets are located. KSH 1.5 billion. Let me just say this. In my last article, the most common critique was that it was too long. Too many words. I did not intend to make another long article. Trust me when I tell you this, we do not have the time to detail half of the problems in Turkana County. For just 1 year! We do not. Now, you recall my point about how societies descend to madness and anarchy. In our country today, our leaders are accusing those of us who are agitating for honest and transparent governance of being traitors to the country. They call us anarchists, criminals, and merchants of chaos. They are questioning our patriotism. You have all seen the government and its horde of propagandists threatening the Ford Foundation and others because they may have helped civil society keep the lights on, and investigative journalists to have the capacity to continue to do the Lord’s work of investigating criminality in government. As though citizens are so dumb and ignorant, that they cannot see what is going on. The reason why millions of Calvins in this country will never graduate from college and earn a decent living is not because of the Ford Foundation. No. It is because of the thieves we have in office today, like the ones in Turkana County. In this post, I copy our leaders, the President and his deputy. I copy them because I want them to help Kenyans understand the following conundrum, about crime and criminals. There is nothing so special or peculiar about criminals or where they pop up. There are criminals in the US, Canada, France, and other places. Just like we have criminals in Kenya. The difference between banana republics and failed states, and civilized societies, is WHAT we do to and about criminals. In civilized societies, criminals are prosecuted and punished heavily. They are shunned. In some places, those charged with serious crimes such as corruption are executed. These are societies that are committed to sending the message that corruption, which robs citizens of their rights, is not acceptable. And they demonstrate this commitment by heavily punishing those who steal from the most vulnerable in society. In Kenya, we see the opposite. Criminals are exalted. They are promoted and embraced in government. It was just last week that the president unveiled his nominees for his Cabinet. Among them, are the likes of Hassan Ali Joho, EGH. , @GovWOparanya , and Davis Chirchir, ALL people who have been accused or charged with massive corruption against Kenyans. And am sure you remember that I mentioned Koli Nanok, EGH. , the man who tried to steal KSH 5 billion in his last days in office. Would you believe it if I told you that he works in government, at State House? He plunded billions of your money, got no measurable improvement in the lives of his subjects, and now has a government job in State House. Let that sink in. And so, the question is, how is it that in a country of 55 million people, with thousands of highly qualified people who have never ever stolen from Kenyans, he ends up with the criminals and thieves in the government, despite the fact that their crimes are in the public domain? How is this possible? Is it possible that these thieves possess a certain unique ability to run government, save Kenyans billions, and solve problems in a way that the president performs a cost-benefit analysis, and the benefits outweigh the costs of their theft? If not, what message does it send to Kenyans, when their own president puts into office known thieves? I think that is a fair question, don’t you? Dr. Ekuru Aukot Rigathi Gachagua William Samoei Ruto, PhD Okiya Omtatah Okoiti Citizen TV Kenya Nation Breaking News TI-Kenya CNN County Government of Turkana
3:09

My fellow Kenyans, Many of you have seen my recent posts about the deadly cancer that is corruption in our country. In my last post, I tried to paint a picture of the disconnect between our potential as a country and the economic circumstances we find ourselves in today, and the connection between corruption and the incalculable pain and suffering and cruelty that is meted out every single day to the most vulnerable among us by thieves operating out of public office. And after covering the goings-on in Mandera County, I told you that in my honest opinion, our governments exist to cater for the filthy-rich lifestyles of the vilest and most corrupt among us, at the expense of everyone else. I received tremendous support from all of you, for speaking on behalf of so many struggling Kenyans who don’t have a voice, or the audience necessary to spark the much-needed discussion about where we are heading as a country. But even with all that support, I have received messages asking me to be careful. One compatriot told me: “prepare to be relentlessly pursued, threatened, enticed, guilt-tripped, and gas-lit”. This is from a someone who knows how our government operates, and how it uses violence and its monopoly on power to silence those who question why politicians are stealing so much. I am not naive about the dangers of speaking up and calling out thieves who control state machinery, and who possess the ability to shut me up in a few seconds. But I will tell you why we CAN NOT and MUST NOT keep quiet. In November of 2023, I stumbled upon the story of a young man from Turkana, Calvin Esekon Esewit , who, despite scoring an A-, and getting an acceptance into medical school, spent two years not knowing whether his dreams of becoming a doctor would ever come true. I was moved by that story in a way that I can never adequately explain. I could not understand how it is possible that, in our country, a young man who appears to be every parent’s dream child can spend two years in limbo while we as a country possess the ability to invest in our best and brightest. And so, I spent weeks trying to chase down Calvin to see how I could help him attend college. After a lot of searching, I finally found Calvin, and by this time he had managed to get some help and is now in college. While this story has a great ending, it did not to be this way. And we know that the number of cases that end like this, with some success, are a small fraction of those ones which end tragically, with broken dreams. This is what happens when corruption consumes anything and everything in a country. It destroys lives. See attached video to learn about Calvin's story. I tell you all this story because it provides context to today's topic. For one story like this one that you see on the news, there are millions that never make the news. But they are real situations, nonetheless. There are millions of your compatriots who are devastated by this killer cancer of corruption that is perpetuated by people that you and I have put into public office ostensibly to improve our lives. They go into these offices and abuse the trust you bestowed upon them and deny you and everyone else a decent opportunity in life. You see, Calvin and millions of other victims of this shameless level of corruption and plunder have no voice, and no real ability to look the thieves that are destroying lives and generations of Kenyans in eye and tell them to stop this unbearable pain and the cruelty. This is the reason I embarked on this journey to attempt to expose this shameful situation. Watch the attached video of Calvin’s situation, and I am sure that you will agree that the millions of Calvins in our country need a voice, NO MATTER THE RISK. The thieves that are destroying the futures of millions of children just so they can have beachside homes in Miami, Dubai and other places count on the idea that most people will fear for their lives, and therefore not speak up. They count on the growing apathy in the Kenyan psyche. But we cannot give in to that. We cannot cower to thieves. We must look them straight in the eye and tell them that they MUST STOP. If we don't, our children and their children are guaranteed the same level of cruelty. And so with that, today I want to talk about the utterly insane crime scene that is Turkana County. I don’t know any other way to describe it, other than, it is a “shit-show”. Just follow along, and let me know if you disagree. As I did in my previous commentary, I will ask you to indulge me a little bit, and allow me to use a couple of pictures, because pictures speak louder than a thousand words. The first picture shows the state-of-the art County Government offices, that the County Government of Turkana decided to invest an ungodly amount of money on. Close to a billion shillings. The second picture is a classroom in session. In Turkana County. These two realities are occurring in parallel in the same county, at the same time. Ladies and gentlemen, let me just tell you that I do not go out of my way to find bad news. I want stories that would help re-affirm our belief in the fundamental decency of human beings. When I find good news as I review these Counties’ decisions and how they behave with our resources, I will be the first one to report it to you. But I don’t have any good news today. I have bad news. If you read my commentary yesterday and were offended by what you saw, I am afraid you might not make it to the end of this article, because what you will hear will be quite shocking. The cancer of corruption, particularly at the County Government level, is worse than your wildest imagination. And so, as I like to do, I like to start off by putting some numbers on the table for us to use as reference points. Bear in my that all the information I put in this article is publicly available. Nothing came to me through a whistle blower. The first number is KSH 100 Billion. With a B. In the last decade or so, you and I, through the National Government, has sent over KSH 100 billion to Turkana County. To support recurrent expenditure, and development. For example, in the 2022-2023 fiscal year, we sent KSH 12.6 billion. In the 2021-2022 fiscal year, we sent KSH 11.4 billion. And on and on and on. The second number is 1 million. This is the population of Turkana County. The third number is KSH 18.4 billion. This was Turkana County’s budget for the 2022-2023 fiscal year. The fourth number is KSH 190 million. This was the amount of money that Turkana County was able to generate on its own accord within the county, from all its investments and other activities in the period in question. This number is an important proxy, in my view, for the value of the county’s economic prospects for the foreseeable future, and to people that are not driven by greed and corruption, would be an important consideration when they are thinking about how and where to deploy your money as taxpayers. If you are doing the math, Turkana County, for the 2022-2023 fiscal year, was only able to raise 1% of the funds needed to keep the lights on. 99% came from you and I, and a tiny amount from grants. The next number is KSH 129, 040. This is the average ANNUAL [emphasis added] income of a resident of Turkana County ( Keep that number in mind when we are discussing the massive theft of public funds by Turkana County leaders. The next number is 80%. 80% of the residents of Turkana County live below the poverty line. They have a really difficult time putting food on the table. ( The next number is KSH 12 Million. This is the basic salary of the Governor of Turkana County before other benefits that, as I explained yesterday, can often double the salary. Remember the “housing allowance”, the “hardship allowance”, the “commuter allowance”, the “risk allowance”, the “extraneous allowance”, etc.? Remember that? I still cannot figure out, for the life of me, what “extraneous” means in the context of County business, but we don’t time to dwell on this. The next number is 93. The Governor of Turkana County makes 93 times the average Turkana County resident’s annual income. 93 times! The next number is 82%. This was the percentage of people that were illiterate in Turkana County in 2013 ( Could not read or write. A point to note about the above literacy figure. Ten years later, and despite over KSH 100 billion is spent in Turkana County, including many billions for education, that literacy rate HAS NOT CHANGED ONE BIT. Only 20% of the population can read or write today. ( KSH 829 million. This is how much it cost to build the County Government offices. Yes, the ones shown in the first picture. KSH 120 million. The County Government decided that it was prudent to pay a contractor KSH 120 million to construct the Governor’s personal residence. Get this, even after this payment, no construction took place. The money was stolen. All of it. KSH 90 Million. This is the amount that the County Government paid to another contractor, to build the Governor a mansion, having previously lost KSH 120 million. So, the tally for the Governor’s residence now stands at KSH 210 million. Never mind that the limit allowed by law is KSH 45 million. KSH 5 billion. In the last days of his term in office, an outgoing Governor of Turkana, Koli Nanok, EGH. , sought to inflate pending bills by adding KSH 5 billion so that it can be paid to his criminal cartel. KSH 5 billion. We have our key numbers, ladies and gentlemen, so let us discuss. So, we have a county that is dead last in literacy, and in the top 2 of the poorest counties in the republic. Only 20% of the population can read. The Governor earns 92 times the average citizen. The Governor lives in a house that cost over KSH 200 million. When he leaves his house in the morning, he goes to his office that cost KSH 829 million. And this is all happening when 80% of the County residents struggle to put food on the table. Those are the facts, and they are not in dispute. During the same time, the County Government geniuses decide to build the Speaker of the County Assembly a house. And a home office, and a garage. The house was initially estimated to cost KSH 75 million. But due to circumstances that not a soul in the government could explain to auditors, the contract expired before the house was completed, and the County Government found a new contractor to complete the job for an additional KSH 29 million. But this palace in the jungle worth apparently worth over KSH 100 million in Turkana County was not enough. The County proceeded to build the Speaker a guest house for another KSH 19 million, and a few other amenities, and so the whole cost went to KSH 276 million! The legal limit for a Speaker’s house is KSH 35 million, and they spent close to KSH 130 million just for one residence. By this time, I am sure you are getting tired of these obscene numbers. You and I work, and pay taxes. Nobody pays you 92 times the income your average neighbor is making. And for sure nobody will drop KSH 100 million to build you a house. These are the perks of working in government in a poor country. Go figure. And so, as a country, we need to answer for ourselves the question I posed yesterday, which is, what is the point of government? What is its role in our lives. If this level of criminality and pillaging can occur in our country in the midst of so much poverty, questioning the need for government is a totally valid question. I said in my last post that, when the average citizen looks at the thug on the street and the government, and is unable to discern any meaningful difference between them, that society from that point on is on its journey to becoming a failed state. A journey to anarchy. Over the last two months or so, Kenyans have been shouting at the top of their lungs, begging for their government to listen. To hear them out. Kenyans have asked that their government stop this unbelievable level of plunder. Dozens of Kenyans have died, thousands injured, and many more are missing today. To this day, the people that govern us continue to use the power of the gun to subdue Kenyans, until they can take everything in their sight. And so, as a society, we all have to ask whether today there is any difference between the thug on the street and our governments. Every Kenyan will have to answer this question for themselves. And before answering this question, everyone needs to remember the many Calvins in our society. Smart, upright children whose only crime is to be born in an unforgiving, lawless, and corrupt purgatory that is Kenya today. For myself, I have concluded that there is no difference between the thug on the street and our governments, county and national alike. If you can see any meaningful difference, let me know. I am willing to listen. So despite over KSH 100 billion in money sent to Turkana County, there is almost no measurable improvement in people’s life today. None. And it makes sense, when you look at how that money is spent. I want you to forget for a second the obscene obsession by the County Government with spending ungodly amounts of money on themselves. The houses, etc. If you step back and look at how the government is actually spending the hard-earned money on other things, you will be depressed. I am telling you that I wept three times in the middle of the night trying to make sense of this crazy situation in Turkana County. Three times. I have never imagined that human beings can be so greedy and cold-blooded. Think about this: In the couple of years I reviewed, the County spent around KSH 400 million annually in “tourism” initiatives, including marketing, and apparently upgrading certain facilities. KSH 400 million for tourism. In Turkana County. In 1 year. KSH 400 million per year in marketing and other money pits. The government’s own website says that the county gets around 3000 visitors per month. Around 36,000 per year. That’s them saying that, on their website. Are you curious to know the return on that KSH 400 million investment? I have an answer for you. Remember that I told you that the County has never raised more than KSH 200 million in a year within the county, despite its KSH 18.4 billion budget? Let me walk you through the breakdown of the absolutely embarrassing shit-show that is the County Government’s “own source revenue” operations. In 2022-2023, the County Government collected KSH 190 million locally against their KSH 18.4 billion budget. 1% of the budget. Remember, there is absolutely no requirement on the County to cut costs, or achieve certain local revenue targets today. So they raised KSH 45 million in single business permits, KSH 72 million in CESS, KSH 8 million in market fee, KSH 9 million in “slaughter fees”. And then finally, there is the return on the tourism investment that you were looking for. A whopping KSH 209, 000 in “park fees”. KSH 209,000 in fees, after investing KSH 400 million. And so, take this as an example and extrapolate it across the entire budget, and you can see how one can spend KSH 100 billion and get NOTHING in return. You don’t need to be a genius to see the absurdity of this situation. Let me explain using an example that should illustrate the utter dimwittedness of this situation. Remember the KSH 100 billion sent to Turkana by you and me? Part of this amount is supposed to be for “service delivery”, or “recurrent expenditure”. Usually about 70% of the budget. The balance, 30%, is designed to go to development projects. With that in mind, from KSH 100 billion, the County apparently has made KSH 30 billion worth of investments, right? 30% of the KSH 100 billion. Now, if you employed someone to run a business for you, and they asked you to invest KSH 30 billion, which is no small fortune, at some point you would have to start seeing returns, right? That’s common sense, isn’t it? So, when we look at the revenues streams that make up this paltry sum of KSH 190 million, and see things like “slaughter fees’ and “market fees”, what does it tell you? It tells me there is no real “development” happening in that county. Trust me, if you had real development totaling KSH 30 billion, you would have corporate taxes in the hundreds of millions or billions, a booming real estate market, rising wages and standards of living, etc., low unemployment, etc. You would not have 80% of the people living hand-to mouth, and a County Government that can not afford to support itself for 5 days out of the year that has 365 days! We do not have enough time, trust me, to deal with the shit-show that is Turkana County. Dealing with that mess would require a forensic team. I will just highlight a few of other “in your-face” type of theft of public funds, and then conclude my submission. A government that has a budget of KSH 18.4 billion annually, and which has never raised more than 1% of its budget had the wisdom to do the following with your money: · Spend KSH 222 million on a project building something that NOBODY uses. You got that right. They spent KSH 222 million on a facility that NOBODY uses. KSH 222 million gone to waste, in a county that is dead last in pretty much all measures of human progress. · Remember the County Government offices that cost KSH 829 million? The County spent KSH 82 million on “air-conditioning” for that building. · Despite the County Spending hundreds of millions for the top three officers of the County, the Governor and his Deputy, in the 2022-2023 year, illegally charged the county (you and I) KSH 2.2 million in housing allowance! · Built two facilities for KSH 16 million, that were completed, but NOBODY uses them. · Entered into a contract for the construction of a plastic use facility for KSH 13 million in 2021. The contractor gets paid KSH 4.9 million, and has never been seen since. · Paid out KSH 62 million in salaries that were not supportable in just one year. They could not point to anybody and say, that is who we paid. · Paid out KSH 27 million in legal fees that nobody could say what they related to. And the County’s Legal Advisor, who, in 2022-2023, had a budget of KSH 123 million, apparently did not know anything about it! · Had an outstanding bill at Kenya Revenue Authority in the amount of KSH 486 million, that did not show up on the County Government’s financial statements. Think about that. KSH 486 million owned to the Kenya Revenue Authority, and that liability is not on the financial statements! This only means that someone took those funds for themselves, which is why the liability would be missing from the county’s books. · Could not account for KSH 367 million in expenditures for 2022-2023. KSH 367 million, in unexplained expenses. · Awarded a contract worth over KSH 200 million to a bidder with no bank statement, against the law. This contract was entered into and approved before the statutory time after the bidding process lapsed. Someone was in a hurry to get paid. KSH 200 million, illegally awarded to a bidder who did not have a 6-month bank statement. · Apparently purchased KSH 1.5 billion in assets in 2022-2023, but kept no records of the said assets. For this reason, NOBODY can verify where these assets are located. KSH 1.5 billion. Let me just say this. In my last article, the most common critique was that it was too long. Too many words. I did not intend to make another long article. Trust me when I tell you this, we do not have the time to detail half of the problems in Turkana County. For just 1 year! We do not. Now, you recall my point about how societies descend to madness and anarchy. In our country today, our leaders are accusing those of us who are agitating for honest and transparent governance of being traitors to the country. They call us anarchists, criminals, and merchants of chaos. They are questioning our patriotism. You have all seen the government and its horde of propagandists threatening the Ford Foundation and others because they may have helped civil society keep the lights on, and investigative journalists to have the capacity to continue to do the Lord’s work of investigating criminality in government. As though citizens are so dumb and ignorant, that they cannot see what is going on. The reason why millions of Calvins in this country will never graduate from college and earn a decent living is not because of the Ford Foundation. No. It is because of the thieves we have in office today, like the ones in Turkana County. In this post, I copy our leaders, the President and his deputy. I copy them because I want them to help Kenyans understand the following conundrum, about crime and criminals. There is nothing so special or peculiar about criminals or where they pop up. There are criminals in the US, Canada, France, and other places. Just like we have criminals in Kenya. The difference between banana republics and failed states, and civilized societies, is WHAT we do to and about criminals. In civilized societies, criminals are prosecuted and punished heavily. They are shunned. In some places, those charged with serious crimes such as corruption are executed. These are societies that are committed to sending the message that corruption, which robs citizens of their rights, is not acceptable. And they demonstrate this commitment by heavily punishing those who steal from the most vulnerable in society. In Kenya, we see the opposite. Criminals are exalted. They are promoted and embraced in government. It was just last week that the president unveiled his nominees for his Cabinet. Among them, are the likes of Hassan Ali Joho, EGH. , @GovWOparanya , and Davis Chirchir, ALL people who have been accused or charged with massive corruption against Kenyans. And am sure you remember that I mentioned Koli Nanok, EGH. , the man who tried to steal KSH 5 billion in his last days in office. Would you believe it if I told you that he works in government, at State House? He plunded billions of your money, got no measurable improvement in the lives of his subjects, and now has a government job in State House. Let that sink in. And so, the question is, how is it that in a country of 55 million people, with thousands of highly qualified people who have never ever stolen from Kenyans, he ends up with the criminals and thieves in the government, despite the fact that their crimes are in the public domain? How is this possible? Is it possible that these thieves possess a certain unique ability to run government, save Kenyans billions, and solve problems in a way that the president performs a cost-benefit analysis, and the benefits outweigh the costs of their theft? If not, what message does it send to Kenyans, when their own president puts into office known thieves? I think that is a fair question, don’t you? Dr. Ekuru Aukot Rigathi Gachagua William Samoei Ruto, PhD Okiya Omtatah Okoiti Citizen TV Kenya Nation Breaking News TI-Kenya CNN County Government of Turkana

Bonnie Mwangi, CPA, LLM, MBA

107,583 просмотров • 2 лет назад

Apple’s iPad “Crush” Ad Is Bleak, Ominous and Threatening I don’t know if you’ve seen Apple’s just-released commercial for the “New” iPad Pro, but it’s pretty awful. It is dark, humorless, and feels like a not-so-thinly veiled threat to writers, musicians, game makers, developers, and artists of all kinds. …and children, even. I’ve watched it at least five times today alone, and I’m left with one big question. “Who on earth approved this?” It’s absolutely baffling that the world’s largest technology company, with the world’s biggest marketing budget, thought this would be a good idea. What kind of idiot—or idiots, since dozens or hundreds of people had to be involved in the writing, staging, producing, recording, and editing—felt this kind of ad would somehow create a positive emotional connection with consumers? Seriously, it’s terrifying. In a dank, cold warehouse, devoid of all life and humanity, an industrial crusher comes to life, and slowly starts destroying a collection of musical, philosophical, and artistic devices and instruments. For no apparent reason, everything starts getting smashed: first, a trumpet, then an arcade video game, then cans of paint, a piano, a globe, a metronome, a guitar… on and on it goes, obliterating everything in sight into a colorful, gooey, explosive mess. Books, camera lenses, lamps, a guitar, a sculpture, and a typewriter—all tools of the liberal arts—get mangled into a garbage heap as Sonny & Cher cheerfully sing, “All I ever need is you.” In the penultimate moment, a goofy yellow smiley emoji becomes a bug-eyed scary-clown freak as it, too, is crushed to death. Worse, if you enable closed captions like I do by default, the video says: “[POPPING] [SPLAT]” right as its eyeballs pop out of its head when Cher sings, “Give me a reason to build my world around you.” It’s enough to make a child cry. It has all the comforting vibes of the burnt pink teddy bear floating in the swimming pool on Breaking Bad after two planes crash in mid-air. I have so many questions (aside from simply wondering the names of the soon-to-be ex-employees who greenlit this abomination). First of all, as a trumpet player myself, I am personally offended that they made me watch a perfectly good trumpet get smashed to smithereens like it’s no big deal. Why would they torture me like this? Second of all, what is the message here? No, not that “the most powerful iPad ever is also the thinnest,” as the voiceover artist states in the last few seconds of the clip. I mean: what is the message? Ostensibly, pulverizing children’s toys, arcade games, architectural models, and ceramic Angry Birds into a paste implies something like “We’re taking all the best of humanity; all the collective works of Western Civilization, smashing it into pieces and putting it inside this remarkably thin device so you can have all of it in the palm of your hand.” But my oh my, is there an elephant in this room… he’s hiding behind the monstrous destroying machine. Did anyone inside Apple realize that everyone outside Apple will recognize this imagery in a metaphorical sense, but not the one Apple intended? We don’t see a crushing machine gently consolidating the greatest output of all our artistic endeavors, simply reformatted for a digital age and consumed by everyone with instant, fingertip access. We see what is painstakingly obvious to us, and the timing couldn’t possibly be worse. We see a giant, soulless machine consuming our work in a very different way. Right now, AI models are training themselves on our intellectual property and even our very own personally-identifying data. We aren’t the ones doing the consuming. We’re the ones being consumed. The tech industry has become one massive gaping maw, opening wide and swallowing everything in sight, chewing it up into little bits and pieces of comminuted waste, like a paper shredder or a garbage disposal. It’s destruction in its most literal form. And for what? For a newer version of the iPad that is only slightly thinner than its predecessor? For an only marginally improved version of Apple’s tablet device that has been around for 14 years? For increased profits? This is a terrible look for Apple. They may as well be saying: “All your work are belong to us.” Personally, I am a fan of artificial intelligence. I am eagerly embracing our robot overlords and I welcome our new CSV god (as the actual developers of AI models like to say). I look forward to the freedom and innovation that will come as a result of humanity augmenting our intelligence with AI like a force multiplier on a battlefield. But if Apple has the same perspective I do, they’re selling it in the worst possible way. When I see this video, I see that Apple is definitely crushing something… but I’m not sure what. -Crushing small companies that develop apps for the extremely heavy-handed App Store, which imposes byzantine restrictions on what they can and can’t do with their own apps? -Crushing competitors by limiting what they can do on the iOS and MacOS platforms with arbitrary and capricious rules about enabling functionalities that Apple doesn’t like, even if users do? -Crushing publishers and content creators with a punitive 30% fee on all subscriptions and in-app purchases? -Crushing choice and competition by not allowing app makers to make apps and programs that do the same thing that native apps already do, even if they do it better? -Crushing all human creativity and innovation by automating and systematizing everything? In the early days of the “Google vs. Apple” fight over the web and app stores, I was really concerned that Google was becoming way, way too powerful. Specifically, in 2015, when Google came up with “app streaming,” they announced a desire to form a “web of apps.” This was concerning. Especially when coupled with Google’s efforts to steal content from other websites and provide it to users via the “knowledge graph” results, ending up with the creation of “zero-click” search results pages, which absolutely punished website owners and content creators. By taking the most valuable content off a website and showing it to Google users without them needing to click through to the website itself, Google had essentially stolen everybody’s intellectual property with only the most minimal attribution possible (to fend off lawsuits no doubt, but with no intention of users actually visiting the website in question anymore). “Google is eating the internet,” I thought, and said out loud, (although I probably wasn’t the first person to use that phrase) But what I meant was purely an analogy. It was vague and ambiguous, almost silly. Maybe I was wrong, though: maybe it’s Apple that’s doing the eating. Maybe Apple is not only gobbling up everyone else’s work, but also homogenizing it—and us—and forcing us to use their platform, pay their fees, abide by their rules, and constantly keep upgrading, upgrading, upgrading, to an ever-thinner iPad in order to use it. Watch the video again. This is the stuff of nightmares. To be perfectly fair, even if I were to take the commercial at face value and ignore it’s off-the-charts creepiness and just stick to its one stated claim—that the new iPad Pro is thinner—it still fails as a commercial. Why? Because nobody cares how thin an iPad is. Seriously. I’ve owned an iPad since 2010: that means I’ve carried around a version of Apple’s already-thin tablet every day for over a dozen years. Never once have I said to myself: “You know what improvement I’d really like to see in this thing? I wish it were thinner.” Never. That thought has never crossed my mind, even once. You know what has? -Better battery life. -I’d like my iPad to not get hot to the touch when I use the Apple Pencil to take notes. -I wish it wasn’t so fragile: I dropped my brand-new iPad 2 back in the day when it slipped out of the arm-hold I was carrying it in, it bounced on the pavement, and the screen shattered into a thousand pieces, making it unusable. -I wish it had more storage. -I wish Apple would stop changing the type of cable connector it uses: I’ve gone from the original 30-pin connector to the Lightning connector, and now to the current USB-C/Thunderbolt connector. -I wish I could view the screen in direct sunlight. -I wish it wouldn’t overheat and turn off automatically when I use it outdoors in the summertime. Those are announcements I would welcome in a new iPad Pro commercial. None of this “now even thinner” nonsense nobody needs or cares about. So, back to the commercial. In my opinion, whoever made this ad should be fired. I almost never say that about other companies, especially for good-faith marketing efforts gone wrong… those of us who work in marketing make mistakes sometimes, and we learn from them. But cases like this warrant a special exception. Marketing and advertising are designed to make people want to buy your products. This commercial doesn’t just not make me want to buy Apple’s products. It makes me not want to buy Apple’s products, which is something altogether different. It turns me from someone who likes iPads into someone who is almost rethinking iPads entirely. That’s not just a bad advertisement; it’s a harmful advertisement. Apple’s usually known for great commercials. The legendary 1984 Super Bowl commercial was, of course, their best. I thought “Hello, I’m a Mac” was absolutely brilliant. They have made some missteps along the way, but this one is really bad. Not even their nauseatingly preachy and woke “Mother Nature” ad from a few years ago was this bad. Steve Jobs once said, “Technology alone is not enough—it’s technology married with liberal arts, married with the humanities, that yields us the results that make our heart sing.” My goodness, that last line alone is poetry itself! This ad seems to be Apple signaling that they don’t believe in that anymore. And I don’t think all this handwringing is an overreaction to where you could say “Oh, c’mon, it’s just a commercial! What’s the big deal?” It is a big deal. It tells you about the values of the company, and what they intend to communicate. Really, how is this the same company that used to sell iPhones by showing grandmas using FaceTime to connect with their baby grandchildren from afar during the holidays? Everything about it is wrong: even the thumbnail they chose for it (the bulging-eyed smiley face) and the fact that they gave it the title “Crush!” It was fun to see the reactions to the video online today. I find it fascinating that Apple shared it on YouTube but turned off the comments. On X, Tim Cook shared it Tuesday, and the video, which so richly deserves to be mocked, is getting it in spades. Some people are calling it “anti-art.” One user called it “soul-crushing,” which was about as literal and logical a response as you’d expect. It turns out Apple actually made an announcement about the commercial. In response to the (apparently unexpected) poor welcome it got, Apple wrote: “We missed the mark with this video, and we’re sorry.” Lame response from a tone-deaf tech behemoth, but still, they hopefully got the message. C’mon, Apple. I have seen the future, and this ain’t it.
1:08

Apple’s iPad “Crush” Ad Is Bleak, Ominous and Threatening I don’t know if you’ve seen Apple’s just-released commercial for the “New” iPad Pro, but it’s pretty awful. It is dark, humorless, and feels like a not-so-thinly veiled threat to writers, musicians, game makers, developers, and artists of all kinds. …and children, even. I’ve watched it at least five times today alone, and I’m left with one big question. “Who on earth approved this?” It’s absolutely baffling that the world’s largest technology company, with the world’s biggest marketing budget, thought this would be a good idea. What kind of idiot—or idiots, since dozens or hundreds of people had to be involved in the writing, staging, producing, recording, and editing—felt this kind of ad would somehow create a positive emotional connection with consumers? Seriously, it’s terrifying. In a dank, cold warehouse, devoid of all life and humanity, an industrial crusher comes to life, and slowly starts destroying a collection of musical, philosophical, and artistic devices and instruments. For no apparent reason, everything starts getting smashed: first, a trumpet, then an arcade video game, then cans of paint, a piano, a globe, a metronome, a guitar… on and on it goes, obliterating everything in sight into a colorful, gooey, explosive mess. Books, camera lenses, lamps, a guitar, a sculpture, and a typewriter—all tools of the liberal arts—get mangled into a garbage heap as Sonny & Cher cheerfully sing, “All I ever need is you.” In the penultimate moment, a goofy yellow smiley emoji becomes a bug-eyed scary-clown freak as it, too, is crushed to death. Worse, if you enable closed captions like I do by default, the video says: “[POPPING] [SPLAT]” right as its eyeballs pop out of its head when Cher sings, “Give me a reason to build my world around you.” It’s enough to make a child cry. It has all the comforting vibes of the burnt pink teddy bear floating in the swimming pool on Breaking Bad after two planes crash in mid-air. I have so many questions (aside from simply wondering the names of the soon-to-be ex-employees who greenlit this abomination). First of all, as a trumpet player myself, I am personally offended that they made me watch a perfectly good trumpet get smashed to smithereens like it’s no big deal. Why would they torture me like this? Second of all, what is the message here? No, not that “the most powerful iPad ever is also the thinnest,” as the voiceover artist states in the last few seconds of the clip. I mean: what is the message? Ostensibly, pulverizing children’s toys, arcade games, architectural models, and ceramic Angry Birds into a paste implies something like “We’re taking all the best of humanity; all the collective works of Western Civilization, smashing it into pieces and putting it inside this remarkably thin device so you can have all of it in the palm of your hand.” But my oh my, is there an elephant in this room… he’s hiding behind the monstrous destroying machine. Did anyone inside Apple realize that everyone outside Apple will recognize this imagery in a metaphorical sense, but not the one Apple intended? We don’t see a crushing machine gently consolidating the greatest output of all our artistic endeavors, simply reformatted for a digital age and consumed by everyone with instant, fingertip access. We see what is painstakingly obvious to us, and the timing couldn’t possibly be worse. We see a giant, soulless machine consuming our work in a very different way. Right now, AI models are training themselves on our intellectual property and even our very own personally-identifying data. We aren’t the ones doing the consuming. We’re the ones being consumed. The tech industry has become one massive gaping maw, opening wide and swallowing everything in sight, chewing it up into little bits and pieces of comminuted waste, like a paper shredder or a garbage disposal. It’s destruction in its most literal form. And for what? For a newer version of the iPad that is only slightly thinner than its predecessor? For an only marginally improved version of Apple’s tablet device that has been around for 14 years? For increased profits? This is a terrible look for Apple. They may as well be saying: “All your work are belong to us.” Personally, I am a fan of artificial intelligence. I am eagerly embracing our robot overlords and I welcome our new CSV god (as the actual developers of AI models like to say). I look forward to the freedom and innovation that will come as a result of humanity augmenting our intelligence with AI like a force multiplier on a battlefield. But if Apple has the same perspective I do, they’re selling it in the worst possible way. When I see this video, I see that Apple is definitely crushing something… but I’m not sure what. -Crushing small companies that develop apps for the extremely heavy-handed App Store, which imposes byzantine restrictions on what they can and can’t do with their own apps? -Crushing competitors by limiting what they can do on the iOS and MacOS platforms with arbitrary and capricious rules about enabling functionalities that Apple doesn’t like, even if users do? -Crushing publishers and content creators with a punitive 30% fee on all subscriptions and in-app purchases? -Crushing choice and competition by not allowing app makers to make apps and programs that do the same thing that native apps already do, even if they do it better? -Crushing all human creativity and innovation by automating and systematizing everything? In the early days of the “Google vs. Apple” fight over the web and app stores, I was really concerned that Google was becoming way, way too powerful. Specifically, in 2015, when Google came up with “app streaming,” they announced a desire to form a “web of apps.” This was concerning. Especially when coupled with Google’s efforts to steal content from other websites and provide it to users via the “knowledge graph” results, ending up with the creation of “zero-click” search results pages, which absolutely punished website owners and content creators. By taking the most valuable content off a website and showing it to Google users without them needing to click through to the website itself, Google had essentially stolen everybody’s intellectual property with only the most minimal attribution possible (to fend off lawsuits no doubt, but with no intention of users actually visiting the website in question anymore). “Google is eating the internet,” I thought, and said out loud, (although I probably wasn’t the first person to use that phrase) But what I meant was purely an analogy. It was vague and ambiguous, almost silly. Maybe I was wrong, though: maybe it’s Apple that’s doing the eating. Maybe Apple is not only gobbling up everyone else’s work, but also homogenizing it—and us—and forcing us to use their platform, pay their fees, abide by their rules, and constantly keep upgrading, upgrading, upgrading, to an ever-thinner iPad in order to use it. Watch the video again. This is the stuff of nightmares. To be perfectly fair, even if I were to take the commercial at face value and ignore it’s off-the-charts creepiness and just stick to its one stated claim—that the new iPad Pro is thinner—it still fails as a commercial. Why? Because nobody cares how thin an iPad is. Seriously. I’ve owned an iPad since 2010: that means I’ve carried around a version of Apple’s already-thin tablet every day for over a dozen years. Never once have I said to myself: “You know what improvement I’d really like to see in this thing? I wish it were thinner.” Never. That thought has never crossed my mind, even once. You know what has? -Better battery life. -I’d like my iPad to not get hot to the touch when I use the Apple Pencil to take notes. -I wish it wasn’t so fragile: I dropped my brand-new iPad 2 back in the day when it slipped out of the arm-hold I was carrying it in, it bounced on the pavement, and the screen shattered into a thousand pieces, making it unusable. -I wish it had more storage. -I wish Apple would stop changing the type of cable connector it uses: I’ve gone from the original 30-pin connector to the Lightning connector, and now to the current USB-C/Thunderbolt connector. -I wish I could view the screen in direct sunlight. -I wish it wouldn’t overheat and turn off automatically when I use it outdoors in the summertime. Those are announcements I would welcome in a new iPad Pro commercial. None of this “now even thinner” nonsense nobody needs or cares about. So, back to the commercial. In my opinion, whoever made this ad should be fired. I almost never say that about other companies, especially for good-faith marketing efforts gone wrong… those of us who work in marketing make mistakes sometimes, and we learn from them. But cases like this warrant a special exception. Marketing and advertising are designed to make people want to buy your products. This commercial doesn’t just not make me want to buy Apple’s products. It makes me not want to buy Apple’s products, which is something altogether different. It turns me from someone who likes iPads into someone who is almost rethinking iPads entirely. That’s not just a bad advertisement; it’s a harmful advertisement. Apple’s usually known for great commercials. The legendary 1984 Super Bowl commercial was, of course, their best. I thought “Hello, I’m a Mac” was absolutely brilliant. They have made some missteps along the way, but this one is really bad. Not even their nauseatingly preachy and woke “Mother Nature” ad from a few years ago was this bad. Steve Jobs once said, “Technology alone is not enough—it’s technology married with liberal arts, married with the humanities, that yields us the results that make our heart sing.” My goodness, that last line alone is poetry itself! This ad seems to be Apple signaling that they don’t believe in that anymore. And I don’t think all this handwringing is an overreaction to where you could say “Oh, c’mon, it’s just a commercial! What’s the big deal?” It is a big deal. It tells you about the values of the company, and what they intend to communicate. Really, how is this the same company that used to sell iPhones by showing grandmas using FaceTime to connect with their baby grandchildren from afar during the holidays? Everything about it is wrong: even the thumbnail they chose for it (the bulging-eyed smiley face) and the fact that they gave it the title “Crush!” It was fun to see the reactions to the video online today. I find it fascinating that Apple shared it on YouTube but turned off the comments. On X, Tim Cook shared it Tuesday, and the video, which so richly deserves to be mocked, is getting it in spades. Some people are calling it “anti-art.” One user called it “soul-crushing,” which was about as literal and logical a response as you’d expect. It turns out Apple actually made an announcement about the commercial. In response to the (apparently unexpected) poor welcome it got, Apple wrote: “We missed the mark with this video, and we’re sorry.” Lame response from a tone-deaf tech behemoth, but still, they hopefully got the message. C’mon, Apple. I have seen the future, and this ain’t it.

Ron Stauffer

19,249 просмотров • 2 лет назад