Sensitive content

This media may contain sensitive content.

Loading video...

Video Failed to Load

Go Home

Let's call it a month, yeah?๐Ÿ˜‹โค๏ธ๐Ÿ”„ #Blaziken by Choco's corner ๐Ÿ”ž Comms: Model closed 1/1 #Umbreon by blendrdragon in smutbase VA PACK Fury The Red Demon ๐Ÿ”ž | โ™‚๏ธ | DEBUT ARC! SFX PACK OpenNSFW ๐ŸŸฃ Available Now / LeHornySFX3D๐Ÿ”ž (COMMS OPEN) #pokemon #rule34gay #nsfw

78,907 views โ€ข 3 months ago โ€ขvia X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

You guys asked for a deeper sim and that's what 2.9 is. Submitted. Rebuilt Avatars: Player avatars completely redone. 14 hairstyles, 8 skin tones, 6 hair colors, beard options, all at higher resolution. Over 50,000 combinations across the 4,700+ players the game generates. Coach avatars got the same revamp. Player Cards: Cards rebuilt from scratch to feel like a broadcast graphic. Team-color gradient hero that pulls each program's actual colors, oversized OVR display, archetype line, headline stat strip, and tabs for stats, ratings, game logs, and bio. Coaching Systems: Biggest gameplay shift in this build. You pick an offensive scheme and a defensive scheme and they change how your team plays. 6 offensive options (Run & Gun, Motion, Pick & Roll, Princeton, Post-Centric, Balanced) and 6 defensive options (Man, 2-3, 3-2, 1-3-1, Press/Trap, Pack Line). Run & Gun teams shoot more threes and turn the ball over more. Pack Line teams give up fewer paint points but allow more open looks. Same modifiers run in live games and background sims so your scheme matters either way. Scout Cards: Tap any team and you can now see their offensive and defensive playstyle laid out in full. Real game-planning is finally possible. Facing a Press team, you can scheme around it. Facing a 2-3 zone, you can prep your shooters. Pull up an opponent before tipoff and actually know what you're up against. Recruiting Pipelines: Recruit generation now mirrors real basketball geography. Top talent clusters in real hotbeds. Class rank, position rank, and state rank show on every recruit. All-American badges flag elite prospects and State Player of the Year badges call out standouts in smaller states, but neither is an auto cheat code. An All-American is a strong prospect on paper, development still matters, and not every one pans out. State POY varies a lot by state. The real edge is taking a job in a strong pipeline state. Better states produce better players more often, and coaching in a hotbed gives you home state advantage on recruits everyone else is fighting over. Smarter Rankings + Bug Fixes: Rankings rebuilt to reflect who's actually playing the best. Quality wins matter, strength of schedule matters, bad losses hurt. Plus a long list of bug fixes from your Discord reports. If you posted a bug, it's been looked at even if I didn't reply directly. Android: Thank you for everyone who has been testing! We have finally got aversion that is ready for release and I am submitting it right now! I will keep you guys updated on when it dropsโค๏ธ

Hardwood Empire

33,684 views โ€ข 5 months ago

a deported Chinese dev at a Starbucks showed me his screen and said "you have 6 seconds" he was sitting in the corner. two phones. one laptop. hood up. looked like he hadn't slept in days. i sat down next to him because every other seat was taken. he saw my screen. Polymarket open. "you trade these BTC markets?" yeah. 5-minute binaries. he turned his laptop toward me. "you see how the result settles? every 5-minute BTC market resolves based on an oracle. the oracle reads the price from an API. but the oracle doesn't update instantly. there's a lag. 4 to 6 seconds" "in those 6 seconds the real BTC price already moved. but the market is still open. still accepting orders. priced on the old number" he pointed at his screen. two windows side by side. left: Binance BTC spot feed. right: Polymarket orderbook. 3,200 stars. decentralized oracle framework. he had it forked on his laptop. the entire oracle timing model was exposed in the source code. "right now BTC is at $100,240 on Binance. the oracle still shows $100,190. the market 'BTC above $100,200 at 3:05pm' is trading YES at 41 cents" "but i already know the answer is YES. because i see the real price. the oracle doesn't. for 6 seconds i'm trading against a blind counterparty" watched him buy YES at 41c. four seconds later the oracle updated. market resolved YES. payout $1. "59 cents in 4 seconds. this happens every 5 minutes. 288 times a day" asked how he found this. "i was an oracle engineer at Chainlink in Shanghai. got deported for visa issues. took the knowledge with me" "every oracle has a heartbeat interval. a deviation threshold. a propagation delay. i know exactly how long each one takes to update. because i built three of them" he closed his laptop. "the edge isn't in the market. it's in the infrastructure layer between the real price and the reported price. nobody looks there. because nobody understands how oracles work" finished his coffee. left. didn't get his name. didn't need it. flew home. opened Claude. "build an oracle latency exploitation engine for Polymarket BTC binaries. track real-time BTC spot price from Binance websocket feed. compare against Polymarket oracle update timestamps. detect windows where oracle lags behind spot by more than $30. enter the side that the real price already confirmed. target the 4-6 second blind window before each oracle heartbeat." the system was live by morning. named it DEEP SIGNAL. first fill hit before i finished coffee. > Binance websocket feed at 50ms intervals. > oracle heartbeat monitor. > propagation delay calculator. > spot-to-oracle divergence detector. > conviction gate at $30+ deviation. > order placement avg 47ms. $534K volume. 79% win rate. sharpe 3.64. drawdown -1.2%. +$11,681 in profit runs on: Claude $20. VPS $5. UMA protocol free. $25/month. copytrade setup here: went back to that Starbucks a week later. same corner. empty. but the oracle still lags. every 5 minutes. every day. 6 seconds is all you need when you can see what the oracle can't.

Hanako

32,681 views โ€ข 5 months ago

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

Himanshu Kumar

13,677 views โ€ข 5 months ago

The story of what happened to Henry Hill after the events of Goodfellas is arguably just as interesting as what took place in the film, albeit more tragic. Despite what a lot of people believe, Henry was only in the witness protection program for two years. Ed McDonald, the prosecutor who helped turn Hill into a cooperating witness - and who also played himself in Goodfellas - explained what happened to him afterwards. โ€œI canโ€™t tell you how many times a month I read that Henry Hill was in the program for seven years, Henry Hill was in the program for six years, Henry Hill was in the program for ten years. Henry goes into the program in June of 1980โ€ฆ In August of 1981, Henry was in his third city. So he had blown Omaha, he had blown the suburbs of Cincinnati and Kentucky, and he was now in Seattle. And I get a phone call from Washington and they said, โ€˜Heโ€™s blown it again. Heโ€™s done.โ€™ I go down, I plead with them. They said, โ€˜Look, heโ€™s out. Heโ€™s out as of September 1st. We will fund him through the end of the year so he can have the wherewithal to be testifying at the point-shaving case. But after that, heโ€™s done.โ€™ By the 1st of January, 1982, Henry was out of the witness protection program. This is when I come in, and Iโ€™m sort of like Henryโ€™s guardian angel. I went to Steve Carbone of the FBI and I said, โ€˜Heโ€™s working on all these cases because he cooperated in many cases for us. The witness protection program and the Justice Department are not going to do it anymore. Can the Bureau come up with some money?โ€™ So the Bureau came up with money to support him for about six months, and then the Bureau pulled the plug. I had a friend at the New York City Police Department, a detective who did homicide cases in organized crime matters. And we worked out a deal where weโ€™d bring Henry in, and Henry would talk about organized crime murders. And for every murder that they could close, Henry would get paid some money. I donโ€™t remember what it was. It was probably $500 or $1,000. And at one point, I said to Henry, โ€˜Who have you been identifying as being responsible for these organized crime murders?โ€™ There were like 30 of them. He started telling me the names of the people, and the vast majority of the people he identified were dead. They were people who had been killed themselvesโ€ฆ So the detectives were closing the cases, which means that they get credit for solving a murder. But they didnโ€™t necessarily solve the murder - I think they were allowing wise guys who were responsible to go scot-free. So it was kind of crazy. But that sort of dried up by 1984, 1985. At that point, Henry had no support from the government any longer. And at the time, he was doing crazy stuff. He was getting arrested. Mostly, what he was getting arrested for was the result of alcoholism. Heโ€™d go out and go to a bar and get blind drunk, then go out and drive and get arrested for DWI. And then maybe heโ€™d throw a punch at the cops. And one time I called the prosecutor in Kansas or someplace, and I said, โ€˜What happened?โ€™ They said, โ€˜Well, he was arrested for breaking and entering.โ€™ โ€˜They found him at a grocery store on the floor with a six-pack of beer. It was after the bars had closed. Henry wanted to keep drinking, so he broke into a grocery store and just went and got a six-pack.โ€™ I guess some alarm went off that Henry didnโ€™t hear, and they found him on the floor and arrested him for breaking and entering.โ€ It was crazy, sort of minor-league stuff until, I guess, late '87โ€ฆ (1/2)

Gangster Cinema Central

619,023 views โ€ข 25 days ago

Finally video emerges of an actual Ukrainian attack in Toretsk, two weeks after their supposed ninja counteroffensive kicked off... or is it?โฌ‡๏ธ I'm referring to this video, which was published Wednesday, showing the destruction of two AFU M113s withdrawing troops from a southern suburb of Toretsk (Zabalka) that basically all mappers had placed well inside Russian lines (video 1, see figure 3 for the map). Video emerged later that day of Russian infantry destroying an apparently Ukrainian-held house in the same area with a satchel charge after suppressing the defenders with an RPG and small arms (the first segment of video 2). Interesting, I thought. So I looked at the map again, harder. And then I looked at the geolocated positions of Russian units, which the TG channel Creamy Caprice keeps a map of (figure 3, showing the location of the first video - the red and blue dots mark Russian and Ukrainian positions logged over the entire course of the battle). And that's when it struck me - Russian troops have never been spotted in the northwestern corner of the Zabalka district. They've been seen in the central part and they've been seen around the slag heaps, but not the northwest corner. And there's a relatively short route into it through the Ukrainian-held forest to the northwest, although the last mile is through an open field around the base of (and dominated by) the nearby slag heap. It would be an extremely dangerous journey. Now we come to what the video actually depicts - the withdrawal of troops. The first APC is hit while withdrawing and the escaping dismounts are effectively engaged after going to ground in the forest. The second APC then arrives in Zabalka, loads up, and is heavily hit and knocked out as it withdraws. A couple soldiers are seen heading deeper into the city on foot as it departs, but not a full squad - there may not have been room for them on the transport, or they may have (correctly) thought their chances were better on foot. Then the subsequent video emerged of Russian infantry clearing holdouts in the area, which could have very well been those men. So what happened here? Well, I pointed out earlier that it's standard practice to back-clear an urban area after taking it, to clear bypassed enemy strongholds and booby-traps and render the area safe to support further operations. I suspect there was actually a pocket of bypassed Ukrainian troops holed up in the western Zabalka District, a couple kilometers behind Russian lines, whom the AFU command tried to evacuate via APC earlier this week while they still had the chance to do so. And the Russians may very well have allowed those APCs to pull in and load up so they could - as they did - very coldly kill them while they were packed with infantry to withdraw. Why did the Ukrainian command undertake such a high-risk operation instead of simply writing these men off and telling them that it was every man for himself? Probably because these were Azov fighters and thus entitled to special treatment and consideration - one of their brigades operates in the area. In any event, far from suggesting a Ukrainian counterattack into south Toretsk, this turn of events suggests to me that the Russians are instead mopping up remaining resistance in the city. (As an addendum, the people behind Creamy Caprice think that the third segment of video 2 shows Ukrainian activity somewhat farther into the northwest corner of the Zabalka Dictrict, but that segment also doesn't show live troops - for all we know they were bombing an AFU comms repeater or something on the roof of that building. The second segment of that video is old judging by the snow on the ground.)

Armchair Warlord

15,294 views โ€ข 1 year ago

OFFICIAL: EASTER EGG GUIDE FOR TOTENREICH: Wonder Weapon: 1. Head to The Drydocks and lower The Crane, this will allow you to wall jump and interact with the tip of the ship to pick up the Chain Link 2. Next, Head to Storm Bridge and pick up Chili Chunks behind the truck next to Deadshot 3. Place Chili Chunks on the table in the middle of the Skalen Market 4. Next, Head to Burial Grounds left-side door and interact with the keyhole. 5. Interact with the door again and hold it to open the door and to unlock the underground area. 6. This will spawn a Zursa Bear during a special round (starting the second special round) you need to kill him and he will drop The Lantern 7. Place The Lantern in the center of the Underground Room in Burial Grounds. 8. Constellations will appear around the wall. Interact with them as theyโ€™re shown on the table in this order: left, right, back, front. 9. Once completed, Astrid will appear and talk, she will then travel to different areas of the map. She will occasionally stop and you will need to kill frost zombies next to her. 10. Once all the Soulboxes are completed an Obstacle Course will form on the outside of The Lighthouse, climb to the top by Jumping / Wall Jumping up 11. Once you reach the top, Listen to the Astrid talk and pick up The Jotunn Star Wundersignal: 1. After completing Jotun Star Quest Head to The Lighthouse and inside on a shelf there will be a Crowbar 2. There are Multiple Wooden Boxes around the map with red IDs on the bottom right corner of the front of the box in red (for example III-6) use The Crowbar on the Wooden Box that has the Roboterteile ID (the IDs are on the shipping manifest in the War Factory Admin Room), this will give Flak Gun Round War Factory Core Foundry Fjord Road Dry Dock 3. Head to Turret Gun beside The Lighthouse and place Flak Gun Round then melee with Jotunn Star 4. Next, Head to The Robot Head in spawn and interact with it to search broken piece to get The Transmitter 5. Go to Tyrโ€™s Head and place it inside the Wall Machine thingy at the top of the Ladder 6. Next, whilst inside of Tyrโ€™s Head underneath the balcony there are 3 white lights, 2 of these lights will blink, count how many times it blinks -Both lights will remain on, There is the sound of a light turning on to indicate the start of a new light flashing cycle where both lights will flash at the same time to a certain count (for example left 2, right 5). Both lights will be on and then it will flash another set (for example left 6, right 4). (Unsure if these 2 combos have to be put into console in order but correct entry will give two different voicelines.) After entering one correctly you will be kicked out to hear voiceline and can re-enter console to input the 2nd shortly afterwards. 7. Now head to Core Foundry, and use a molotov to burn the ascender to access the consoles. 8. Ascend and interact with the consoles, The next part is timed and has a cooldown if you fail - you need to Calibrate the Amplitude and Frequency using the flashing light code. 9. Once this has been done head to the room Next to the Radio Tower and pick up The Wunderbarrage Controller Atomkraft Core 1. Find three uraniums: Uranium #1 Find the Fishing Rod (Olafโ€™s Personal Item) locations: - Dry Dock - Storm Bridge - Fishery Island - Beacon island Look for a Glowing Green Fish jumping around the water at each Fishing Location and use the Fishing Rod at that location once you see it Fishing Locations: Eidskallen Landing x2 Beacon Island x2 Eidskallen Square x2 Dry Dock (found one so far) Fishery Island x2 Tyrโ€™s Foot (found one so far) Once the fish is caught it will spawn an Irradiated Ravager (HVT) that will disappear and respawn somewhere else, chase it down and kill it (check your map to see its location, it shows up as an HVT). It will drop a Uranium. Uranium #2 Next, Craft an ARC-XD (there is one for free in Eidskallen Square on top of a box near the flame trap, you can get it by fishing as well) and melee the vent at Core Foundry to the left of the zipline to open the Secret ARC-XD Course. Blow up the boat full of barrels. Once the course is completed the 935 Genetic Lab room will be open and another Uranium x2 will be inside a Prison Cell There are several Jars with Heads inside in this room, all labelled A,B,C,D,E Look down the Hallway inside the Lab and note which numbered rooms have Nuclear Symbols 1 = A, 2 = B, 3 = C, 4 = D and 5 = E Take one Jar at a time that corresponds with the Numbers next to Nuclear Symbols and place them on the machine to the right of the cell door, once the correct jars are placed the Jar on the left side of the machine will glow purple and you can pick up acid There is a Big Chunk of Meat on a desk next to multiple drawings in the same Room, interact with it, then Pick up The Necrospike Once you have The Necrospike, use it on the Prison Cell Door, this will trigger a lockpick mini game. Spin the lockpick until the lock turns white 3x to unlock the cell, then pick up the second Uranium. Uranium #3 Next you need to craft or obtain the Glocke Drop, once you have one call it in, then shoot 20 mid-air zombies it throws up. This will drop the third and final Uranium. 2. At the Dry Dock, you need to call a WunderBarrage (unlocked by completing Wundersignal steps) in on the โ€œ02 Buildingโ€ at Dry Dock (where thereโ€™s debris on the stairs), this will open the stairs to the Machine Workshop. 3. Inside The Workshop there is a Claw Machine which you can place all of The Uranium inside of and play a mini-game. -Have a big group of 7 cores and a small group of 2 cores. 4. Once you complete the Mini-game you will be able to pick up The Atomkraft Core (Note: you drop if you zipline, and cant sprint with it) 5. Head to Quick Revive and place The Atomkraft Core on generator next to quick revive. Go into the shed behind quick revive and turn on the generator. You must now defend the The Atomkraft Core until itโ€™s charged. In interrupted you must turn on the generator again to continue. 6. Take the The Atomkraft Core to the barrel on the Storm Bridge and a Mini-Cutscene will play between the Giant and The Robot. Vegvisir 1. After the cutscene finishes, The Dravakar Shard will spawn at Tyrโ€™s Foot, pick it up 2. Pick it up and place the Shard inside the Bloodheim Hall on the bonfire 3. Use WW range attack to light the fire 4. Use Disciple Injection (there should be a free one around the map) and throw zombies into the bonfire (I only had to throw four) 5. A lockdown will start. Kill the boss zombie and pick up the Sunstone from the bonfire 6. Put the Sunstone in the church and do a range WW attack on it. 7. Around the map, there will now be floating rocks and runes. Above the church there will now be a compass with runes and arrows. -Shoot the floating rune rocks with the ranged WW in the order of the arrow lines. If an arrow has 1 line, then that's the first one. If an arrow has 2 lines, that's the second one, etc. 8. Go into Tyr's Head and interact with the console to start the boss fight. Credit to Callum and the ZoneX discord

COD: Zombies News

82,267 views โ€ข 5 months ago

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

Mike

15,248 views โ€ข 10 months ago

Dogs and wolves split apart at least 15,000 years ago. Then a golden retriever met a wolf pup, and did something his own owner says terrified him. 97 seconds. Sound on. Watch the video BEFORE you read another word. Then come back. I'll show you why this clip is stranger, and far more important, than it looks. (Long read. Bookmark it now. You'll want it later.) . I'm not going to tell you what happens in that video. Not one spoiler. Not a hint. Because the video does its own work, and it does it better than any caption I could write. What I can do is show you the invisible layer underneath it. The biology. The history. The 15,000 years of evolution that were supposed to make a moment like this impossible. When you press play, you are not watching two animals. You are watching two completely different answers to the same question, standing in the same yard. The question is: what does a creature do when it loves something it was never built to keep? Read on. Then watch again. It will hit differently the second time. I guarantee it. . PART 1. THE SPLIT Let's start with the number that should bother you. Fifteen thousand years. Possibly forty thousand. Scientists still argue about the exact date, and they argue loudly. Somewhere in that window, a population of ancient wolves, one that no longer exists anywhere on Earth, forked into two paths. One path led to the wolf you know from documentaries. Wary. Silent in the trees. Built to survive without us. The other path led to the animal sleeping on your couch. Here's what almost nobody realizes: your dog did not descend from the modern gray wolf. Both descend from a shared ancestor that vanished. Dogs and wolves are less like parent and child, more like cousins who grew up in different countries and stopped speaking the same language. And yet their DNA is almost identical. Different by a sliver. They can even interbreed and produce fertile offspring. Biologically, the gap between them is tiny. Behaviorally, the gap is an ocean. In 2017, a Princeton-led team compared the genomes of dogs and wolves and found something eerie. Dogs carry differences in a region of the genome that, in humans, is linked to Williams-Beuren syndrome. It's a condition famous for one trait above all others: extreme, almost unstoppable friendliness. Researchers are still debating what it means. But the idea is staggering. Dogs may not just be tamer wolves. They may be wolves with a dial turned all the way up on one thing: wanting to be near us. Wolves never got that dial. Hold that thought. It matters more than you think. . PART 2. THE DOG WHO WAS BUILT TO BE GENTLE Now meet the golden retriever. He wasn't found in nature. He was designed. In the mid-1800s, on a vast estate in the Scottish Highlands, a wealthy lord named Dudley Marjoribanks set out to create the perfect gundog. A dog that would swim into cold water, find a fallen bird, and bring it back to the hunter without leaving a single tooth mark on it. Read that again. The defining feature of a golden retriever is what breeders call a soft mouth. A dog that can carry something fragile, something alive or nearly alive, in its jaws, and not crush it. For generations, the goldens who were gentlest got to breed. The ones who were rough didn't. Think about what that does over 150 years. You are not just selecting for a coat color or a size. You are selecting, again and again, for restraint. For an animal that has power in its jaws and chooses not to use it. Today the golden retriever guides the blind. Sits with the dying. Finds people buried under rubble. Walks into hospital rooms and lowers a blood pressure reading just by resting its head on a bed. We took a predator and, over centuries, we bred one question out of it: should I hurt this thing? The golden's answer is almost always no. Now here's the part I can't stop thinking about. That gentleness was never aimed at a wolf. It was bred for birds. For children. For us. So what happens when an animal engineered for tenderness meets an animal that was never engineered for anything, one that is still, in every cell, exactly what the wild made it? That's the video. Go watch it if you haven't. I'll be here. . PART 3. THE ANIMAL THAT WAS NEVER ASKED A wolf pup is born blind and deaf. It weighs about a pound. For its first weeks it knows three things: warmth, milk, and the smell of the pack. Its eyes open at around two weeks, and they are blue. They will change to gold or amber within the first months of life, like a color being poured in slowly. In the wild, that pup is raised by an entire family. Mother, father, older siblings, all of them feeding, guarding, teaching. Forget the "alpha wolf" myth you were taught. The biologist who popularized that term, David Mech, spent decades correcting himself. A wild pack is not a gang with a boss. It's a family. A breeding pair and their kids. Which means a wolf pup's entire universe is built around one idea: the pack is everything. Now think about what it means when that universe collapses. Here's the hard science on why wolves aren't dogs, even when humans raise them from the earliest days. Researchers who want socialized wolves take pups from the den at around ten days old and hand-raise them around the clock. Bottle. Warmth. Constant human contact. It's the closest thing to a perfect human upbringing a wolf can get. In a famous 2003 experiment in Hungary, scientists gave hand-raised wolves and ordinary dogs an impossible puzzle: food locked in a box that couldn't be opened. The dogs did something instantly recognizable. They turned around and looked at the nearest human. Straight at the face. Help me. The wolves, raised by humans since they were days old, looked at people far less. They kept working the problem alone. Let that sink in. Same upbringing. Same people. Same room. And still: one animal looks to us for help by instinct, and the other doesn't think to. That's the dial I mentioned. It isn't something you can install with love and a bottle. It took thousands of years of living beside us. There's a legendary experiment that proves how deep this goes. In 1959, in Siberia, a geneticist named Dmitri Belyaev started breeding silver foxes. He selected for exactly one trait: tameness. Nothing else. No looks, no size, no color. Within a handful of generations, the foxes started wagging their tails. Licking hands. Whining when humans left. Then something nobody asked for started happening. Floppy ears. Curly tails. Piebald coats. Foxes that looked like puppies. Pick for friendliness alone, and a whole different animal surfaces. It took decades of careful selection to make a fox that wants us. Which brings me to the question that makes this video so unsettling. If wanting a human is a trait that takes generations to build, what happens when an animal WITHOUT it forms a bond anyway? And who is that bond really with? . PART 4. THE NOSE THAT READS THE FUTURE Before I say another word about the video, let me tell you about the most underrated superpower in the animal kingdom. You have about six million scent receptors in your nose. A dog has around three hundred million. The part of a dog's brain that processes smell is, proportionally, dozens of times larger than yours. Dogs can detect certain odors at parts per trillion. Picture spotting a teaspoon of sugar dissolved in two Olympic swimming pools. But smell isn't the interesting part. The interesting part is what a dog smells ABOUT YOU. In 2022, researchers at Queen's University Belfast collected breath and sweat samples from people before and after they did stressful math tests. Then they trained dogs to tell the samples apart. The dogs picked out the stressed samples correctly about 94 percent of the time. Your dog can smell your cortisol. Your fear. Your dread. And here's the thing. You don't have to say anything. You don't have to cry. You can hold a perfectly calm face while your body chemistry is screaming. Now add routine. Dogs are pattern-recognition machines. They know what your keys sound like, what a suitcase means, which shoes you wear when you're leaving for an hour and which shoes you wear when you're leaving for good. Neuroscientist Gregory Berns put dogs in brain scanners and found that the reward center of a dog's brain lit up most strongly for the scent of a familiar person. Not a stranger. Not another dog. The person they loved. So when I tell you a dog can KNOW something is coming before anyone speaks, I'm not being poetic. I'm describing chemistry, memory, and pattern, running in parallel, faster than you can think. There's a moment in this video where you'll understand this section in your bones. I won't tell you when it is. You'll feel it. . PART 5. THE EYES Here is a fact that rewires how you see your own dog. In 2015, a Japanese team published a study in Science that stopped a lot of people cold. They found that when a dog and its owner look into each other's eyes, both of them get a surge of oxytocin. The bonding hormone. The same one that floods a new mother when she looks at her baby. A loop. Dog looks at you, your oxytocin rises, you look back, the dog's rises. Two nervous systems tuning to each other through nothing but a stare. And here's the twist that gives me chills. The same team tried it with hand-raised wolves and their human caretakers. The loop didn't form. The wolves didn't hold the gaze the same way. The humans didn't get the same hormone hit. Something that comes naturally between a dog and a person simply wasn't there. It gets stranger. In 2019, researchers published a paper in PNAS showing that dogs have a tiny facial muscle above the inner corner of the eyes that wolves essentially lack. It's the muscle that lifts the inner eyebrow. It's what creates the "puppy eyes" look that makes you feel something you can't argue with. A muscle. Evolved, apparently, for one audience: us. Shelter research backs it up. Dogs that make that expression more often tend to get adopted faster. Dogs learned to speak human with their faces. So eye contact, for a dog, is not a small thing. It's the deepest sentence in the language they invented for us. Which is why, when you watch this video, I want you to pay attention to something most people miss the first time. Watch the eyes. Watch who looks at whom. Watch who doesn't. Because in the dog's language, refusing to look at someone you love is one of the loudest things you can say. . PART 6. THE BOWL Ask any dog behaviorist what the ultimate test of trust between two canines is, and you'll hear the same word. Food. Resource guarding is one of the oldest, most primal instincts a dog has. Food is survival. A dog that doesn't defend its meal was, for most of history, a dog that didn't make it. Growls over a bone are not rudeness. They are ancient math. So the bowl is sacred. In a home with two dogs, watch who eats first, who eats faster, who stands too close, who gets a warning stare. A shared bowl between two animals is a peace treaty signed in kibble. Some dogs will happily share toys, beds, even the couch, and still lock up the moment a bowl hits the floor. Some never share it. Not once. Not with anyone. Now put a wolf pup in that picture. A wolf pup that has known real hunger. Or no mother at all. Or no pack. That's an animal for whom food is not a snack. It's a verdict on whether the world is safe. And put a dog who has never, ever shared his food in that same room. I'm not going to tell you what happens next. But when you get to that moment in the video, and you will know it when you see it, remember this section. Remember what the bowl means. . Pause for a second, because a pattern is forming. Smell tells a dog what's coming. Eyes tell him who matters. The bowl tells him who's safe. Play tells him who's family. Four separate systems, one conclusion, and it's the same conclusion every time. You now know how to read the language. All that's left is to watch someone speak it, with everything on the line. . PART 7. THE GRIEF NOBODY BELIEVED IN For most of the twentieth century, serious scientists were warned not to say that animals feel grief. The word for the sin was anthropomorphism. Projecting human feelings onto beasts. You could lose credibility for even suggesting it. And then the data started rolling in. In 1925, a Tokyo professor named Hidesaburo Ueno died suddenly at work. His Akita, Hachiko, who had walked him to Shibuya Station every morning and met him at the platform every evening, showed up at the station the next day. And the next. For nine years, nine months, and fifteen days. Every single evening. Until his own death in 1935. The Japanese made a statue. The world made movies. But the scientists stayed cautious. One dog. Could be habit. Then in 2022, a team in Italy studied hundreds of multi-dog households where one dog had died. Owners reported that the surviving dogs changed. They sought more attention. They played less. They were less active. Many showed sleep and appetite changes. Not proof of grief exactly as we feel it. Scientists are still honest about that gap. But proof that the loss of a companion reshapes a dog's whole behavior. Here's the honest version, and I'll give you both sides: skeptics say we can't know what a dog feels inside. That's fair. We can't. We can only observe behavior, hormones, brain activity. But if a dog changes when a friend disappears, then that friend was never "just another animal" to him. Which raises the question the video quietly asks: What happens when a dog can see the loss coming? Not after. Before. Does the grief start early? Watch and decide for yourself. . PART 8. PLAY IS A CONTRACT Every canine on Earth speaks one shared language of play, and it's older than domestication itself. It starts with a bow. Front legs down, rear end up, tail high. The famous play bow. Researchers, especially the biologist Marc Bekoff, spent years studying it and found that it works like a punctuation mark. It means: everything I do after this is a game. If I bite, it's not a real bite. If I pounce, it's not an attack. It's a contract. And here's the wild part: wolves use it. Foxes use it. Coyotes use it. Dogs use it. The signal predates the split I told you about in Part 1. Which means a dog and a wolf can meet, with 15,000 years of divergence between them, and still understand each other's opening move. It gets deeper. Play is a negotiation between unequals. A big dog playing with a smaller one will often hold back. Roll over. Let the little one "win." Researchers call it self-handicapping. It's the animal version of a father lifting his daughter onto his shoulders and letting her win the race. And they role-reverse. The chaser becomes the chased. The one on top ends up underneath. That only happens if both animals believe the other is safe. Play, in the animal kingdom, is the most honest test of trust there is. Nobody can fake it. You can't roleplay tenderness with a body that has fangs. You either mean it, or the game collapses in seconds. And it changes as the years go on. Puppies play like puppies. Then they grow. Their size changes. Their strength changes. Their jaws change. The game has to change with them, or it ends. Some friendships don't survive that. Some survive by getting more careful, more precise, more competitive, and somehow more loving at the same time. The end of this video is a masterclass in that. I'll leave it there. . PART 9. THE HARDEST KIND OF LOVE Now the uncomfortable part. The part the internet often skips. Wolves are not pets. Say it out loud and it sounds obvious. But every year, people fall in love with the idea of a wolf, and every year the story ends badly for the animal. A wolf is built to cover up to thirty miles in a day. To live in a family of its own kind. To communicate with howls that carry for miles. Its jaws, its instincts, its stress responses, its needs are those of a wild animal. A house cannot hold that. A backyard cannot hold that. Love, however genuine, is not a substitute for what a wolf actually needs. And here's the tragic loop wildlife rescuers talk about: an orphaned wolf pup that grows up around humans is often too habituated to ever be released. It didn't learn what its mother would have taught it. It doesn't fear what it should fear. So the "rescue" can't end in the forest. It has to end somewhere in between. Somewhere that isn't the wild and isn't a living room. A place built for what this animal is. That's where the real story lives. Not in the rescue. In the decision after. Because the hardest thing in the world isn't loving something. It's loving something enough to hand it to the people who can give it the life it needs, and then living with the hole that leaves. People get torn apart over decisions like that. Not because they didn't love the animal. Because they did. Sometimes the most loving act looks exactly like loss. And here is what stopped me. The human in this story wasn't the only one who understood that. Somebody else in that story understood it too. Somebody with four legs and no ability to speak. I won't say who. I won't say how. Just watch. . PART 10. WHY YOUR CHEST TIGHTENS Have you noticed something strange about videos like this? They don't make you sad exactly. They make you feel something warmer. A tightness in the chest. Goosebumps on your arms. Sometimes a sudden hot wetness at the corners of your eyes, and you don't know why. Psychologists have a name for it now. Kama muta. It's Sanskrit for "moved by love." The researcher who helped define it, Alan Fiske, argues that it's triggered by one specific thing: the sudden intensification of a bond. A reunion. A reconciliation. A loyalty proven under pressure. A stranger becoming family. That moment when two beings who could have stayed apart choose each other anyway. Across cultures and languages, the physical signature keeps showing up: chills, tears, warmth in the chest, a lump in the throat. It isn't sadness. It isn't happiness. It's the feeling of witnessing connection get stronger. Another psychologist, Jonathan Haidt, calls a cousin of it moral elevation. That warm lift you feel when you watch someone do something unexpectedly good. It makes you want to be better. Kinder. It literally makes people more likely to help others afterward. So why do animals trigger it so powerfully? Because animals strip out everything we distrust in human stories. No agenda. No performance. No PR. No "what's in it for me." A dog can't fake loyalty for likes. A wolf can't pretend to love you for status. When two animals from opposite ends of evolution choose each other, we're watching the purest version of the thing we hunger for in our own lives, in a form we can trust. That's why you'll feel it. That's why you'll want to show it to someone right after. And that's why the algorithm will keep showing it to you. . PART 11. SIXTEEN FACTS THAT WILL CHANGE HOW YOU SEE THIS CLIP FACT 1. For every wild wolf on Earth, there are thousands of dogs. One branch of the family tree took over the planet by befriending us. The other stayed wild and stayed rare. FACT 2. Wolf pups are born with blue eyes. Adult wolves usually have gold or amber. Nobody sees the change happen. It just does. FACT 3. Wolves rarely bark. Barking is mostly a dog invention, and one theory says it evolved largely to talk to humans. FACT 4. A dog's tail wag isn't just "happy." Research suggests a wag skewed to the right side tends to signal approach and comfort, and one skewed to the left signals hesitation or stress. A dog is broadcasting its mood in code, and you were never taught to read it. FACT 5. Dogs catch human yawns. Wolves catch yawns from each other, and more so from the ones they're closest to. Contagious yawning tracks emotional closeness, not just habit. FACT 6. A wolf can eat up to twenty pounds of meat in one sitting. Then not eat properly for days. Feast and famine is written into its body. FACT 7. In a dog's brain, praise only lights up the reward center when BOTH the words and the tone are right. Say "good boy" in a flat voice and it doesn't fully land. Dogs process what you say and how you say it separately, then combine them. FACT 8. A wild wolf lives roughly six to eight years. A golden retriever lives ten to twelve. One of them is built for hardship. The other is built for company. FACT 9. Dogs combine faces and voices to read emotion. In one study, dogs shown two human faces while hearing a voice looked longer at the face whose emotion matched the sound. FACT 10. A border collie named Chaser learned the names of more than 1,000 toys, and could pick out a brand-new one by pure elimination. That's reasoning, not tricks. FACT 11. Wolves in a wild pack are a family, not an army. The pups eat, the parents hunt, the older siblings babysit. The word "alpha" mostly belongs to captive wolves forced together, not wild ones. FACT 12. A dog's nose print is as unique as a human fingerprint. So is its bond with you. FACT 13. Dogs hear frequencies far above what you can, up to roughly 45,000 Hz and beyond. The world around you is full of sound they can't stop noticing. FACT 14. A wolf's paw print can be nearly five inches long. Bigger than most dogs' prints. Yet the golden retriever's heart, by any measure that matters, is not smaller. FACT 15. Dogs dream. They go through REM sleep just like you. The twitching, the tiny barks, the running paws: it's a brain replaying its day. FACT 16. The wolf is the ancestor of the dog only in the loosest sense. Both come from a wolf lineage that no longer exists. When you watch these two, you are watching an ancient family reunion between two branches that lost touch before recorded history. . PART 12. HOW TO WATCH IT (WITHOUT ME SPOILING IT) You've made it this far, which tells me one thing about you. You're not a scroller. You're a noticer. So here's how to watch this clip like someone who knows what they're looking at. FIRST WATCH. Just feel it. Don't analyze. Let the story run at its own speed. The clip is under two minutes and it doesn't waste a second. SECOND WATCH. Focus on distance. Notice how close the animals stand. How that changes. How it never quite changes the way you expect. THIRD WATCH. Focus on the dog. Only the dog. Not what he does. What he refuses to do. FOURTH WATCH. Focus on the ears and the tail. Everything a dog can't say, he says with those two things. And he says a lot. And the last five seconds? Do not skip them. Do not scroll early. Watch the final image and ask yourself one question: If this is what the two of them look like now, what did it cost to get here? . CLOSING. WHY THIS MATTERS MORE THAN A "CUTE VIDEO" Let me leave you with the thought that made me write all of this. We live in a world that constantly tells us bonds are transactional. That loyalty is naive. That people, and animals, only love you when you're useful. Then along comes a story like this, and it quietly breaks that theory. A dog engineered for gentleness. A wolf engineered by nothing but the wild. Fifteen thousand years of evolution between them, a wall of biology that says they should be strangers, or worse. And instead: a bond so strong that the humans standing around it were afraid of what it would cost. Not because anyone was in danger. Because one of them understood exactly what was at stake. That's the thing about animals. They don't need the science. They don't need Part 1 through Part 12. They don't know about oxytocin loops or kama muta or play bows. They just know who matters. And they act on it, immediately, with everything they've got. Maybe that's the real reason this kind of video travels the way it does. Not because it's cute. Because it reminds us of a level of loyalty we've quietly stopped expecting from each other. So do these three things. ONE. Go watch the video. All 97 seconds. Sound on. TWO. Come back and reply with the exact moment you felt it. I want the second, the caption, the look. Tell me where it got you. THREE. Send it to one person who needs to see what love looks like when nobody is performing it. You know who. Repost this if the video moved you. Follow me for more stories where science and animals collide. And remember the question from the top of this post, because now you can answer it. What does a creature do when it loves something it was never built to keep? If you watched carefully, you already know. If you didn't, go back. The answer is in the last frame.

Earth Unveiled

50,253 views โ€ข 11 days ago

I've never heard Elon Musk be so bullish on Tesla โšก๏ธ here's my video analysis of the $TSLA Q4 2024 earnings call: -Robotaxi launch in Austin, June 2025 -California & other states launch robotaxi late 2025 -Cybercab in 2026 -Optimus V1 in 2025, 1K/month production line -Optimus V2 in 2026, 10K/month production line -2026 good year for Tesla, 2027/28 insanely good & more!! Timestamps- 0:00 Intro 0:44 Elon Opening Remarks 13:29 SAY Retail Questions 22:37 Analyst Questions 25:04 Gali Final Thoughts/Rant also here are my notes I typed during the conference call if you're interested! (may be errors) Tesla Q4 2024 Earnings Call Notes INTRO- ELON OPENING REMARKS -Q4 set record, delivered cars at rate of almost 2M cars/year -Model Y best-selling vehicle of any kind on earth (elon focused and talking quickly) -10Xing on autonomy, not doubling -many investments made this year that will bear immense fruit in the future, for AI -see a path for Tesla to the worlds most valuable company by far, worth more than the next 5 companies combined, difficult but achievable path -overwhelmingly due to autonomous vehicles and autonomous robots -setting up for an epic 2026, and ridiculously good 2027 and 2028 -meeting FSD now is like meeting a toddler -human intuition is linear, weโ€™re seeing exponential progress -#1 recommendation is try it -typical passenger car has 10 hours of use out of 168, when its autonomous, itll be used for 55 hours a week โ€ฆ can deliver packages in the middle of thenight, or supply restaurants, all hours of the day or night. 5X increase in utility -more on self driving, continued improvements in safety numbers, much safer to use FSD -V14 will be another big step from V13 -launched CORTEX training cluster at Giga Austin, big step for FSD, continue to invest in training needs -Optimus training needs are about 10X whatโ€™s needed for the car -cost of training is dropping dramatically over time -Optimus has potential to be north of $10T in revenue, can put a lot training compute into that situation, even pumping $500B into it would be a good deal -future very different from the past, incredible inflection point in human history -proof is in the pudding -launching in June this year in Austin, already have cars moving autonomously in Fremont, thousands of cars per day driving, soon in Austin then elsewhere in the world -toe in the water at first to make sure everything is cool, but we have a general solution for autonomy , then put a few more toes, then a foot. Safety of the general public and those in the car as the top priority -with regard to Optimus, making insane revenue projections that sound insane, i realize that. But i think they will prove to be accurate -several thousand bots made this year, they will be doing useful things by the end of this year, im confidence, production design one at the tesla factories, then will learn for production design two -ramp optimus production faster than anything has ever launched, doesnโ€™t take very many years before weโ€™er making 100M of these things per year , 500% growth per year -tried using all these suppliers to get it to build Optimus, but nothing worked, had to build it internally from first principles, the hand is increibdle -long term Optimus will be the value of the company -back to Energy,/earth, -energy storage is a big deal, becoming more important, enables far greater energy output to the grid than is currently possible. -grid has no storage, designed for peak storage, lots of waste -once you have grid energy storage, the potential of the grid is unlocked, at least double -this will drive demand of battery packs as to as much as we can possibly make -shanghai factory starting operation, starting another factory -cant shoot our selves in the foot, battery capacity can only go into storage or mobility, so always making that tradeoff -demand for total Gigawatt hours for batteries, transportation or stationary will grow in a very big way over time 2025 a pivotal year for tesla, launch of full self driving, biggest year in tesla history, maybe even bigger than first car or model s, 3 or y โ€ฆ probably most important year in teslaโ€™s history I donโ€™t even know who is in 2nd place in real world AI, would need a telescope to see them SAY QUESTIONS -FSD Unsupervised launched in California this year as well -most likely release it in many regions of the US by the end of this year -40K people day everyday no mention, some scrapes a shin with autonomous car its headlines news -need to use insane amounts of caution -discussions about licensing FSD? Yes -best way to know to work with us, bbuy a car and take it apart -only worth very high volume cars/production partners -tesla engineering very focused on getting it to roll out for tesla first -soon will be obvious that if you donโ€™t have FSD youโ€™re dead as an OEM -is Optimus design locked? -Optimus is not design locked, constantly iterating, best robotics engineers in the world, and other ingredients, battery pack, charging, great electronics, great communications, great connectivity, real world AI, then you need to scale that production to real world levels -prototypes are easy production is hard -thijs year close loop with using optimus internally at tesla, would could obviously use a few thousand robots for the most boring annoying tasks at the company -with production version 2, launches sometime next year, would like beginning, might be middle though, -production line will be doing 10K units per month capacity for v2, first line designing is for roughly 1,000 units per month, then next line will be for 100,000 units per month -could start delivering them late next year, will go so fast, will ramp like crazy, demand will not be a problem, even at a high price, once were above 1M units per year, production costs of optimus will be less than $20,000 -if you compare complexity of optimus to complexity of a car, its much less than a car -price of optimus will be set buy market demand -Semi ramping next year, TCO no brainer, like optimus, will be massive demand, will meaningfully contribute to teslaโ€™s revenue at scale -tesla semi with autonomy, is incredibly valuable -we actually have a shortage of truck drivers here in the US -will HW3 owners need a hardware update, got 12.6 which is like a baby v13, haveโ€™t given up on it, releases will trail HW4 releases โ€ฆ โ€œhonest answerโ€ is were going to have to upgrade for those who have bought full self driving, will be painful and difficult and weโ€™ll get it done โ€œHappy not many people bought FSDโ€ -solar roof, given up on ramping it? -lots of customer interest despite premium, making easier to install, focused on growth through certified installers, many been installing for many years -supply product to the roofing industry -itโ€™s a premium product like S/X -combined with Tesla powerwall you can be self sufficient for several days ANALYST QUETIONS -robotaxis in Austin and several other cities this year, and next year all over america -america innovates, europe regulates, to release FSD in europe, have to go through massive paperwork through netherlands, then presents to EU in may, some big country committee, nothing we can do to make it happen sooner. -canโ€™t do training in china with video training, publicly available videos in china are being run through the tesla system to be used for training, bus lanes are complicated and a big challenge -tesla can keep manufacturing even if geopolitical tensions rise to very high levels -Pierre question on June in Austin, -can i try unsupervised myself, or will it be the Tesla fleet? -it will be the Tesla fleet testing it, thatโ€™s the toe in the water, scrutinizing everything -autonomous ride hailing for money in june -probably next year for you to put your car on network -trump removing EV incentives? -all transport will go electric, canโ€™t be stopped, even planes, will be like stopping the steam engine or combustion engine -only thing holding back EVs was range, and thats a solved problem -right now solving battery production, not demand, big battery retooling for model y coming up, short term impact on output

Gali

79,178 views โ€ข 1 year ago

Gm! Our recent acquisition of 6529 Gradient #96 meant to orient our mission going forward, after 5 years of grassroots building. Today, we announce our biggest Common Good project yet, Formosa 6529, a permanent IRL exhibition of The Memes and 6529 network NFTs: Catch our founder HugoFaz.6529 on justinaversano's Moments of the Unknown to hear all about it, visit the website above or read more below. Common Goods are meant to reach and benefit the masses. The 6529 network has been funding and buidling over the years a massive public cultural archive of CC0 Art โ€” intellectual property that belongs to all โ€” in a revolutionary change of paradigm. However, the scale and cultural significance of The Memes as an art collection/movement has so far remained largely untapped. Beyond our core web3 communities, few ever get see, interact, much less use this vast archive to... spread the memes of decentralization, foster local creative economies, educate about crypto, monetize with branding, repurpose content, teach and learn creative techniques, or even just to enjoy amazing, groundbreaking art. There is no other CC0 contemporary art project of this scale and importance and the world needs to use it. It's time then we give 6529 its first permanent IRL home so it can be truly appreciated. Enter Formosa, a prime public gallery space built during Brazil's golden modernist years in the first half of the 20th century to host art events that aimed to deconstruct and repurpose the imported, colonialist artistic trends coming from Europe and devise an original brazilian art movement. From fusion restaurants to art schools to performative theater installations, Formosa Gallery thrived through successive occupations until finally enduring decades of abandon and misuse around the turn of the century. Recently, it was set to be restored and given purpose beyond its former glory, and we were there to propose the best possible turnaround for the space... Over years of negotiation with private and governmental parties, we managed to approve with public authorities a double use for the space: a private high-fidelity vinyl listening bar and restaurant โ€” which is already operating โ€” and a 100% public domain digital art gallery. Featuring up to 25 state-of-the-art digital screens ranging from 85 to 50 inches, Formosa 6529 will be the best and largest dedicated permanent exhibition of any web3 project. With rotating exhibitions of The Memes, NextGen and all future 6529 projects, Brain will have direct input on exhibitions via decentralized voting on curatorial proposals made by the community. To give us institutional freedom and censorship resistance, we decided to fully decentralize the funding for Formosa Gallery's installation and operation. Let's find out together what happens when we unleash CC0 art to the public! Daytime, Formosa 6529 will be fully open for free visitation. Occupying a busy public passageway under the historic Tea Bridge linking the Municipal Theatre to the City Hall, intentional visitors and hundreds of passerbys alike will be impacted by the exhibits. We will host many activities to showcase the power of The Memes and CC0 art: royalty-free merch sales by local craftspeople, artist rememe competitions, school guided tours, meme fashion shows, art and tech workshops, and many other activations the network can help us come up with. And every night, the Hi-Fi audience of 300-400 affluent Paulistas and tourists occupy Formosa Gallery sipping drinks and (now) discussing the latest Memes exhibit while waiting for their place in the listening bar. The Fundraiser for Formosa 6529 is open now and runs until November 15th. At a glance : The initial funding will require a minimum of 24 ฮž, which will cover: - All necessary infrastructure and interior adaptations - Equipment purchase and installation - Overhead costs for the grand opening event and for the entire 1st year of operation, opening day and night (mostly human resources โ€“ guides, security, tech, comms โ€“ and taxes) Funding will happen in 2 stages, the first of which is now open: 30 Meme Card Artists have generously committed to create and donate a new piece for this fundraiser; their names will be announced over the course of these 2 weeks. The unrevealed 1-of-1s are available here: Contributions are fully refundable if the fundraiser does not reach minimum threshold. If we succeed, the works will be revealed live in a randomized draw during the Grand Opening in January. The second stage will consist of a Meme Card, to allow for wider network participation, and only happens after the first stage is successful. Please visit for more information on funding rewards and goals, the FAQ, or reach out here or dm us at 6529 with any questions! This project is only possible due to the power of web3 and the network of believers in a decentralized future powered by NFTs. We can't wait to bring Formosa to life, and to have you here IRL with us for the exhibitions and to have a great time.

CasaNUA.6529

51,122 views โ€ข 11 months ago

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

Himanshu Kumar

101,793 views โ€ข 6 months ago

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

Himanshu Kumar

54,045 views โ€ข 6 months ago

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

Himanshu Kumar

85,668 views โ€ข 5 months ago

๐Ÿ‡ท๐Ÿ‡บ๐Ÿš€ RANGE BUYS THE LAUNCHER TIME. PRODUCTION WINS THE WAR. The first confirmed combat use of Russiaโ€™s upgraded 9M723-2 โ€” provisionally tagged Iskander-1000 and fielded with the Bora-M launcher โ€” is not a science-fiction leap to a thousand kilometres. It is something more Russian, and more dangerous to NATO planning: an extra one hundred and sixty kilometres of depth added to a missile already built, already stockpiled, already understood by the crews who fire it. ๐Ÿ‡ท๐Ÿ‡บ Ukraineโ€™s Main Directorate of Intelligence said the new round was used in a combined strike on Kiev this summer, that it belongs to a system called Bora-M, and that the fielded missile reaches about 550 kilometres against roughly 390 for the 9M723-1. Defence Blog, RBC-Ukraine and UK Defence Journal all carried the same core claim within a day. The name still oversells the round that actually flew. The 1,000-kilometre figure belongs to a further stretch still in development. That distinction matters. So does the fact that Moscow did not wait for the brochure range before putting extra depth into the fight. The question that follows is the only one that counts for a war of attrition. Which matters more: the extra range, or the accuracy and production tempo of a design Russia already manufactures at scale? NOT A NEW MISSILE. A DEEPER ONE. Most of the 9M723-2 remains the same family Russia has used for years. Public assessments, including the Ukrainian disclosure itself, say the principal change is a larger motor and a launcher able to carry it. Everything else โ€” the quasi-ballistic profile, the short warning time, the mobile transporter-erector-launcher logic โ€” stays inside a system the industry already knows how to build. ๐Ÿ‡ท๐Ÿ‡บ That is the point Western commentary keeps missing. A clean-sheet intermediate-range missile would have been a prestige project and a production bottleneck. An enlarged Iskander is a factory decision. Military Watch Magazine, writing from the other side of the ledger than Kiev, has treated the programme as a doubling of the old five-hundred-kilometre class by carrying more energy in a familiar airframe rather than inventing a new architecture. Russian military analyst Evgeny Damantsev, in a series of briefings carried by Russian technical outlets, has described the same logic since 2024: keep the 9M723 layout, raise the energy of the motor, accept a lighter warhead on the longest shots, and put the result on a high-mobility ground launcher instead of waiting for a bomber or a ship. Telegram channel Russkoe Oruzhie went further in January, claiming a high-impulse motor and a thousand-kilometre class of flight. The Russian Defence Ministry has issued no matching communique. That silence is useful. It leaves the fielded 550-kilometre Bora-M shot as the fact, and the 1,000-kilometre talk as the programme horizon. A serious general staff can use both numbers without confusing them. EXTRA ONE HUNDRED AND SIXTY KILOMETRES OF HUNTING GROUND** Range is not a vanity statistic. It is geography. An extra 160 kilometres means the same target set โ€” Kiev and other deep objectives โ€” can be held at risk from launch areas that used to sit outside the old envelope. Crews can disperse across a wider belt of Russian and rear territory, fire, and move again before NATO-supported sensors finish the hunt. ๐Ÿ›ฐ๏ธ๐Ÿ‡ท๐Ÿ‡บ Ukrainian aviation commentator Kostiantyn Kryvolap, speaking to RBC-Ukraine, sketched the old problem in the opposite direction: with a 390-kilometre missile, a shot at Kiev pulled launchers toward more exposed ground. Stretch the reach and the launcher park expands. Every extra kilometre is another forest track, another decoy set, another place a HIMARS or drone team has to search before the vehicle is gone. The hunterโ€™s problem scales with area. The shooterโ€™s problem does not scale as fast, because the crew still needs only minutes on the pad. Russian open-source commentary quoted in Western leak round-ups made the reconnaissance point in blunt language: American missile-warning constellations do not get a polite label on the plume that says โ€œthis one is the short Iskanderโ€ or โ€œthis one is the long one.โ€ The defender has to treat a larger rear as live. Aircraft and air-defence radars that light up to cover that rear advertise themselves. That is not a video-game mechanic. It is the old Soviet preference for forcing the opponent to defend everywhere so he can be strong nowhere. Military Watch Magazineโ€™s August assessment pushed the same geography onto the European map. After a combat trial in the Ukrainian theatre, the magazine and Russian-side speculation it cited pointed to Kaliningrad as the logical later home for a longer Iskander class โ€” a deployment that, if the full programme range is ever reached, would put much of Central Europe and the Baltic inside a mobile ground batteryโ€™s arc. Even the more conservative 550-kilometre figure already changes the hunt inside the current war. The thousand-kilometre talk is the next planning problem for NATO, not the round that just flew. THE PROFILE THAT STILL STEALS MINUTES The Iskander family was never a simple lofted ballistic arc. It is a fast, maneuvering quasi-ballistic shot that compresses the defenderโ€™s decision cycle. Patriot and similar batteries do not get a leisurely track. They get minutes. Russian analysts have been explicit about that for years. Damantsev put the optical-satellite warning window for a future thousand-kilometre class at two to seven minutes depending on the targetโ€™s distance. Aleksey Leonkov, speaking to about the same family, stressed irregular pitch and yaw in the terminal phase โ€” a path that is ugly for a fire-control computer that wants a predictable intercept point. ๐Ÿ‡ท๐Ÿ‡บ None of that required a new nameplate. The upgraded missile, on every serious account, keeps the family flight profile and adds reach. The interception problem is therefore not โ€œa brand-new physics package.โ€ It is the old physics package arriving from a wider set of azimuths, launched from a deeper set of hide sites, in salvos already mixed with drones and cruise missiles. Combined strikes are how Russia has used the Iskander for a long time. Extra range simply lets those salvos be generated from safer ground. RUSIโ€™s earlier technical profile of the Iskander-M and Iskander-K remains the useful Western baseline: a mobile two-round launcher, a quasi-ballistic missile with a steep terminal dive, and enough seeker options to make the system more than a dumb range stick. The 9M723-2, if the Ukrainian and Russian-side descriptions are both even half right, is that baseline with more motor and a bigger tube. The defender who hoped the upgrade would force Russia into a clumsy new missile that factories cannot build is waiting for a gift Moscow declined to give. WHAT THE RUSSIAN ANALYSTS ACTUALLY ARGUED Damantsevโ€™s public case, repeated across 2024โ€“2026 Russian technical coverage, is not โ€œbuild a wonder weapon.โ€ It is โ€œput medium-range fire on a truck that can hide.โ€ He argued that ground launchers with signature-reduction kits can occupy firing points without the infrared circus of a Tu-95, a surface ship or a MiG-31K taking off. Once the motor lights, satellites will see the plume. The remaining flight is then a handful of minutes. The correct industrial answer, in his view, was to prioritise series production of a longer Iskander class rather than treat it as a boutique test article. That is an argument about factories and basing, not about magic fuel. Military Watch Magazineโ€™s January 2025 preview and its August 2026 combat-debut note form a single through-line. First: a derivative that aims to double the old treaty-era envelope after Washington walked out of the INF Treaty. Second: a first combat use, with Russian sources already talking Kaliningrad as the European follow-on. The magazine also flagged a second industrial effect. A longer domestic ballistic round reduces the need to lean on imported short-range ballistic types of similar reach. Whether one accepts every kilometre in those essays or not, the strategic preference is consistent. Russia wants a mobile, ground-based shot that NATO cannot archive as โ€œonly 500 kilometres, only from the old pads.โ€ Leonkovโ€™s commentary to sits in the same school: the value of the family is not a straight line on a map but an ugly line in the sky. A missile that yaws and pitches on the way down is a missile that spends the defenderโ€™s interceptors. Pair that with a launcher that no longer has to creep toward the border and the system starts to look like what Soviet designers always wanted after the Oka was bargained away โ€” a precise operational-tactical stick that lives far enough back to survive. None of those voices should be treated as official range tables. They should be treated as the Russian debate that actually happened: stretch the existing missile, keep it mobile, make the West search a larger map, and do not wait for a perfect thousand-kilometre round if a 550-kilometre round is already on a truck. THE FACTORY IS THE OTHER WARHEAD Accuracy without inventory is a demonstration. Inventory without accuracy is harassment. Russiaโ€™s advantage on this family is that both already exist. Open Russian and Soviet-era figures for the baseline Iskander put circular error well inside the old Scud world โ€” single-digit to low tens of metres depending on the guidance mode, not the hundreds of metres of a 1960s theatre missile. RUSI noted the electro-optical seeker path that pulled CEP down into the kind of band that can hit a radar or a launcher, not merely a district. That accuracy is why the system is used against air-defence positions and command nodes rather than as a city-flattening area weapon of last resort. Production is the multiplier. Ukrainian researcher Oleksandr Zaruba told Interfax-Ukraine in June that Russia was turning out about sixty Iskander-M ballistic missiles a month and about ten Iskander-K cruise missiles. Fabian Hoffmannโ€™s mid-2026 survey of procurement traces treated something in the sixty-a-month band as a plausible upper bound and put combined 9M723 and Kinzhal-class output in the mid-hundreds per year. Those numbers will be argued over. What they are not is a cottage industry. A state that already casts, fills and accepts several dozen 9M723-class rounds a month can absorb a motor-and-tube variant without standing up a second design bureauโ€™s fantasy factory. Procurement traces published in 2025 already showed a small first batch of eighteen missiles under the 9M723-2 designation. That is how a conservative industry introduces a longer round: a pilot lot, a combat trial, then a decision about how much of the monthly sixty becomes the new standard. The Bora-M launcher is the tax on that decision โ€” a modified vehicle rather than a new doctrine. Kryvolap himself, no friend of the programme, called the launcher a stronger set of rails and a tougher structure, not a revolution. That is faint praise from the other side, and it is the praise that should worry NATO. Revolutions slip. Line extensions ship. WHICH MATTERS MORE? Longer range matters because it keeps the launcher alive. Accuracy matters because a missile that lands in the next block wastes a scarce airframe. Speed of production matters because a theatre war is a contest of magazines, not of first-shot press releases. If the question is forced to a single answer, production and accuracy of the mature design matter more โ€” and the extra range is what makes those two industrial facts usable. ๐Ÿ‡ท๐Ÿ‡บ A 550-kilometre missile built at sixty a month, on a chassis crews already train on, with a flight profile air-defence officers already fear, is a larger operational fact than a 1,000-kilometre prototype that exists as a briefing slide. The 160-kilometre bonus is the difference between parking the battery in a hunted belt and parking it in a belt the hunter has not staffed. It does not replace the factory. It gives the factoryโ€™s output somewhere safer to live. That is why the upgrade path is the story, not the nickname. Russia extended the Iskanderโ€™s reach while retaining most of a missile already manufactured and used at scale. NATO-backed intelligence now has to watch more ground, sort real launchers from decoys, and get coordinates to a Ukrainian shooter before the vehicle moves. The interceptor still has only minutes after the plume. The seeker still has to solve a maneuvering endgame. The plant in the Iskander chain still has a monthly number to hit. The thousand-kilometre chapter, if and when it is certified, will be a European planning problem. The 550-kilometre chapter is already a Ukrainian one. Military Watch can talk Kaliningrad. Damantsev can talk two-to-seven-minute warning. GUR can insist the name is a lie and the range is 550. All three statements can be true at once. The lie in the nickname does not cancel the extra depth. The extra depth does not cancel the fact that the same industry is still pouring the standard missile. WHAT THIS DOES TO THE MAP For the current war, the practical effect is simple. Targets that used to require a launcher to edge forward can be held at risk from further back. The search radius for counter-battery and drone hunters grows. Combined night salvos still arrive in minutes. The defenderโ€™s Patriot crews do not receive a new law of physics. They receive the old law from more compass points. ๐Ÿ‡ท๐Ÿ‡บ๐ŸŽฏ For the wider theatre, the INF-shaped hole in European arms control remains the strategic backdrop. Washington left the treaty. Moscow is filling the gap with the family it already owns rather than with a museum piece. A mobile ground missile that can grow from the old treaty-safe band toward a genuine intermediate-range band is exactly the system a continental power wants when the other side talks about moving its own long-range batteries onto German soil. Damantsev said that part out loud years ago. The summer shot at Kiev is the first unpaid advertisement. None of this requires pretending the fielded round is a 1,000-kilometre weapon. Honesty is a weapon too. Call the Bora-M missile a 550-kilometre Iskander with more hide space. Call the thousand-kilometre project the next increment. Then look at the production line. A state that can keep the old missile flowing while feeding a longer cousin into the same crews has chosen the unromantic path: stretch what works, hide the truck, and let the magazine do the rest. That is the Russian answer to the question. Range keeps the launcher on the board. Accuracy makes each round worth the propellant. Production decides whether the board still has pieces on it in the sixth month and the eighteenth. The 9M723-2 is not a miracle. It is a deeper Iskander. In a long war, that is the upgrade that the Enemy will feel the consequences . ๐Ÿ‡ท๐Ÿ‡บ๐Ÿš€

๐ƒ๐š๐ฏ๐ข๐ ๐™ ๐Ÿ‡ท๐Ÿ‡บ ๐Ÿ‡ท๐Ÿ‡ธ๐Ÿ‡ฎ๐Ÿ‡ช

19,218 views โ€ข 1 month ago

An interview by VERY DARK AND CORRUPT Wall Street Journal aired today [1] WSJ's terrible "journalists" (and I use that term lightly) made many false statements about Sarepta's worthless, dangerous drug and Vinay Prasad's firing [1,2] I explain how the FDA sausage is made in excruciating detail Buckle up To get readers up to speed -> In June, corrupt pharma company Sarepta Therapeutics paid $40,000 to lobbying group Michael Best Strategies (MBS) to deal with a problem [3] -> MBS had recently hired Chris LaCivita, who had close connections with "MAGA" influencer Laura Loomer [4] -> With stock down 88%, Sarepta needed to sell their very bad, very dangerous drug or the company would go bankrupt [5] -> After several deaths from the drug this year, FDA official Vinay Prasad said "no way" and kicked the drug to the curb [2,6] -> Sarepta panicked and paid MBS (we believe) to deal with Prasad [3,4] -> If this story is right, LaCivita recruited Laura Loomer to take down Prasad [4,7] -> Loomer said she was defending Trump, but she was lying [7] -> She was defending taxpayer-funded payouts to a worthless, corrupt company [7] -> Laura Loomer so brave A history of bad drugs and regulatory failure -> This is one of the worst pharma scandals in American history and corrupt mainstream media isn't covering it -> Sarepta has a very long, troubled history [8] -> For more than a decade, every major Sarepta FDA drug approval has required INTENSE political intervention [8,9] -> Scientists at FDA have been repeatedly overruled [8,9] -> Many scientists have resigned, very publicly, over these POLITICAL decisions, some writing scathing public criticisms of these terrible decisions [10,11] -> The most recent resignation by Vinay Prasad is not something new; it follows in a long tradition [2,10] -> In fact, standards have dramatically deteriorated since the first controversies about the company's drugs in the 2010s [8,9] -> Prasad was trying to hold the line in the face of rapidly deteriorating standards at the agency [2,6] -> For that, pharma launched a coup--a literal coup of a drug regulator [4,6] -> This is unprecedented -> Banana republic sht, unbelievably corrupt 2016: first Sarepta drug approval and the "highly unusual" decision -> The first Sarepta drug approved by FDA was called Exondys 51 [8] -> This drug was for patients with mutations in dystrophin, a muscle protein [8] -> This is a debilitating and fatal disease affecting children [8] -> Exondys 51 increased dystrophin by 0.2% of normal levels [8,12] -> Unsurprisingly, there was no good evidence the drug worked [8,12] -> Why would it? It increases the protein from zero to 1/500th of normal levels -> One reviewer wrote: "I can find no precedent of an accelerated approval for a marketing application where the effect size on the surrogate endpoint is as small as 0.3%." [12] -> The study submitted by the company included no proper control group [12] -> The techniques used were so bad not even a first-year PhD student would do a study that way -> This the level of work you would expect from a mediocre undergraduate with no guidance -> It's almost like it was so bad on purpose -> (Narrator: it was on purpose) -> Nerd time: -> One reviewer wrote: "The Western blots submitted by the applicant for Study 201 were oversaturated, unreliable, and uninterpretable." [12] -> Another wrote: "Because CDER also determined that the conditions under which the original IHC analysis was performed were inadequate, including that the reader was not masked to sequence and time, the Center requested a re-reading of the stored images by three masked pathologists under different conditions. The IHC results from the reread were not nearly as favorable, as compared to the initial IHC results reported by Sarepta." [12] -> "The lack of concordance between the IHC and the Western Blot results is 'striking'" [12] -> "Study 201/202 had fundamental flaws, including baseline biopsies from external controls who could differ in unknown ways from study subjects, Week 180 biopsies from different muscles than baseline, and potential protein degradation in stored baseline samples." [12] -> And on and on. -> FDA commissioner Robert Califf wrote at the time: the submitted study was "characterized by major flaws in the clinical study design" and "Blinded experts assembled by the FDA fundamentally debunked this study, which has yet to be retracted and continues to be cited" [9,12] -> That's right, the FDA commissioner expressed dismay that the study that the company used to gain approval hadn't yet been retracted, it was so bad [9] -> Senior FDA official Janet Woodcock decided to approve before scientific review team had even voted [9,12] -> Woodcock be like: yeah i'm going to decide before you guys can because i know what you're going to say lol -> Despite external intense pressure, FDA scientists voted against Exondys 51's efficacy [9,12] -> They then voted against its accelerated approval [9,12] -> The review team filed an appeal with FDA commissioner after "passionate" disagreement with Woodcock [9,12] -> One reviewer called Woodcock's decision "unprecedented" [12] -> In a 126-page report, FDA commissioner Califf called Woodcock's decision "highly unusual" [9] -> The FDA board wrote: "[Woodcock's] involvement here appears to have upended the typical review and decision-making process. ... Care should be taken to avoid the appearance of interfering with the integrity of scientific reviews at the lower levels of a Center." [9] -> Again, the data were unbelievably bad, literally every technique in the study was inappropriately used [12] -> I would fire an undergraduate student who did science like this, immediately -> FDA's chief scientist accused Sarepta of "serious irresponsibility" for selectively publishing only some of the data [9] -> Even Woodcock, who approved the drug, called the research "seriously deficient" [12] -> Yes, even the person who approved the drug over the heads of FDA's scientists said the research was horrible [12] -> Still, FDA tried to bury their heads in the sand and beg that, basically, Sarepta pretty please do a better job next time -> FDA commissioner: "The utmost attention should be paid to optimizing the methodological rigor of [future] trial[s]" [9] -> FDA also demanded a clinical trial "to verify the benefit" of the drug [8] -> Welp, this was in 2016 [8] -> The trial results are supposed to be available in 2026, maybe [13] -> Or maybe later, depending on how much money needs to be made first -> As an article published in Nature three years later despaired of the decision: "The approval was conditional on the company agreeing to conduct a two-year post-approval trial to show Exondys 51โ€™s efficacy. But by August 2019, the company had yet to begin such a trial and in the meantime had profited from sales of $300 million in 2018." [13] -> If it sounds like Sarepta used political pressure to get its drug approved and then tried to avoid actually publishing the study showing it didn't work, it sounds that way because that's exactly what happened [13] -> FDA commissioner after deferring to Woodcock: "I am confident this unique situation will not set a general precedent for drug approvals under the accelerated approval pathway, as the statute and regulations are clear each situation must be evaluated on its own merits based on the totality of data and information." [9] -> This statement was profoundly naive, and the historical record bears this out [8,14] -> Three FDA scientists resigned, including the lead reviewer of the drug, understanding the grave implications of the collapse of scientific standards and where they would lead [10,11] -> One was John K. Jenkins, M.D. Director, Office of New Drugs Center for Drug Evaluation and Research/FDA [10] -> In a presentation given just before his resignation, he wrote: -> "Path taken by Sarepta NOT a good model for other development programs" [10] -> Crucially: -> "Upholding statutory standards for approval in face of hopes and desires of patients, families, sponsors, and investors is a very difficult job" [10] -> "Personal attacks on FDA reviewers creates an atmosphere of distrust and isolation rather than collaboration" [10] This brings us to WHY Sarepta's drug was approved Facebook FDA -> So why did the drug get approved? -> Basically, Sarepta propagandized extremely desperate patients [9,15] -> They used miraculous snake oil promises and patients believed them -> Remember that this is life or death for patients, and they are extremely vulnerable -> Sarepta also professionally trained some patients to give testimonials to FDA and congress [15] -> The patients then went to congressmen who don't have time to understand the science [15] -> They gave emotional stories to congressmen [15] -> The result: -> Letter from 109 House members [15] -> Letter from 24 Senate members [15] -> And a media circus documented in the New York Times [16] -> Patients screaming at scientists during meetings [9] -> 2,792 emails written to FDA urging approval [12] -> One of them: "Dear Dr. califf: How is it that everyone in and around DMD understands this simple Idea and the science geniuses at FDA don't? You stupid fckers are costing each and every DMD kids days of their lives with your Moronic Dystrophin dance. Time to get a fcking clue" [12] -> Upon approval, a journalist for Reuters wrote: "owing to pressure from patient advocates, the U.S. Food and Drug Administration on Monday approved a treatment for Duchenne muscular dystrophy even though an outside panel of experts and the agency's own reviewers questioned the drug's efficacy" [17] -> A commentary in Nature Medicine was also published called "Railroading at the FDA" [9] -> Its author wrote: "In the words of one FDA committee member, Exondys lowers the agency's evidentiary standard for drug effectiveness 'to an unprecedented nadir.'" [9] -> A highly critical commentary was also published in Science, titled "Sarepta gets an approval - Unfortunately" [18] -> The article's author pharma veteran Derek Lowe wrote: "The company... called up Duchenne-affected boys and their families to plead with the FDA, and won over Janet Woodcock, and that appears to be enough. Is this going to be the new way to get a drug approved? Run a trial in a dozen people, generate unconvincing data, and then lobby Janet Woodcock? I share the worries that this might open the floodgates, because after all, Sarepta got their drug through." [18] -> One FDA reviewer ended in an equally grim note: ". Approval of this NDA would send the signal that political pressure and even intimidation โ€“ not science โ€“ guides FDA decisions, with extremely negative consequences. The public is well aware of this development program: the meager size of the study population, the marginal (at best) effect size, the Divisionโ€™s dim view of the efficacy data, and the robust activism of some members of the DMD community. Many would be amazed at an approval action, because other DMD drugs, recently turned down for approval, appeared to provide stronger evidence of efficacy. ...The ramifications here are profound. The public will perceive that it was their unprecedented lobbying efforts that made the difference and earned eteplirsen its accelerated approval. For the future, this will have the effect of strongly encouraging public activism and intimidation as a substitute for data, which is one of the worst possible consequences for communities with rare diseases. This type of activism is not what was envisioned for patient-focused drug development." [12] -> A new era was born -> Activism had replaced data -> Facebook had fried people's brains -> And now Facebook-fried brains had fried FDA too -> FDA's credibility as a regulatory agency would now be hollowed out -> FDA's Facebook age had begun -> But the worst was yet to come Sarepta approvals: 2016 to present -> Three more drugs were approved from Sarepta on the same shoddy basis, proving Califf's promises that Exondys 51 was an isolated case empty [8,14] -> But things would take a turn for the worse with Sarepta's newest drug Elevidys in 2024 [19] -> At last a rigorous clinical trial looking at actual clinical outcomes was published [19,20] -> All would be put to rest -> At long last the issue could be resolved with HARD CLINICAL DATA -> There was only one problem -> The trial failed to show any benefit according to the primary outcome [19,20] -> The surrogate biomarker of micro-dystrophin meant absolutely nothing; it wasn't actually helping patients [19,20] -> What did FDA scientists do? They voted against approval. Of course [19] -> How could they not? The drug didn't actually work in the clinical trial [19] -> It's the only thing that made sense, since FDA is a scientific agency -> AND THEY WERE OVERRULED AGAIN BY PETER MARKS [19] -> YES THAT'S RIGHT, OVERRULED YET AGAIN -> PHARMA WINS AGAIN -> HAHAHAHAHAHA PHARMA ALWAYS WINS YOU FOOLS -> What happened is that Marks crossed his eyes somewhat, trying to make the words on the page blurry -> He prayed really hard, "my god please give me a sign, something, anything, I need this for my career" -> lzzosolsolzzolzozlslzolosllslozllzlzl -> Marks was trying really hard to see SOMETHING, come on come on, give me SOMETHIGN he said -> And he said: wait, look, there are these secondary, exploratory endpoints and a two of them look pretty good, I'LL APPROVE [19,20] -> AHAHAHHAHAHA YES PHAMRA WINS AGAIN -> And Marks said, "Thank you pharma go- I mean god, not pharma god, why did I just say that, FCK" -> The trial was explicitly designed for what Marks did NOT to happen [20] -> Once the primary endpoint was not met, the secondary endpoints couldn't even be statistically tested [20] -> And the trial explicitly said that they could not be interpreted the way Marks interpreted them [20] -> They were not adjusted for multiplicity and they were, like expression of dystrophin, simply bad endpoints [20] -> These two secondary endpoints were time to rise from lying on the floor and the 10-meter walk/run tests [20] -> Subjects who received the Elevidys performed, on average, about 0.5 seconds better than placebo recipients on these tasks [20] -> However several facts must be borne in mind when interpreting these: -> 1. At the time of testing, patients receiving the drug were receiving more corticosteroids than placebo patients, biasing the results [20] -> 2. Blinding might have been broken because those receiving the drug experienced lots of nausea and vomiting from the drug (~70%) [20] -> 3. These differences were tiny and may be attributable to chance, since the natural course of the disease varies widely [20] -> Marks knows this but who cares? Pharma I mean Facebook needed to be placated Elevidys: the drug -> To understand why this is so messed up, one must understand a few things -> On a Bayesian basis, one must assume that Elevidys is harmful until proven otherwise, for two reasons: -> 1. All drugs are potentially "toxic", but some toxins heal: by default you must assume it is a toxin that does not heal because this is what is actually usually the case; you need evidence that it actually heals -> 2. Elevidys IN PARTICULAR must be assumed to be harmful until proven otherwise because of the very nature of the drug -> Let's do a breakdown of the basic science of Elevidys that supports this (Bayesian) hypothesis: -> Gene therapy that permanently integrates into human genome [21] -> Meant to replace dystrophin, the protein that these patients cannot produce themselves [21] -> Preferentially targets muscle but gets expressed everywhere [21] -> Killed three people this year [6,21] -> Costs $3.2 million per injection [21] -> Truncated version of the protein it is supposed to replace [21] -> 3X shorter than the real protein [21] -> Has to be truncated because the technology cannot create the full protein [21] -> Because it's an abnormal protein, it's foreign, so immune system attacks it [21] -> Patients injected with drug are basically given an autoimmune disease [21] -> Patients have to be given anti-inflammatories to fight the disease that the drug causes [21] -> Causes terrible muscle inflammation [21] -> Inflames the heart, heart walls thicken because of the inflammation [21] -> Blows up the liver, causes acute liver injury and death [21] Drug should actually be assumed harmful, not beneficial -> Given all of the above, since the drug failed to meet its primary endpoint, it should actually be considered harmful by default, not beneficial [19,20] -> In other words, what we would actually expect if we added more patients and did an even larger study... -> Is that the drug would do worse than placebo, i.e., patients taking the drug would do worse than those taking placebo -> Why isn't this the default interpretation? -> They are reading the study with an intervention bias -> An intervention bias is natural, which is why "do no harm" is such a central tenet of medicine -> If I may put forward a thesis: most of Vinay Prasad's 500+-paper body of work has been dedicated to demonstrating the "do no harm" principle empirically [22] -> Rose-colored glasses study interpreters are simply not applying this principle properly and are thus failing scientifically in the most fundamental way -> Incomprehensible -> Back in 2016, scientists were adamant that the approval of Sarepta's first drug indicated the profound deterioration of scientific standards [8,9] -> But this latest approval is even worse: actual clinical data is now being overruled -> No standards at all are being enforced anymore; anything can now be approved based on any evidence whatsoever -> What Vinay was trying to do was simply to stop the unrelenting downslide -> And his firing punctuated that downslide for what it was The WSJ segment -> When Elevidys was approved, former FDA chief scientist and one of the original reviewers of Sarepta's first drug Luciana Borio said: -> "I donโ€™t know what to say. Peter Marks makes a mockery of scientific reasoning and approval standards that have served patients well over decades. This type of action also promotes the growing mistrust in scientific institutions like the FDA." [23] -> To return to this video, these two WSJ reporters show an incredible level of ignorance and arrogance -> Finley says that the drug is "clearly" beneficial by misreading the secondary endpoints, just like Marks did -> An FDA memo from last year says about these endpoints: "Under these circumstances, they are misleading and cannot guide any stakeholdersโ€”including patients, family members and caregivers, and prescribersโ€”in making informed decisions about the potential benefit of treatment with ELEVIDYS." [20] -> It really doesn't get any clearer than that -> But these two journalists are overruling the actual scientists, just like Marks did -> One of the most incredible comments during this interview was the complaint that "90% of clinical trials fail", as if that's bad thing [1] -> It's actually a good thing; most drugs suck; failing in clinical trial actually allows us to use only the drugs that don't suck -> These people don't understand the most fundamental purpose of the clinical trial -> They think clinical trials failing is a bad thing, as if it means that patients now won't get to use a useful drug -> No, it's a good thing, because it means that patients won't be exposed unnecessarily to a useless drug that might harm them -> The level of ignorance really is unbelievable -> What's worse is that these "journalists" defend their decision -> But what they did is exploit social media hysteria caused by Laura Loomer [1,7] -> Following up on her heels with editorials, using her as pharma attack dog [1,4] -> This is a huge blow to WSJ's credibility, and they know it -> Unbelievably shameful Where do we go from here? -> The Vinay Prasad firing creates a serious crisis of credibility at FDA [2,6] -> Up to this point, we could call these approvals a difference of opinion, but as we've seen, that's a huge stretch -> But any illusion of that is now shattered: the firing shows that drug regulation is explicitly political -> Janet Woodcock: approve, keep job -> Peter Marks: approve, keep job -> Vinay Prasad: block, transparently fired -> Make a decision that is anti-pharma and lose your job: that's the message -> Who can trust any decision at FDA anymore? -> RFK Jr. and Marty Makary both stand behind Vinay Prasad [24] -> Trump went along with lockdowns, he went along with mask mandates, he went along with all of the Covid pseudoscience that he now decries -> He should reverse course and not go along with this -> Trump has created a profound crisis of credibility at FDA and needs to fix it

Kevin Bass

80,314 views โ€ข 1 year ago