Podcasts about SLA

Neste episódio do Vamos de Vendas, exploramos o crescimento da função de SDRs (Sales Development Representatives) no Brasil e o impacto dessa transformação na estrutura comercial das empresas B2B. Para essa conversa, recebemos Maucir Nascimento, especialista em vendas, estruturação de times e geração de demanda, que tem acompanhado de perto a evolução dessa função nos últimos anos.Com ampla experiência em tecnologia e vendas, Maucir compartilha uma visão estratégica sobre como os SDRs deixaram de ser vistos como meros auxiliares e se tornaram protagonistas na previsibilidade e escala das operações comerciais. Ele revela os bastidores da formação de equipes de alta performance, os desafios culturais do mercado brasileiro e os impactos da adoção de tecnologias como IA generativa e CRM na rotina desses profissionais.

Invitée : Lorène Vivier, autrice - témoignage  La maladie de Charcot donne entre trois et cinq ans dʹespérance de vie dʹaprès tous les spécialistes. " C'est absurde ! Il en sera autrement " a décrété Lorène Vivier âgée de 35 ans au moment du diagnostic. Son témoignage est bouleversant, drôle et inspirant. Il dit son combat quotidien entre espoir, résilience et engagement pour faire avancer la recherche autour de la SLA. Lorène nous invite à célébrer la vie et à ne jamais renoncer. Son parcours est un message puissant dʹoptimisme et de détermination. Lorène Vivier : " La vie est belle, essaie-la " Editions Tredaniel

In the corner of the ICU, on multiple pressors, distended, oliguric, and intubated you'll find the necrotizing pancreatitis patient. Sounds intimidating, but with the persistence, patience, and the proper care these patients can make it! In this episode from the HPB team at Behind the Knife listen in as we discuss the Step-Up approach, when to surgically intervene, various approaches to pancreatic Necrosectomy, and additional aspects of the multidisciplinary care required for the successful treatment of necrotizing pancreatitis.  Hosts Anish J. Jain MD (@anishjayjain) is a current PGY3 General Surgery Resident at Stanford University and a former T32 Research Fellow at the University of Texas MD Anderson Cancer Center. Jon M. Harrison is a 2nd year HPB Surgery Fellow at Stanford University. He will be joining as faculty at the Massachusetts General Hospital in Boston, MA at the conclusion of his fellowship in July 2024.    Learning Objectives ·      Develop an understanding of the severity of necrotizing pancreatitis and the proper indications to surgical intervene on this often-tenuous patients.  ·      Develop an understanding of the Step-Up approach and key aspects (reimaging, clinical status, physiologic status, etc.) that determine when to “step-up” treatment for patients with necrotizing pancreatitis. ·      Develop an understanding of long term sequalae and complications associated with necrotizing pancreatitis and operative management ·      Develop an understanding of multidisciplinary care and long-term follow-up necessary for adequate treatment of patients suffering from necrotizing pancreatitis. Suggested Reading Maurer LR, Fagenholz PJ. Contemporary Surgical Management of Pancreatic Necrosis. JAMA Surg. 2023;158(1):81–88. doi:10.1001/jamasurg.2022.5695 https://pubmed.ncbi.nlm.nih.gov/36383374/ Harrison JM, Day H, Arnow K, Ngongoni RF, Joseph A, Aldridge T, Wheeler KJ, DeLong JC, Bergquist JR, Worth PJ, Dua MM, Friedland S, Park W, Eldika S, Hwang JH, Visser BC. What's Behind it all: A Retrospective Cohort Study of Retrogastric Pancreatic Necrosis Management. Ann Surg. 2024 Sep 3. doi: 10.1097/SLA.0000000000006521. https://pubmed.ncbi.nlm.nih.gov/39225420/ Harrison JM, Visser BC. Not Dead Yet: Managing the Abdominal Catastrophe in Necrotizing Pancreatitis. Pancreas. 2025 May 20. doi: 10.1097/MPA.0000000000002512. https://pubmed.ncbi.nlm.nih.gov/40388698/ Harrison JM, Li AY, Sceats LA, Bergquist JR, Dua MM, Visser BC. Two-Port Minimally Invasive Nephrolaparoscopic Retroperitoneal Debridement for Pancreatic Necrosis. J Am Coll Surg. 2024 Dec 1;239(6):e7-e12. doi: 10.1097/XCS.0000000000001152. https://pubmed.ncbi.nlm.nih.gov/39051721/ van Santvoort HC, Besselink MG, Bakker OJ, Hofker HS, Boermeester MA, Dejong CH, van Goor H, Schaapherder AF, van Eijck CH, Bollen TL, van Ramshorst B, Nieuwenhuijs VB, Timmer R, Laméris JS, Kruyt PM, Manusama ER, van der Harst E, van der Schelling GP, Karsten T, Hesselink EJ, van Laarhoven CJ, Rosman C, Bosscha K, de Wit RJ, Houdijk AP, van Leeuwen MS, Buskens E, Gooszen HG; Dutch Pancreatitis Study Group. A step-up approach or open necrosectomy for necrotizing pancreatitis. N Engl J Med. 2010 Apr 22;362(16):1491-502. doi: 10.1056/NEJMoa0908821. https://pubmed.ncbi.nlm.nih.gov/20410514/ Bang JY, Arnoletti JP, Holt BA, Sutton B, Hasan MK, Navaneethan U, Feranec N, Wilcox CM, Tharian B, Hawes RH, Varadarajulu S. An Endoscopic Transluminal Approach, Compared With Minimally Invasive Surgery, Reduces Complications and Costs for Patients With Necrotizing Pancreatitis. Gastroenterology. 2019 Mar;156(4):1027-1040.e3. doi: 10.1053/j.gastro.2018.11.031. https://pubmed.ncbi.nlm.nih.gov/30452918/ Zyromski NJ, Nakeeb A, House MG, Jester AL. Transgastric Pancreatic Necrosectomy: How I Do It. J Gastrointest Surg. 2016 Feb;20(2):445-9. doi: 10.1007/s11605-015-3058-y. https://pubmed.ncbi.nlm.nih.gov/26691148/ Please visit https://behindtheknife.org to access other high-yield surgical education podcasts, videos and more.   If you liked this episode, check out our recent episodes here: https://app.behindtheknife.org/listen

Forty years after the Patty Hearst "trial of the century", people still don't know the true story of the events. Revolution's End fully explains the most famous kidnapping in US history, detailing Patty Hearst's relationship with Donald DeFreeze, known as Cinque, the head of the Symbionese Liberation Army. Not only did the heiress have a sexual relationship with DeFreeze while he was imprisoned, she didn't know he was an informant and a victim of prison behavior modification. Neither Hearst nor the white radicals who followed DeFreeze realized that he was molded by a CIA officer and allowed to escape, thanks to collusion with the California Department of Corrections. DeFreeze's secret mission: infiltrate and discredit Bay Area antiwar radicals and the Black Panther Party, the nexus of 70s activism. When the murder of the first black Oakland schools' superintendent failed to create an insurrection, DeFreeze was alienated from his controllers and, his life in jeopardy, decided to become a legitimate revolutionary. Revolution's End finally elucidates the complex relationship of Hearst and DeFreeze and proves that the largest shoot-out in US history, which killed six members of the SLA in South Central Los Angeles, ended when the LAPD purposely set fire to the house and incinerated those six radicals on live television, nationwide, as a warning to American leftists.Become a supporter of this podcast: https://www.spreaker.com/podcast/the-opperman-report--1198501/support.

Lorène Vivier pourrait être notre sœur, notre amie, notre voisine… Elle est une jeune femme pleine de vie, éprise de liberté, passionnée par les voyages, la beauté, les parfums, la musique et la danse. Lorène Vivier offre un témoignage bouleversant. Celui d'une vie qui pourrait paraître ordinaire, et qui devient une extraordinaire aventure. Celle de transmettre sa passion de vivre chaque instant avec une joie et une intensité impressionnantes. Tel est le choix de vie de Lorène, et sa manière de répondre à la grave maladie qui lui a été diagnostiquée il y a trois ans. Depuis, entourée de ses proches, elle réussit à rassembler de plus en plus de monde dans son combat, pour que sa maladie soit mieux connue et pour faire avancer la recherche médicale. Lorène n'a aucun doute que le traitement pour guérir de la sclérose latérale amyotrophique (SLA), plus connue sous le nom de maladie de Charcot, sera bientôt trouvé. Aujourd'hui, elle nous invite à l'aider dans cette course contre le temps, pour qu'elle puisse enfin être soignée et guérie comme toutes les autres personnes atteintes comme elle.    Lorène confie à quel point c'est grâce à ses croyances et à son recours à la vie spirituelle qu'elle trouve la force et la joie de vivre, de combattre et de rayonner. La beauté de son témoignage d'amour est un cadeau magnifique, pour guérir de toutes les peurs et de toutes les souffrances. Un hymne à la vie, à l'amour et à notre merveilleuse humanité. Pour lire La vie est belle, essaie-la !, le livre de Lorène Vivier, cliquer ici. --------------      Pour découvrir le compte Instagram de Lorène Vivier, cliquer ici. --------------      Pour découvrir l'Association pour la Recherche sur la Sclérose Latérale Amyotrophique (ARSLA) et lui faire un don, cliquer ici. Pour Lorène  Chers amis, chers auditeurs de Zeteo, La rencontre avec Lorène que nous vous proposons aujourd'hui est bouleversante. Il y a en elle une exaltation de la vie et de l'instant présent qui valent plus que des millions d'enseignements. La passion de la vie et la joie qui habitent Lorène ne doivent pas cacher le combat qu'elle mène avec tant de courage et de détermination. Lorène est engagée dans une course contre le temps. Il faut donner à la recherche les moyens indispensables pour qu'elle trouve enfin le traitement qui permettra de soigner et surtout de guérir ceux qui, comme elle, sont frappés par la sclérose latérale amyotrophique (SLA), plus communément appelée maladie de Charcot. Nous vous appelons à faire un don défiscalisable au profit de l'ARSLA, première association en France à lutter contre la SLA, et dont Lorène est l'une des grandes figures. Le lien pour vous rendre sur le site de l'ARSLA est disponible en dessus de ce texte, ou en cliquant ici. D'avance, nous vous remercions infiniment pour votre geste !   Fraternellement, Guillaume Devoud  ________________________ Pour soutenir Zeteo, podcast diffusé entièrement gratuitement Pour faire un don, il suffit de cliquer ici pour aller sur notre compte de paiement de dons en ligne sécurisé par HelloAsso. Ou de cliquer ici pour aller sur notre compte Paypal. Vos dons sont défiscalisables à hauteur de 66% : par exemple, un don de 50€ ne coûte en réalité que 17€. Le reçu fiscal est généré automatiquement et immédiatement à tous ceux qui passent par la plateforme de paiement sécurisé en ligne de HelloAsso Nous délivrons directement un reçu fiscal à tous ceux qui effectuent un paiement autrement (Paypal, chèque à l'association Telio, 116 boulevard Suchet, 75016 Paris – virement : nous écrire à info@zeteo.fr ).   Pour lire d'autres messages de nos auditeurs : cliquer ici. Pour en savoir plus au sujet de Zeteo, cliquer ici. Pour en savoir plus au sujet de Bethesda, cliquer ici. Pour en savoir plus au sujet de Telio, cliquer ici. Pour lire les messages de nos auditeurs, cliquer ici. Nous contacter : contact@zeteo.fr Proposer votre témoignage ou celui d'un proche : temoignage@zeteo.fr

Une plongée dans l'univers de l'industrie musicale antillaise. C'est ce que nous propose le réalisateur Julien Dalle, avec la série Wish. A l'affiche, des acteurs de talent comme Firmine Richard. La bande son, avec la voix d'artistes comme Thierry Cham ou Slaï, transporte le spectateur de son canapé aux Antilles. Note vocale : Matthieu Barthélémy, fondateur du Do you remember festival qui aura lieu à Taverny (95) du 4 au 6 juillet. Pour visionner les clips, cliquez sur les titres des chansons :  Singuila - On fait comment Dj Kawest et Aya Nakamura - Chouchou Jean-Philippe Martelly et Thierry Benoit - Nou Collectif Wish - Heriraj Wish Eternal - Stay Ophélie Winter - Dieu m'a donné la foi Khadja Nin - Sambolera Mayi Son Retrouvez notre playlist sur Deezer. 

Naudoti automobiliai ir toliau išlieka populiaresni nei nauji automobiliai ar juo labiau elektromobiliai. Tačiau dalis vairuotojų vis dar gana dažnai būna apgauti – už automobilį sumoka per daug, nusiperka daužtą ar su suklastota rida. Kaip jums sekasi įsigyti naudotą automobilį?Muzikos pasaulyje vis labiau įsitvirtina nauja muzikos grupė „THEMA“. Ši grupė susibūrė prieš metus visiškai netikėtai, kai dar tuomet studentė Milda Bertašiūtė Vilniuje stovykloje, kurioje dirbo, sutiko du moksleivius krepšininkus iš Jonavos – Adą Giedraitį ir Paulių Jankauską.Šeimai turi būti leista oriai atsisveikinti su ligoninėje mirštančiu artimuoju, sako Seimo kontrolierė Erika Leonaitė. Tyrimą atlikusi kontrolierė nustatė, kad šiuo metu nėra teisės akto, kuris įpareigotų visas gydymo įstaigas nustatyti tvarką, leidžiančią mirštančiam asmeniui ir jo artimiesiems oriai atsisveikinti. Kaip turėtų atrodyti orus atsisveikinimas su ligoninėje mirštančiu artimuoju?Antys bėgikės, stručiai, povai, fazanai, dekoratyviniai balandžiai – Birutės Slažinskienės hobis ir rūpestis, kai lieka laiko nuo darbų uogų auginimo šeimos ūkyje. Radviliškio rajone Mandeikių kaime savo sodyboje įrengtame voljere visi dekoratyviniai paukščiai gyvena darniai.Ved. Edvardas Kubilius

Lorène Vivier… Ce nom vous parle ?L'histoire de Lorène est venue me toucher il y a quelques semaines en la découvrant un samedi soir dans l'émission « Quelle Epoque ! » puis en découvrant son livre et son combat à travers un documentaire produit par Caroline Delage et « Au Tableau Production ! ».Diagnostiquée à 35 ans d'une SLA (maladie de Charcot), cette jeune femme combattive m'a touché profondément et j'ai décidé de soutenir sa cause.Dans l'épisode que vous retrouvez en ce 21 juin (journée internationale de la SLA), vous allez pouvoir découvrir Lorène et son combat, la chanson que je lui ai dédiée et l'opération « Eclats de Juin » (je me trompe dans l'appellation de l'opération dans mon introduction, pardon pour mon erreur) qui doit permettre de réunir de l'argent pour soutenir les chercheurs qui doivent trouver un remède pour Lorène et tous les malades de la SLA (environ 4 000 par an).   A retrouver :·       L'Instagram de Lorène et de son combat contre la SLA : https://www.instagram.com/lavieestbelle_sla/?hl=fr·       Page concernant Lorène Vivier sur le site de son éditeur Guy Trédaniel : https://www.editions-tredaniel.com/lorene-vivier-auteur-6505.html·       Ma page de dons sur Eclatsdejuin.arsla.org si vous voulez aider et faire péter les compteurs : https://eclatsdejuin.arsla.org/fundraisers/gerardkleczewskiclech·       Le lien pour acquérir mon recueil de chansons « Les Chansons sont des papillons » sur Amazon  (1,50€ reversé par exemplaire à l'association): https://www.amazon.fr/chansons-sont-papillons-Chansons-l%C3%A2ge/dp/B0F8VXTCP5/ref=sr_1_1Bonne écoute et mobilisez-vous !GérardRetrouvez ces interviews sur toutes les plateformes de podcast, sur YouTube, ainsi que sur Instagram (@bla.bla.lebonheurlesautres)et Facebook (https://www.facebook.com/Lebonheurcestlesautres).Hébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠⁠⁠⁠⁠⁠⁠https://www.lovelightsofia.com/selflovechallenge2025⁠⁠⁠⁠⁠⁠⁠SELF LOVE Academy(SLA)の詳細 ＆ Waitlistはこちらから→https://www.lovelightsofia.com/selfloveacademy無料インナーチャイルド瞑想：⁠⁠⁠⁠⁠⁠⁠https://lovelightsofia.activehosted.com/f/1⁠1:05~-ゲスト紹介1:40~-SLAに入ったきっかけ・悩んでいたこと3:15~-SLA入った時、どんな悩みがありましたか？SLAに入ったきっかけ3:45~-SLA以前は、どんな思考・感情のパターンがありましたか？4:38~-SLAに入ろうと決めた時どんな気持ちでしたか？5:50~-実際にSLAに入ってみてどうでしたか？（プログラム・サポート・学び）7:00~-ネガティブのお掃除・過去引きずっていることをワークで解決8:05~-SLAは義務教育で知りたかった9:00~-落とし込み・体現しやすい環境とは？成功確率が高い環境とは？10:10~-SLAのFacebookコミュニティについて思うこと10:36~-SLAを受講して、以前と変わったと思うことは？13:50~-SLAに興味があるけれど、悩んでいる方へ伝えたいこと

Star Link Communication is revolutionizing workforce management by offering AI-powered facial recognition systems to eliminate proxy attendance and ensure data accuracy. To support a smooth upgrade from outdated fingerprint systems, the company provides buyback options.Responding to client feedback, Star Link has enhanced device durability with reinforced designs, making them ideal for industrial use. The company also ensures seamless nationwide support through a network of 70+ engineers, a structured SLA system, and a transparent escalation matrix.Its Canteen Management System has been optimized for stability and remote monitoring via the cloud. The Visitor Management System (VMS) now integrates smoothly with HRMS platforms, enabling real-time visitor control and data synchronization.A standout feature is Shift Masking, which restricts attendance to assigned shifts and supports shift-wise bonuses. Combined with cloud-hosted Time & Attendance software, Star Link simplifies leave tracking, overtime, and payroll integration.With over 25 years of expertise, Star Link is more than a device provider — it's a trusted technology partner, committed to building secure, efficient, and transparent workplaces.

Dining out on acronymsWe use abbreviations every day - in writing, texting, note-taking, talking and, of course, in paymentsThere are a few different categories of abbreviations, and acronyms is one of themWhen you shorten a phrase by using just the first letter of each word and then pronounce it as a new word, you're using an acronymPayments aficionados often dine out on acronyms with the first letters often replacing the full phraseIt's been a while since Direct Debits were processed by Bankers Automated Clearing Services or you purchased your house with a payment sent via the Clearing House Automated Payment ServiceIt has been many years since both Bacs and CHAPS entered our vocabulary as clear derivations of long established payment scheme namesBack in 2006/7 a name was needed for a new kid on the payments blockIt was time to invent a name for the near real time payment system scheduled for introduction by the UK banks in May 2008.Today's global payments naming convention would have led to this new payment type to be christened Instant Payments but 2006/7 was a long time ago and, as a deferred net settlement or Near Real Time system with a SLA time of 2 hours perhaps an “instant” moniker would not have been appropriate.For a time it looked like the new payment type might be called Immediate Payments but if “instant” didn't work then it was unlikely that “immediate” would either. Also, an additional complication that was that Immediate Payments Limited wasn't a company that the Payment System Operator (at the time CHAPS Clearing Company Limited) owned.So with a distinct lack of creative innovation we ended up with a Faster Payment and an acronym of FPS - with the “S” being interchangeable between Service, System and Scheme!Today, we all know Faster Payments (and don't really care about what the “S” stands for) but did you know that, in 2008, the UK nearly ended up with what was referred to as a Scandinavian model designed to deliver a “same day Bacs1”?The term “Swedish model” is referred to as the special institutional arrangements of a society that is sometimes described as a middle way between capitalism and socialism.In the second half of the first decade of the 2000's a different type of Swedish model was about to take centre stage for the “same day Bacs” payment type slated for launch in May 2008.In response to the demand for a “same day Bacs” payment by Payment Systems Task Force set up by the Office of Fair Trading (OFT) the industry initially offered ELLE(Early for Late and Late for Early) where a payment submitted by midday would be delivered by close of business that day and one submitted after midday would be delivered by midday the next day.However, in December 2005 the Payment Systems Task Force accepted an APACS2recommendation for a still more ambitious target on payment times to ensure access to funds within a couple of hours of any payment being made, and allowing payments to be sent 24 hours a day, 7 days a week, to be available by November 2007 (later amended to May 2008).With the ELLE acronym ceasing to be relevant and naming options including instant and immediate not really working the industry opted for the easy option of a Faster (than Bacs) Payment - along with three variations of “S”.And the rest, they say, is history - interestingly despite the “couple of hours” translating into a two hour SLA the Faster Payment Scheme has actually delivered an instant or immediate transfer of funds between the remitter and the beneficiary (albeit with a deferred net settlement happening in the background) so, perhaps, an instant payments moniker could have been used instead of defaulting to a Faster (than what?) Payment.Whilst the naming convention may leave a lot to be desired we should be thankful that sense prevailed and the “same day Bacs” design chosen was the Faster Payments Scheme / Service / System that we have enjoyed for the last 15 years - the UK would have been mush poorer with Elle.

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠https://www.lovelightsofia.com/selflovechallenge2025⁠SELF LOVE Academy(SLA)の詳細 ＆ Waitlistはこちらから→https://www.lovelightsofia.com/selfloveacademy無料インナーチャイルド瞑想：⁠https://lovelightsofia.activehosted.com/f/1⁠1:05~-ゲスト紹介1:40~-SLAに入ったきっかけ3:15~-SLAに入るにあたり、悩んだことはありますか？4:00~-SLAに入ってみてどうでしたか？4:45~-SLAにいるだけで心が強くなれる理由（Liveセッション・自己投資）5:40~-人生ダウンした時に必要なものとは7:12~-SLAのFacebookコミュニティもお気に入り7:28~-SLAのプログラムやワークが役立っていること（過去の振り返り・インナーチャイルドの癒し）9:45~-私たちは、過去を引きずっている10:05~-SLAのワークで、意外なあの人に許しを与えられた時11:20~-過去に対する怒り、悲しみ、恨みを持ち続けていると、、12:10~-SLAを受講する前、自分自身に対して思っていたこと・受講後の変化（周りに優しいけど自分に厳しい・Good girlでなくてはいけない・怒りを感じてもいい）14:20~-SLAを始めて、怒りを感じた？自分の怒りをリリースすること16:03~-パートナーシップの変化16:25~-SLAを始めて人生・パートナーシップ・人間関係で感じた良い変化は？19:45~-SLAに興味があるけれど、悩んでいる方へ伝えたいこと

Středověká architektura Ondřeje Slačálka odjakživa fascinovala. Tvrz Malešov poznal už jako dítě, když bydlel v Kutné Hoře. Jako mladý odešel studovat do zahraničí, ale když se vrátil, naplno se v něm probudila vášeň pro historii a zatoužil kousek jí vlastnit. Chvíli se rozhlížel po celé naší zemi, ale nakonec se vrátil do rodného kraje. Tvrz Malešov koupil v roce 2002, když mu bylo sedmadvacet let. Dlouhých patnáct let pak s rodinou a přáteli věnoval její obnově.

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠https://www.lovelightsofia.com/selflovechallenge2025⁠SELF LOVE Academy(SLA)の詳細 ＆ Waitlistはこちらから→https://www.lovelightsofia.com/selfloveacademy無料インナーチャイルド瞑想：⁠https://lovelightsofia.activehosted.com/f/1⁠1:05~-ゲスト紹介1:55~-The SELF LOVE Academy(以下SLA）に入る前は、どんなことに悩んで、SLAに入校を決めた理由3:00~-人の目が気になることは、自分の人生でどうマイナスだった？3:55~-どんな時にSofiaを知り、SLAに入ろうと決めましたか？5:10~-実際SLAに入ってみて（カリキュラム・コミュニティなど）6:35~-SLAのコミュニティへの在籍を継続している理由は？8:00~-SLAのコミュニティについて9:00~-SLAに入って変化したことについて10:00~-SLAをやってみたいけれど、悩んでいる人へ贈りたい言葉11:35~-SLAに入って、自然にできる様になったセルフラブなアクションとは？

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠⁠⁠⁠⁠⁠https://www.lovelightsofia.com/selflovechallenge2025⁠⁠⁠⁠⁠⁠SELF LOVE Academy(SLA)の詳細 ＆ Waitlistはこちらから→https://www.lovelightsofia.com/selfloveacademy無料インナーチャイルド瞑想：⁠https://lovelightsofia.activehosted.com/f/1⁠奈津子さんのインスタ： ⁠https://www.instagram.com/natsuko_mt/?hl=ja⁠1:05~-ゲスト紹介1:40~-SLAに入ったきっかけ・Sofiaを知ったきっかけ6:23~-SLAに入ってみてどうでしたか？6:55~-SLAに入って変化したことについて（ワーク・マインドセット）7:52~-独立に大切なこと、９割はマインドセット8:42~-セルフラブは、エンパワーメント♡9:50~-コーチを選ぶ時に大切なこと12:20~-SLAに入って変化した良いこと Part2 （人間関係・自分関係）15:10~-慈悲の気持ち・他人の背景を思いやることの大切さ Part.117:07~-幸せな気持ちで人生ポジティブに生きるための捉え方・考え方の工夫18:40~-何を信じているか？が私たちのエネルギーを作っている19:50~-慈悲の気持ち・他人の背景を思いやることの大切さ Part.221:40~-エゴを手放し、慈悲の気持ちを持つ練習と習慣化22:23~-SLAの多岐に渡るワークについて（自分のフェーズに合った練習ができる）23:10~-SLAが気になっている方へ贈りたい言葉24:15~-セルフラブコーチとして想うこと・Sofiaが先日、日本に一時帰国した時に思ったこと

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠https://www.lovelightsofia.com/selflovechallenge2025⁠SELF LOVE Academy(SLA)の詳細 ＆ Waitlistはこちらから→https://www.lovelightsofia.com/selfloveacademy無料インナーチャイルド瞑想：⁠https://lovelightsofia.activehosted.com/f/1⁠1:05~-ゲスト紹介1:32~-SLAに参加する前、どの様なことで悩んでいましたか？2:37~-SLAに参加しようと思った決め手は？不安はあった？4:00~-実際SLAに入ってみて（SLAのプログラム・コミュニティについて）8:38~-SLAランチ会で実際にお会いしてみて9:20~-特に印象に残っているSLAのセッションやワークは？11:11~-感情処理セッションについて12:52~-SLAに入ってから感じた変化とは14:15~-SLAは引き寄せ体質になる！その理由17:10~-自己投資することへの不安に感じている人に伝えたいこと20:20~-外側を変えるには、まずは内側から変わろう！本質的で持続的な変化は、内側を変えることが大切22:35~-SLAに入ってみたいけれど悩んでいる方に伝えたいこと24:41~-過去15年多岐に渡り投資したSofiaからのメッセージ27:13~-記美恵さんにとって、最近のセルフラブとは？

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠⁠⁠⁠https://www.lovelightsofia.com/selflovechallenge2025⁠⁠⁠⁠次期募集SLAウェイトリスト：⁠https://www.lovelightsofia.com/selfloveacademy⁠無料インナーチャイルド瞑想：⁠⁠⁠⁠https://lovelightsofia.activehosted.com/f/1⁠

"First day, worst day, every day — that's what we're built for." — Patrick Quirk, President & GM, Opengear At Cisco Live 2025 in San Diego, Patrick Quirk, President and General Manager of Opengear, joined Technology Reseller News publisher Doug Green to unveil a major innovation in network resilience: Opengear's new Foundational Support platform. Designed to meet the growing demands of increasingly complex, high-density network environments, the SLA-backed solution debuts as part of Opengear's commitment to full-lifecycle customer support. “It's not just about selling equipment,” said Quirk. “It's about walking with the customer through every stage of the network's lifecycle — from deployment to daily operations to disaster recovery.” A long-standing Cisco partner, Opengear has evolved from traditional console servers to a critical infrastructure provider, helping companies maintain uptime in an era where milliseconds matter — especially amid today's AI-driven network traffic spikes. “Outages aren't just inconvenient,” Quirk noted. “They're expensive. We're seeing potential losses of $21,000 per minute during downtime.” Opengear's edge? Out-of-band management. Unlike in-band VLAN control planes, which can be compromised during incidents or overloaded by data traffic, out-of-band infrastructure operates on a completely separate path. This architecture allows for immediate network visibility and control during even the worst disruptions, such as fiber cuts or cyberattacks. Supporting both operational and compliance objectives, Opengear enables organizations to maintain certifications like ISO, SOC 2, and NIST. “We're the wrapper around your network,” said Quirk, emphasizing the company's ability to enforce security and governance alongside performance. The conversation also spotlighted Opengear's recent AI-focused global research, which found a “lens gap” between network engineers and the C-suite. While both groups recognize AI's potential, engineers view it as a productivity tool, whereas executives prioritize compliance and customer value. “There's alignment,” Quirk said. “It just needs more conversation.” At Cisco Live, Opengear is exhibiting at booth 4324 and hosting sessions on topics like agentic AI and network strategy. More details are available at opengear.com.

[GRAINE DE METAMORPHOSE] Xavier Pitois reçoit Lorène Vivier, 37 ans, atteinte de Sclérose Latérale Amyotrophique (SLA) ou maladie de Charcot. Comment continue-t-on à avancer quand le corps lâche ? Que fait-on du temps, quand l'avenir se rétrécit ? Et comment transforme-t-on un diagnostic bouleversant en énergie d'action, pour soi, mais aussi pour les autres ? Lorène Vivier a choisi de faire de son quotidien un engagement : sensibiliser, témoigner, mobiliser. Une réflexion profonde sur le sens de la vie. Épisode #127Quelques citations du podcast avec Lorène Vivier :"On est en 2925, on va sur Mars, on ne peut toujours pas aller investiguer le système neurologique du corps humain.""Je n'ai plus envie de ramener du chiffre d'affaires, j'ai envie de ramener de l'argent pour la recherche, pour moi c'est ça le plus important.""C'est important de vivre pleinement les choses aujourd'hui."Thèmes abordés lors du podcast avec Lorène Vivier :00:00 Introduction03:22 Les origines du livre de Lorène Vivier06:47 L'importance de parler de la SLA07:16 Qu'est-ce que la maladie de Charcot ou SLA ?09:02 L'annonce de la maladie14:20 Les phrases qui apaisent16:38 La phase de lutte19:38 Le sens de l'engagement associatif22:04 Recherche et moyens financiers23:16 L'importance d'impliquer les entreprises25:10 Le goût du voyage26:27 La spiritualité : un vrai soutien30:05 Maladie progressive et sens de la vie32:14 Les aménagements au quotidien33:44 Comment aider ?34:51 Le regard des autres36:39 Le rapport au corps38:52 Les deux experts indispensables39:20 La place des aidants et de la famille41:28 Mettre en lumière la maladieAvant-propos et précautions à l'écoute du podcast Découvrez Objectif Métamorphose, notre programme en 12 étapes pour partir à la rencontre de soi-même.Recevez chaque semaine l'inspirante newsletter Métamorphose par Anne GhesquièreFaites le TEST gratuit de La Roue Métamorphose avec 9 piliers de votre vie !Suivez nos RS : Insta, Facebook & TikTokAbonnez-vous sur Apple Podcast / Spotify / Deezer / CastBox/ YoutubeSoutenez Métamorphose en rejoignant la Tribu MétamorphosePhoto © Christophe Martin Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

In this episode, Chris Lehmann, founding principal and CEO of Science Leadership Academy schools, shares his compelling journey from a shy English teacher to a pioneer of the "school 2.0 movement." Discover how SLA embodies an inquiry-driven pedagogy where students actively ask questions, research, collaborate, and present their learning, fostering an environment where technology is as essential and unnoticed as oxygen.Science Leadership Academy, inquiry-driven, project-based school in Philadelphia, PAInquiry Schools, non-profit dedicated to modernizing learning experiencesBuilding School 2.0: How to Create the Schools We Need, book by Chris Lehman, Zac ChasePractical Theory - A View From the Schoolhouse, blog from Chris LehmanEducon,an educational innovation conference where people can come together to discuss the future and the now of schoolsTed Sizer (educational philosophy)Deborah Meier (educator)Ann Cook (educator)Understanding by Design (UbD)Chubbies Steaks (Roxborough, Philadelphia)Jim's Steaks (South Street, Philadelphia)D'Alessandro's Steaks (Roxborough, Philadelphia)

[GRAINE DE METAMORPHOSE] Xavier Pitois reçoit Lorène Vivier, 37 ans, atteinte de Sclérose Latérale Amyotrophique (SLA) ou maladie de Charcot. Comment continue-t-on à avancer quand le corps lâche ? Que fait-on du temps, quand l'avenir se rétrécit ? Et comment transforme-t-on un diagnostic bouleversant en énergie d'action, pour soi, mais aussi pour les autres ? Lorène Vivier a choisi de faire de son quotidien un engagement : sensibiliser, témoigner, mobiliser. Une réflexion profonde sur le sens de la vie. Épisode #127Quelques citations du podcast avec Lorène Vivier :"On est en 2925, on va sur Mars, on ne peut toujours pas aller investiguer le système neurologique du corps humain.""Je n'ai plus envie de ramener du chiffre d'affaires, j'ai envie de ramener de l'argent pour la recherche, pour moi c'est ça le plus important.""C'est important de vivre pleinement les choses aujourd'hui."Thèmes abordés lors du podcast avec Lorène Vivier :00:00 Introduction03:22 Les origines du livre de Lorène Vivier06:47 L'importance de parler de la SLA07:16 Qu'est-ce que la maladie de Charcot ou SLA ?09:02 L'annonce de la maladie14:20 Les phrases qui apaisent16:38 La phase de lutte19:38 Le sens de l'engagement associatif22:04 Recherche et moyens financiers23:16 L'importance d'impliquer les entreprises25:10 Le goût du voyage26:27 La spiritualité : un vrai soutien30:05 Maladie progressive et sens de la vie32:14 Les aménagements au quotidien33:44 Comment aider ?34:51 Le regard des autres36:39 Le rapport au corps38:52 Les deux experts indispensables39:20 La place des aidants et de la famille41:28 Mettre en lumière la maladieAvant-propos et précautions à l'écoute du podcast Découvrez Objectif Métamorphose, notre programme en 12 étapes pour partir à la rencontre de soi-même.Recevez chaque semaine l'inspirante newsletter Métamorphose par Anne GhesquièreFaites le TEST gratuit de La Roue Métamorphose avec 9 piliers de votre vie !Suivez nos RS : Insta, Facebook & TikTokAbonnez-vous sur Apple Podcast / Spotify / Deezer / CastBox/ YoutubeSoutenez Métamorphose en rejoignant la Tribu MétamorphosePhoto © Christophe Martin Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠⁠⁠https://www.lovelightsofia.com/selflovechallenge2025⁠⁠⁠次期募集SLAウェイトリスト：https://www.lovelightsofia.com/selfloveacademy無料インナーチャイルド瞑想：⁠⁠⁠https://lovelightsofia.activehosted.com/f/1⁠Megumiさんアカウント：megumi.wellness

6/23スタート！セルフラブチャレンジへの参加はこちらから→ ⁠⁠https://www.lovelightsofia.com/selflovechallenge2025⁠⁠次期募集SLAウェイトリスト：⁠https://www.lovelightsofia.com/selfloveacademy⁠無料インナーチャイルド瞑想：⁠⁠https://lovelightsofia.activehosted.com/f/1⁠Momokoさんアカウント→ www.instagram.com/narimohearts

Support our Sponsors: HungryRoot: https://hunryroot.com/milehigher Intro 0:00 The Hearst Empire 4:40 Patty's Birth into Privilege 9:26 Berkley, the Home of a Revolution 10:57 Birth of the SLA 14:32 Targeting Marcus Foster 22:20 The Kidnapping of Patty Hearst 28:33 Radicalization 35:28 Robbing Hibernia Bank 39:30 A History of Shootouts 46:14 The Biggest Shootout in LA History 48:36 The Second Robbery, a Disaster 1:01:13 Patty's Arrest and Trial 1:05:41 Freedom... Where are the SLA Members Now? 1:10:48 Final Thoughts & Outro 1:15:47 Higher Hope Foundation: https://higherhope.org Mile Higher Merch: https://milehighermerch.com Check out our other podcasts! The Sesh https://bit.ly/3Mtoz4X Lights Out https://bit.ly/3n3Gaoe Planet Sleep https://linktr.ee/planetsleep Join our official FB group! https://bit.ly/3kQbAxg Join our Discord community, it's free! https://discord.gg/hZ356G9 MHP YouTube: http://bit.ly/2qaDWGf Are You Subscribed On Apple Podcast & Spotify?! Support MHP by leaving a rating or review on Apple Podcast :) https://apple.co/2H4kh58 MHP Topic Request Form: https://forms.gle/gUeTEzL9QEh4Hqz88 You can follow us on all the things: @milehigherpod Instagram: http://www.instagram.com/milehigherpod YouTube: https://www.youtube.com/@MileHigher Hosts: Kendall: @kendallraeonyt IG: http://instagram.com/kendallraeonyt YT: https://www.youtube.com/c/kendallsplace Josh: @milehigherjosh IG: http://www.instagram.com/milehigherjosh Producers: Janelle: @janelle_fields_ IG: https://www.instagram.com/janelle_fields_/ Ian: @ifarme IG: https://www.instagram.com/ifarme/ Tom: @tomfoolery_photo IG: https://www.instagram.com/tomfoolery_photo   Podcast sponsor inquires: adops@audioboom.com ✉ Send Us Mail & Fan Art ✉ Kendall Rae & Josh Thomas  8547 E Arapahoe Rd Ste J # 233 Greenwood Village, CO 80112 Music By: Mile Higher Boys YT: https://bit.ly/2Q7N5QO Spotify: https://open.spotify.com/artist/0F4ik... Sources: https://pastebin.com/mvJkUhPe The creator hosts a documentary series for educational purposes (EDSA). These include authoritative sources such as interviews, newspaper articles, and TV news reporting meant to educate and memorialize notable cases in our history. Videos come with an editorial and artistic value.

Saifond, l'un des artistes les plus populaires en Guinée, sera en concert samedi 7 juin au Casino de Paris. Accompagné de son manager, Raya Ly, élu meilleur manager d'artistes en Guinée, en 2024, il répond aux questions de Claudy Siar, Yasmine Bakayoko et Stéphane Linon.Puis, Slaï, acteur de premier plan du zouk, nous présentera la deuxième édition du Caribbean Summer Festival qui aura lieu à l'Accor Arena le vendredi 6 juin 2025.  Pour visionner les clips, cliquez sur les titres des chansons : Saïfond - Fenanilan Saïfond - Hakill Saïfond - Taa WoullouSlaï -La dernière danse Saïfond -NénéSaïfond -Djarama Retrouvez notre playlist sur Deezer. 

Saifond, l'un des artistes les plus populaires en Guinée, sera en concert samedi 7 juin au Casino de Paris. Accompagné de son manager, Raya Ly, élu meilleur manager d'artistes en Guinée, en 2024, il répond aux questions de Claudy Siar, Yasmine Bakayoko et Stéphane Linon.Puis, Slaï, acteur de premier plan du zouk, nous présentera la deuxième édition du Caribbean Summer Festival qui aura lieu à l'Accor Arena le vendredi 6 juin 2025.  Pour visionner les clips, cliquez sur les titres des chansons : Saïfond - Fenanilan Saïfond - Hakill Saïfond - Taa WoullouSlaï -La dernière danse Saïfond -NénéSaïfond -Djarama Retrouvez notre playlist sur Deezer. 

In Episode 177 of The Fleet Success Show, Marc Canton and Steve Saltzgiver unload a truth-packed conversation on the painful realities of outsourcing fleet maintenance. From horror stories about seven visits for the same repair to $3,500 upsell attempts during a routine oil change, this episode explores the downside of putting your fleet's fate in the hands of external vendors — especially without tight service-level agreements (SLAs) in place.Marc vents his real-world frustrations as a fleet leader turned vehicle caretaker for his entire family. Steve, bringing decades of fleet management and consulting experience, breaks down how fleets can build smarter, more accountable outsourcing relationships. Together, they unpack when outsourcing makes sense, how to hold vendors accountable, and why an in-house shop might still be your best line of defense against inefficiency, comebacks, and ballooning costs. 

La globalización moderna empezó a ganar fuerza en los años 80. Es un fenómeno complejo que ha integrado economías, culturas y sociedades a nivel mundial. Nos ha permitido tener productos a precios competitivos y ha traído consigo un aumento de la riqueza global, pero también ha tenido consecuencias negativas tanto a nivel económico, como social y ambiental. Ahora el mundo está cambiando, sus bloques económicos también y la globalización no vive su mejor momento. Pero, ¿está superada?, ¿podemos hablar de una nueva era?, ¿o simplemente el tablero se está reconfigurando? Se lo preguntamos a Amanda Mars, directora de Cinco Días y subdirectora de información económica de EL PAÍS. CRÉDITOS: Presenta y realiza: Marta Curiel Diseño de sonido: Nacho Taboada Edición: Ana Ribera Dirección: Silvia Cruz Lapeña Sintonía: Jorge Magaz PARA SABER MÁS: La globalización en retirada El fin de un periodo históricamente anómalo de globalización pacífica Si tienes quejas, dudas o sugerencias, escribe a defensora@elpais.es o manda un audio al +34 649362138 (no atiende llamadas).

Today's guest is someone you may remember from one of our most listened-to episodes of last year—Sarah Ashcroft. Sarah is one of the original fashion creators in the UK, and in our last episode, she took us through her journey turning her online presence into the fashion powerhouse that was SLA The Label.But since then, a lot has changed.In Feburary this year, Sarah announced that SLA was closing. This episode is the first time she's speaking on a podcast about that situation—what led to it, how it felt to walk away from something she built from the ground up, and what she's learned in the months since.This is a conversation about identity, pressure, clarity, and the harsh reality of running a business in public. It's raw, it's reflective, and it's going to resonate with anyone who's ever had to make a difficult decision or gone through a huge life change.I'm so grateful to Sarah for trusting us with this conversation. +SARAH ASHCROFTInstagram: https://www.instagram.com/sarahhashcroft/?hl=enYoutube: https://www.youtube.com/@sarahhashcroft +MY LINKS: https://gracebeverley.komi.io/+RETROGRADE, SHREDDY, TALA and THE PRODUCTIVITY METHOD are my own businesses, therefore any mention of them - whilst not being a sponsorship - is obviously monetarily endorsed. As usual, sponsorships do not change my opinions nor my honesty, but I will always disclaim to make sure motives are clear

Přivezla Rudá armáda v květnu 1945 do Československa svobodu? „Totalitní Sovětský svaz nebyl svobodný a nemohl svobodu ani přinášet. Spíš přinesl vítězství nad nacismem,“ míní v pořadu Pro a proti historik a filozof Petr Hlaváček, hlavní editor časopisu Forum 24. „Svobodu omezil už poválečný nacionalismus a etnická čistka Němců a Maďarů,“ upozorňuje pro Český rozhlas Plus politolog Ondřej Slačálek.Všechny díly podcastu Pro a proti můžete pohodlně poslouchat v mobilní aplikaci mujRozhlas pro Android a iOS nebo na webu mujRozhlas.cz.

Show Website: https://mspbusinessschool.com/ Guest Name: Dustin Puryear LinkedIn page: https://www.linkedin.com/in/dustinpuryear/ Company: Giant Rocket Ship Website: https://giantrocketship.com/ Host Brian Doyle: https://www.linkedin.com/in/briandoylevciotoolbox/ In this episode of MSP Business School, host Brian Doyle is joined by Dustin Puryear of Giant Rocketship to delve into effective solutions for enhancing service delivery within MSP operations. Dustin shares his journey from managing an MSP to developing a vendor product that addresses the industry's common pain points. The conversation focuses on how Giant Rocketship innovates ticket management and service coordination through automation, reducing backlog and improving client satisfaction. Dustin Puryear explains the genesis of Giant Rocketship as a response to the inefficiencies he noticed in ticket management during his MSP tenure. By automating the dispatch and prioritization of tasks, Rocketship helps MSPs manage workloads more effectively, saving time and resources. Dustin highlights the importance of focusing on the volume of work rather than ticket numbers, a common oversight in service delivery operations. With trends towards AI and automation, the discussion underscores the evolving nature of MSP business models and the necessity of adapting to new technologies. Key Takeaways: Streamlining Operations: Giant Rocketship automates the dispatch process, helping MSPs reduce ticket backlogs and improve service efficiency.  Prioritization Through Automation: By prioritizing tickets based on SLA, customer impact, and team capabilities, the system ensures that urgent tasks are addressed promptly.  Cost-Effectiveness: Implementing automation can help MSPs reassign resources and potentially reduce staffing needs, significantly improving ROI.  Evolving Perceptions: Dustin emphasizes shifting from ticket-focused to activity-focused operations to enhance service delivery and customer satisfaction.  Industry Trends: The adoption of AI and automation in MSPs is reshaping traditional service delivery models, necessitating a more strategic approach to technology and resources.  Sponsor vCIOToolbox: https://vciotoolbox.com

Why do short clear SLAs improve your services, customer satisfaction, and life? How do you write and use an effective SLA?

In our recent episode on global burn surgery with Dr. Barclay Stewart and Dr. Manish Yadav, we discussed several cases at Kirtipur Hospital in Nepal to illustrate the global burden of burns and similarities and differences in treating burns at Harborview Medical Center, a level 1 trauma and ABA verified burn center in Seattle, WA and Kirtipur Hospital (Nepal Cleft and Burn Center) in Kathmandu, Nepal. In this episode Dr. Stewart and Dr. Yadav return for an interview by UW Surgery Resident, Paul Herman, sharing insights on how to get involved in global surgery with an emphasis on sustainable participation. Hosts:  Manish Yadav, Kirtipur Hospital, Nepal Barclay Stewart, UW/Harborview Medical Center Paul Herman, UW/Harborview General Surgery Resident, @paul_herm  Tam Pham, UW/Harborview Medical Center (Editor) Learning Objectives 1.     Approaches to global surgery  a.     Describe historical perspectives on global health and global surgery reviewing biases global surgery inherits from global health due to the history of colonialism, neo-colonialism and systemic inequalities b.     Review a recently published framework and evaluation metrics for sustainable global surgery partnerships (GSPs) as described by Binda et al., in Annals of Surgery in March 2024. c.      Provide examples of this framework from a successful global surgery partnership d.     Define vertical, horizontal and diagonal global surgery approaches e.     Share tips for initial engagement for individuals interested in getting involved in global surgery References 1.     Gosselin, R., Charles, A., Joshipura, M., Mkandawire, N., Mock, C. N. , et. al. 2015. “Surgery and Trauma Care”. In: Disease Control Priorities (third edition): Volume 1, Essential Surgery, edited by H. Debas, P. Donkor, A. Gawande, D. T. Jamison, M. Kruk, C. N. Mock. Washington, DC: World Bank. 2.     Qin R, Alayande B, Okolo I, Khanyola J, Jumbam DT, Koea J, Boatin AA, Lugobe HM, Bump J. Colonisation and its aftermath: reimagining global surgery. BMJ Glob Health. 2024 Jan 4;9(1):e014173. doi: 10.1136/bmjgh-2023-014173. PMID: 38176746; PMCID: PMC10773343. https://pubmed.ncbi.nlm.nih.gov/38176746/ 3.     Binda CJ, Adams J, Livergant R, Lam S, Panchendrabose K, Joharifard S, Haji F, Joos E. Defining a Framework and Evaluation Metrics for Sustainable Global Surgical Partnerships: A Modified Delphi Study. Ann Surg. 2024 Mar 1;279(3):549-553. doi: 10.1097/SLA.0000000000006058. Epub 2023 Aug 4. PMID: 37539584; PMCID: PMC10829902.  https://pubmed.ncbi.nlm.nih.gov/37539584/ 4.     Jedrzejko N, Margolick J, Nguyen JH, Ding M, Kisa P, Ball-Banting E, Hameed M, Joos E. A systematic review of global surgery partnerships and a proposed framework for sustainability. Can J Surg. 2021 Apr 28;64(3):E280-E288. doi: 10.1503/cjs.010719. PMID: 33908733; PMCID: PMC8327986. https://pubmed.ncbi.nlm.nih.gov/33908733/ 5.     Frenk J, Gómez-Dantés O, Knaul FM: The health systems agenda: prospects for the diagonal approach. The handbook of global health policy. 2014 Apr 24; pp. 425–439 6.     Davé DR, Nagarjan N, Canner JK, Kushner AL, Stewart BT; SOSAS4 Research Group. Rethinking burns for low & middle-income countries: Differing patterns of burn epidemiology, care seeking behavior, and outcomes across four countries. Burns. 2018 Aug;44(5):1228-1234. doi: 10.1016/j.burns.2018.01.015. Epub 2018 Feb 21. PMID: 29475744. https://pubmed.ncbi.nlm.nih.gov/29475744/ 7.     Strain, S., Adjei, E., Edelman, D. et al. The current landscape of global international surgical rotations for general surgery residents in the United States: a survey by the Association for Program Directors in Surgery's (APDS) global surgery taskforce. Global Surg Educ 3, 77 (2024). https://doi.org/10.1007/s44186-024-00273-2 8.     Francalancia S, Mehta K, Shrestha R, Phuyal D, Bikash D, Yadav M, Nakarmi K, Rai S, Sharar S, Stewart BT, Fudem G. Consumer focus group testing with stakeholders to generate an enteral resuscitation training flipbook for primary health center and first-level hospital providers in Nepal. Burns. 2024 Jun;50(5):1160-1173. doi: 10.1016/j.burns.2024.02.008. Epub 2024 Feb 15. PMID: 38472005; PMCID: PMC11116054. https://pubmed.ncbi.nlm.nih.gov/38472005/ 9.     Shrestha R, Mehta K, Mesic A, Dahanayake D, Yadav M, Rai S, Nakarmi K, Bista P, Pham T, Stewart BT. Barriers and facilitators to implementing enteral resuscitation for major burn injuries: Reflections from Nepalese care providers. Burns. 2024 Oct 28;51(1):107302. doi: 10.1016/j.burns.2024.107302. Epub ahead of print. PMID: 39577105. https://pubmed.ncbi.nlm.nih.gov/39577105/ Please visit https://behindtheknife.org to access other high-yield surgical education podcasts, videos and more.   If you liked this episode, check out our recent episodes here: https://app.behindtheknife.org/listen

Making a LIDAR scanner Pt 1, X1C Unbox and Setup, Tariff impacts 

U povodu obilježavanja 28 godina postojanja i kontinuiranog rada hora "Modra rijeka" iz Sydneya donosimo razgovor sa profesoricom Slađanom Hodžić, muzičkim pedagogom, dirigenticom i osnivačicom hora "Modra rijeka", koji svojim višedecenijskim radom pronosi širom Australije ljepotu bosanske pjesme, te čuva od zaborava neprocjenjivo blago bosanskohercegovačkog kulturnog naslijeđa. Hor "Modra rijeka" će 10. maja održati svoj redovni godišnji koncert u Sydneyu, slaveći uzajamno poštovanje i ljubav prema muzici, tradiciji i zajedništvu. Pjevanje u horu donijelo je opuštanje, duševni mir, iscjeljenje, međusobno poštovanje. "Sve bilo je muzika..."

U želji da saznamo koja su najvažnija izborna pitanja koja zanimaju zajednicu Bosanaca i Hercegovaca uoči Saveznih izbora u Australiji, proveli smo anketu među istaknutim članovima zajednice u Perthu, Sydneyu i Melbourneu. Šta očekuju od Saveznih izbora i koje su najvažnije teme na osnovu kojih će procijeniti kome dati svoj glas, saznali smo od gospodina Muhameda Merdžanića, direktora Bosanskog sportsko- rekreacionog centra u Perthu, profesorice Slađane Hodžic, dirigentice i voditeljice hora "Modra rijeka" iz Sydneya, gospodina Fuada Mehmedovića, glasnogovornika BH Centra Springvale iz Melbournea, te nastavnica Bosanske škole u Viktoriji Sade Makaš i Mirne Bardak.

Dime qué piensas del episodio.Mi invitada de hoy es Pati Jinich IG: @patijinich, una de las voces más influyentes de la cocina mexicana en el mundo. Nacida en la Ciudad de México y formada como analista política en el ITAM, el CIDE y Georgetown, dejó atrás una carrera como investigadora en Washington D.C. para contar la historia de México a través de sus sabores.Por favor ayúdame y sigue Cracks Podcast en YouTube aquí."Vivir en el limbo es lo peor de todos los mundos."- Pati Jinich @PatiJinichComparte esta frase en TwitterEste episodio es presentado por Hospital Angeles Health System que cuenta con  el programa de cirugía robótica más robusto en el sector privado en México y por  LegaLario la empresa de tecnología legal que ayuda a reducir costos y tiempos de gestión hasta un 80%.Su serie Pati's Mexican Table, que va por la temporada 14, y sus documentales La Frontera y Panamericana, la han llevado a explorar desde los acantilados de Nuevo León con escaladores, hasta las montañas aisladas de Sinaloa donde fue la primera visitante en aprender las recetas de una aldea perdida en el tiempo.Hoy hablamos de identidad, de valentía, de reinvención y de cómo una mujer que pudo haber terminado en una oficina de política pública, eligió escribir historia desde la cocina.Qué puedes aprender hoyEl error de prepararte de másLa paradoja Judío-americanaCómo superar el limbo de la toma de decisiones*Este episodio es presentado por Hospital Angeles Health SystemLos avances en cirugía robótica permiten intervenciones con menos sangrado, menos dolor, cicatrices más pequeñas y una recuperación más rápida.Hospital Angeles Health System tiene el programa de cirugía robótica más robusto en el sector privado en México. Cuenta con 13 robots DaVinci, el más avanzado del mundo y con el mayor número de médicos certificados en cirugía robótica ya que tiene el único centro de capacitación de cirugía robótica en el país.Este es el futuro de la cirugía. Si quieres conocer más sobre el programa de cirugía robótica de Hospital Angeles Health System y ver el directorio de doctores visita cracks.la/angeles*Este episodio es presentado por LegaLario, la Legaltech líder en México.Con LegaLario, puedes transformar la manera en que manejas los acuerdos legales de tu empresa. Desde la creación y gestión de contratos electrónicos hasta la recolección de firmas digitales y la validación de identidades, LegaLario cumple rigurosamente con la legislación mexicana y las normativas internacionales.LegaLario ha ayudado a empresas de todos los tamaños y sectores a reducir costos y tiempos de gestión hasta un 80%. Y lo más importante, garantiza la validez legal de cada proceso y la seguridad de tu información, respaldada por certificaciones ISO 27001.Para ti que escuchas Cracks, LegaLario ofrece un 20% de descuento visitando www.legalario.com/cracks. Ve el episodio en Youtube

Dieter Schwarze is a true 3D printing icon. Here we get the twisting, arduous tale of Dieter's journey into additive. Starting with inkjet, SLA and lots of other technologies, Dieter´s path was filled with telenovela-like plot twists. The Nikon SLM Solutions story is an important element of his tale, but the entire saga is much more complex. With a lot of candor, he talks about getting started, growing a business, selling to Nikon, and more. We get a real entrepreneurial vision here. Nothing has been straightforward in Dieter's journey, and there is so much to learn. This is a must-listen for those who wish to be entrepreneurs or are already.

Original 420 flag, from the Waldo's official website. All five of the original 420 Waldos are in the studio today on Brew Ha Ha with Steve Jaxon and Herlinda Heras. Waldo Dave and Waldo Steve were on Brew Ha Ha once before, on this episode of April 18, 2019. This time, all five of them are here. Steve, Dave, Jeff, Larry and Mark are here, they are the original Waldos from San Rafael High School in the early 1970s. There is ample documentation of their invention of the expression 420 on their website. It is the first time all five of them have been together for a radio interview. They used to hang out on the wall, every day between classes and after school. “We were all about comedy and having fun.” They also listened to a lot of music, including the great bands from the Bay Area at the time. Lagunitas makes a special 420 Waldos beer and they have some of it in studio today. At the time, one of them had a brother who was in the Coast Guard who knew of a secret garden. One of them got the map. Visit our sponsor Pizzaleah in Windsor for the finest pizza menu and the most authentic flavors around!

“The more you can adjust your communication to fit your customer, the more effective you'll be.” – Rob Broadhead In this episode of Building Better Developers, part of the Building Better Businesses season, hosts Rob Broadhead and Michael Meloche explore customer communication strategies. From tone and timing to tools and follow-up processes, they share real stories and practical tips that every developer and entrepreneur should know. Tone and Timing: Keys to Effective Customer Communication Strategies One of the top takeaways? Tone matters. Even when following up on an unanswered email, how you phrase things can shape how your customer perceives you. Rob cautions against saying things like, “As I said in my last email…”, which can feel accusatory. Instead, assume the best: maybe the message got lost, or perhaps they're dealing with their storms (literal or figurative). ⏱ Timing tip: If you don't get a response within 24–48 hours, follow up—but kindly. A quick “just checking in” keeps communication open and positive. Customer Communication Strategies Start with the Right Tools “Don't force your communication tools on your customers. Find out what works best for them.” – Michael Meloche Different customers prefer different channels. Some want a phone call, others prefer text, while many prefer email. Your job? Adapt to their preferences. This can be a game-changer in building trust for developers and entrepreneurs juggling multiple platforms.

Join hosts Daniel Garcia and Eric Peterson as they dive into the latest news and updates in the BoxLang and CFML world. Don't miss out on insights, discussions, and what's coming next for modern software development!

In 2002 a group of surgeons got together and radically changed surgical training forever. They just got together again... They call themselves the Blue Ribbon Committee. When they met in 2002 they addressed critical issues such as residency structure, specialization, work-life balance, and simulation-based training. Now, with rapid advancements in medicine and education, BRC II has revisited these topics and introduced new priorities to ensure that surgical education meets the demands of the modern era. In this episode, we are joined by Dr. Steven Stain, co-chair of BRC II and a leader in surgical education. Dr. Stain shares insights into the motivations behind the second committee, its key findings, and how competency-based education, entrustable professional activities (EPAs), and other innovations are shaping the future of surgical training. Join hosts Pooja Varman MD, Judith French PhD, and Jeremy Lipman MD, MHPE for an engaging discussion on what surgical educators, trainees, and institutions need to know about the new recommendations from BRC II and the future of surgical education. Learning Objectives By the end of this episode, listeners will be able to  1.     Under the origins and impact of the first Blue Ribbon Committee (BRC I) 2.     Explain the factors that led to the formation of the BRC II and its major recommendations 3.     Identify challenges and opportunities in modern surgical education 4.     Discuss the role of competency-based education and EPAs in training future surgeons 5.     Recognize how institutions and educators can adapt to BRC II recommendations References 1.     Recommendations on Surgical Education and Training in the United States: 2024. Ann Surg. 2024;280(4):535. doi:10.1097/SLA.0000000000006360 https://pubmed.ncbi.nlm.nih.gov/38814074/ 2.     Blue Ribbon Committee II Advises Sweeping Changes in Surgical Education. ACS. Accessed January 12, 2025. https://www.facs.org/for-medical-professionals/news-publications/news-and-articles/bulletin/2024/may-2024-volume-109-issue-5/blue-ribbon-committee-ii-advises-sweeping-changes-in-surgical-education/ ***Fellowship Application Link: https://forms.gle/PQgAvGjHrYUqAqTJ9 Please visit https://behindtheknife.org to access other high-yield surgical education podcasts, videos and more. If you liked this episode, check out our recent episodes here: https://app.behindtheknife.org/listen

Tune in to the latest Suite Spot episode featuring TMG's very own Chief Technology Officer, Jason Lee, as he gives listeners the latest update on our newest innovation, SMART Response powered by TMG AI. Hear about the development, successes, and challenges of building a guest review response solution with the ingenuity of artificial intelligence. Ryan Embree: Welcome to Suite Spot, where hoteliers check in, and we check out what's trending in hotel marketing. I'm your host, Ryan Embree. Welcome to another episode of The Suite Spot. As you can see, if you're watching us on our YouTube channel, we are here in our Suite Spot podcast studio in Maitland, Florida, here with CTO, Jason Lee at Travel Media Group. Jason, thank you so much for being back on the Suite Spot. Jason Lee: Yeah, thanks for having me. In the seated position. Ryan Embree: Yes. I feel like we should be celebrating maybe like a 10th or 15th milestone of you coming on the Suite Spot or something like that. It's been a lot, but we're here to talk about a really important topic, something that's been bubbling up in conferences, conversations that we're having something that you're not a stranger to. You've been doing some research on this and, and have some updates for us. But AI, I mean, it seems to be the, obviously the, the hot topic, like I said, at these conferences or just in the industry, outside of the industry in general, and then pairing it with guest review response, something that Travel Media group obviously known for. We're coming up on the 2 million guest review mark. Which Is a fantastic milestone, really exciting milestone, but I figured we could start the episode by just kind of talking about how Travel Media Group got into guest review response. A lot of the stuff and solutions that we've talked about on this podcast have been through hotel your feedback. Talk to us a little bit about this journey in review response, and then we'll get to maybe where the state of the industry is now, and AI and guest review response. Jason Lee: Well, you know, working with hotels the way we have for a lot of years, almost 10 years ago, we were getting a lot of requests to do review response. And so, we're like, yeah, I think we can do it. And then as we got into it, we realized like, wow, this is complicated because every hotel's different. The vibe of the hotel is different, but also the amenities and policies, the quantities, the types of sites that are, have more text or less text ratings and like, I think even getting deeper into, you know, how a hotel wants to use language. And so like, it's even beyond voice, you know? So it's like it's literally grammar and also types of words. And so I think, so we started in this very simple place, very innocent, like, we can do this. This is gonna be awesome. And I think the first offering we had was 20 reviews. It was an SLA of 20 reviews a month. It was TripAdvisor only and . So we, like, we, we jumped to that and quickly, almost like instantly it was like, well, we need, we definitely need Google, and well, we definitely need Expedia. We definitely need booking. You know, so we had to adapt. And it went, the adoption was not just in the sites that we've brought on, it was also in the complexity of the response. It was also in then systematically creating a flow. So the review comes in, we have a writer that writes a response. That response goes to the property. So like, that stuff wasn't initially there. It goes to the property, the property can edit it, and then, and then it goes live back on the site. So that whole process was also sort of formulated during those first, that first year, and then has become very perfected over time where, where we've taken that and we have all sorts of mechanisms to make sure we capture hotel voice, make sure we're doing the right things, critical review pieces that we're doing. So all of these things to really sort of make it as authentic as possible...

El nuevo primer ministro de Groenlandia, Jens-Frederik Nielsen, asume su cargo en un momento crítico para la isla. Donald Trump quiere Groenlandia por las buenas o por las malas, y su vicepresidente JD Vans lo ha reafirmado en su reciente visita a la isla danesa. Su posición estratégica entre el Atlántico y el Ártico y sus recursos naturales también atraen a China, Rusia y la Unión Europea. Mientras tanto sus casi 60.000 habitantes se encuentran ante un dilema complejo: elegir entre avanzar hacia la independencia o aceptar una mayor influencia de Estados Unidos. En este episodio hablamos con el periodista Carlos Torralba que cubre los países nórdicos en el periódico y que ha estado recientemente en Nuuk, la capital de Groenlandia. CRÉDITOS Realizado por: Elsa Cabria Presenta: Marta Curiel Edición: Marta Curiel y Ana Ribera Grabación en estudio: Nacho Taboada Diseño de sonido: Nicolás Tsabertidis Sintonía: Jorge Magaz Dirección: Silvia Cruz Lapeña PARA SABER MÁS La primera ministra de Dinamarca llega a Groenlandia para mostrar “unión” frente a la presión de Estados Unidos J. D. Vance, el ariete de la estrategia de Trump Si tienes quejas, dudas o sugerencias, escribe a defensora@elpais.es o manda un audio a +34 649362138 (no atiende llamadas).

On his mom's side, Woody LaBounty's San Francisco roots go back to 1850. In Part 1, get to know Woody, who, today, is the president and CEO of SF Heritage. But he's so, so much more than that. He begins by tracing his lineage back to the early days of the Gold Rush. His maternal great-great-great-grandfather arrived here mid-Nineteenth Century. Woody even knows what ship he was on and the exact day that it arrived in the recently christened city of San Francisco. On Woody's dad's side, the roots are about 100 years younger than that. His father grew up in Fort Worth, Texas (like I did). His dad's mom was single and fell on hard times in Texas. She came to San Francisco, where she had a step-brother. Woody's parents met at the Donut Bowl at 10th Avenue and Geary Boulevard (where Boudin Bakery is today). Donut Bowl was a combination donut shop/hot dog joint. At the time the two met, his dad worked as a cook there and his mom was in high school. His mom and her friends went to nearby Washington High and would hang out at the donut shop after school. The next year or so, his parents had their first kid—Woody. They came from different sides of the track, as it were. Woody's mom's family wasn't crazy about her dating his working-class dad, who didn't finish high school. But once his mom became pregnant with Woody, everything changed. The couple had two more sons after Woody. One of his brothers played for the 49ers in the Nineties and lives in Oregon today. His other brother works with underserved high school kids in New Jersey, helping them get into college. Woody shares some impressions of his first 10 years or so of life by describing The City in the mid-Seventies. Yes, kids played in the streets and rode Muni to Candlestick Park and The Tenderloin to go bowling. It was also the era of Patty Hearst and the SLA, Jonestown, and the Moscone/Milk murders. But for 10-year-old Woody, it was home. It felt safe, like a village. Because I'm a dork, I ask Woody to share his memories of when Star Wars came out. Obliging me, he goes on a sidebar about how the cinematic phenomenon came into his world in San Francisco. He did, in fact, see Star Wars in its first run at the Coronet. He attended Sacred Heart on Cathedral Hill when it was an all-boys high school. He grew up Catholic, although you didn't have to be to go to one of SF's three Catholic boys' high schools. Woody describes, in broad terms, the types of families that sent their boys to the three schools. Sacred Heart was generally for kids of working-class folks. After school, if they didn't take Muni back home to the Richmond District, Woody and his friends might head over to Fisherman's Wharf to play early era video games. Or, most likely, they'd head over to any number of high schools to talk to girls. Because parental supervision was lacking, let's say, Woody and his buddies also frequently went to several 18+ and 21+ spots. The I-Beam in the Haight, The Triangle in the Marina, The Pierce Street Annex, Enrico's in North Beach, Mabuhay Gardens. There, he saw bands like The Tubes and The Dead Kennedy's, although punk wasn't really his thing. Woody was more into jazz, RnB, and late-disco. We chat a little about café culture in San Francisco, something that didn't really exist until the Eighties. To this day, Woody still spends his Friday mornings at Simple Pleasures Cafe. And we end Part 1 with Woody's brief time at UC Berkeley (one year) and the real reason he even bothered to try college. Check back next week for Part 2 with Woody LaBounty. And this Thursday, look for a bonus episode all about We Players and their upcoming production of Macbeth at Fort Point. We recorded this episode in Mountain Lake Park in March 2025. Photography by Jeff Hunt

If you're in SF: Join us for the Claude Plays Pokemon hackathon this Sunday!If you're not: Fill out the 2025 State of AI Eng survey for $250 in Amazon cards!We are SO excited to share our conversation with Dharmesh Shah, co-founder of HubSpot and creator of Agent.ai.A particularly compelling concept we discussed is the idea of "hybrid teams" - the next evolution in workplace organization where human workers collaborate with AI agents as team members. Just as we previously saw hybrid teams emerge in terms of full-time vs. contract workers, or in-office vs. remote workers, Dharmesh predicts that the next frontier will be teams composed of both human and AI members. This raises interesting questions about team dynamics, trust, and how to effectively delegate tasks between human and AI team members.The discussion of business models in AI reveals an important distinction between Work as a Service (WaaS) and Results as a Service (RaaS), something Dharmesh has written extensively about. While RaaS has gained popularity, particularly in customer support applications where outcomes are easily measurable, Dharmesh argues that this model may be over-indexed. Not all AI applications have clearly definable outcomes or consistent economic value per transaction, making WaaS more appropriate in many cases. This insight is particularly relevant for businesses considering how to monetize AI capabilities.The technical challenges of implementing effective agent systems are also explored, particularly around memory and authentication. Shah emphasizes the importance of cross-agent memory sharing and the need for more granular control over data access. He envisions a future where users can selectively share parts of their data with different agents, similar to how OAuth works but with much finer control. This points to significant opportunities in developing infrastructure for secure and efficient agent-to-agent communication and data sharing.Other highlights from our conversation* The Evolution of AI-Powered Agents – Exploring how AI agents have evolved from simple chatbots to sophisticated multi-agent systems, and the role of MCPs in enabling that.* Hybrid Digital Teams and the Future of Work – How AI agents are becoming teammates rather than just tools, and what this means for business operations and knowledge work.* Memory in AI Agents – The importance of persistent memory in AI systems and how shared memory across agents could enhance collaboration and efficiency.* Business Models for AI Agents – Exploring the shift from software as a service (SaaS) to work as a service (WaaS) and results as a service (RaaS), and what this means for monetization.* The Role of Standards Like MCP – Why MCP has been widely adopted and how it enables agent collaboration, tool use, and discovery.* The Future of AI Code Generation and Software Engineering – How AI-assisted coding is changing the role of software engineers and what skills will matter most in the future.* Domain Investing and Efficient Markets – Dharmesh's approach to domain investing and how inefficiencies in digital asset markets create business opportunities.* The Philosophy of Saying No – Lessons from "Sorry, You Must Pass" and how prioritization leads to greater productivity and focus.Timestamps* 00:00 Introduction and Guest Welcome* 02:29 Dharmesh Shah's Journey into AI* 05:22 Defining AI Agents* 06:45 The Evolution and Future of AI Agents* 13:53 Graph Theory and Knowledge Representation* 20:02 Engineering Practices and Overengineering* 25:57 The Role of Junior Engineers in the AI Era* 28:20 Multi-Agent Systems and MCP Standards* 35:55 LinkedIn's Legal Battles and Data Scraping* 37:32 The Future of AI and Hybrid Teams* 39:19 Building Agent AI: A Professional Network for Agents* 40:43 Challenges and Innovations in Agent AI* 45:02 The Evolution of UI in AI Systems* 01:00:25 Business Models: Work as a Service vs. Results as a Service* 01:09:17 The Future Value of Engineers* 01:09:51 Exploring the Role of Agents* 01:10:28 The Importance of Memory in AI* 01:11:02 Challenges and Opportunities in AI Memory* 01:12:41 Selective Memory and Privacy Concerns* 01:13:27 The Evolution of AI Tools and Platforms* 01:18:23 Domain Names and AI Projects* 01:32:08 Balancing Work and Personal Life* 01:35:52 Final Thoughts and ReflectionsTranscriptAlessio [00:00:04]: Hey everyone, welcome back to the Latent Space podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Small AI.swyx [00:00:12]: Hello, and today we're super excited to have Dharmesh Shah to join us. I guess your relevant title here is founder of Agent AI.Dharmesh [00:00:20]: Yeah, that's true for this. Yeah, creator of Agent.ai and co-founder of HubSpot.swyx [00:00:25]: Co-founder of HubSpot, which I followed for many years, I think 18 years now, gonna be 19 soon. And you caught, you know, people can catch up on your HubSpot story elsewhere. I should also thank Sean Puri, who I've chatted with back and forth, who's been, I guess, getting me in touch with your people. But also, I think like, just giving us a lot of context, because obviously, My First Million joined you guys, and they've been chatting with you guys a lot. So for the business side, we can talk about that, but I kind of wanted to engage your CTO, agent, engineer side of things. So how did you get agent religion?Dharmesh [00:01:00]: Let's see. So I've been working, I'll take like a half step back, a decade or so ago, even though actually more than that. So even before HubSpot, the company I was contemplating that I had named for was called Ingenisoft. And the idea behind Ingenisoft was a natural language interface to business software. Now realize this is 20 years ago, so that was a hard thing to do. But the actual use case that I had in mind was, you know, we had data sitting in business systems like a CRM or something like that. And my kind of what I thought clever at the time. Oh, what if we used email as the kind of interface to get to business software? And the motivation for using email is that it automatically works when you're offline. So imagine I'm getting on a plane or I'm on a plane. There was no internet on planes back then. It's like, oh, I'm going through business cards from an event I went to. I can just type things into an email just to have them all in the backlog. When it reconnects, it sends those emails to a processor that basically kind of parses effectively the commands and updates the software, sends you the file, whatever it is. And there was a handful of commands. I was a little bit ahead of the times in terms of what was actually possible. And I reattempted this natural language thing with a product called ChatSpot that I did back 20...swyx [00:02:12]: Yeah, this is your first post-ChatGPT project.Dharmesh [00:02:14]: I saw it come out. Yeah. And so I've always been kind of fascinated by this natural language interface to software. Because, you know, as software developers, myself included, we've always said, oh, we build intuitive, easy-to-use applications. And it's not intuitive at all, right? Because what we're doing is... We're taking the mental model that's in our head of what we're trying to accomplish with said piece of software and translating that into a series of touches and swipes and clicks and things like that. And there's nothing natural or intuitive about it. And so natural language interfaces, for the first time, you know, whatever the thought is you have in your head and expressed in whatever language that you normally use to talk to yourself in your head, you can just sort of emit that and have software do something. And I thought that was kind of a breakthrough, which it has been. And it's gone. So that's where I first started getting into the journey. I started because now it actually works, right? So once we got ChatGPT and you can take, even with a few-shot example, convert something into structured, even back in the ChatGP 3.5 days, it did a decent job in a few-shot example, convert something to structured text if you knew what kinds of intents you were going to have. And so that happened. And that ultimately became a HubSpot project. But then agents intrigued me because I'm like, okay, well, that's the next step here. So chat's great. Love Chat UX. But if we want to do something even more meaningful, it felt like the next kind of advancement is not this kind of, I'm chatting with some software in a kind of a synchronous back and forth model, is that software is going to do things for me in kind of a multi-step way to try and accomplish some goals. So, yeah, that's when I first got started. It's like, okay, what would that look like? Yeah. And I've been obsessed ever since, by the way.Alessio [00:03:55]: Which goes back to your first experience with it, which is like you're offline. Yeah. And you want to do a task. You don't need to do it right now. You just want to queue it up for somebody to do it for you. Yes. As you think about agents, like, let's start at the easy question, which is like, how do you define an agent? Maybe. You mean the hardest question in the universe? Is that what you mean?Dharmesh [00:04:12]: You said you have an irritating take. I do have an irritating take. I think, well, some number of people have been irritated, including within my own team. So I have a very broad definition for agents, which is it's AI-powered software that accomplishes a goal. Period. That's it. And what irritates people about it is like, well, that's so broad as to be completely non-useful. And I understand that. I understand the criticism. But in my mind, if you kind of fast forward months, I guess, in AI years, the implementation of it, and we're already starting to see this, and we'll talk about this, different kinds of agents, right? So I think in addition to having a usable definition, and I like yours, by the way, and we should talk more about that, that you just came out with, the classification of agents actually is also useful, which is, is it autonomous or non-autonomous? Does it have a deterministic workflow? Does it have a non-deterministic workflow? Is it working synchronously? Is it working asynchronously? Then you have the different kind of interaction modes. Is it a chat agent, kind of like a customer support agent would be? You're having this kind of back and forth. Is it a workflow agent that just does a discrete number of steps? So there's all these different flavors of agents. So if I were to draw it in a Venn diagram, I would draw a big circle that says, this is agents, and then I have a bunch of circles, some overlapping, because they're not mutually exclusive. And so I think that's what's interesting, and we're seeing development along a bunch of different paths, right? So if you look at the first implementation of agent frameworks, you look at Baby AGI and AutoGBT, I think it was, not Autogen, that's the Microsoft one. They were way ahead of their time because they assumed this level of reasoning and execution and planning capability that just did not exist, right? So it was an interesting thought experiment, which is what it was. Even the guy that, I'm an investor in Yohei's fund that did Baby AGI. It wasn't ready, but it was a sign of what was to come. And so the question then is, when is it ready? And so lots of people talk about the state of the art when it comes to agents. I'm a pragmatist, so I think of the state of the practical. It's like, okay, well, what can I actually build that has commercial value or solves actually some discrete problem with some baseline of repeatability or verifiability?swyx [00:06:22]: There was a lot, and very, very interesting. I'm not irritated by it at all. Okay. As you know, I take a... There's a lot of anthropological view or linguistics view. And in linguistics, you don't want to be prescriptive. You want to be descriptive. Yeah. So you're a goals guy. That's the key word in your thing. And other people have other definitions that might involve like delegated trust or non-deterministic work, LLM in the loop, all that stuff. The other thing I was thinking about, just the comment on Baby AGI, LGBT. Yeah. In that piece that you just read, I was able to go through our backlog and just kind of track the winter of agents and then the summer now. Yeah. And it's... We can tell the whole story as an oral history, just following that thread. And it's really just like, I think, I tried to explain the why now, right? Like I had, there's better models, of course. There's better tool use with like, they're just more reliable. Yep. Better tools with MCP and all that stuff. And I'm sure you have opinions on that too. Business model shift, which you like a lot. I just heard you talk about RAS with MFM guys. Yep. Cost is dropping a lot. Yep. Inference is getting faster. There's more model diversity. Yep. Yep. I think it's a subtle point. It means that like, you have different models with different perspectives. You don't get stuck in the basin of performance of a single model. Sure. You can just get out of it by just switching models. Yep. Multi-agent research and RL fine tuning. So I just wanted to let you respond to like any of that.Dharmesh [00:07:44]: Yeah. A couple of things. Connecting the dots on the kind of the definition side of it. So we'll get the irritation out of the way completely. I have one more, even more irritating leap on the agent definition thing. So here's the way I think about it. By the way, the kind of word agent, I looked it up, like the English dictionary definition. The old school agent, yeah. Is when you have someone or something that does something on your behalf, like a travel agent or a real estate agent acts on your behalf. It's like proxy, which is a nice kind of general definition. So the other direction I'm sort of headed, and it's going to tie back to tool calling and MCP and things like that, is if you, and I'm not a biologist by any stretch of the imagination, but we have these single-celled organisms, right? Like the simplest possible form of what one would call life. But it's still life. It just happens to be single-celled. And then you can combine cells and then cells become specialized over time. And you have much more sophisticated organisms, you know, kind of further down the spectrum. In my mind, at the most fundamental level, you can almost think of having atomic agents. What is the simplest possible thing that's an agent that can still be called an agent? What is the equivalent of a kind of single-celled organism? And the reason I think that's useful is right now we're headed down the road, which I think is very exciting around tool use, right? That says, okay, the LLMs now can be provided a set of tools that it calls to accomplish whatever it needs to accomplish in the kind of furtherance of whatever goal it's trying to get done. And I'm not overly bothered by it, but if you think about it, if you just squint a little bit and say, well, what if everything was an agent? And what if tools were actually just atomic agents? Because then it's turtles all the way down, right? Then it's like, oh, well, all that's really happening with tool use is that we have a network of agents that know about each other through something like an MMCP and can kind of decompose a particular problem and say, oh, I'm going to delegate this to this set of agents. And why do we need to draw this distinction between tools, which are functions most of the time? And an actual agent. And so I'm going to write this irritating LinkedIn post, you know, proposing this. It's like, okay. And I'm not suggesting we should call even functions, you know, call them agents. But there is a certain amount of elegance that happens when you say, oh, we can just reduce it down to one primitive, which is an agent that you can combine in complicated ways to kind of raise the level of abstraction and accomplish higher order goals. Anyway, that's my answer. I'd say that's a success. Thank you for coming to my TED Talk on agent definitions.Alessio [00:09:54]: How do you define the minimum viable agent? Do you already have a definition for, like, where you draw the line between a cell and an atom? Yeah.Dharmesh [00:10:02]: So in my mind, it has to, at some level, use AI in order for it to—otherwise, it's just software. It's like, you know, we don't need another word for that. And so that's probably where I draw the line. So then the question, you know, the counterargument would be, well, if that's true, then lots of tools themselves are actually not agents because they're just doing a database call or a REST API call or whatever it is they're doing. And that does not necessarily qualify them, which is a fair counterargument. And I accept that. It's like a good argument. I still like to think about—because we'll talk about multi-agent systems, because I think—so we've accepted, which I think is true, lots of people have said it, and you've hopefully combined some of those clips of really smart people saying this is the year of agents, and I completely agree, it is the year of agents. But then shortly after that, it's going to be the year of multi-agent systems or multi-agent networks. I think that's where it's going to be headed next year. Yeah.swyx [00:10:54]: Opening eyes already on that. Yeah. My quick philosophical engagement with you on this. I often think about kind of the other spectrum, the other end of the cell spectrum. So single cell is life, multi-cell is life, and you clump a bunch of cells together in a more complex organism, they become organs, like an eye and a liver or whatever. And then obviously we consider ourselves one life form. There's not like a lot of lives within me. I'm just one life. And now, obviously, I don't think people don't really like to anthropomorphize agents and AI. Yeah. But we are extending our consciousness and our brain and our functionality out into machines. I just saw you were a Bee. Yeah. Which is, you know, it's nice. I have a limitless pendant in my pocket.Dharmesh [00:11:37]: I got one of these boys. Yeah.swyx [00:11:39]: I'm testing it all out. You know, got to be early adopters. But like, we want to extend our personal memory into these things so that we can be good at the things that we're good at. And, you know, machines are good at it. Machines are there. So like, my definition of life is kind of like going outside of my own body now. I don't know if you've ever had like reflections on that. Like how yours. How our self is like actually being distributed outside of you. Yeah.Dharmesh [00:12:01]: I don't fancy myself a philosopher. But you went there. So yeah, I did go there. I'm fascinated by kind of graphs and graph theory and networks and have been for a long, long time. And to me, we're sort of all nodes in this kind of larger thing. It just so happens that we're looking at individual kind of life forms as they exist right now. But so the idea is when you put a podcast out there, there's these little kind of nodes you're putting out there of like, you know, conceptual ideas. Once again, you have varying kind of forms of those little nodes that are up there and are connected in varying and sundry ways. And so I just think of myself as being a node in a massive, massive network. And I'm producing more nodes as I put content or ideas. And, you know, you spend some portion of your life collecting dots, experiences, people, and some portion of your life then connecting dots from the ones that you've collected over time. And I found that really interesting things happen and you really can't know in advance how those dots are necessarily going to connect in the future. And that's, yeah. So that's my philosophical take. That's the, yes, exactly. Coming back.Alessio [00:13:04]: Yep. Do you like graph as an agent? Abstraction? That's been one of the hot topics with LandGraph and Pydantic and all that.Dharmesh [00:13:11]: I do. The thing I'm more interested in terms of use of graphs, and there's lots of work happening on that now, is graph data stores as an alternative in terms of knowledge stores and knowledge graphs. Yeah. Because, you know, so I've been in software now 30 plus years, right? So it's not 10,000 hours. It's like 100,000 hours that I've spent doing this stuff. And so I've grew up with, so back in the day, you know, I started on mainframes. There was a product called IMS from IBM, which is basically an index database, what we'd call like a key value store today. Then we've had relational databases, right? We have tables and columns and foreign key relationships. We all know that. We have document databases like MongoDB, which is sort of a nested structure keyed by a specific index. We have vector stores, vector embedding database. And graphs are interesting for a couple of reasons. One is, so it's not classically structured in a relational way. When you say structured database, to most people, they're thinking tables and columns and in relational database and set theory and all that. Graphs still have structure, but it's not the tables and columns structure. And you could wonder, and people have made this case, that they are a better representation of knowledge for LLMs and for AI generally than other things. So that's kind of thing number one conceptually, and that might be true, I think is possibly true. And the other thing that I really like about that in the context of, you know, I've been in the context of data stores for RAG is, you know, RAG, you say, oh, I have a million documents, I'm going to build the vector embeddings, I'm going to come back with the top X based on the semantic match, and that's fine. All that's very, very useful. But the reality is something gets lost in the chunking process and the, okay, well, those tend, you know, like, you don't really get the whole picture, so to speak, and maybe not even the right set of dimensions on the kind of broader picture. And it makes intuitive sense to me that if we did capture it properly in a graph form, that maybe that feeding into a RAG pipeline will actually yield better results for some use cases, I don't know, but yeah.Alessio [00:15:03]: And do you feel like at the core of it, there's this difference between imperative and declarative programs? Because if you think about HubSpot, it's like, you know, people and graph kind of goes hand in hand, you know, but I think maybe the software before was more like primary foreign key based relationship, versus now the models can traverse through the graph more easily.Dharmesh [00:15:22]: Yes. So I like that representation. There's something. It's just conceptually elegant about graphs and just from the representation of it, they're much more discoverable, you can kind of see it, there's observability to it, versus kind of embeddings, which you can't really do much with as a human. You know, once they're in there, you can't pull stuff back out. But yeah, I like that kind of idea of it. And the other thing that's kind of, because I love graphs, I've been long obsessed with PageRank from back in the early days. And, you know, one of the kind of simplest algorithms in terms of coming up, you know, with a phone, everyone's been exposed to PageRank. And the idea is that, and so I had this other idea for a project, not a company, and I have hundreds of these, called NodeRank, is to be able to take the idea of PageRank and apply it to an arbitrary graph that says, okay, I'm going to define what authority looks like and say, okay, well, that's interesting to me, because then if you say, I'm going to take my knowledge store, and maybe this person that contributed some number of chunks to the graph data store has more authority on this particular use case or prompt that's being submitted than this other one that may, or maybe this one was more. popular, or maybe this one has, whatever it is, there should be a way for us to kind of rank nodes in a graph and sort them in some, some useful way. Yeah.swyx [00:16:34]: So I think that's generally useful for, for anything. I think the, the problem, like, so even though at my conferences, GraphRag is super popular and people are getting knowledge, graph religion, and I will say like, it's getting space, getting traction in two areas, conversation memory, and then also just rag in general, like the, the, the document data. Yeah. It's like a source. Most ML practitioners would say that knowledge graph is kind of like a dirty word. The graph database, people get graph religion, everything's a graph, and then they, they go really hard into it and then they get a, they get a graph that is too complex to navigate. Yes. And so like the, the, the simple way to put it is like you at running HubSpot, you know, the power of graphs, the way that Google has pitched them for many years, but I don't suspect that HubSpot itself uses a knowledge graph. No. Yeah.Dharmesh [00:17:26]: So when is it over engineering? Basically? It's a great question. I don't know. So the question now, like in AI land, right, is the, do we necessarily need to understand? So right now, LLMs for, for the most part are somewhat black boxes, right? We sort of understand how the, you know, the algorithm itself works, but we really don't know what's going on in there and, and how things come out. So if a graph data store is able to produce the outcomes we want, it's like, here's a set of queries I want to be able to submit and then it comes out with useful content. Maybe the underlying data store is as opaque as a vector embeddings or something like that, but maybe it's fine. Maybe we don't necessarily need to understand it to get utility out of it. And so maybe if it's messy, that's okay. Um, that's, it's just another form of lossy compression. Uh, it's just lossy in a way that we just don't completely understand in terms of, because it's going to grow organically. Uh, and it's not structured. It's like, ah, we're just gonna throw a bunch of stuff in there. Let the, the equivalent of the embedding algorithm, whatever they called in graph land. Um, so the one with the best results wins. I think so. Yeah.swyx [00:18:26]: Or is this the practical side of me is like, yeah, it's, if it's useful, we don't necessarilyDharmesh [00:18:30]: need to understand it.swyx [00:18:30]: I have, I mean, I'm happy to push back as long as you want. Uh, it's not practical to evaluate like the 10 different options out there because it takes time. It takes people, it takes, you know, resources, right? Set. That's the first thing. Second thing is your evals are typically on small things and some things only work at scale. Yup. Like graphs. Yup.Dharmesh [00:18:46]: Yup. That's, yeah, no, that's fair. And I think this is one of the challenges in terms of implementation of graph databases is that the most common approach that I've seen developers do, I've done it myself, is that, oh, I've got a Postgres database or a MySQL or whatever. I can represent a graph with a very set of tables with a parent child thing or whatever. And that sort of gives me the ability, uh, why would I need anything more than that? And the answer is, well, if you don't need anything more than that, you don't need anything more than that. But there's a high chance that you're sort of missing out on the actual value that, uh, the graph representation gives you. Which is the ability to traverse the graph, uh, efficiently in ways that kind of going through the, uh, traversal in a relational database form, even though structurally you have the data, practically you're not gonna be able to pull it out in, in useful ways. Uh, so you wouldn't like represent a social graph, uh, in, in using that kind of relational table model. It just wouldn't scale. It wouldn't work.swyx [00:19:36]: Uh, yeah. Uh, I think we want to move on to MCP. Yeah. But I just want to, like, just engineering advice. Yeah. Uh, obviously you've, you've, you've run, uh, you've, you've had to do a lot of projects and run a lot of teams. Do you have a general rule for over-engineering or, you know, engineering ahead of time? You know, like, because people, we know premature engineering is the root of all evil. Yep. But also sometimes you just have to. Yep. When do you do it? Yes.Dharmesh [00:19:59]: It's a great question. This is, uh, a question as old as time almost, which is what's the right and wrong levels of abstraction. That's effectively what, uh, we're answering when we're trying to do engineering. I tend to be a pragmatist, right? So here's the thing. Um, lots of times doing something the right way. Yeah. It's like a marginal increased cost in those cases. Just do it the right way. And this is what makes a, uh, a great engineer or a good engineer better than, uh, a not so great one. It's like, okay, all things being equal. If it's going to take you, you know, roughly close to constant time anyway, might as well do it the right way. Like, so do things well, then the question is, okay, well, am I building a framework as the reusable library? To what degree, uh, what am I anticipating in terms of what's going to need to change in this thing? Uh, you know, along what dimension? And then I think like a business person in some ways, like what's the return on calories, right? So, uh, and you look at, um, energy, the expected value of it's like, okay, here are the five possible things that could happen, uh, try to assign probabilities like, okay, well, if there's a 50% chance that we're going to go down this particular path at some day, like, or one of these five things is going to happen and it costs you 10% more to engineer for that. It's basically, it's something that yields a kind of interest compounding value. Um, as you get closer to the time of, of needing that versus having to take on debt, which is when you under engineer it, you're taking on debt. You're going to have to pay off when you do get to that eventuality where something happens. One thing as a pragmatist, uh, so I would rather under engineer something than over engineer it. If I were going to err on the side of something, and here's the reason is that when you under engineer it, uh, yes, you take on tech debt, uh, but the interest rate is relatively known and payoff is very, very possible, right? Which is, oh, I took a shortcut here as a result of which now this thing that should have taken me a week is now going to take me four weeks. Fine. But if that particular thing that you thought might happen, never actually, you never have that use case transpire or just doesn't, it's like, well, you just save yourself time, right? And that has value because you were able to do other things instead of, uh, kind of slightly over-engineering it away, over-engineering it. But there's no perfect answers in art form in terms of, uh, and yeah, we'll, we'll bring kind of this layers of abstraction back on the code generation conversation, which we'll, uh, I think I have later on, butAlessio [00:22:05]: I was going to ask, we can just jump ahead quickly. Yeah. Like, as you think about vibe coding and all that, how does the. Yeah. Percentage of potential usefulness change when I feel like we over-engineering a lot of times it's like the investment in syntax, it's less about the investment in like arc exacting. Yep. Yeah. How does that change your calculus?Dharmesh [00:22:22]: A couple of things, right? One is, um, so, you know, going back to that kind of ROI or a return on calories, kind of calculus or heuristic you think through, it's like, okay, well, what is it going to cost me to put this layer of abstraction above the code that I'm writing now, uh, in anticipating kind of future needs. If the cost of fixing, uh, or doing under engineering right now. Uh, we'll trend towards zero that says, okay, well, I don't have to get it right right now because even if I get it wrong, I'll run the thing for six hours instead of 60 minutes or whatever. It doesn't really matter, right? Like, because that's going to trend towards zero to be able, the ability to refactor a code. Um, and because we're going to not that long from now, we're going to have, you know, large code bases be able to exist, uh, you know, as, as context, uh, for a code generation or a code refactoring, uh, model. So I think it's going to make it, uh, make the case for under engineering, uh, even stronger. Which is why I take on that cost. You just pay the interest when you get there, it's not, um, just go on with your life vibe coded and, uh, come back when you need to. Yeah.Alessio [00:23:18]: Sometimes I feel like there's no decision-making in some things like, uh, today I built a autosave for like our internal notes platform and I literally just ask them cursor. Can you add autosave? Yeah. I don't know if it's over under engineer. Yep. I just vibe coded it. Yep. And I feel like at some point we're going to get to the point where the models kindDharmesh [00:23:36]: of decide where the right line is, but this is where the, like the, in my mind, the danger is, right? So there's two sides to this. One is the cost of kind of development and coding and things like that stuff that, you know, we talk about. But then like in your example, you know, one of the risks that we have is that because adding a feature, uh, like a save or whatever the feature might be to a product as that price tends towards zero, are we going to be less discriminant about what features we add as a result of making more product products more complicated, which has a negative impact on the user and navigate negative impact on the business. Um, and so that's the thing I worry about if it starts to become too easy, are we going to be. Too promiscuous in our, uh, kind of extension, adding product extensions and things like that. It's like, ah, why not add X, Y, Z or whatever back then it was like, oh, we only have so many engineering hours or story points or however you measure things. Uh, that least kept us in check a little bit. Yeah.Alessio [00:24:22]: And then over engineering, you're like, yeah, it's kind of like you're putting that on yourself. Yeah. Like now it's like the models don't understand that if they add too much complexity, it's going to come back to bite them later. Yep. So they just do whatever they want to do. Yeah. And I'm curious where in the workflow that's going to be, where it's like, Hey, this is like the amount of complexity and over-engineering you can do before you got to ask me if we should actually do it versus like do something else.Dharmesh [00:24:45]: So you know, we've already, let's like, we're leaving this, uh, in the code generation world, this kind of compressed, um, cycle time. Right. It's like, okay, we went from auto-complete, uh, in the GitHub co-pilot to like, oh, finish this particular thing and hit tab to a, oh, I sort of know your file or whatever. I can write out a full function to you to now I can like hold a bunch of the context in my head. Uh, so we can do app generation, which we have now with lovable and bolt and repletage. Yeah. Association and other things. So then the question is, okay, well, where does it naturally go from here? So we're going to generate products. Make sense. We might be able to generate platforms as though I want a platform for ERP that does this, whatever. And that includes the API's includes the product and the UI, and all the things that make for a platform. There's no nothing that says we would stop like, okay, can you generate an entire software company someday? Right. Uh, with the platform and the monetization and the go-to-market and the whatever. And you know, that that's interesting to me in terms of, uh, you know, what, when you take it to almost ludicrous levels. of abstract.swyx [00:25:39]: It's like, okay, turn it to 11. You mentioned vibe coding, so I have to, this is a blog post I haven't written, but I'm kind of exploring it. Is the junior engineer dead?Dharmesh [00:25:49]: I don't think so. I think what will happen is that the junior engineer will be able to, if all they're bringing to the table is the fact that they are a junior engineer, then yes, they're likely dead. But hopefully if they can communicate with carbon-based life forms, they can interact with product, if they're willing to talk to customers, they can take their kind of basic understanding of engineering and how kind of software works. I think that has value. So I have a 14-year-old right now who's taking Python programming class, and some people ask me, it's like, why is he learning coding? And my answer is, is because it's not about the syntax, it's not about the coding. What he's learning is like the fundamental thing of like how things work. And there's value in that. I think there's going to be timeless value in systems thinking and abstractions and what that means. And whether functions manifested as math, which he's going to get exposed to regardless, or there are some core primitives to the universe, I think, that the more you understand them, those are what I would kind of think of as like really large dots in your life that will have a higher gravitational pull and value to them that you'll then be able to. So I want him to collect those dots, and he's not resisting. So it's like, okay, while he's still listening to me, I'm going to have him do things that I think will be useful.swyx [00:26:59]: You know, part of one of the pitches that I evaluated for AI engineer is a term. And the term is that maybe the traditional interview path or career path of software engineer goes away, which is because what's the point of lead code? Yeah. And, you know, it actually matters more that you know how to work with AI and to implement the things that you want. Yep.Dharmesh [00:27:16]: That's one of the like interesting things that's happened with generative AI. You know, you go from machine learning and the models and just that underlying form, which is like true engineering, right? Like the actual, what I call real engineering. I don't think of myself as a real engineer, actually. I'm a developer. But now with generative AI. We call it AI and it's obviously got its roots in machine learning, but it just feels like fundamentally different to me. Like you have the vibe. It's like, okay, well, this is just a whole different approach to software development to so many different things. And so I'm wondering now, it's like an AI engineer is like, if you were like to draw the Venn diagram, it's interesting because the cross between like AI things, generative AI and what the tools are capable of, what the models do, and this whole new kind of body of knowledge that we're still building out, it's still very young, intersected with kind of classic engineering, software engineering. Yeah.swyx [00:28:04]: I just described the overlap as it separates out eventually until it's its own thing, but it's starting out as a software. Yeah.Alessio [00:28:11]: That makes sense. So to close the vibe coding loop, the other big hype now is MCPs. Obviously, I would say Cloud Desktop and Cursor are like the two main drivers of MCP usage. I would say my favorite is the Sentry MCP. I can pull in errors and then you can just put the context in Cursor. How do you think about that abstraction layer? Does it feel... Does it feel almost too magical in a way? Do you think it's like you get enough? Because you don't really see how the server itself is then kind of like repackaging theDharmesh [00:28:41]: information for you? I think MCP as a standard is one of the better things that's happened in the world of AI because a standard needed to exist and absent a standard, there was a set of things that just weren't possible. Now, we can argue whether it's the best possible manifestation of a standard or not. Does it do too much? Does it do too little? I get that, but it's just simple enough to both be useful and unobtrusive. It's understandable and adoptable by mere mortals, right? It's not overly complicated. You know, a reasonable engineer can put a stand up an MCP server relatively easily. The thing that has me excited about it is like, so I'm a big believer in multi-agent systems. And so that's going back to our kind of this idea of an atomic agent. So imagine the MCP server, like obviously it calls tools, but the way I think about it, so I'm working on my current passion project is agent.ai. And we'll talk more about that in a little bit. More about the, I think we should, because I think it's interesting not to promote the project at all, but there's some interesting ideas in there. One of which is around, we're going to need a mechanism for, if agents are going to collaborate and be able to delegate, there's going to need to be some form of discovery and we're going to need some standard way. It's like, okay, well, I just need to know what this thing over here is capable of. We're going to need a registry, which Anthropic's working on. I'm sure others will and have been doing directories of, and there's going to be a standard around that too. How do you build out a directory of MCP servers? I think that's going to unlock so many things just because, and we're already starting to see it. So I think MCP or something like it is going to be the next major unlock because it allows systems that don't know about each other, don't need to, it's that kind of decoupling of like Sentry and whatever tools someone else was building. And it's not just about, you know, Cloud Desktop or things like, even on the client side, I think we're going to see very interesting consumers of MCP, MCP clients versus just the chat body kind of things. Like, you know, Cloud Desktop and Cursor and things like that. But yeah, I'm very excited about MCP in that general direction.swyx [00:30:39]: I think the typical cynical developer take, it's like, we have OpenAPI. Yeah. What's the new thing? I don't know if you have a, do you have a quick MCP versus everything else? Yeah.Dharmesh [00:30:49]: So it's, so I like OpenAPI, right? So just a descriptive thing. It's OpenAPI. OpenAPI. Yes, that's what I meant. So it's basically a self-documenting thing. We can do machine-generated, lots of things from that output. It's a structured definition of an API. I get that, love it. But MCPs sort of are kind of use case specific. They're perfect for exactly what we're trying to use them for around LLMs in terms of discovery. It's like, okay, I don't necessarily need to know kind of all this detail. And so right now we have, we'll talk more about like MCP server implementations, but We will? I think, I don't know. Maybe we won't. At least it's in my head. It's like a back processor. But I do think MCP adds value above OpenAPI. It's, yeah, just because it solves this particular thing. And if we had come to the world, which we have, like, it's like, hey, we already have OpenAPI. It's like, if that were good enough for the universe, the universe would have adopted it already. There's a reason why MCP is taking office because marginally adds something that was missing before and doesn't go too far. And so that's why the kind of rate of adoption, you folks have written about this and talked about it. Yeah, why MCP won. Yeah. And it won because the universe decided that this was useful and maybe it gets supplanted by something else. Yeah. And maybe we discover, oh, maybe OpenAPI was good enough the whole time. I doubt that.swyx [00:32:09]: The meta lesson, this is, I mean, he's an investor in DevTools companies. I work in developer experience at DevRel in DevTools companies. Yep. Everyone wants to own the standard. Yeah. I'm sure you guys have tried to launch your own standards. Actually, it's Houseplant known for a standard, you know, obviously inbound marketing. But is there a standard or protocol that you ever tried to push? No.Dharmesh [00:32:30]: And there's a reason for this. Yeah. Is that? And I don't mean, need to mean, speak for the people of HubSpot, but I personally. You kind of do. I'm not smart enough. That's not the, like, I think I have a. You're smart. Not enough for that. I'm much better off understanding the standards that are out there. And I'm more on the composability side. Let's, like, take the pieces of technology that exist out there, combine them in creative, unique ways. And I like to consume standards. I don't like to, and that's not that I don't like to create them. I just don't think I have the, both the raw wattage or the credibility. It's like, okay, well, who the heck is Dharmesh, and why should we adopt a standard he created?swyx [00:33:07]: Yeah, I mean, there are people who don't monetize standards, like OpenTelemetry is a big standard, and LightStep never capitalized on that.Dharmesh [00:33:15]: So, okay, so if I were to do a standard, there's two things that have been in my head in the past. I was one around, a very, very basic one around, I don't even have the domain, I have a domain for everything, for open marketing. Because the issue we had in HubSpot grew up in the marketing space. There we go. There was no standard around data formats and things like that. It doesn't go anywhere. But the other one, and I did not mean to go here, but I'm going to go here. It's called OpenGraph. I know the term was already taken, but it hasn't been used for like 15 years now for its original purpose. But what I think should exist in the world is right now, our information, all of us, nodes are in the social graph at Meta or the professional graph at LinkedIn. Both of which are actually relatively closed in actually very annoying ways. Like very, very closed, right? Especially LinkedIn. Especially LinkedIn. I personally believe that if it's my data, and if I would get utility out of it being open, I should be able to make my data open or publish it in whatever forms that I choose, as long as I have control over it as opt-in. So the idea is around OpenGraph that says, here's a standard, here's a way to publish it. I should be able to go to OpenGraph.org slash Dharmesh dot JSON and get it back. And it's like, here's your stuff, right? And I can choose along the way and people can write to it and I can prove. And there can be an entire system. And if I were to do that, I would do it as a... Like a public benefit, non-profit-y kind of thing, as this is a contribution to society. I wouldn't try to commercialize that. Have you looked at AdProto? What's that? AdProto.swyx [00:34:43]: It's the protocol behind Blue Sky. Okay. My good friend, Dan Abramov, who was the face of React for many, many years, now works there. And he actually did a talk that I can send you, which basically kind of tries to articulate what you just said. But he does, he loves doing these like really great analogies, which I think you'll like. Like, you know, a lot of our data is behind a handle, behind a domain. Yep. So he's like, all right, what if we flip that? What if it was like our handle and then the domain? Yep. So, and that's really like your data should belong to you. Yep. And I should not have to wait 30 days for my Twitter data to export. Yep.Dharmesh [00:35:19]: you should be able to at least be able to automate it or do like, yes, I should be able to plug it into an agentic thing. Yeah. Yes. I think we're... Because so much of our data is... Locked up. I think the trick here isn't that standard. It is getting the normies to care.swyx [00:35:37]: Yeah. Because normies don't care.Dharmesh [00:35:38]: That's true. But building on that, normies don't care. So, you know, privacy is a really hot topic and an easy word to use, but it's not a binary thing. Like there are use cases where, and we make these choices all the time, that I will trade, not all privacy, but I will trade some privacy for some productivity gain or some benefit to me that says, oh, I don't care about that particular data being online if it gives me this in return, or I don't mind sharing this information with this company.Alessio [00:36:02]: If I'm getting, you know, this in return, but that sort of should be my option. I think now with computer use, you can actually automate some of the exports. Yes. Like something we've been doing internally is like everybody exports their LinkedIn connections. Yep. And then internally, we kind of merge them together to see how we can connect our companies to customers or things like that.Dharmesh [00:36:21]: And not to pick on LinkedIn, but since we're talking about it, but they feel strongly enough on the, you know, do not take LinkedIn data that they will block even browser use kind of things or whatever. They go to great, great lengths, even to see patterns of usage. And it says, oh, there's no way you could have, you know, gotten that particular thing or whatever without, and it's, so it's, there's...swyx [00:36:42]: Wasn't there a Supreme Court case that they lost? Yeah.Dharmesh [00:36:45]: So the one they lost was around someone that was scraping public data that was on the public internet. And that particular company had not signed any terms of service or whatever. It's like, oh, I'm just taking data that's on, there was no, and so that's why they won. But now, you know, the question is around, can LinkedIn... I think they can. Like, when you use, as a user, you use LinkedIn, you are signing up for their terms of service. And if they say, well, this kind of use of your LinkedIn account that violates our terms of service, they can shut your account down, right? They can. And they, yeah, so, you know, we don't need to make this a discussion. By the way, I love the company, don't get me wrong. I'm an avid user of the product. You know, I've got... Yeah, I mean, you've got over a million followers on LinkedIn, I think. Yeah, I do. And I've known people there for a long, long time, right? And I have lots of respect. And I understand even where the mindset originally came from of this kind of members-first approach to, you know, a privacy-first. I sort of get that. But sometimes you sort of have to wonder, it's like, okay, well, that was 15, 20 years ago. There's likely some controlled ways to expose some data on some member's behalf and not just completely be a binary. It's like, no, thou shalt not have the data.swyx [00:37:54]: Well, just pay for sales navigator.Alessio [00:37:57]: Before we move to the next layer of instruction, anything else on MCP you mentioned? Let's move back and then I'll tie it back to MCPs.Dharmesh [00:38:05]: So I think the... Open this with agent. Okay, so I'll start with... Here's my kind of running thesis, is that as AI and agents evolve, which they're doing very, very quickly, we're going to look at them more and more. I don't like to anthropomorphize. We'll talk about why this is not that. Less as just like raw tools and more like teammates. They'll still be software. They should self-disclose as being software. I'm totally cool with that. But I think what's going to happen is that in the same way you might collaborate with a team member on Slack or Teams or whatever you use, you can imagine a series of agents that do specific things just like a team member might do, that you can delegate things to. You can collaborate. You can say, hey, can you take a look at this? Can you proofread that? Can you try this? You can... Whatever it happens to be. So I think it is... I will go so far as to say it's inevitable that we're going to have hybrid teams someday. And what I mean by hybrid teams... So back in the day, hybrid teams were, oh, well, you have some full-time employees and some contractors. Then it was like hybrid teams are some people that are in the office and some that are remote. That's the kind of form of hybrid. The next form of hybrid is like the carbon-based life forms and agents and AI and some form of software. So let's say we temporarily stipulate that I'm right about that over some time horizon that eventually we're going to have these kind of digitally hybrid teams. So if that's true, then the question you sort of ask yourself is that then what needs to exist in order for us to get the full value of that new model? It's like, okay, well... You sort of need to... It's like, okay, well, how do I... If I'm building a digital team, like, how do I... Just in the same way, if I'm interviewing for an engineer or a designer or a PM, whatever, it's like, well, that's why we have professional networks, right? It's like, oh, they have a presence on likely LinkedIn. I can go through that semi-structured, structured form, and I can see the experience of whatever, you know, self-disclosed. But, okay, well, agents are going to need that someday. And so I'm like, okay, well, this seems like a thread that's worth pulling on. That says, okay. So I... So agent.ai is out there. And it's LinkedIn for agents. It's LinkedIn for agents. It's a professional network for agents. And the more I pull on that thread, it's like, okay, well, if that's true, like, what happens, right? It's like, oh, well, they have a profile just like anyone else, just like a human would. It's going to be a graph underneath, just like a professional network would be. It's just that... And you can have its, you know, connections and follows, and agents should be able to post. That's maybe how they do release notes. Like, oh, I have this new version. Whatever they decide to post, it should just be able to... Behave as a node on the network of a professional network. As it turns out, the more I think about that and pull on that thread, the more and more things, like, start to make sense to me. So it may be more than just a pure professional network. So my original thought was, okay, well, it's a professional network and agents as they exist out there, which I think there's going to be more and more of, will kind of exist on this network and have the profile. But then, and this is always dangerous, I'm like, okay, I want to see a world where thousands of agents are out there in order for the... Because those digital employees, the digital workers don't exist yet in any meaningful way. And so then I'm like, oh, can I make that easier for, like... And so I have, as one does, it's like, oh, I'll build a low-code platform for building agents. How hard could that be, right? Like, very hard, as it turns out. But it's been fun. So now, agent.ai has 1.3 million users. 3,000 people have actually, you know, built some variation of an agent, sometimes just for their own personal productivity. About 1,000 of which have been published. And the reason this comes back to MCP for me, so imagine that and other networks, since I know agent.ai. So right now, we have an MCP server for agent.ai that exposes all the internally built agents that we have that do, like, super useful things. Like, you know, I have access to a Twitter API that I can subsidize the cost. And I can say, you know, if you're looking to build something for social media, these kinds of things, with a single API key, and it's all completely free right now, I'm funding it. That's a useful way for it to work. And then we have a developer to say, oh, I have this idea. I don't have to worry about open AI. I don't have to worry about, now, you know, this particular model is better. It has access to all the models with one key. And we proxy it kind of behind the scenes. And then expose it. So then we get this kind of community effect, right? That says, oh, well, someone else may have built an agent to do X. Like, I have an agent right now that I built for myself to do domain valuation for website domains because I'm obsessed with domains, right? And, like, there's no efficient market for domains. There's no Zillow for domains right now that tells you, oh, here are what houses in your neighborhood sold for. It's like, well, why doesn't that exist? We should be able to solve that problem. And, yes, you're still guessing. Fine. There should be some simple heuristic. So I built that. It's like, okay, well, let me go look for past transactions. You say, okay, I'm going to type in agent.ai, agent.com, whatever domain. What's it actually worth? I'm looking at buying it. It can go and say, oh, which is what it does. It's like, I'm going to go look at are there any published domain transactions recently that are similar, either use the same word, same top-level domain, whatever it is. And it comes back with an approximate value, and it comes back with its kind of rationale for why it picked the value and comparable transactions. Oh, by the way, this domain sold for published. Okay. So that agent now, let's say, existed on the web, on agent.ai. Then imagine someone else says, oh, you know, I want to build a brand-building agent for startups and entrepreneurs to come up with names for their startup. Like a common problem, every startup is like, ah, I don't know what to call it. And so they type in five random words that kind of define whatever their startup is. And you can do all manner of things, one of which is like, oh, well, I need to find the domain for it. What are possible choices? Now it's like, okay, well, it would be nice to know if there's an aftermarket price for it, if it's listed for sale. Awesome. Then imagine calling this valuation agent. It's like, okay, well, I want to find where the arbitrage is, where the agent valuation tool says this thing is worth $25,000. It's listed on GoDaddy for $5,000. It's close enough. Let's go do that. Right? And that's a kind of composition use case that in my future state. Thousands of agents on the network, all discoverable through something like MCP. And then you as a developer of agents have access to all these kind of Lego building blocks based on what you're trying to solve. Then you blend in orchestration, which is getting better and better with the reasoning models now. Just describe the problem that you have. Now, the next layer that we're all contending with is that how many tools can you actually give an LLM before the LLM breaks? That number used to be like 15 or 20 before you kind of started to vary dramatically. And so that's the thing I'm thinking about now. It's like, okay, if I want to... If I want to expose 1,000 of these agents to a given LLM, obviously I can't give it all 1,000. Is there some intermediate layer that says, based on your prompt, I'm going to make a best guess at which agents might be able to be helpful for this particular thing? Yeah.Alessio [00:44:37]: Yeah, like RAG for tools. Yep. I did build the Latent Space Researcher on agent.ai. Okay. Nice. Yeah, that seems like, you know, then there's going to be a Latent Space Scheduler. And then once I schedule a research, you know, and you build all of these things. By the way, my apologies for the user experience. You realize I'm an engineer. It's pretty good.swyx [00:44:56]: I think it's a normie-friendly thing. Yeah. That's your magic. HubSpot does the same thing.Alessio [00:45:01]: Yeah, just to like quickly run through it. You can basically create all these different steps. And these steps are like, you know, static versus like variable-driven things. How did you decide between this kind of like low-code-ish versus doing, you know, low-code with code backend versus like not exposing that at all? Any fun design decisions? Yeah. And this is, I think...Dharmesh [00:45:22]: I think lots of people are likely sitting in exactly my position right now, coming through the choosing between deterministic. Like if you're like in a business or building, you know, some sort of agentic thing, do you decide to do a deterministic thing? Or do you go non-deterministic and just let the alum handle it, right, with the reasoning models? The original idea and the reason I took the low-code stepwise, a very deterministic approach. A, the reasoning models did not exist at that time. That's thing number one. Thing number two is if you can get... If you know in your head... If you know in your head what the actual steps are to accomplish whatever goal, why would you leave that to chance? There's no upside. There's literally no upside. Just tell me, like, what steps do you need executed? So right now what I'm playing with... So one thing we haven't talked about yet, and people don't talk about UI and agents. Right now, the primary interaction model... Or they don't talk enough about it. I know some people have. But it's like, okay, so we're used to the chatbot back and forth. Fine. I get that. But I think we're going to move to a blend of... Some of those things are going to be synchronous as they are now. But some are going to be... Some are going to be async. It's just going to put it in a queue, just like... And this goes back to my... Man, I talk fast. But I have this... I only have one other speed. It's even faster. So imagine it's like if you're working... So back to my, oh, we're going to have these hybrid digital teams. Like, you would not go to a co-worker and say, I'm going to ask you to do this thing, and then sit there and wait for them to go do it. Like, that's not how the world works. So it's nice to be able to just, like, hand something off to someone. It's like, okay, well, maybe I expect a response in an hour or a day or something like that.Dharmesh [00:46:52]: In terms of when things need to happen. So the UI around agents. So if you look at the output of agent.ai agents right now, they are the simplest possible manifestation of a UI, right? That says, oh, we have inputs of, like, four different types. Like, we've got a dropdown, we've got multi-select, all the things. It's like back in HTML, the original HTML 1.0 days, right? Like, you're the smallest possible set of primitives for a UI. And it just says, okay, because we need to collect some information from the user, and then we go do steps and do things. And generate some output in HTML or markup are the two primary examples. So the thing I've been asking myself, if I keep going down that path. So people ask me, I get requests all the time. It's like, oh, can you make the UI sort of boring? I need to be able to do this, right? And if I keep pulling on that, it's like, okay, well, now I've built an entire UI builder thing. Where does this end? And so I think the right answer, and this is what I'm going to be backcoding once I get done here, is around injecting a code generation UI generation into, the agent.ai flow, right? As a builder, you're like, okay, I'm going to describe the thing that I want, much like you would do in a vibe coding world. But instead of generating the entire app, it's going to generate the UI that exists at some point in either that deterministic flow or something like that. It says, oh, here's the thing I'm trying to do. Go generate the UI for me. And I can go through some iterations. And what I think of it as a, so it's like, I'm going to generate the code, generate the code, tweak it, go through this kind of prompt style, like we do with vibe coding now. And at some point, I'm going to be happy with it. And I'm going to hit save. And that's going to become the action in that particular step. It's like a caching of the generated code that I can then, like incur any inference time costs. It's just the actual code at that point.Alessio [00:48:29]: Yeah, I invested in a company called E2B, which does code sandbox. And they powered the LM arena web arena. So it's basically the, just like you do LMS, like text to text, they do the same for like UI generation. So if you're asking a model, how do you do it? But yeah, I think that's kind of where.Dharmesh [00:48:45]: That's the thing I'm really fascinated by. So the early LLM, you know, we're understandably, but laughably bad at simple arithmetic, right? That's the thing like my wife, Normies would ask us, like, you call this AI, like it can't, my son would be like, it's just stupid. It can't even do like simple arithmetic. And then like we've discovered over time that, and there's a reason for this, right? It's like, it's a large, there's, you know, the word language is in there for a reason in terms of what it's been trained on. It's not meant to do math, but now it's like, okay, well, the fact that it has access to a Python interpreter that I can actually call at runtime, that solves an entire body of problems that it wasn't trained to do. And it's basically a form of delegation. And so the thought that's kind of rattling around in my head is that that's great. So it's, it's like took the arithmetic problem and took it first. Now, like anything that's solvable through a relatively concrete Python program, it's able to do a bunch of things that I couldn't do before. Can we get to the same place with UI? I don't know what the future of UI looks like in a agentic AI world, but maybe let the LLM handle it, but not in the classic sense. Maybe it generates it on the fly, or maybe we go through some iterations and hit cache or something like that. So it's a little bit more predictable. Uh, I don't know, but yeah.Alessio [00:49:48]: And especially when is the human supposed to intervene? So, especially if you're composing them, most of them should not have a UI because then they're just web hooking to somewhere else. I just want to touch back. I don't know if you have more comments on this.swyx [00:50:01]: I was just going to ask when you, you said you got, you're going to go back to code. What

Before Patty Hearst appeared as an actress in John Waters' movies, she captivated America on the silver screen as a hostage terrorized by the Symbionese Liberation Army. When the newspaper heiress was kidnapped by the radical organization in 1974, the country sympathized with her plight. But after just a few months, the SLA's guns weren't pointing at Patty anymore. Suddenly, Patty was firing her own weapons during fistfights and bank robberies as a member of the same terrorist group that once kept her locked in a closet. In court, Patty claimed she was brainwashed and that she played along for her own safety. It's true that Patty Hearst gave the performance of a lifetime — but we still don't know which part of her life was the performance. This episode contains themes that may be disturbing to some listeners, including graphic depictions of violence. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

¡El único noticiero que te manda un abrazo está de aniversario! Este mes cumplimos CINCO AÑOS y para celebrarlo estamos organizando un minifestival con el EQUIPO DE LA ENCERRONA e INVITADOS SORPRESA. Entrada general: S/ 100.00 ¡50% de DESCUENTO para Premiums y Patreons! Para más información e inscripciones, ingresa aquí: Si eres patreon: https://www.patreon.com/posts/123811406 Si eres premium de Canal Ya: https://www.youtube.com/channel/UCP0AJJeNkFBYzegTTVbKhPg/community?lb=UgkxTx-hPMFZqgD6q47CKlOHezCUc8I7Worw Si aún no eres suscriptor: https://docs.google.com/forms/d/e/1FAIpQLSfsqVF-RugljrIROxOpewGgUF-TZ8ncDcf8ft4LzS5WmrwWxg/viewform?usp=sharing (Puede pedir loguearse en Google) *** ¡Buenos días! 🛑 Hasta aquí nomás. Santiváñez debe irse. Más de 1800 peruanos víctimas de homicidio en su gestión. El último: Paul Flores, de Armonía 10. ADEMÁS: La hipocresía del pacto. MIENTRAS TANTO: 🤳 La historia de los selfies de Dina enviados a su "amor". TAMBIÉN: Se confirman las CUATRO operaciones estéticas de la presidenta. Y... 🎭 Sobre la ola intolerante y conservadora contra el arte –y en especial, contra el teatro– conversamos con Alberto ísola y Pepa Duarte. **** ¿Te gustó este episodio? ¿Buscas las fuentes de los datos mencionados hoy? SUSCRÍBETE en http://patreon.com/ocram para acceder a nuestros GRUPOS EXCLUSIVOS de Telegram y WhatsApp. También puedes hacerte MIEMBRO de nuestro canal de YouTube aquí https://www.youtube.com/channel/UCP0AJJeNkFBYzegTTVbKhPg/join **** Únete a nuestro CANAL de WhatsApp aquí https://whatsapp.com/channel/0029VaAgBeN6RGJLubpqyw29 **** Para más información legal: http://laencerrona.pe

Do you find yourself saying: “Hey, what's the big idea with that newfangled whole blood in the refrigerator next to the trauma bay?”  Like using whole blood but not sure why?  Don't like using whole blood but not sure why? Join us for a 30 minute power session in whole blood where we try to get you the information you need to know! Hosts: - Michael Cobler-Lichter, MD, PGY4/R2: University of Miami/Jackson Memorial Hospital/Ryder Trauma Center @mdcobler (X/twitter) - Eva Urrechaga, MD, PGY-8, Vascular Surgery Fellow University of Pennsylvania Recent graduate of University of Miami/Jackson Memorial Hospital/Ryder Trauma Center General Surgery Residency @urrechisme (X/twitter) - Eugenia Kwon, MD, Trauma/Surgical Critical Care Attending: Loma Linda University  Recent graduate of University of Miami/Jackson Memorial Hospital/Ryder Trauma Center Trauma/CC Fellowship - Jonathan Meizoso, MD, MSPH Assistant Professor of Surgery, 6 years in practice University of Miami/Jackson Memorial Hospital/Ryder Trauma Center @jpmeizoso (twitter) Learning Objectives: - Describe the proposed benefits of whole blood resuscitation in trauma -  Identify current problems with synthesizing the existing literature on whole blood resuscitation in trauma - Propose needed areas for future research regarding whole blood resuscitation in trauma Quick Hits: 1. There is significant heterogeneity in study design across whole blood resuscitation studies, complicating comparison 2.  There is likely a mortality benefit to whole blood resuscitation in trauma, however this is likely dependent on the specific population 3. Future research directions should focus on prospective randomized work to try and better quantify the exact benefit of whole blood, and determine in which populations this benefit is actually realized References 1.     Hazelton JP, Ssentongo AE, Oh JS, Ssentongo P, Seamon MJ, Byrne JP, Armento IG, Jenkins DH, Braverman MA, Mentzer C, Leonard GC, Perea LL, Docherty CK, Dunn JA, Smoot B, Martin MJ, Badiee J, Luis AJ, Murray JL, Noorbakhsh MR, Babowice JE, Mains C, Madayag RM, Kaafarani HMA, Mokhtari AK, Moore SA, Madden K, Tanner A 2nd, Redmond D, Millia DJ, Brandolino A, Nguyen U, Chinchilli V, Armen SB, Porter JM. Use of Cold-Stored Whole Blood is Associated With Improved Mortality in Hemostatic Resuscitation of Major Bleeding: A Multicenter Study. Ann Surg. 2022 Oct 1;276(4):579-588. doi: 10.1097/SLA.0000000000005603. Epub 2022 Jul 18. PMID: 35848743. https://pubmed.ncbi.nlm.nih.gov/35848743/ 2.     Sperry JL, Cotton BA, Luther JF, Cannon JW, Schreiber MA, Moore EE, Namias N, Minei JP, Wisniewski SR, Guyette FX; Shock, Whole Blood, and Assessment of Traumatic Brain Injury (SWAT) Study Group. Whole Blood Resuscitation and Association with Survival in Injured Patients with an Elevated Probability of Mortality. J Am Coll Surg. 2023 Aug 1;237(2):206-219. doi: 10.1097/XCS.0000000000000708. Epub 2023 Apr 11. PMID: 37039365; PMCID: PMC10344433. https://pubmed.ncbi.nlm.nih.gov/37039365/ 3.     Meizoso JP, Cotton BA, Lawless RA, et al. Whole blood resuscitation for injured patients requiring transfusion: A systematic review, meta-analysis, and practice management guideline from the Eastern Association for the Surgery of Trauma. J Trauma Acute Care Surg. 2024;97(3):460-470. doi:10.1097/TA.0000000000004327 https://pubmed.ncbi.nlm.nih.gov/38531812/ Please visit https://behindtheknife.org to access other high-yield surgical education podcasts, videos and more.   If you liked this episode, check out our recent episodes here: https://app.behindtheknife.org/listen