Sensitive content

This media may contain sensitive content.

Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Using a free use whore would fix me right now #cnc #rapebait #rapekink #tabookink #agegap #ageplay #breedingkink #ddlg #sizekink #rapemeat #rapethreats #abductionkink #kidnapkink #bondage #tiedup #rough #brat

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

I never imagined connecting a wallet to ROZO would be hard for anyone… until someone reached out to me saying they were completely stuck and frustrated. So if you're dealing with that right now — don't worry, it's usually a quick fix with the right setup. ...here's what works for most people who hit this wall. 🔻 🔹️ The problem first Some browsers or wallets just don't cooperate with Rozo's connection flow. You get errors, nothing loads, or it keeps failing for no clear reason. The person who messaged me was running into exactly that. The good news? Switching a couple things makes it feel effortless. 🔹️ LOBSTR wallet + browser combo I recommend using LOBSTR wallet — it's built specifically for the Stellar network, so it stays stable and links up with Rozo much better than other options. Also: use Chrome as your browser. If it still doesn't work in Chrome, switch to Brave — that will definitely do the trick for almost everyone. 🔹️ How it actually works ⤞ Use Chrome (or Brave if needed) ⤞ Go to: ⤞ Use LOBSTR wallet ⤞ When you're on the site, use your Passkey (like FaceID or your fingerprint) to get in ⤞ Once you're done checking your earnings or moving funds, log out That's it. You're in. 🔹️ The part people overlook You won't need to dig up any long seed phrases. Passkey is a lot faster and keeps everything tied to your own device security. Logging out is a simple habit, but it's the best way to keep your wallet safe from any browser-based attacks. 🔹️ Final thought Connecting should feel boringly easy — not like a puzzle. With LOBSTR, Chrome (or Brave), and this setup, it finally does for most people who were stuck. ✔ Use LOBSTR. ✔ Use Chrome (or Brave). ✔ Log in with Passkey. ✔ Log out when done. ROZO community: If you're still having trouble, drop a reply — happy to help you get sorted

EMMA

22,771 Aufrufe • vor 6 Monaten

Since last night, Russian "Z-war correspondents" complain that Russia's Starlink satellite terminals are turned off. SpaceX and Ukrainian Defense Ministry worked out a solution that would allow to keep Ukrainian Starlinks active, and Russia's turned off. Russian propagandist Solovyev demands President Trump to call Elon Musk. Otherwise, Solovyev is threatening strikes on Starlink factories and satellites in space. I translated a few more of the "Z-bloggers'" complaints for you: "The Starlink situation has turned out badly. And so has Musk. As the godfather finished his cucumber, he concluded with anguish: 'Turns out our father wasn’t a father at all, but a bastard...' Though it’s not entirely clear what we were doing during all those years when Musk turned a blind eye to the Russian Armed Forces using Starlink. Presumably, some preparations were made for a shutdown. Maybe a 'Plan B' was worked out." "As the saying goes, not until the roasted rooster pecks you in the *ss... Starlinks are down after all... And we have barely any communications system of our own - and what little there is costs an arm and a leg." "A betrayal of cosmic proportions. We were lied to. Communications have disappeared across all Russian Armed Forces units. Right now, everything has reverted to the early days of the 'special military operation' in 2022, when there was zero coordination between units - which led to well-known results. Let me remind you that just before the 'SMO,' Roscosmos was working on building a satellite communications constellation - for the United Kingdom. Roscosmos launched more than 400 communications satellites for OneWeb, which are now, among other things, being used to strike Russia." "In reality, the problem isn’t Musk or Trump. They weren’t the ones who effectively hooked the entire army at the front on the technology of a direct adversary, making the Russian Armed Forces dependent on a single master switch located in Washington. They weren’t the ones who, for years, did absolutely nothing to change this - to develop even a rough equivalent or find an alternative means of access. They weren’t the ones who treated the situation as normal for years, using Starlink and assuming it would always be available - as if satellite internet were universal, like air. Most likely, what we’re seeing now is just one stage in countering the Russian army’s use of Starlink, since not everything - and not everyone - has been disconnected. But once Ukrainian terminal whitelists are fully operational, it’s still unclear how they could be bypassed. Even if a temporary workaround is found, this entire situation is not just a wake-up call - it’s a massive blow to the tsar bell."

Anton Gerashchenko

467,558 Aufrufe • vor 5 Monaten

If you are a SaaS founder, read this. I think I found the best way for you to use OpenClaw. You can literally turn your agent into Paul Graham telling you how to fix your SaaS. The insights I got from it are just insane. TLDR; 1. OpenClaw analyzes your Stripe 2. Tries your onboarding like your ICP 3. Gets Paul Graham's knowledge base 4. Gives you a full report to fix your SaaS 1 - Create a "read only" API on Stripe. Give it to your OpenClaw (or whatever agent you're using right now). Ask it to analyze the full data: - Pricing - Churn - Conversion - LTV - Trial to paid rate - Discount impact - Invoice patterns Ask it to really go deep. Not the surface level. Go into every corner. Check invoices, not only graphs. Look at cohort behavior month by month. Ask it to calculate your real MRR after discounts (not the vanity number Stripe shows you). When I did this, I found so many golden nuggets in my Stripe Data. And the feedbacks from my OpenClaw were already super valuable. But this is not enough. We need the whole context, not just Stripe. 2 - Ask your Agent to try your tool Give it a free coupon for your SaaS and ask it to sign up and follow the onboarding like your ICP (if you didn't yet, define it before you send it on your landing page). It will follow step by step, take screenshots, and tell you what's good, what's not and give you solutions. Ask it to push the feedback on Notion (so you can visualize it). This already will give you enough work for the next month. 3 - Turn your OpenClaw into YC Founder Paul Graham co-founded Y Combinator and invested in Stripe, Airbnb, Dropbox, Reddit. He's written 230 essays on startups over 20 years. It's basically the bible of building companies. Send this link to your OpenClaw and ask it to find anything that could apply to your SaaS and current problems you're facing: paulgraham[.]com/articles.html Your agent will read all of them and pull out what's relevant to YOUR situation. 4 - The cherry on the cake Now ask it to combine all the data it gathered so far: - Stripe analysis - Onboarding feedback - Paul Graham knowledge base And tell it to give you a full analysis and solution for your SaaS and push it to Notion. This is where it gets insane. I got a 9 section report with specific fixes ranked by impact. Not just "improve your onboarding". This took me one afternoon. Imagine how much it would have cost me to get these kind of feedback a few years ago?

Florian Darroman

14,684 Aufrufe • vor 4 Monaten

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 Aufrufe • vor 3 Monaten

Don't Buy a Mac Mini for Clawdbot: The Secret $10,000 Architecture That Costs You Nothing clawdbot might be the reason you feel like you need a ten thousand dollar computer right now but i am about to show you why that fomo is going to leave you broke. if you have been watching everyone rush out to buy mac minis and mac studios just to run open claw or some local models you are witnessing a massive transfer of wealth from your pocket to apple for no reason. there is a specific setup i use that costs almost nothing and keeps my main machine safe from whatever these autonomous agents are doing. if you stick with me i will walk you through the exact architecture of a professional trading system that handles the heavy lifting without you needing to drop a single rack on hardware most people are scared of running these bots on their main computer because they don't want an agent messing with their personal files or browser sessions. instead of buying a second mac mini for six hundred dollars you can just go to the top left of your screen and create a brand new user profile. this acts like a completely isolated sandbox where you can install all your trading tools and agents without them ever seeing your main data. it is essentially like getting a free computer for the price of five minutes of clicking around your settings but what if you aren't on a mac or you need to access your system while you are traveling without carrying three laptops in your backpack. this is where the first loop of professional automation starts to close because i use something called chrome remote desktop to bridge the gap. this allows me to leave a dedicated machine running in a safe place while i access the full desktop environment from a tablet or a cheap laptop anywhere in the world. it solves the mobility issue but it still doesn't solve the problem of those massive ten thousand dollar price tags for high end mac pros if you are a pc user or just someone who doesn't want to own physical hardware yet you should look into a windows vps through a provider like contabo. most developers will tell you to use a linux terminal but if you aren't a coder yet you need a visual interface you can actually see. getting a windows server allows you to log in and see a desktop just like your home computer for about fifteen dollars a month. i usually recommend at least twelve gigabytes of ram to keep things from getting janky when you are running multiple browser windows and agents at once now you might be thinking that the whole point of the big hardware was to run local models like kimi or glm to save on api costs. i spent years thinking i had to own the machines myself and i even spent hundreds of thousands on developers before i realized i could just do this myself. the secret to running those massive open source models without the ten thousand dollar investment is renting gpu power by the hour. sites like lambda labs let you spin up a monster machine that can run any model in existence for just a couple dollars an hour this is the ultimate pivot because it allows you to test if your strategy actually prints money before you commit to the hardware. you can turn the server on when you are iterating and turn it off the second you are done which keeps your overhead near zero. if you haven't proven that your bot can pay for itself yet then buying a mac studio is just an expensive hobby rather than a business move. there is a much bigger loophole involving the anthropic subscriptions that most people are completely overlooking right now right now i am using a specific plan with claude code that costs about two hundred dollars a month but it lets me run open claw all day without hitting api limits. if i were paying for those same tokens through the standard api i would probably be spending hundreds of dollars every single day. it is a massive cost savings that allows you to iterate and fail until you find a winning strategy without draining your bank account. even if they eventually close this loophole or snitch on the usage patterns it serves as the perfect training ground for a data dog the goal is to find a system that works with a smaller or cheaper model like haiku before you ever try to scale up to the heavy weights. if you can make a strategy profitable using a less intelligent and cheaper model then you know you have found real alpha. once you have that foundation you can decide if it finally makes sense to build your own custom pc rig which will always be half the price of an apple machine. i am an apple guy so i usually pay the tax anyway but i only do it once the system is already generating enough to cover the cost ten times over i believe that code is the great equalizer because it took me from losing money and getting liquidated to having fully automated systems doing the work for me. i had to learn to live with the iterations and the failures on youtube to get to this point of clarity. the universe tends to get out of your way once you make a non negotiable contract with yourself to see the process through to the end. you don't need the flashy hardware or the most expensive setup to start winning in this game stay focused on the logic and the data rather than the hype and the fomo that everyone else is falling for. if you can master the bridge between renting power and owning your logic you will be ahead of ninety nine percent of the people in this space. the path to a fully automated life isn't paved with expensive gadgets but with the discipline to iterate until the system finally prints

Moon Dev

17,382 Aufrufe • vor 5 Monaten

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 Aufrufe • vor 2 Monaten

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

Mike

14,195 Aufrufe • vor 8 Monaten

The 118,000% Alpha: Building a High-Frequency AI Trading Floor with Claude Code if you think claude code is just for writing simple scripts then you are already losing to the bots that are hunting your liquidity right now. most traders are still clicking buttons while i have an ai employee running backtests on twenty eight different data sources simultaneously. i am going to show you how a strategy that returned over four hundred thousand percent was built in minutes using a secret sub agent workflow most people treat ai like a chatbot but i treat it like a quant architect that builds systems better than the devs i used to pay hundreds of thousands of dollars. there is one specific indicator combo that actually survived a stress test across tesla and bitcoin at the same time and i will reveal that logic further down. we have to talk about why your current backtests are probably lying to you before we get into the code my name is moon dev and i truly believe that code is the great equalizer in this world. for years i was the guy getting liquidated and overtrading because i was letting my emotions drive the wheel. i spent an insane amount of money hiring developers to build apps for me because i thought i was not smart enough to code myself. through that pain i realized that if i wanted to win i had to automate everything and learn to do it live on youtube for the world to see the secret to trading with claude code is not asking it for a strategy but using it to build a backtest architect. this sub agent acts as a consistent employee that understands how to test against massive datasets without getting tired. it allows me to iterate through hundreds of ideas in the time it used to take me to write one single line of python. this is how i found the strategy that hit a one hundred and eighteen thousand percent return on a single run there is a massive trap that almost every beginner falls into when they start using ai for trading. they find a strategy that looks amazing on one chart and they think they found the holy grail of wealth. that is usually just a lucky fluke or a curve fit mess that will blow up your account next week. the real secret to staying alive is the multi data testing system that claude built for me today we test every single idea against bitcoin and ethereum and solana but we also throw in apple and tesla and nvidia. if a strategy only works on crypto it is probably just riding a trend that is already over. i want to find the logic that is robust enough to handle the volatility of a meme coin and the steady grind of a blue chip stock. this is the only way to prove that the code actually has an edge in the market before we dive into the kalman filter logic i have to tell you about the dca bot i have running on solana right now. it is called housecoin and the thesis behind it is either going to make me a genius or leave me with nothing. it is buying every time we are under the five minute sma and i have been checking the transactions live. i will explain the risk management behind this "all or nothing" play shortly but first we need to look at the winners the winner of today was the acceleration bands combined with a kalman filter. the kalman filter is incredible because it helps remove the noise and lag that you get with standard moving averages. most indicators repaint which means they change their past values to look better after the price has already moved. the way i have implemented this filter prevents that trap so the results you see in the backtest are actually tradable when we ran the acceleration bands across the hourly nvidia chart it returned over two hundred percent while the underlying asset was down forty percent. that is a massive alpha gap that most people will never see because they are stuck using standard rsi settings. i have found that adding a volatility breakout with atr to this setup helps catch the moves that the banks are trying to hide. the math behind the atr breakout is what kept me from getting chopped up in the sideway ranges you might be wondering why i am giving all this code away for free on github instead of keeping it in a vault. it is because i remember what it felt like to be on the other side of the trade losing money every single day. i want to build a community of quads that are all researching and backtesting together. the goal is to chase the legacy of jim simons who proved that math and code are the only things that matter in the long run the rbi system is the framework that i follow every single day without exception. it stands for research and backtest and implement. most traders skip the middle step because they are too impatient to see the results. they hear a rumor on twitter and they buy the top only to get liquidated when the whales decide to take profits. if you do not backtest your ideas then you are just gambling with your life savings i am spending around forty to one hundred dollars a day on claude opus tokens because it is a drop in the bucket compared to what a developer would charge. this ai does not need a lunch break and it does not get bored when i ask it to create sixty different variations of a strategy. we just created five different parabolic sar versions today and found that the long only setup was the only one worth keeping. it returned sixteen thousand percent on the soul data set because it stayed out of the short side traps shorting crypto is extremely dangerous and usually not worth the stress for most people. i have found that focusing on long only strategies with a tight trail stop is the most consistent way to grow an account. the sub agent architect allowed me to verify this across twenty five data sources in less than ten minutes. this speed of iteration is the only way to stay ahead of the curve in an industry that changes every few seconds the dca bot i mentioned earlier is still grinding away and buying the dips as we speak. i have built it to be a long term play where i am slowly accumulating a position in housecoin based on smas. if the price stays under the moving average the bot keeps buying and if it goes above then it sits on its hands. it is a simple logic but it removes the human desire to "buy the moon" when the price is already overextended i found that the camarilla pivot indicator was mostly trash today when we ran the numbers. even though it looks fancy on a chart the backtest showed negative expectancy across almost every asset we tried. this is why backtesting is so important because it kills the "indicator porn" that influencers use to sell you courses. i would much rather know that a strategy is a loser now than find out after i put real money on the line the true secret to using claude code is to treat it like a partner and not just a tool. i ask it to find anomalies and then i ask it to prove me wrong by testing it against the worst market conditions in history. if a strategy can survive the 2022 crypto crash and the 2020 stock market dip then i might consider it for a live run. we are stepping on the gas every single day because there are always new anomalies popping up if you are fast enough to find them i have uploaded over twenty five new backtests to the github today for everyone to use. code is the equalizer because it does not care about your background or how much money you started with. if you can write the logic and prove the edge then the market has to pay you. i am going to keep building in public and showing the wins and the losses because that is the only way to stay real in this space the final piece of the puzzle is the mindset of iteration over perfection. i would rather run a hundred messy backtests today than spend a month trying to write one perfect script. the ai allows me to fail fast so that i can find the winners that actually move the needle. my housecoin dca bot is a testament to that philosophy of just building and letting the systems do the heavy lifting for me if you are still trading by hand you are playing a game that is rigged against you by the biggest firms in the world. they have the best servers and the best data and the best phds but they do not have your specific creativity. when you combine your ideas with the power of claude code you are creating a custom weapon that they have never seen before. i will see you in the code and we will keep chasing the goat until we find that ultimate edge

Moon Dev

18,390 Aufrufe • vor 5 Monaten

There is nothing more disgusting than a government using a parent's grief as cover to ram through bad law. Emma Mason is being used. You can see just how cruel the government is, on this interview with Deb Knight on A Current Affair last night. Her grief is being abused by governments and the media in Australia to justify removing access to social media from all children under the age of 16. Worse than that, they are using her to justify the most draconian internet access rules in the world, and it’s not just for kids. Every adult in Australia will have to age verify to get online to use sites like YouTube, facebook, Instagram, TikTok and X. Emma’s story, and that of her daughter is tragic, but the truth is: banning selective social media access will not stop bullying. It will not save the lives of children, and it does not absolve parental responsibility. Outsourcing parenting to government is both cowardly and foolish. Anyone who caught the ABC Lateline piece from 1975 released on this platform by John Adams earlier this week, would know, the Australian Government does not care about our children. We’ve seen real harm perpetrated on kids at government and government regulated childcare facilities. We see a rise in juvenile crime and weak bail laws, encouraging kids to perpetrate more and more extreme crime, and we know there still exists a culture of coverup when it comes to child harm among the establishment elite. The people who have drafted and passed the social media age ban laws are either not au fait with technology, or worse, they are authoritarian bullies who do not want any criticism from the only outlet available to the public – social media. Most disturbing to me though, is this misconceived belief that parents need the government to ban social media so they can parent their children. That is most certainly not the case. Mason further calls on even more government to provide the resources to help parents copilot the law. Because even she can see that it is an absolute mess that will cause harm. The government is an uncaring and incompetent machine, and most Australians seem completely unaware of those facts. The law only impacts the law abiding, and silly laws make for more lawlessness. The social media age ban and the subsequent requirement for adult identification is a silly law. It is possible to circumvent, and it will be circumvented. It will also breed a culture of lawlessness among our youth, and when they start to get away with these smaller ‘crimes’, they will indeed feel emboldened to test other laws. I am tired of Australian governments using tragedy to take more of our rights and freedoms away. We don’t need the government’s help to parent our children or lull us into the false sense of security that they keep us and our children safe. Go shopping in Melbourne and see how safe you feel. Watching the heartless machine use a mother’s grief is painful. It is disgusting. Albanese, Ley and the rest of the Australian political establishment should be ashamed of themselves, because they know exactly what they are doing. We must not stand for this. We must resist, push back and not comply. It is nothing more than a government sponsored attack on our privacy and free speech. It has nothing to do with child safety. We must parent our own children and educate them on how much we have already lost in the name of security and safety. We must show them that we don’t support the government, and maybe by the time they have grown up and are voting, we can start to elect people who deserve to be in leadership positions. Because the people we have right now are a danger to our future prosperity. This is not Australia. I just want Australia back.

Matthew Camenzuli

29,745 Aufrufe • vor 9 Monaten

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

Himanshu Kumar

37,447 Aufrufe • vor 3 Monaten

Brazilian Judge Pushes Nationalist Conspiracy Theory To Weaponize Federal Police Against Defenders Of Free Speech Brazil’s Federal Police discuss me in new report commissioned by Supreme Court Justice Alexandre de Moraes Yesterday, a Brazilian Supreme Court Justice, who is also the President of the Superior Electoral Commission, lashed out angrily at X owner Elon Musk. At an event heavily promoted by Globo News, Alexandre de Moraes claimed that Musk is part of a vast extremist conspiracy to undermine Brazil’s sovereignty and democracy. He claimed that Musk was an “irresponsible mercantilist” motivated solely by profits who had “united” with “extremist Brazilian politicians.” But there is no evidence of any conspiracy. Musk did not know I would publish the Twitter Files Brazil. Nor did the Brazilian politicians who reacted to them. And many of the politicians and journalists who de Moraes is demonizing as “extremist” are advocates of freedom of speech, including the right to criticize de Moraes. It’s true that some of the people who de Moraes is censoring have urged a military intervention and have made unsubstantiated claims about elections and Covid. I do not agree with many of the statements made by the people whom de Moraes has censored. But freedom of speech means nothing if it does not protect people and ideas you disagree with. If we aren’t going to allow people to criticize democracy, elections, and vaccines, how will we ever know if they are bad? If people are spreading false information about democracy, elections, and vaccines, the best way to deal with the false information is with accurate information, not censorship. The real extremist spreading disinformation here is de Moraes. If Musk were solely motivated by money, then he would not have stood up to de Moraes, which resulted in the Brazilian government halting all advertising on X, the resignation of X’s top lawyer in Brazil, who feared for his safety, and may result in de Moraes shutting down X in Brazil. He is not simply demanding that social media platforms censor specific content by controversial journalists and politicians. He is demanding that all social media platforms ban them for life. He often does so through secret hearings without the right of appeal. In fact, it’s all much worse than that. You can’t be a politician or journalist if you can’t communicate on social media. And so de Moraes is not just violating the Brazilian constitution’s protections of free speech, he is also attacking the freedom of the press, destroying careers, and interfering in elections. De Moraes has acted unilaterally to invent entirely new laws. He is thus interfering and taking over the role of Congress and of the president. That means he is behaving like a dictator. And now de Moraes has weaponized the Federal Police, including against me, for publishing the Twitter Files in Brazil. The Federal Police delivered two reports to de Moraes, one on April 18 and the other on April 19. The reports consist of a gigantic conspiracy theory, suggesting connections and relationships that simply do not exist. The reports single me out and suggest it is somehow suspicious that I only have paid for one subscription on X, which is to Elon Musk. But there is nothing suspicious about this. I am paying Musk, not the other way around. And, as the Police report notes, Musk takes a percentage of the revenue of the people who subscribe to my content on X. And the reports claim that people who de Moraes had demanded be censored had gained limited access to communicate on X, in particular through X’s Spaces, which allows for live conversation. In other words, de Moraes is totally obsessed with silencing his enemies. It’s not enough for X to have blocked profiles. He also doesn’t want them to be able to use their voice. It helps that the Brazilian government directly pays the Brazilian news media. The new Lula government increased government funding by 60% for Globo alone. Globo is the biggest media in Brazil. It has been demanding more censorship and running propaganda for de Moraes. De Moraes is a brutish authoritarian. His censorship is as bad as the censorship imposed by Brazil’s military dictators. He is seeking, as a judge, to eliminate particularly politicians and journalists from public life. This is hardly the first time de Moraes has weaponized the Federal Police. And in calling Elon Musk a foreign mercantilist, de Moraes is using the exact same kind of nationalist rhetoric that he has attacked his enemies for using. Why does Moraes have so much power? In Brazil, people told me it was because de Moraes controls so many court cases involving rich and powerful people, including politicians and other judges. The solution is for Brazil’s Congress to open an investigation, known as a Parliamentary Commission of Inquiry (CPI). A CPI can evaluate judicial abuses of power, and that is obviously what is happening here. Under a CPI, Brazil’s Congress could gain access to communications between police and judges or anyone else. A CPI could also hear from the victims of censorship. It could bring light to thousands of cases under secrecy. And it could discover how social media platforms were compelled to obey or collaborate with the regime. Musk has taken extraordinary and historic actions to protect free speech. So, too has the US Congress. Now it’s time for Brazil’s Congress to act against the anti-democratic extremism of de Moraes. It must do so before the extremist de Moraes starts arresting his political enemies and shuts down X, and thus free speech, in Brazil.

Michael Shellenberger

12,409,279 Aufrufe • vor 2 Jahren

CANCEL Your Weekend Plans and Learn Vibe Coding Today, Start Making $10,000/Month Building Apps for People. $0 in Coding Experience. I made 5 AI Trading Bots & Apps Built in 6 Hours. Each One Worth $3,000-$15,000 to Clients. You Spent $500 on a Bootcamp and Still Can't Deploy a Landing Page. That's not the bootcamp's fault. That's you. People with zero coding skills are building full apps with payments, databases, and authentication using AI. Charging clients $5,000-$10,000 per project. Finishing in one afternoon. You're still Googling "should I learn Python or JavaScript first." This attached video is a goldmine. 6 hours. 5 real apps. From complete beginner to deploying revenue-generating products. One video. Free. Save it. Watch it this weekend. Not next weekend. Today. Now let me break down exactly what's inside and why you can't afford to ignore this. Save this post. You'll hate yourself if you lose it. ↓ Let's talk about why you still can't code... You bought the Udemy course. $12.99. Watched 3 lectures. Got confused. Told yourself you'd continue tomorrow. That was 8 months ago. You bought another course. $49.99. This one had better reviews. Watched the intro. Bookmarked the rest. Never opened it again. You signed up for a bootcamp. $5,000. Dropped out at week 4 because "life got busy." Life didn't get busy. You got scared. Three years. Hundreds of dollars. Multiple courses. Zero apps built. Zero projects deployed. Zero revenue generated. And now someone with zero coding experience is building full apps in hours using AI tools you haven't even tried. You're not falling behind slowly. You're falling behind at full speed. Save this post right now. This is the course that makes every other coding course you bought irrelevant. Follow Himanshu Kumar so you don't miss the breakdown. ↓ What is vibe coding and why should you care? Traditional coding: Learn syntax for 6 months. Build a to-do app. Feel proud. Realize nobody will pay for a to-do app. Give up. Vibe coding: Describe what you want to build. AI builds it. You guide, adjust, deploy. People pay for it. You're not writing code line by line. You're directing an AI agent that writes code for you. Think of it like this: Traditional coding = you're the construction worker. Vibe coding = you're the architect. The architect makes more money. The architect doesn't carry bricks. The architect doesn't need to know how to pour concrete. The architect needs to know what to build and why. That's vibe coding. And while you've been debating whether to learn Python or JavaScript first, people are skipping both and building apps that generate revenue. With zero coding knowledge. This isn't the future. This is right now. Save this post and follow Himanshu Kumar for more vibe coding breakdowns that actually make you money. ↓ What this 6-hour course covers. This isn't some 20-minute tutorial that shows you how to make a button change color. This is 6 hours. 5 complete apps. Real software engineering. Real deployment. Real money-making potential. Here's what you'll build: > Portfolio website - deployed live on Netlify > Full-stack client dashboard - with database and auth > Lead generation app - with API integrations > Thumbnail generator - with payment integration via Stripe > Splinter - a full SaaS product with pricing and marketing Not toy projects. Not "follow along and never use again." Actual apps that people pay for. Built with Gemini 3.1 Pro, Antigravity, Supabase, Next.js, Vite, and more. You know how many people charge $5,000+ to build a single one of these apps for a client? You'll be able to build all 5 by the end of this weekend. You can't afford to scroll past this. Bookmark this post. Follow Himanshu Kumar because I'm breaking down every tool in this stack separately. ↓ The tools you'll master. Gemini 3.1 Pro: Google's most powerful AI model. You'll use it to generate entire codebases. Not snippets. Entire apps. Antigravity: The AI coding environment that makes vibe coding actually work. Agent chat. MCP servers. Voice dictation. It's not VS Code with a chatbot bolted on. It's built from the ground up for AI-first development. Supabase: Your backend. Database. Authentication. All set up in minutes. Not weeks of configuration. Next.js + Vite: Modern frameworks that make your apps fast, scalable, and professional. Stripe: Payment integration. So your apps can actually charge people money. You know, the whole point. Claude Code: Yes, Claude Code is covered too. Because the best developers in 2026 don't use one AI tool. They use all of them. While you're still trying to decide which AI tool is "the best one," smart people are using all of them together and making money from every angle. Stop debating tools. Start using them. Save this post and follow Himanshu Kumar for deep dives into each of these tools. ↓ What you'll actually learn beyond just "building apps." This course doesn't just teach you to copy and paste prompts. You'll learn real software engineering: > Hosting and deployment > Modern software design patterns > Languages and frameworks > Version control and GitHub > Programming with AI agents and agent teams > Database design (SQL vs NoSQL) > Security audits > API integration > Payment processing This is everything a $15,000 bootcamp teaches. In 6 hours. For free. On YouTube. Your friend who spent $15K on a bootcamp is going to be really upset when you build better apps than them after watching one YouTube video this weekend. Don't tell them about this course. Or do. Their reaction will be priceless. This is a $15,000 education for $0. Save this post before it gets buried. Follow Himanshu Kumar for more free resources that make paid courses look like scams. ↓ The guy teaching this actually makes money. Not "makes money selling courses about making money." Actually makes money. Nick built automated businesses with Make . Most notably 1SecondCopy, a content company that hit 7 figures. Seven figures. From automation. He's not teaching theory. He's showing you what real systems that generate real revenue look like. 90% of coding teachers on YouTube have never shipped a product that made $1. They teach coding. They don't use coding to make money. This guy does both. That's why this course is different. You've been learning from people who teach for a living. Start learning from people who build for a living. Save this post. Follow Himanshu Kumar for more content from builders, not lecturers. ↓ Let me tell you what's really happening while you "think about learning to code." Every week that passes, AI coding tools get better. Every week that passes, more people learn vibe coding. Every week that passes, the market gets more competitive. Right now, vibe coding is still early. Not many people know how to do it well. Clients are desperate for someone who can build apps fast. $3,000 for a landing page with payments. $5,000 for a SaaS MVP. $10,000 for a full client dashboard. These are real prices people are charging for apps they built in a single day using the exact tools in this course. But this window won't last forever. In 6 months, everyone will know how to vibe code. In 12 months, it'll be a basic requirement. In 24 months, not knowing this will be like not knowing how to use email in 2010. You're either early or you're irrelevant. Right now you can still be early. But not if you spend this weekend on Netflix. The window is closing. Every weekend you waste is a weekend someone else uses to get ahead of you. Save this post. Follow Himanshu Kumar before this opportunity becomes obvious to everyone. ↓ The 5 apps you'll build and what they're actually worth. App 1: Portfolio Website. What clients pay for this: $500-$2,000. Time to build with vibe coding: 30 minutes. App 2: Client Dashboard. What clients pay for this: $5,000-$15,000. Time to build with vibe coding: 2-3 hours. App 3: Lead Generation Tool. What clients pay for this: $3,000-$8,000. Time to build with vibe coding: 1-2 hours. App 4: Thumbnail Generator with Payments. What clients pay for this: $2,000-$5,000. Or sell it as a SaaS for recurring revenue. Time to build: 1-2 hours. App 5: Splinter (Full SaaS Product). What clients pay for this: $10,000-$25,000. Or launch it yourself for monthly recurring revenue. Time to build: 2-3 hours. Total value of apps you can build after this course: $20,000-$55,000. Total cost of this course: $0. Total time investment: one weekend. You spend more than one weekend deciding which Netflix show to start next. At least this weekend would pay you back. Read those numbers again. Save this post. Follow Himanshu Kumar because I'll be breaking down how to sell each of these apps as a service. ↓ Here's the business model nobody's talking about. Learn vibe coding this weekend. Build 5 apps. Pick the one you're best at. Offer it as a service. "I build professional SaaS dashboards for businesses using AI. Faster than agencies. Fraction of the cost. $5,000 per project." 2 projects per month = $10,000/month. Working maybe 20 hours total. While you're applying for jobs that pay $4,000/month and require 5 years of experience you don't have, someone who watched this course last weekend just landed their second $5,000 client. No degree. No portfolio. No 5 years of experience. Just the ability to build what people need faster than anyone else. That's the entire business model. Learn fast. Build fast. Charge accordingly. Stop applying for jobs. Start creating them. Save this post. Follow Himanshu Kumar for the exact outreach scripts to land your first vibe coding client. ↓ Why you won't watch this course. Because it's 6 hours. "6 hours?? That's too long." You binged an entire season of a show last weekend in 8 hours. You scrolled Twitter for 4 hours yesterday. You spent 3 hours watching YouTube shorts that you don't even remember. But 6 hours to learn a skill that could make you $10,000/month? "I don't have time for that." You have time. You just don't have discipline. And that's the actual reason you're broke. Not the economy. Not the market. Not your circumstances. Your inability to sit down for 6 hours and learn something that changes your life. Everything else is a story you tell yourself to feel better about doing nothing. That's the uncomfortable truth. Save this post so it stares at you every time you open your bookmarks. Follow Himanshu Kumar because I'll keep reminding you until you actually do something. ↓ What happens this weekend determines your next year. Path A: Watch the course Saturday. Build your first app Sunday. Start offering services Monday. Land first client within 2 weeks. $5,000-$10,000/month within 60 days. Path B: Sleep in Saturday. Brunch Sunday. Netflix Sunday night. Monday morning alarm goes off. Back to the same job. Same salary. Same frustration. Same "I'll start next weekend." 52 weekends in a year. How many have you already wasted? Path A costs you one weekend. Path B costs you your entire future. Same video. Same information. Same 6 hours. Two completely different lives. ↓ Full 6-hour course attached. 5 real apps. Real deployment. Real revenue potential. From the guy who built a 7-figure automated business. Not theory. Not motivation. Actual hands-on building. The course is free. The tools are free. The knowledge is right here. The only thing that costs money is your decision to do nothing. And that cost compounds every single day. Follow Himanshu Kumar for more breakdowns that turn free YouTube videos into $10,000/month skill sets. Save this post. Watch the video. Build something this weekend that your Monday self will thank you for. Or don't. And wonder next year why nothing changed.

Himanshu Kumar

39,379 Aufrufe • vor 4 Monaten

A QUICK TECH FIX TO BYPASS THE TEDIOUS MANUAL SEARCH IN SIR DRAFT ROLL–2026 Tired of manually scanning ~1,000 names in the SIR Draft Roll–2026 just to check whether your name exists? Here’s a simple workaround. 🔹 Download the PDF of the SIR–2026 Draft Roll for your Polling Station 🔹 Right-click → Open with the latest version of Google Chrome (Desktop/Laptop only) 🔹 Chrome magically makes the PDF searchable, even though the Spokesperson ECI had rendered it machine non-readable on almost all standard PDF readers, including Adobe. 👉 This means Ctrl + F works in Chrome, sparing you the eye-straining, page-by-page hunt. I am attaching screen recording. Trust me: I spent nearly 15 minutes manually scanning every page of the correct polling booth and still couldn’t find my name. This trick worked instantly. #GyaneshKumar certainly makes life “interesting” for those of us who enjoy pushing technology to its limits 😃 Background (Why this hack is needed): ✅ Since 2023, Election Commission of India has been issuing Electoral Rolls in machine non-readable PDFs. As a result, searching names using Ctrl+F is disabled on most PDF readers. ✅ Shockingly, even EPIC numbers are not searchable in the SIR Draft Roll PDFs, arguably in violation of directions of the #SupremeCourtofIndia, making verification unnecessarily cumbersome. ✅ Searching by EPIC number or personal details on only gives the serial number in the existing Electoral Roll, which may not match the serial number in the SIR Draft Roll–2026, because: Some voters above you may not have submitted enrolment forms, or Their data could not be mapped till now with the 2002–03 SIR database. ✅ Opening the PDF in the latest Chrome (Desktop) solves this problem. ✅ For Indian language rolls (including Hindi), use a Unicode-enabled keyboard such as the Microsoft Indic Language Input Tool or similar. ⚠️ Note: This workaround works on a PC/laptop only. The mobile version of Chrome doesn’t support this yet, maybe a future update will. So, Jagat Prakash Nadda Mallikarjun Kharge Mamata Banerjee M.K.Stalin - தமிழ்நாட்டை தலைகுனிய விடமாட்டேன் Rahul Gandhi Pinarayi Vijayan may also want to run some quick data analytics using this very trick. Incidentally, there are simple and well-established tools through which such electoral roll PDFs can be made fully machine-readable. This is precisely what Nitin Sethi and his team demonstrated while identifying over 14 lakh duplicate voters in #BiharSIR2025. In an era where data analytics, AI, and OCR tools are routine, it is difficult to comprehend why the Election Commission of India continues to insist on issuing non-searchable electoral rolls, by relying on a narrow interpretation of the Kamal Nath judgment (2018) on Electoral Rolls. Transparency, verifiability, and ease of access are core democratic values, not optional conveniences. Purity of electoral rolls must take precedence over individual privacy. After all, the Electoral Roll only has age and address. A democracy survives on one person–one vote, not on opacity disguised as data protection. Free and fair elections are a constitutional imperative and that requires a publicly verifiable Electoral Rolls. 🙏 CEO Uttar Pradesh CEO West Bengal Chief Electoral Officer, Chhattisgarh CEO RAJASTHAN Maneesh Garg IAS Rajdeep ThePrintIndia Chief Electoral Officer Tamil Nadu may also want to have a look.

Sanjeev Gupta

31,201 Aufrufe • vor 6 Monaten

Moneytaur study blueprint 🗺️ The process I used to go from not knowing what an order block is to pulling cash from the crypto markets in under 6 months using 🎯 Master concepts. Proof of performance, past 120 days👇 Start date: 09/03/2025 Requirements: - A PC/laptop - Wifi - A basic understanding of trading. ( What candlesticks are, how to actually place trades , etc ) - A free mind - Time or the ability to free up time. Starting: - Structure and routine - Stick to that routine + Pre mortem plan. - Notion / Obsidian setup. The first thing you need to create is a clear routine moulded around how you intend to approach this very large and complex task. This will not be linear and you will naturally adapt it as you progress but especially in the beginning some resemblance of structure each day is vital. This is an individual process but it is important to understand from the beginning that this will require a majority of your free time assuming you work a full time Job or study as a student. For me in the beginning this looked like: - Wake up at 6:30. - Shower - Study/work for 1h 45m before leaving for work. - 09:00 -> 17:00 work - 17:30 Exercise / Train - Eat - 19:00 resume study/work - 22:30 Start to wind down and get ready to sleep. It changed several times over the months and especially now I am full time but this is irrelevant, the only thing that matters is sticking with what you choose. Whatever your own routine may look like, it is important to understand it will inevitably require sacrifice. --- The next thing once you have established a draft framework of your routine is ensuring you will actually stick to that routine. Something I implemented which I found particularly beneficial was the concept of a Pre-Mortem plan. This involves creating several scenarios of a future in which you have failed and working backwards from each of these to find where it went wrong. Here is a video which explains it fully: When I did this I came up with 3 scenarios as well as prevention and cure for each. In the 6 months that followed each scenario presented at some point but I was able to catch them early due to having done this. The last thing is to not over complicate this, don't hyper focus on systems and loose momentum optimizing each detail. Just ensure you do the fucking work. I was a little guilty of the above at times, trying to craft the perfect routine. In reality the person who just gets up, drinks too much coffee and works his ass off out performs the workflow perfectionist who visualizes and repeats affirmations, any day of the week. --- Next you need somewhere to store your notes, journal your trades and build your knowledge. For me this was Obsidian but I have also used Notion before and it is an equally viable option. Whichever one of these you choose be warned you will inevitably want to bang your head against a wall trying to use them for the first few days, but they will both click pretty quick and are 100% better options the word document or paper alternative. Here is my full obsidian setup tutorial: Here is a link to MisterPA 's notion Journal: Here is how I create "Meta-Notes" using obsidian: The process: - How I did it. - How I would do it if doing it again. Now I did things the "hard way" and manually worked my way back through each of MT's tweets starting in 2021, reading every one and logging those that I felt where relevant. You can see in my first post: the very first system I used to do this. I quickly adapted though after about a week and focused less on just logging each relevant tweet but trying to find and focusing on those which contained the most information. There where a lot of charts I looked at then skipped over because especially at the start of his timeline they contained little useful information and my time was better spent finding those where there was something to decode. Now this does not mean skip out on "work" just use your time efficiently. -- If however if I was to start from the beginning again with the goal of levelling up technical understanding as quickly as possible I would take a different approach. To start with I would familiarise myself with all relevant SMC concepts, I have linked the best free recourses for this below 👇 CryptoChase beginner friendly index: Barncore's "The Moneytaur Way" series: Gian Luca's Trading bootcamp playlist: Following this I would then work through all of Taur's subscription posts working backwards, recreating his charts and taking notes on his logic. The subscription feed has the highest value density and least noise. Video example of my notes from his subscription posts 👇: --- Okay so now once you have a basic understanding of concepts and can re-recreate them on charts of your own it is time to put this in to practice. The next step is vigorous backtesting, you can use the trading view tool but I think trade Zella offers a more use friendly option if you pay for the subscription. Especially as it allows you to change timeframes without skipping ahead to candle close time of the timeframe you change too ( like Trading view does ) *my only note would be that their LTF/Micro TF data feed with be different to brokerage charts you will use on Trading view, to start with though you should not be going low enough that this is an issue. When you backtest in this context, treat it like real trading. That means journal and logging like you would if real cash was on the line. Take time, do not rush and focus on quality. Stick to BTC, ETH, Major FX pairs or indices as these assets are less reliant on confluence, backtesting a shitcoin is near useless as whether levels work or not will be highly dependent on Majors PA. Go on HTF, scroll back a couple years and try not too look at chart while doing so and then begin. Start with HTF analysis and work down to 2H or wherever you feel comfortable, chart it fully and then identify setups. Make rough notes / plans and then press play, execute the setups as they hit, log and journal trade management as well as observations and key notes. It is very important to not cheat when you do this, do not skip back and adjust your stoploss because it hit by 0.1%, do not skip back and adjust plan because you missed a block and your TP got frontrun. Instead these are the things you journal, embrace these mistakes because they are the cheapest mistakes you are going to make. Grind this, do it for hours, put some music on and enjoy. To start with focus on HTF's, as you get better and start netting $ on paper you can drop the timeframes and increase the difficulty. HTF = Normal, MTF = Medium, LTF = Hard. Even if you do not intend to day trade, learning how to read the lower TF's that force you to think faster, harder and prepare you for lower win rates / loss streaks can greatly improve your ability on higher TF's. While you are doing this as you start to have concepts click you now want to build up your real trading experience, take a sum of money that you care about but will be okay loosing and dedicate this to live trading. Start taking real trades and expect net losses in the beginning. This is where you will make you 2nd cheapest mistakes. This is also where you can begin to learn about your psychology. You may encounter some elements already in backtesting but the real market is where true colours really start to show. Mental issues are inevitable and part of the game, get used to them and start working to identify and fix them. Reading and applying books like Trading in the Zone and Mental Game of Trading are important and will help a lot but there is no easy fix, for some stuff you I believe you just have to get used to it and it goes away with experience. Losses suck at the beginning but after you loose 100 times you starting getting pretty numb to it, same goes for the winners. To accelerate the learning process, build connections and get advice there is also always the option of private groups, while I never personally chose this route and committed to learning everything through my own endeavours there is no denying that having nearly all the information you need structured and compiled in one place is valuable and can save time. Beyond this having access to real time thoughts and opinions of profitable traders can accelerate performance, however it carries the risk of being a double edged sword if not used properly, if relying on it like a crutch and using it as a substitute for real work you will not succeed. With that said if you take it for what it is, a learning opportunity then I believe it can be very beneficial. I am not a member of, nor affiliated with any paid group. There are now many options available within the community, all run by different people with different styles, tailored to different needs. If I was to make a recommendation though, as a non-member, it would be Albert & Co's 618'ers simply due to the diversity in styles of the traders running it and results I have seen from members I know personally. It is important that as you start to trade with real capital you reduce noise in your social feeds or eliminate it all together. You do not need 5 different opinions, you also do not need 2 people telling you the same thing in their own way so you feel re-assured. What you do need is to develop your independent thinking as a trader and be comfortable making different decisions to others, even traders ahead of yourself if it fits with your system or understanding of market. Taur here is perhaps an exception as this is who you are learning from but down the line a real test of your own ability and independence will be being able to stick with your own plan even when it differs from his. Don't get me wrong, counter trading him is retarded but you must learn to adapt his gift to your own style. This will make sense at some point. The next stage is taking your understanding of specific concepts to higher level as you simultaneously snowball experience. Look back through your journal and review where you lost money and made money, do not over extrapolate from a small sample but start to take notes and observe if trends in performance emerge. This is the beginning of the transition to self reliance, you now understand the strategy but must learn for yourself when and where it works. Here you can also learn more nuanced secondary concepts such as VSA, orderflow etc and add these to your game where appropriate. Do NOT get lost in the sauce though and remember mastery of basics is key. IMO a big focus should be understanding correlation thoroughly but especially on HTF's this is the most important thing and what triggers the majority of large swings where most of your cash will be made and losses recovered. Some people will disagree with me here but IMO you should also not be *focusing* on Odd TF's. These are secondary at best and most people overweight their significance leading to avoidable losses while wondering why price did not care about their 327minute Breaker Block which they think is the key to the market. Study Taurs feed and take note of how he mostly uses: 3M, 1M, 3W, 2W, 1W, 5D, 4D, 3D, 2D, 1D, 12H, 8H, 6H, 4H, 2H, 1H, 30m, 15m + micro time frames. The only thing left is time and repetition, you must show up each day and really do this, for months. Maybe you start to see result's, you catch your first key swing and where able to trade where others froze. Congratulations. Learn from these winners and repeat the actions. Find what assets work best for you, find your style, refine and grow. --- The last thing I will include is a short list of tools or links that can be helpful. - Trading view tutorial: - Dictionary: - Market news Calendar: --- Thank you too all those who have read this, I hope this has been helpful for the beginners who want to start but are just not sure how. 🫶 Don't just bookmark this and move on, start 🙃

Ace

45,054 Aufrufe • vor 8 Monaten

Israel Moved Gaza’s Yellow Line And Then Shelled Palestinians For Being On The Wrong Side Drop Site News reports that the IDF quietly moved part of the “yellow line” which divides Gaza 300 meters forward, and then started shelling Palestinians for being on the “wrong side” of the line. They just keep finding new ways to carve off more pieces of Gaza and murder more Palestinians. ❖ Haaretz has a disturbing story out about a 14 year-old Palestinian boy who was waiting for his school bus in the West Bank on a quiet street eating a cookie, when suddenly a bunch of IDF vehicles pulled up and a soldier shot him directly in the face with a teargas canister. Then they sped off. The boy lost his right eye in the attack. Israelis will just casually shoot a Palestinian kid in the fucking face for no fucking reason, and then go online and call you hateful for opposing them. ❖ Leftists are going to hate Israel for leftist reasons and rightists are going to hate Israel for rightist reasons. This is not a difference that needs to be reconciled or a problem that needs to be solved. Some groyper hating the same genocidal apartheid state I hate doesn’t say anything about me or my politics anymore than our having the same opinion on the importance of dental hygiene. It doesn’t make me the same as him. It doesn’t make him my friend. It doesn’t mean I have to be nice to him. It doesn’t mean I have to stop opposing Israel and its atrocities. It doesn’t mean I am obligated to do anything to protect Israel from the western rightists who’ve been turning against it in rapidly increasing numbers. It doesn’t mean anything. It just is what it is. You’ll see Israel supporters point to the rising number of rightists who oppose Israel and trying to marry it to pro-Palestine leftists in some way. I recently saw former Israeli spokesman Eylon Levy claiming that antizionism “builds coalitions on both extremes — and increasingly between them — by mobilizing politics against Jews.” But that’s just some nonsense they’re making up in order to justify their genocidal atrocities. Leftist opposition to Israel is about justice, equality, anticolonialism, antiracism, anti-imperialism, antiwar and anti-apartheid activism, and has nothing whatsoever to do with hating Jews. Rightist opposition to Israel is more about nationalism, anti-interventionism, America First ideology, and yes, in many cases a hatred of Jews. These are two completely different things. You never saw Zionists bitching about the far right until they started pivoting against Israel; until then they were happy to make alliances with them, and still are as long as they remain supportive of Israel. And half the time you see them citing anti-Israel sentiments on the right it’s only to play guilt-by-association by framing them as the same as the pro-Palestine left. It’s just more empty narrative-diddling from Israel apologists. It’s not a real argument, and doesn’t require a counter-argument. It’s just them flailing around trying anything they can to stop the entire western political spectrum from flushing Israel down the toilet. ❖ New York Times war propagandist Bret Stephens has a new article out titled “The Case for Overthrowing Maduro” in which he argues for US regime change interventionism in Venezuela on the basis that “the regime’s close economic and strategic ties to China, Russia and Iran give America’s enemies a significant foothold in the Americas.” This would be the same Bret Stephens who in 2023 wrote an article in the New York Times titled “20 Years On, I Don’t Regret Supporting the Iraq War,” by the way. On a related note, the leftist outlet Current Affairs presently has a special going where if you cancel your New York Times subscription and send proof of cancelation to [email protected] right now, you’ll get a free year-long digital subscription to their vastly superior publication. ❖ Right wingers think a mother should be at home raising her children, an arrangement that many mothers would be on board with, but if you say this requires either state support or for employers to be forced to increase pay so that single-income families can exist they say “No that’s socialism!” They want the mothers to stay at home while the fathers work 80-hour work weeks for ten bucks an hour so that billionaires can become trillionaires. ❖ Elon Musk says that in 10 to 20 years work will be optional and money will be meaningless because AI and automation will eliminate the need for labor and make everything wonderful. Something tells me the guy who just took a trillion-dollar pay package from Tesla doesn’t really believe money is going to be meaningless anytime soon. This soon-to-be-trillionaire whose ego is so fragile and infantile that his AI chatbot tells people he’s smarter than da Vinci and more athletic than LeBron James is asking us to believe that revolutionary change isn’t necessary because capitalists like himself are going to fix it so that everyone lives in luxury. Yeah sure, buddy. A likely story. ❖ OpenAI reportedly plans on building 250 gigawatts of capacity by 2033 to use for its energy-consuming servers, about the same amount of electricity that’s used by 1.5 billion people in India. So, no. No to this. Your right to extend your fist ends at my nose. You don’t get to just add this giant burden to the already severely overburdened ecosystem we all depend on for survival in order to expand your chatbot project. The collective is entitled to stop you. By force. Reading by Tim Foley:

Caitlin Johnstone

36,316 Aufrufe • vor 8 Monaten