Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

.@PBR_Uncommitted ‘26 OF/RHP Layton Pohl just showing off some LOUD tools today. Layton Pohl New Hope HS Baseball ▪️5-foot-11, 188-pounds ▪️6.90 60-yard dash ▪️93 mph from OF ▪️104.8 mph EV 🤯 Some unteachable stuff w/ stout, athletic build. Dynamic two-way talent & name to know this summer. #ViperScout || ViperBaseballAcademy

17,022 görüntüleme • 2 yıl önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Marathon | Ultimate Overview, Gameplay, Hands-On Impressions ▪️Team based extraction shooter set on Tau Ceti IV, scavenge remains of a lost colony for glory and fortune ▪️Launch: Coming to PS5, Xbox and PC on September 23 ▪️Will be a "premium" product, meaning not F2P ▪️"Weapons and movement feels crisp, fluid, and incredibly satisfying in that rarified way that few studios can achieve" ▪️3 maps, 6 runner classes at launch, more to follow post-launch ▪️Plans to support the game with new maps, weapons, characters, and more as it goes on ▪️Ranked play, end game challenges, seasonal storytelling, secrets to discover, community events all in Season One with more content coming ▪️You play as a "runner", cybernetic mercenary who's given up their human form for a bio-synthetic shell with unique abilities and stats ▪️Runner Types: "Locus" is a soldier class for pushing forward, can use a shield, "Void" is stealth, sneak by undetected, use smoke grenades, "Blackbird" is reconnaissance based, find players, positioning, and more ▪️Uncover secrets hidden in the wake of the original Marathon trilogy's events - how and where this overlaps or clashes with the original games "is a story that will unfold over time" ▪️Objective is to get in, get as much loot as you can, and get out alive ▪️If you die, your gear and loot will be up for grabs. Survive and you can take your gear with you on future runs as you grow in power and fill your vault ▪️Fight in a crew of up to 3 players, various map sizes up to 18 players ▪️PvP + PvE, battle other players, security forces, and "otherworldly threats" ▪️Contextual pings, shared objectives, down-but-not-out mechanics ▪️Environments are filled with weapons, materials, items, resources, cores, keys, backpacks, secrets etc to find You can find things like backpacks that expand your inventory, powerful and unique weapons, consumables to heal yourself, ▪️Select your runner, strategically build your loadouts pre-match ▪️Factions in the game can sponsor you and your loadout ▪️You have the freedom to opt out of crew fill and take all the glory for yourself as a solo runner ▪️"This is probably the best-looking, best-feeling extraction shooter ever made", not easy for newcomers to the genre, can be tough to get into, but one previewer was "reluctant to put Marathon down. This is a good sign – the best thing I can say after any preview is that I want more – but big questions remain" ▪️No two matches ever play out the same, dynamic events, variable weather, unpredictable players etc ▪️Customization: Each Runner "brings their own flair", but serve as foundations to customize your playstyle - collect implants and equipment to augment your Runner, like stacking implants/upgrades to reduce heat build-up to allow you to keep running, jumping, sliding longer ▪️Contracts: "Ingenious" incentives, finish contracts you accept for permanent upgrades to your stats, add precious items like grenades, shields, inventory-expanding backpacks, etc to your market. The bigger your market, the better your minimum loadout becomes ▪️Contracts provide "valuable direction", bring welcome diversity and add a "precious hit of semi-permanent progression" ▪️Prestige Cores: Rare items that can "really push the boundaries" (ex: Glitch has an upgrade that turns double jump into triple jump for more manueverability) ▪️Another rare item is a backpack that turns you invisible while interacting with containers (very useful when everyone on the map is hunting you) ▪️Each match "feels like the most important one ever", high stakes, "surprisingly challenging AI enemies" that were "much, much better at surrounding and overwhelming players than the vast majority of AI enemies found in other games" ▪️Having a balanced crew helps in exploring the "dark and forgotten places" in maps - filled with deadly creatures like a species of giant ticks who swarm you frantically ▪️Battles can become frantic as you encounter other crews, stalk them across the map, encounter AI enemies to fend off when others come to claim your loot (one preview battle turned into a 9 player free-for-all) ▪️Downside could be the reward system where skilled players enter fresh matches with high level gear that outmatches less skilled players, though Bungie says it has gone out of its way to try and make it where a poorly equipped squad can still stand a chance if they play well ▪️Even if you die, you can can still get upgrades, improve your reputation with factions, advance in perk trees, etc by completing various quests, looting chests, or fulfilling specific objectives which unlock new bits of story and can grant perks like buying slightly better gear from vendors ▪️"The world Bungie has built is every bit as beautiful as it is creepy and dystopian, and there are moments where they satisfyingly hint at the events of the Marathon trilogy from the ‘90s", though "what little I saw did only slightly more than pay lip service to the world" ▪️Uses the seasonal reset model like in Diablo 4, where players are stripped of their loot and progress at the end of each season to mix things up with new content and new meta ▪️Game is designed to get you killed, Bungie expects average exfiltration rates to be comfortably below 50% ▪️"You will lose a lot, and losing hurts a lot[...]Extracts are snapshots of this unpredictability. That white-knuckle countdown may become a gut-punch defeat, an unforgettable clutch, a desperate last-second dive into the portal as your downed allies watch in envy and horror (couldn't be me), or an unnerving anticlimax. It's not always a pleasant one, but it is a strong emotional hook" ▪️Some previewers worried about variety, weren't impressed with the objectives in the alpha, like hunting computer monitors on the map, sprinting over, marking dropships, sprinting over, and repeating, though random events help spice things up ▪️Not a 20-map game says Bungie, map design "does have that sticky battle royale quality of generating memories", though still worried 3-4 medium sized maps might not be enough ▪️Bungie's "verbiage" on updates sounds like possibly 1 new map a year + refreshing existing ones in between, which could work in its favor pushing players to really learn maps, but will they hold up over hundreds of hours? ▪️Fights are decided by gun skill, clever ability use, map awareness, how strong your shield is, how many healing supplies you have, etc ▪️Example: If you have one bar of shield and enemy has four, you'll lose 1v1, but change it up with powerful grenades, status effects like toxic or overheat, backpacks are "transformative", etc Gameplay Trailer ▶️ Gameplay Overview ▶️ PS Blog ➡️ IGN ➡️ GamesRadar ➡️ ▶️

Shinobi602

181,743 görüntüleme • 1 yıl önce

RHP Matt Scott (Stanford Baseball) is one of the premier college arms in this year's Draft. After a solid Freshman season that was split between the bullpen and the rotation, Scott this year anchored the Stanford rotation and collected a career-high 103 strikeouts against 36 walks across 80 innings. Earned a Team USA invite for the second straight summer. Scott has an XL, workhorse frame at 6-foot-7 and 247-pounds with plenty of strength and physicality throughout. Quiet, "checkpoint-like" delivery. Small side step towards 1B side, gathers himself and breaks into the rest of his operation. Attacks from a high-three quarter slot. Low effort, does a nice job of staying connected and in-sync for someone of his stature. FB sits in the 93-96 range, but will routinely touch 97/98. Tons of carry through the zone, averaged 22.5" of IVB last year. At its best when located in the top-1/2 of the zone, which is also where it generates most of its whiffs. Just needs to stay out of the middle. Threw it 62% of the time and generated a pretty impressive miss rate of 26%, though I think it can become even more effective if he's able to hone in on his command of it. 55 pitch right now, eventual 60 if some of the low hanging fruit is cleaned up. Supplements his FB with a mid-to-upper-80s gyro SL. I actually think Scott's feel for the SL is on par, if not better, than his feel for the heater. Effective against both right and lefthanded hitters. True, hard gyro look against LHH. Will flash more two-plane tilt against RHH with some sharpness to it. Another 55 pitch that last year had a 40% miss rate. Scott needs to up the usage on his split-change. Threw it just 6% of the time last year and I think it's his best secondary pitch. Legit weapon against LHH. Averaged nearly 12 MPH off his FB and he does an excellent job of killing spin on it; averaged 866 RPMs last season. Essentially falls off a table as it approaches the plate. Serious tumbling life with a bit of arm side fade. 48% miss across a limited sample in '24, I'd give it a 60. Command and control are both average, if not a tick above. Little-to-no reliever risk. Really like the body and stuff. Projects to be one of the first few college arms off the board this July and is a potential first-rounder.

Peter Flaherty III

23,661 görüntüleme • 1 yıl önce

LHP Ben Abeldt (TCU Baseball) is a name to follow closely this spring. Enjoyed a strong Freshman year in which he worked a 3.60 ERA with 71 Ks to 24 BB in 55 IP. Was dominant last spring and pitched his way to a 1.83 ERA with 54 Ks to just 16 BB across 44.1 IP. Two-time Team USA invitee. Standard pitchers' frame at 6-foot-3 and 210-pounds. Added noticeable strength and physicality to it between '23 and '24. Some natural funk and deception in his delivery. Uncomfortable look, especially for LHH. Works exclusively on the 1B side of the rubber which makes it even tougher for LHH. Long, loose arm stroke and attacks from a low-three quarter slot. Big time crossfire. Abeldt relies heavily on his fastball (threw it 79% of the time in '24) that sits in the 91-94 MPH range. Was up to 96 during the spring and up to 98 over the summer. Run and ride through the zone with particular life on his arm side. Like a lot of the low-release lefties who have a little giddy up on their heaters, it's generates the most whiffs when located on the inner-1/2 and/or top-1/2 of the zone. Does a nice job of staying off the barrel with it, 23% whiff and OBA of .208 last spring. Go-to secondary offering is his low-80s slider. Long, sweeping life with some late bite at times. Not to beat a dead horse, but just a brutal look for lefties; Abeldt will release the pitch from essentially behind their backs. Legit swing-and-miss pitch that's effective against both right and lefthanded hitters. 45% miss rate last spring, comfortably a 55. Closer to a 6 than a 55. Third pitch right now is a low-80s CH for which he's still gaining a feel. Gets good separation off his FB (averaged 10 MPH off) and does a nice job of killing spin. Natural fade to the arm side and will occasionally flash some tumbling life. Profiles as an effective option against RHH. Strike-throwing ability is above-average. The key for Abeldt this season is selling his ability to start. Has made just 2 starts in his collegiate career and could headline TCU's rotation in '25. Look for both the SL and CH usage (especially the SL) to tick up. Curious to see how he fares in more extended looks. Easy comp is former Miami LHP Rafe Schlesinger. 3rd-4th round type this July.

Peter Flaherty III

27,890 görüntüleme • 1 yıl önce

OF COURSE ISRAEL WAS INVOLVED IN THE ASS*SSINATION OF CHARLIE KIRK. Let me explain why. 🔖& share this. In November 2023, a leaked call from Jonathan Greenblatt of the ADL revealed a "major generational problem" regarding declining support for israel in America. He revealed polling that showed it wasn't "Left vs. Right," but it was "young vs. old." He called this the "TikTok problem," or the "Gen Z problem." He called Gen Z "useful idiots" and said the "real game" was to solve this problem. He called for the jewish community to put their collective brains together to solve this generational problem. Here's what we know they did: 1. They immediately pressured Tiktok to increase censorship. In November 2023 alone, TikTok deleted over 900,000 pro-Palestine videos. They also blocked various hashtags, including "israel did 911." 2. They mobilized a high-pressure campaign against the Ivy League campuses that were the epicenter of pro-Palestine protests & activism. Several university presidents were punished & replaced by jews and/or zionists willing to suppress free speech. (We must note that this campus activism was driven by Leftist organizations. This will be important later.) 3. They lobbied congress, which then passed new laws suppressing & punishing campus free speech & demonstrations classified as "antisemitic." 4. They lobbied congress to outright shut down & ban Tiktok, which congress obliged. However, Trump ended up "saving" TikTok, which was then forced to sell itself to a consortium of pro-israel jewish billionaires, led principally by uber-zionist Larry Ellison. That sale went through on September 16, 2025—6 days after Charlie Kirk was ass*ssinated. 5. In early 2025, the newly-installed Trump administration threatened to withhold $Hundreds of Millions in federal aid to several universities unless they put "safeguards" in place preventing the outbreak of pro-Palestinian activism (again defined as "antisemitism"). 6. In 2025, israel, through organizations like Israel365, started spending $Millions on sending hundreds of American "influencers" to israel in order to get them promoting the zionist cause and rehabilitating israel's image. 7. In 2025, Netanyahu launched Israel's "8th-Front" Information Warfare campaign, targeting the social media & AI landscape in the United States. Israel has earmarked an additional $729 million in FY2026 for these operations. 8. Zionist billionaires took over the entire CBS/Paramount media ecosystem in August 2025. (And they've just now added the entire Warner Bros. Discovery ecosystem, which they've also been pursuing since the fall of 2025). But despite all of this, israel had a problem. Call it the Charlie Kirk TPUSA problem. ▪️Charlie led a campus organization for youth ON THE RIGHT, with 600k+ lifetime members, and 250k+ active members. The largest organization of its kind, completely beholden to his leadership. ▪️Charlie generated billions of views on Tiktok & across the social media landscape, and was firmly opposed to censorship of all kinds including and explicitly speech critical of israel. ▪️Charlie was completely critical of the ADL, calling for its ban on social media & diametrically opposing its calls for more censorship. ▪️Charlie was extremely outspoken and critical of Left-wing jewish activism, which he blamed for the radical, open-borders Marxism ruining the country. ▪️Charlie actively asserted his massive influence to oppose regime-change war in Iran, pressuring Donald Trump inside the Whitehouse itself. ▪️Charlie was becoming increasingly critical of israel & zionism: questioning the suspicious events of 10/7, openly platforming debates against zionism, & himself leading discussions that advocated for cutting aid to israel, releasing the Epstein files, and calling for AIPAC to be registered as a foreign agent under FARA. It should be noted that demanding FARA registration of the israel lobby was one of the actions that got JFK ass*ssinated by the same people. ▪️Charlie was giving TPUSA platform access to powerful israel-critical voices like Tucker Carlson & Dave Smith, and intended to expand that to include Candace Owens. You have seen how ape-sh*t crazy they're going over Tucker & Candace—people who were telling the truth about Epstein & israeli control over the US government and also discouraging war with Iran. ▪️We now also know that Charlie was done with the pro-israel cause and had been signaling his intent to drop it. We have the leaked text, but that didn't happen in a vacuum. That was no doubt the culmination of a lot of momentum in that direction. Here's what I want you to realize if you haven't already: Charlie Kirk was single-handedly undoing or undercutting every move israel & organized jewry had made over the previous 2 years to solve the "Gen Z problem." Remember how organized campus opposition to israel came from the Left? Well here came Charlie Kirk re-platforming it on the Right! Charlie had transformed TPUSA into a Trojan horse—allowing & amplifying everything they'd sought to eliminate from the Left! Charlie Kirk was a massive roadblock to the jewish plan to re-conquer the minds of the youth of America. He was literally AND figuratively the Big Man On Campus. The most influential man in America on the youth. He was allowing and accelerating the rising generation to be radically anti-israel while simultaneously being "Conservative Republicans" in good standing who wouldn't be canceled. THE PLAN The israel-network tried several (ineffective) methods to solve the Charlie Kirk TPUSA problem. 1. They tried to quietly & privately influence him in private with through people like Josh Hammer & Rabbi Wolicki, and surround him with pro-zionists like Rob McCoy & Frank Turek. 2. They launched a high-pressure influence operation against him, which culminated in a 2-day "moral blackmail" event in the Hamptons. He took to the media to denounce these efforts. 3. They tried to outright buy him off when Netanyahu offered $150 million. He refused. 4. They tried to force his hand by pulling funding—notable was the $2 million withdrawn by Robert Shillman. He responded by launching a DOGE effort to shore up the finances and by announcing his intentions to leave the pro-israel cause. In summary: they dragged him privately & publicly; they blackmailed him; and then they tried to buy him. Nothing worked. He deflected everything, said 'NO,' and fought off all the attacks. He had resolved to find a new way forward with the new financial situation. Is there any doubt he would have succeeded? That left the israel-jewish network with only one option—an option that time-and-time-again they've been all too willing to resort to. Don't come at me with "Charlie Kirk supported israel!" and "Charlie Kirk loved the jews!" nonsense. John F. Kennedy also supported israel and embraced the jews. But there was a conflict: he put America first. And so did Charlie Kirk. My facts are true. And my logic is sound. I won't hear of this "lone gunman" nonsense any more. Miss me with the "Some random kid all by himself drove 300 miles on a week's notice, shoved a 110-year old gun down his pants, walked onto a roof directly in front of Charlie, delivered a perfect 1-shot/1-kill, escaped with no problem, and then immediately texted the whole plan to his furry roommate." israel would not be able to take this country to war against Iran if Charlie Kirk were still alive today. Period. I don't care how much he loved jews on a personal level. The hostile takeover of TPUSA was every bit as necessary as the hostile takeover of Tiktok and the Ivy league universities. Either you believe israel was the recipient of the most timely, fantastic stroke of geopolitical good luck ever, or you realize that Jonathan Greenblatt's injunction to take back Gen Z has been fulfilled in practically every particular.

Sam Parker 🇺🇸🧯

313,603 görüntüleme • 7 ay önce

Zack Polanski, "Today I was in Oxfordshire, standing in the aftermath of the devastation caused by a wildfire. Trees reduced to charcoal, cars turned to burnt out wrecks. The smell of smoke still lingering in the air on the site of what was once a thriving local business now reduced to ash." "Wildfires, literal scorched earth and a looming sense. And I really want everyone to hear this. This is only just the beginning. And today, as temperatures fall at the end of yet another extreme heat alert, we know that if it rains now, the soil being baked dry means it's much more likely to flood." "These days feel exceptional. But what we are living through right now are likely some of the least extreme summer temperatures we'll experience in our lifetimes. Today I am sounding the alarm and I'm laying out a plan." "Because last week, while a wildfire the size of 200 football pitches was raging across Suffolk, I called on, Prime Minister Burnham to act urgently to address the crisis. I suggested a COBRA meeting being the very least he could do." "And six days later, with another heat alert just having ended, we have still heard next to nothing from the very top of government. No emergency briefings, no new plan and precious little detail about how this government will protect people from the crisis." "It is putting lives and livelihoods at risk across the entire uk. So today I'm delivering a reality cheque. We are facing the biggest threat to this country since the Second World War." "I'm setting out what Prime Minister Burnham can do now to tackle the crisis and I am challenging him to act with the urgency we need. You will hear today from those on the front line of this crisis and they will lay out what they have dealt with in the past few weeks." "And to them, on behalf of the entire country, I want to say thank you. Extreme weather is now the new normal and without action, the impact on the people of this country will be unimaginably grave." "The threats we face are three hold first, the threat to the safety of the population. Almost 3,000 people have died from the effects of extreme heat this summer. And we know that older people and those with pre existing conditions are particularly at risk from these dangerous temperatures." "Those are the people who have been forced to stay at home for days on end, windows, curtains closed, trying to wait out the extreme heat. And these are the people who are most likely now to have grieving families whose bodies were under such intense strain and trying just to stay cool that their kidneys and their hearts could no longer cope." "Meanwhile, wildfires have seen hundreds evacuated from their homes, while many thousands more wait anxiously with Flames on the horizon and smoke in their lungs. We've seen across Europe how bad things can get." "Hundreds of thousands evacuated, half a million acres burned. The sheer scale of the devastation is hard to comprehend, but we need to look it in the face, because this is only a taster of what's to come if we don't act now." "Second, we face a threat to our food and water security. Farmers are now warning we could see food shortages after flooding followed by drought has decimated crops. And despite farmers working really hard through the nights to avoid the heat, food production is grinding to a halt and our food prices are set to rise." "Half of England is experiencing serious drought. And across the country, 8 of our water reservoirs are at risk of running dry. Privatised water companies they've failed to build a single new reservoir to since 1992, are, losing nearly 3 billion litres of water a day from leaky pipes." "That's five times more than a nationwide host pipe ban would even save. The threat is so severe that the UK's National Risk Register warns that if we have three years of exceptionally dry weather like this, we could face water rationing." "These aren't distant possibilities, they're very real scenarios and they are coming straight at us down the track because finally, we face a threat to our very way of life. Parents unable to take their children to the playground because the slides are so hot it could burn, their skin off." "Temperatures so high they keep us inside for days for the sake of our health. Cities feeling like ghost towns, parks turned into deserts. We only have to look across the Channel to France and Spain to see what faces us in the years ahead." "Europe is heating at, twice the rate of the rest of the world. Wildfires, droughts, deadly floods. The scenes we have seen play out on our TV screens are, frankly apocalyptic. And yet the response from our government is to pretend none of this is happening." "It is an astonishing dereliction of duty from those whose very first responsibility is to keep all of us safe, and from the media. With some brilliant and notable exceptions, we have seen more clamouring for North Sea drilling in the last few weeks than actually raising the alarm on climate breakdown." "While our country has come together, people have offered shelter to those who have had to leave their homes due to wildfires. They've checked in with older neighbours to care for those who are sick because of the heat. But the government. The government have been far, far too quiet on what is an emergency." "So today you will hear from some of those on the front line of this crisis and Those with vital insights into how we face this threat. A doctor, a firefighter, someone who served this country in the armed forces, and someone who has dedicated his entire career to our precious nature and wildlife." "It's experts like these that this government should be bringing to the table to design a full scale emergency response. So I want to step out from this big picture and look at some of the urgent steps that Prime Minister Burnham needs to urgently announce to protect people right now and keep us safe from what we know is coming down the track." "In the immediate term, we need to keep people safe from extreme temperatures. That means a free accessible cool space in every local area. And financial support for households so they can heat proof their homes. Second, we need a robust wildfire prevention strategy." "A fire service with the resources it needs to tackle blazes when they come. And that must include firefighting helicopters when needed. And not again ever seeing the shocking sight of requiring a charity to step in to contract a private firm to help fight fires." "And this should all be funded by taxing the fossil fuel giants who are profiting from fueling these infernos. And finally, to secure our water supply, prevent droughts and protect our food system, we need to bring water back into public hands." "Right now, money is flowing out of our hands into the pockets of shareholders, just like water is flowing out of those companies leaky pipes in the middle of a drought. Every single penny households pay for their water needs to go back into strengthening our infrastructure, building new reservoirs and protecting us from the droughts of the future." "We know that these extreme temperatures, these deadly wildfires, are being driven by the burning of fossil fuels. The sad reality is decades of inaction of politicians allowing fossil fuel companies to profit from pumping out deadly emissions have guaranteed the extreme weather we are seeing right now." "And we will see for the rest of our lifetimes. But there is still time to stop total breakdown. So let me speak directly to the Prime Minister. If we are to secure a livable future for our children and for our grandchildren, there can be no new drilling for oil and gas." "On this, the, the science is crystal clear. As politicians, we have a moral responsibility to do what is right for the people we serve, even when it's not politically convenient. And I know that whatever our differences, we both care deeply about the people of this country and the future of our planet." "So when the time comes, I hope you will have the courage to be truthful, be brave and hold firm to your party's commitment to no new oil and gas drilling in the North Sea, including both Rosebank and, Jackdaw." "Now, some will say we can't afford to make these changes. These last few weeks are showing we can't afford not to. We are facing an existential threat. People are dying. People are scared." "It is time to act. And when we do, we won't just avoid the worst effects of climate breakdown. We will lower bills permanently, help our communities thrive, and give a grounded sense of hope for generations to come."

Farrukh

87,169 görüntüleme • 1 ay önce

CHARLIE KIRK, POLITICAL ASS*SSINATIONS, AND THE B'NAI B'RITH (Warning: For Elite Pattern Recognizers Only) Candace Owens ▶️ This is a long post, and won't get very good reach unless you heavily interact with it. Please give it a like, a bookmark, a comment and a retweet. Or else it will just die. 5 minutes to read, 5 minutes to watch the video. But in 10 minutes you'll get an advanced class on B'nai B'rith and ass*ssinations that took me months of research to put together. If you watched Candace Owens yesterday, you learned a little about the B'nai B'rith, a jewish masonic secret society/fraternal order, & its related institution, the ADL. I clocked the ADL 4 days after Charlie Kirk was ass*ssinated. By October 4th, I was openly suspecting them of allegedly playing some kind of role in the hit. But to understand why I suspected to find their involvement, we must review some history. Then we can apply it to Charlie Kirk's ass*ssination. The B'nai B'rith/ADL were materially involved in the JFK, RFK, & MLK ass*ssinations: ▪️JFK▪️ B'nai B'rith member Julius Schepps was President of the Dallas Citizens Council, the organization that invited JFK to Dallas the fateful day of the ass*ssination. It's believed Abraham Zapruder, the jew who captured the infamous footage, was also a member of the B'nai B'rith. Zapruder's office was in the Dal-Tex building (which was next to the Texas School Book Depository) where dozens of witnesses attested that multiple gunshots came from. The Dal-Tex building was owned by the jews David Weisblat and Morris J. Russ until November 1, 1963, when it was transferred to Russ's widow Sylvia Golden Russ just 3 weeks before the ass*ssination. David Weisblat worked for the Anti-Defamation League of the B’nai B’rith. The ADL. Perhaps to get ahead of things, the B'nai B'rith awarded JFK a presidential Gold Medal on January 31, 1963, while he was mired in a battle with israeli Prime Minister David Ben Gurion over israel's illicit nuclear program. What better way to deflect blame! "He was our greatest ally!" Sound familiar? ▪️RFK▪️ RFK's Press Secretary, Frank Mankiewicz, was the Civil Rights Director for the western branch of the Anti-Defamation League of B’nai B’rith. The ADL. It was Mankiewicz who diverted RFK from exiting out the ballroom of the Ambassador Hotel as planned and into the kitchen where Sirhan Sirhan & Thane Eugene Cesar were waiting to shoot him. At the time, the Ambassador Hotel was owned by the jew Junius Myer Schine, who once upon a time allowed the jewish gangster Mickey Cohen to operate an illegal casino inside the hotel. Mickey Cohen had a famous stripper girlfriend named Candy Barr whom he notoriously shared with JACK RUBY and jewish terrorist/israeli Prime Minister Menachem Begin (Begin was leader of the Irgun & mastermind of the King David Hotel bombing in 1946. He also founded the Likud, the party that Netanyahu is a member of, which is currently running israel). RFK's DOJ had previously sent Mickey Cohen to prison for 15 years, after RFK personally grilled Cohen in televised senate hearings. BONUS: Junius Schine's son David was mentored by the homosexual jewish fixer Roy Cohn, and they both made the cover of Time Magazine for their central role in the famous Army-McCarthy senate hearings. David would go on to marry Miss Universe 1955, Hillevi Rombin of Sweden (I'll note that the Miss Universe Pageant was owned by jews at the time). Later, Roy Cohn would mentor another young man in the New York real estate scene named Donald J. Trump. Trump would later buy the Ambassador Hotel AND the Miss Universe Pageant! (Try not to notice the intersection between pageants, modeling, and the so-called Epstein network. But, I digress. Lol). ▪️MLK▪️ The ADL had of course been a long-time partner and ally with MLK in the Civil Rights movement. However, according to Henry Schwarzschild—who worked in the ADL’s publications department from 1962 to 1964—the ADL monitored (spied on) King because it considered him a "loose cannon", and the ADL periodically passed information on King to the FBI. Schwarzschild alleged this was “common and casually accepted knowledge” within the ADL. Later, MLK & his Southern Christian Leadership Conference (SCLC) was targeted by the FBI's infamous COINTELPRO. During that entire era, the ADL was known to collaborate closely with the FBI, just as they do now. For years, the ADL has trained every FBI agent. But there's an even deeper & more specific connection between the ADL and the MLK assassination. James Earl Ray's handler Raul once gave Ray an "emergency phone number" of sorts. Raul was a known business associate of Jack Ruby—why does he keep popping up? Raul was also involved in an illegal arms trafficking operation smuggling weapons to israel. This phone number Raul gave a Ray was to Samuel Laventhal, owner of Marine Supply and Salvage Co. of New Orleans. Laventhal was a member of the B'nai B'rith & Zionist Organization of America. In the initial appeal of his conviction, Ray reported that Laventhal was "distressed" about MLK's forthcoming public support for Palestine. Later, in 1978, Ray testified before the House Select Committee on Assassinations that someone in MLK's organization had made contact with the Palestinians about a potential alliance, and that King "intended to support the Arab cause." MLK had already famously 'left the pro-israel cause' when he canceled his much-publicized trip to israel scheduled for November 1967. MLK had soured on israel after its aggression in the 6-Day War placed him in a difficult political position with the 3rd world, with whom he was building a coalition. It was sometime after King's israel trip cancelation that Ray learned from Laventhal of MLK's allegiance switch (Remember, the ADL of the B'nai B'rith was spying on MLK & his organization). But before an alliance with Palestine could be worked out & publicly announced, King was murdered on April 4, 1968, and Ray was framed as the lone gunman patsy. We should note that the cover alias James Earl Ray somehow obtained and assumed while he was on the run was Eric S. Galt, a man who had national security clearance and was the manager of a Union Carbide plant manufacturing proximity bomb fuses being illegally smuggled to israel. Very weird! BACK TO CHARLIE KIRK Knowing this information, and having already noted many troubling similarities between Charlie's ass*ssination and the 3 ass*ssinations mentioned above, I was on the lookout for signs of ADL involvement. The B'nai B'rith is an underground network (literally) that could theoretically facilitate surreptitious planning, collaboration and coordination. Allegedly. I've written extensively about the battle Charlie was waging against the ADL since he joined us in September 2023 calling to #BanTheADL. Search my timeline for "Charlie AND ADL" For its part, the ADL had included TPUSA in its infamous "Glossary On Extremism & Hate." Charlie called to ban the ADL multiple times in September 2023. He called it an anti-White hate group. In November 2023, he declared the ADL was "part and parcel with Black Lives Matter" and "went all in on woke." He included them as one of the Left-wing jewish groups that was pushing the radical open borders and quasi-marxist policies ruining America. At the same time that Charlie was attacking the ADL in the fall of 2023, the ADL was on record proclaiming that America had a GenZ/TikTok problem regarding support for israel, and it launched a set of major initiatives to help reclaim America's youth. Many of these initiatives centered on college campuses and social media—two arenas dominated by Charlie Kirk. After Charlie's ass*ssination, the ADL published a hit piece on people alleging that israel was behind Charlie's murder. Their "Glossary On Extremism & Hate" began to circulate online and they were pressured to shut it down, which they did on September 30th, 2025. In early October, Kash Patel piled on, announcing that the FBI would be severing its longstanding ties with the ADL. (I've seen little evidence for this actually happening, btw). He also announced an end to the FBI's partnership with the SPLC, another radical jewish organization that had been attacking Charlie and TPUSA. It was at that point that a most curious thing happened: on October 3rd, Marissa Streit, former member of IDF Unit 8200 & CEO of PragerU, attacked the ADL & SPLC—which I clocked at time as being kosher theater. We should also note that according to Ben Shapiro, the Daily Wire shared space, talent and equipment with PragerU when both organizations were in their infancy. This will soon become more important in our story. Here's what I think was (allegedly) happening: the Conspirators were using the ADL and its adversarial relationship to TPUSA & Charlie Kirk to help cement the narrative that Charlie was murdered because of radical Leftist hate. That's why the ADL took down its "Glossary On Extremism & Hate." That's why Kash Patel publicly distanced the FBI from the ADL. And that's why fellow jewish intelligence operative Marissa Streit denounced it the ADL. But that's just one interpretation of the facts and I'm not accusing anyone specifically of a crime. Do your own research and make up your own mind. Right after that, on October 4th, 2025, Candace Owens found out that Kash Patel had flown in the agents from the FBI's Connecticut Office to "investigate" at UVU. That's the FBI office that shares building space with the ADL. At that point, I'd seen enough, and I started publicly airing my initially private hypothesis that the ADL was likely materially involved with Charlie's ass*ssination. But my tenuous alleged hypothesis was strengthened yesterday when we found out that Ben Shapiro was having a breakfast/lunch meeting with the Gary Javitch—Former Executive Director of B'nai B'rith International & former president of the Henry Monsky Lodge of the B'nai B'rith & member of the ADL—when Ben found out about the hit on Charlie almost right away. Within about 5 minutes or less, Ben's IDF security team was on the phone with someone in Charlie's SUV while it sped Charlie to the hospital. Mind-boggingly weird & dumbfounding. I'm not making any accusations of guilt, I want to be very clear about that. But this is a troubling set of facts and patterns that I believe looks like more than a coincidence. Why the heck would the security team of a long-time enemy to Charlie be on phone with Charlie's security team as it raced Charlie to the hospital? And while Shapiro just happened to be in a meeting with a high-level member of the ADL & the B'nai B'rith?! What. Are. The. Odds? And let's not forget that after months without any interaction, and knowing that Charlie saw Ben Shapiro as an adversary, Andrew Kolvet booked Shapiro as Charlie's guest the day before Charlie was assassinated. The same day Charlie proclaimed that he was leaving the pro-israel cause. The same day that Charlie likely had a Zoom struggle session with Rabbi Wolicki and Josh Hammer (who is a close friend of Ben Shapiro). The same day that Charlie texted multiple people the cryptic 'they're going to kill me.' And then within a week, Ben was hosting the Charlie Kirk Show and proclaiming he'd pick up the bloody mic? I'm sorry, but given all this context I've painstakingly recounted, am I the only one who thinks we deserve an explanation? WTF, Shapiro? ▪️Like, retweet, reply, bookmark▪️

Sam Parker 🇺🇸🧯

144,068 görüntüleme • 2 ay önce

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,934 görüntüleme • 6 ay önce

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

Mike

15,248 görüntüleme • 10 ay önce

A tree stood in that backyard for probably 40 years. Nobody who walked past it, sat under it, leaned a bike against it, ever knew what was living inside the trunk. Then someone cut into it. And what came out shouldn't be possible. Not sap. Not resin. Water. Gallons of it. Pouring out of solid wood like someone left a hose running inside a living organism. If your first reaction is "that's fake" — I understand. I had the same reaction the first time I saw footage like this. Trees are supposed to be dry on the inside. Bark, wood, rings, maybe some sticky sap if you're unlucky enough to touch a pine. Nobody grows up learning that a tree can be a pressurized tank. But here's the thing nobody tells you in school: some trees are. There's a real, documented, scientifically studied phenomenon behind this, and once you understand it, you will never look at a tree the same way again. I'm going to walk you through exactly what's happening inside these trees, why it happens, which species are famous for it, the wild historical accounts of people discovering it by accident (sometimes violently), and why arborists still get caught off guard by it after decades on the job. Stick with me. This gets stranger the deeper you go. — FIRST: the phenomenon has a name. Arborists and plant pathologists call it "wetwood," and in its more advanced, foul-smelling form, "slime flux." It's not folklore. It's not an urban legend some guy made up on a forum. It's in forestry textbooks, USDA plant pathology bulletins, and arborist training manuals. Here's the mechanism, stripped down to plain English: Trees have a core of heartwood — the dead, structural center of the trunk that no longer transports nutrients. It's basically the tree's skeleton. In most trees, that heartwood is just dry, solid wood. But in certain species, under certain conditions, bacteria colonize that heartwood core. Anaerobic bacteria — the kind that thrive without oxygen — move in and start fermenting the wood tissue from the inside. That fermentation process does two things. First, it draws in and traps enormous amounts of water inside the wood, way beyond what healthy wood would ever hold. Second, it produces gas as a byproduct — methane, carbon dioxide, hydrogen sulfide — and that gas has nowhere to go. It's sealed inside solid wood, inside bark, inside a living, growing tree. So you end up with a chamber, sometimes several feet long, sitting inside the trunk, completely pressurized, completely hidden, holding a mixture of bacteria-laden water and trapped gas — sometimes under enough pressure that when the seal finally breaks, it doesn't drip. It sprays. It gushes. It pours out like the tree itself is bleeding. Now imagine you're an arborist. You've cut down thousands of trees. You know the drill: bark, sapwood, heartwood, done. And then one day your saw breaks through into a hidden pocket you had no way of detecting from the outside, and suddenly you're standing in a puddle that came from inside a tree trunk. That moment is what you're about to see. — Let me give you some numbers, because the scale of this is what makes people stop scrolling. Documented cases of wetwood trees have released water measured in the dozens of gallons from a single cut. Some large elms and cottonwoods have been recorded discharging water continuously for hours after being wounded, with foresters describing "streams" running from the trunk down to the base of the tree and pooling on the ground like a slow leak from a cracked pipe. Certain species are repeat offenders. Elm. Poplar. Cottonwood. Mulberry. Certain oaks. These trees, especially older ones with some history of trunk injury (a old pruning wound, storm damage, a lightning strike, construction damage to the roots), are far more likely to develop internal wetwood pockets, because any breach in the bark is an open door for the bacteria that start this whole process. That's the part that should sit with you for a second. It usually starts with something small. A branch snapped off in a storm. A lawnmower nick at the base. A woodpecker hole. Something that looks like nothing. And over years — sometimes decades — that tiny wound becomes the entry point for a slow-motion transformation happening entirely out of sight, turning part of the tree's interior into a sealed reservoir. You could have one in your own yard right now. You'd have no way of knowing. That's not a scare tactic, that's just how wetwood works — it's invisible from the outside until the tree is cut, cored, drilled, or storm-damaged enough to expose the pocket. — There's an older, uglier cousin of wetwood, and it's called "slime flux," and I promise you the name undersells it. When the pressure inside a wetwood pocket gets high enough, it doesn't wait for someone with a chainsaw. It finds its own way out — through cracks in the bark, through old wounds, through the base of branches. And when that fluid meets open air, the bacteria and yeast in it start reacting with oxygen, and the whole thing turns into a foul, fermenting slurry running down the bark. Old-time foresters called this "flux disease," and some described the smell as somewhere between rotten cabbage and spoiled beer. Insects love it. Certain flies and beetles are specifically drawn to fluxing trees, and some entomologists have documented entire miniature ecosystems living in the wet, fermented bark of a heavily infected wetwood tree. So the version you're about to watch — a clean cut suddenly releasing a rush of water — is actually the tamer version of this phenomenon. It's what happens when the pressure is released fast and deliberately, in a controlled way, instead of slowly seeping and fermenting on the bark for months. It's dramatic, but it's not even the strangest form this condition takes. — Here's where it gets almost unbelievable if you didn't grow up around old-growth forests or work in forestry: this isn't new, and it isn't rare enough to be dismissed as a one-off. Loggers in the 19th and early 20th centuries wrote about "water trees" and "spring trees" — trunks that, when felled or split, would release surprising volumes of water, sometimes described as clean and cold enough that thirsty travelers would drink straight from a freshly cut trunk. Some of these accounts read almost like myth: a felled tree in a dry stretch of forest becoming an impromptu water source for a work crew that had run out of canteens. Indigenous and folk traditions across multiple continents have stories about trees that "cry" or "bleed" water, long before anyone had a bacteriological explanation for it. In parts of the American South, old-timers used to warn newcomers about certain elms and cottonwoods being "wet-hearted," a term passed down generation to generation with no formal science behind it — just observation. They knew, decades before plant pathologists gave it a Latin name, that some trees were different on the inside. There's something almost humbling about that. A phenomenon that sounds like it belongs in a fantasy novel — a tree holding a hidden reservoir inside its trunk — turns out to be something people quietly knew about for centuries, passed down as folk wisdom, and modern science eventually caught up and explained the mechanism. — Let's talk about pressure, because this is the part that turns a "huh, neat" fact into something genuinely dramatic to witness. Wetwood pockets aren't just wet. They're pressurized. Researchers who have studied this by drilling into infected trees and measuring the internal gas pressure have recorded readings significantly above normal atmospheric pressure — high enough that when a probe finally punctures the pocket, gas and liquid don't just seep out, they can audibly hiss, spray, or in some documented cases, forcefully eject material several feet from the trunk. Think about what that means physically. You have a living tree. Roots pulling water up. Leaves doing their thing. Bark looking completely normal, maybe a little bit of old staining near a wound if you know exactly what to look for. And inside, invisible to anyone walking by, there's a sealed chamber behaving less like "wood" and more like a bottle of soda that's been shaken and capped for years. Cut into that with the wrong angle, at the wrong depth, and you are opening something that has been building pressure since before some of you reading this were born. That is not an exaggeration. Some of these wetwood pockets, in old trees with a long history of minor trunk injuries, have been forming and sealing and re-sealing for twenty, thirty, forty years before anyone finally exposes them. — I want to address the skeptics directly, because there's always a version of this that goes semi-viral and the replies fill up with "CGI," "staged," "fake," before anyone bothers to check. This is genuinely, boringly, documented science. Forestry extension offices at multiple universities have publications specifically on wetwood and slime flux — the kind of dry, unglamorous PDF nobody reads unless they're an arborist student cramming for an exam. Plant pathology courses cover it. It's in the same category as things like "trees can produce enough root pressure to push water dozens of feet upward with no pump" — real, measurable, and honestly stranger than most fiction, which is exactly why it keeps going viral every time footage surfaces. The wild part isn't that it's fake. The wild part is that it's real, it's been known for over a century, and most people are hearing about it for the first time through a random video instead of a biology class. — Here's a question worth sitting with: how many trees around you, right now, could be holding something like this? You're not going to know by looking. That's the unsettling part. Wetwood doesn't announce itself from the outside in any reliable way most people would recognize. Sometimes there's a dark wet-looking stain running down the bark from an old wound — that's actually one of the only visible clues, and most people who see it assume it's just water damage or normal bark discoloration, not a sign of a pressurized internal reservoir. Arborists who specialize in tree risk assessment actually have to factor this into their evaluations, because a wetwood pocket can also be a structural weak point — the internal decay associated with it can compromise a tree's strength in ways that aren't visible from a standard visual inspection. So this isn't purely a "huh, cool fact" situation. For professionals, it's something they're trained to watch for, because it changes how a tree behaves, how it should be pruned, and in some cases whether it's even safe to keep standing near a structure. — Let's go species by species for a second, because the "which trees do this" question comes up every single time this kind of footage circulates. Elms are probably the most famous offenders — American elm and Siberian elm both show up repeatedly in wetwood and slime flux case studies. Cottonwoods and poplars are right behind them, especially older specimens with a history of storm damage or pruning wounds. Mulberry trees have a documented tendency toward it as well. Certain oaks can develop it, though it's less common and usually tied to a specific injury history. Willows, with their notoriously soft and moisture-loving wood, are also frequent candidates. What connects almost all of these species isn't some exotic trait — it's actually pretty mundane. They tend to be fast-growing, softer-wooded trees that are more prone to storm damage, cracking, and wound formation over their lifespan, which means more entry points for the bacteria that kick off the entire process. Slower-growing, denser hardwoods are comparatively less prone, though not immune. So if you've got an old elm, cottonwood, poplar, willow, or mulberry anywhere near you — especially one that's taken some damage over the decades, a lost limb, a lightning strike, an old chainsaw wound from a previous trim — there's a real, non-zero chance that tree is sitting on its own hidden reservoir right now, quietly pressurizing, waiting for the day someone finally cuts into the wrong spot. — There's a specific kind of moment that happens on video like this, and if you've watched enough tree-work content you already know it: the split second between the cut going in and the reaction on the face of whoever's holding the saw. That reaction is real. You cannot fake genuine, immediate confusion. Professionals who have done this job for years, who have felled hundreds or thousands of trees, who think they've seen every possible thing a tree trunk can do — and then something happens that their entire career didn't prepare them for. That's the part that makes this kind of footage so different from staged "reaction" content you see everywhere else online. Nobody scripts confusion that specific. Nobody fakes the half-second delay where someone's brain is visibly trying to process what their eyes are showing them. — I'll leave you with this. Every single day, all over the world, people are cutting down trees for completely mundane reasons — storm cleanup, construction, disease removal, firewood, somebody's yard finally getting redone. Thousands of trees. Every day. Most of the time it's exactly as boring as it sounds: cut, drop, haul, done. And then every so often, completely without warning, one of those ordinary trees turns out to be something else entirely. A tree that's been quietly filling itself with water for years, maybe decades, completely undetectable from the outside, sealed shut under bark that looks exactly like every other tree on the block. Nobody plans for that. Nobody sees it coming. That's exactly what makes it worth watching when it happens to be caught on camera. You already scrolled past the video once. Go back and actually watch what happens the second that bar breaks through. You will not believe how much comes out. And once you know why, you'll start looking at every old tree in your neighborhood a little differently. — Let's talk about the pressure numbers again, because I glossed over just how absurd they get in the most extreme documented cases. Standard atmospheric pressure at sea level is about 14.7 pounds per square inch. Some measured wetwood pockets have registered internal gas pressures multiple times higher than that — enough that when researchers insert a hollow probe to sample the gas, it doesn't calmly bubble out, it forces its way through with an audible hiss, sometimes strong enough to make a sound loud enough to hear from several feet away. Now picture that same pressure, except instead of a thin research probe, it's a chainsaw bar plowing straight through the wall of the pocket in one continuous motion. There's no controlled release valve. There's no slow bleed-off. The seal just fails all at once, and whatever's inside — water, gas, fermented bacterial slurry — takes the fastest path out, which is usually straight toward whoever is standing closest. That's not drama for the sake of drama. That's just fluid dynamics doing what fluid dynamics does when a pressurized container gets breached in one violent motion instead of a slow leak. — People love comparing this to other "trees doing things they shouldn't" phenomena, so let's run through a few, because it puts wetwood in context. Root pressure is a real, separately documented thing — some trees, particularly certain maples and grapevines, can generate enough internal pressure through osmosis alone to push water dozens of feet upward through their trunk with zero mechanical pump involved, which is part of why maple syrup tapping works in early spring: cut a hole, and sap doesn't just sit there, it actively flows out under real pressure. Bamboo, meanwhile, has hollow internal chambers between each node that can fill with water and, when punctured, release a surprising rush for something that looks like solid stalk from the outside. Certain cacti and succulents store such enormous internal water reserves that a single barrel cactus can hold multiple gallons, enough that desert survival guides have long described (with real caveats about bitterness and toxicity in some species) cutting into one as an emergency water source. None of those are the exact same mechanism as bacterial wetwood. But they all share the same core surprise: the outside of a plant tells you almost nothing about what's happening on the inside. Trees and plants in general are far better at hiding internal reservoirs, chambers, and pressure systems than most people ever consider, because we're trained from childhood to think of "wood" as uniformly solid and dry. — Here's a question I want you to actually think about instead of just scrolling past: why does this footage hit people so hard emotionally, when it's "just" water? I think it's because it breaks a category we didn't know we had. Somewhere in your brain, without ever being taught it explicitly, you built a rule: solid things don't have hidden liquid interiors. Rocks are solid. Wood is solid. A tree trunk, no matter how big, is filed under "solid object" right next to a brick or a fence post. So when a tree trunk suddenly behaves like a punctured water balloon, it's not just surprising — it's a small, harmless violation of a rule you didn't know you were relying on. That's the exact same psychological mechanism behind why people can't look away from videos of hidden compartments, false walls, geodes cracked open to reveal crystal interiors, or ice cores pulled from glaciers showing air bubbles thousands of years old. The object looked like one thing on the outside and turned out to be something completely different on the inside. Our brains are wired to lock onto that specific kind of surprise and replay it. — I want to walk through what's actually happening at a microscopic level too, because the bacteria part is honestly the wildest piece of this whole story and it usually gets skipped over. The bacteria responsible for wetwood are largely anaerobic — meaning they thrive specifically in environments with no oxygen, which describes the sealed interior of a heartwood pocket perfectly. Species commonly implicated include various strains that also show up in other low-oxygen fermentation processes elsewhere in nature. These bacteria essentially treat the interior of the tree the way yeast treats a sealed fermentation vessel: they break down wood sugars and cellulose components, and as a byproduct of that metabolic process, they release gas. Methane. Carbon dioxide. Sometimes hydrogen sulfide, which is the compound responsible for the "rotten egg" smell associated with some of the worst slime flux cases. Here's the part that should genuinely unsettle you a little: this process can continue, essentially undisturbed, for years. The bacteria don't need light. They don't need a food source refill from outside — the wood itself is the food source. They don't need anything from us at all. They just sit there, fermenting slowly, generation after generation, quietly filling an internal chamber with liquid and gas, completely indifferent to whatever's happening in the world outside the bark. Somebody could mow the lawn around that tree every single week for fifteen years and never once suspect that a private, self-sustaining microbial ecosystem is operating a few inches away, sealed inside solid wood. — Foresters have their own folklore around this too, separate from the old "wet-hearted tree" naming I mentioned earlier, and some of it is genuinely unsettling if you sit with it. There are accounts — some documented in forestry incident reports, some passed around as workplace stories among tree crews — of wetwood pockets releasing enough pressurized gas and liquid on impact to knock a chainsaw sideways out of the operator's hands, or to spray fluid several feet, catching a nearby coworker completely off guard. Tree removal is already one of the more dangerous manual trades that exists — statistically it's consistently ranked among the more hazardous occupations — and wetwood is one of those factors that experienced crews specifically train new hires to be aware of, precisely because it's invisible until the exact moment it isn't. Some crews have a rule: if you see that telltale dark wet staining running down bark from an old wound, you treat the cut differently. Different angle. Different bracing. A moment of hesitation most people watching a video would never think to expect from someone who cuts trees for a living every single day. That hesitation, when you see it, is not caution for no reason. It's caution earned from someone else's story about the day their trunk sprayed back. — Let's zoom out for a second and talk about why nature keeps doing this to us — hiding things in plain sight that overturn assumptions we didn't even know we were making. Geodes look like plain gray rocks from the outside and crack open into crystal cathedrals. Certain seemingly solid ice formations conceal air pockets and liquid water inside glacial ice that's been sealed for centuries. Some seeds remain dormant and viable inside dry-looking husks for years, sometimes decades, before conditions trigger germination. Nature is, on some fundamental level, extremely good at packaging surprising internal states inside boring, unremarkable exteriors, because there's rarely an evolutionary or physical reason for the outside of something to accurately advertise what's happening on the inside. A tree trunk covered in bark has absolutely no obligation to tell you what's going on underneath. And most of the time, honestly, there's nothing dramatic going on under there — it really is just solid wood, rings, sapwood doing its normal job. But every so often, under the right combination of an old wound, the right bacteria finding their way in, and years of undisturbed fermentation, you get this. A tree that's secretly been operating as a sealed, pressurized reservoir the entire time, waiting for someone with a saw to finally find out. — A few quick things people always ask once they learn about this, so let's knock them out here. Is the water safe to drink? Historically, some accounts describe it as drinkable in a pinch, but modern guidance is far more cautious — wetwood fluid is loaded with bacteria and fermentation byproducts, and depending on the tree and how advanced the infection is, it can range from relatively clean-tasting to genuinely foul and bacterially loaded. Not something to treat as a reliable water source by modern standards, whatever old logging stories might say. Does it kill the tree? Not necessarily, and that's part of what makes it so strange. Trees can live with wetwood for years, even decades, functioning normally from the outside — leafing out every spring, growing new rings — while quietly carrying an internal pocket the entire time. It's more of a chronic condition than an acute one in most cases, though severe cases can weaken the tree structurally and contribute to internal decay. Can you tell from the outside before cutting? Sometimes, if you know exactly what to look for — that dark staining running from an old wound is the main visible tell. But plenty of wetwood trees show no obvious external sign at all until the moment someone cuts into the wrong spot. — If you made it this far, you now know something about trees that the overwhelming majority of people who scroll past videos like this never bother to learn. You know the name of the phenomenon. You know the bacterial mechanism behind it. You know which species are most prone to it, why old wounds matter, how much pressure can actually build up inside, and why experienced tree crews still treat certain trunks with real caution. That's a strange amount of knowledge to walk away with from what looks, at first glance, like just another oddly satisfying clip. But that's usually how it goes with the genuinely wild stuff nature does — it looks small on the surface, and then you pull one thread and end up somewhere you didn't expect. Go watch it again with all of that in your head this time. Watch the exact frame where the bar breaks through. Watch what the water does the instant it has somewhere to go. Watch the reaction on the person holding the saw — that's not performance, that's genuine surprise from someone who has almost certainly done this exact job a thousand times before and never seen a tree do this. Some trees really are just wood, top to bottom, nothing hiding inside. And then there are the ones that have been quietly running their own private reservoir for twenty or thirty years, sealed under ordinary-looking bark, waiting for exactly one cut to finally let it out. You just watched what that looks like the moment it happens.

Earth Unveiled

103,596 görüntüleme • 6 gün önce

[eng trans] Gunil's 11-Minute Concert Ment at Summer Xcape 2026 🐹 hello, it's gunil. so, did something happen yesterday? firstly, i'd just like to share a few thoughts about how i felt during today's show. i'm always the type to talk for a long time, so i'm trying to be careful because i'm worried some of you might fall asleep. but if you want to sleep, that's okay. you have the freedom. 🐹 anyway, the thing i felt while performing today was that... honestly, i think yesterday we were all still a little shy around each other. i know some of you were here yesterday too. because of that, i was honestly really worried about today. ah, but still, we only had two days to begin with, so since this is the second and final day, we really have to enjoy ourselves and have fun without any regrets. i wanted Xdizzto have fun, and i wanted villains to have fun too. but i kept thinking, will that really work out? i was really worried about it a lot. 🐹 but the moment today's first performance started, you all welcomed us with such loud cheers that i think those worries just disappeared. and honestly, today, even when we made our silly jokes, you reacted so well. you cheered like this even when jooyeon was just tuning his guitar. ah, i'm really, truly grateful for that. so, in conclusion, i had a great time today. 🐹 i think it's almost been five years since our debut now, right? five calendar years, right? anyway, some time has passed, and while we've stood on countless stages during that time, i think yesterday and today, Xcape 2026, will remain one of those performances that i'll remember for a very long time. 🐹 today's concert was really fun. but when i think to myself whether that means it was a perfect performance... personally, i don't think so. while i was playing the drums and listening through my in-ear monitor, there were parts i felt like were lacking. and the more i perform, the more ideas i have about areas we can improve so we can make our concerts even more enjoyable. i've noticed a lot of those things myself, and found parts i wanted to improve. so yes, although today's concert was really fun, i won't let us become satisfied with just this. i want us to continue creating performances that are even more fun and have better quality. that's something i really wanted to tell all of you. 🐹 did you all have fun? you all traveled such a long way to get here. for a lot of people, yeongjongdo is actually pretty far away. so the fact that you came all the way here just to see xdiz, is really an act of love. thank you once again, from the bottom of my heart, for loving us so much and coming all this way to support us. i'm not crying. my nose isn't stuffed either. can you hear my sniffling? when i talk quietly, I don't think you can hear me. 🐹 anyway, along time ago, i made a promise to you all, didn't i? i said that xdiz would always be the kind of team that keeps simmering bone broth. [see reply for the context of his "real bone broth" ment] of course, if you eat bone broth every single day, eventually you might start doubting and think "is this really bone broth?" because you get so used to it. but i really cross my heart on this. i'll bet everything on this. without lying, i'll always give my absolute best. i think that's only natural. isn't it wrong to not give your best? 🐹 anyway, i hope you'll continue to believe in us. i hope you keep trusting xdiz. we'll also keep working hard so we can live up to that trust. i believe that precious relationships, as they get deeper, will have more crises/problems. because, well, think about your precious friends. or maybe a neighborhood friend you're close with. or a classmate you were incredibly close to. haven't there been incidents where suddenly that relationship becomes strained because of a crisis? but i believe that a crisis can become an opportunity. so even if there are any of you who may have doubted us, i want to use that as an opportunity to keep proving ourselves to you. 🐹 i hope you know that we're never the kind of people, or the kind of team, that would carelessly take you for granted or treat your love half-heartedly. and i'm so grateful that there are far more people who don't think that way. we really love you all so much. we'll keep talking together after every show, giving each other feedback among ourselves, adressing the areas we fell short on today, and working hard to show you performances that are even more fun and with higher quality. 🐹 oh, right. earlier, when i talked about that promise while mentioning the bone broth, there was something else i said back then too. do you remember me saying the bigger this group gets, as more and more new villains join us, i mentioned that i was afraid some of you may leave so i said i wanted to protect all of you no matter what. nobody actually says things like "what will you protect? protect yourself first." but i think you all understand what i feel. 🐹 honestly, every single one of you is genuinely precious to me. whether there's just one villain or 200,000 villains, you're all still villains. but as our fandom keeps growing, it naturally starts feeling like one huge group. so because of that, i think we might stop feeling like we're seen as an individual person anymore. once again, what i want to tell you here is that every single piece of love that each of you sends us is incredibly precious. really. every single one of you. everyone here, from zone 1 all the way to zone 7000 is so incredibly precious to us. 🐹 when one person comes together... ah no, not just one person. when one person, then another person come together, sometimes they become ten thousand people. that's how it goes, doesn't it? 🐹 anyway, you all know the song "one candle", right? oh, i'm sorry. this is really the last one... actually, you all know i'm a tmi talker. you know, a too much talker. so for a while, i've been telling myself, "ah, i need to restrain myself" and holding back but it's been a while, so, i'll loosen up my mouth a bit more. 🐹 i really love the song "one candle" it talks about how when one candle joins another, then another, and so on, they become one really great light. you are every single one of those lights. when you're standing alone, in a way, you might sometimes feel insignificant. but truly, every one of you is not insignificant. not at all. 🐹 we will become xdiz that grows by constantly reflecting on ourselves, growing through self-reflection, and will never lose our humility so we can become a team that doesn't feel insignificant even if there's just one of us, and even if there were only one of you, we'd still give everything we have until the very end. we would be really grateful if you'll keep believing in us until the very end. and i'll keep believing in our villains until the very end too. thank you. 🐹 also, wasn't this concert amazing? the drums came down from the sky. the instruments came down too. so many incredible things prepared for this show, but this concert couldn't have happened through our efforts alone. there are so many staff members working behind the scenes, and honestly, i think they worked even harder than we did. please give our staff a huge round of applause. and finally, villains, please give yourselves a round of applause too.

ten

33,967 görüntüleme • 3 ay önce

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.

Jeffrey Emanuel

25,483 görüntüleme • 8 ay önce