ๆญฃๅœจๅŠ ่ฝฝ่ง†้ข‘...

่ง†้ข‘ๅŠ ่ฝฝๅคฑ่ดฅ

"๐ถ๐‘Ž๐‘› ๐ผ โ„Ž๐‘Ž๐‘ฃ๐‘’ ๐‘Ž ๐‘Ÿ๐‘–๐‘‘๐‘’?" "๐‘‡๐‘œ ๐‘ฆ๐‘œ๐‘ข๐‘Ÿ ๐‘ค๐‘’๐‘‘๐‘‘๐‘–๐‘›๐‘”?" "๐ด๐‘ค๐‘Ž๐‘ฆ ๐‘“๐‘Ÿ๐‘œ๐‘š ๐‘š๐‘ฆ ๐‘ค๐‘’๐‘‘๐‘‘๐‘–๐‘›๐‘”." It's the summer of '99 and one week can change everything๐Ÿซ ๐ ๐š๐ฆ๐›๐ฅ๐ž๐ ๐จ๐ฎ๐ซ ๐ฌ๐จ๐ฎ๐ฅ๐ฌ ๐ญ๐จ ๐ญ๐ก๐ž ๐ฌ๐ฎ๐ฆ๐ฆ๐ž๐ซ / / ๐จ๐œ๐ญ๐จ๐›๐ž๐ซ ๐Ÿ๐Ÿ–๐ญ๐ก

32,525 ๆฌก่ง‚็œ‹ โ€ข 9 ไธชๆœˆๅ‰ โ€ขvia X (Twitter)

0 ๆก่ฏ„่ฎบ

ๆš‚ๆ— ่ฏ„่ฎบ

ๅŽŸๅง‹ๅธ–ๅญ็š„่ฏ„่ฎบๅฐ†ๆ˜พ็คบๅœจ่ฟ™้‡Œ

็›ธๅ…ณ่ง†้ข‘

โ€œDo not give into this carbon footprint thing. It is all just control.โ€ On his podcast today with Senator Bernie Sanders, Joe Rogan criticized the โ€œclimate crisisโ€ narrative, carbon taxes, 15 minute cities, and the lack of criticism on Chinaโ€™s unchecked emissions, suggesting that they are tools being used to get money and exert control over people. Hereโ€™s some of the dialogue: ๐’๐€๐๐ƒ๐„๐‘๐’: โ€œ[๐ผ] ๐‘˜๐‘›๐‘œ๐‘ค ๐‘กโ„Ž๐‘Ž๐‘ก ๐‘กโ„Ž๐‘’๐‘Ÿ๐‘’ ๐‘Ž๐‘Ÿ๐‘’ ๐‘ ๐‘œ๐‘š๐‘’ ๐‘๐‘’๐‘œ๐‘๐‘™๐‘’ ๐‘คโ„Ž๐‘œ ๐‘กโ„Ž๐‘–๐‘›๐‘˜ ๐‘๐‘™๐‘–๐‘š๐‘Ž๐‘ก๐‘’ ๐‘โ„Ž๐‘Ž๐‘›๐‘”๐‘’ ๐‘–๐‘  ๐‘Ž โ„Ž๐‘œ๐‘Ž๐‘ฅโ€”๐‘–๐‘ก ๐‘Ž๐‘–๐‘›โ€™๐‘ก ๐‘Ž โ„Ž๐‘œ๐‘Ž๐‘ฅ. ๐ผ ๐‘กโ„Ž๐‘–๐‘›๐‘˜ ๐‘กโ„Ž๐‘’ ๐‘™๐‘Ž๐‘ ๐‘ก ๐‘ก๐‘’๐‘› ๐‘ฆ๐‘’๐‘Ž๐‘Ÿ๐‘  โ„Ž๐‘Ž๐‘ฃ๐‘’ ๐‘๐‘’๐‘’๐‘› ๐‘กโ„Ž๐‘’ ๐‘ค๐‘Ž๐‘Ÿ๐‘š๐‘’๐‘ ๐‘ก ๐‘œ๐‘› ๐‘Ÿ๐‘’๐‘๐‘œ๐‘Ÿ๐‘‘...โ€ ๐‘๐Ž๐†๐€๐: โ€œ๐ผ ๐‘กโ„Ž๐‘–๐‘›๐‘˜ ๐‘กโ„Ž๐‘’ ๐‘๐‘™๐‘–๐‘š๐‘Ž๐‘ก๐‘’ ๐‘โ„Ž๐‘Ž๐‘›๐‘”๐‘’ ๐‘–๐‘ ๐‘ ๐‘ข๐‘’ ๐‘–๐‘  ๐‘ฃ๐‘’๐‘Ÿ๐‘ฆ ๐‘๐‘œ๐‘š๐‘๐‘™๐‘–๐‘๐‘Ž๐‘ก๐‘’๐‘‘. ๐ท๐‘–๐‘‘ ๐‘ฆ๐‘œ๐‘ข ๐‘ ๐‘’๐‘’ ๐‘กโ„Ž๐‘’ ๐‘Š๐‘Ž๐‘ โ„Ž๐‘–๐‘›๐‘”๐‘ก๐‘œ๐‘› ๐‘ƒ๐‘œ๐‘ ๐‘ก ๐‘๐‘–๐‘’๐‘๐‘’ ๐‘กโ„Ž๐‘Ž๐‘ก ๐‘กโ„Ž๐‘’๐‘ฆ ๐‘ค๐‘Ÿ๐‘œ๐‘ก๐‘’ ๐‘คโ„Ž๐‘’๐‘Ÿ๐‘’ ๐‘กโ„Ž๐‘’๐‘ฆ ๐‘‘๐‘–๐‘‘ ๐‘กโ„Ž๐‘–๐‘  ๐‘™๐‘œ๐‘›๐‘”-๐‘ก๐‘’๐‘Ÿ๐‘š ๐‘ฃ๐‘–๐‘’๐‘ค? โ€ฆ๐‘กโ„Ž๐‘’ ๐‘Ÿ๐‘’๐‘Ž๐‘™๐‘–๐‘ก๐‘ฆ ๐‘–๐‘  ๐‘กโ„Ž๐‘Ž๐‘ก ๐‘กโ„Ž๐‘’ ๐ธ๐‘Ž๐‘Ÿ๐‘กโ„Žโ€™๐‘  ๐‘ก๐‘’๐‘š๐‘๐‘’๐‘Ÿ๐‘Ž๐‘ก๐‘ข๐‘Ÿ๐‘’ โ„Ž๐‘Ž๐‘  ๐‘›๐‘’๐‘ฃ๐‘’๐‘Ÿ ๐‘๐‘’๐‘’๐‘› ๐‘ ๐‘ก๐‘Ž๐‘ก๐‘–๐‘โ€ฆ ๐‘–๐‘กโ€™๐‘  ๐‘Ž๐‘™๐‘ค๐‘Ž๐‘ฆ๐‘  ๐‘๐‘’๐‘’๐‘› ๐‘ข๐‘ ๐‘Ž๐‘›๐‘‘ ๐‘‘๐‘œ๐‘ค๐‘›โ€ฆ ๐ธ๐‘ ๐‘ ๐‘’๐‘›๐‘ก๐‘–๐‘Ž๐‘™๐‘™๐‘ฆ, ๐‘กโ„Ž๐‘’๐‘ฆ ๐‘“๐‘œ๐‘ข๐‘›๐‘‘ ๐‘กโ„Ž๐‘Ž๐‘ก ๐‘ค๐‘’โ€™๐‘Ÿ๐‘’ ๐‘–๐‘› ๐‘Ž ๐‘๐‘œ๐‘œ๐‘™๐‘–๐‘›๐‘” ๐‘๐‘’๐‘Ÿ๐‘–๐‘œ๐‘‘โ€ฆ (Rogan is speaking about the last 485 million years, not on recent trends since, say, 1850).โ€ ๐’๐€๐๐ƒ๐„๐‘๐’: โ€œ๐‘Š๐‘’๐‘™๐‘™, ๐ผโ€™๐‘š ๐‘›๐‘œ๐‘ก ๐‘ ๐‘ข๐‘Ÿ๐‘’. ๐ผ ๐‘‘๐‘–๐‘‘๐‘›โ€™๐‘ก ๐‘Ÿ๐‘’๐‘Ž๐‘‘ ๐‘กโ„Ž๐‘Ž๐‘ก ๐‘Ž๐‘Ÿ๐‘ก๐‘–๐‘๐‘™๐‘’. ๐ต๐‘ข๐‘ก, ๐‘ฆ๐‘œ๐‘ข ๐‘˜๐‘›๐‘œ๐‘ค, ๐‘กโ„Ž๐‘’ ๐‘ ๐‘๐‘–๐‘’๐‘›๐‘ก๐‘–๐‘ ๐‘ก๐‘  ๐‘คโ„Ž๐‘œ ๐‘Ž๐‘Ÿ๐‘’ ๐‘œ๐‘ข๐‘ก ๐‘กโ„Ž๐‘’๐‘Ÿ๐‘’โ€”๐ผ ๐‘กโ„Ž๐‘–๐‘›๐‘˜ ๐ผ ๐‘˜๐‘›๐‘œ๐‘ค.โ€ ๐‘๐Ž๐†๐€๐: โ€œ๐ต๐‘ข๐‘ก, ๐‘กโ„Ž๐‘’๐‘Ÿ๐‘’โ€™๐‘  ๐‘Ž ๐‘™๐‘œ๐‘ก ๐‘œ๐‘“ ๐‘š๐‘œ๐‘›๐‘’๐‘ฆ ๐‘–๐‘›๐‘ฃ๐‘œ๐‘™๐‘ฃ๐‘’๐‘‘ ๐‘–๐‘› ๐‘กโ„Ž๐‘Ž๐‘ก ๐‘ก๐‘œ๐‘œ, ๐ต๐‘’๐‘Ÿ๐‘›๐‘–๐‘’. ๐‘‡โ„Ž๐‘Ž๐‘กโ€™๐‘  ๐‘๐‘Ž๐‘Ÿ๐‘ก ๐‘œ๐‘“ ๐‘กโ„Ž๐‘’ ๐‘๐‘Ÿ๐‘œ๐‘๐‘™๐‘’๐‘š. ๐‘‡โ„Ž๐‘’๐‘Ÿ๐‘’โ€™๐‘  ๐‘Ž ๐‘™๐‘œ๐‘ก ๐‘œ๐‘“ ๐‘š๐‘œ๐‘›๐‘’๐‘ฆ ๐‘–๐‘›๐‘ฃ๐‘œ๐‘™๐‘ฃ๐‘’๐‘‘ ๐‘–๐‘› ๐‘กโ„Ž๐‘–๐‘  ๐‘คโ„Ž๐‘œ๐‘™๐‘’ ๐‘๐‘™๐‘–๐‘š๐‘Ž๐‘ก๐‘’ ๐‘โ„Ž๐‘Ž๐‘›๐‘”๐‘’ ๐‘’๐‘š๐‘’๐‘Ÿ๐‘”๐‘’๐‘›๐‘๐‘ฆ ๐‘–๐‘ ๐‘ ๐‘ข๐‘’. ๐ด๐‘›๐‘‘, ๐‘กโ„Ž๐‘’๐‘Ÿ๐‘’โ€™๐‘  ๐‘Ž ๐‘™๐‘œ๐‘ก ๐‘œ๐‘“ ๐‘๐‘œ๐‘›๐‘ก๐‘Ÿ๐‘œ๐‘™... ๐‘๐‘œ๐‘ก ๐‘œ๐‘›๐‘™๐‘ฆ ๐‘กโ„Ž๐‘Ž๐‘ก, ๐‘–๐‘“ ๐‘ค๐‘’โ€™๐‘Ÿ๐‘’ ๐‘—๐‘ข๐‘ ๐‘ก ๐‘ก๐‘Ž๐‘™๐‘˜๐‘–๐‘›๐‘” ๐‘Ž๐‘๐‘œ๐‘ข๐‘ก ๐‘๐‘Ÿ๐‘–๐‘š๐‘Ž๐‘Ÿ๐‘–๐‘™๐‘ฆ ๐‘๐‘Ž๐‘Ÿ๐‘๐‘œ๐‘› ๐‘Ž๐‘›๐‘‘ ๐‘๐‘Ž๐‘Ÿ๐‘๐‘œ๐‘› ๐‘“๐‘œ๐‘œ๐‘ก๐‘๐‘Ÿ๐‘–๐‘›๐‘ก, ๐‘คโ„Ž๐‘Ž๐‘ก ๐‘Ž๐‘Ÿ๐‘’ ๐‘ค๐‘’ ๐‘”๐‘œ๐‘–๐‘›๐‘” ๐‘ก๐‘œ ๐‘‘๐‘œ ๐‘Ž๐‘๐‘œ๐‘ข๐‘ก ๐ถโ„Ž๐‘–๐‘›๐‘Ž?โ€ ๐’๐€๐๐ƒ๐„๐‘๐’: โ€œ๐‘‡โ„Ž๐‘’๐‘ฆ ๐‘Ž๐‘Ÿ๐‘’ ๐‘กโ„Ž๐‘’ ๐‘š๐‘Ž๐‘—๐‘œ๐‘Ÿ ๐‘๐‘œ๐‘™๐‘™๐‘ข๐‘ก๐‘’๐‘Ÿ ๐‘Ÿ๐‘–๐‘”โ„Ž๐‘ก ๐‘›๐‘œ๐‘ค ๐‘–๐‘› ๐‘ก๐‘’๐‘Ÿ๐‘š๐‘  ๐‘œ๐‘“ ๐‘๐‘Ž๐‘Ÿ๐‘๐‘œ๐‘›. ๐‘Š๐‘’โ€™๐‘Ÿ๐‘’ ๐‘›๐‘ข๐‘š๐‘๐‘’๐‘Ÿ ๐‘ก๐‘ค๐‘œ; ๐‘ค๐‘’ ๐‘ข๐‘ ๐‘’๐‘‘ ๐‘ก๐‘œ ๐‘๐‘’ ๐‘œ๐‘›๐‘’, ๐‘กโ„Ž๐‘’๐‘ฆ ๐‘Ž๐‘Ÿ๐‘’ ๐‘›๐‘ข๐‘š๐‘๐‘’๐‘Ÿ ๐‘œ๐‘›๐‘’ ๐‘Ÿ๐‘–๐‘”โ„Ž๐‘ก ๐‘›๐‘œ๐‘คโ€ฆ ๐ฟ๐‘œ๐‘œ๐‘˜, ๐‘–๐‘กโ€™๐‘  ๐‘›๐‘œ๐‘ก ๐‘Ž๐‘› ๐ด๐‘š๐‘’๐‘Ÿ๐‘–๐‘๐‘Ž๐‘› ๐‘–๐‘ ๐‘ ๐‘ข๐‘’, ๐‘–๐‘ก ๐‘–๐‘  ๐‘Ž ๐‘”๐‘™๐‘œ๐‘๐‘Ž๐‘™ ๐‘–๐‘ ๐‘ ๐‘ข๐‘’ ๐‘Ž๐‘›๐‘‘ ๐‘Ž๐‘™๐‘™ ๐‘กโ„Ž๐‘Ž๐‘ก ๐ผ ๐‘๐‘Ž๐‘› ๐‘ก๐‘’๐‘™๐‘™ ๐‘ฆ๐‘œ๐‘ข ๐‘–๐‘  ๐‘กโ„Ž๐‘Ž๐‘ก ๐‘ค๐‘’ ๐‘Ž๐‘Ÿ๐‘’, ๐‘–๐‘› ๐‘š๐‘ฆ ๐‘ฃ๐‘–๐‘’๐‘ค, ๐‘”๐‘œ๐‘–๐‘›๐‘” ๐‘ก๐‘œ ๐‘ ๐‘’๐‘’ ๐‘š๐‘œ๐‘Ÿ๐‘’ ๐‘’๐‘ฅ๐‘ก๐‘Ÿ๐‘’๐‘š๐‘’ ๐‘ค๐‘’๐‘Ž๐‘กโ„Ž๐‘’๐‘Ÿ ๐‘‘๐‘–๐‘ ๐‘ก๐‘ข๐‘Ÿ๐‘๐‘Ž๐‘›๐‘๐‘’๐‘  ๐‘–๐‘› ๐‘กโ„Ž๐‘’ ๐‘๐‘œ๐‘š๐‘–๐‘›๐‘” ๐‘ฆ๐‘’๐‘Ž๐‘Ÿ๐‘ โ€ฆโ€ ๐‘๐Ž๐†๐€๐: โ€œ[๐‘‡]โ„Ž๐‘’ ๐‘๐‘Ÿ๐‘œ๐‘๐‘™๐‘’๐‘š ๐‘–๐‘  ๐‘”๐‘–๐‘ฃ๐‘–๐‘›๐‘” ๐‘๐‘’๐‘œ๐‘๐‘™๐‘’ ๐‘–๐‘› ๐‘๐‘œ๐‘ค๐‘’๐‘Ÿโ€ฆ ๐‘š๐‘œ๐‘Ÿ๐‘’ ๐‘๐‘œ๐‘›๐‘ก๐‘Ÿ๐‘œ๐‘™ ๐‘œ๐‘ฃ๐‘’๐‘Ÿ ๐‘๐‘–๐‘ก๐‘–๐‘ง๐‘’๐‘›๐‘ . ๐‘‡โ„Ž๐‘–๐‘  ๐‘–๐‘  ๐‘Ž ๐‘ฃ๐‘’โ„Ž๐‘–๐‘๐‘™๐‘’ ๐‘“๐‘œ๐‘Ÿ ๐‘กโ„Ž๐‘Ž๐‘ก... โ€˜๐ถ๐‘Ž๐‘ข๐‘ ๐‘’ ๐‘–๐‘ก ๐‘Ž๐‘™๐‘™๐‘œ๐‘ค๐‘  ๐‘กโ„Ž๐‘’๐‘ ๐‘’ ๐‘“๐‘ข๐‘๐‘˜๐‘–๐‘›๐‘” ๐‘๐‘Ÿ๐‘’๐‘’๐‘๐‘ โ€”๐‘กโ„Ž๐‘Ž๐‘ก โ„Ž๐‘Ž๐‘ฃ๐‘’ ๐‘๐‘’๐‘’๐‘› ๐‘๐‘œ๐‘›๐‘ก๐‘Ÿ๐‘œ๐‘™๐‘™๐‘–๐‘›๐‘” ๐‘๐‘’๐‘œ๐‘๐‘™๐‘’ ๐‘Ž๐‘›๐‘‘ ๐‘๐‘œ๐‘›๐‘ก๐‘Ÿ๐‘œ๐‘™๐‘™๐‘–๐‘›๐‘” ๐‘คโ„Ž๐‘Ž๐‘ก ๐‘ฆ๐‘œ๐‘ข ๐‘‘๐‘œ ๐‘Ž๐‘›๐‘‘ ๐‘คโ„Ž๐‘Ž๐‘ก ๐‘ฆ๐‘œ๐‘ข ๐‘ ๐‘Ž๐‘ฆ ๐‘Ž๐‘›๐‘‘ โ„Ž๐‘œ๐‘ค ๐‘ฆ๐‘œ๐‘ข ๐‘ ๐‘๐‘’๐‘›๐‘‘ ๐‘ฆ๐‘œ๐‘ข๐‘Ÿ ๐‘š๐‘œ๐‘›๐‘’๐‘ฆโ€”๐‘ก๐‘œ ๐‘™๐‘œ๐‘œ๐‘˜ ๐‘Ž๐‘ก [your] ๐‘๐‘Ž๐‘Ÿ๐‘๐‘œ๐‘› ๐‘“๐‘œ๐‘œ๐‘ก๐‘๐‘Ÿ๐‘–๐‘›๐‘ก, ๐‘ฆ๐‘œ๐‘ข ๐‘๐‘Ž๐‘› ๐‘™๐‘œ๐‘œ๐‘˜ ๐‘Ž๐‘ก ๐‘กโ„Ž๐‘’ ๐‘Ž๐‘š๐‘œ๐‘ข๐‘›๐‘ก [you] ๐‘ก๐‘Ÿ๐‘Ž๐‘ฃ๐‘’๐‘™, ๐‘๐‘ข๐‘ก ๐‘Ž ๐‘๐‘Ž๐‘Ÿ๐‘๐‘œ๐‘› ๐‘ก๐‘Ž๐‘ฅ ๐‘œ๐‘› ๐‘กโ„Ž๐‘’๐‘ ๐‘’ ๐‘๐‘’๐‘œ๐‘๐‘™๐‘’โ€ฆ ๐‘‡โ„Ž๐‘Ž๐‘กโ€™๐‘  ๐‘คโ„Ž๐‘Ž๐‘ก ๐‘๐‘œ๐‘กโ„Ž๐‘’๐‘Ÿ๐‘  ๐‘š๐‘’ ๐‘Ž๐‘๐‘œ๐‘ข๐‘ก ๐‘กโ„Ž๐‘–๐‘  ๐‘๐‘™๐‘–๐‘š๐‘Ž๐‘ก๐‘’ ๐‘โ„Ž๐‘Ž๐‘›๐‘”๐‘’ ๐‘’๐‘š๐‘’๐‘Ÿ๐‘”๐‘’๐‘›๐‘๐‘ฆโ€ฆโ€ This was a thoughtful conversation and I [mostly] agree with Rogan on this issue. I listened to the full interview, and I have to say, whether you like or agree with Bernie or not (and I donโ€™t on a lot), he is smart and is one of the more intelligent figures on the political left. Link to full interview below ๐ŸŽ™๏ธ๐Ÿ‘‡ ๐Ÿ”—

Chris Martz

13,839 ๆฌก่ง‚็œ‹ โ€ข 1 ๅนดๅ‰

Q: Engine changes that you can make with ADUO, is the title still possible for you & the team? "It's unlikely from from an update perspective it's not like now we can just bring an update next week it takes months and months and months to develop and change components on the engine to prove it to make sure it still holds reliability and it's it's a long long development process so whether or not the engine will catch up this year it's highly unlikely I would say that the engine is going to catch up this year with the time we have left it's more the opportunity close the gap for next year, power wise." Q: But do you think... "But in terms of the title I'm still... I think if we we can still outdo people in terms of how we develop the car a car is very good the the downforce package that we have is really good we're gonna have to double up make sure that we're always one step ahead of everyone in terms of advancing that so we can go through the corners quicker and catch up the deficit we may lose down the straights improve efficiency so we maybe can improve a bit on drag for example to try and close that gap in speed but you know and there's lots of different things happening in all these different tracks so you know never say never and I just keep pushing give it absolutely everything." F1 2026 || Barcelona

sim ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ฒ๐Ÿ‡ฝ๐Ÿ‡ธ๐Ÿ‡ณ๐Ÿ‡ซ๐Ÿ‡ท๐Ÿ‡ญ๐Ÿ‡น

87,280 ๆฌก่ง‚็œ‹ โ€ข 1 ไธชๆœˆๅ‰

๐Ÿšจ THIS IS NOT NORMAL Look at the chart. Gold dumping. Silver dumping. Both rolling over at the exact same moment - **2026**, the year a 150-year-old cycle map marked as *"high prices, time to sell."* Everyone's screaming "collapse." They're wrong. This isn't the system dying it's capital *moving,* right on schedule. Here's what most people miss: in a liquidity crunch, the *safe* stuff sells first. Not because it failed because it's what funds *can* sell to cover margin calls. Gold and silver get used as ATMs. Dumped at any price. We've seen this movie: โ†’ 2008 - silver cut nearly in half mid-crisisโ€ฆ then gold ran to records. โ†’ 2020 - everything red in one week, metals includedโ€ฆ then they exploded to new highs. The pattern never changes: **first liquidation, then rotation.** Capital doesn't vanish - it moves to wherever the rules change next. And the same chart points the arrow down to **2032โ€“2039**: the cycle's "time to *buy*" window. So ask the real question - when trust in banks fades and currencies get diluted to save the system, where does the money go? Not into paper. Not into anything that can be frozen, seized, or printed. Gold *used* to be the only exit. But gold is heavy, centralized, sitting in vaults run by the same institutions now under stress. **Bitcoin isn't.** No issuer. No counterparty. No permission. That's why it gets sold hardest in the panic - and bought hardest once liquidity stabilizes. The crash of old finance isn't bearish for the exit asset. It's the entire reason it exists. The rotation won't be gradual. It never is. One moment it's "just another risk asset." The next, it's the only neutral one left standing - and by then the move is already done. Don't follow narratives. Follow liquidity. I've called every major top and bottom for 10+ years. When I make my next move, it goes here first. Follow and turn notifications on. A lot of people are going to wish they'd listened sooner.

Shelpid.WI3M

136,413 ๆฌก่ง‚็œ‹ โ€ข 1 ไธชๆœˆๅ‰

'Pistol Pete' Maravich sharing his testimony of faith in Jesus Christ in 1987 less than one year before his death at the age of 40: "I want all of you to know this tonight about Peter Maravich. You may never have heard of me. It makes no difference. I'm just one person on this earth saved by the grace of God through faith in Jesus Christ. I want you to know this, that the change that came into my life was Jesus Christ. It was not winning. I won all my life. I won every trophy, award, everything you can think of, but every time I won something, I wanted something more. I had to win again. It wasn't money, because money'll buy you everything but happiness. It'll pay your fare at every place but Heaven. Material thingsโ€”I've driven everything some of you strive for from Rolls Royces to BMWs to Mercedes to Porsches. It wasn't religion because in the name of religion, Jesus Christ was placed upon that cross. And the purest thing about Christianity is the fact that it's your choice. You can't work. You can't earn. I knew that, and I understood it now. I want you to know this. The last thing I'd like to say is this, next week I'll be inducted into the Hall of Fame. I'll get that big ring. In fact, it's a bigger ring than I would have got for the championship, but I'll tell you something about all the awards. They all pale to the glory of Christ and what He's done in my life. It's amazing what He has done in my life. I wouldn't trade my position in Christ for a thousand NBA championships or a thousand Hall of Fame rings or for a hundred billion dollars. There's nothing like the joy of Jesus Christ in your life."

Melissa the Hopeful๐Ÿ Homemaker

607,851 ๆฌก่ง‚็œ‹ โ€ข 4 ไธชๆœˆๅ‰

FULL TRANSCRIPT OF ELON'S CYBERCAB AND ROBOVAN PRESENTATION 00:00 Welcome 01:16 Cybercab & Future of transportation 04:33 Cost 05:53 Timeline 07:13 Self-driving technology 10:05 Inductive charging 10:24 The cities of the future 11:04 Robovan 12:13 Optimus Welcome Welcome to the We, Robot party. We have quite a show for you tonight. I think you're going to like it. As you can see, I just arrived in the Robotaxi, the Cybercab. And there's 20 more where that came from. So they've been traveling, there's no people in them. As you can see, the car is just going by with no people. We have 50 fully autonomous cars here tonight. So you'll see model Y's and the Cybercabs, all driverless. You'll be able to take a ride in the Cybercab. There's no steering wheel or pedals. So I hope this goes well, we'll find out. You see a lot of sci-fi movies where the future is dark and dismal, where it's not a future you want to be in. So, you know, I love Blade Runner, but I don't know if we want that future. We want that duster he's wearing, but not the bleak apocalypse. We want to have a fun, exciting future that, if you could look in a crystal ball and see the future, you'd be like, yes, I wish I could be there now. That's what we want. Cybercab & Future of transportation So, when we think about transport today, there's a lot of pain that we take for granted, that we think is normal. Like having to drive around LA in 3 hours of traffic. Yeah, people that live in LA, I mean, you know, try to get from Pasadena to El Segundo during rush hour. You can fly to another city faster than you can get to LA. And you have to drive the whole way, unless you're in a Tesla. Of course, our Tesla already does quite well at this supervised self-driving. So, supervised full self-driving is actually working quite well. I'm sure there's people in the crowd who are using that. So, we'll move from supervised full self-driving to unsupervised full self-driving where the car, you could fall asleep and wake up at your destination. But there's also a challenge for a lot of people that cars cost too much. I mean, when you factor in everything that goes into a car and the car insurance and the car payments, storage of the car, it's very expensive. You say, like, how many hours a week are cars used? Your average passenger car is only used about 10 hours a week out of 168 hours. So, the vast majority of the time cars are just doing nothing. But if they're autonomous, they could be used, I don't know, five times more, maybe ten times more. So you could actually, for the same car, would have five times as much value, maybe ten times as much value. There's 168 hours in the week, and like I said, only ten of them are used for driving. And then, a bunch of those hours are looking for a parking spot, which can be pretty annoying at times. So, with autonomy, you get your time back. This is a very big deal. So it's not just, it'll save lives, like a lot of lives and prevent injuries. I think we'll see autonomous cars become ten times safer than a human. I mean, if you think of times past where there used to be an elevator operator in every elevator but once in a while, they get tired and accidentally shear somebody in half. Now, we have automated elevators. You just get an elevator and you press a button and you don't even think about it and it just takes you to the floor. And if you did see an elevator operator with a big relay switch, you'd be like, that's weird. That's how cars will be. And it's not just the lives saved in injuries, but if you think about the cumulative time that people spend in a car and the time that they will get back that they can now spend, well, I guess, on their phones or watching a movie or doing work or whatever you want to do you can think of the car in autonomous world as being like just little lounge. You're just sitting in a comfortable little lounge and you can do whatever you want while you're in this comfortable little lounge. And when you get out, you will be at your destination. So, yeah, it's gonna be awesome. Cost So, in fact, I think the cost of autonomous transport will be so low that you can think of it like individualized mass transit. The average cost of a bus per mile for a city, not the ticket price, because that is subsidized, but the average price is about a dollar a mile, whereas the cost of Cybercab we think probably over time, the operating cost is probably going to be around twenty cents a mile. Including taxes and everything else, it probably ends up being 30 or 40 cents a mile. And you will be able to buy one. And we expect the cost to be below $30,000. And I think there'll be an interesting business model where, let's say somebody is an Uber or Lyft driver today where they can actually sort of manage a fleet of cars and like, sort of manage, I don't know, 10, 20 cars and just take care of them. Like a shepherd tends their flock. You have a little flock of cars and you're the shepherd and you take care of your flock of cars. I think that would be pretty cool. I think it's going to be a glorious future. It's going to be really something special. Timeline We do expect actually to start fully autonomous unsupervised FSD in Texas and California next year. And that's obviously, that's with the Model 3 and Model Y. And then we expect to be in production with the Cybercab, which is really highly optimized for autonomous transport in probably, I tend to be a little optimistic with time frames, but in 2026. So, yeah, before 2027, let me put it that way. And we'll make this vehicle in very high volume. But well, before that, you will experience a robotic taxi via the Model 3 and Model Y program and model S and X, too. But the Model 3 and Y will achieve unsupervised full self-driving with permission, in wherever regulators essentially approve it. In the US, and then to follow outside the US. And Cybertruck, too. All our cars are basically, all cars that we make. Let's not get nuanced here. Self-driving technology One of the reasons why the computer can be so much better than a person is that we have millions of cars that are training on driving. It's like living millions of lives simultaneously and seeing very unusual situations that a person in their entire lifetime would not see. With that amount of training data, it's obviously going to be much better than what a human could be because you can't live a million lives. And it's also, it can see in all directions simultaneously and it doesn't get tired or text or any of those things. So, it will naturally be, like I said 10, 20, 30 times safer than a human, just for all those reasons. And I want to emphasize that the solution that we have is, AI and vision. So, there's no expensive equipment needed. The Model 3 and Model Y and S and X that we make today will be capable of full autonomy, unsupervised. And that means that our cost of producing the vehicle is low. Now, we are going to actually over-spec the computer for the Cybercab. So, our AI 5 computer will be somewhat over-spec'd because I think there's actually also an opportunity, sort of like an Amazon Web Services, where if the car is driving for 50 hours a week, there's still over 100 hours left and there's a potential there to have a massive amount of distributed inference compute, where if you've got like a fleet of 100 million vehicles and a kilowatt of efficient inference compute, you have 100 gigawatts of compute, which is really quite substantial. And if it's there, you might as well use it so that I think will make sense. So, our autonomous future is here. As I said, we've got 50 Teslas driving autonomously. We're trying to give you a sense of what cities will be like in the future. And when you get in, you'll see like, it's really quite a wild experience to just be in a car with no steering wheel, no pedals, no controls, and it feels great. So we have enough vehicles here, so everyone should be able to try it out and experience the set that we've built here. It's a very big set. So it's like really we've used I don't know, 20, 30 acres or something like that. It's really big. So, it goes on, the ride's long. And we set it up to feel like a ride, like a park ride. So, it'll be cool and you'll get to experience it tonight. Inductive charging Something we're also doing is and it's really high time we did this is inductive charging. So, the robotaxi has no plug. It just goes over the inductive charger and charges. So, yeah, it's kind of how it should be. The cities of the future One of the things that is really interesting is how will this affect the cities that we live in. And when you drive around a city, or when the car drives you around the city, you'll see there's a lot of parking lots. There's parking lots everywhere, parking garages. What would happen if you have an autonomous world is that you can now turn parking lots into parks. And so, from we're taking the inglot out of parking lot. You're welcome. So, there's a lot of opportunity to create green space in the cities that we live in. So, like, that would be quite fantastic. Robovan Oh, and also, what happens if you need a vehicle that is bigger than a Model Y? The Robovan. We're going to make this and it's going to look like that. Now, can you imagine going down the streets and you see this coming towards you? That'd be sick. So this can carry up to 20 people, and it can also transport goods. You can configure it for goods transport within a city. Or transport of up to 20 people at a time. The Robovan is what's gonna solve for high density. If you want to take a sports team somewhere or you're looking to really get the cost of travel down to, I don't know, 5, 10 cents a mile, then you can use the Robovan. One of the things we want to do, and we've seen this with the Cybertruck, is we want to change the look of the roads. The future should look like the future. Optimus Speaking of robots. Everything we've developed for our cars, the batteries, power electronics, the advanced motors, gearboxes, the software, the AI inference computer, it all actually applies to a humanoid robot. The same techniques. It's just a robot with arms and legs instead of a robot with wheels. We've made a lot of progress with Optimus. And as you can see, we started up with someone in a robot suit. And then, we've progressed dramatically, year after year. So, if you extrapolate this, you're really going to have something spectacular, something that anyone could own. So, you can have your own personal R2-D2-C3PO. And I think at scale, this would cost something like, I don't know, $20,000, $30,000, probably less than a car is my prediction, long-term. It'll take us a minute to get to the long term. But fundamentally, at scale, the Optimus robot, you should be able to buy an Optimus robot for, I think, probably $20,000 to $30,000, long-term. And what can it do? It'll basically do anything you want. It can be a teacher or babysit your kids, it can walk your dog, mow your lawn, get the groceries, just be your friend, serve drinks whatever you can think of, it will do. And, yeah, it's going to be awesome. I think this will be the biggest product ever of any kind, because I think everyone of the 8 billion people of Earth, I think everyone's going to want their Optimus buddy. And there's going to be maybe two. And then, they'll be producing products and services. I predict, actually, provided we address risks of digital superintelligence, 80% probability of good outcome, look on the bright side, the cup is 80% full, the cost of products and services will decline dramatically. And basically, anyone will be able to have any products and services they want. It will be an age of abundance the likes of which people have not, almost no one has envisioned. It will be something special. So now, one of the things we wanted to show tonight was that Optimus is not a canned video. It's not walled off. The Optimus robots will walk among you. Please, please be nice to the Optimus robots. You'll be able to walk right up to them and they'll serve drinks at the bar. I mean, it's a wild experience just to have humanoid robots and they're there, you're just in front of you. So yeah, with that, let's party!

Mario Nawfal

241,051 ๆฌก่ง‚็œ‹ โ€ข 1 ๅนดๅ‰

โ€ผ๏ธ๐Ÿšจ๐Ÿ”ตPRESSER๐Ÿ”ต๐Ÿšจโ€ผ๏ธ โ€‹๐ŸŽ™Enzo Maresca's Full Pre-Nottingham Forest Press Conference: ๐Ÿ”นEnzo Maresca on Cole Palmer: "I was wrong. Unfortunately, he needs to be out for six more weeks. Yes, absolutely [no surgery]. We just try to protect Cole as much as we can." ๐Ÿ”นEnzo Maresca more on Cole Palmer: "The medical are not magicians. We hope six weeks are enough. It's a problem we need to see step by step, week after week. But for sure, he will be okay. He looks very good, relaxed. He is trying to recover. He is doing all that he needs to do." ๐Ÿ”นEnzo Maresca: "Unfortunately, Benoit will be out until December - injury again, a muscular problem." ๐Ÿ”นEnzo Maresca: "Moi, Enzo and Pedro didn't take part of the session yesterday. We will see if they train today. Reece is fully fit." ๐Ÿ”นEnzo Maresca: "It was a big moment for many reasons. Since I joined the club, we never won a game at home in the last minute. We were playing the Champions of England, so it was an important moment." ๐Ÿ”นEnzo Maresca: "We lost two players in the moment that for us have been the main players in the build up. Levi, for us, was the main one from behind, and Cole in the middle of the pitch. We are trying to find solutions." ๐Ÿ”นEnzo Maresca: "We lost two players in the moment that for us have been the main players in the build up. Levi, for us, was the main one from behind, and Cole in the middle of the pitch. We are trying to find solutions." ๐Ÿ”นEnzo Maresca on Forest conceding goals after 70 minutes: "When we analyse a team, we consider everything. You have to go match by match. It's always different. For sure, in the international break we watched all the games with Ange in charge. Making changes is something you usually plan but it is sometimes dependant on the game." ๐Ÿ”นEnzo Maresca on Set-pieces this season: "Since I joined the club, Bernardo is the one in charge of set-pieces. We didn't change nothing, we are working the same way. We spend time on set-pieces. You can score, you can concede; it depends a little bit. We are doing quite well [on that front]." ๐Ÿ”นEnzo Maresca on Replacing Palmer: "First of all, to replace Cole, it's difficult. Cole is a very important player for us, one of the best in the league. The ones we have, in Cole's position against Liverpool was Malo Gusto. The game vs Benfica was Facundo. It depends on the game plan we have. We don't have another player like Cole. Cole is unique." ๐Ÿ”นEnzo Maresca on International break: "It's a good period. Tosin is back. Fofana is back. Andrey Santos is back. Enzo is out, Moi is out, Pedro is out. We are going to try and find the best solution for the next games.โ€ ๐Ÿ“ฒ CFC_ChelseaFC via Telegram

Miki Djan

17,503 ๆฌก่ง‚็œ‹ โ€ข 9 ไธชๆœˆๅ‰

ART BERMAN'S BASE CASE: OIL SPIKES TO $160 THEN STABILIZES PERMANENTLY AT $110 Petroleum geologist Art Berman built a probability model for the current oil crisis that rejects political theater and quick deals. He treats every forecast as a distribution of outcomes because the situation has no historical precedent. His base case carries the highest weight and it points to a permanent break from the energy world of 2025. ART BERMAN'S PROBABILITY MODEL โžก๏ธ He maps best case, base case, and worst case scenarios instead of offering single predictions because no one can know the exact path through unprecedented disruption. โžก๏ธ The best case assumes a perfect deal by early June yet still delivers only 50 percent of normal flows by the end of 2026 due to demining, insurance delays, and weeks of tanker queuing. โžก๏ธ Even that optimistic path leaves three quarters of 2026 operating under severely reduced energy supplies with catastrophic economic consequences. THE BASE CASE THAT DRIVES EVERYTHING โžก๏ธ Iran has no incentive to ever fully reopen the Strait of Hormuz and will likely maintain control indefinitely. โžก๏ธ Restarting shut-in production faces massive lags from damaged reservoirs, lost investment confidence, and infrastructure that may never fully recover. โžก๏ธ The global system faces irreversible change with no realistic path back to 2025 economic conditions. THE OIL PRICE PROJECTION โžก๏ธ In the realistic base case oil prices will almost certainly spike into the 150 to 160 dollar per barrel range by summer. โžก๏ธ Extreme prices trigger demand destruction that pulls Brent back down to around 100 to 105 dollars. โžก๏ธ Prices then slowly rise and stabilize in the 105 to 115 dollar per barrel range through 2027 and likely beyond. WHY THIS SHOCK IS 60 TO 99 TIMES FASTER โžก๏ธ The rate of supply loss is 60 to 99 times faster than the greatest previous oil shocks in recorded history. โžก๏ธ No rapid solutions like vaccines or policy reversals exist this time to cushion the blow. โžก๏ธ Inventories have masked the crisis so far but those savings are running out fast and the full impact is coming. THE BOTTOM LINE Art Berman's model shows the world just suffered its greatest energy blunder in modern history by jeopardizing the entire global economy with one move. Oil will spike hard then settle into a permanently higher range because the old supply system is broken beyond repair. #OilPrices #ArtBerman #EnergyCrisis #OilShock #HormuzBlockade #DemandDestruction #NewOilNormal HT: YouTube Palisades Gold Radio Art Berman

Mark

48,969 ๆฌก่ง‚็œ‹ โ€ข 2 ไธชๆœˆๅ‰

After working with Nick shirley in San Francisco, LA and Sacramento, my account is really starting to get a lot of new followers... I am humbled and very grateful for all the love and support ๐Ÿ‡บ๐Ÿ‡ธ Allow me to reintroduce myself to y'all ๐ŸŒŽ๐ŸŒ๐ŸŒ Hello, my name is Darren Stallcup and long story short my house burned down to the ground when I was a kid and I started hitchhiking North, East, South and West across the country. Ended up in an Eskimo Village on the arctic ocean. Now I'm back home fighting the good fight in San Francisco. The Far Left Lion's Den. Imagine, if you would be so kind, the pressure of being a Republican in San Francisco... For the last four five six seven eight nine ten years, every single day has been a brutal tooth and nail uphill battle for every inch just to survive in what was once (and still can be) one of the most beautiful cities in the world. San Francisco, The Paris Of The West. Iโ€™ve walked these blocks day and night as a citizen journalist, shining a light on the chaos. Between 2019 and 2026, 5,000+ have **** from fentanyl in just San Francisco alone. Numbers released by health officials are not accurate. Coroner's office sure as hell can't keep up with all the bodies much less identify them. For many moons I went to sleep to the sounds of people screaming on the streets below and EVERY morning without would awake to emergency sirens. Iโ€™ve volunteered at churches and shelters, raised awareness about the dangers of fentanyl, defended families and tourists from violent drugged out lunatics, stopped more than one restaurant robberies, guarded our last few remaining grocery stores from hordes of thieves for over 200+ nights, I have spent countless days helping the less fortunate struggling on our streets, handing out food, clothing, blankets, ponchos, winter jackets and other personal hygine kits.... because talk is cheap but real action in the frontline trenches actually saves lives. Yeah, Iโ€™ve been in the field and I am a real frontline trenches leader. Iโ€™ve stood up and spoken truth at City Hall, on national stages and even international television, refusing to back down no matter how loud the opposition gets. When China President Xi came to San Francisco, I was passed the ball and I made sure America knew the truth: Our city only gets cleaned up for communists and the super bowl. This fight isnโ€™t pretty or cool. Many people consider my work to be cringe or gross. I guess it's not a trend to care about your fellow human beings slowly rotting away on the sidewalk... And it takes a toll on my body. I do have PTSD. I do have survivors guilt. I have lost family and friends on the streets of San Francisco. I do sometimes suffer from anxiety and depression. I can't sleep at night. Any small noise and I immeadiatly jump. That's how many times I have woken up to my door getting kicked in and fighting off burglars. Healing doesn't happen over night and it will take generations for our city to recover from the damage done by these corrupt and incompetent far left leaders who have enabled chaos for fiannical gain. These organizations, non-profits and NGOs who support these leftist politicans also just so happen to be benefiting from the suffering of the less fortunate on the streets. That's not an accident. We are on the 20th year anniversary of Gavin Newsom's 10 year plan to solve homelessness in California... Billions of dollars later and the situation is worse than ever before. Not the first billions of dollars wasted by these leftists... Look at that high speed train between LA and SF. What a pipe dream that was... Maybe someday when I am 99 years old and can barely walk California will finally get that train... Of course, here in upside down world California, every day feels like an episode from the twilight zone. The good guys have become the bad guys and the bad guys have become the good guys. I have been attacked, harassed, doxxed, followed home, gangstalked and everything else underneath the sun. These leftists are violent and have no respect for our country and anybody that dare love America, they go after them. It's been It's exhausting and someday they might take me out but until that day comes I refuse to surrender San Francisco to the far left. If you are sick and tired of the same old damn broken system here in California, know that there are warriors like me still in the arena, fighting for real change with everything we got. We The People must stand tall together and take our cities back. My Message To America: Keep fighting the good fight and never give up hope. One small act truly does have the power to change the world. Be that change. #WorldPeace

Darren Stallcup - World Peace Movement

105,681 ๆฌก่ง‚็œ‹ โ€ข 3 ไธชๆœˆๅ‰

Almost Everything Youโ€™ve Noticed Change In America Can Be Traced Back To Barack Obama In 1992, A Real Communist Party USA Meeting Was Held In California At The University Of Berkeley. Many Of The Attendees Ended Up Working In The Barack Obama Administration A Full Communist Agenda and how they would achieve their goal would be to โ€œUse the environmental movement to take down the free enterprise system in America.โ€ This should be extremely eye opening for everyone. We are living through their agenda. โ€œBack in 1992, an older friend of my father who was from Saint Louis asked me to go to this meeting that the Communist Party USA was having at the University of California Berkeley. And he had studied communism and written books about communism back in the sixties and stuff. And he was curious Because if you remember back in 1989, the Berlin Wall had come down, and everyone was saying communism is dead. It's over. Then in 91 in December, the Soviet Union dissolved. โ€Œ And so this is 6 months later, the summer of 92, and the Communist Party USA is having a meeting. So he asked me to go out to this meeting. He said, would you go out there and just see what they're talking about? Because we we won. This thing's over. โ€Œ And so I went to that. And for 3 days, I sat there in breakout sessions and lectures and and listened to these hardcore communists. And and one thing shocking about it too, I thought it'd be college radical since it was at Berkeley, so I dressed like a college radical with some radical t shirt on it. I walk into the autumn the auditorium, there's 14 or 1,500, 50, 60, and 70 year olds with briefcases. And I thought, woah. โ€Œ This is actually serious. It's not just some radicals. And many of those exact people, as I researched them later, ended up being in Obama's cabinet in 2008. And that's what motivated me to make movie because I rise these are the people that were at this communist meeting with me back back in 1992. But at that meeting, they laid out this plan how they wanted to take America down from the inside. โ€Œ They were gonna focus all their energies on that now. They've been focusing on it for a while, but they realized they could never outspend America because capitalism, free enterprise is so successful. And they kind of that woke them up. Okay. We gotta go to plan b. โ€Œ They they just keep building more and more. And, of course, we had all the years of Reagan where he'd really built the military up, so they realized We're in trouble here. Um, and so that's what they talked about to me and how they were going to do that from the inside, and I didn't think that much about it, went on with my life. But then again, 16 years later in 2008 from 92, when I remembered what they had talked about, like, one thing, uh, that is so clear how it had changed. They had said back in 92, we're gonna use the environmental movement to take down the free enterprise system in America.โ€ โ€Œ I canโ€™t transcribe it all due to Xโ€™s text limits but this is a CRAZY listenโ€ฆ This is the systematic takedown of America from the inside under the disguise of Climate Change

Wall Street Apes

480,419 ๆฌก่ง‚็œ‹ โ€ข 2 ๅนดๅ‰

Listening to people complain about the Tesla Robotaxi rollout reminds me of that scene in Idiocracy where President Camacho promises everyone that Not Sure (Ashok) is going to fix all the country's problems, and do it all in one week. It turns out that the economy is collapsing because people have been watering the crops with Gatorade instead of water. They switch back to water, but by the time the week is over Not Sure is fighting for his life roman gladiator style in a giant colosseum. Then people realize that the crops actually *are* growing with the water, and his life is saved just in time. I remember a time when the Tesla community was a powerful force in pushing back against naysayers. When a chorus of haters and short sellers said "Model 3 production is too slow. They will never reach 5,000 a week. They will never reach profitability" it was the Tesla community that pushed back and said they believed in the company. And sure enough the company did eventually scale up Model 3 and Y, did eventually hit profitability, and did eventually hit their targets even if they missed them a few times first. The Tesla community saw that because they understood the company in a way the naysayers didn't. Now, many of those some people have become the naysayers. I can't blame them completely. A lot of the people who understood EVs and the auto industry very well are left scratching their head trying to understand AI, autonomy, and robotaxis. You've got a bunch of options traders who are not AI experts but bought options that are expiring now, hoping Robotaxi would have scaled further. Just like the people in Idiocracy they have good reason to be upset โ€” they're hungry, and the crops aren't growing. But just like the naysayers were wrong about Tesla being unable to scale the Model 3 & Y, today's naysayers couldn't be more wrong about Tesla being unable to scale Robotaxi. At this point they have hundreds of fully driverless cars registered in 6 cities. This is the first time this has ever been done with pure computer vision. How many announcements and signs of progress can you dismiss before you finally admit what is happening? This is not a linear thing. The first step in deploying Robotaxis is to put a few on the road and see how they work. And no, it's not just going to be perfect out of the box on the first day. There are going to be issues you couldn't forsee, unique problems in new areas, and improvements to be made. But once you can do 200 driverless cars safely, it doesn't take much more to scale to 1,000 and beyond. Just look at last week in Texas where we went from 100 to 175 cars registered in a 24 hour period. The number increased slowly, then all at once in one big jump. That is how exponential growth works. If you're looking at the initial growth and trying to extrapolate that out linearly, you're going to be way off. It feels like everyone is so focused on Elon not solving everything in one week like he promised that they're missing the fact that it is actually working. The crops actually are starting to grow. How are people not seeing the progress of FSD 14.3.6, FSD 14 lite, and all the new cities Robotaxi is entering? Remember when driving a car with pure vision, without LIDAR or Radar, was supposed to be impossible? That's the magic of Elon Musk. He takes what is supposed to be impossible โ€” a reusable spaceship, generalized self-driving cars at scale โ€” and makes what's supposed to be impossible feel like it's actually late. When he starts on a project, they say it can never be done. By the time he finishes, people are asking why they didn't finish it faster. Say what you will, but the Tesla team is absolutely executing right now. They are killing it. I can't be the only one that sees the signs. Everything I've seen tells me that they are going to scale this. As they add more training compute, as the data set grows larger, as the fleet crosses 10 million cars, as they ship FSD 15 and their AI5 and AI6 chips, the cars are just going to keep getting smarter and smarter. The capabilities of these autonomous vehicles are already starting to cross into the realm of superhuman, and they're not stopping there. If you want to point out every stumble, every missed deadline, every limitation in the current Robotaxi service, that's your prerogative. You have the right to say whatever you want. But I think that as we look back on this time, these people are going to look extremely dumb in hindsight. When autonomous vehicles blanket the globe, we'll ask how people didn't see it earlier as the service expanded into 7 markets. This company has nearly 10 million cars on the road. More than 12 billion FSD miles have been driven around the globe. And international expansion is just starting. This is the company that developed Cybercab to be as dead simple as possible. To not require any paint. They built a vehicle that can truly bring generalized autonomy to the masses around the world. I can't believe how many people are unable to see it. Based on everything I'm seeing, I've never had more conviction that this technology is going to change the world. AI is beginning to reach out of our computer and into the physical world, and Tesla has a central role to play in making that a reality.

Whole Mars Catalog

96,259 ๆฌก่ง‚็œ‹ โ€ข 19 ๅคฉๅ‰

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 ๆฌก่ง‚็œ‹ โ€ข 8 ไธชๆœˆๅ‰

The revisionist history about Baker Mayfield and the Browns is out of control. We're happy for Baker and the success he's found in Tampa Bay. But everyone claiming he'd be doing the same exact thing right now in Cleveland is just lying to themselves. One, you can't just copy and paste the stats a player has on one team and project them onto another team. Doesn't work that way. A lot of things had to transpire for Baker to be in the position he's in now. In 2021, everyone--national media, Cleveland media, fans, etc.--said Baker wasn't the guy to take the Browns to the next level. The receipts are everywhere (RGIII might be the funniest one). On the Pardon My Take Podcast just this past summer, Baker admitted that playing through his injury in 2021 was a mistake: "The last year in Cleveland, as banged up as I was...should I have gotten surgery and sat out? Yeah." So many people want to believe the Browns forced Baker out of town. Sorry, but that simply is not what happened. We remember because we covered this every week on the podcast that season. Baker would tell the media on Friday that his shoulder was fine and he was making every throw in practice. Then after he played poorly on Sunday, he'd tell the media his shoulder was really bothering him. It happened every week. Baker forced the Browns to play him injured, not the other way around. You can refute this all you want, but Baker admitted this himself. "I learned a lot of lessons about how damn stubborn I am. Watching the film from those games now...I was a stubborn asshole. I wasn't able to play to the best of my ability by any means." Everything happens for a reason. The success Baker is having with the Buccaneers wouldn't be happening if things hadn't gone the way they did in Cleveland. And then in Carolina. And then in Los Angeles. Remember, Baker was statistically the worst quarterback in the NFL in 2022. He had a 26.3 QBR (32nd), 60% CMP and 10 TDs to 8 INTs in 12 games. Baker needed to mature as a person and a quarterback. And that happened because he was rejected by 3 teams in one calendar year. It happened because his only opportunity was a 1-year/$4M deal to compete with Kyle Trask. Honestly, it's all part of the story only Baker Mayfield could write. No other quarterback in the 2018 class could've survived in Cleveland with Hue Jackson, Freddie Kitchens and all the other nonsense that took place during those seasons. Spare me with the Browns could've had Josh Allen or Lamar Jackson talk, neither of those guys would likely be who they are had they come to Cleveland. And how many guys could've been turned away by 3 teams, had one foot firmly out of the league and still continued to fight and grow to do what he's doing now in Tampa? The list is probably just Baker. Like we said, we're happy for Baker and what he's accomplishing. But we don't need to revise the truth of how things went in Cleveland just to make ourselves feel better about other things the Browns have done that didn't work out.

The Dawgs - A Cleveland Browns Podcast

34,341 ๆฌก่ง‚็œ‹ โ€ข 1 ๅนดๅ‰

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,694 ๆฌก่ง‚็œ‹ โ€ข 4 ไธชๆœˆๅ‰

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,685 ๆฌก่ง‚็œ‹ โ€ข 4 ไธชๆœˆๅ‰

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

Himanshu Kumar

85,668 ๆฌก่ง‚็œ‹ โ€ข 3 ไธชๆœˆๅ‰

I revived my 14-year-old dog with peptides. 6 months ago, he was slowing down fast. He was limping, achy, getting up slowly, and couldn't jump on the couch. We honestly didn't know if we had 6 months left with him. Today, our boy is running, jumping on the patio, going on long walks again, and even his hearing is back. I approached his protocol the same way I'd approach mine. - We started with BPC-157 and TB-500. 1-2 mg a day, 5 days on, 2 days off, injected basically the same way you'd inject a human. Within a couple of weeks, we saw less limping, less stiffness, he was moving better, etc. - Then we ran his labs the same way I run mine. Everything looked good except some minor kidney markets, and at his age kidney issues can spiral into problems dogs don't come back from. We addressed this with a bioregulator stack, again the same ones I use. - Then we put him on TRT. We're all aware of what happens to men when testosterone tanks with age. Now consider that we neuter our dogs, cut off their testosterone production entirely, and never think about it again. We put our boy on testosterone and the change was immediate. Within days of the first shot he became a different dog. We started with one shot a week, but just like in humans, by day 5 or 6 the levels drop and you get peaks and troughs. So we split it into two shots a week: Tuesday and Friday. We started conservatively, around 20mg per shot, and titrated up from there based on how he responded and how his labs looked. We landed at about 60mg total per week for a 70 pound dog, keeping a close eye on labs the whole way. That made a huge difference. Shot day is like a revival for him. ... And it's not just us, in fact other families are running the same protocol and seeing similar results. 6 months ago we were counting the time we had left with him. My kids were horrified by the thought that he would no longer be there as they grew up with him as their full-time guardian. Now I genuinely believe we have another 3 years. If you have a dog, understand that he's aging the same way you are. He needs help, but he can't do the research... you can! And after seeing what this protocol did for him, I knew other dog owners deserved access to it too, so check the tweet below.

Michael Morelli

818,642 ๆฌก่ง‚็œ‹ โ€ข 17 ๅคฉๅ‰