Loading video...

Video Failed to Load

Go Home

Q: Which country are you most looking forward to visit next with your Mamay? Hahaha... napakunot noo tuloy si Sheena Sheena: "Ha? Anong with your Mamay? Ha? Ha?" (Binulungan siguro sya na Lola) Sheena. "It's not Mamay, that's my nickname. It's Amma. Oh my gosh! This Bloom.... Hindi ka...

81,739 views • 4 days ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Coach Matthew Almodovar's birthday message: Happy birthday, Shee. Knina naglalakad ako sa, kasi may break time—so magkukwento ako guys, ah, sorry. Mabilis lang to—so lumabas ako kanina to get coffee, tapos may nagabot sakin ng picture mo. Basta yung may "Happy Birthday Sheena" tapos nakita ko... na dun ko narealize na parang, "Shucks, nagma-mature na nga si Sheena." Tapos parang nung nakita ko yung picture, feeling ko parang nagflashback yung trainee days. [...] Parang sobrang bebe mo lang, ganyan. I mean, in my eyes you're still that girl. But like, looking at those pictures, parang I saw them na kung ano na yung mga na accomplish mo. Hindi lang, like, yung awards but like all the things that you went through. [...] So parang for me, such a blessing to witness and also somehow be a part of it, parang sobrang blessing sakin. And parang napag-usapan na namin ni Lord to eh, sabi ko kay Lord parang, kahit anong mangyari, I'll be there for you. Like if you want a dad, a mom, a lolo, kahit aso pa. Tatahol ako para sayo if you needed. No pressure, if you needed. Yeah, so yun lang. Masaya ako kung paano ka ngayon as a person. I feel like what you're giving now to BINI, and to a lot of people here, hindi lang siya yung talent eh, but also your personality. Na parang sobrang nabi-bless kami. You make me laugh sobra, as in parang makita pa lang kita, actually kahit wala ka pang sinasabi! Natatawa na ako. But I feel like hindi nya kasalanan yun. Yung energy niya lang talaga kasi sobrang bright. So salamat sa life mo, and I love you Shee, grabe. I love you. BINI SHEENA 22RIFIC YEARS #twenSHEEtwo #MagpaSHEEkat #BINI_Sheena

່͏

15,126 views • 2 months ago

sheena's final ment Thank you everyone who came tonight, grabe. Thank you for buying tickets. Thank you for spending your—anong araw ngayon?—your Saturday with us. Thank you for all the greetings, all the gifts. Thank you to all the performers na nagperform today, grabe I can't believe na nakuha kayo lahat [...] But thank you so much, fantasy ko to, and the drag queens, thank you so much po, like... totoo yung sinabi ni Trish, honestly, sabi ko, "Wag na, gastos lang yan. Magbouldering nalang tayo." Mga ganun ganun. Pero I trusted you and look, oh. It's a success. [...] I know this is for me, but know na this is also for you. I know na if I'm happy, you're also happy. [...] Sobrang tagal na sakin ni Trish, since PBB pa lang. That's why I really appreciate her. And sobrang bata pa nya, obvious naman (laughs). Pero sobrang matured nya magisip and sa kanya rin ako kumukuha ng mga advice sa mga bagay bagay. I really love it. And of course, timshi thank you so much. Thank you El, thank you ate Gill, thank you Rai. Thank you. Thank you so much. Sobrang solid nila, feeling ko kaya kong mabuhay ng sila lang yung kasama ko... hindi, joke lang (laughs). Hindi ko kaya. But thank you. Thank you so much guys. Grabe, I feel so loved... kahit mukha akong relaxed lang na ano, pero, sobrang, sobra akong nata-touch. Siguro iiyak ko to pag-uwi. Pero I really appreciate na everyone na nandito for all the things you guys are doing for me. I don't know if I even deserve all of this, but thank you so much. Thank you Shinies. Ay grabe, Blooms! Shinies ko lang to gumawa ng grupo [...] Love it. Next Sheenayaw ha. Ayun lang. Thank you guys for coming. Grabe, I'm so happy... I'm so happy. Thank you Lord, thank you God. Good night, tara na (laughs). Maaga pa ako bukas. BINI SHEENA 22RIFIC YEARS #twenSHEEtwo #MagpaSHEEkat #BINI_Sheena

່͏

21,704 views • 2 months ago

"No matter how many achievements your idols unlock… you still don't look satisfied. You're loud, but not fulfilled. You're winning on paper, but still insecure in reality." - 🧹 Atecco, parang fandom nyo ata tinutukoy mo dito? 😂😂😂 wdym kattapos nyo lang sa kuchela at kung ano ano pang ganaps but then here your are, triggered sa 100k crowd ng SB19 solo con.😅 Hindi mahal ng masa? Okay sige inyo na yan, kasi yang masa na sinasabi mo are the same people who ridiculed and bashed your faves nung kasagsagan ng back to back issues nila. They'll hype and praise you for clout then disappear when things get rough. We don’t need fake support here. We're good with a solid, dedicated A'TIN community that consistently shows up, filling venues like SMDC open grounds and even sustaining two consecutive days at the PH Arena.😄😌 flex ko lang din, 3 years old palang si 1Z Entertainment but they're already ✨thriving✨ dahil sa joint force ng 1Z, brand partners, & A'TIN. I can't say the same for....🤭 emeeeeeee! Atp, I'm not even angry, nattawa nalang tlaga ako sa mga sinasabi nyo against SB19, kasi nung naglalakad kami papunta sa SMDC together with this sea of A'TIN from different age groups, i realized na wow ganito pala karami ang sumusuporta sa Esbi.🥹 sure, most of us hindi pala-socmed (baka kasi ang basehan nyo ay likes at views sa tiktok 😂) but we show up where it matters and when it counts. 🥰

ɪᴛʟ⦵ɢ ɴɪ ᴘᴀʙʟ⦵ 🥚

51,425 views • 2 months ago

CEO of JPMorgan, Jamie Dimon, shares his top career advice: "Work hard. There's no such thing as success without hard work. So some people have this quick get-rich-quick notion. I've never seen it. I mean, maybe it's like a casino. Maybe it's happened, but it's not the normal way. Second, you're going to spend your life learning. You know, I read four or five newspapers every morning. I read tons of stuff. I read everything that people send me. When you go out on the road, learn, learn, learn. You learn from clients, learn from competitors. When we meet with small businesses, you're always learning. And that could be a small thing that someone said, why do you do this? You say, my God, we should do that differently. It's a very large thing. Even innovation sometimes is not an aha. It's a lot of little things added on top of each other. The iPhone was 3G. You know, the glass, the semiconductors, the batteries. It wasn't one thing that created an iPhone. So learn, learn, learn. Treat people the way you want to be treated. You know, like have respect for people and be willing to change your job a little bit. Don't worry about your income level. You know people focus. Oh my god. I take that job I love the people but it's less money. Y ou know what sometimes it's the absolute right thing to do So be a little bit of flexible and the job you take and try you know in your in your lifetime. You should be prepared to do a bunch of different things. We tell people it's your job to take care of your mind, your body, your spirit, your soul, your friends, your family. You need to do that at any level because if you don't know you probably won't be a particularly productive worker we can help and but we can't do it for you. We can provide opportunities, but we can't do it for you. Second, you know, when you're... Wait, so what does that mean? You want people to basically say, I'm going to leave, I've got to... Yes. You've got to go take care of your kid's baseball game. You don't feel well. You need a spiritual getaway. You should do those things, and it can be done. Most of the people in my life who are always fringy, they can't get it done, I always tell them, it's you. It's not the company. There are a lot of people doing that exact same job, and they're always at peace and at ease, and they have their family time. You know, if you're a male who just had a bunch of babies, you know, maybe you can't play golf every day in the weekends. Maybe you got to just cut back on other things and focus on that. You can't give kids, for example, quality time only. You don't get the quality without quantity. And I tell people, so you have to arrange your life so it works for you in a way that you're taking care of your health. When I go travel overseas, I schedule exercise time. Management is get it done, follow up, discipline, planning, analysis, facts, facts, facts, analysis, get the right people in the room. You know, kill the bureaucracy, all these various things are going to get done, which if you don't, you won't be particularly good. But the real keys to leadership aren't just doing that or making sure it's done, but having people who want to work at the place. So you might want to work for me if you trust me. If you know what I care about is the client, the country, something different. If the person's selfish, you know, blames you and takes the credit, you're not going to want to work there. So to me, humility openness, fairness, being authentic, that's what creates leadership. Not that they're the smartest person in the room or the hardest working person in the room. And you can, you know, if you made a list of good CEOs, it's not their charisma, it's not always their brainpower, but you won't be a good CEO without that because people want to work there. And so to me, that is a whole different way of making sure you manage it."

Black Edge

52,072 views • 4 months ago

Stop perma full clearing if you want to win games Video below explaining it but i am providing a transcript for anyone that doesnt speak english to translate or maybe that are deaf You are losing games by full clearing now. What I mean by this isn't that full clearing is inherently bad. What I mean is that lot of people get stuck thinking they just have to full clear the problem is once you get your first item, a lot of the time it's actually best to just not full clear. Because when you get your first item and especially when you're ahead, you should be looking to do things actively on the map. Because if you just full clear, you're giving the enemy essentially, breathing space. And if they're behind, they shouldn't have breathing space. If you're just full clearing and they're full clearing, you're giving They equal gold, which you never want to do when you're ahead, because any they get is going to be worth more than any gold you get, because of percentages. so whenever you're strong like this, you want to look for ways you can impact the map instead of full clearing. Especially since, in this scenario here, I can see my entire top side is warded. So even if I do get invaded and lose my camps, I at least know it's getting invaded. and I can account for that and do something else here. So, my bot lane just came out of base, fresh items, so they're also strong. So they're also looking to fight. Here I need to wait for them to push one more way before dragon. So I'm just going to take my red buff, and then we're going to look to do the dragon. And the reason this is so important is because we're both spiking. We just came from base. And the enemy has a very strong dragon fight. They have Lissandra, Rengar, and Ash Seraphine, which means Ash Seraphine should almost always have prio. So, if we don't take Dragon with this one timer, Ash Seraphine will always have prio, and then they have a strong 2v2 with the Slander Vengar. So, we have this one time to take it. If I was just to go full clear, my bot would never have prio ever again. This is our one window, and we're able to take the Dragon where my bot lane has prio. So instead of full clearing, I just go straight to the Dragon. And if there is a fight, I'm strong here because I'm on Item Spike, and so is my bot lane. So it's actually a decent fight. And then I can fast forward. So then Rengar ends up ganking my bot lane. I kill him. And then I'm recalling again because I have a decent buy here of 1500 gold. And it's going to be the same thing essentially here. I'm not just going to full clear. There's no reason to just full clear, right? I'm very strong. I have full item. I just bought 1500 gold worth of items. And top's kind of overextending here. So I'm just going to sprint straight top. And we don't end up killing, but we do get his ult and his flash. That's pretty worth. Could have honestly killed him if I Thresh missed his hook. It's a bit unlucky. But the point is. The point is to just not folklore. and I still get my camps guaranteed, and the most Rengar could take is just my raptors. I know he can't take my top side because I'm top side right. So the most I can lose is my raptors. And it's always worth it to just go for the kill top. If I lose my raptors now, it's earlier in the game, and it's a lot harder to break your full clear because you do get punished more. Because one, it's harder to kill people because have less items, less damage, less cooldown stuff like that. It's harder to farm it takes longer. So more camps, you're more your camps are sitting the longer it's going to take for you to clear them. And then, if you do lose camps early game, it snowballs way harder. So I'd say once you get your upgraded Smite, like your Rainbow Smite, like your first upgraded Smite, that's when it's a little bit easier to skip camps. You basically don't really want to break your full clear aside from that. But once you get your first item, for sure, you want to be skipping camps to look for proactive plays. You don't have to go for plays just to go for plays, but you should be looking for that. So I hope that was pretty helpful. Any questions, you can just always DM me or comment below and I'll try to get back to you.

Griffin

635,276 views • 3 months ago

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

Himanshu Kumar

37,367 views • 3 months ago

The most epic 13 minute AI rant I've heard in 2026 PS: My parent's heard this when I was playing it in the car and thought Jason ✨👾SaaStr.Ai✨ Lemkin went OFF like Stephen A Smith does on first take PPS: Full transcript below [17:00] Harry Stebbings: I I just wanted to ask Jason, if the people that we want are fundamentally different, the developers that we used to hire, we don't because AI writes the code for us. The marketers we don't want, the sales people we don't want—who who do we want genuinely? Like what is the attractive profile? Because your Anthropic’s and your OpenAIs are hiring, so so what are the people that we want in the companies of the future? [17:18] Jason Lemkin: Look, I know it sounds trite, but but the answer is simple. It's just the expression each year changes. We want folks that are genuinely AI fluent. It's pretty simple. Now you know, maybe last year we called them prompt engineers, right? That used to be a job. I don't know if you remember that actually used to be the hottest job on planet earth. Now no one needs a prompt engineer because it's pretty easy to prompt all these tools. That job died. Okay. Um and now we need go-to-market engineers. Um I think that job's going to die. We need—everyone needs so many forward deployed engineers. Like you can't hire enough forward deployed engineers. But uh you know um but Palantir just announced in whatever their their big their big event—they've gotten their deployment times down over 90% with forward deployed engineers. So that may become—so the this wave of disruption for the titles and the specificity, it's also exhaustingly accelerating. But it's really simple. You meet anyone for any role—sales, marketing, engineering, product, QA—they're they're either they're either they can't keep all of the ways they use AI to accelerate their job from spewing out of their mouth, or they're staring at you. It's there's nowhere in the middle. Like, and the person that comes in and says—it's it's it sounds Captain Obvious—but like, you know, you just had the whatever from Lovable, the the marketing head that was super popular on the show, right? She's just spewing AI-native insights into Lovable, right? It's not that complicated. You hire her, Elena, or whatever it is. You just hire her. It doesn't matter whether she's still in college or a junior or a senior or a middler, a left or right. And honestly, if you interview people, I would say of all even of the best startups I've invested in, maybe 30% of the management team meets this standard at best. 30%. Maybe less. And of the interviews I do in general, it's single-digit percents. It's just and in in that sense, it's the same as ever. Like you either lower the bar in hiring or you hire someone that's actually great. And someone that's actually great is so far ahead of you in how to apply to to employ the efficiencies of AI in their role, your jaw falls on the table. The difference is we used to need warm bodies. That's what's changing. We used to need warm bodies to answer the call, to do QA, to do code review, to to get the blue pixel to go from the upper left to the lower right. You laugh, but you need you literally needed to brute force this with humans. With AI, every day that goes by, the AI—you do not need brute force human beings on your team. And that's another reason they're shrinking. Why are all these new companies so efficient? They're just not brute forcing things with humans. They're just not. They're choosing not to. And so these team—all the brute forcers out there—everyone talks about how bloated teams got in 2021. I don't agree with that. I think they got as big as they needed to be when growth was high and you needed humans to do everything. All you look at these teams that that doubled—well if growth continued at 60% like the rate in early 2021 for 5 years or can help me do the math and every single thing a software company did required a human. You were understaffed by your 2021 headcount. You'd be sitting here in 2026. You every office in SoMa would be triple packed and you there wouldn't be enough humans to staff your company. It's just the world changed. [20:33] Harry Stebbings: Jason, you live on the bleeding edge. I think me and Rory see that and I think the world sees that when they hear you every week in terms of how you run SaaS. For all of the CEOs and execs who listen to the show, what would you advise them in terms of determining whether someone is AI fluent when they meet them for jobs, for talent? [20:51] Jason Lemkin: Here's I realized I was just asked this. I just did a review with a super fast startup growing just crossing 100 million and I was asked this question. And one of my favorite executives, I thought his answer was pretty dated and because he gave me an answer that was about 6 months old. The answer 6 months old is: "I look for folks in my team, I look for you know at what tools they play with." Okay, that was a great answer in like summer of 2025. Okay, I tried Lovable last week. Okay, the answer in 2026 is: "What commercial AI tool have you brought into your organization this month?" That's the test. Anyone that is on the bleeding edge that you would want to hire—now there are so many great products in the market. Okay, there is no excuse in any role to have not brought one tool a month into your organization. Okay, there—now there's going to be better and better tools and better and better products as the year goes on. What's the one you did? And you will see folks with their deer in the headlights to this question. What what sales tool? What marketing tool? What product tool? What engineering tool? What did you bring in? Why did you pick it? How does it working? Because if you're at remotely at the cutting edge, you're all over this. You're looking for the next agentic tools that will radically improve how you do business. This is—you think everyone thinks SaaS is at the bleeding edge, right? You know, you know, all we do is we're just looking for the tools and trying them. Okay? Okay, we're one year ahead of everybody else because we did the simplest thing in the world. Like we tried the tools early and we trained them. We trained them for a month. Okay, I'll give you—want hear a horrible example from this week? Super hot AI company valued at 6 billion. Okay, I'm not going to name it. Um, this week yesterday told us we had to quadruple what we spent on their product. Okay, their agent told us, right? And why did this happen? Okay. Well, at this $6 billion company, no one had trained the agent on its pricing properly. No one had tested it. They said, "Well, well, we've been in beta." And we said, "Well, when did the beta launch? A year ago." Okay, these are people asleep at at the wheel. You want somebody who the instant this comes up, they exactly know what the issue is. And "Hey, when I was at Lovable Replit, we trained the agent. This is how we did it. I brought in this tool. I brought in this tool that that Rory invested in last week. It solved all these issues." That's what you want to hear. And if they haven't brought in a tool in the last 30 days, at least deeply evaluated it. I don't really care whether they bought it, but gone so far down the funnel they can tell you—pick whatever tool: Fixie, Regie, GC, AIGC—I don't care how you went through it, you looked at it, you can tell me the eight ways it would improve the productivity of your business and three you didn't. Just don't hire that person because they're going to run your company to the ground. This is the job today. The job today is not to screw around on ChatGPT and to be a prompt engineer. The job today is to bring the best AI and agentic products into your organization and leverage all the hard work that the engineers have done building those products. That's your job. You don't have to screw around. You don't have to be a prompt engineer anymore. You have to be an agent deployment expert. A—this is the new job we're making up today. An Agentic Deployment Expert. That's your job from C-level to junior. Agentic Deployment Expert. Don't hire anybody else. You're going to regret it. They're going to stare at the camera. He's good. Stare at the camera. He's honorable. We could probably just I could slip away, get a coffee, and come back. No. And I I sound exasperated, Rory. And I—but the reason I am is I can just see I can see my best companies doing it. And I can see some companies I've invested in not doing it. And I want to cry. I just want to cry when they have no ADs on their team. I just—like you're flushing your years of your life down the toilet by not approaching your how you're building this company this way. [24:33] Rory: Yes. And at the risk of being positive, it's worth pointing out two things he didn't say. Well, something implicit why he said—Jason didn't do the only hire, you know, he didn't commit the um employment law, I think it's a civil penalty of saying only employ people below X who get the new new thing because he implicitly said anyone can do it provided you're willing to learn. And I think that's the big aha that's one of the positive statements to make here right? Look and I think it applies—I'm always wary of being "Hey, coming across, hey this this is the things that you all have to do." I think it applies to everyone including investors right? I mean I will say I have found that unless you're willing to invest the time learning these tools you actually shouldn't be investing in them. One of my partners Andy had this expression: "You know, if you decide you want to stop learning new things you probably should retire within 6 to 12 months and never write another check again." Maybe that's down to 3 to 6 months at this stage, right? And I think, you know, it's— [25:27] Harry Stebbings: Yeah, I actually I actually had a meeting with mine and Jason's biggest investor the other day and I—pretend he's not here—I said I think he's the most equipped investor for this generation of investing because I don't think anyone quite sits at the bleeding edge like he does on the investor side. [25:42] Harry Stebbings: Why in terms of using the equip stuff? Yeah. Yeah. In terms of using the stuff, understanding understanding bottlenecks, constraints. For sure. [25:51] Jason Lemkin: But can I just add one point? We can just cuz it's so important if it helps people. Okay, we are—and thank you Harry. We're going through these phases. Okay, and when AI started to blow up for real for us, uh call it early 2024, right? Maybe late '23, I wasn't equipped. It was too technical. I wasn't going to go in and figure out—I wasn't smart enough to figure out how to deal with a massively hallucinating LLM API and turn that and turn that into something magical. Kudos to investors and others that that got it in early '23, '22. I mean I remember I—I guess it was maybe SaaStr Annual '23. I was with David Sacks and I did a Q&A and I said, "How you thinking about AI at Craft?" He's like, "Well we're all in. We want 80% of '23 of investments to be AI." I'm like, "Great but like show me the show me the great ones in market." He's like, "They're all prototypes. We're all they're all they're all proof of concepts but we're all in anyway." That's where you kind of had to be in '23 if you weren't investing at like the LLM level. Okay, I wasn't smart enough. Then we went through this weird-ass prompt engineer era where like you you could torture these products to do something good, right? But you had to torture them. You had to like craft these crazy things that made no sense. Now we are in the era where mere ordinarily smart generalists can make these tools do magical things. And literally I go to these meetings and people be like, "I don't know how to like this is so scary. I don't know how to do this." And we show them our backends. Do you know how to do a workflow generator? Do you know how to do a a decision tree? Like we've been building these since software in the '90s. Okay, if you—I can show you all of our agents. The how they work is novel. They do have to be trained. You can't be lazy and have these agents work. But honestly, the the UI, the UX, the way we interact with them, it's just software. And so my point is: Pick yourself off the ground. This is your time now. If you felt lost in AI era, if you felt like you're behind, you don't understand what all these people are saying on X and Twitter and their Claude and and their and talking about all the 4.6 point Nano point and it's over—like you just it's not your world. This is your time. This is your time for the generalist that knows how to use software tools really really well. And I—this is my last point but it's so important. If ever in your recent life—and this is why you could be all you need to be is young at heart to Rory's point—if in the last three to five years you have successfully deployed a piece of enterprise software of any sort you yourself, not some agency you hired, but if you have deployed it, you can deploy any agentic tool. Any. And you can become the hero in your company and you can become the hero in your functional area. But I watch folks—I'm literally helping a company now that they're adding hundreds of sales folks this year with a new pre-IPO COO—he's not hasn't brought in a single tool, totally scared of it. Okay, it's not that hard. Did you use SalesLoft? Did you use Outreach? Did you use HubSpot? Do you know these tools? If you can deploy these tools, you can deploy a world-changing AI agent. And so this is the time for people like the folks that that were shut out of the AI revolution right now. The generalist folks that are not that know how to deploy software that don't even know how to build software. Like vibe coding for me was folks who knew how to build software, but you didn't have to be an engineer. Now, you just need to know how to deploy software to win with AI agents. That's all you need to know. So many people have these skills and they're petrified of AI. "How did you do that? How did you deploy an AI BDR?" Well, we bought a piece of software, we figured out how it worked for a day, we set it up in an afternoon, and then and then we did spend 30 months training it, which you didn't do with this old software because in the old days, we just had to manually upload all the data, right? And there was no training. The the only non-intuitive part is training these things. And it's it's it's just work. So that's why when I see folks on the management team not doing this, there's no excuse. You do not need to be technical to win with AI agents in Q2 of '26. You do not need to be even 1% technical. Not at all. So it's your time. Or you're going to get laid off. Or you're going to get laid off because you're not going to matter.

Arjun Mahadevan (Mr. LLC 🇺🇸)

37,596 views • 4 months ago

🚨 Rep. LUISTRO DARES TO ASK THE UNASKABLE🚨 Congresswoman Gerville “Jinky Bitrics” Luistro, unshaken and fearless, confronts former President Duterte in a gripping interpellation, seeking clarity and accountability for the war on drugs and its chilling legacy. Emphasizing his promise to take full legal responsibility, Luistro probes: What happened to the bodies buried in Laud Quarry? To the victims of the Davao Death Squad? To the lives lost in the 2004 Dumoy raid? Former President Duterte fires back, asking, "Where is your proof?" Luistro responds: "Mr. President, I’m anchoring my questions about these separate incidents from your initial statement—that you are taking full legal responsibility for all the victims of the war on drugs, both legal and illegal. You are a long-time prosecutor, and of course, it is fundamental among us all lawyers to uphold the requirements of due process." Duterte counters with: "We are zeroing in on a particular individual now." Luistro powerfully reminds: "Mr. President, due process is the law that hears before it condemns. Due process is the law that requires notice and hearing." The former president’s short rebuttal, "If you say so," leaves the air thick with tension. Luistro quips back with another gripping reminder: "Mister President, I hope that we will be reminded that by due process, THE END DOES NOT JUSTIFY THE MEANS." Congresswoman Luistro proceeds to present statistics on the war on drugs: - 6,252 individuals killed in police anti-drug operations as of May 2022. - 27,000 to 30,000 individuals killed, including vigilante-style executions. - 427 activists, human rights defenders, and grassroots leaders killed as of December 2021. - 166 land and environmental defenders killed as of December 2020. - 23 journalists and media workers killed as of April 2022. - 66 judges, lawyers, and prosecutors killed as of December 2021. - 28 mayors and vice mayors killed as of December 2021. Cong. Luistro then delivers the crucial question: "Mr. President, my question is: When you implemented the war on drugs, did you strictly comply with the requirements of due process?" With a firm and unwavering tone, former President Duterte responds, "YES." She continues, pointing out: "It is my humble submission that, contrary to the answer of the former president, I humbly believe that the war on drugs never complied with the requirements of due process. The statistics show the huge number of victims of the war on drugs. If my memory serves me right, during the Aquino administration, there were around 200 victims, and during the present administration, there are around 200 victims as well. Given these statistics, there are almost or around 31,000 victims. If indeed they followed the requirements of due process, there should not have been this many deaths. Instead, there should have been many cases pending in court. I hope that all of us are reminded by the fundamental law that no person should be deprived of life, liberty, or property without due process of law. It is the humble submission of this representation that the Quad Comm is ready to make a recommendation for the filing of the necessary actions in court for violations of RA 9851—an act defining and penalizing crimes against international humanitarian law—or, at the very least, for murder cases as defined under the Revised Penal Code." The Interpellation Intensifies To conclude her interpellation, she delivers a series of no-holds-barred questions: Luistro: "Mr. President, three Chinese drug lords were killed at the Davao Penal Colony. Are you willing to take accountability and responsibility for this?" Duterte: "Wala ako sa Davao, nandito na ako sa Manila." Luistro: "Are you saying no?" Duterte: "If gusto mong isali yan, idagdag mo, ok lang." Luistro: "How about the death of General (Ret.) Barayuga? Are you willing to take full legal responsibility for this?" Duterte: "No, I do not kill generals." Luistro: "The death of Mayor Parojinog and the 15 others in Ozamiz City. Are you taking full responsibility for this?" Duterte: "Hindi ako nagpapatay ng mga mayor, ma’am." Luistro: "The death of Mayor Espinosa of Albuera, Leyte. Are you taking full responsibility for this?" Duterte: "That is my birthplace." Luistro: "The death of Mayor Toni Halili of Tanauan City?" Duterte: "Malayo yan sa akin, ma’am." Luistro: "The death of Mayor Perez of Los Baños?" Duterte: "Lalo na." A Riveting Ending Luistro fires back: "If you are denying all these, alin po yung tinutukoy niyo when you said you are taking full responsibility for all the victims of the war on drugs, both legal and illegal?" The former president mumbles in response: "Yes, kasi order ko kasi yung, that is my campaign against drugs. Alam mo maraming estasyon, maraming police. Kung nagkaleche-leche doon, hindi ako maghuhugas ng kamay. Of course, nagkamali sila. If there is an appropriate action na gusto niyong ilabas, then file a case in court. I’m challenging anybody or everybody who makes the accusation, whether it is really true or not—maybe true—file the case in court, because may korte tayo. Even if I admit na totoo yan, because I will make the admission there again." Luistro counters: "Are you saying, Mr. President, when you go to court, you are willing to admit accountability for all the deaths during the war on drugs?" Duterte replies: "Of course, may abogado ako, ma’am. Kung ano ang sasabihin ng abogado ko, susunod ako." Luistro presses further: "I hope that everything you said before the Quad can be reduced in writing so that truly we can believe that you are taking full legal responsibility for all the victims of the war on drugs, both legal and illegal. Because as lawyers, we believe that by extrajudicial confession, we have to put that in writing, Mr. President." Duterte responds: "...It’s a policy of government or the president. Hindi ako maghuhugas ng kamay..." The Final Question Luistro asks: "If one of these days the ICC will come, will you voluntarily submit yourself?" Duterte retorts: "Sipain ko pa sila, ma’am." Luistro reminds him: "But you said a while ago, that if somebody will sponsor your fare to the ICC, you will voluntarily submit yourself to their investigation and jurisdiction." Duterte replies: "Yes, pero kung sila pumunta dito, sipain ko." Luistro clarifies: "But will you confirm that you are willing to voluntarily submit yourself to the ICC?" Duterte firmly states: "Oo, punta ako doon, sipain ko din sila." A Gripping Conclusion Luistro ends her interpellation with grace and precision: "I have nothing further. Thank you, Mr. President." In this powerful exchange, Congresswoman Luistro demonstrates fearless leadership and unwavering commitment to truth and accountability, leaving no question unanswered in her pursuit of justice. #LargaLuistro2025

Informed PH

257,167 views • 1 year ago

BBFF2026 PRESS TOUR D1 #BBFanFest2026LIVED1 🎤: How abt you guys? What pair do you guys fill up on, bc a lot of the other pairs are filling up on you. 🗣️: Actually, don't they get their fill on themselves? 🐰: Oh, so you already know we get our fill of each other? 🎤: How abt the other pairs? 🦊: Today, I've kinda been getting my fill of P'Kapook. 🗣️: (studio goes wild) Ciize: Only P'Kapook??? 🦊: I feel like I've never seen her like this before. It's surprising me. 🎤: You usually see her in still photos. 🦊: She's someone who really draws your attention and makes you want to look at her. 🐰: I was going yes yes, along with her. 🦊: She's beautiful and funny too. My heart is beating fast, what did I say. Kapook: She's wondering what I'm going to say next. 🐰: And she's funny with a deadpan face. She's funny in a way that I'm not prepared or expecting that she's abt to say something funny. That's really amazing. 🦊: Usually, when I see photos of her I already think she's beautiful, but today she's even more beautiful than I've seen in photos. And on top of that she's funny too. She's really cute. 🎤: Hang on, Emi, you're not abt to commit a crime here, right? 🦊: Seriously, I can't stop looking at her. 🐰: 🙂 Ciize: P'Emi, look at the camera. 🐰: I've taken note, I've taken note. 🦊: Sitting there, I'd have to look at you like this to see you! (bends forward to look at Bonnie's face) 🗣️: (studio goes wild) 🐰: There's no need to say anything! 🦊: But I just have to turn around and I can see her. Kapook: Clear things up among yourselves, okay? This top (seme) has nothing to do with it (runs her fingers through her hair handsomely) 😌 🗣️: (studio goes even wilder) 👥: 🤣🤣🤣🤣🤣 🦊: (doesn't fall on the floor, but leaves her chair and the frame altogether) 🐰: Hey, that's a really geung* move. 🦊: Can I absorb some of that from you? 🐰: Try doing it, try doing it. 🦊: This top (seme) has nothing to do with it na kub (tries to do the same slick move). 🦊: This is my first time understanding what geung means. 🦊: This top (seme) has nothing to do with it na kub. * กึง (geung) refers to someone who acts masculine or tough in public, but in private they're actually feminine. It's slang originating from the gay men community.

K-bab

26,389 views • 3 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,376 views • 3 months ago

Steve Jobs gave a 15-minute speech at Stanford in 2005 that still changes lives today: "Today I want to tell you three stories from my life. That's it. No big deal. Just three stories." Story 1: Connecting the dots "I dropped out of Reed College after the first 6 months. I couldn't see the value in it. I had no idea what I wanted to do with my life, and here I was spending all of the money my parents had saved their entire life. So I decided to drop out and trust that it would all work out. It was pretty scary at the time, but looking back, it was one of the best decisions I ever made." Steve shares what happened next: "Because I had dropped out, I decided to take a calligraphy class. I learned about serif and sans-serif typefaces, about varying the space between letter combinations, about what makes great typography great. None of this had even a hope of any practical application in my life. But ten years later, when we were designing the first Macintosh, it all came back to me. It was the first computer with beautiful typography." He reflects: "You can't connect the dots looking forward. You can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something: your gut, destiny, life, karma, whatever. Believing that the dots will connect down the road will give you the confidence to follow your heart, even when it leads you off the well-worn path." Story 2: Love and loss "At 30, I got fired from Apple, the company I started. What had been the focus of my entire adult life was gone. It was devastating. I was a very public failure, and I even thought about running away from the valley." Steve explains what saved him: "But something slowly began to dawn on me, I still loved what I did. The turn of events at Apple had not changed that one bit. I had been rejected, but I was still in love. And so I decided to start over." He shares what came next: "Getting fired from Apple was the best thing that could have ever happened to me. The heaviness of being successful was replaced by the lightness of being a beginner again. During the next five years, I started NeXT, started Pixar, and fell in love with an amazing woman who would become my wife. I'm pretty sure none of this would have happened if I hadn't been fired from Apple." His advice: "Your work is going to fill a large part of your life. The only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven't found it yet, keep looking. Don't settle." Story 3: Death "When I was 17, I read a quote: 'If you live each day as if it was your last, someday you'll most certainly be right.' Since then, for the past 33 years, I have looked in the mirror every morning and asked myself: 'If today were the last day of my life, would I want to do what I am about to do today?' And whenever the answer has been 'No' for too many days in a row, I know I need to change something." Steve shares why death is such a powerful tool: "Remembering that I'll be dead soon is the most important tool I've ever encountered to help me make the big choices in life. Almost everything, all external expectations, all pride, all fear of embarrassment or failure, these things just fall away in the face of death, leaving only what is truly important. You are already naked. There is no reason not to follow your heart." He concludes: "Your time is limited, so don't waste it living someone else's life. Don't be trapped by dogma, which is living with the results of other people's thinking. Don't let the noise of others' opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary." His final words: "Stay Hungry. Stay Foolish."

Jaynit

128,486 views • 4 months ago

🚨🚨Dr Mike Yeadon's Address to Northern Ireland Parliament ----------------------------------- Hello, my name is Dr. Mike Yeadon, and in the next 15 minutes or so, I would like to address those of you who've been vaccine injured or bereaved, and also those of you who are involved in the political process in Northern Ireland, as well as anywhere else in the world who might hear me. At the end of this process, I hope you will believe what I'm going to tell you, which, shockingly, is that the materials masquerading as vaccines were designed intentionally to harm the people who received them. I'm probably the most qualified former pharmaceutical company research executive in the world speaking out on this matter, and since I spent my entire career in the business of working with teams designing molecules to be new potential medicines, I think I am qualified to comment on it, and that is my shocking judgement that has been only reinforced over the last almost four years since I first said it. I'll also have some suggestions for what we can do together to fight against the global crime which is ongoing. So, just a little bit about me so you can decide whether or not to believe me. So, I'm a career-long research scientist. I've worked all of my life in the pharmaceutical industry and in biotech. My first degree included a training in toxicology, so that's an understanding of how materials can injure human beings at a molecular level, and what the relationship is between the structure of them and the toxicity. In my second degree, a PhD, I did research in respiratory pharmacology, control of breathing and control of respiratory reflexes. So, and then after that, I joined the pharmaceutical industry in 1988, and I worked until very recently on new medicines for allergic and respiratory diseases. In my corporate career, I was for a long time responsible at Pfizer, then the biggest research-based drug company in the world, for everything to do with allergic and respiratory diseases in the research field. So, that was my responsibility. And in the last 10 years, after leaving in 2011, I was an independent and I became the founder and CEO of a biotech company, which was eventually acquired by Novartis, which was then the biggest drug company in the world. So, I have had a good career, and I was well regarded in the industry for my scientific acumen and judgments, until, of course, I started speaking out against the nonsense, the COVID pandemic, and especially the so-called vaccines. I've become persona non grata. It was my former colleagues after that. So, I'm well qualified to comment on the toxicological principles, properties of molecules, and the kind of effects you might see from certain structures. So, just very briefly, before I talk about the so-called vaccines, what happened in 2020? It's taken me a long time to get there, and I haven't made everybody happy with the decision I've reached, but there was not a pandemic or a public health emergency. I don't think there was anything at all, apart from lies, propaganda, fear-based information, fake diagnostic tests called PCR, and then, as it were, misattribution of real illnesses that people did have, which were called COVID when there was no such thing. But what happened, shockingly, was that after the World Health Organisation's chairman called a pandemic, which was not true. There's never been a pandemic. There won't be pandemics. They're immunologically impossible. But after he called them, many countries in the world changed radically their medical management practises for people in hospitals, also in care homes, and in the community. And very briefly, in hospitals, many people were sedated, had a plastic tube put down their airway, and unconscious, put on mechanical ventilators. I can assure you that is not ever an appropriate treatment for someone with an influenza-like illness, whatever you might think COVID was. But that would not be something you would do, and if applied to frail and elderly people, they will die in large numbers, which they did. So that was the first crime. It's not a mistake. There are no mistakes here. Mistakes were not made. They were told to do this by figures at supranational level. We don't know exactly who, but we know this because these mad procedures changed in many countries all at the same time. So that's hospitals, in care homes, assisted living, old-age people's homes, and so on. Many people were given drugs like Midazolam, which is an injectable form of a drug like Valium, a sedative. But they were also given injections of pain-relieving drugs like morphine, even if they weren't in pain. My PhD was in the field of understanding what opiate drugs like morphine do to the respiratory reflux, and I can assure you it suppresses and suppresses it and depresses it. So if you give an elderly person on their own an injection of Midazolam, they will become sedated and sleepy, and if you give them an injection of morphine, their breathing will slow. I can tell you, it's absolutely forbidden to give a person those two drugs together, those two drug classes together, unless they are under intense ongoing medical monitoring. And the reason is they're likely to fall asleep and stop breathing. That, of course, is what happened. So that's hospitals and care homes. Your relatives were killed by the medical procedures that were imposed. Now, it's quite possible early on that not everybody involved knew what was happening, but I'm afraid after a few days, you'd have to be a blockhead not to realise that it was what you were doing to your charges, your patients, that was resulting in their deaths. So I've completely lost any trust in the medical profession because virtually no one has spoken up four and a half years later. This happens to lots of people. If you listen to the recordings, heartbreaking recordings given to the Scottish COVID Enquiry, I think that's probably the only place where there's been an official taking of evidence from people. And what I just described is exactly what happens to lots of people's relatives and no doubt happens to some people in Northern Ireland as well. It certainly happens in England. There were worse things as well. People in the community were deprived of medical care that would have saved their lives. And there's plenty of evidence to say that not being given antibiotics when they had incipient bronchial pneumonia also killed thousands, possibly tens of thousands of people. And there, ladies and gentlemen, was your pandemic. All of those deaths were attributed to COVID and you were told this is this terrible pandemic, you need to lock down, wear masks, do what you're told. Nothing was happening at all apart from medical murder and propaganda from the television and the newspaper, politicians and many public, well-known public figures who are doing what they were told. So of course one conclusion I'm going to come to later is stop listening to liars. The people who've lied to you shouldn't listen to them ever again. Stop listening to them today. But for me, I think the worst thing, because it comes out of my industry and because it's so deliberate, it requires such a lot of forethought, are the so-called vaccines. Now we were told there was this new infectious disease, so far so good ladies and gentlemen, but then they said don't worry we'll rustle up a vaccine and they did so at least in about 10 months, something like that. I can tell you after spending a career in this industry, you can no more make a baby in one month with nine women than you can make a complicated biological product in 10 months. It cannot be done. It was not done. They did something else. They created materials which were essentially injected poisons. They were not vaccines. There was never anything to vaccinate against. And when you've listened to what I've just told you, you know that must be true because you can't do something in 10 months that normally takes 6 to 12 years. Medicines are not put together randomly. They are built. And they're built by people who are discussing with colleagues, work out what kind of materials, what kind of structures, what kind of formulations, what kind of doses you would need to add in order to hit a particular molecular target to have a chance of a particular therapeutic goal being reached without unacceptable side effects. That's called rational design. And that is my whole career, ladies and gentlemen, from my undergraduate days to today. So when I look at the design of the medicine, whatever kind it is, and look at the design on paper and its composition structures and so on, it is as if I'm looking over the shoulder of the designer, someone like me, someone with my qualifications designed these things. So when I look at them, I'm looking over the shoulder of the designer and I can discern something of what their objectives were, what were they trying to do? And I came quickly to the conclusion that they wanted to bring about toxicity that would injure, kill and reduce fertility. There aren't any other alternatives. And remember, there was no public health emergency. So I'll just give you three examples. I'm not going to be too scientific, but three things so you can check them. The objective of these so-called gene-based vaccines was to inject you with a genetic sequence for something called spike protein. Now, it doesn't really matter what spike protein is, if it's real, where it came from. The point is, it's a genetic sequence for a protein that doesn't belong in your body. It's non-self, it's foreign. Your immune system is a wonderful work of God and nature. It distinguishes self, things that are meant to be inside you and are fine from anything else, foreign, non-self. If you inject a person with a genetic sequence that instructs your body to become a factory for some protein that doesn't belong in you, your immune system will detect that and it will attack every cell that's done that instruction and kill it. Now, these materials, when injected in your arm, didn't stay in your arm, they travelled around your heart, your lungs, your kidneys, your brain, your ovaries. And in every place it landed, if it was taken up and expressed, your body registered that as foreign invasion and it attacks and kills every cell doing it. There is no other possible consequence from doing that. So that's step one and no one can argue that's not what they did. That is the design of them. It also picks a particular protein. I'm not really sure where spike protein came from, if it's really real, but proteins like the one they claim was encoded in these gene-based materials are known to be toxic. There are loads of experiments, lots of published experiments, showing that proteins like that one cause blood coagulation, damaged nerves, damaged heart tissue. So they injected you with something that would make your body make a protein that doesn't belong there, knowing axiomatically, automatically, unavoidably, your immune system would attack that. It would be like rejecting an organ transplant. Your body would say, that's foreign, got to go, uses your immune system to kill it. And then they also inject you with something that's inherently toxic. So if it got out into your body or wherever it was made, it would harm you. And I've got a third one that cannot be argued with. At least the mRNA products from Pfizer and Moderna were encapsulated in something called lipid nanoparticles. It's really a blob of fat, complicated, technical blob of fat, that's what it is after all. And what that material did is allowed your injection to glide all around your body across all biological barriers and get everywhere in your body. So of course, it's not what you would want, is it? For something that they told you was inhaled into your nose and lungs. But no, it went all around your body, into your brain, blood vessels. But in particular, I need to tell you, there were publications that are now more than 10 years old in peer-reviewed journal articles. I'm sceptical about whether they're always very honest, but there were peer-reviewed journal articles showing that lipid nanoparticles were recognised over a decade ago of having a particular property, which you're not going to like to hear, which shocked me when I learned it. They tend to deposit their payload into the ovaries. That is exactly what happened with these injected materials. There was at least one study performed with the Pfizer agents, with the Japanese regulatory authorities. Lo and behold, the material accumulated in the ovaries of the test animals. That is what's happened, ladies and gentlemen, every woman and girl injected with these materials. Remember what I said about designing molecules to do things deliberately with objectives in mind? They picked lipid nanoparticles, knowing they accumulate the payload in ovaries. It's not an accident. Mistakes were not made. So I tell you, as a professional who spent his whole honest scientific career in an industry I did not realise was corrupt, trying to make experimental medicines for respiratory and allergy diseases, that my experience tells me that there are multiple independent, unnecessary and obvious mechanisms of toxicity built into these so-called vaccines. And then by sheer luck, all four companies, Moderna, Johnson & Johnson, AstraZeneca and Pfizer, all chose basically the same formula for their so-called vaccines. That would never happen if it was real. For a start, I would call my opposite numbers and say, we should do different things because if something goes wrong, if we're wrong in an assumption, all of the so-called vaccines will fail for the same reason. We should do different things. It's called diversification. But no, they all did the same things because they're just lying. They were making intentionally dangerous material, passing them off as vaccines to having you and your children. And that's what they did. Of course, I didn't get injected and neither did my children and most of my relatives. Some of them didn't believe me. I'm afraid they've been injected too. So big picture, what happens, I think from the research I've done, and of course, I'm an expert in research and development, not in politics, but I believe that very wealthy people, the kind of people who run foundations with names, have planned, as have their antecedents for a couple of generations, to take over the world, to remove the freedoms of ordinary people like us that they regard as useless eaters. They don't want us around anymore. And their intention is to strip us of our freedoms by persuading us that there are very frightening events occurring in the world, and we need them to lead us to safety. There are documents you can find from a group called the Club of Rome, who in the late 1960s were commissioned by some of these people who run the nameless global foundations that have hundreds of billions of pounds of worth. They were asked to come up with scenarios that would produce challenges for countries that couldn't be solved by countries on their own, so they would have to look outwards and upwards to supranational solutions. Now guess what? The two things they came up with, pandemics of infectious diseases, which I know as an immunologist are not possible and have never happened. The other thing they said to account for or plan for were climate change crises. I've done enough research now, ladies and gentlemen, I've spoken to people who have spent as long in climate atmospheric research as I have in pharmaceutical R&D, and they have explained to me, and I understand very well, that there's all of this nonsense about carbon dioxide, global boiling, net zero. It's all a complete scam from the same people who bought you the Covid scam and the dangerous injections. It's the same people. They want one world government, they want to be deprived of your liberty, and then I'm afraid I think they will kill us using these injections because they're going to do it again. All over the world, factories to make mRNA-based materials are being thrown up, billions of doses are being made, and if we let them they will sicken in our arms and people will sicken and die. So those of you who have been injured or bereaved, in my mind no blame whatsoever attaches to you. How could you know that people you trusted and thought you could trust were lying to you? Well, you didn't know, but if you let them inject you again, you have no sympathy for me because they have lied to you, you've been injured or killed, and I've explained to you that they're liars and they have attacked us. So if you go along with it, you cannot be saved. All we need to do is enough of us continue to speak out about this and say we're not having it anymore, get lost, don't listen to liars anymore. People who've lied to you forfeit their trust forever, in my view, and so anyone who's in the political process, for example in Northern Ireland looking at this so-called public health bill, which if you pass it would allow these supranational criminals to take you from your house, to inject you by force if necessary, they are aiding and abetting a global crime. And I saw someone online say recently that if you pass that legislation, I don't think it'd be unreasonable to interpret that as an act of war. It's as serious as that. So politicians, you may well be under pressure from shadowy figures, but if you go along with it and hope for like an easier time of it, you will have unlocked the doors of hell and pushed everybody in it and you as long with it as well. So this is your time to do what I'm doing, which is to speak out no matter the consequences. I say to you if you're frightened about what happens, if you speak out, you should be absolutely terrified about what's going to happen if you don't. So really that's all I've got to say. I do think these criminals are going to do it again, they're continuing to threaten us with pandemics like bird flu, monkey pox and so on. It is all nonsense. Stop listening to liars right now. Put things right between you, the people you love, and between you and God if you haven't already. And for goodness sake, be one of the people who speaks out no matter what the consequences, because if you don't, we'll lose our freedom and then our lives. Thank you.

aussie17

36,116 views • 1 year ago

Slovakian PM, Fico, Orbán 2.0 light, has ‘powerful and very important information’ for the European allies from putin and he says Europe needs someone who understands the 'Russian soul' to talk to putin. Journalist: “Thank you. I would also like to ask about your visit to Moscow. You mentioned that after your conversation with vladimir putin, you have serious messages for your partners in the European Union. So, what serious message is vladimir putin is sending to the European Union? Robert Fico: “I don't know, ma'am. Surely you don't expect that what I listened to and what I am supposed to say... I have already spoken, I spoke with the Czech Premier, Andrej Babiš. The most essential thing about these talks, ma'am, is that on one hand I am criticised, but believe me, afterwards when I go to the restroom, they follow me and ask me in that restroom: "Robert, what did putin say?" And I tell them. Why on earth don't you go to him and hold a dialogue? We must maintain a normal dialogue with Russia. Well, what is everyone... Hold on. Everyone was shocked when Russian president putin mentioned the name Schröder, suggesting he could be a communicator in this campaign or in this, this military operation. Yes, putin simply wants someone who knows at least a little bit about the Russian soul. You can't just take anyone and tell them to go negotiate peace between Russia and Ukraine when they don't know absolutely anything about that country. The conversation with mr president putin had two parts. The first part was before the delegation meeting, when we had to close the doors twice because we still hadn't finished our conversation. Those poor guys kept closing and opening the doors because we were already supposed to go inside, but we didn't go because we were still negotiating something. And then the one-on-one meeting continued after that session. And President putin states his positions very clearly, very clearly when it comes to the possibilities of peace. He states them very clearly. I think this is information that needs to be passed on to our partners, and that is what will happen. The next time I meet with them, I will speak about the outcomes of this visit, and we simply have to realise the frame of mind of the Russian political leadership as well. You know, you write with such joy that they are starving to death in Russia, that there is nothing there, and that it's a dead town. You are completely off track. That putin has no support and I don't know what else—you are completely off track. I think it is our duty to lead a serious dialogue with Russia, in which we show the same respect to our Russian partners as we do to our Ukrainian partners. And president putin always leads such a dialogue with me as well. He tells me things, and he genuinely tells me things that are so important to me. For example, during my last visit to Moscow, I was the first in the European Union to know that a ceasefire would be declared. I knew it because he said so. He said: "Well, I am talking to you now, so I'll tell you what, where, and how." So, if you'll excuse me, there are things here that European partners need to hear because, in my opinion, we are living in some strange illusion that this conflict can be resolved militarily. This conflict cannot be resolved militarily, unfortunately it only leads to tens of thousands of severely injured and dead people. So yes, I have powerful and very important information for the allies. When I am with them, I will certainly pass it on. I have already told Mr. Babiš the basic things.”

Yasmina

11,147 views • 2 months ago

Roger Federer: "Effortless is a myth. I worked very hard to make it look easy." "I left school at age 16 to play tennis full-time. So I never went to college. But I did graduate recently. I graduated tennis. I know the word is 'retire', but retired sounds awful. Like you, I finished one big thing and I'm moving on to the next. Like you, I'm figuring out what that is." Lesson 1: Effortless is a myth. "People would say my play was 'effortless.' Most of the time, they meant it as a compliment. But it frustrated me when they'd say, 'He barely broke a sweat' or 'Is he even trying?' The truth is, I had to work very hard to make it look easy." Roger shares the wake-up call: "An opponent at the Italian Open publicly questioned my mental discipline. He said, 'Roger will be the favorite for the first two hours. Then I'll be the favorite after that.' Everyone can play well the first two hours you're fit, you're fast, you're clear. After two hours, your legs get wobbly, your mind starts wandering, your discipline starts to fade. My parents, my coaches, even my rivals were calling me out. So I started to train harder. A lot harder." He explains the paradox: "I got the reputation for being 'effortless' because my warmups at tournaments were so casual that people didn't think I'd been training hard. But I had been working hard before the tournament when nobody was watching." Roger redefines talent: "Yes, talent matters. But talent has a broad definition. Most of the time, it's not about having a gift, it's about having grit. A great forehand can be called a talent. But discipline is also a talent. Patience is a talent. Trusting yourself is a talent. Embracing the process, loving the process, these are talents too. Some people are born with them. Everybody has to work at them." Lesson 2: It's only a point. "You can work harder than you thought possible and still lose. I have many times. Tennis is brutal. Every tournament ends the same way: one player gets a trophy. Every other player gets back on a plane, stares out the window, and thinks, 'How the hell did I miss that shot?'" Roger shares the statistic that changed his mindset: "In the 1,526 singles matches I played in my career, I won almost 80% of those matches. But what percentage of points do you think I won? Only 54%. Even top-ranked tennis players win barely more than half of the points they play." He explains what this teaches: "When you lose every second point on average, you learn not to dwell on every shot. You teach yourself to think: 'Okay, I double-faulted. It's only a point.' 'I came to the net and got passed again. It's only a point.' Even a great shot, an overhead backhand smash that ends up on ESPN's Top 10, that too is just a point." Roger shares the key mindset: "When you're playing a point, it has to be the most important thing in the world. And it is. But when it's behind you, it's behind you. This frees you to fully commit to the next point with intensity, clarity, and focus." He reflects on losing Wimbledon 2008: "Some call it the greatest match of all time. Okay, all respect to Rafa, but I think it would've been way better if I had won. Looking back, I feel like I lost at the very first point. I looked across the net and saw a guy who just a few weeks earlier crushed me in straight sets at the French Open. And I thought, 'This guy is maybe hungrier than I am.' It took me until the third set to remember 'Hey buddy, you're the five-time defending champion. You're on grass. You know how to do this.' But it came too late." Roger shares what champions understand: "The best in the world are not the best because they win every point. It's because they know they'll lose again and again, and have learned how to deal with it. You accept it. Cry it out if you need to. Then force a smile. Move on. Be relentless. Adapt and grow. Work harder, work smarter." Lesson 3: Life is bigger than the court. "A tennis court is 2,106 square feet. That's where singles matches happen. Not much bigger than a dorm room. I worked a lot, learned a lot, and ran a lot of miles in that small space. But the world is a whole lot bigger than that." Roger explains his philosophy: "Even when I was just starting out, I knew that tennis could show me the world, but tennis could never be the world. I knew that if I was lucky, I could play competitively until my late 30s, maybe even 41. But even when I was in the top five, it was important to me to have a life, a rewarding life full of travel, culture, friendships, and especially family. These are the reasons I never burned out." He shares what matters most: "Tennis has given me so many memories. But my off-court experiences are the ones I carry forward just as much. The places I've travelled, the platform that lets me give back, and most of all the people I've met along the way." Roger concludes: "Tennis, like life, is a team sport. Yes, you stand alone on your side of the net. But your success depends on your team, your coaches, your teammates, even your rivals. All these influences help make you who you are." His final words: "Whatever game you choose, give it your best. Go for your shots. Play free. Try everything. And most of all, be kind to one another, and have fun out there."

Jaynit

250,395 views • 3 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 • 2 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

14,195 views • 7 months ago