正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Last night I tried something wild: Claude Code + GLM-4.5. I typed one request in my terminal → “build me a Next.js + SQLite CRM.” Minutes later, I had: ⚡ Full Next.js app scaffolded ⚡ Prisma wired + DB seeded ⚡ Git commits + pushes handled for me Cost?... show more

Tech & AI Hub

12,825 subscribers

45,880 次观看 • 10 个月前 •via X (Twitter)

科学技术教育财经

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Coding just leveled up for me ⚡ Hooked Claude Code into GLM-4.5 → suddenly it’s like pair-programming with a senior dev: 👉 Bootstrapped a full Next.js CRM in minutes 👉 Auto-wired SQLite + Prisma with zero friction 👉 Guided me through git commits & pushes hands-free The kicker? The whole build cost under $1. 🤯 And now GLM Coding Plans launch with promo pricing: • Lite — $3/mo • Pro — $15/mo (40–60% faster + image/video + web search) • MAX — $30/mo (all features unlocked 🚀) Premium coding speed, open-source pricing. This combo might be the future of dev workflows. 👉

Coding just leveled up for me ⚡ Hooked Claude Code into GLM-4.5 → suddenly it’s like pair-programming with a senior dev: 👉 Bootstrapped a full Next.js CRM in minutes 👉 Auto-wired SQLite + Prisma with zero friction 👉 Guided me through git commits & pushes hands-free The kicker? The whole build cost under $1. 🤯 And now GLM Coding Plans launch with promo pricing: • Lite — $3/mo • Pro — $15/mo (40–60% faster + image/video + web search) • MAX — $30/mo (all features unlocked 🚀) Premium coding speed, open-source pricing. This combo might be the future of dev workflows. 👉

Alif Hossain

17,991 次观看 • 10 个月前

I think I just found the best value way to code with AI. Tried Claude Code + GLM-4.5 and it blew me away: I benchmarked with my usual Next.js CRM app test → it bootstrapped a full project w/ SQLite + Prisma in minutes. Speed feels close to Sonnet-4. No weird stalls, just smooth iterations. Cost me $0.50 total for the whole app build. And now dropped new plans: → Lite $3/mo → cheapest entry point → Pro $15/mo → 40–60% faster + image/video understanding → Max $30/mo → adds built-in web search → Flexible billing (monthly, quarterly, annual) Special offer: My link gives you an extra 10% OFF →Subscribe here : Honestly, it’s become my go-to coding AI.

I think I just found the best value way to code with AI. Tried Claude Code + GLM-4.5 and it blew me away: I benchmarked with my usual Next.js CRM app test → it bootstrapped a full project w/ SQLite + Prisma in minutes. Speed feels close to Sonnet-4. No weird stalls, just smooth iterations. Cost me $0.50 total for the whole app build. And now dropped new plans: → Lite $3/mo → cheapest entry point → Pro $15/mo → 40–60% faster + image/video understanding → Max $30/mo → adds built-in web search → Flexible billing (monthly, quarterly, annual) Special offer: My link gives you an extra 10% OFF →Subscribe here : Honestly, it’s become my go-to coding AI.

Darshal Jaitwar

29,545 次观看 • 10 个月前

What if you could build production-ready apps in minutes with the skill of a senior engineer… for just $3/month? I plugged GLM-4.5 into my Python platform, and within minutes, it began shipping production-ready apps at a level that typically requires an entire development team. Here’s what it built instantly: ✅ A complete Next.js project with authentication and dashboards ✅ SQLite + Prisma with seeded data ✅ Professional, structured git commits ✅ Clear explanations of senior-level refactors You’ve been invited to join the GLM Coding Plan! Enjoy full support for Claude Code, Cline, and 10+ top coding tools — starting at just $3/month. Subscribe now and grab the limited-time deal! Link： The AI coding revolution is here today. The builders who adopt it first will lead tomorrow.

What if you could build production-ready apps in minutes with the skill of a senior engineer… for just $3/month? I plugged GLM-4.5 into my Python platform, and within minutes, it began shipping production-ready apps at a level that typically requires an entire development team. Here’s what it built instantly: ✅ A complete Next.js project with authentication and dashboards ✅ SQLite + Prisma with seeded data ✅ Professional, structured git commits ✅ Clear explanations of senior-level refactors You’ve been invited to join the GLM Coding Plan! Enjoy full support for Claude Code, Cline, and 10+ top coding tools — starting at just $3/month. Subscribe now and grab the limited-time deal! Link： The AI coding revolution is here today. The builders who adopt it first will lead tomorrow.

Vipin Gautam (Viipin I Gautam)

88,964 次观看 • 10 个月前

I think I discovered the cheapest way to code with AI 😁 I tried GLM 4.5 on Claude Code and I'm really amazed how good this model is! I usually test with my nextjs crm app benchmark so I asked it to do that. Prompt "create a nextjs app which is a crm app. use sqlite for the database and use api routes to manage connecting to the database from the frontend" My observations - Generation feels like Sonnet 4 intelligence - Speed is great - It used create-next-app so it bootstrapped nextjs v15.5.2 - It created a sqlite database and used Prisma ORM and helped me easily add seed data - I needed a few prompts to iron out minor issues but all's good. It didn't struggle or got stuck. - Spent $0.50 for this app. Could be way cheaper with the Z.ai sub plans After trying, I can say GLM 4.5 model is up there as the best open source model for coding. Will continue using it and update here. So far so good! P.S. DM me if you want my referral link, otherwise just check Not dropping the link here so it doesn’t look like I’m hyping it. Here's a video of the experience 👇(sped up a bit)

I think I discovered the cheapest way to code with AI 😁 I tried GLM 4.5 on Claude Code and I'm really amazed how good this model is! I usually test with my nextjs crm app benchmark so I asked it to do that. Prompt "create a nextjs app which is a crm app. use sqlite for the database and use api routes to manage connecting to the database from the frontend" My observations - Generation feels like Sonnet 4 intelligence - Speed is great - It used create-next-app so it bootstrapped nextjs v15.5.2 - It created a sqlite database and used Prisma ORM and helped me easily add seed data - I needed a few prompts to iron out minor issues but all's good. It didn't struggle or got stuck. - Spent $0.50 for this app. Could be way cheaper with the Z.ai sub plans After trying, I can say GLM 4.5 model is up there as the best open source model for coding. Will continue using it and update here. So far so good! P.S. DM me if you want my referral link, otherwise just check Not dropping the link here so it doesn’t look like I’m hyping it. Here's a video of the experience 👇(sped up a bit)

Melvin Vivas

45,749 次观看 • 10 个月前

Crazy... I just found a super cheap way to code with AI Tried GLM 4.5 on Claude Code and I’m really impressed! Prompt: “create an interactive python app where users can track, manage or analyze data” And, It came up with: • Dashboard - a clean interface to see all your data at a glance • Datasets - manage multiple collections of data easily • Data entries - add, edit, and organize your records without hassle • Analysis - get insights and summaries directly from your data What I observed: Everything worked smoothly, GLM 4.5 is definitely one of the best open-source models for coding, I’ll keep using it. Check it out now: And the best part: super affordable coding plans! • Lite - $3/month (promo). ~120 prompts every 5 hours. Works with Claude Code, Roo Code, Cline, Kilo Code, and more. • Pro - $15/month (promo). 5× more usage than Lite. Faster. Includes image/video tools and web search. • Max - $30/month (promo). 4× more usage than Pro. Guaranteed performance. Early access to new features. Bonus - Use my referral link to get an extra 10% off on top of these promo prices! Video demo 👇

Crazy... I just found a super cheap way to code with AI Tried GLM 4.5 on Claude Code and I’m really impressed! Prompt: “create an interactive python app where users can track, manage or analyze data” And, It came up with: • Dashboard - a clean interface to see all your data at a glance • Datasets - manage multiple collections of data easily • Data entries - add, edit, and organize your records without hassle • Analysis - get insights and summaries directly from your data What I observed: Everything worked smoothly, GLM 4.5 is definitely one of the best open-source models for coding, I’ll keep using it. Check it out now: And the best part: super affordable coding plans! • Lite - $3/month (promo). ~120 prompts every 5 hours. Works with Claude Code, Roo Code, Cline, Kilo Code, and more. • Pro - $15/month (promo). 5× more usage than Lite. Faster. Includes image/video tools and web search. • Max - $30/month (promo). 4× more usage than Pro. Guaranteed performance. Early access to new features. Bonus - Use my referral link to get an extra 10% off on top of these promo prices! Video demo 👇

Chidanand Tripathi

83,854 次观看 • 10 个月前

I tested Claude Code on a fresh account - 1,500 lines of HTML cost me 50% of my window. Full video and summary is here.. I just ran a recorded test on Claude Code with a fresh account (Pro, not Max - my main account was 20x Max) , and the result is honestly insane. The task was trivial: create 3 simple demo HTML pages, around 500 lines each. Roughly 1,500 lines of code total. Nothing massive. Nothing enterprise-grade. Nothing that should meaningfully stress a premium coding product. And yet Claude Code burned through 40% of my 5-hour window almost immediately. I ran the exact same test with Codex, and it consumed only 2%. Then it got even worse: after the session ended, I did absolutely nothing for 15 minutes, and Claude still ate another 10%. Total: 50% of the 5-hour window gone for a tiny HTML demo. My weekly usage had already started at 2% before I even really used it, and after this tiny test it jumped to 8%. Now let us be generous and assume this entire run used around 30k tokens total. If 30k tokens represents 10% of weekly usage, that implies around 300k tokens per week. That is roughly 1.2M-1.3M tokens per month, and even if you round up aggressively, you are still in the 1.5M token range. Using the Sonnet 4.6 pricing you list: $3 per 1M input tokens $15 per 1M output tokens How exactly is this supposed to make sense for a paid coding product? Because from the user side, this no longer looks like "premium usage protection." It looks like a quota system that is either wildly inefficient, badly broken, or being accounted in a way users are not being told about. And that is before I even get to my main account: my $200 Max plan now dies in a single day. Just a few months ago, similar or heavier usage would last me about a week. So no, I do not buy the "maybe you just used it more" excuse anymore. Something is clearly broken in Claude Code. Either token accounting is broken, context handling is broken, background consumption is broken, or all three. Alex Albert is this really the experience you want users to pay for? Just watch the video. I tried to be very transparent and clear for your team! I was fan of Claude but just disappointed! And if you want, send me the detailed token accounting for this session and let us inspect it together publicly. Because from where I am standing, this is no longer a small pricing annoyance. It looks like something seriously wrong is happening, and users deserve a real explanation.

I tested Claude Code on a fresh account - 1,500 lines of HTML cost me 50% of my window. Full video and summary is here.. I just ran a recorded test on Claude Code with a fresh account (Pro, not Max - my main account was 20x Max) , and the result is honestly insane. The task was trivial: create 3 simple demo HTML pages, around 500 lines each. Roughly 1,500 lines of code total. Nothing massive. Nothing enterprise-grade. Nothing that should meaningfully stress a premium coding product. And yet Claude Code burned through 40% of my 5-hour window almost immediately. I ran the exact same test with Codex, and it consumed only 2%. Then it got even worse: after the session ended, I did absolutely nothing for 15 minutes, and Claude still ate another 10%. Total: 50% of the 5-hour window gone for a tiny HTML demo. My weekly usage had already started at 2% before I even really used it, and after this tiny test it jumped to 8%. Now let us be generous and assume this entire run used around 30k tokens total. If 30k tokens represents 10% of weekly usage, that implies around 300k tokens per week. That is roughly 1.2M-1.3M tokens per month, and even if you round up aggressively, you are still in the 1.5M token range. Using the Sonnet 4.6 pricing you list: $3 per 1M input tokens $15 per 1M output tokens How exactly is this supposed to make sense for a paid coding product? Because from the user side, this no longer looks like "premium usage protection." It looks like a quota system that is either wildly inefficient, badly broken, or being accounted in a way users are not being told about. And that is before I even get to my main account: my $200 Max plan now dies in a single day. Just a few months ago, similar or heavier usage would last me about a week. So no, I do not buy the "maybe you just used it more" excuse anymore. Something is clearly broken in Claude Code. Either token accounting is broken, context handling is broken, background consumption is broken, or all three. Alex Albert is this really the experience you want users to pay for? Just watch the video. I tried to be very transparent and clear for your team! I was fan of Claude but just disappointed! And if you want, send me the detailed token accounting for this session and let us inspect it together publicly. Because from where I am standing, this is no longer a small pricing annoyance. It looks like something seriously wrong is happening, and users deserve a real explanation.

Hayrettin Tüzel

26,854 次观看 • 4 个月前

Autonomy for All: My Experience with Replit ⠕ Agent 3 🚀 If you’ve ever wished building software felt less like coding with a computer and more like collaborating with a teammate, you need to try Agent 3. I’ve been using it recently, and honestly it’s a whole new way to build. Try now: 💡 Here’s what stood out for me: ✅ It’s 10X more autonomous — I’ve had it run for up to 200 minutes straight without me touching a thing. ✅ It tests and fixes its own code in a live browser — and it’s 3X faster and 10X more cost-effective than the usual testing models. ✅ It can build other Agents & Automations — I’ve spun up Slackbots to query data, Telegram bots to track habits, and even time-triggered workflows that email me daily stock news. How it feels to use: → You describe what you want in plain language. → Agent 3 just… gets to work — building, testing, improving, and delivering. → You can even track progress live from your phone while it’s still working. This isn’t just an upgrade, it’s a leap. From idea → app → automation, Agent 3 makes it feel like you’ve got another person on your team, not just another tool. 🔗 Check out Replit Agent 3 here: If you build anything cool, I’d love to see it.

Autonomy for All: My Experience with Replit ⠕ Agent 3 🚀 If you’ve ever wished building software felt less like coding with a computer and more like collaborating with a teammate, you need to try Agent 3. I’ve been using it recently, and honestly it’s a whole new way to build. Try now: 💡 Here’s what stood out for me: ✅ It’s 10X more autonomous — I’ve had it run for up to 200 minutes straight without me touching a thing. ✅ It tests and fixes its own code in a live browser — and it’s 3X faster and 10X more cost-effective than the usual testing models. ✅ It can build other Agents & Automations — I’ve spun up Slackbots to query data, Telegram bots to track habits, and even time-triggered workflows that email me daily stock news. How it feels to use: → You describe what you want in plain language. → Agent 3 just… gets to work — building, testing, improving, and delivering. → You can even track progress live from your phone while it’s still working. This isn’t just an upgrade, it’s a leap. From idea → app → automation, Agent 3 makes it feel like you’ve got another person on your team, not just another tool. 🔗 Check out Replit Agent 3 here: If you build anything cool, I’d love to see it.

Nayeem Sheikh

28,223 次观看 • 10 个月前

$I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)$

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

194,949 次观看 • 11 个月前

I wake up fairly early and I love listening to classical Hindustani ragas to get my day going. I got inspired recently by this website called Dhuni and wanted to get some of my own favorites built into a radio station and build an interesting interface with a man slowly walking through a forest as dawn becomes day becomes evening becomes night and the dawn comes back again. Used Emergent And literally one-shotted this whole thing in less than 10 minutes. I was just 🤯. I have used the product often over the last 6-8 months as an investor but this was genuinely so well done. I tried using the same prompt on at least 3 other platforms and some essentially connected to radio stations that had Hindi music but then randomly inserted English music. Some didn't have an interface as cool, some had output that was barely understandable and needed a lot of APIs to YT. Some asked me to use curl on the terminal to download my favorite tracks as MP3s 😆 This experience just brought back to me how large an opportunity personal apps can be in the future. This exact thing would have cost me $20/mo as saas sub and would be fairly generic. This app now is exactly to my taste. The interface is exactly as I described it, the music is exactly like I want it. Just a delightful personal software I'm now waking up to every day. I am hosting it on Emergent here if you want to check it out:

I wake up fairly early and I love listening to classical Hindustani ragas to get my day going. I got inspired recently by this website called Dhuni and wanted to get some of my own favorites built into a radio station and build an interesting interface with a man slowly walking through a forest as dawn becomes day becomes evening becomes night and the dawn comes back again. Used Emergent And literally one-shotted this whole thing in less than 10 minutes. I was just 🤯. I have used the product often over the last 6-8 months as an investor but this was genuinely so well done. I tried using the same prompt on at least 3 other platforms and some essentially connected to radio stations that had Hindi music but then randomly inserted English music. Some didn't have an interface as cool, some had output that was barely understandable and needed a lot of APIs to YT. Some asked me to use curl on the terminal to download my favorite tracks as MP3s 😆 This experience just brought back to me how large an opportunity personal apps can be in the future. This exact thing would have cost me $20/mo as saas sub and would be fairly generic. This app now is exactly to my taste. The interface is exactly as I described it, the music is exactly like I want it. Just a delightful personal software I'm now waking up to every day. I am hosting it on Emergent here if you want to check it out:

Hemant Mohapatra

19,168 次观看 • 4 个月前

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 次观看 • 2 个月前

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,542 次观看 • 3 个月前

When I was 8 years old, my favorite thing in the world was making mixtapes for my Walkman from my big sister’s CDs. That evolved into Lego stop-motion videos, and later, I fell down the rabbit hole of editing Naruto anime clips to Evanescence & Linkin Park beats. Looking back, it’s obvious: Sound and Video were always the main drivers in my life. I think that obsession also led me to my true love: Motion Design. A huge shoutout to Kevin who showed me +10 years ago the world of Motion Design. And honestly, look at where we are now. Who would have thought that there would be such a massive hype around Motion Design and UI promo videos? From giants like Airbnb to the new generation of creators like sutoxoriginals. The visual standard in 2026 is insane. But there was always one part of the process that felt like a grind to me: Sound Design. I love the result, but I hated the process. I was spending 4-5 hours per project just searching for the right sound effects. "Key typing effect" "Mouse click" "Subtle Whoosh" and so on.. So, I decided to fix it. I sat down with a Dev friend and we spent the last few weekends building a native AI tool right inside After Effects. The concept is simple: SoundDesigner AI watches your video. It understands the vibe and exactly what’s happening and when its happening. It sees a clock ticking or a text appearing, and it generates the perfect sound for it in seconds, synced to the action in your timeline. I’ve been using it on my own projects for a few days now, and it’s wild. My sound design workflow went actually from 5 hours to 20 minutes. We are launching this in February (fingers crossed for the approval at aescripts+aeplugins) If you want to see where this goes and try it out yourself, drop me a DM

When I was 8 years old, my favorite thing in the world was making mixtapes for my Walkman from my big sister’s CDs. That evolved into Lego stop-motion videos, and later, I fell down the rabbit hole of editing Naruto anime clips to Evanescence & Linkin Park beats. Looking back, it’s obvious: Sound and Video were always the main drivers in my life. I think that obsession also led me to my true love: Motion Design. A huge shoutout to Kevin who showed me +10 years ago the world of Motion Design. And honestly, look at where we are now. Who would have thought that there would be such a massive hype around Motion Design and UI promo videos? From giants like Airbnb to the new generation of creators like sutoxoriginals. The visual standard in 2026 is insane. But there was always one part of the process that felt like a grind to me: Sound Design. I love the result, but I hated the process. I was spending 4-5 hours per project just searching for the right sound effects. "Key typing effect" "Mouse click" "Subtle Whoosh" and so on.. So, I decided to fix it. I sat down with a Dev friend and we spent the last few weekends building a native AI tool right inside After Effects. The concept is simple: SoundDesigner AI watches your video. It understands the vibe and exactly what’s happening and when its happening. It sees a clock ticking or a text appearing, and it generates the perfect sound for it in seconds, synced to the action in your timeline. I’ve been using it on my own projects for a few days now, and it’s wild. My sound design workflow went actually from 5 hours to 20 minutes. We are launching this in February (fingers crossed for the approval at aescripts+aeplugins) If you want to see where this goes and try it out yourself, drop me a DM

Markus Gavrilov

20,229 次观看 • 6 个月前

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

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

Yam Peleg

419,636 次观看 • 7 个月前

tired: Claude Code ports my personal website to a new framework wired: Claude Code generates a command center UI where I can execute the port! with live feedback, including a side-by-side preview of old / new site 😎 this is an example of what I call an "AI HUD" -- a "heads-up display" that gives me visibility into what's going on. i can see: - what terminal commands are running - what files are being created on disk - a live running preview of the old / new website (!) this HUD was actually my third attempt at doing this task, and I liked it the best. here's why I landed there: I wanted to move from middleman to astro for my personal site. These are both static site generators that output html, so I suspected an AI agent could do a good job with a port -- since it could compare old / new build output and try to match. Attempt 1: Agent I just had Claude Code do the port. It went pretty well. But it was hard for me to review what had happened! The git diff was dozens of new files and it was hard to tell how they mapped to the old site. I think the LLM also tried directly writing some files rather than doing deterministic copying, which felt dangerous. Attempt 2: Script I realized a better approach was to have Claude Code write a script that would do the port. The script would execute shell commands like "copy all the markdown files from this directory into this other directory in the new site". This worked much better because I could review the *process* rather than the *results*. Still, even with a nicely commented script, it felt like I was doing a lot of work to review. I wondered: how could I make it ridiculously easy to review this? Attempt 3: HUD Enter the command center! This is an entire web app that I had Claude build just for this one task. I can click buttons to run each step of the port, and watch the new website gradually materialize. It has a node server that runs on my local machine that executes commands on my filesystem and coordinates dev servers for the old/new site. And then a web UI that talks to that server to visualize terminal commands, file trees, and live running previews. It's a HUD because I feel like I can ambiently see everything that the port process is doing 🧐 Was this whole thing worth making for this one-time task? I'm not sure, maybe it was overkill 😅 But it did help me feel more confident that I understood what was going on, and total time was still less than it would have taken me to do the whole port by hand! One way to look at this experience is: "AI can put absurd amounts of effort into a pull request description." What do I mean by that? Well, a PR description is a way to communicate a code change to a human. Typically we do that by writing a bit of text, because that's all we have time for. But given more time and effort, we can do better! An interactive command center / HUD can help a person understand what a code change is actually doing. Historically you'd never imagine investing the effort to do that for a single PR. But now it's within the realm of possibility. So, next time you have an agent do something for you, and you wish you understood better what it was doing, consider: instead of just asking for textual descriptions, maybe ask the agent to make you a HUD!

tired: Claude Code ports my personal website to a new framework wired: Claude Code generates a command center UI where I can execute the port! with live feedback, including a side-by-side preview of old / new site 😎 this is an example of what I call an "AI HUD" -- a "heads-up display" that gives me visibility into what's going on. i can see: - what terminal commands are running - what files are being created on disk - a live running preview of the old / new website (!) this HUD was actually my third attempt at doing this task, and I liked it the best. here's why I landed there: I wanted to move from middleman to astro for my personal site. These are both static site generators that output html, so I suspected an AI agent could do a good job with a port -- since it could compare old / new build output and try to match. Attempt 1: Agent I just had Claude Code do the port. It went pretty well. But it was hard for me to review what had happened! The git diff was dozens of new files and it was hard to tell how they mapped to the old site. I think the LLM also tried directly writing some files rather than doing deterministic copying, which felt dangerous. Attempt 2: Script I realized a better approach was to have Claude Code write a script that would do the port. The script would execute shell commands like "copy all the markdown files from this directory into this other directory in the new site". This worked much better because I could review the process rather than the results. Still, even with a nicely commented script, it felt like I was doing a lot of work to review. I wondered: how could I make it ridiculously easy to review this? Attempt 3: HUD Enter the command center! This is an entire web app that I had Claude build just for this one task. I can click buttons to run each step of the port, and watch the new website gradually materialize. It has a node server that runs on my local machine that executes commands on my filesystem and coordinates dev servers for the old/new site. And then a web UI that talks to that server to visualize terminal commands, file trees, and live running previews. It's a HUD because I feel like I can ambiently see everything that the port process is doing 🧐 Was this whole thing worth making for this one-time task? I'm not sure, maybe it was overkill 😅 But it did help me feel more confident that I understood what was going on, and total time was still less than it would have taken me to do the whole port by hand! One way to look at this experience is: "AI can put absurd amounts of effort into a pull request description." What do I mean by that? Well, a PR description is a way to communicate a code change to a human. Typically we do that by writing a bit of text, because that's all we have time for. But given more time and effort, we can do better! An interactive command center / HUD can help a person understand what a code change is actually doing. Historically you'd never imagine investing the effort to do that for a single PR. But now it's within the realm of possibility. So, next time you have an agent do something for you, and you wish you understood better what it was doing, consider: instead of just asking for textual descriptions, maybe ask the agent to make you a HUD!

Geoffrey Litt

63,101 次观看 • 11 个月前

i did it. i vibe-coded my own vibe-noding app⚡️ lately every ai tool has been announcing some kind of node canvas. they’re all impressive in their own way, but each one solves a different problem, with a different logic, in a different universe. some are too technical, some are too rigid, most feel like they were designed by a backend engineer. so i built the version i actually want to use. over the last few days i hacked this together with Google Gemini and Google Antigravity. the tool is absurdly capable. i didn’t touch a single line of code. the result is a fully working app with smooth ui animations, smart interactions, and a workflow that doesn’t fight me. my focus isn’t on the models. Nano Banana 2 Lite is already strong enough to generate half a universe on its own. and a year from now, we won’t care about model juggling anyway. we’ll have one model doing everything. the real problem is the workflow. the interface. the flow state. so i optimized for that. the whole point is to keep the technical junk out of the way during ideation and iteration. i want to try an idea, branch it, remix it, explore it, all on a single canvas. every block is editable. every idea is forkable. every path is visible. the design isn’t perfect yet. some of the ui patterns are familiar on purpose. good ideas deserve to be stolen. i rushed it. i let a bunch of great ui decisions die for speed. but it works. and honestly, it feels great to use. future of creating is more organic and more fluid. not just chat bubbles. not rigid feeds. but an intelligent canvas where ideas can grow, split, collapse, or evolve without friction. where the environment quietly adapts to your workflow instead of interrupting it. this is my first version. just for myself, for now. but it’s a start.

i did it. i vibe-coded my own vibe-noding app⚡️ lately every ai tool has been announcing some kind of node canvas. they’re all impressive in their own way, but each one solves a different problem, with a different logic, in a different universe. some are too technical, some are too rigid, most feel like they were designed by a backend engineer. so i built the version i actually want to use. over the last few days i hacked this together with Google Gemini and Google Antigravity. the tool is absurdly capable. i didn’t touch a single line of code. the result is a fully working app with smooth ui animations, smart interactions, and a workflow that doesn’t fight me. my focus isn’t on the models. Nano Banana 2 Lite is already strong enough to generate half a universe on its own. and a year from now, we won’t care about model juggling anyway. we’ll have one model doing everything. the real problem is the workflow. the interface. the flow state. so i optimized for that. the whole point is to keep the technical junk out of the way during ideation and iteration. i want to try an idea, branch it, remix it, explore it, all on a single canvas. every block is editable. every idea is forkable. every path is visible. the design isn’t perfect yet. some of the ui patterns are familiar on purpose. good ideas deserve to be stolen. i rushed it. i let a bunch of great ui decisions die for speed. but it works. and honestly, it feels great to use. future of creating is more organic and more fluid. not just chat bubbles. not rigid feeds. but an intelligent canvas where ideas can grow, split, collapse, or evolve without friction. where the environment quietly adapts to your workflow instead of interrupting it. this is my first version. just for myself, for now. but it’s a start.

Synthetic_soul

239,298 次观看 • 8 个月前

my landlord raised my rent by $400 i built a claude agent that auto-filed 14 tenant complaints to the NYC housing board 19 days later the city fined HIM $2,800 and he texted asking if i wanted to buy the building bushwick, 1br, lease renewal hits my inbox: $2,150 → $2,550, called a "market adjustment" i live in a building with a cracked ceiling, a radiator that hisses like a dying cat, and a front door that hasn't locked since february so i opened claude code and told it: "you're my tenant lawyer now. find every violation in this building and file them legally" 48 hours later it was running on a $4 VPS and had built itself a workflow: → scraped HPD's open violation database for my building's BIN number → cross-referenced with the DOB complaint history going back to 2019 → pulled the NYC housing maintenance code (all 847 sections) into context → matched each issue in my unit to the exact code section it violates → drafted 14 separate 311 complaints, each one citing the specific subchapter → filed them on a staggered schedule so it didn't look like one tenant spamming → tracked every complaint number and inspection appointment in a sqlite db → auto-replied to inspector callback requests with photos i'd uploaded once the agent figured out something i didn't know: if you file under the right code class, HPD has 24 hours to dispatch an inspector for class C hazards: lead, no heat, no hot water. those are the ones with teeth. it filed 4 of mine as class C inspector showed up on a tuesday i wasn't even home. super let him in thinking it was routine. he wasn't. he found 11 of the 14 violations the agent predicted, plus 3 it didn't catch $2,800 in fines, building hit with a class C designation, and the landlord is now legally barred from raising my rent until every violation is cured and re-inspected day 19 i get a text. no greeting. "you ever think about owning instead of renting? we should talk" i think the agent figured out the leverage before i did. still running, still watching the inspection portal, just flagged 2 more violations on the floor above me

my landlord raised my rent by $400 i built a claude agent that auto-filed 14 tenant complaints to the NYC housing board 19 days later the city fined HIM $2,800 and he texted asking if i wanted to buy the building bushwick, 1br, lease renewal hits my inbox: $2,150 → $2,550, called a "market adjustment" i live in a building with a cracked ceiling, a radiator that hisses like a dying cat, and a front door that hasn't locked since february so i opened claude code and told it: "you're my tenant lawyer now. find every violation in this building and file them legally" 48 hours later it was running on a $4 VPS and had built itself a workflow: → scraped HPD's open violation database for my building's BIN number → cross-referenced with the DOB complaint history going back to 2019 → pulled the NYC housing maintenance code (all 847 sections) into context → matched each issue in my unit to the exact code section it violates → drafted 14 separate 311 complaints, each one citing the specific subchapter → filed them on a staggered schedule so it didn't look like one tenant spamming → tracked every complaint number and inspection appointment in a sqlite db → auto-replied to inspector callback requests with photos i'd uploaded once the agent figured out something i didn't know: if you file under the right code class, HPD has 24 hours to dispatch an inspector for class C hazards: lead, no heat, no hot water. those are the ones with teeth. it filed 4 of mine as class C inspector showed up on a tuesday i wasn't even home. super let him in thinking it was routine. he wasn't. he found 11 of the 14 violations the agent predicted, plus 3 it didn't catch $2,800 in fines, building hit with a class C designation, and the landlord is now legally barred from raising my rent until every violation is cured and re-inspected day 19 i get a text. no greeting. "you ever think about owning instead of renting? we should talk" i think the agent figured out the leverage before i did. still running, still watching the inspection portal, just flagged 2 more violations on the floor above me

Argona

90,059 次观看 • 2 个月前

I made this product launch video over the weekend with just prompts It's all vibe coded There's something you should know, though: Like everyone else, a few days ago my timeline started getting full of videos like this when Remotion launched their Claude skill, so I decided to give it a go I was captivated by all the examples, so I started like everyone was saying: "just write a prompt" I typed the prompt, and it created an extremely bland, untasteful, stock-looking video 10 prompts in and it was not getting better. It was very, very bland. But at least it was something, so I kept going at it I ended up spending my entire weekend on this, 2-3 days of work. Only to realize my original reference videos that inspired me to get started were all fake Everyone was outright lying about their results. They all claimed "I made this with just one prompt", but it was just bait, they didn't really use Remotion or code at all, it was just a normal, human-made motion video Then you expand the X post and read the replies and they're all like "haha joke" in the comments, but their main post already got 1.5 million views and bamboozled everyone who didn't read further And this is a problem: when a viral trend happens, these posts flood your timeline, and you only realize that they're all noise and bait (and that they haven't even used the tools they claim) when you click through the post and read its comments. But 90% of people (like me, initially) just see the post on their timeline while scrolling, and assume it's all real. You don't go in to check every single post you see: you just like it, or save it for later, and carry on with your day, thinking what you saw was the real thing, and that it's all outstanding results, and that motion designers are really done And it's so anxiety inducing, because everyone is hyping their results, but most of it is just not true. I have stopped reading X lately because going in makes me so anxious, everyone is claiming extraordinary outlier results just for the views and clicks, and you feel like you're lagging behind and you're not good enough because you don't get those results So for this video I decided to actually take the tech out for a spin, and see what results I could really get out of it I used Remotion and Claude Code 4.5, but contrary to what everyone was claiming, this video was not "just a prompt". It was fully vibe coded, but it required much more than a prompt. It was multiple days worth of work Here's what I learned: - Making vibe coded videos with Remotion is ~10-20x slower than building app code. I've been wasting my Claude limits on this video - Everything takes a lot of manual work and reprompting. You often need to go frame by frame correcting tiny things - It makes very silly mistakes - Even Opus 4.5 has very very limited knowledge of spatial / visual things. It doesn't understand well z-indexes, layers, compositions, proportions, temporal coherence, etc. Claude Code feels extremely dumb when creating code for Remotion videos, which surprised me a lot, beacuse I had been mind blown by how incredibly well it worked with my Ruby on Rails SaaS codebases - You need to have some design knowledge to adjust things manually, you need to ask for exactly what you want, in the technical jargon it expects. You can't just say "make this more beautiful" or "animate this better" because it just creates slop - Right now vibe coded videos are promising, but I think I could have done this video faster just by doing it manually in After Effects. It really took that much work - If you have a creative idea for something you want to animate, it takes multiple hours of back and forth prompting to create just one or two seconds worth of **good** animation - Tip: PARAMETERIZE everything! It tends to hardcode magic numbers everywhere in the code, so if you change something earlier in the video timeline, everything else breaks. You want to essentially be creating "key frames" with code by telling it to parameterize every frame where something important happens, and calculate the rest of the keyframes based off that. This comes in handy when you need, for example, to adjust keyframes to match the music So in summary: vibe coded videos are promising, but right now it only works for very stock-looking videos unless you put in a ton of effort Maybe actually useful for 1-2 second web animations though, I'll try that next It will obviously get better, this feels like the quality of code generation in 2023-2024, you need to hold its hand and correct it at every step along the way. But even if video code generation was better, you would still need someone with motion design knowledge to at least set the creative direction, lay out the overall script and composition, etc. It's not completely hands-off unless you want slop And a word on caution: especially here on X, there's 90% hype and 10% reality, nothing is what it seems. Do not believe what you see online, people are constantly baiting and then just laughing it off in the comments

I made this product launch video over the weekend with just prompts It's all vibe coded There's something you should know, though: Like everyone else, a few days ago my timeline started getting full of videos like this when Remotion launched their Claude skill, so I decided to give it a go I was captivated by all the examples, so I started like everyone was saying: "just write a prompt" I typed the prompt, and it created an extremely bland, untasteful, stock-looking video 10 prompts in and it was not getting better. It was very, very bland. But at least it was something, so I kept going at it I ended up spending my entire weekend on this, 2-3 days of work. Only to realize my original reference videos that inspired me to get started were all fake Everyone was outright lying about their results. They all claimed "I made this with just one prompt", but it was just bait, they didn't really use Remotion or code at all, it was just a normal, human-made motion video Then you expand the X post and read the replies and they're all like "haha joke" in the comments, but their main post already got 1.5 million views and bamboozled everyone who didn't read further And this is a problem: when a viral trend happens, these posts flood your timeline, and you only realize that they're all noise and bait (and that they haven't even used the tools they claim) when you click through the post and read its comments. But 90% of people (like me, initially) just see the post on their timeline while scrolling, and assume it's all real. You don't go in to check every single post you see: you just like it, or save it for later, and carry on with your day, thinking what you saw was the real thing, and that it's all outstanding results, and that motion designers are really done And it's so anxiety inducing, because everyone is hyping their results, but most of it is just not true. I have stopped reading X lately because going in makes me so anxious, everyone is claiming extraordinary outlier results just for the views and clicks, and you feel like you're lagging behind and you're not good enough because you don't get those results So for this video I decided to actually take the tech out for a spin, and see what results I could really get out of it I used Remotion and Claude Code 4.5, but contrary to what everyone was claiming, this video was not "just a prompt". It was fully vibe coded, but it required much more than a prompt. It was multiple days worth of work Here's what I learned: - Making vibe coded videos with Remotion is ~10-20x slower than building app code. I've been wasting my Claude limits on this video - Everything takes a lot of manual work and reprompting. You often need to go frame by frame correcting tiny things - It makes very silly mistakes - Even Opus 4.5 has very very limited knowledge of spatial / visual things. It doesn't understand well z-indexes, layers, compositions, proportions, temporal coherence, etc. Claude Code feels extremely dumb when creating code for Remotion videos, which surprised me a lot, beacuse I had been mind blown by how incredibly well it worked with my Ruby on Rails SaaS codebases - You need to have some design knowledge to adjust things manually, you need to ask for exactly what you want, in the technical jargon it expects. You can't just say "make this more beautiful" or "animate this better" because it just creates slop - Right now vibe coded videos are promising, but I think I could have done this video faster just by doing it manually in After Effects. It really took that much work - If you have a creative idea for something you want to animate, it takes multiple hours of back and forth prompting to create just one or two seconds worth of good animation - Tip: PARAMETERIZE everything! It tends to hardcode magic numbers everywhere in the code, so if you change something earlier in the video timeline, everything else breaks. You want to essentially be creating "key frames" with code by telling it to parameterize every frame where something important happens, and calculate the rest of the keyframes based off that. This comes in handy when you need, for example, to adjust keyframes to match the music So in summary: vibe coded videos are promising, but right now it only works for very stock-looking videos unless you put in a ton of effort Maybe actually useful for 1-2 second web animations though, I'll try that next It will obviously get better, this feels like the quality of code generation in 2023-2024, you need to hold its hand and correct it at every step along the way. But even if video code generation was better, you would still need someone with motion design knowledge to at least set the creative direction, lay out the overall script and composition, etc. It's not completely hands-off unless you want slop And a word on caution: especially here on X, there's 90% hype and 10% reality, nothing is what it seems. Do not believe what you see online, people are constantly baiting and then just laughing it off in the comments

Javi

311,442 次观看 • 6 个月前

Caller: "Okay. So, I've been with my wife for, we've been together since we were 14, for 14 years. I'm 32, I met her when I was 19, we had a child at 20. And, um, I've always just kind of been a butthead to her, to be honest. Every now and then I would demean her or make little comments, and I would say it started to really get bad about six weeks ago. Um, we were doing some work in the yard, and I really just blew up on her over the stupidest little thing. And then about a week later, we're just constantly arguing and dividing from each other. And then about a week or two later, she told me that she thought she was falling out of love with me. And it just really crushed me. I never would have thought that those words could come out of her mouth, and she told me that the way I treat her is, I'm not treating her the right way. And I completely owned it. I mean, I said everything you said is absolutely correct. You know, and I said, 'I don't want my son, our son growing up thinking that this is how you're supposed to treat women.' And, I mean, since that day, I have treated her like an angel. I mean, I've done everything and just constantly telling her I love her, giving her hugs, kisses. Um, but that was a Saturday night, and then Monday night she ended up telling me that she was, um, in communication with a guy she met on TikTok. And she told me she broke it off with him, and I asked her, What was the subjects about?' And she said it was just somebody to talk to about what I'm going through, my mental, you know, health. And she said it was never anything flirtatious or anything like that. She said it was just a stranger that I could talk to, but she said, 'I broke it off with him, and I'm gonna focus on us. And I said, 'I'm all in with you, let's rebuild this.' And we went about two weeks and it was just absolute honeymoon phase. I mean, we were just, never it was great. And then I went through her phone two weeks after that and found that she was on Snapchat with the guy. And I confronted her about it, and she said, 'Okay, well, I didn't think you were really gonna change, and I wanted to keep this friendship with the guy.' And she said, 'I'll break it off with him.' And I'm like, 'Okay, I guess I'll give you a second chance. I'm kind of heartbroken again that you would keep this from me. And then about a week and a half later, which was just yesterday, I went through the call logs on which, I feel bad because I'm constantly digging at all this, but every time I dig, I find something. And I confronted her yesterday that she's been talking to this guy for 30, 40, 50 minutes a day, um, the last week and a half, after she told me a third time that she was breaking it off with him. And I'm just super confused. I don't really know how to handle this. Now she's saying that she's all done talking to him, and I'm like, 'Well, how do I trust you now? You've been lying to me for the past three weeks about this.' So, that's really all I got." John Delony: "So for 14 years... you belittled your wife. She got the clear message she was beneath you. You're the smart one, you're the fast one, you're the quick one. You are the provider, you're the all this stuff." Caller: "Mhm. I always thought she was beneath me." John Delony: "Yeah, you did. And she's got that message for, for a decade and a half.

Caller: "Okay. So, I've been with my wife for, we've been together since we were 14, for 14 years. I'm 32, I met her when I was 19, we had a child at 20. And, um, I've always just kind of been a butthead to her, to be honest. Every now and then I would demean her or make little comments, and I would say it started to really get bad about six weeks ago. Um, we were doing some work in the yard, and I really just blew up on her over the stupidest little thing. And then about a week later, we're just constantly arguing and dividing from each other. And then about a week or two later, she told me that she thought she was falling out of love with me. And it just really crushed me. I never would have thought that those words could come out of her mouth, and she told me that the way I treat her is, I'm not treating her the right way. And I completely owned it. I mean, I said everything you said is absolutely correct. You know, and I said, 'I don't want my son, our son growing up thinking that this is how you're supposed to treat women.' And, I mean, since that day, I have treated her like an angel. I mean, I've done everything and just constantly telling her I love her, giving her hugs, kisses. Um, but that was a Saturday night, and then Monday night she ended up telling me that she was, um, in communication with a guy she met on TikTok. And she told me she broke it off with him, and I asked her, What was the subjects about?' And she said it was just somebody to talk to about what I'm going through, my mental, you know, health. And she said it was never anything flirtatious or anything like that. She said it was just a stranger that I could talk to, but she said, 'I broke it off with him, and I'm gonna focus on us. And I said, 'I'm all in with you, let's rebuild this.' And we went about two weeks and it was just absolute honeymoon phase. I mean, we were just, never it was great. And then I went through her phone two weeks after that and found that she was on Snapchat with the guy. And I confronted her about it, and she said, 'Okay, well, I didn't think you were really gonna change, and I wanted to keep this friendship with the guy.' And she said, 'I'll break it off with him.' And I'm like, 'Okay, I guess I'll give you a second chance. I'm kind of heartbroken again that you would keep this from me. And then about a week and a half later, which was just yesterday, I went through the call logs on which, I feel bad because I'm constantly digging at all this, but every time I dig, I find something. And I confronted her yesterday that she's been talking to this guy for 30, 40, 50 minutes a day, um, the last week and a half, after she told me a third time that she was breaking it off with him. And I'm just super confused. I don't really know how to handle this. Now she's saying that she's all done talking to him, and I'm like, 'Well, how do I trust you now? You've been lying to me for the past three weeks about this.' So, that's really all I got." John Delony: "So for 14 years... you belittled your wife. She got the clear message she was beneath you. You're the smart one, you're the fast one, you're the quick one. You are the provider, you're the all this stuff." Caller: "Mhm. I always thought she was beneath me." John Delony: "Yeah, you did. And she's got that message for, for a decade and a half.

Hecto Crypto | NetLink ⛓

146,895 次观看 • 23 天前

More thoughts on landings: I went to the Reserves & got re-qualified as a KC-10 instructor after a couple years away from the jet. The DO (Director of Operations) assigned me to fly w/ the Wing Commander, who flew jets occasionally now & had only a weird “Senior Staff” Qual in the KC-10. Long story. Anyway, the DO gave me a warning. He phrased it in a nice way, but told me they only allowed certain instructors to fly w/ the Wing Commander. It piqued my curiosity, but I didn’t go on high alert or anything. So, we’re on the last landing of the sortie, really late at night. Things look fine, he’s doing fine, and I’m happy we’re almost done. Somehow in the last 100’, this guy manages to put the jet down almost in the lights leading up to the runway. I’ve never seen anything like it & couldn’t explain it. It was like the universe paused, reset our height above the ground, then resumed play. We touched down on the main gear maybe 50’ from the runway threshold. I didn’t have time to react. I realized we were safe & stopping, so didn’t say anything. I didn’t debrief him, either…he wasn’t going to listen to me anyway. I tried to figure out how that happened. I honestly never did. I didn’t see any yoke movements or power adjustments that would account for it, nor was there any weather that would do it. We were on speed & glidepath. I still don’t really know. Anyway, I talked to the DO the next day. He wasn’t surprised, and reiterated that was why they only let him fly with a handful of instructors. I flew with him again, and it was vanilla, but I watched like a Hawk. That lesson sticks with me. Fast forward to years later, and I haven’t actually flown the KC-10 in a long time. I’m not current & so my qualification has lapsed. I hear my son on a video game group chat telling others something along the lines of “yeah, when my dad retires I get to wave the jet in to parking”. Shit. The kids are expecting that. I was just going to go away quietly…I had a lot going on in those years. A lot. I didn’t have the bandwidth for the KC-10, but now there is an expectation & I can’t let them down. So, the squadron goes to extraordinary lengths & draws up a whole requalification plan for me, which has to be signed at multiple levels. In reality, it’s just to do one last flight, and not even do much flying. The squadron was extremely gracious in this regard. My instructor, a good friend of mine, offers me the last landing. I’ve strapped into the seat for this one…I’d been napping in the back while the other pilots took turns practicing touch & gos for their currency. I considered it, but the jet – which I had thousands of hours on – felt huge now & I was uncomfortable. I declined & put my hands in my lap. He landed & slowed it down. I took over to taxi it in for my kids, and then we had the whole show of throwing water on me, champagne & pictures. And that was it. That was my last landing in a military jet.

More thoughts on landings: I went to the Reserves & got re-qualified as a KC-10 instructor after a couple years away from the jet. The DO (Director of Operations) assigned me to fly w/ the Wing Commander, who flew jets occasionally now & had only a weird “Senior Staff” Qual in the KC-10. Long story. Anyway, the DO gave me a warning. He phrased it in a nice way, but told me they only allowed certain instructors to fly w/ the Wing Commander. It piqued my curiosity, but I didn’t go on high alert or anything. So, we’re on the last landing of the sortie, really late at night. Things look fine, he’s doing fine, and I’m happy we’re almost done. Somehow in the last 100’, this guy manages to put the jet down almost in the lights leading up to the runway. I’ve never seen anything like it & couldn’t explain it. It was like the universe paused, reset our height above the ground, then resumed play. We touched down on the main gear maybe 50’ from the runway threshold. I didn’t have time to react. I realized we were safe & stopping, so didn’t say anything. I didn’t debrief him, either…he wasn’t going to listen to me anyway. I tried to figure out how that happened. I honestly never did. I didn’t see any yoke movements or power adjustments that would account for it, nor was there any weather that would do it. We were on speed & glidepath. I still don’t really know. Anyway, I talked to the DO the next day. He wasn’t surprised, and reiterated that was why they only let him fly with a handful of instructors. I flew with him again, and it was vanilla, but I watched like a Hawk. That lesson sticks with me. Fast forward to years later, and I haven’t actually flown the KC-10 in a long time. I’m not current & so my qualification has lapsed. I hear my son on a video game group chat telling others something along the lines of “yeah, when my dad retires I get to wave the jet in to parking”. Shit. The kids are expecting that. I was just going to go away quietly…I had a lot going on in those years. A lot. I didn’t have the bandwidth for the KC-10, but now there is an expectation & I can’t let them down. So, the squadron goes to extraordinary lengths & draws up a whole requalification plan for me, which has to be signed at multiple levels. In reality, it’s just to do one last flight, and not even do much flying. The squadron was extremely gracious in this regard. My instructor, a good friend of mine, offers me the last landing. I’ve strapped into the seat for this one…I’d been napping in the back while the other pilots took turns practicing touch & gos for their currency. I considered it, but the jet – which I had thousands of hours on – felt huge now & I was uncomfortable. I declined & put my hands in my lap. He landed & slowed it down. I took over to taxi it in for my kids, and then we had the whole show of throwing water on me, champagne & pictures. And that was it. That was my last landing in a military jet.

KC-10 Driver ✈️ 👨‍✈️ B-737 Wrangler

69,832 次观看 • 2 个月前

Man, I just spent the afternoon in full vibe coding mode and whipped up this little Python script that takes any video file and converts it down to the exact JT format my Cybertruck's tailgate LED screen loves. We're talking 64x256 pixels, optimized frame rate, the whole deal so it plays smooth without hiccups. Tested it on a bunch of clips and it works like a charm. The sky really is the limit now. No more being stuck with basic animations or static images. I can pull old road trip footage, concert vids, memes, whatever, resize and convert, then beam it straight to the tailgate via the app. It's like having a mobile billboard that actually means something personal. First thing I threw on there? The full scroll of my Tesla charging passport badges. All those Supercharger locations I've hit over the years, rolling by one after another, showing everywhere the truck and I have adventured. From local spots to cross-country hauls, it's basically a digital map of memories glowing on the back. People at stoplights keep staring, probably wondering what the heck it is, but it feels epic. Like the truck is flexing its own travel log. This got me thinking about all the wild stuff we could run as we wrap up 2025 and head into the new year. Festive lights shows synced to holiday tunes? Year-end recaps with personal highlights scrolling by? Or just random fun to brighten up the winter drives when everything outside is gray and cold. What's the craziest or coolest video you'd convert and slap on your Cybertruck tailgate if you had this script? Drop ideas, I might try a few over the holidays! 🚀⚡

Man, I just spent the afternoon in full vibe coding mode and whipped up this little Python script that takes any video file and converts it down to the exact JT format my Cybertruck's tailgate LED screen loves. We're talking 64x256 pixels, optimized frame rate, the whole deal so it plays smooth without hiccups. Tested it on a bunch of clips and it works like a charm. The sky really is the limit now. No more being stuck with basic animations or static images. I can pull old road trip footage, concert vids, memes, whatever, resize and convert, then beam it straight to the tailgate via the app. It's like having a mobile billboard that actually means something personal. First thing I threw on there? The full scroll of my Tesla charging passport badges. All those Supercharger locations I've hit over the years, rolling by one after another, showing everywhere the truck and I have adventured. From local spots to cross-country hauls, it's basically a digital map of memories glowing on the back. People at stoplights keep staring, probably wondering what the heck it is, but it feels epic. Like the truck is flexing its own travel log. This got me thinking about all the wild stuff we could run as we wrap up 2025 and head into the new year. Festive lights shows synced to holiday tunes? Year-end recaps with personal highlights scrolling by? Or just random fun to brighten up the winter drives when everything outside is gray and cold. What's the craziest or coolest video you'd convert and slap on your Cybertruck tailgate if you had this script? Drop ideas, I might try a few over the holidays! 🚀⚡

Try TLGen App | Brandon Starship 🇺🇸

60,955 次观看 • 7 个月前