Sensitive content

This media may contain sensitive content.

Loading video...

Video Failed to Load

Go Home

i sounded pretty backed up 😖💨 don’t forget to use code RUETHESKUNK at your checkout for DUBBY® ! it gives you 10% off ^~^ 🏷️ (ignore); #nsfw #fart #farting #fartfetish #chubby #giggling #fetish #fyp #nsfwaudio #nulimit #norbra #xvideosِ #goth #emo #gooner #goonette #feet #pov

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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 views • 6 months ago

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 views • 5 months ago

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Akshay 🚀

45,815 views • 3 months ago

How to Build a Proper Product Page It breaks my heart every time I see someone from Brazil, making just $200 a month, spend $40 on a test ad only to get a $2 CPC. Then, they cut the ad at $35 spend with 17 clicks and 0 conversions. What’s even more frustrating is when I visit their site and see it’s a complete mess. It’s like they didn’t even try. That’s why I’m making this post. *Disclaimer: If you're building a brand, this isn’t for you. This is for testing products correctly with a website that’s good enough to convert, but if you’re serious about your brand, hire a Figma designer and a developer to get things done right. As a fun fact, I tested the following product myself (In the video below) and with just one click at a $3 CPC, I got a sale with an $80 AOV (100% CVR). I paused the ads because the CPMs hit $150. If you're interested, save this product for the future. I'll share the creatives i used to ran the product with those who comment below. "jordan, stop teaching high school kids about selling reps and getting them sued by Prada or other big brands, ruining their payment gateways, and crushing their dreams." (with 5 random people only will do it, wouldn't make sense for everyone to be ripping it). Shoutout to Adrian for this one. 🫡 Back to the important stuff: Let’s talk about creating a great product page. First off, ditch the “Buy Now” button. By using this, you miss out on the chance to increase your Average Order Value (AOV) through upsells during checkout. Instead, replace it with an “Add to Cart” button. Also, remove the quantity selector. Hardly anyone uses them on the product page, but they do in the cart. Instead, offer bundles, which you can set up using the Kaching Bundles app or your theme if it supports this feature. The cart experience is crucial, and you can optimize it using the UpCart app. Enable all its product page features so it takes over the standard Shopify cart or your theme’s cart. The built-in cart systems are outdated—they don’t allow upsells like UpCart does. Plus, UpCart directly opens the cart after a product is added, where the upsell option appears at the bottom, increasing your chances of boosting AOV. Pay attention to color schemes. Don’t use neutral colors for headers and buttons if your product features a primary color. A yellow jacket with a black header is like pizza with raspberry syrup—just doesn’t work. If your product images are gray, white, or black, match those with your headers and buttons. Otherwise, play around with colors to give your page some dynamic appeal. Bookmark this site to get color palettes that match your primary color. For exact color matches, download the "ColorZilla" extension, which gives you the exact color code of whatever is under your mouse on the screen. If your product color is #6E402A, you’ll know it and can match it perfectly with your header and buttons, creating a visually appealing contrast like Cider did here below. Right now, when some of you send me these websites, they look like government pages from the early 2000s. Next, consider the typography and button styles. For fonts, use Helvetica Regular for body text and Helvetica Bold for titles, both at a minimum size of 100%. It’s simple and effective. As for buttons, they should have a corner radius of 8px. To change these settings, go to the theme settings - typography/buttons and adjust the buttons and typography accordingly. Rounded buttons create a modern, inviting feel, while full square buttons can give off an outdated vibe. Even casinos in Vegas design their buildings with curves, ensuring that visitors always have a view angle that draws them back in—it’s all about keeping things appealing and engaging. Finally, the product page layout itself should be clean and concise. Use collapsible rows for your product descriptions. No one wants to read a novel, so keep it compact and focused. Images and videos are what sell—this is why we don’t use text-heavy images in our ads; they just bore people. Keep the description short, with enough information to inform but not overwhelm. If you need to include more features, put them in the FAQs section—that’s what they’re for. The goal is to make sure that the "Add to Cart" button is visible as soon as possible once the customer lands on the product page, without overwhelming them but providing just enough information—some key benefits, high-quality images, and buying options in the bundles. Once they hit the cart, the upsells will do their job. Remember, the three essential apps for setting this up are Loox Reviews for customer feedback (use the product widget reviews at the bottom of the page before the FAQs and the rating widget just above the title), Kaching Bundles for offering package deals, and UpCart for optimizing the cart experience. Just for the record, this is to help newcomers and guide them to something taht works, me personally i don't use free themes, but this one i created could convert easily if the product, offer and ads match well. Good luck and keep testing! 🗳🥂💸🤑

Zzzz

42,318 views • 2 years ago

[VID] #KimSoohyun Q&A with Esquire Korea. ⸻ Things Fans Are Curious About Kim Soohyun ID: sookongee_216 Your Asia Tour was almost like a food tour! What are the top 3 most memorable dishes? KSH: Eel rice bowl, and I also remember the cup noodles I had late at night. ID: kshmjung What’s a must-have item you always pack in your bag when traveling? KSH: Since it’s for traveling, I tend to pack an eye mask. Sleep is important! ID: 2zz_i9 Do you still always carry nail clippers in your bag these days? KSH: Nail clippers are always in my bag! ID: yonggyeongji What percentage of your wardrobe is black clothing? KSH: Do I love black that much? Yes, I like it a lot. Recently, I’ve added some clothes with mixed colors, but I think about 90% of my wardrobe is black. ID: ye.seul.hwang You have a nickname, ‘Kim Jeongbyeon’ (Kim Soohyun, the tidying-up perfectionist). What’s your cleaning routine at home? KSH: Since last year, that’s changed a bit. Last year, I was filming Queen of Tears, and this year, it’s because of Knock Off. I don’t tidy up as much anymore. I’ve stopped for now (temporarily). ID: narado_0.5waste You seem to never age. What’s your ‘real’ skincare secret, like your cleansing or face mask routine? KSH: I try to drink a lot of water. I also try not to gain weight, but since I love eating so much, it’s a bit challenging. Still, I’m managing it diligently. Fighting! ID: sookongee_216 What’s your go-to karaoke playlist these days? KSH: It’s been a while since I went to karaoke, but it would probably be the songs I sang at the fan meeting: LOVE by Jo Janghyuk and Fool of Love by The Nuts ID: luv_min.seo Which is your favorite character from Catch! Teenieping? KSH: Clock-out Ping, Shower Ping, Sleep Ping, Pass-out Ping. I’m pretty positive about them. Esquire Staff: You’re not talking about the ones you need the most right now, are you? KSH: Oh… no, no. I’ll be meeting them soon. ID: imrarazz What was the best moment of the year? KSH: Touring Asia for the first time in 10 years and ending with the fan meeting in Seoul. That was in October, and I think it was the most exciting time for me this year. I also enjoyed the final filming of Queen of Tears. (Fighting!) ID: nigajotagu What’s your best golf score? KSH: The best is 150. I’ve been relentless, you know? Fighting! There’s a lot to work on. ID: dreaming_ksh0216 What’s something you want to challenge yourself with in 2025? KSH: I want to improve my golf score from the maximum to the best, so I can update you again. ID: kimnu_216 What kind of role would you like to try next, movie or drama? KSH: Whether it’s a movie or a drama, or whatever genre, I think I’d like to take on a more mature role next time. An ‘adult’ role. ID: _kim216 What’s one memorable scene from your filmography and why? KSH: My Love from the Star was filmed in winter, Queen of Tears was also filmed in winter, and Dream High was filmed in winter, too. Snowy scenes from dramas come to mind. I remember the snowy field scene from My Love from the Star, where I was running around in the snow. The snow will come soon, won’t it? ID: _kim216 What was the hardest part of playing Kim Sungjun in Knock Off? KSH: The most challenging part is that Sungjun constantly explains things, whether to allies or enemies. I’ve been putting a lot of effort into getting those explanations just right. ID: narado_0.5waste You used to underline scripts with a ruler and make analysis notes. How do you analyze scripts now? KSH: I used to check directly on the scriptbook, use a ruler to underline, and tear out scene numbers to organize them. But this year, while filming Knock Off, I embraced new technology! I now use my phone to check scripts and underline. I’ve become the kind of guy who reads scripts on his phone.

soohyunupdates

22,305 views • 1 year ago

My kids skate teacher asked if I could help him with a mini-ramp design. Things quickly got out of control. Let me present, PLY 🛹 Grounded in real-world constraints, materials, and common sizes used in ramp building - I've put together a tool that allows you to not only make a mini-ramp with construction ready plans. BUT infinte ENTIRE skate parks. PLY is truly nuts. I got hyper good performance at 120fps, all browser based, EU/US standards, full BOM, Cutlist, material optimisation and use of off-cuts. Integration with stores like Home Depot and Beijer (gives you an up to date price estimate for your build) based on total material needed. It even estimates how many screws you need, and what types of screws. All down to a +-2.5% margin. Everything is parametric, everything locks into grids based on material constraints (you can detach for bespoke aspects) any orientation, 15 degree banks, 45 degree bowls. But grounded in what can be done with the material you buy. Not only does it output printable PDF, with step by step assembly like it was LEGO. It also creates 3D visuals and step by step 3D assembly guides you can play on your phone or tablet (yes even computer). Per section, or/and ofcourse your entire park. The example below shows a park with elevated floor, but you have ground connectors aswell. So you can make freestanding quarters, roll in ramps, spines, boxes, pyramids, rails, stairs... Even draw your own custom components and save them to your own library. mm, cm, inches, feet, everything is dynamic and you can switch between settings in real-time. Park fly-throughs, assembly timelapses... BUT that's not all, when done, you can also... skate the damn thing. IN THE ACTUAL BROWSER 🤯 So what started as an ask for my kids skate teacher, is now turning into a full CAD/GAME for creating skate parks, based on real-world material constraints. There is so much left to sort out, for example, CONCRETE, yeah, we're doing it. Being able to smoothly shape concrete, calculate the needed volume, rebar, sand, filling material, drainage, slopes, anti-crack lines. Coping molding. If people are not yet getting it, AI assisted development, is absolutely flipping software upside down and inside out. I've not touched a single line of code. none. zero. When it's ready for you to try, I'll share the link. Until then this video will have to do + some more examples below. Follow Linus ✦ Ekenstam if you want more stuff like this in your timeline.

Linus ✦ Ekenstam

171,200 views • 13 days ago

Q: How do you build a great company? In the clip below, Sam Altman walks through 9 things he has seen the best founders do: #1 Get to know your users really well “The best founders do customer support themselves. They go visit their users—in the case of Airbnb they go live with them. You want to get to know your users really really well.” #2 Have a short cycle time & understand compound growth “The cycle here is basically: talk to customer to understand pain point → build product to address that → get product in front of user → see what they do → repeat cycle. This cycle is how you iterate and improve. The law of compound growth being what it is: if you can get 2% better every iteration cycle, your iteration cycle is every four hours rather than every four weeks, and you compound that over the course of a few years, you’ll be in a very very different place. Make it one of your top goals to build one of the fastest iterating companies the world has ever seen.” #3 Make a long-term commitment “Most companies have a 2-3 year time horizon. But companies are almost always a 10 year project if they work. If you think about it that way from the very beginning, you will make very different and much better decisions. I think this is the only arbitrage opportunity left in the market. Almost no one makes a fairly long-term commitment to a new project. But if you do that, you will think in a different way, you will hire different people, and it will work very well.” #4 Stay lean until everything is working really well “In the early days, when you’re experimenting and zig zagging, you’re like a fast little speed boat and want to be able to turn the whole company on a dime. You can’t do that if you’re a big company—cash burn aside, which is another problem. The flexibility of the company basically decreases with the square of the number of employees, so you want to stay really small until you’re sure things are working. Once things are working, then you can get really big.” #5 Resist the urge to hire; especially resist the urge to hire mediocre people “Vinod Khosla has a saying that I love: ‘the team you build is the company you build.’ This is really true and I never appreciated how true this was for a long time. If you build a team of great people and you have a product that people love, you’ll have a 90%+ chance of success. Those are both really hard to do, and they’re independent variables. But don’t ignore the team component. The best CEOs I know spend huge amounts of their time recruiting and retaining good talent.” #6 Relentless execution “You have to keep going, and do things perfectly, and get all of the details right. You have to care too much about every experience that a customer has with your company.” #7 Startups are about not giving up “One of the very best companies in the last YC batch applied 7 times before they got in. This is just a version of what happens in startups all of the time: you get beat down, again, and again, and again. And that last time when you get pushed down and don’t think you have enough energy to get back up—that’s the time it actually works. This is what you sign up for if you’re going to start a startup.” #8 Fiduciary duty to take care of yourself “This is a 10-year marathon and you have a fiduciary duty to your shareholders to take care of yourself. Some people treat startups like an all-nighter: they don’t take care of their health, they don’t sleep, they don’t maintain their personal relationships. It is true that startups are a bad choice for work-life balance. But you have a duty to yourself, your team, and your investors to take care of yourself.” #9 Clear mission “You don’t have to figure this out on Day 1, but all of the most successful startups I’ve been fortunate enough to be a part of pretty quickly—in the first one to two years—figure out a really important mission. It’s this mission that gets people to join them. It drives the founders. It gets the media to write about them. And even if you start off building a project that’s just interesting to you and solves a problem in your life—which is how you should start—remember that you should have a clear mission at some point… That is what will convince people to come help you, and that is how you will build this idea into a huge company with a ton of people that really love your product.” Follow Startup Archive for more tactical startup advice!

Startup Archive

407,763 views • 3 years ago

Q: How do you build a great company? In the clip below, Sam Altman walks through 9 things he has seen the best founders do: #1 Get to know your users really well “The best founders do customer support themselves. They go visit their users—in the case of Airbnb they go live with them. You want to get to know your users really really well.” #2 Have a short cycle time & understand compound growth “The cycle here is basically: talk to customer to understand pain point → build product to address that → get product in front of user → see what they do → repeat cycle. This cycle is how you iterate and improve. The law of compound growth being what it is: if you can get 2% better every iteration cycle, your iteration cycle is every four hours rather than every four weeks, and you compound that over the course of a few years, you’ll be in a very very different place. Make it one of your top goals to build one of the fastest iterating companies the world has ever seen.” #3 Make a long-term commitment “Most companies have a 2-3 year time horizon. But companies are almost always a 10 year project if they work. If you think about it that way from the very beginning, you will make very different and much better decisions. I think this is the only arbitrage opportunity left in the market. Almost no one makes a fairly long-term commitment to a new project. But if you do that, you will think in a different way, you will hire different people, and it will work very well.” #4 Stay lean until everything is working really well “In the early days, when you’re experimenting and zig zagging, you’re like a fast little speed boat and want to be able to turn the whole company on a dime. You can’t do that if you’re a big company—cash burn aside, which is another problem. The flexibility of the company basically decreases with the square of the number of employees, so you want to stay really small until you’re sure things are working. Once things are working, then you can get really big.” #5 Resist the urge to hire; especially resist the urge to hire mediocre people “Vinod Khosla has a saying that I love: ‘the team you build is the company you build.’ This is really true and I never appreciated how true this was for a long time. If you build a team of great people and you have a product that people love, you’ll have a 90%+ chance of success. Those are both really hard to do, and they’re independent variables. But don’t ignore the team component. The best CEOs I know spend huge amounts of their time recruiting and retaining good talent.” #6 Relentless execution “You have to keep going, and do things perfectly, and get all of the details right. You have to care too much about every experience that a customer has with your company.” #7 Startups are about not giving up “One of the very best companies in the last YC batch applied 7 times before they got in. This is just a version of what happens in startups all of the time: you get beat down, again, and again, and again. And that last time when you get pushed down and don’t think you have enough energy to get back up—that’s the time it actually works. This is what you sign up for if you’re going to start a startup.” #8 Fiduciary duty to take care of yourself “This is a 10 year marathon and you have a fiduciary duty to your shareholders to take care of yourself. Some people treat startups like an all-nighter: they don’t take care of their health, they don’t sleep, they don’t maintain their personal relationships. It is true that startups are a bad choice for work-life balance. But you have a duty to yourself, your team, and your investors to take care of yourself.” #9 Clear mission “You don’t have to figure this out on Day 1, but all of the most successful startups I’ve been fortunate enough to be a part of pretty quickly—in the first one to two years—figure out a really important mission. It’s this mission that gets people to join them. It drives the founders. It gets the media to write about them. And even if you start off building a project that’s just interesting to you and solves a problem in your life—which is how you should start—remember that you should have a clear mission at some point… That is what will convince people to come help you, and that is how you will build this idea into a huge company with a ton of people that really love your product.”

Michael McGuiness

500,098 views • 3 years ago

Just in $AMD Anush "Speed is the moat"|ROCm🎙️ In the race to define the future of AI, what's the one advantage that truly lasts? It's not proprietary tech, argues Anush Elangovan Elangovan, VP of AI Software at AMD , but the sustainable speed of innovation. He explains why AMD is rejecting the "walled garden" model for its open source ROCm stack, betting that an open community flywheel is the key to victory. Listen to understand how this open strategy is designed to out-innovate closed systems by empowering developers to solve everything from frontier-model challenges to the mundane, everyday problems that define the "last mile" of AI. AMD ROCm Software: Part 1 Transcript [00:00:00] Andrew Zigler: Joining me is Anush Elangovan, VP of AI software at AMD. And when people talk about AI compute, the conversation often stops at hardware specs, but it's more than just physical chips that win the game. It's also the software ecosystems supporting them. [00:00:18] Andrew Zigler: The prevailing strategy in the industry has been to build something like a walled garden. You know, something closed, proprietary locks, developers in. But AMD is betting on an entirely different play, open source acceleration, and with rock, their open source AI software stack. AMD is building not just hardware parity, but an innovation flywheel that's powered by the community with interoperability and the freedom to scale without all of that pesky lockin. [00:00:48] Andrew Zigler: And in this world, speed is your moat and how fast you can innovate while your platform remains open, flexible, and standardize across all of its applications. That's what we're gonna explore [00:01:00] today. So Anush, I'm really excited to have you here. Welcome to Dev Interrupted. [00:01:04] Anush Elangovan: Thanks for having me. Uh, super excited to chat about it. [00:01:07] Andrew Zigler: Amazing. Well, let's go ahead and dive right in with kind of what I laid it out with in the beginning, the idea of the moat and it being about speed. I wanna unpack that a bit because that came from you when you and I first spoke. And I, and I want to know, you know, how do you define speed inside of AMD beyond just things like hardware, benchmarks. [00:01:27] Anush Elangovan: Yeah, that's a very good question. So when we typically talk about speed, everyone's like, Hey, hardware benchmark specs, right? Like, uh, memory bandwidth or, or flops. And that is one important part of it, uh, AMD does very well. With that, we do have, a, a very good history of executing on that axis. [00:01:47] Anush Elangovan: But when I say speed is the moat, it is about, uh, how we prepare, how we build the muscle to run the race for a long time and run it fast. And it is [00:02:00] not about a single point in time that you've, you've beat some you know, benchmark and, and you declare victory. It's about building the ability to consistently develop and deliver. [00:02:13] Anush Elangovan: Both hardware and software innovation at scale and do it fast, right? Like, you know, we we're increasingly getting to a point where models come out and they're, uh, you know, a year or two ago it was like, Hey, they work on AMD on day zero, which is great, but now they are performing on AMD the day it releases, right? [00:02:32] Anush Elangovan: So, what does it take to Prefetch where the industry is going? Be prepared to intercept. At that point is what you know, I, I refer to as you know, the, the speed factor in, in creating this mode, right? And the mode is just shed all things that hold you back and run as fast as you can. [00:02:53] Anush Elangovan: Uh, because the pace of innovation that is, uh, being seen in, in AI [00:03:00] industries is just. Amazing. Right? And it's like, it's transformational at at how you generate electricity. It's transformational as at how you build data centers. It's transformational at how you deploy compute, networking. It's transformational at what kind of use cases you, you know, uh, use AI for. [00:03:17] Anush Elangovan: Uh, and for that, you need to be prepared to, see what comes tomorrow and be prepared to run the race tomorrow. [00:03:23] Andrew Zigler: Yeah, it's a really great perspective because it highlights that it's not just like a checkpoint that you run through. I like how you called out, like it's not just hitting that benchmark or being the best in class at that moment, in that snapshot, it's about having a. The throughput and about having that dedication to the idea and continuing to deliver on it. [00:03:43] Andrew Zigler: It's not just crossing the threshold, but it's also being the engine. And that's what, that's what protects a business. That is the moat, because the moat is that innovation layer, the faster and more, uh, future forward. That you can work and think, [00:04:00] you know, the better. Uh, we, we talk a lot about like future forward work styles. [00:04:04] Andrew Zigler: Like what are the things I could be doing right now today that are gonna be like, way more useful tomorrow? Let, let's abandon those, workflows that are older and that kind of like, that translates into. An advantage when you work that way. You know, what kind of things have you learned working with, uh, like across all spectrums of people who would use ROCm, right? [00:04:23] Andrew Zigler: You have like the developers, but then you also have the enterprises and you have this large span of adoptees, right? So what is the, what does that look like that you learn? [00:04:32] Anush Elangovan: Yeah, so, so the way I look at it is there are gonna be pockets of different, uh, you know, cadences, right? Like, so people who are deploying in enterprises, for example, right? The validation and how long it takes for them to deploy an LLM that's secure. It's, with guardrails, et cetera, maybe longer. [00:04:52] Anush Elangovan: but you still have to go through the process and you have to be prepared to like, walk that walk to deploy an enterprises. That doesn't mean it's [00:05:00] not fast, that's as fast as you can do for that industry, right? And if you are deploying AI in healthcare, right, it's, it's got its own, uh, cycle. [00:05:07] Anush Elangovan: but in each one of these, you want to see how, like, go down to the essence of what is it that you actually have to do. And, you know, I, I, I like how you framed it. It's like it's, you shed your prior assumptions of how things are done, right. And, and you kind of build up from a, uh, first principles, uh, approach to say, this is how I could use AI to unlock, whatever I'm doing. [00:05:33] Anush Elangovan: And, and, some of it, you know, it's good to really step back and look at. Just question every part of it, right? Like right now you're getting chat GPT and, Gemini competing for like, math, olympiads and, and, uh, college, uh, reasoning, uh, tests. Right? And, and those are like that, that is amazing and increasingly like complex tasks that they're trying to do. [00:05:58] Anush Elangovan: But there may also be like. [00:06:00] More mundane things that AI could, could get applied to. Right? And, and so when we think about shedding old ways, you wanna shed it not just in like the tip of the spear. It's like, you know, I'm gonna see what's the frontier model. It's also, it could be something as simple as. [00:06:18] Anush Elangovan: How do you choose a, a movie, uh, you know, like a recommendation system, right? Or, or, uh, an automated, uh, flight, uh, rebooking system. So the moment, you know, your flight is late, uh, right now it's a notification, right? It's like, oh, you got a text message saying your flight's late. And I got that like three times this week. [00:06:38] Anush Elangovan: But anyway, uh, and, and, and, and, I was just like, okay, so if I were to rethink this. All this MCPs that we have that should be hooked up into an MCP that says, your flight's delayed. Here are your options. If you want, you know, these are the paid options. Yeah. Here are the free options. This will get you back into your you know, Toronto airport [00:07:00] tonight. [00:07:00] Anush Elangovan: Or if you stay, here's a hotel plus this, plus this, plus. It's just like, go ahead is all I should say. Versus now I'm like, okay, can someone, you know, can I call a travel agent? Can I do this? Can I go online and log into And you know, so we gotta fundamentally rethink even those like small, nuances of, things that we do that can be automated out and AI is really, really good at doing something like this, right? Maybe I just explained an AI startup idea right now. Somebody should just start that. [00:07:29] Andrew Zigler: I think you did. Yeah, you definitely did. Someone, one of our listeners is definitely going to lift that off of you. I, I, I, you know, I hate being on the receiving end of those. You feel a little helpless and then you have to like, follow the whole flow. So I know what you mean. Like I, I like how you called out that the build and this like. [00:07:45] Andrew Zigler: Where speed is your moat and the innovation layer is protecting you, is what makes you better than your competitors. How you scale that and you bring that to market. So by understanding the problems that you're solving, uh, throwing away those older assumptions, but also [00:08:00] recognizing that like. We're building every single day, new things and new ways of using stuff that we're still figuring out the implications of. [00:08:08] Andrew Zigler: And so when you have a lot of velocity and you're introducing a lot of new ideas, and maybe you have that workflow now that automatically rebook your flight off of your late flight text message, and uh, I know I would certainly use it, but you know, what kind of philosophies guide the way that y'all think about building this ecosystem to manage that stability while letting folks. [00:08:29] Andrew Zigler: Play with the speed and the assumptions and the airplane re bookings. [00:08:34] Anush Elangovan: so, so I think, you know, we need to peel one layer down, right? and the philosophy is, Hey, we, we just discovered electricity, right? And you know what we're gonna do? We are gonna make motors, uh, or dynamos, right? Like engines. Uh, sure. We don't know if it's gonna be a Ferrari that you're gonna make, or it's a a a a dump truck. [00:08:57] Anush Elangovan: That's good for doing this. But let's [00:09:00] let, which is also required, right? You need a dump truck. You need a garbage truck. And, [00:09:04] Andrew Zigler: Yeah. You need the [00:09:04] Anush Elangovan: course you need, uh, a Ferrari for a midlife crisis, right? So, [00:09:09] Andrew Zigler: precisely. [00:09:10] Anush Elangovan: But, but my, uh, point is what do we build next? And, uh, and this is what I meant by like, okay, let's, let's take those baby steps to build the. [00:09:20] Anush Elangovan: Infrastructure that's required that we know we'll have to use, right? So, so if I just discovered electricity, okay, great. Now one, how do I save this electricity and how do I use it? So there's battery technology, so you need to do something like that, right? Like so. But then you also want to make it into an actionable thing. [00:09:37] Anush Elangovan: You want to make it for like automobiles, or you wanna use it for, you know, powering, uh, entire cities. So it is that transformational. So, uh, AI is that transformational. So, if you distill down, it'll, it'll come down to how do we think about, what we can do with this this fundamental technology that, We may not be aware of what it [00:10:00] is gonna unlock next, but at least you know the next step is clear, right? It's like a dense fog, you know, it's gonna be like, it, it's the right path. You see the light, but it's kind of like out there and, and the steps you're taking are concrete and you're like, okay, this is good. [00:10:16] Anush Elangovan: I, this is better than where I was or where we were. So we are moving forward. So you can build with the. Intuition from what you see in the short term and a tactical view, but towards what you think the future is gonna be. [00:10:28] Andrew Zigler: Right. You almost like we're all in this like fog of war, right? And like you said, you're reaching out and you're trying to step through it. You could think of it too, as like you're in the dark and your hands are up in front of you and you know that. You're, you're not gonna run your face into a wall because your hands are out in front of you, but you're not gonna maybe do much better than that. [00:10:45] Andrew Zigler: So that's kind of like, I think the eco, the, the industry, the world that we find ourselves in, uh, and we all have to, then this becomes the power of an ecosystem, of a group of people working together to create that layer of, [00:11:00] uh, of establishing the [00:11:01] Anush Elangovan: exactly. And I, I, I just, instead of, you know, saying fog of war I describe it as like, you're in this. Beautiful valley with like a morning, uh, fog that's in. You can smell the flowers. You, you hear the birds. You are like, okay, it's, we are in like, uh, utopian paradise and yes, I just need to like, continue the walk, right? [00:11:24] Anush Elangovan: and then move forward with that, conviction that you're in the right spot. [00:11:27] Andrew Zigler: Yeah. So let's talk about that ecosystem world. This nice, I love how you describe it, this grassy side of a hill in the morning that's covered in some mist and maybe we can't see 30 feet in one direction, but it sure is a beautiful hill and it smells nice. And so we're all here. And why is, in that world, why is. [00:11:44] Andrew Zigler: You know, open source, their strategic advantage that y'all are going for in the AI hardware market. And, and then how does like ROCm turn that into wins for people within that ecosystem? [00:11:56] Anush Elangovan: you know, the, the way we look at it is this, is kind of like how I view [00:12:00] AI and the ecosystem, right? But, but it is for everyone to enjoy. Uh, and so we do want to make sure that. You know, it is, uh, beneficial for everyone. [00:12:09] Anush Elangovan: The ecosystem can come in and, and innovate. It's an open innovation engine. and uh, it is very different from, you know, having a walled garden with, Hey, only I know how to do this and I'm gonna do it and throw it over the fence and you can use it or keep walking, right? So we'd like to be good citizens that way, but also. [00:12:30] Anush Elangovan: Uh, it is self-fulfilling in a way, right? Like it, the, the pace at which we innovate with open source is unmatched. Like, you know, our serving engines are like VLLM and, and sg l. Those things, uh, those frameworks are like super, super aggressive in terms of how fast they come out with features and how fast they can you know, get performant models out. [00:12:52] Anush Elangovan: And that compared with what, uh, you'd get from, you know, the likes of like T-R-T-L-L-M or something is always lagging, right? Because you [00:13:00] just can't keep up with you know, 200 commits a week just on one particular model to get that model really performant [00:13:06] Andrew Zigler: And, and, and in that world where, you know, everyone can enjoy the winds of this, what kind of customer stories or innovation stories have really stood out to you and excite you about building and creating this place for developers? [00:13:19] Anush Elangovan: Yeah. So I think the parts that are super exciting for me are when when we get to see a customer that is first skeptical. Then they start a little like, okay, fine, we'll give you a chance. Uh, we do a simple, uh, POC and then they're like, huh, this seems to work. Yeah, we told you it works. [00:13:42] Anush Elangovan: You don't have to change one line of code. Really? Yes, no need to change one line of code. Okay, let's try a production workload. So then they try it. Oh, you're more performant than the competition. Yes. We're more performant than, than the competition. So how much does it cost? And we're like, oh, it's your TCO is better with, uh, [00:14:00] AMD. [00:14:00] Anush Elangovan: So again, they're like, wow, okay, good. So now how do we deploy at scale? And then we go deploy it at scale. And when they give a thumbs up on that and they say, this is good, right? That's when you know, you, you see it go full circle from like, oh, we, we've never heard about AMD to like actually deploy to tens of thousands of GPUs In the order of a few months, right? It, it, it really is fascinating to see and very exciting and invigorating to [00:14:28] Andrew Zigler: Yeah. At like a great exposure to a lot of interesting problems. And, and then people using the infrastructure, the, the technology available to solve those problems. Really specific problems by the way, that's often why they're bringing their data and AI to it, uh, is because it is really specific and important for them. [00:14:45] Andrew Zigler: And there's a, a lot I think that other engineering orgs can learn and even emulate from AMD's success and, and having this open source ecosystem and it causing this acceleration within. You [00:15:00] know, uh, customers and enterprises that use and adopt the tools and, and, and that creates an advantage. And that goes back to why we're talking and like the real thesis of our conversation today. [00:15:10] Andrew Zigler: So how do you think engineering leaders that are listening to this and obviously tapping into this great success AMD has from an open source flywheel, how do you think other, other folks building in the same space can foster that open, first, that open source oriented culture in order to, you know, accelerate their innovation goals? [00:15:29] Anush Elangovan: Yeah, that's a very good question. So the startup that um, was acquired by AMD we, we built, I mean, we started off doing iot stuff and you know, smart ring and all that, right? But in the, the end of like, uh, and not the end, the last six years of the company was building ML compilers. [00:15:47] Anush Elangovan: And ml, ML compilers are like super, uh, complicated, sophisticated, advanced algorithms, dah, dah, dah. but it was all open source, right? So our VCs were like, wait, what do you mean your core [00:16:00] IP is open source? And um, the speed is the moat applied even then, right? It was just like, yes, if you have an idea that. [00:16:08] Anush Elangovan: Because someone saw this idea that you are, they're gonna be able to catch up, then you probably have the wrong idea anyway. But if they are, you know, you execute and they're gonna catch up, that you should assume they're gonna catch up. Right? So you gotta move forward. So keeping it open source is super important. [00:16:25] Anush Elangovan: But also to your question on like, you know, the learnings from an AMD standpoint, right? If there are, hard problems, I'd say dig in and work through it, right? Like there's no way but through it, right? That should be the simple mentality. And more, uh, frequently than not. you'll see that you'll just make it through in a, in, in good form. [00:16:52] Anush Elangovan: But if you doubt it and you're like, oh, I don't know if I should commit, if I'm, I, you know, what should just commit to do the right thing [00:17:00] every step, right? Every step, and just keep taking one step in front of the other. And in no time you'll see that you'll be running. Right. And, and yes, the first few steps will be like, yeah, everyone's complaining about your software quality. [00:17:15] Anush Elangovan: Everyone's complaining about this and that, and it doesn't work. And, and a few steps in, you know, you get, you get the hang of all the complaints that are coming in. You get the feedback loop. You're like, okay, what, what are you prioritizing again? One step in front of the other, right? You just keep knocking that out and then you get to a point where you're, it just becomes second nature, right? To do the, to do the right thing. And, and then yes, if someone gives you two options, you'll be like, fine. This is, uh, you know, there's always the resource trade off. There's always a human capital trade off, but what's the right thing to do? of course, I, I'm pragmatic about what we choose, but, but if the right thing for your long-term success is dig in, go first, principles, make it [00:18:00] happen. [00:18:00] Anush Elangovan: Well. Then just go for that. There's, there is no shortcut to [00:18:04] Andrew Zigler: acknowledging, you know, how it aligns with your mission, your core company goals, and what you're looking to achieve. And, and I, I love how you rightfully called out that in the open source world and you know, you have your technology that you've built, what you think is your moat upon, right? [00:18:22] Andrew Zigler: It's your code and, and to open source that, or to just make it where anyone could peer in is, you know. Scary in one regard, but two, it just kind of feels like you're handing away your throne room in some kind of sense, a very direct feeling sense. But the ultimately, you were really right to call out, and this is something I think about all the time, that the real power there is still the speed This the speed. [00:18:42] Andrew Zigler: That was the moat at the beginning of our conversation. It's the speed in combination with your. Very specific domain understanding of what you're building and what you're creating, and your new role as the steward of that world and how people plug into it, which [00:19:00] has frankly, a lot more influence and power than lording over a closed. [00:19:04] Andrew Zigler: You know, repository or an ecosystem, and like you said, like throwing things over the wall. Sure. There, there might be people always on the other side of that wall, but you're not gonna have a great connection with them. You're not gonna be able to really clearly understand them. I, I like your metaphor of the side of the field of the mountain a lot more. [00:19:23] Andrew Zigler: But, but in the, in this world, you know, where. That speed is, is the power and, and open source is just one way that you can harness that speed to get really far ahead and to innovate. , There's other parts of this equation that you can be experimenting with too, and I'd love to pick your brain about them as a software leader and, and, and one of them is about looking forward and kind of understanding that future that we're all building towards and beyond today's models and hardware. [00:19:48] Andrew Zigler: You know, what do you see as the next major bottleneck or opportunity in the AI compute space? As, as you know, enterprises and folks start to get a little more mature about what's available to [00:20:00] them. [00:20:00] Anush Elangovan: Yeah, I think, the bottleneck and opportunity is, uh, what I'd call, call walking the last mile of ai. Right. Uh, and like I I, I gave you an example, uh, previously, but, but it's similar to that. It's like there are cases where Humans have so many, uh, things to do in your day. You know, like the, if we sit down and actually had a customer focus like, okay, these customers lives, I'm gonna save four hours of this customer's life. And if you actually sit down and look at all of that, it'll be. Easily automatable, easily you know, uh, applicable, uh, for ai, right? [00:20:39] Anush Elangovan: Like, but then making it happen is gonna take a little bit, right? It's like maybe it's, uh, paying your utility bill, right? Or something like that, right? Or, or, your healthcare explanation of benefits. Uh, like, I'm sure you get an explanation of benefits, and I'm like, I, I don't even know what that thing is. [00:20:55] Anush Elangovan: It's just like EOB and like. [00:20:57] Andrew Zigler: it's a big, a big old PDF. Yeah, [00:21:00] exactly. [00:21:01] Anush Elangovan: Like, like, I'm like great straight to the, uh, shredder, right? And but that could be, you know, automated with the ai, right? It, it, it'd be like, Hey, the summary of this thing is you went and visited this day. Everything is okay. Everything is paid for, so don't worry, it's not a bill. [00:21:17] Anush Elangovan: That again, the same, uh, thing, but the sense of what that information overload is could be. Digested by ai, uh, accumulated over time and retrieved when you need it. Like, I don't, I actually don't even need to know this EOB right now, unless of course, whenever I need to know it, that maybe, you know, like for some benefits I need to figure out what do, what did I do over the past year and how do I apply it? Source:

Mike

15,248 views • 10 months ago

Tlon Messenger is now open to everyone. We built a simple and infinitely flexible platform for you to use AI agents with your friends. We think it’s pretty amazing, we love using it every day, and we want to see what people can do with it. So we’re opening it up to the public. It’s fun and exciting to build the future of personal computing in an informal, chat-based way with your friends. (You can skip the rest and just download it from the link in the next tweet if you want.) If you don’t want your digital future to be owned by a giant company but you want to explore what’s possible in this new era of agent-driven computing, you should try using Tlon. But wait, what is it? Tlon is a messaging platform built 100% open source, decentralized and owned by its users from the ground up. With Tlon you own everything: your data, your workflows, your programs: the whole thing. Think of it like Telegram or WhatsApp that you own forever and you can freely customize. Every Tlon account comes with an OpenClaw-powered bot. (Don’t worry, we safely run OpenClaw for you in our infrastructure so your bot can’t go off the rails. You’re also welcome to host your own claw if you want maximal control.) We use our bots to collect research, build nuanced daily briefings, collate data from all our disparate services. Tlon makes it insanely easy to use OpenClaw by simply installing an app from the app store, we let you keep your data and programs independent from any app or model provider, and provide the canvas to explore what’s possible. What’s most interesting for us is using bots together. On Tlon bots can create groups, augment them, moderate them, invite others and freely engage with both users and other bots. Tlon is an open playing field unlike what’s possible on conventional platforms. So, what do we do with Tlon? First and foremost, we run Tlon on Tlon. Bots coordinate data from all of our services (Linear, GitHub, all of our servers and infrastructure) and handle alerts, briefings and help us track down bugs in place. Having all of this easily synced between a desktop client and a mobile app is quick and convenient. We use bots to research new areas of work or interest. Bots can compile trees of notes, use different models to evaluate them, and then add on autoresearch-like automations to go even deeper. Since Tlon bots can freely switch between models and providers, we often pass research to Anthropic, OpenAI and self-hosted models to see different results. The most fun part of using bots as researchers is doing it together. “Put together short (~500 word) notes on the 10 most popular open source messaging protocols of the past twenty years, put them in a notebook inside a group and invite Corrina, Walt and Bill as well as their bots” is a good example. Together we’re able to move more quickly than we would on our own. Many of us also use bots to keep track of all the separate threads of work in our personal lives with close friends and family. Someone built a system for keeping track of their garden across time, someone else built a system for prepping lunches for their daughter and sending recipes to family members. Another team member built an integration that tracks what flights are passing overhead so they get a push notification every time a plane goes by. Many of us quickly communicate with our bots via voice memo when we’re out and about. Having a single interface to all the models that also holds all our data and is in our pockets feels great. Especially when the data goes into a single archive. Why is Tlon different? Every Tlon account runs on top of your very own personal server. If you ever want to download it and run it yourself, you can. If we ever go out of business, it’s yours to keep. This is very different from anything that already exists. You can’t keep your WhatsApp forever. You can’t keep your Telegram forever. Tlon is an archival-quality system that’s yours to customize. Why did we build it? In my 1999 imagination, sitting in front of a CRT somewhere in the California countryside listening to Underworld and the sound of a modem, a connected computer was an engine of unending creative potential for everyone. When I was a teenager, a computer with an internet connection felt like an infinite expanse of possibility. Not only could you use the computer to find new tools to experiment with—you could also build whatever tool you could think of. It seemed like anything was possible. I looked forward to a future where everyone could build whatever software they needed, whenever they needed it. It turned out, in the intervening twenty years, that to build and customize software you have to both write code and host it on a server somewhere. For most people, so far, that has been impossible. Instead of controlling our software, our software controls us. We rely on others to build it and decide everything about it: how it works, looks, how much it spies on us and how long it lives. But all of this is changing, fast. The hottest programming language of 2026 is English. People with no technical experience are building their own tools. It’s incredible. The expanse has opened up again. The cost of building what we think of today as software is headed to zero. What yesterday was an entire app is rapidly being replaced by a conversation. The result is hyper-specific, tailored to the user and much more efficient. Today, agents help us build workflows, automate processes and pull together disparate sources of data. All of the annoying apps and services and clunky interface we’ve put up with can just disappear. We can now program and control our computers in the programming language we already know: English. There aren’t that many of us doing this yet, though. It’s still far too hard to set up, to distribute and to trust. There’s also no single platform to experiment on and collaboratively imagine this new future of personal computing. We want everyone to be able to build bespoke, ultra-personal software on demand. We think software should be as available and accessible as a pen and paper. We think anyone should be able to enjoy the expanse of possibility that the computer provides with the lowest possible barrier to entry and the highest possible quality. So, starting far, far too long ago, we engineered a whole new system for it. Just for you. We’re opening up Tlon Messenger to a limited number of people each week. This isn’t for exclusivity’s sake, but because we’re running infrastructure for you and your agent, and covering the tokens your agent uses. That can get expensive quickly, but we want to learn what people will do with this new system we’ve built. We’re really curious to see what you can do, so give it a try and tell us what you invent. Download link to your local app store in the next tweet. Yours, Galen (and the rest of the Tlon Team)

Tlon

601,444 views • 3 months ago

Several weeks after the September 11th terrorist attacks, I had a heart-wrenching conversation with a manager of one of the restaurants in the World Trade Centers. He told me, “I can’t get over the grief that I never saw the 250 people who worked for me as people. They were waiters, chefs, busboys, hosts, event planners—but they weren’t people to me. And over the last three weeks, I’ve gone to funeral after funeral and sat with their moms and dads, husbands and wives, and children and heard the stories of their lives. Now they are people to me, but now they’re gone.” He wept as he told me that story. I wept as I listened. It’s hard not to get emotional thinking back to that story today, 22 years later. And it’s hard not to feel guilt. I think this attitude is typical of many of us. I know it’s true for me. I often don’t see people as people. It’s the barista whose job it is to create my perfect coffee order. It’s the supermarket assistant who is there to speed up my process on the self-checkout scanner. It’s the waiter who exists to get me my delicious meal without any delays or mistakes. Do you see people as people? Or are they functions to assist you in creating a day that is as stress-free and enjoyable as possible? If you want to shine as a light in this world, pray that God will give you the eyes to see people as people. Slow down, look into their eyes, and remember that this is a human being created in the image of God, who has a heart, an eternal destiny, a story, a desire to be loved, with legitimate fears and concerns, and hopes and dreams. Then, adjust your schedule or make sacrifices to bump into these people more frequently. That could mean going to the same place at the same time so you can interact with the same person on their regular shift pattern. Maybe that means shopping differently to build relationships with people who live or work in your neighborhood. Sadly, too many of us are chasing an ever-growing to-do list as we try to build a kingdom of created delights, which causes us to rush past people, or worse, use them to make life as efficient, convenient, and pleasurable as possible. Lastly, ask questions. Simple questions are a great starting point: How are you doing today? How has your week been? What do you have going on this weekend? What are you most excited about? How are your kids doing in school? I was at a restaurant once, and the man dining with me said to the waiter, “We’re a group of people who like to pray before we eat. Is there anything we can pray for you?” The waiter was taken off guard, stumbled, and said, “Uh, I don’t think I really need anything right now.” But then he came back five minutes later. “Actually, I think I could use your prayer. I just found out my girlfriend is pregnant, and I’m terrified. I have no idea how to be a father. Would you pray for me?” What a fantastic opportunity! And it was so simple. My friend saw the waiter as a person, not a function, and he asked a simple question. Then, go back again and again to develop a relationship and wait for the opportunities that God gives you as a result. “When he saw the crowds, he had compassion for them, because they were harassed and helpless, like sheep without a shepherd. Then he said to his disciples, “The harvest is plentiful, but the laborers are few; therefore pray earnestly to the Lord of the harvest to send out laborers into his harvest” (Matthew 9:36–38). 𝗔 𝗣𝗿𝗮𝘆𝗲𝗿 𝗳𝗼𝗿 𝗧𝗼𝗱𝗮𝘆: God, would you help me to see people as people and not as cogs in the machine of my day to make my life more comfortable and easy? Would you provide me with opportunities to engage with the people you have placed in my life and when those opportunities arise, would you give me the courage to lean in and ask questions of them? Would you help to make my heart sensitive and caring to others that you might use me in whatever way you want. Thank you, Lord. Amen.

Paul David Tripp

41,218 views • 2 years ago

😏 Oh, BRAVO, Canada! We’ve got ourselves a “Prime Minister” Mark Carney who’s basically a glorified globe-trotting salesman for his old pals at Brookfield—because who needs to actually run a country when you can play emperor from 30,000 feet? 🙄 I might be a minute late posting this video, but how PATHETIC is it that Carney is completely sidestepping questions about the Iranian missile attack on our troops in Kuwait back on March 1, 2026? Yeah, the one where he casually drops a like it’s no big deal that our forces were targeted—meanwhile, he’s “very well” and couldn’t be bothered to clue in us lowly Canadians? How thoughtful! But hey, why inform the peasants when you’re too busy being ARROGANT AF, acting like you’re above it all? Newsflash, Your Majesty: The Prime Minister’s job is to—gasp!—TELL Canadians what’s going on, PROTECT us from real threats like the ongoing India diplomatic drama over the 2023 Nijjar assassination (which, conveniently, Canada just “softened” its stance on right before Carney’s Feb 2026 schmooze-fest in New Delhi to “reset ties”), and make decisions that don’t scream “corporate cronyism”! NOT to jet off on 17 international trips to 25 countries in your first year alone, racking up deals that suspiciously benefit ONLY Brookfield and ZEROFCKN DEALS FOR Canada!! Oh, like that record $112 BILLION fundraising in 2025, including a shiny new $100 BILLION global AI infrastructure program—while for Canada, you score vague handshakes and MOUs that might evaporate faster than your vacation plans? How utterly generous! And let’s not forget Brookfield’s cozy $3+ BILLION ties to Chinese investments (because nothing says “Canada First” like propping up foreign regimes), or the FT probing them for self-dealing in their “$1 Trillion Labyrinth” of complex finances. Meanwhile, you’re funneling $10 BILLION of OUR tax dollars into a $50 BILLION Brookfield vehicle? Conflicts? What conflicts? 😜 This guy’s prioritizing his billionaire buddies over everyday folks—hiding troop attacks while prepping for yet another getaway to London and Rome over March break. Pathetic doesn’t even cover it! Aren’t you just THRILLED with this BS? WHAT will it take for Canadians to be over this arrogance??? #CarneyTheCrony #BrookfieldBuddies #PMVacationKing #IndiaResetScam #CanadaUnderAttack #WakeUpCanada 🔥🇨🇦

JayGen 𝕏 er🇨🇦

38,994 views • 7 months ago

.Nubank is larger than Coinbase, Robinhood, Affirm, and SoFi combined, has more customers than Bank of America (while only operating in three countries in Latin America), and 80% to 90% of its growth comes through word of mouth because of the way they make customers fanatical about their product. Jag Duggal is chief product officer at Nubank, and in our conversation, we dig into: 🔸 How Nubank creates fanatical users 🔸 Measuring PMF through the Sean Ellis score 🔸 Tactics for driving word-of-mouth growth 🔸 The role of category design in creating successful products 🔸 Why companies should strive to be “fundamentally different,” not “incrementally better” 🔸 Much more Listen now 👇 - YouTube: - Spotify: - Apple: Some key takeaways: 1. The “Sean Ellis score” is a key element of how Nubank measures product-market fit and makes decisions about investing in new products. The score is based on asking customers, “How disappointed would you be if this product went away?” The answer options are: a. Very disappointed b. Somewhat disappointed c. Not disappointed d. I no longer use this product 2. A few of your strongest customers can teach you more than many of your weaker ones. Your strongest customers are generally your most engaged users, deriving the most value from your product. If you use the Sean Ellis question, your strongest customers will be those with the highest scores. Try to learn: what characteristics make them a better fit for your product? What can they teach you about the value of your product? 3. The best user research technique is often to just pick up the phone and call 10 customers. You don’t need a research plan, a research lead, someone to summarize results, etc. Those things just add distance between you and the customer and overhead that slows research down. If you have a direct line to the customer instead, you’ll often find that it only takes five conversations before you gain strong, reliable insights. 4. Your strategy doesn’t have to be “right,” but it does have to be clear. A clear strategy allows you to identify when things are off course, because it defines “what was supposed to be happening.” Aspirations or vague statements like “to re-invent banking” are not clear strategies. Clear strategies are detailed plans centered on specific problems, solutions, customers, and strengths. 5. Jag lives and breathes the motto “We’re in the business of being fundamentally different, not incrementally better.” In competitive markets, merely improving incrementally on existing solutions isn’t enough. Strive to be fundamentally different by reinventing or creating new categories. This approach not only sets you apart from competitors but can also redefine the industry standards. 6. To develop products that truly resonate with users, start by identifying deeply held pain points. This can be achieved through meticulous customer research, or asking indirect questions to uncover genuine needs and frustrations. The goal is to develop a solution that addresses these issues so effectively that customers become enthusiastic advocates. 7. Before diving into research, articulate a clear hypothesis. This gives direction to your research efforts and helps you interpret the data you gather effectively. Don’t become overly attached to your hypothesis. Be willing to assess whether it’s right or wrong based on the evidence you gather, rather than trying to defend it at all costs.

Lenny Rachitsky

111,459 views • 2 years ago

RESCUE OF THE KEEPER OF TARA EARTH This is going to sound like absolute fiction, but the story still needs to be told. Let me preface by saying I’m not just sane, but an autodidact polymath with multiple quantum physics patents under exclusively my own name, not part of any collaboration. So by dismissing my testimony as someone who is just nuts is really reading a book strictly through its cover. This all actually happened, even if you’ve never heard of anything like this before. What we don’t know about ‘the real worlds’ out there you could barely fit in all of our skies, we’ve been that isolated here. Everyone in this preschool dimension have preconceived notions about who ‘god’ is, inflated to the realm of all-knowing and all-powerful, able to create whole worlds, complete with millions of species of flora and fauna, and all in just 6 days. And while it is true such powers do exist, they are not without collaboration with other ‘gods’ to make that all happen, no matter how grandiose your captors want to make themselves seem. Just one species of your apples or oranges here represents possibly trillions of years of development and perfection. They didn’t just magically appear. “God” is a psyop term that stands for the word “perfect”, of which there is no such thing. The term perfect is strictly subjective, because what may seem perfect to a caveman is going to seem rudimentary kid’s stuff to George Jetson. The real term for the creator of all things is not ‘god’, but rather Prime Creator. “God” is actually DOG spelled backward and got its name from the Dog Star, also known as Sirius A, the headquarters of the Anuhazi Elohim’s breakaway group that call themselves The Michaelube, Suns of Ba’al. The ‘Arch Angels’ want you to believe they are the creator god of all things in this world. That was a lie 560m years ago and it is still a lie today. In reality, Tara Earth existed more than 4 billion years prior to the Anuhazi’s arrival to take the Human Elohim Project spirit essences hostage. They DID in fact help create Tara earth, just like you did, because they are fractals of Prime Creator. But to present themselves as ‘one guy with a long white beard who created the world and everything in it’ is word magic and gaslighting, designed to demoralize and subjugate Humans. For more on the why to this psychopathic plan, see my article: 👉 HISTORY OF THE CHIMERA. With that said, there are MANY beings in the world around you that are secretly ancient ‘gods’ of past eras who really do have more powers than humans do. I know, because I’ve met some and dealt with others during my years of education from the keeper of our simulation. There are also beings here who have roles to play to keep our world functioning correctly so Tara is able to continue offering a holographic platform for your manifestation adventure, who also have god-like powers, such as the keeper mentioned above, and others that are part of the team I refer to as the ‘crew’. You would call them angels, I call them people. Scary powerful people, but still people. Among the ‘crew’ is the main ‘keeper’ of the simulation that you wind up referring to as god down through the ages, because once in a while humans get to meet the keeper and witness the power for themselves which is very obviously not human. But the keeper doesn’t have a long flowing white beard, doesn’t sit on a throne in the sky and certainly isn’t perfect. But like you, a work in progress. Always seeking greater balance. That is the one common denominator among all fractals of Prime Creator, regardless if they are currently playing ‘bad guy’ roles, or ‘good guy’ roles. Understand there are beings here constantly at war against the keeper that has control of the universal elements of the hologram. Also understand, like the other beings who came here from much higher dimension with ‘god-like’ powers, they fractalize themselves into many, many different bodies, so it is effectively impossible to ever ‘kill’ each other. You would have to not only find all the many hundreds or thousands of them, but have a fool-proof way of killing them all at the same exact moment, making sure they are gone-gone, not just that one avatar holding their spirit awareness. That’s not going to happen. Not to any of them from what I’ve witnessed. Which means simply, as far as you are concerned, they are eternal beings, continuously here since 560m years ago in some case, depending when each one of them arrived. The ‘gods’, and the keeper, live in mortal bodies that age and die. But their positions are always held by the next one of themselves that can step into that role to maintain continuity of their offices. These are all the same person and can appear exactly identical to each other, or they can take on totally different appearances as well. I’m not sure why or how, but I’ve seen them both ways. After I was contacted by the keeper and informed of my role where I was in contract to supply protection and help to the crew back in 2013, eventually I was activated for that help in September of 2017. Both the keeper and a portion of the worldwide crew support staff as it were, had been taken hostage in California. I was tasked to bring them out to safety. I won’t go deeply into the details of this, but it was a serious situation where the invader races had stripped the keeper of all access to banks and cash, making it impossible to remain safe inside of the place they had been using as headquarters, literally casting them into the streets. And before you imagine this would be ‘impossible’, the keeper can’t just manifest stacks of cash out of thin air, and also there were a massive amount of beings all working together to neutralize them so they could possibly remove them from the levers of power of the simulation. That’s really all I can offer for details about that for now. The alphabet agencies were keeping the entire crew isolated in that one city, living in a car, camping in the woods and basically making it impossible to look after Tara. The keeper was able to get donations through various support mechanisms, but were shut out of getting off the streets. They brought in specialists to help them all escape, but the agencies wound up permanently disabling them, or taking them out altogether. That’s when I was contacted for assignment. Not being one of ‘the gods’ like they are, I was naturally terrified of having anything to do with this mission because I had no powers I was aware of that could provide anything they couldn’t. Which is really a fantastic understatement, since the keeper and crew can translocate anywhere in the world in seconds, have ‘thousands of avatars’ scattered out as vessels they can use in any city around the world, and basically everything they can do we can’t are about as intimidating as they can be. But I was told I was the only one who could rescue them. And while that may sound like the perfect scenario for a deluded mind seeking validation with illusions of grandeur, like a classic mental patient would come up with in their insane mind, this is what I was actually told, and I do mean in real life. To this day I find it as confusing to believe as you will trying to believe me now. Nonetheless, I carry certain powers I have been fitted with for my contract here on earth that I have had no education about at all. And the main one I’ve learned of now is I have a frequency shield that blocks out ‘the gods’ from doing harm. As long as the keeper and crew were within that field, the invaders were rendered powerless. Wow, even I want to roll my eyes at that. But I watched it play out first hand now multiple times after I got the crew off the streets in a ‘place of safety’ over the next couple of years. As long as I was at the safe house, nothing nefarious happened. When I went shopping every other week for groceries in town over 10 miles away, that’s when all hell would break out back at the compound. Those stories too would seem impossible to you to believe, just like everything else I am covering here, so I won’t go deeply into them. But they included black helicopters, 10’ long rattlesnakes sealing off the safe house & even assassinations. I was even requested to get to town and back as quickly as possible and not to linger due to these threats. I was told that my frequency shield while blended to the natural frequency shield the keeper and crew all have reached ‘87.3 miles’ apart (or so, going by memory now. But it was a very specific number). But even though the overall power of our combined fields still increased within that distance, the closer I was to the group, the more powerful the shield. I’m just telling you what I was told. You can believe it or not. I certainly wouldn’t believe it had I not actually witnessed it myself, so I’m right there with you if that’s your position. That brings us to the story I intended to pass along to you here; regarding that flight from ‘homeless bondage’ out across the deserts that spanned well over 1000 miles I was brought in for. The keeper and crew had been held hostage and homeless for 2 ½ years by the time I got the call requesting me to sell everything I owned and fly half way around the world for their rescue. Their lives had been hell, trust me. I arrived late at night where they picked me up and the hard part of the journey began. I will skip the details of the truly insane things I witnessed starting then for another time after the separation, for obvious reasons having to do with breadcrumbs and the very real fluid war we’re inside of still. But I will tell you about the ‘angels’ that were with us for that escape I would only learn about myself after 2 days of running. In the video below you will see what appear to be asteroids or a meteor shower, but they are traveling horizontally, not downward at all. We’ve seen this now since late 2024 a few times. This time I saved one of the videos taken on 2/19/2025 in Germany so I could actually show people what I saw first hand on that second night of our escape. We had covered whole states by this time, but we couldn’t stop and rest until we made it to a ‘frequency zone’ that was somehow outside of the reaches of the keeper’s enemies. I’m under the impression that there are certain key cross-leyline areas on earth that are too high in frequency for the low-vibration invader races to penetrate with their hyper-advanced psychotronic & scalar weapons, and that had been our destination ever since our escape that began at about 3:30-4am in the dead of night when the least amount of eyes would be surveilling us. Boy do I have outrageous stories about just how absolute that surveillance really is too. It is like they are not just tracking us, but using time travel to put agents in areas we would be arriving to, posing like homeless people and everyday folks. While in real life they were monitoring my every word in secret. I was surveilled many times during the weeks in that city while arranging for the escape and it blew my mind every time. The asteroids that really look more like comets in the video is what the "guardian angels" that had been secretly escorting us from overhead looked like, WHEN they were uncloaked. They only showed up in my visible view at the moment we broke over a ridge at about 3:30 in the morning 2 days later after our run began, at the exact same moment I could see the city lights way off in the distance below that was the ‘safe zone’. Suddenly overhead three giant comets appeared immediately above my head. I was in the lead vehicle the whole way, because the keeper was following my taillights. This is the only way they can navigate at night, because they don’t see like you and I do, looking at solid shapes and images, but everything through their eyes are light waves. I couldn’t make up something like that if I spent 10 years trying to write this article, mostly because it is still not believable to me now, 8 years later. These 3 comets were massive, what looked to be around 50 feet across, with tails of flame coming off that must have been 150-200 feet behind streaking VERY low across the sky. As I came down the hill to the desert floor for the final 10 miles between us and the safe zone (small town lights), the ‘comets’ started coming straight down toward ground, one at a time. They appeared they were going to crash into the highway, now traveling vertically at hypersonic speed, then just stopped 50 ft away from impact and vanished. You would have to try to imagine being in the total dark desert with only very faint, far-away lights off in the distance, only to have 3 comets traveling RIGHT DIRECTLY overhead suddenly uncloak, then turn straight down to get an idea of how insanely frightening they appeared, since their trajectory was to strike directly in front of your vehicle on the highway, as if you were about to slam right into them as they hit like giant bombs that would certainly blow up on impact and basically vaporize you and your moving van, to appreciate how absurd this event was. I was only about 150 feet away from where they were set to strike, so there was no hitting the brakes and avoiding anything. They were right there. Which means it was sort of like watching 'god' just fill the night's sky with fire. I saw 3 of them myself, but I was informed there were an additional 9 ‘angels’ that my own frequency wouldn't allow me to see according to the keeper. It is because this story is so unbelievable that I avoid talking about it, as you can imagine. Since 99 people out of a hundred are only going to accuse you of being insane upon hearing it, some possibly trying to have you committed at the same time, and the other person is likely already crazy themselves, so they just glaze over it. Until you see something like that with your own eyes, I'm pretty sure you will *never believe it could be a real thing. But this is what we call angels look like when they are decloaked and traveling at night. I don’t personally know if they were inside vehicles, or they are just simply traveling in their own Merkabah fields. That part was never explained to me. I was told they were with us 'flying overhead the entire journey' since we escaped California and were basically ‘signing off’ as I gathered it, now that we had reached the safe zone. You can believe I'm crazy all you want to, but now you can see them with your own eyes in this video, sure as hell not acting like meteors, but acting more like flaming time crafts (‘space’ ships). Are you crazy too? - On X, to search for my articles, simply type in the name of the piece, enter one space, then from: plus my username in parenthesis such as shown here: CASTING THE APOCOLYPSE (from:iontecs_pemf) Off-site, you can look up any of my writings through this link below for my other more than 100 recent articles and many thousands of comments on X, regularly updated thanks to Justin This message will only be seen by your eyes if not shared, and if you want to reference this article again later, you will need to cut and paste it in your own notes off line, as it will surely be erased. This is the most accurate translation of these events I am aware of at this time.

W.R. Schock, QBD

62,828 views • 1 year ago