Sensitive content

This media may contain sensitive content.

Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Ipde deep oombala poda vanga pasangala. Video code 12 available on Telegram id: #shemale #madurai #chennai #bangalore #hydrabad

Anamika (40k)

36,025 subscribers

124,334 görüntüleme • 6 ay önce •via X (Twitter)

NSFW #shemale #madurai #chennai #bangalore #hydrabad

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Introducing Unsloth Desktop 🦥 The first desktop app to run and train models locally. • Open-source. Runs on Mac, Windows and Linux • Supports MLX, diffusion image/video, audio, GGUF • Connect Claude Code and Codex to local LLMs • 50% more accurate, self-healing tool calls + sandboxed code exec • Works for CPU + multiGPU setups - NVIDIA, AMD, Intel, Mac • Train models 2× faster with 70% less VRAM • Private web search, deep research, RAG, MCP and exports (NVFP4, GGUF) • Use Unsloth’s OpenAI-compatible API and cloud models • Securely deploy LLMs remotely and access anywhere Unsloth Desktop is now available on and GitHub. GitHub: Blog and Guide:

Introducing Unsloth Desktop 🦥 The first desktop app to run and train models locally. • Open-source. Runs on Mac, Windows and Linux • Supports MLX, diffusion image/video, audio, GGUF • Connect Claude Code and Codex to local LLMs • 50% more accurate, self-healing tool calls + sandboxed code exec • Works for CPU + multiGPU setups - NVIDIA, AMD, Intel, Mac • Train models 2× faster with 70% less VRAM • Private web search, deep research, RAG, MCP and exports (NVFP4, GGUF) • Use Unsloth’s OpenAI-compatible API and cloud models • Securely deploy LLMs remotely and access anywhere Unsloth Desktop is now available on and GitHub. GitHub: Blog and Guide:

Unsloth AI

796,892 görüntüleme • 19 gün önce

🚀 SANA-Video 2.0 is here! A full-stack optimized video model designed for efficiency — while still delivering high quality. We combine a hybrid architecture closely related to the recent Kimi K3 design, adopt Self-Flow from FLUX 3, and further accelerate it with our own Sol-Engine. Key technical ingredients: 🧠 Hybrid Linear–Softmax Attention 3 gated linear layers + 1 gated-softmax anchor (75% linear / 25% softmax) 🧱 Block Attention Residuals (AttnRes) Boosts deep-layer effective rank by ~12% 🏗️ Unified 5B & 14B models Trained from scratch under very limited resources: • 5B → only 16 nodes of H100 • 14B → 48 nodes of B200 Results 📊 • 84.30 VBench Total • 3.2× faster DiT forward than matched full-softmax at 720p/60s • 720p/5s in 13.06s on a single H100 with Sol-Engine • 120× faster than Wan 2.2-A14B under the same one-H100 setup SANA-Video 2.0 shows that high-quality 720p video generation can be both efficient and practical on a single GPU. 🎬 Project: 📄 Paper: 💻 Code: Proud of the team! 🎉 More details below 🧵

🚀 SANA-Video 2.0 is here! A full-stack optimized video model designed for efficiency — while still delivering high quality. We combine a hybrid architecture closely related to the recent Kimi K3 design, adopt Self-Flow from FLUX 3, and further accelerate it with our own Sol-Engine. Key technical ingredients: 🧠 Hybrid Linear–Softmax Attention 3 gated linear layers + 1 gated-softmax anchor (75% linear / 25% softmax) 🧱 Block Attention Residuals (AttnRes) Boosts deep-layer effective rank by ~12% 🏗️ Unified 5B & 14B models Trained from scratch under very limited resources: • 5B → only 16 nodes of H100 • 14B → 48 nodes of B200 Results 📊 • 84.30 VBench Total • 3.2× faster DiT forward than matched full-softmax at 720p/60s • 720p/5s in 13.06s on a single H100 with Sol-Engine • 120× faster than Wan 2.2-A14B under the same one-H100 setup SANA-Video 2.0 shows that high-quality 720p video generation can be both efficient and practical on a single GPU. 🎬 Project: 📄 Paper: 💻 Code: Proud of the team! 🎉 More details below 🧵

Enze Xie

25,420 görüntüleme • 1 ay önce

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.

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 görüntüleme • 3 ay önce

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.

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 görüntüleme • 4 ay önce

Prompt-to-DeFi Early Access is now live. Today, DeFi strategy creation and execution changes forever: The agentic way. One prompt. Complete execution. INFINIT possibilities. Describe any DeFi strategy or workflow in plain language and watch the INFINIT AI Agent Swarm transform them into executable DeFi strategies. Here's how the new way to DeFi looks like. > Prompt-to-DeFi Makes DeFi Navigation As Simple As Typing Early Access Now Available For Phase 1 Waitlisters & Code Holders The Beginning of The Agentic DeFi Economy < Creators in this early phase position themselves at an advantage over others before fee collection and fee sharing to creators are enabled. Later on, creators will earn fees as users adopt their frameworks, attracting more creators and accelerating universal access to expert-level DeFi. The flywheel accelerates toward expert-level DeFi for everyone. Creativity is now the only limit. Start getting creative now:

Prompt-to-DeFi Early Access is now live. Today, DeFi strategy creation and execution changes forever: The agentic way. One prompt. Complete execution. INFINIT possibilities. Describe any DeFi strategy or workflow in plain language and watch the INFINIT AI Agent Swarm transform them into executable DeFi strategies. Here's how the new way to DeFi looks like. > Prompt-to-DeFi Makes DeFi Navigation As Simple As Typing Early Access Now Available For Phase 1 Waitlisters & Code Holders The Beginning of The Agentic DeFi Economy < Creators in this early phase position themselves at an advantage over others before fee collection and fee sharing to creators are enabled. Later on, creators will earn fees as users adopt their frameworks, attracting more creators and accelerating universal access to expert-level DeFi. The flywheel accelerates toward expert-level DeFi for everyone. Creativity is now the only limit. Start getting creative now:

INFINIT

103,939 görüntüleme • 8 ay önce

Hezbollah has been boasting how it could destroy the USS Gerald R. Ford (CVN-78) and its escorts. Lets dive into how Hezbollah Terrorists could attack a US Navy Aircraft carrier in the Med, what could happen, and the possible outcomes, assisted with Command Development Team simulation software. To understand the footage shown, let me break down some basic concepts of modern naval combat: Military ships often use a concept called "EMCON", which stands for EMission CONtrol, or "Radio silence" in laymans terms. Consider it like this: if you are with a flashlight in the night, you can spot a person say 500 Meters away by shining at him with the flashlight. You will however, be able to see that flashlight from many kilometers away, without being seen, even if it is directed at you, giving you the location of the person with the flashlight, without disclosing your presence. So ships really avoid "radio emissions", such as radar. Carrier Strike Groups (CSG) like the Ford CSG WANT Radar coverage for their own safety, but not in a way that their location can be known. This is done by Airplanes that fly in the general vicinity of the CSG, providing coverage, without compromising the CSG location. The US Navy uses the E-2 Hawkeye for this in most cases. In this case here, we are not using the E-2 Hawkeye, but the (likely in Theater anyway) E-3 Sentry from NATO. A system that is likely LESS sophisticated than the cutting edge E-2D Advanced Hawkeyes that were visible on the USS Ford pictures that surfaced recently. We do not simulate any carrier based "Combat Air Patrol" either, to test the "ship based" defenses. The composition of the Ford CSG is modeled using the actual ships listed. The CSG is moving on a nothern course at 15 knots, under full EMCON, 115 miles off the coast. The maximum range of the Russian Bastion-P coastal missle complex is about 100 miles, we have to assume that the US Navy will sail their ships outside of (possible) Hezbollah radar range. We also assume, as this is a time of very heightened alert, that the US Navy has Rules of Engagement that would allow it to shoot down any Hezbollah drones or craft coming at it with apparent hostile intention. I have assumed this to be 50 miles away from the CSG in this scenario. Now lets look at the Hezbollah side. We assume to have 6 Bastion-P complexes, with 2 missles per Transport-Erector-Launcher (TEL). So if it can be figured out where the CSG is, 12 P-800 Oniks missle with speeds over Mach 2 would be able to engage the CSG. The problem however is, that you can not "shoot" at a ship without knowing its location. While this may sound very simple indeed, when the ship you are looking for does not disclose its location voluntarily, you can not go to "marinetraffic" and look for the carrier. You can also not use your airforce, if you do not really have one, like Hezbollah. You can not use Sattelites, if you have none. You can try to use drones, if you know the overall direction, or use radar. Land based Radar? Out of Range. Drones? Yes, lets fly drones to the overall direction, hoping to see the carrier. Satellites? Nope. Wait, lets ask Putin. He will probably be nice enough to us, to have a liasion tell us in real time from a russian sattelite where the CSG is. And thats what we are running with here, as drones will not reach the carrier. A russian sattelite could provide rather real time information on the CSG location, allowing manual targeting. The video will provide you with the results. A US CSG with such powerful escorts will not be fundamentally threatened by the assets of Hezbollah. It will have to defend, but will do so rather easily. At the conclusion of the Engagement, the CSG still has literally 100s of SM-2, SM-6 and ESSM Missles. Note: this is done on commercially available software, the software uses NTDS/APP6 icons, white is air radar range, yellow surface, green sonar. The white cones off the missles are their onboard active radar seeker. If you have any questions understanding any of the things displyed, please ask. Note that this is a hobby analysis with publicly available data and tools, and not military research. Thanks for reading! #usnavy #HezbollahTerrorists #hezbullah #hezbollah #israel #IsraelUnderAttack #ukraine #russia #nato Naval News SubBrief Tyler Rogoway Status-6 (War & Military News) TheIntelFrog @CovertShores Raw Combat log output, starting with Hezbollah detecting CSG via RU Proxy: 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1070 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1071 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1072 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1073 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1145.4nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1074 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1153.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1075 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1148nm 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1073 has been positively identified as: DDG 63 Carney [Arleigh Burke Flight I] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1121 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1071 has been positively identified as: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1070 has been positively identified as: CVN 78 Gerald R. Ford - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1072 has been positively identified as: DDG 61 Ramage [Arleigh Burke Flight I] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1074 has been positively identified as: DDG 80 Roosevelt [Arleigh Burke Flight IIA] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1129 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1075 has been positively identified as: CG 60 Normandy [Ticonderoga Baseline 3, VLS] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1124 nm) 13/10/2023 12:47:23 - [USA] Contact: BOGEY #24 has been classified as: Ababil-3 UAV [Mod. Seeker 2D Copy] - Determined as: Unfriendly (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: AN/SPY-1D(V) MFR [ABM Mod]] [NCTR mode] at 56.9 nm) 13/10/2023 12:47:23 - [USA] Contact: BOGEY #26 has been classified as: Shahed-161 UAV - Determined as: Unfriendly (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: AN/SPY-1D(V) MFR [ABM Mod]] [NCTR mode] at 34.9 nm) 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3507 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 95.2nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3508 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.4nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3509 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 95.6nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3510 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.8nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3511 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.1nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3512 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.4nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3513 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 97.1nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3514 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 98nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3515 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 97.2nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3576 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 68deg - 91nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3577 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 89.9nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3578 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 90.7nm 13/10/2023 12:48:13 - Side 'Hezbollah' is now considered HOSTILE to USA 13/10/2023 12:48:13 - [USA] Contact: Shahed-161 UAV #26 has been manually marked as hostile! 13/10/2023 12:48:20 - [USA] Contact: BOGEY #22 has been manually marked as hostile! 13/10/2023 12:48:55 - [Hezbollah] New contact! Designated SAM #1238 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 266deg - 10nm 13/10/2023 12:48:59 - [Hezbollah] New contact! Designated SAM #1243 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 266deg - 8.6nm 13/10/2023 12:49:00 - [Hezbollah] New contact! Designated SAM #1245 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 234deg - 13.3nm 13/10/2023 12:49:17 - Weapon: RIM-174A ERAM SM-6 Blk IA #40 is attacking Shahed-161 UAV with a base PH of 90%. PH adjusted for weapon speed: 36% (pure-aerodynamic attitude control). Intercept angle is 304 deg - hit probability adjusted to 25%.Final PH: 25%. Result: 30 - MISS 13/10/2023 12:49:17 - [Hezbollah] Hezbollah :Contact SAM #1238 has been lost. 13/10/2023 12:49:25 - [Hezbollah] New contact! Designated SAM #1271 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 248deg - 13.1nm 13/10/2023 12:49:34 - Weapon: RIM-174A ERAM SM-6 Blk IB #41 is attacking Ababil-3 UAV [Mod. Seeker 2D Copy] with a base PH of 90%. Intercept angle is 51 deg - hit probability adjusted to 65%.Final PH: 65%. Result: 12 - HIT 13/10/2023 12:49:34 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:34 - [Hezbollah] Hezbollah :Contact SAM #1271 has been lost. 13/10/2023 12:49:34 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has been destroyed! 13/10/2023 12:49:34 - [USA] Contact Ababil-3 UAV [Mod. Seeker 2D Copy] #23 has been lost. 13/10/2023 12:49:39 - Weapon: RIM-174A ERAM SM-6 Blk IB #42 is attacking Ababil-3 UAV [Mod. Seeker 2D Copy] with a base PH of 90%. Intercept angle is 313 deg - hit probability adjusted to 66%.Final PH: 66%. Result: 11 - HIT 13/10/2023 12:49:39 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:39 - [Hezbollah] Hezbollah :Contact SAM #1243 has been lost. 13/10/2023 12:49:39 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has been destroyed! 13/10/2023 12:49:39 - [USA] Contact Ababil-3 UAV [Mod. Seeker 2D Copy] #24 has been lost. 13/10/2023 12:49:43 - Weapon: RIM-174A ERAM SM-6 Blk IB #43 is attacking Shahed-161 UAV with a base PH of 90%. Intercept angle is 65 deg - hit probability adjusted to 57%.Final PH: 57%. Result: 11 - HIT 13/10/2023 12:49:43 - [Hezbollah] Shahed-161 UAV has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:43 - [Hezbollah] Hezbollah :Contact SAM #1245 has been lost. 13/10/2023 12:49:43 - [Hezbollah] Shahed-161 UAV has been destroyed! 13/10/2023 12:49:43 - [USA] Contact Shahed-161 UAV #25 has been lost. 13/10/2023 12:49:54 - [Hezbollah] New contact! Designated SAM #1301 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 258deg - 10.5nm 13/10/2023 12:50:10 - Weapon: RIM-174A ERAM SM-6 Blk IA #44 is attacking Shahed-161 UAV with a base PH of 90%. PH adjusted for weapon speed: 83% (pure-aerodynamic attitude control). Target signature modifier: -5% (Director [Active Radar Seeker] has tech-gen: Late 2010s). Intercept angle is 316 deg - hit probability adjusted to 59%.Final PH: 59%. Result: 42 - HIT 13/10/2023 12:50:10 - [Hezbollah] Shahed-161 UAV has suffered weapon damage: 89 DPs 13/10/2023 12:50:10 - [Hezbollah] Hezbollah :Contact SAM #1301 has been lost. 13/10/2023 12:50:10 - [Hezbollah] Shahed-161 UAV has been destroyed! 13/10/2023 12:50:10 - [USA] Contact Shahed-161 UAV #26 has been lost. 13/10/2023 12:51:58 - [USA] Contact: VAMPIRE #3507 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3508 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3509 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3511 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:00 - [USA] Contact: VAMPIRE #3510 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:00 - [USA] Contact: VAMPIRE #3512 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:04 - [USA] Contact: VAMPIRE #3513 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:04 - [USA] Contact: VAMPIRE #3577 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:05 - [USA] Contact: VAMPIRE #3514 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:05 - [USA] Contact: VAMPIRE #3515 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:06 - [USA] Contact: VAMPIRE #3576 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:06 - [USA] Contact: VAMPIRE #3578 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:08 - Weapon: RIM-162D ESSM #45 is attacking SSC-5 Stooge [P-800 Yakhont] #28 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 357 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 34 - HIT 13/10/2023 12:52:08 - [USA] Contact GuidedWeapon #3507 has been lost. 13/10/2023 12:52:09 - Weapon: RIM-162D ESSM #46 is attacking SSC-5 Stooge [P-800 Yakhont] #29 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 31 - HIT 13/10/2023 12:52:09 - [USA] Contact GuidedWeapon #3508 has been lost. 13/10/2023 12:52:11 - Weapon: RIM-162D ESSM #49 is attacking SSC-5 Stooge [P-800 Yakhont] #32 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 36 - HIT 13/10/2023 12:52:11 - [USA] Contact GuidedWeapon #3511 has been lost. 13/10/2023 12:52:11 - Weapon: RIM-162A ESSM #52 is attacking SSC-5 Stooge [P-800 Yakhont] #31 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 355 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 9 - HIT 13/10/2023 12:52:11 - [USA] Weapon: RIM-162A ESSM #57 has been redirected to new target: GuidedWeapon #3515 13/10/2023 12:52:11 - [USA] Contact GuidedWeapon #3510 has been lost. 13/10/2023 12:52:12 - Weapon: RIM-162D ESSM #50 is attacking SSC-5 Stooge [P-800 Yakhont] #30 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 356 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 25 - HIT 13/10/2023 12:52:12 - [USA] Contact GuidedWeapon #3509 has been lost. 13/10/2023 12:52:12 - Weapon: RIM-162A ESSM #55 is attacking SSC-5 Stooge [P-800 Yakhont] #33 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 355 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 20 - HIT 13/10/2023 12:52:12 - [USA] Weapon: RIM-162A ESSM #59 has been redirected to new target: GuidedWeapon #3576 13/10/2023 12:52:12 - [USA] Contact GuidedWeapon #3512 has been lost. 13/10/2023 12:52:13 - [USA] Weapon: RIM-162D ESSM #47 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:14 - [USA] Weapon: RIM-162D ESSM #48 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:15 - Weapon: RIM-162A ESSM #57 is attacking SSC-5 Stooge [P-800 Yakhont] #36 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 0 deg - hit probability adjusted to 80%.Final PH: 80%. Result: 71 - HIT 13/10/2023 12:52:15 - [USA] Contact GuidedWeapon #3515 has been lost. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #60 is attacking SSC-5 Stooge [P-800 Yakhont] #34 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 360 deg - hit probability adjusted to 80%.Final PH: 80%. Result: 49 - HIT 13/10/2023 12:52:16 - [USA] Weapon: RIM-162A ESSM #65 has no eligible alternative target to be redirected to... 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3513 has been lost. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #51 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #54 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #58 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #59 is attacking SSC-5 Stooge [P-800 Yakhont] #38 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 357 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 75 - HIT 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3576 has been lost. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #63 is attacking SSC-5 Stooge [P-800 Yakhont] #38 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 359 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 57 - HIT 13/10/2023 12:52:16 - [USA] Weapon: RIM-162A ESSM #70 has been redirected to new target: GuidedWeapon #3514 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3577 has been lost. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #53 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162A ESSM #65 has no eligible alternative target to be redirected to... 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #56 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #61 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:18 - Weapon: RIM-162A ESSM #70 is attacking SSC-5 Stooge [P-800 Yakhont] #35 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 63 - HIT 13/10/2023 12:52:18 - [USA] Contact GuidedWeapon #3514 has been lost. 13/10/2023 12:52:18 - Weapon: RIM-174A ERAM SM-6 Blk IA #73 is attacking SSC-5 Stooge [P-800 Yakhont] #39 with a base PH of 90%. Intercept angle is 355 deg - hit probability adjusted to 88%.Final PH: 88%. Result: 34 - HIT 13/10/2023 12:52:18 - [USA] Contact GuidedWeapon #3578 has been lost.

Hezbollah has been boasting how it could destroy the USS Gerald R. Ford (CVN-78) and its escorts. Lets dive into how Hezbollah Terrorists could attack a US Navy Aircraft carrier in the Med, what could happen, and the possible outcomes, assisted with Command Development Team simulation software. To understand the footage shown, let me break down some basic concepts of modern naval combat: Military ships often use a concept called "EMCON", which stands for EMission CONtrol, or "Radio silence" in laymans terms. Consider it like this: if you are with a flashlight in the night, you can spot a person say 500 Meters away by shining at him with the flashlight. You will however, be able to see that flashlight from many kilometers away, without being seen, even if it is directed at you, giving you the location of the person with the flashlight, without disclosing your presence. So ships really avoid "radio emissions", such as radar. Carrier Strike Groups (CSG) like the Ford CSG WANT Radar coverage for their own safety, but not in a way that their location can be known. This is done by Airplanes that fly in the general vicinity of the CSG, providing coverage, without compromising the CSG location. The US Navy uses the E-2 Hawkeye for this in most cases. In this case here, we are not using the E-2 Hawkeye, but the (likely in Theater anyway) E-3 Sentry from NATO. A system that is likely LESS sophisticated than the cutting edge E-2D Advanced Hawkeyes that were visible on the USS Ford pictures that surfaced recently. We do not simulate any carrier based "Combat Air Patrol" either, to test the "ship based" defenses. The composition of the Ford CSG is modeled using the actual ships listed. The CSG is moving on a nothern course at 15 knots, under full EMCON, 115 miles off the coast. The maximum range of the Russian Bastion-P coastal missle complex is about 100 miles, we have to assume that the US Navy will sail their ships outside of (possible) Hezbollah radar range. We also assume, as this is a time of very heightened alert, that the US Navy has Rules of Engagement that would allow it to shoot down any Hezbollah drones or craft coming at it with apparent hostile intention. I have assumed this to be 50 miles away from the CSG in this scenario. Now lets look at the Hezbollah side. We assume to have 6 Bastion-P complexes, with 2 missles per Transport-Erector-Launcher (TEL). So if it can be figured out where the CSG is, 12 P-800 Oniks missle with speeds over Mach 2 would be able to engage the CSG. The problem however is, that you can not "shoot" at a ship without knowing its location. While this may sound very simple indeed, when the ship you are looking for does not disclose its location voluntarily, you can not go to "marinetraffic" and look for the carrier. You can also not use your airforce, if you do not really have one, like Hezbollah. You can not use Sattelites, if you have none. You can try to use drones, if you know the overall direction, or use radar. Land based Radar? Out of Range. Drones? Yes, lets fly drones to the overall direction, hoping to see the carrier. Satellites? Nope. Wait, lets ask Putin. He will probably be nice enough to us, to have a liasion tell us in real time from a russian sattelite where the CSG is. And thats what we are running with here, as drones will not reach the carrier. A russian sattelite could provide rather real time information on the CSG location, allowing manual targeting. The video will provide you with the results. A US CSG with such powerful escorts will not be fundamentally threatened by the assets of Hezbollah. It will have to defend, but will do so rather easily. At the conclusion of the Engagement, the CSG still has literally 100s of SM-2, SM-6 and ESSM Missles. Note: this is done on commercially available software, the software uses NTDS/APP6 icons, white is air radar range, yellow surface, green sonar. The white cones off the missles are their onboard active radar seeker. If you have any questions understanding any of the things displyed, please ask. Note that this is a hobby analysis with publicly available data and tools, and not military research. Thanks for reading! #usnavy #HezbollahTerrorists #hezbullah #hezbollah #israel #IsraelUnderAttack #ukraine #russia #nato Naval News SubBrief Tyler Rogoway Status-6 (War & Military News) TheIntelFrog @CovertShores Raw Combat log output, starting with Hezbollah detecting CSG via RU Proxy: 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1070 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1071 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1072 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1149.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1073 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1145.4nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1074 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1153.3nm 13/10/2023 12:46:13 - [Hezbollah] New contact! Designated SKUNK #1075 - Detected by Resurs P1 [Sensors: Generic Satellite Visual Camera] at 177deg - 1148nm 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1073 has been positively identified as: DDG 63 Carney [Arleigh Burke Flight I] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1121 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1071 has been positively identified as: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1070 has been positively identified as: CVN 78 Gerald R. Ford - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1072 has been positively identified as: DDG 61 Ramage [Arleigh Burke Flight I] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1125 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1074 has been positively identified as: DDG 80 Roosevelt [Arleigh Burke Flight IIA] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1129 nm) 13/10/2023 12:46:23 - [Hezbollah] Contact: SKUNK #1075 has been positively identified as: CG 60 Normandy [Ticonderoga Baseline 3, VLS] - Determined as: Hostile (ID by: Resurs P1 [Sensor: Generic Satellite Visual Camera] at Estimated 1124 nm) 13/10/2023 12:47:23 - [USA] Contact: BOGEY #24 has been classified as: Ababil-3 UAV [Mod. Seeker 2D Copy] - Determined as: Unfriendly (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: AN/SPY-1D(V) MFR [ABM Mod]] [NCTR mode] at 56.9 nm) 13/10/2023 12:47:23 - [USA] Contact: BOGEY #26 has been classified as: Shahed-161 UAV - Determined as: Unfriendly (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: AN/SPY-1D(V) MFR [ABM Mod]] [NCTR mode] at 34.9 nm) 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3507 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 95.2nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3508 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.4nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3509 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 95.6nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3510 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.8nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3511 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.1nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3512 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 96.4nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3513 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 97.1nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3514 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 98nm 13/10/2023 12:47:52 - [USA] New contact! Designated VAMPIRE #3515 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 70deg - 97.2nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3576 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 68deg - 91nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3577 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 89.9nm 13/10/2023 12:48:12 - [USA] New contact! Designated VAMPIRE #3578 - Detected by E-3A Sentry [Sensors: AN/APY-2 RSIP] at 69deg - 90.7nm 13/10/2023 12:48:13 - Side 'Hezbollah' is now considered HOSTILE to USA 13/10/2023 12:48:13 - [USA] Contact: Shahed-161 UAV #26 has been manually marked as hostile! 13/10/2023 12:48:20 - [USA] Contact: BOGEY #22 has been manually marked as hostile! 13/10/2023 12:48:55 - [Hezbollah] New contact! Designated SAM #1238 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 266deg - 10nm 13/10/2023 12:48:59 - [Hezbollah] New contact! Designated SAM #1243 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 266deg - 8.6nm 13/10/2023 12:49:00 - [Hezbollah] New contact! Designated SAM #1245 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 234deg - 13.3nm 13/10/2023 12:49:17 - Weapon: RIM-174A ERAM SM-6 Blk IA #40 is attacking Shahed-161 UAV with a base PH of 90%. PH adjusted for weapon speed: 36% (pure-aerodynamic attitude control). Intercept angle is 304 deg - hit probability adjusted to 25%.Final PH: 25%. Result: 30 - MISS 13/10/2023 12:49:17 - [Hezbollah] Hezbollah :Contact SAM #1238 has been lost. 13/10/2023 12:49:25 - [Hezbollah] New contact! Designated SAM #1271 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 248deg - 13.1nm 13/10/2023 12:49:34 - Weapon: RIM-174A ERAM SM-6 Blk IB #41 is attacking Ababil-3 UAV [Mod. Seeker 2D Copy] with a base PH of 90%. Intercept angle is 51 deg - hit probability adjusted to 65%.Final PH: 65%. Result: 12 - HIT 13/10/2023 12:49:34 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:34 - [Hezbollah] Hezbollah :Contact SAM #1271 has been lost. 13/10/2023 12:49:34 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has been destroyed! 13/10/2023 12:49:34 - [USA] Contact Ababil-3 UAV [Mod. Seeker 2D Copy] #23 has been lost. 13/10/2023 12:49:39 - Weapon: RIM-174A ERAM SM-6 Blk IB #42 is attacking Ababil-3 UAV [Mod. Seeker 2D Copy] with a base PH of 90%. Intercept angle is 313 deg - hit probability adjusted to 66%.Final PH: 66%. Result: 11 - HIT 13/10/2023 12:49:39 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:39 - [Hezbollah] Hezbollah :Contact SAM #1243 has been lost. 13/10/2023 12:49:39 - [Hezbollah] Ababil-3 UAV [Mod. Seeker 2D Copy] has been destroyed! 13/10/2023 12:49:39 - [USA] Contact Ababil-3 UAV [Mod. Seeker 2D Copy] #24 has been lost. 13/10/2023 12:49:43 - Weapon: RIM-174A ERAM SM-6 Blk IB #43 is attacking Shahed-161 UAV with a base PH of 90%. Intercept angle is 65 deg - hit probability adjusted to 57%.Final PH: 57%. Result: 11 - HIT 13/10/2023 12:49:43 - [Hezbollah] Shahed-161 UAV has suffered weapon damage: 89.9 DPs 13/10/2023 12:49:43 - [Hezbollah] Hezbollah :Contact SAM #1245 has been lost. 13/10/2023 12:49:43 - [Hezbollah] Shahed-161 UAV has been destroyed! 13/10/2023 12:49:43 - [USA] Contact Shahed-161 UAV #25 has been lost. 13/10/2023 12:49:54 - [Hezbollah] New contact! Designated SAM #1301 - Detected by Shahed-161 UAV [Sensors: Generic IRST] at 258deg - 10.5nm 13/10/2023 12:50:10 - Weapon: RIM-174A ERAM SM-6 Blk IA #44 is attacking Shahed-161 UAV with a base PH of 90%. PH adjusted for weapon speed: 83% (pure-aerodynamic attitude control). Target signature modifier: -5% (Director [Active Radar Seeker] has tech-gen: Late 2010s). Intercept angle is 316 deg - hit probability adjusted to 59%.Final PH: 59%. Result: 42 - HIT 13/10/2023 12:50:10 - [Hezbollah] Shahed-161 UAV has suffered weapon damage: 89 DPs 13/10/2023 12:50:10 - [Hezbollah] Hezbollah :Contact SAM #1301 has been lost. 13/10/2023 12:50:10 - [Hezbollah] Shahed-161 UAV has been destroyed! 13/10/2023 12:50:10 - [USA] Contact Shahed-161 UAV #26 has been lost. 13/10/2023 12:51:58 - [USA] Contact: VAMPIRE #3507 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3508 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3509 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:51:59 - [USA] Contact: VAMPIRE #3511 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:00 - [USA] Contact: VAMPIRE #3510 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:00 - [USA] Contact: VAMPIRE #3512 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:04 - [USA] Contact: VAMPIRE #3513 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:04 - [USA] Contact: VAMPIRE #3577 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:05 - [USA] Contact: VAMPIRE #3514 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:05 - [USA] Contact: VAMPIRE #3515 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:06 - [USA] Contact: VAMPIRE #3576 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 13.9 nm) 13/10/2023 12:52:06 - [USA] Contact: VAMPIRE #3578 has been type-classified as: GuidedWeapon (Classification by: DDG 116 Thomas Hudner [Arleigh Burke Flight IIA Technology Insertion] [Sensor: Mk46 Mod 1 [CCD]] at 14 nm) 13/10/2023 12:52:08 - Weapon: RIM-162D ESSM #45 is attacking SSC-5 Stooge [P-800 Yakhont] #28 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 357 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 34 - HIT 13/10/2023 12:52:08 - [USA] Contact GuidedWeapon #3507 has been lost. 13/10/2023 12:52:09 - Weapon: RIM-162D ESSM #46 is attacking SSC-5 Stooge [P-800 Yakhont] #29 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 31 - HIT 13/10/2023 12:52:09 - [USA] Contact GuidedWeapon #3508 has been lost. 13/10/2023 12:52:11 - Weapon: RIM-162D ESSM #49 is attacking SSC-5 Stooge [P-800 Yakhont] #32 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 36 - HIT 13/10/2023 12:52:11 - [USA] Contact GuidedWeapon #3511 has been lost. 13/10/2023 12:52:11 - Weapon: RIM-162A ESSM #52 is attacking SSC-5 Stooge [P-800 Yakhont] #31 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 355 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 9 - HIT 13/10/2023 12:52:11 - [USA] Weapon: RIM-162A ESSM #57 has been redirected to new target: GuidedWeapon #3515 13/10/2023 12:52:11 - [USA] Contact GuidedWeapon #3510 has been lost. 13/10/2023 12:52:12 - Weapon: RIM-162D ESSM #50 is attacking SSC-5 Stooge [P-800 Yakhont] #30 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 356 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 25 - HIT 13/10/2023 12:52:12 - [USA] Contact GuidedWeapon #3509 has been lost. 13/10/2023 12:52:12 - Weapon: RIM-162A ESSM #55 is attacking SSC-5 Stooge [P-800 Yakhont] #33 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 355 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 20 - HIT 13/10/2023 12:52:12 - [USA] Weapon: RIM-162A ESSM #59 has been redirected to new target: GuidedWeapon #3576 13/10/2023 12:52:12 - [USA] Contact GuidedWeapon #3512 has been lost. 13/10/2023 12:52:13 - [USA] Weapon: RIM-162D ESSM #47 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:14 - [USA] Weapon: RIM-162D ESSM #48 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:15 - Weapon: RIM-162A ESSM #57 is attacking SSC-5 Stooge [P-800 Yakhont] #36 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 0 deg - hit probability adjusted to 80%.Final PH: 80%. Result: 71 - HIT 13/10/2023 12:52:15 - [USA] Contact GuidedWeapon #3515 has been lost. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #60 is attacking SSC-5 Stooge [P-800 Yakhont] #34 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 360 deg - hit probability adjusted to 80%.Final PH: 80%. Result: 49 - HIT 13/10/2023 12:52:16 - [USA] Weapon: RIM-162A ESSM #65 has no eligible alternative target to be redirected to... 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3513 has been lost. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #51 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #54 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - [USA] Weapon: RIM-162D ESSM #58 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #59 is attacking SSC-5 Stooge [P-800 Yakhont] #38 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 357 deg - hit probability adjusted to 78%.Final PH: 78%. Result: 75 - HIT 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3576 has been lost. 13/10/2023 12:52:16 - Weapon: RIM-162A ESSM #63 is attacking SSC-5 Stooge [P-800 Yakhont] #38 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 359 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 57 - HIT 13/10/2023 12:52:16 - [USA] Weapon: RIM-162A ESSM #70 has been redirected to new target: GuidedWeapon #3514 13/10/2023 12:52:16 - [USA] Contact GuidedWeapon #3577 has been lost. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #53 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162A ESSM #65 has no eligible alternative target to be redirected to... 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #56 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:17 - [USA] Weapon: RIM-162D ESSM #61 is running blind for more than 5 sec... self-destructing. 13/10/2023 12:52:18 - Weapon: RIM-162A ESSM #70 is attacking SSC-5 Stooge [P-800 Yakhont] #35 with a base PH of 90%. Target speed modifier: -10%. Intercept angle is 358 deg - hit probability adjusted to 79%.Final PH: 79%. Result: 63 - HIT 13/10/2023 12:52:18 - [USA] Contact GuidedWeapon #3514 has been lost. 13/10/2023 12:52:18 - Weapon: RIM-174A ERAM SM-6 Blk IA #73 is attacking SSC-5 Stooge [P-800 Yakhont] #39 with a base PH of 90%. Intercept angle is 355 deg - hit probability adjusted to 88%.Final PH: 88%. Result: 34 - HIT 13/10/2023 12:52:18 - [USA] Contact GuidedWeapon #3578 has been lost.

C Schmitz

47,721 görüntüleme • 2 yıl önce

My RLM finally went recursive! Looking at these logs is way too addictive please send help. Notes: > Sent it 10 long wikipedia articles about deep learning (~2M context). > Asked it to find BLEU scores from Attention paper & explain MHA from these articles > RLM controlled by the new Minimax 2.5 ! Minor prompt changes were needed from the RLM paper. > Spends first 3 iterations understanding data format, works through errors, until it locates the Attention article from the mess. Like a human would use a Jupyter Notebook. > Launches subagent on only AIAYN article > This subagent launches 2 more subagents to fetch (a) BLEU score and (b) MHA (my original two-part question) > The lowest subagent returns the output using "FINAL_VAR" (i.e. it does not generate the text! Just finds the correct location in the context and sends it back as a variable) > Recursion propagates upwards > Outermost LLM recieves the RLM output, and generates the full text response. > Took 2.5 minutes walltime. Max recursion depth level was 2. 12 LLM calls in total. (This video contains cuts when the LLM is thinking/generating) > Subagents never gets to see more than 2000 characters. Only the outermost LLM gets to see the full output - it's needed to answer the final question, but its only 200-300 tokens compared to 2M! > Fully async. Code execution and subagent tasks can happen simultaneously! I feel soooo satisfied. Been some time since I've been this excited about shooting a tutorial video.

My RLM finally went recursive! Looking at these logs is way too addictive please send help. Notes: > Sent it 10 long wikipedia articles about deep learning (~2M context). > Asked it to find BLEU scores from Attention paper & explain MHA from these articles > RLM controlled by the new Minimax 2.5 ! Minor prompt changes were needed from the RLM paper. > Spends first 3 iterations understanding data format, works through errors, until it locates the Attention article from the mess. Like a human would use a Jupyter Notebook. > Launches subagent on only AIAYN article > This subagent launches 2 more subagents to fetch (a) BLEU score and (b) MHA (my original two-part question) > The lowest subagent returns the output using "FINAL_VAR" (i.e. it does not generate the text! Just finds the correct location in the context and sends it back as a variable) > Recursion propagates upwards > Outermost LLM recieves the RLM output, and generates the full text response. > Took 2.5 minutes walltime. Max recursion depth level was 2. 12 LLM calls in total. (This video contains cuts when the LLM is thinking/generating) > Subagents never gets to see more than 2000 characters. Only the outermost LLM gets to see the full output - it's needed to answer the final question, but its only 200-300 tokens compared to 2M! > Fully async. Code execution and subagent tasks can happen simultaneously! I feel soooo satisfied. Been some time since I've been this excited about shooting a tutorial video.

AVB

38,241 görüntüleme • 6 ay önce

It has been a long time since I made a video. I am sharing a deep dive into 2fac, a new 2FA app I built to replace Authy. What makes this project special is its massive scope, running natively across Android, iOS, watchOS, desktop, CLI, browser extensions, and the web. Building this many features across so many platforms was only possible through agentic coding. Huge thanks to Copilot, Claude, OpenCode, and Pi for completely changing how I write software. Here is what is covered in the video. In the pre-AI world, so many features, taking it to such a polished state (ui, design, relialibility of how it works, and quality of code too, you can take a look for yourelf) single handedly, that too working on spare time on the side from a day job, was simply not possible for non 10x, mid engineers like me 00:00:00 Project Overview & Motivation 00:03:31 Android App Demo 00:04:19 iOS & watchOS App Demo 00:05:32 Desktop App Demo 00:06:05 System Tray Integration 00:07:05 CLI Demo 00:08:44 Browser Extension Demo 00:10:00 Web App (PWA) Demo 00:11:40 Secure Unlock & Passkeys 00:16:30 GitHub Repo & Release Plans 00:17:30 CI/CD Pipeline Setup 00:19:00 AI Agentic Coding Workflow 00:23:50 Production Usage Warning 00:26:00 Custom AI Agent Skills 00:28:30 Automated Planning & Roadmaps 00:31:14 UI Testing with Maestro 00:35:12 Creating Custom AI Agents 00:38:34 Codebase Test Coverage 00:41:30 AI-Driven TDD

It has been a long time since I made a video. I am sharing a deep dive into 2fac, a new 2FA app I built to replace Authy. What makes this project special is its massive scope, running natively across Android, iOS, watchOS, desktop, CLI, browser extensions, and the web. Building this many features across so many platforms was only possible through agentic coding. Huge thanks to Copilot, Claude, OpenCode, and Pi for completely changing how I write software. Here is what is covered in the video. In the pre-AI world, so many features, taking it to such a polished state (ui, design, relialibility of how it works, and quality of code too, you can take a look for yourelf) single handedly, that too working on spare time on the side from a day job, was simply not possible for non 10x, mid engineers like me 00:00:00 Project Overview & Motivation 00:03:31 Android App Demo 00:04:19 iOS & watchOS App Demo 00:05:32 Desktop App Demo 00:06:05 System Tray Integration 00:07:05 CLI Demo 00:08:44 Browser Extension Demo 00:10:00 Web App (PWA) Demo 00:11:40 Secure Unlock & Passkeys 00:16:30 GitHub Repo & Release Plans 00:17:30 CI/CD Pipeline Setup 00:19:00 AI Agentic Coding Workflow 00:23:50 Production Usage Warning 00:26:00 Custom AI Agent Skills 00:28:30 Automated Planning & Roadmaps 00:31:14 UI Testing with Maestro 00:35:12 Creating Custom AI Agents 00:38:34 Codebase Test Coverage 00:41:30 AI-Driven TDD

Arnav Gupta

109,905 görüntüleme • 5 ay önce

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

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

Himanshu Kumar

13,677 görüntüleme • 4 ay önce

🚀 The Segment Anything Model (SAM) has been upgraded to SAM2, featuring an efficient image encoder for segmenting images and videos. But does SAM2 outperform SAM1 in medical image and video segmentation? We're thrilled to present our paper "Segment Anything in Medical Images and Videos: Benchmark and Deployment"! We comprehensively benchmark SAM2 across 11 medical image modalities and videos. 📄 Paper: 💻 Code: **Highlights:** 1. SAM2 doesn’t always outperform SAM1 in 2D medical images, but excels in video segmentation, making it more accurate and efficient for 3D images, such as CT and MR scans. 2. MedSAM still outperforms SAM2 on most 2D modalities, but SAM2 surpasses MedSAM for 3D image segmentation in a slice-by-slice approach. 3. Segmentation performance varies with model size; sometimes the smallest model outperforms larger ones. 4. Fine-tuning SAM2 significantly boosts its performance for medical image segmentation. While SAM2 may struggle with challenging objects that have unclear boundaries or low contrast, it excels in generating good initial segmentation masks for common medical images and videos. However, the official interface doesn’t support medical data formats and has limitations on video length. To address this, we've developed a 3D Slicer Plugin and Gradio API for efficient 3D medical image and video segmentation. We invite you to try them out and provide feedback! 🔧 Deployment: - 3D Slicer Plugin: - Gradio API: (Note: Due to GPU limitations, the online API is available for only 12 hours and may be slow. We highly recommend deploying the Gradio API with your own computing resources: A big shoutout to Jun Ma (JunMa) who recently joined our UHN AI hub (UHN AI Hub) as Machine Learning Lead, and kudos to all co-authors: Sumin Kim, Feifei Li, Mohammed Baharoon (Mohammed Baharoon), Reza Asakereh, and Hongwei Lyu! This is true teamwork! Looking forward to collaborating with the community to advance 3D medical image and video segmentation foundation models! University Health Network U of T Department of Computer Science Department of Laboratory Medicine & Pathobiology Temerty Centre for AI in Medicine (T-CAIREM) Vector Institute #MedTech #AIinHealthcare #DeepLearning #MedicalImaging #SAM2 #MedSAM #AIResearch

🚀 The Segment Anything Model (SAM) has been upgraded to SAM2, featuring an efficient image encoder for segmenting images and videos. But does SAM2 outperform SAM1 in medical image and video segmentation? We're thrilled to present our paper "Segment Anything in Medical Images and Videos: Benchmark and Deployment"! We comprehensively benchmark SAM2 across 11 medical image modalities and videos. 📄 Paper: 💻 Code: Highlights: 1. SAM2 doesn’t always outperform SAM1 in 2D medical images, but excels in video segmentation, making it more accurate and efficient for 3D images, such as CT and MR scans. 2. MedSAM still outperforms SAM2 on most 2D modalities, but SAM2 surpasses MedSAM for 3D image segmentation in a slice-by-slice approach. 3. Segmentation performance varies with model size; sometimes the smallest model outperforms larger ones. 4. Fine-tuning SAM2 significantly boosts its performance for medical image segmentation. While SAM2 may struggle with challenging objects that have unclear boundaries or low contrast, it excels in generating good initial segmentation masks for common medical images and videos. However, the official interface doesn’t support medical data formats and has limitations on video length. To address this, we've developed a 3D Slicer Plugin and Gradio API for efficient 3D medical image and video segmentation. We invite you to try them out and provide feedback! 🔧 Deployment: - 3D Slicer Plugin: - Gradio API: (Note: Due to GPU limitations, the online API is available for only 12 hours and may be slow. We highly recommend deploying the Gradio API with your own computing resources: A big shoutout to Jun Ma (JunMa) who recently joined our UHN AI hub (UHN AI Hub) as Machine Learning Lead, and kudos to all co-authors: Sumin Kim, Feifei Li, Mohammed Baharoon (Mohammed Baharoon), Reza Asakereh, and Hongwei Lyu! This is true teamwork! Looking forward to collaborating with the community to advance 3D medical image and video segmentation foundation models! University Health Network U of T Department of Computer Science Department of Laboratory Medicine & Pathobiology Temerty Centre for AI in Medicine (T-CAIREM) Vector Institute #MedTech #AIinHealthcare #DeepLearning #MedicalImaging #SAM2 #MedSAM #AIResearch

Bo Wang

178,579 görüntüleme • 2 yıl önce

Here's my conversation with Khabib Nurmagomedov (khabib nurmagomedov), one of the greatest fighters of all time. It was truly an honor to get to train with him, to have this deep conversation, and to get to know him over the past few months. We did this conversation entirely in Russian. It's translated and dubbed into English. Both language audio tracks and subtitles are available on YouTube. Here on X, I'm posting the English & Russian language versions as seperate videos. The translation & dubbing was a huge amount of work (which I deeply care about) with humans & AI collaborating. Thanks to the amazing team at ElevenLabs for their help. Good luck to Islam Makhachev, Khabib & team this weekend at UFC 330! And as I've said in the video, I'm truly grateful for all of you, for your support all these years. I love you all ❤️ Timestamps: 0:00 - Introduction 1:35 - Why Dagestan produces so many great fighters 11:41 - History of Dagestan warrior culture 21:02 - Hard training in the mountains of Dagestan 24:53 - The trap of fame, money, and power 35:34 - The key to Khabib's dominance 46:47 - Discipline and hard work 59:15 - Street fights in Dagestan 1:12:56 - Khabib's top pressure 1:18:40 - Khabib vs Conor McGregor 1:31:25 - Khabib's toughest fight 1:39:12 - Greatest MMA fighters of all time 1:56:57 - Coaching 2:02:30 - Daniel Cormier 2:06:48 - Islam Makhachev 2:16:46 - Dana White 2:20:16 - Joe Rogan 2:22:31 - Ali Abdelaziz 2:25:08 - Football 2:32:23 - Messi vs Ronaldo 2:50:23 - Dubai 2:54:14 - God 3:01:57 - Advice for young people

Here's my conversation with Khabib Nurmagomedov (khabib nurmagomedov), one of the greatest fighters of all time. It was truly an honor to get to train with him, to have this deep conversation, and to get to know him over the past few months. We did this conversation entirely in Russian. It's translated and dubbed into English. Both language audio tracks and subtitles are available on YouTube. Here on X, I'm posting the English & Russian language versions as seperate videos. The translation & dubbing was a huge amount of work (which I deeply care about) with humans & AI collaborating. Thanks to the amazing team at ElevenLabs for their help. Good luck to Islam Makhachev, Khabib & team this weekend at UFC 330! And as I've said in the video, I'm truly grateful for all of you, for your support all these years. I love you all ❤️ Timestamps: 0:00 - Introduction 1:35 - Why Dagestan produces so many great fighters 11:41 - History of Dagestan warrior culture 21:02 - Hard training in the mountains of Dagestan 24:53 - The trap of fame, money, and power 35:34 - The key to Khabib's dominance 46:47 - Discipline and hard work 59:15 - Street fights in Dagestan 1:12:56 - Khabib's top pressure 1:18:40 - Khabib vs Conor McGregor 1:31:25 - Khabib's toughest fight 1:39:12 - Greatest MMA fighters of all time 1:56:57 - Coaching 2:02:30 - Daniel Cormier 2:06:48 - Islam Makhachev 2:16:46 - Dana White 2:20:16 - Joe Rogan 2:22:31 - Ali Abdelaziz 2:25:08 - Football 2:32:23 - Messi vs Ronaldo 2:50:23 - Dubai 2:54:14 - God 3:01:57 - Advice for young people

Lex Fridman

401,930 görüntüleme • 18 gün önce

This is why TikTok was banned JUST before President Trump's inauguration. Incoming FBI Director Kash Patel said the FBI covered up ALL evidence pertaining to Jeffrey Epstein's client list. Which would mean that one DAY ONE of Kash being sworn in with President Trump, Kash will have direct access to ALL of it. He also stated President Trump should RELEASE the evidence (list) on DAY ONE of his Presidency. It's ABSOLUTELY NO COINCIDENCE our government fought like hell to BAN TIKTOK one day prior. Since 2017, Anons HERE worked tirelessly for 12+ hours a day, 7 days a week on Twitter to thread original open-source research and showing just how corrupt our government truly has been, dating back to its conception, hijacked by a 3,000+ year old satan worshipping cannibalistic death cult. In 2019 when Fauci's / ChYna's Covid-19 Bioweapon pLandemic was released, bored TikTok influencers under covid lockdowns were taking note of our viral Twitter threads and what we were doing here on the public stage as well as on Telegram after the TwitLer purges. The Truth movement we were birthing on the public stage spread to TikToka nd Instagram. Those influencers who were scrolling Twitter, started taking our research and uniquely compiled and written viral threads and turning our digs into video form for their TikTok audiences who had NO IDEA The Great Awakening was happening here on this platform. TikTok reaches MILLIONS AND MILLIONS of EVERYDAY people who are ASLEEP and will NEVER find us here in the Truth Movement on Twitter / Telegram / Truth Social because they aren't looking for the Truth until they become subjected to it and they'll NEVER have a Twitter/𝕏 account UNTIL they "wake up" and decide NOTHING else in Life matters except joining us in the fight to eradicate this evil we're up against. Example: Said "asleep" citizens is just on lunch break at work or laying in bed at night casually scrolling through TikTok videos when suddenly they swipe into a video of Bill Gates doing a Ted-Talk talking about the world being too overpopulated and that he can "fix that" to reduce the world population through vaccines and reproductive services. Which causes the viewer's inner monologue to say, "What the HELL did this Gates dude just say?!" They then "LIKE" the video and the UNIQUE TikTok algorithm starts putting SIMILAR CONTENT into their feed consisting of Truth bombs they've never seen and didn't even know they were supposed to be looking for. Before they know it, they're accidentally swiping into piles and piles of Red-Pills they weren't even looking for, leading them into a deep inner-standing of government corruption, Big Pharma evil, occulted metaphysics related to biology worshipped by the elites and many other deep rabbit holes. TikTok is the Chicago bus stop with the ability to reach passer-by's casually walking and as a result, MILLIONS are being subjected to our information and becoming activated to demand change to a system they didn't realize they were enslaved and chained to and our satanic government creating and releasing Covid-19 shut everything down and lock everyone inside activated MILLIONS. Welcome to the Great Awakening. It's a beautiful event unfolding for our species. Watch what happens next.

This is why TikTok was banned JUST before President Trump's inauguration. Incoming FBI Director Kash Patel said the FBI covered up ALL evidence pertaining to Jeffrey Epstein's client list. Which would mean that one DAY ONE of Kash being sworn in with President Trump, Kash will have direct access to ALL of it. He also stated President Trump should RELEASE the evidence (list) on DAY ONE of his Presidency. It's ABSOLUTELY NO COINCIDENCE our government fought like hell to BAN TIKTOK one day prior. Since 2017, Anons HERE worked tirelessly for 12+ hours a day, 7 days a week on Twitter to thread original open-source research and showing just how corrupt our government truly has been, dating back to its conception, hijacked by a 3,000+ year old satan worshipping cannibalistic death cult. In 2019 when Fauci's / ChYna's Covid-19 Bioweapon pLandemic was released, bored TikTok influencers under covid lockdowns were taking note of our viral Twitter threads and what we were doing here on the public stage as well as on Telegram after the TwitLer purges. The Truth movement we were birthing on the public stage spread to TikToka nd Instagram. Those influencers who were scrolling Twitter, started taking our research and uniquely compiled and written viral threads and turning our digs into video form for their TikTok audiences who had NO IDEA The Great Awakening was happening here on this platform. TikTok reaches MILLIONS AND MILLIONS of EVERYDAY people who are ASLEEP and will NEVER find us here in the Truth Movement on Twitter / Telegram / Truth Social because they aren't looking for the Truth until they become subjected to it and they'll NEVER have a Twitter/𝕏 account UNTIL they "wake up" and decide NOTHING else in Life matters except joining us in the fight to eradicate this evil we're up against. Example: Said "asleep" citizens is just on lunch break at work or laying in bed at night casually scrolling through TikTok videos when suddenly they swipe into a video of Bill Gates doing a Ted-Talk talking about the world being too overpopulated and that he can "fix that" to reduce the world population through vaccines and reproductive services. Which causes the viewer's inner monologue to say, "What the HELL did this Gates dude just say?!" They then "LIKE" the video and the UNIQUE TikTok algorithm starts putting SIMILAR CONTENT into their feed consisting of Truth bombs they've never seen and didn't even know they were supposed to be looking for. Before they know it, they're accidentally swiping into piles and piles of Red-Pills they weren't even looking for, leading them into a deep inner-standing of government corruption, Big Pharma evil, occulted metaphysics related to biology worshipped by the elites and many other deep rabbit holes. TikTok is the Chicago bus stop with the ability to reach passer-by's casually walking and as a result, MILLIONS are being subjected to our information and becoming activated to demand change to a system they didn't realize they were enslaved and chained to and our satanic government creating and releasing Covid-19 shut everything down and lock everyone inside activated MILLIONS. Welcome to the Great Awakening. It's a beautiful event unfolding for our species. Watch what happens next.

Bridgett Fertig

592,747 görüntüleme • 1 yıl önce

List of Tornado in Tamil Nadu in last 15 years, we stand that Yesterday event in Thoothukudi was indeed a Tornado. 1. Chennai (Uthandi) September 12, 2013 (1st Photo enclosed) 2. Sankarankoil in Tirunelveli November 18, 2015 3. Nazareth in Thoothukudi October 26, 2016 4. Thoothukudi on June 21, 2026 (yesterday event, 2nd photo enclosed) In 2013, it was hard to see whether the funnel cloud touched the ground. But IMD officials confirmed that it was Tornado after thorough analysis. This time, IMD has stated that the Thoothukudi event of June 2026 was not a tornado. However, instead of undertaking a detailed investigation into why such an unusual phenomenon occurred and whether similar events could become more frequent in the future, the matter appears to have been closed rather hastily. There are compelling reasons why the Thoothukudi event warrants closer scientific scrutiny. What makes the event noteworthy is the combination of: • A visible funnel cloud/vortex; • Reported injuries (6 members of the public) • Structural damage and uprooted trees see the video - • Occurrence beneath an active thunderstorm. Taken together, these characteristics are consistent with features commonly associated with weak tornadoes or landspouts. While the final classification should be based on detailed meteorological and damage assessments, the available evidence suggests that the event deserves a comprehensive post event study rather than a summary dismissal. The damage patterns visible in the photographs and videos shared through the links, together with eyewitness accounts, appear to indicate that the rotating funnel extended from the cloud base to the ground. The visual evidence suggests a continuous connection between the cloud and the surface, accompanied by localized damage along its path. Attention should be given to understanding why such tornado like phenomena have been observed repeatedly in Tamil Nadu over the past decade and whether changing atmospheric and oceanic conditions are making them more likely.

List of Tornado in Tamil Nadu in last 15 years, we stand that Yesterday event in Thoothukudi was indeed a Tornado. 1. Chennai (Uthandi) September 12, 2013 (1st Photo enclosed) 2. Sankarankoil in Tirunelveli November 18, 2015 3. Nazareth in Thoothukudi October 26, 2016 4. Thoothukudi on June 21, 2026 (yesterday event, 2nd photo enclosed) In 2013, it was hard to see whether the funnel cloud touched the ground. But IMD officials confirmed that it was Tornado after thorough analysis. This time, IMD has stated that the Thoothukudi event of June 2026 was not a tornado. However, instead of undertaking a detailed investigation into why such an unusual phenomenon occurred and whether similar events could become more frequent in the future, the matter appears to have been closed rather hastily. There are compelling reasons why the Thoothukudi event warrants closer scientific scrutiny. What makes the event noteworthy is the combination of: • A visible funnel cloud/vortex; • Reported injuries (6 members of the public) • Structural damage and uprooted trees see the video - • Occurrence beneath an active thunderstorm. Taken together, these characteristics are consistent with features commonly associated with weak tornadoes or landspouts. While the final classification should be based on detailed meteorological and damage assessments, the available evidence suggests that the event deserves a comprehensive post event study rather than a summary dismissal. The damage patterns visible in the photographs and videos shared through the links, together with eyewitness accounts, appear to indicate that the rotating funnel extended from the cloud base to the ground. The visual evidence suggests a continuous connection between the cloud and the surface, accompanied by localized damage along its path. Attention should be given to understanding why such tornado like phenomena have been observed repeatedly in Tamil Nadu over the past decade and whether changing atmospheric and oceanic conditions are making them more likely.

Tamil Nadu Weatherman

58,400 görüntüleme • 2 ay önce

I don't know anyone who is as consistently ahead of culture than Trevor McFedries. I talked to Trev🙃r about culture, markets, technology, curiosity, why selling out is punk now, and why creative people should be rich. Trevor has lived many lives: touring DJ who produced a top 10 album, co-creator of lil miquela, founder of Friends With Benefits... among many others (go watch the last 10 seconds of KATY PERRY's I Kissed a Girl music video). Today, he's the founder of new co runner.rodeo and is 1/2 of electronic dance duo SofTT. He also has a fantastic nose for weird, bridges high and low status worlds across culture, capital, art, and tech, and truly lives natively between the frontiers of tech and culture. We talked about: - Why the only creative people who can "opt out" of the algorithm are trust fund kids - How cultural capital has merged with financial capital - Why speculation is rational - The belief economy: from making → framing → predicting - What he learned working with Kanye for three months - Finding new subcultures in the dark corners of Telegram - Why he's long humanity despite everything Timestamps: 0:00 - Opening Highlights 1:18 - Intro to Trevor 4:12 - Thanks to Notion 5:21 - Start: Creative People Should Be Rich 12:03 - Creative Ignition, Infrastructure, and Why Selling Out is Punk 21:49 - Authenticity, Honesty, Divine Creativity, and Borrowed Nostalgia 30:15 - Low Status Games and High Culture, Cultural & Financial Capital, and Crypto 42:08 - The Belief Economy: From Making to Framing to Predicting 48:45 - Markets, Power, Consensus, and Truth 58:22 - Speculation is Rational 1:06:34 - Developing a Nose for Weird, Being Early and On Time 1:19:06 - Unfettered Cultural Spaces on the Internet 1:26:33 - FWB, Community, and Exclusivity 1:31:02 - LilMiquela, Online Storytelling and Celebrity, Touring as a Performer 1:45:41 - Softt, Music as a Way In, Music as a Business 1:52:45 - Culture & Business 1:54:38 - Kanye 2:06:20 - Optimism, The Next Generation, Parenting, The Stuff that Counts, and Cerulean Available on all platforms now.

I don't know anyone who is as consistently ahead of culture than Trevor McFedries. I talked to Trev🙃r about culture, markets, technology, curiosity, why selling out is punk now, and why creative people should be rich. Trevor has lived many lives: touring DJ who produced a top 10 album, co-creator of lil miquela, founder of Friends With Benefits... among many others (go watch the last 10 seconds of KATY PERRY's I Kissed a Girl music video). Today, he's the founder of new co runner.rodeo and is 1/2 of electronic dance duo SofTT. He also has a fantastic nose for weird, bridges high and low status worlds across culture, capital, art, and tech, and truly lives natively between the frontiers of tech and culture. We talked about: - Why the only creative people who can "opt out" of the algorithm are trust fund kids - How cultural capital has merged with financial capital - Why speculation is rational - The belief economy: from making → framing → predicting - What he learned working with Kanye for three months - Finding new subcultures in the dark corners of Telegram - Why he's long humanity despite everything Timestamps: 0:00 - Opening Highlights 1:18 - Intro to Trevor 4:12 - Thanks to Notion 5:21 - Start: Creative People Should Be Rich 12:03 - Creative Ignition, Infrastructure, and Why Selling Out is Punk 21:49 - Authenticity, Honesty, Divine Creativity, and Borrowed Nostalgia 30:15 - Low Status Games and High Culture, Cultural & Financial Capital, and Crypto 42:08 - The Belief Economy: From Making to Framing to Predicting 48:45 - Markets, Power, Consensus, and Truth 58:22 - Speculation is Rational 1:06:34 - Developing a Nose for Weird, Being Early and On Time 1:19:06 - Unfettered Cultural Spaces on the Internet 1:26:33 - FWB, Community, and Exclusivity 1:31:02 - LilMiquela, Online Storytelling and Celebrity, Touring as a Performer 1:45:41 - Softt, Music as a Way In, Music as a Business 1:52:45 - Culture & Business 1:54:38 - Kanye 2:06:20 - Optimism, The Next Generation, Parenting, The Stuff that Counts, and Cerulean Available on all platforms now.

Jackson Dahl

40,863 görüntüleme • 7 ay önce

HOW TO MAKE $50K/MONTH SELLING MANAGED AI AGENTS (FULL COURSE) The model: sell managed AI agents to businesses for $5K/month each. You handle the infrastructure, they get an employee that never sleeps. 10 clients puts you at $50K MRR with 85%+ margins, run entirely by you and a fleet of agents. Nick Vasilescu is doing exactly this, and he came on the pod to walk through the whole playbook. Here's what I learned: 1. The arbitrage is that nobody knows this is possible. 99% of business owners are still asking ChatGPT what the weather is. One working agent hooks them on the spot. 2. Sell abundance. Unlimited agents, unlimited infrastructure. They don't care what an MCP is, they care that their problem is gone. 3. Don't niche too early. Say yes to everyone and let the market pull you. You find the niche by doing reps, not guessing. 4. Paid audit into managed service. Charge $1K to map every automation opportunity, then credit it toward month one. Qualifies the lead, makes the upsell a no-brainer. 5. First call, don't sell. Record it, map the workflow tip to tail, find the automation with the most value and least effort. Start there. 6. The stack is Hermes + Composio + Orgo. Composio connects all their apps in one click. Orgo spins up a working Hermes agent in 26 seconds. 7. Productize with a golden snapshot. Build one perfect agent, clone it, and every copy comes over one for one with auth intact. 8. Turn client call transcripts into skills in 10 minutes. Feed the recording to Claude Code, write the skill, port it to the client's agent via Orgo MCP. 9. Watchdogs make you look elite. Get alerted before the client notices anything broke. "Already fixed it" is why they keep paying you. 10. You become their guy. You drive more outcomes than their own employees, they credit every win to you, and churn drops to almost nothing. His 2 key takeaways: 1. Bet on cost going to zero. They launched unlimited tokens when it was barely profitable because they knew they'd capture the spread. Build for where the puck is going. 2. One client every six weeks gets you to $600K a year. The model isn't hard, it's just unevenly executed. That's the entire opportunity. Nick is crushing this model and we had a blast diving deep on how you can do the same. Go follow Nick Vasilescu Full video below. (Also available on the Build With AI podcast wherever you get your pods)

HOW TO MAKE $50K/MONTH SELLING MANAGED AI AGENTS (FULL COURSE) The model: sell managed AI agents to businesses for $5K/month each. You handle the infrastructure, they get an employee that never sleeps. 10 clients puts you at $50K MRR with 85%+ margins, run entirely by you and a fleet of agents. Nick Vasilescu is doing exactly this, and he came on the pod to walk through the whole playbook. Here's what I learned: 1. The arbitrage is that nobody knows this is possible. 99% of business owners are still asking ChatGPT what the weather is. One working agent hooks them on the spot. 2. Sell abundance. Unlimited agents, unlimited infrastructure. They don't care what an MCP is, they care that their problem is gone. 3. Don't niche too early. Say yes to everyone and let the market pull you. You find the niche by doing reps, not guessing. 4. Paid audit into managed service. Charge $1K to map every automation opportunity, then credit it toward month one. Qualifies the lead, makes the upsell a no-brainer. 5. First call, don't sell. Record it, map the workflow tip to tail, find the automation with the most value and least effort. Start there. 6. The stack is Hermes + Composio + Orgo. Composio connects all their apps in one click. Orgo spins up a working Hermes agent in 26 seconds. 7. Productize with a golden snapshot. Build one perfect agent, clone it, and every copy comes over one for one with auth intact. 8. Turn client call transcripts into skills in 10 minutes. Feed the recording to Claude Code, write the skill, port it to the client's agent via Orgo MCP. 9. Watchdogs make you look elite. Get alerted before the client notices anything broke. "Already fixed it" is why they keep paying you. 10. You become their guy. You drive more outcomes than their own employees, they credit every win to you, and churn drops to almost nothing. His 2 key takeaways: 1. Bet on cost going to zero. They launched unlimited tokens when it was barely profitable because they knew they'd capture the spread. Build for where the puck is going. 2. One client every six weeks gets you to $600K a year. The model isn't hard, it's just unevenly executed. That's the entire opportunity. Nick is crushing this model and we had a blast diving deep on how you can do the same. Go follow Nick Vasilescu Full video below. (Also available on the Build With AI podcast wherever you get your pods)

Corey Ganim

85,723 görüntüleme • 2 ay önce

No one seemed to want to answer the important question regarding the M&S in Colchester. Are there any spaces just for men or just for women or are they all "gender neutral"/Mixed Sex? So I rang them. The woman in the recent video said they were "breaking the law". They aren't. Marks and Spencer told me that they have 6 changing spaces LOCATED within the Men's dept. 6 spaces LOCATED within the women's department. All 12 are mixed sex and available to everyone. They are not marked as single sex spaces because they aren't single sex. Audio recording below. I did not give Yvonne the customer services representative a hard time because I was not making a complaint, I was getting clarification and info about the store's changing provision and she is not responsible for producing Marks and Spencer policy. The company policy dictating this mixed sex changing arrangement throughout the store is legal. This is the entire problem. Women have been misled to think single-sex changing spaces have now been returned to them. That would be a lie. Marks and Spencer and others can continue to provide spaces unacceptable and unsafe to women. They can do it within the remit of the Equality Act. For women to be safe there needs to be a change to the law which insists on women having single sex space to change or go to the toilet. That has not been achieved by any court ruling or guidance around the Equality Act and GC groups who mostly applauded the recently released 'Code of Practice' know this because they are stuffed full of lawyers. The man in the video may have terrible customer service skills, he may even be prejudiced against women with GC views, but the policy is legal. Grassroots activism on behalf of women might eventually force a change from providers. It is probably all that could, because the Equality Act remains rigidly against us. Yet the grassroots have previously been frowned upon and sneered at for our shouty ways while the GC Suits "handle everything professionally". The woman in the store accused a man of "breaking the law" which he wasn't. Now we have one of the Sex Matters lawyers exposing that employee's details online. What a mess.

No one seemed to want to answer the important question regarding the M&S in Colchester. Are there any spaces just for men or just for women or are they all "gender neutral"/Mixed Sex? So I rang them. The woman in the recent video said they were "breaking the law". They aren't. Marks and Spencer told me that they have 6 changing spaces LOCATED within the Men's dept. 6 spaces LOCATED within the women's department. All 12 are mixed sex and available to everyone. They are not marked as single sex spaces because they aren't single sex. Audio recording below. I did not give Yvonne the customer services representative a hard time because I was not making a complaint, I was getting clarification and info about the store's changing provision and she is not responsible for producing Marks and Spencer policy. The company policy dictating this mixed sex changing arrangement throughout the store is legal. This is the entire problem. Women have been misled to think single-sex changing spaces have now been returned to them. That would be a lie. Marks and Spencer and others can continue to provide spaces unacceptable and unsafe to women. They can do it within the remit of the Equality Act. For women to be safe there needs to be a change to the law which insists on women having single sex space to change or go to the toilet. That has not been achieved by any court ruling or guidance around the Equality Act and GC groups who mostly applauded the recently released 'Code of Practice' know this because they are stuffed full of lawyers. The man in the video may have terrible customer service skills, he may even be prejudiced against women with GC views, but the policy is legal. Grassroots activism on behalf of women might eventually force a change from providers. It is probably all that could, because the Equality Act remains rigidly against us. Yet the grassroots have previously been frowned upon and sneered at for our shouty ways while the GC Suits "handle everything professionally". The woman in the store accused a man of "breaking the law" which he wasn't. Now we have one of the Sex Matters lawyers exposing that employee's details online. What a mess.

Jean Hatchet

93,624 görüntüleme • 3 ay önce

This guy sells AI employees to small businesses. He's a non-technical designer with no audience, spends $0 on ads, has no tech background. Yet he's still done 21 agent setups in 6 months, almost all from referrals. His model: install one AI agent as a digital employee, then get paid monthly to manage it and coach the owner. Setup fee plus a per-agent monthly rate. Phil came on the Build With AI pod to walk us through the whole playbook. Here's what I learned: 1. The product is the coaching, not the agent. Owners treat AI like Google. You get paid to manage it so they never have to. 2. Raise your price every yes. $500 setups became $1,000. Now he's targeting $2,000 setups plus $1,000/month per agent. 3. Give the agent a value ledger. It logs every task and sends a weekly ROI report. One client's first week: 63 hours saved, $6,300 in value. 4. Put yourself in the group chat. Telegram group with Phil, the client, and the agent. The client learns by watching him talk to it. 5. The agents handle real multi-step work. One prompt: find the invoice email, extract the PDF into Excel, save to Dropbox, send the link. Done in 10 minutes. 6. Uptime is a selling point. The best prospects tried agents themselves and quit when they broke. Phil fixes it before the client notices. 7. Free work is the referral engine. Friends in his small Georgia town told friends in Atlanta and Dallas. Now he has clients nationwide. 8. The pitch is one text. "I'm testing a managed agent service. Want to be a guinea pig? I'll charge you less." First client: $250/month. 9. Make the agent write to Excel, not its own markdown. A shared source of truth is the difference between a demo and a system. 10. Phil builds his agents on Orgo. $29/month gets your agent a computer with pre-built templates. Phil's agent handles the Orgo admin itself. His 2 key takeaways: 1. You only need to be one step ahead. If you've built an agent for yourself, you know more than the owner who never has. Charge from day one. 2. Visible ROI is the retention strategy. A weekly "you saved $6,300" report re-sells the retainer every single week. Phil is doing this at a level most technical people are not, and we had a blast going deep on it. Go follow Phil Full video below. (Also available on the Build With AI podcast wherever you get your pods)

This guy sells AI employees to small businesses. He's a non-technical designer with no audience, spends $0 on ads, has no tech background. Yet he's still done 21 agent setups in 6 months, almost all from referrals. His model: install one AI agent as a digital employee, then get paid monthly to manage it and coach the owner. Setup fee plus a per-agent monthly rate. Phil came on the Build With AI pod to walk us through the whole playbook. Here's what I learned: 1. The product is the coaching, not the agent. Owners treat AI like Google. You get paid to manage it so they never have to. 2. Raise your price every yes. $500 setups became $1,000. Now he's targeting $2,000 setups plus $1,000/month per agent. 3. Give the agent a value ledger. It logs every task and sends a weekly ROI report. One client's first week: 63 hours saved, $6,300 in value. 4. Put yourself in the group chat. Telegram group with Phil, the client, and the agent. The client learns by watching him talk to it. 5. The agents handle real multi-step work. One prompt: find the invoice email, extract the PDF into Excel, save to Dropbox, send the link. Done in 10 minutes. 6. Uptime is a selling point. The best prospects tried agents themselves and quit when they broke. Phil fixes it before the client notices. 7. Free work is the referral engine. Friends in his small Georgia town told friends in Atlanta and Dallas. Now he has clients nationwide. 8. The pitch is one text. "I'm testing a managed agent service. Want to be a guinea pig? I'll charge you less." First client: $250/month. 9. Make the agent write to Excel, not its own markdown. A shared source of truth is the difference between a demo and a system. 10. Phil builds his agents on Orgo. $29/month gets your agent a computer with pre-built templates. Phil's agent handles the Orgo admin itself. His 2 key takeaways: 1. You only need to be one step ahead. If you've built an agent for yourself, you know more than the owner who never has. Charge from day one. 2. Visible ROI is the retention strategy. A weekly "you saved $6,300" report re-sells the retainer every single week. Phil is doing this at a level most technical people are not, and we had a blast going deep on it. Go follow Phil Full video below. (Also available on the Build With AI podcast wherever you get your pods)

Corey Ganim

224,702 görüntüleme • 27 gün önce

HERMES AGENT HAS 5 SYSTEMS RUNNING UNDER THE HOOD. UNDERSTAND THEM AND YOU USE THE AGENT 10X BETTER. In this video Alejandro AO 🤗 explained: 1. THE AGENT LOOP every message triggers the same cycle: → you send a message → Hermes builds context (SOUL.md + memory.md + user.md + skills + tools + message history) → sends everything to the LLM → LLM decides: call a tool or respond → if tool call: execute, return result, loop back → if response: deliver to you → after response: memory update (agent checks if anything is worth remembering, writes to memory.md or user.md) this loop is why Hermes gets better over time. the memory update after every response means the agent learns from every conversation. 2. CONTEXT ASSEMBLY what the LLM sees on every turn: → SOUL.md (your agent's personality and rules) → memory.md (facts the agent learned over time) → user.md (facts about you, auto-updated) → AGENTS.md and .hermes.md (project context files) → skill descriptions (loaded on demand) → tool schemas (available actions) → message history (current conversation) if SOUL.md is empty, Hermes falls back to a default system prompt. write your own SOUL.md and the agent becomes yours, not generic. CONTEXT COMPRESSION: conversations hit context limits. Hermes handles this at two checkpoints: preflight: before each turn. if conversation exceeds 50% of context window, compression fires. older messages get summarized. last 20 messages stay intact (protect_last_n). gateway auto-compression: between turns. fires at 85%. more aggressive. prevents API errors before the agent even starts processing your message. after compression, a new session lineage ID is generated. the agent can trace back to the original conversation through SQLite. three things break prompt cache: switching models mid-session, changing memory files, or changing context files. 3. THE GATEWAY the system that keeps Hermes reachable on 27+ messaging platforms. an async loop runs continuously. listens for incoming messages from Telegram, Discord, Slack, WhatsApp, email, SMS, and every other adapter. when a message arrives: → gateway identifies which session it belongs to → queries SQLite for the full message history (session ID = platform prefix + chat ID) → builds the context from scratch → sends everything into the agent loop → delivers the response back to the platform the gateway also runs the session manager. when you send a message while the agent is busy: → default: queued for next turn → /steer: injected without interrupting → /interrupt: stops current work without the gateway, Hermes is a CLI tool. with the gateway, Hermes is an always-on agent you reach from your phone. 4. MEMORY (THREE LAYERS) LAYER 1 — MARKDOWN FILES SOUL.md (identity), memory.md (learned facts), user.md (facts about you). injected into context after the system prompt. updated by the agent after every response. LAYER 2 — SQLITE full transcripts of every session stored locally. FTS5 full-text search across all past conversations. session lineage tracking across compressions. the agent can recall what you discussed weeks ago using /recall or session search. LAYER 3 — EXTERNAL PROVIDERS (optional) 8 supported providers: Mem0, SuperMemory, Honcho, Zep, and more. each works differently (semantic search, LLM extraction, similarity matching). queried after the first message in each session. the agent processes your topic first, then checks external memory for related context from past conversations. not enabled by default. enable for significantly better long-term recall. 5. CRON ENGINE a loop inside the gateway ticks every 60 seconds. each tick checks ~/.hermes/cron/jobs.json for scheduled tasks. if a job is due: → fresh session (no chat history, no memory pollution) → execute the prompt with assigned tools → store the run output as markdown in ~/.hermes/cron/output/[job-id]/ → deliver result to your home messaging platform cron does NOT use the send_message tool. delivery happens at the system level, not the agent level. a cron session cannot create more cron jobs. prevents runaway loops. WHY THIS MATTERS: the agent loop teaches it. the context assembly focuses it. the gateway reaches it. the memory remembers it. the cron engine automates it. five systems. one agent. understanding how they connect changes how you configure every level. full 15 levels breakdown in the article 👇

HERMES AGENT HAS 5 SYSTEMS RUNNING UNDER THE HOOD. UNDERSTAND THEM AND YOU USE THE AGENT 10X BETTER. In this video Alejandro AO 🤗 explained: 1. THE AGENT LOOP every message triggers the same cycle: → you send a message → Hermes builds context (SOUL.md + memory.md + user.md + skills + tools + message history) → sends everything to the LLM → LLM decides: call a tool or respond → if tool call: execute, return result, loop back → if response: deliver to you → after response: memory update (agent checks if anything is worth remembering, writes to memory.md or user.md) this loop is why Hermes gets better over time. the memory update after every response means the agent learns from every conversation. 2. CONTEXT ASSEMBLY what the LLM sees on every turn: → SOUL.md (your agent's personality and rules) → memory.md (facts the agent learned over time) → user.md (facts about you, auto-updated) → AGENTS.md and .hermes.md (project context files) → skill descriptions (loaded on demand) → tool schemas (available actions) → message history (current conversation) if SOUL.md is empty, Hermes falls back to a default system prompt. write your own SOUL.md and the agent becomes yours, not generic. CONTEXT COMPRESSION: conversations hit context limits. Hermes handles this at two checkpoints: preflight: before each turn. if conversation exceeds 50% of context window, compression fires. older messages get summarized. last 20 messages stay intact (protect_last_n). gateway auto-compression: between turns. fires at 85%. more aggressive. prevents API errors before the agent even starts processing your message. after compression, a new session lineage ID is generated. the agent can trace back to the original conversation through SQLite. three things break prompt cache: switching models mid-session, changing memory files, or changing context files. 3. THE GATEWAY the system that keeps Hermes reachable on 27+ messaging platforms. an async loop runs continuously. listens for incoming messages from Telegram, Discord, Slack, WhatsApp, email, SMS, and every other adapter. when a message arrives: → gateway identifies which session it belongs to → queries SQLite for the full message history (session ID = platform prefix + chat ID) → builds the context from scratch → sends everything into the agent loop → delivers the response back to the platform the gateway also runs the session manager. when you send a message while the agent is busy: → default: queued for next turn → /steer: injected without interrupting → /interrupt: stops current work without the gateway, Hermes is a CLI tool. with the gateway, Hermes is an always-on agent you reach from your phone. 4. MEMORY (THREE LAYERS) LAYER 1 — MARKDOWN FILES SOUL.md (identity), memory.md (learned facts), user.md (facts about you). injected into context after the system prompt. updated by the agent after every response. LAYER 2 — SQLITE full transcripts of every session stored locally. FTS5 full-text search across all past conversations. session lineage tracking across compressions. the agent can recall what you discussed weeks ago using /recall or session search. LAYER 3 — EXTERNAL PROVIDERS (optional) 8 supported providers: Mem0, SuperMemory, Honcho, Zep, and more. each works differently (semantic search, LLM extraction, similarity matching). queried after the first message in each session. the agent processes your topic first, then checks external memory for related context from past conversations. not enabled by default. enable for significantly better long-term recall. 5. CRON ENGINE a loop inside the gateway ticks every 60 seconds. each tick checks ~/.hermes/cron/jobs.json for scheduled tasks. if a job is due: → fresh session (no chat history, no memory pollution) → execute the prompt with assigned tools → store the run output as markdown in ~/.hermes/cron/output/[job-id]/ → deliver result to your home messaging platform cron does NOT use the send_message tool. delivery happens at the system level, not the agent level. a cron session cannot create more cron jobs. prevents runaway loops. WHY THIS MATTERS: the agent loop teaches it. the context assembly focuses it. the gateway reaches it. the memory remembers it. the cron engine automates it. five systems. one agent. understanding how they connect changes how you configure every level. full 15 levels breakdown in the article 👇

YanXbt

51,860 görüntüleme • 2 ay önce