Podcasts about Ris

Another pioneer in the field of play therapy joins Lisa for this next episode. Lisa is super excited to be joined by Dr. Risë VanFleet (learn about her amazing background below*) for a conversation about Filial Therapy and how parents and caregivers can become a change agent for their child. Join Risë and Lisa in this insightful discussion that will enhance your child client's therapy experience through their relationship with their parent/caregiver and deepen your commitment to the model. You'll also hear how Risë entered the field of play therapy and learn … The history of Filial Therapy and the theoretical elements that make the model successful; How Filial Therapy is a psychoeducational model (vs. a medical model) The 7 key aspects that make up Filial Therapy and create the elegance of the model; How parents/caregivers become the primary change agent for their child; and How to combine Filial Therapy with other therapeutic interventions. *Dr. Risë VanFleet is a Licensed Psychologist (PA), Registered Play Therapist-Supervisor and specializes in Animal Assisted Play Therapy™, Filial Therapy, play therapy, chronic medical illness in families, disaster mental health, complex trauma and attachment issues, as well as animal welfare and behavior.  She's also the President of the Family Enhancement & Play Therapy Center, Inc., in Boiling Springs, Pennsylvania, an organization specializing in the training and supervision of child, family, and play therapy professionals. She is the founder and president of the International Institute for Animal Assisted Play Therapy®. Podcast Resources:  Synergetic Play Therapy Institute Synergetic Play Therapy Learning Website FREE Resources to support you on your play therapy journey  Aggression in Play Therapy: A Neurobiological Approach to Integrating Intensity * If you enjoy this podcast, please give us a five-star rating and review on Apple Podcast, subscribe wherever you listen to podcasts, and invite your friends/fellow colleagues to join us.

Major sits down with author Jack Farrell to discuss his most recent book "Ted Kennedy: A Life," a biography of the so-called Lion of the Senate. Kennedy served nearly 47 years in the chamber, championing liberal policies. Farrell writes that Kennedy suffered from chronic self-doubt which, in part, sunk his 1980 bid for the White House. Farrell also discusses his books on Richard Nixon and Clarence Darrow. We're at Ris in Washington's West End. Join us!See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Dr. Robert Malone is one of the co-inventors of the mRNA technology behind COVID jabs and #1 Wall Street Journal bestselling author of the new book Lies My Government Told Me: And the Better Future Coming.   He joins the show to discuss how he has built up tens of thousands of paying subscribers on his Substack newsletter (https://rwmalonemd.substack.com/) and millions of followers on alternative social media like WhatsApp, TikTok, Gettr, Gab, and Truth Social, despite being deplatformed and censored by mainstream news and social media because of his outspoken publishing of data and evidence regarding mRNA vaccines - the very invention he helped create. Malone is vaccinated himself, and nearly died from COVID before the vaccines were out in 2021.   Despite the negative publicity, Dr. Malone still advises, consults, and is on the payroll of tens of healthcare, medical, and pharmaceutical companies worldwide, as well as Wall Street research firms. Business continues to improve for him to the point where he is not taking on any new contracts or clients.   Dr. Malone tops off the discussion by advising work from homers on how to best take care of their hearts and overall health - particularly if you're vaccinated or previously infected with COVID - including getting cardiac troponin and Vitamin D levels tested.   Websites:  www.rwmalonemd.com www.rwmalonemd.substack.com www.MaloneInstitute.org     Moderna Research:   https://abcnews.go.com/Health/wireStory/sweden-suspends-moderna-vaccine-young-people-80432244   https://medicalxpress.com/news/2021-10-iceland-halts-moderna-jabs-heart-inflammation.html   https://www.dailymail.co.uk/health/article-10182673/amp/France-latest-European-nation-telling-people-age-30-NOT-Moderna-vaccine.html   https://www.reuters.com/world/europe/finland-pauses-use-moderna-covid-19-vaccine-young-men-2021-10-07/     Ivermectin Research:   https://youtu.be/fqb6NY4Yi74   https://m.theepochtimes.com/new-study-links-ivermectin-to-large-reductions-in-covid-19-deaths_3867278.html   https://buffalonews.com/news/local/after-judge-orders-hospital-to-use-experimental-covid-19-treatment-woman-recovers/article_a9eb315c-5694-11eb-aac5-53b541448755.html   https://journals.lww.com/americantherapeutics/fulltext/2021/08000/ivermectin_for_prevention_and_treatment_of.7.aspx   https://m.jpost.com/health-science/israeli-scientist-says-covid-19-could-be-treated-for-under-1day-675612   http://thehealthedge.com/japanese-medical-association-now-endorses-ivermectin-for-covid-19/   https://ivmmeta.com   https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0247163   https://www.medrxiv.org/content/10.1101/2021.01.05.21249310v1   https://journals.sagepub.com/doi/pdf/10.1177/03000605211013550   https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3765018   https://www.ncbi.nlm.nih.gov/labs/pmc/articles/PMC7816625/ https://ejmo.org/pdf/A%20Comparative%20Study%20on%20IvermectinDoxycycline%20and%20HydroxychloroquineAzithromycin%20Therapy%20on%20COVID19%20Patients-16263.pdf   https://www.ijidonline.com/article/S1201-9712(20)32506-6/fulltext   https://www.fox32chicago.com/news/illinois-family-credits-ivermectin-with-saving-life-of-father-hospitalized-with-covid-19   https://www.researchgate.net/publication/356962821_Ivermectin_prophylaxis_used_for_COVID-19_reduces_COVID-19_infection_and_mortality_rates_A_220517-subject_populational-level_retrospective_citywide   https://www.cureus.com/articles/82162-ivermectin-prophylaxis-used-for-covid-19-a-citywide-prospective-observational-study-of-223128-subjects-using-propensity-score-matching   https://amgreatness.com/2022/01/18/new-peer-reviewed-study-shows-ivermectin-significantly-reduces-covid-infections-hospitalization-and-mortality-rates/   https://www.reuters.com/business/healthcare-pharmaceuticals/japans-kowa-says-ivermectin-effective-against-omicron-phase-iii-trial-2022-01-31/   https://fism.tv/peer-reviewed-study-ivermectin-reduced-covid-19-mortality-by-92/     mRNA Shot Research:   https://www.telegraph.co.uk/news/2021/09/09/teenage-boys-risk-vaccines-covid/   1. Exploring the relationship between all-cause and cardiac-related mortality following COVID-19 vaccination or infection in Florida residents - study conducted by the Surgeon General of Florida: Primary findings: “In the 28 days following vaccination, a statistically significant increase in cardiac-related deaths was detected for the entire study population (RI = 1.07, 95% CI = 1.03 - 1.12). Stratifying by age group revealed RIs were significantly higher for age groups 25 - 39 (RI = 2.16, 95% CI = 1.35 - 3.47) and 60 or older (RI = 1.05, 95% CI = 1.01 - 1.10).” https://floridahealthcovid19.gov/wp-content/uploads/2022/10/20221007-guidance-mrna-covid19-vaccines-analysis.pdf?utm_medium=email&utm_source=govdelivery   2. Clinical cardiovascular emergencies and the cellular basis of COVID-19 vaccination: Primary findings: “COVID-19 vaccines evoke rare but fatal thrombotic events, whereas messenger RNA55based vaccines appear to be associated with risks of pericarditis/myocarditis, with the latter being more predominant in young adults following the second dose.” https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9444584/pdf/main.pdf   3. Cardiac complications following mRNA COVID-19 vaccines: A systematic review of case reports and case series: Primary findings: “Myocarditis/myopericarditis and pericarditis were the most common adverse events among the 243 reported cardiac complications, post mRNA COVID-19 vaccination. Males with a median age of 21 years had the highest frequency of myocarditis.” https://pubmed.ncbi.nlm.nih.gov/34921468/   4. Postmarketing active surveillance of myocarditis and pericarditis following vaccination with COVID-19 mRNA vaccines in persons aged 12 to 39 years in Italy: Primary findings: “…increased risk of myocarditis/pericarditis was associated with the second dose of BNT162b2 and both doses of mRNA-1273. The highest risks were observed in males of 12 to 39 years and in males and females 18 to 29 years vaccinated with mRNA-1273.” https://pubmed.ncbi.nlm.nih.gov/35900992/   5. Serious adverse events of special interest following mRNA COVID-19 vaccination in randomized trials in adults: Primary findings: “Pfizer and Moderna mRNA COVID-19 vaccines were associated with an excess risk of serious adverse events of special interest of 10.1 and 15.1 per 10,000 vaccinated over placebo baselines of 17.6 and 42.2 (95 % CI −0.4 to 20.6 and −3.6 to 33.8), respectively.” https://www.sciencedirect.com/science/article/pii/S0264410X22010283?ref=cra_js_challenge&fr=RR-1   6. Autopsy-based histopathological characterization of myocarditis after anti-SARS-CoV-2-vaccination: Primary findings: “Overall, autopsy findings indicated death due to acute arrhythmogenic cardiac failure. Thus, myocarditis can be a potentially lethal complication following mRNA-based anti-SARS-CoV-2 vaccination.” https://link.springer.com/article/10.1007/s00392-022-02129-5#Sec3   7. SARS-CoV-2 Vaccination and Myocarditis in a Nordic Cohort Study of 23 Million Residents Primary findings: “In a cohort study of 23.1 million residents across 4 Nordic countries, risk of myocarditis after the first and second doses of SARS-CoV-2 mRNA vaccines was highest in young males aged 16 to 24 years after the second dose. For young males receiving 2 doses of the same vaccine, data were compatible with between 4 and 7 excess events in 28 days per 100 000 vaccinees after second-dose BNT162b2, and between 9 and 28 per 100 000 vaccinees after second-dose mRNA-1273.” https://jamanetwork.com/journals/jamacardiology/fullarticle/2791253   8. Booster Vaccination with SARS-CoV-2 mRNA Vaccines and Myocarditis Risk in Adolescents and Young Adults: A Nordic Cohort Study of 8.9 Million Residents: Primary findings: “Our results suggest that a booster dose is associated with increased myocarditis risk in male adolescents and young male adults.” https://www.medrxiv.org/content/10.1101/2022.12.16.22283603v1   In addition to these studies, the FDA has cautioned that some COVID-19 vaccines carry the risk of myocarditis and pericarditis, especially in young men. https://www.fda.gov/news-events/press-announcements/coronavirus-covid-19-update-june-25-2021   Though not related to young men, on January 13, 2023, CDC cautioned that Pfizer/BioNTech's Bivalent booster vaccine might increase the risk of ischemic stroke in people over 65, a condition in which blood clots of other particles block the blood vessels to the brain. While the concern relates to those over 65, this new safety signal illustrates that we do not know the mid- or long-term health outcomes of the COVID-19 vaccines. https://ktxs.com/news/nation-world/cdc-flags-possible-safety-issue-with-updated-pfizer-covid-19-booster-ischemic-stroke-potential-health-risk-senior-fellow-cato-institute-dr-jeffrey-singer-omicron-variants-protection   Although some have suggested that myocarditis and pericarditis are elevated after a case of COVID-19, a large study of about 600,000 adults concludes that is not the case. The study, “The Incidence of Myocarditis and Pericarditis in Post COVID-19 Unvaccinated Patients-A Large Population-Based Study” stated, “We did not observe an increased incidence of neither pericarditis nor myocarditis in adult patients recovering from COVID-19 infection.” https://pubmed.ncbi.nlm.nih.gov/35456309/

We're back with another insightful episode recorded at last month's NRF "Big Show." This time our focus is on how entrepreneurs bring their ideas to market, secure venture capital funding, and fight through all the challenges to create a sustainable, remarkable business.We're fortunate to have two great female founders join us to share their wisdom. Michelle Bacharach heads up FindMine, the AI powered company that helps consumers and brands find their best looks. Katie Hotze founded and leads Grocery Shopii, an innovative technology platform that powers digital meal planning. In a wide ranging discussion we learn about the inspiration for their companies, how they've funded and scaled them, and explore some of the unique challenges faced by founders from under-represented communities. But first we give our perspectives on the most remarkable retail news of the week, with a fairly deep dive into Amazon's concerning quarterly earnings report. We also give our quick takes on news about Sam's Club's expansion plans, a very strong US jobs report, Tom Kingsbury being named "permanent" CEO at Kohl's, Ryan Cohen's setting his activist sights on Nordstrom, Bed, Bath & Beyond's looming bankruptcy filing, and how Rent the Runway has kicked the debt can down the road. ******We're headed to Las Vegas in March for another edition of Shoptalk. Retailers and brands can get a Shoptalk ticket for a reduced rate of just $1950 rate here using our special discount code RBREMARK1950.About MichelleMichelle is CEO and Co-Founder of FINDMINE, an award winning software platform that uses machine learning to scale product curation for the world's top retailers. As a product and strategy expert, Michelle is experienced in growing companies by launching software, apps and websites to millions of people, putting together joint ventures, and conceiving of new products. Michelle has shared her expertise with thousands of leaders in retail and technology as a speaker at SXSW, the National Retail Federations' Retail's Big Show and Shop.org, Intel's Shift, Women in Machine Learning and Data Science, and many others.  About KatieNamed a Top 10 Women in Grocery Tech by RIS, Katie Hotze is an innovative leader and entrepreneur with over two decades of experience in digital marketing, data analytics and business strategy. Katie is the founder and CEO of Grocery Shopii, a Charlotte-based startup that solves a $550B problem in the CPG & Retail industry by reducing cart abandonment with machine learning. Grocery Shopii uses recipes as a recommendation engine to expedite online grocery shopping inside the shopping journey.Prior to Grocery Shopii, Katie spent 20 years in management and technology consulting where she led global marketing teams for Mercer, the world's largest HR consultancy, and BearingPoint. She holds an M.B.A. and Business Analytics certification from William & Mary, and a B.S. in Marketing from Virginia Commonwealth University. In 2018, Katie was a Direct Marketing News (DMN) 40-Under-40 Award Recipient. She's also been awarded the Top Women in Grocery honor by Progressive Grocer. Today, she is a regular speaker on both digital and social media topics at conferences in the marketing and grocery retail spaces.A resident of Charlotte, N.C., Katie is a graduate of UNC-Charlotte's Ventureprise entrepreneurial program and is an active participant in the city's tech community.About UsSteve Dennis is an advisor, keynote speaker and author on strategic growth and business innovation. You can learn more about Steve on his       website.    The expanded and revised edition of his bestselling book  Remarkable Retail: How To Win & Keep Customers in the Age of Disruption is now available at  Amazon or just about anywhere else books are sold. Steve regularly shares his insights in his role as a      Forbes senior contributor and on       Twitter and       LinkedIn. You can also check out his speaker "sizzle" reel      here.Michael LeBlanc  is the Founder & President of M.E. LeBlanc & Company Inc and a Senior Advisor to Retail Council of Canada as part of his advisory and consulting practice.   He brings 25+ years of brand/retail/marketing & eCommerce leadership experience, and has been on the front lines of retail industry change for his entire career.  Michael is the producer and host of a network of leading podcasts including Canada's top retail industry podcast,       The Voice of Retail, plus  Global eCommerce Leaders podcast, and The Food Professor  with Dr. Sylvain Charlebois.    You can learn more about Michael   here  or on     LinkedIn. Be sure and check out Michael's latest venture for fun and influencer riches - Last Request Barbecue,  his YouTube BBQ cooking channel!

Nytt år, nytt hjem og ny episode! Endelig er jeg på plass i Oslo og tar deg med gjennom mine refleksjoner om julen og julepresset, flyttekaos og folk som ikke dukker opp, og en ideell nyttårsfeiring. En ny start på en ny tilværelse her i Oslo, og forhåpentlig mer innhold fra meg fremover.-Min andre podcast "Virkelig Grusomt" finnes i alle podcast apper-YouTube: www.youtube.com/tonesabro-Støtt meg på Patreon: www.patreon.com/tonesabro-Ris og ros: nervemedtone@gmail.com -Sosiale medier: @nervemedtone / @tonesabro

Link to bioRxiv paper: http://biorxiv.org/cgi/content/short/2023.01.04.522780v1?rss=1 Authors: Bach, M., Bergs, A., Mulcahy, B., Zhen, M., Gottschalk, A. Abstract: To survive in a complex environment, animals must respond to external cues, e.g., to escape threats or to navigate towards favorable locations. Navigating requires transition between motor states, e.g. switching from forward to backward movement. Here, we investigated how two classes of interneurons, RIS and RIM, fine-tune this transition in the nematode C. elegans. By Ca2+ imaging in freely moving animals, we found that RIS gets active slightly before RIM and likely biases decision-making towards a reversal. In animals lacking RIS, we observed lowered Ca2+-levels in RIM prior to a reversal. Combined photo-stimulation and voltage imaging revealed that FLP-11, a neuropeptide released by RIS, has an excitatory effect on RIM, while tyramine, released from RIM, inhibits RIS. Voltage imaging of intrinsic activity provided evidence for tight electrical coupling between RIS and RIM via gap junctions harboring UNC-7 innexins. Asymmetric junctional current flow was observed from RIS to RIM, and vice versa. We propose that the interplay of RIS and RIM is based on concerted electrical and chemical signaling, with a fast junctional current exchange early during the transition from forward to backward movement, followed by chemical signaling, likely during reversal execution. Copy rights belong to original authors. Visit the link for more info Podcast created by Paper Player, LLC

durée : 00:39:29 - Côté saveurs - France Bleu Picardie

Achieving net zero carbon by 2050 will need more electrification of the GB railway. This episode looks at new and updated standards that don't just make the requirements easier to understand. They also have the potential to deliver cost savings of well over £27m over five years. So, if you design OLE or AC-powered trains, you'll want to listen to this episode.01:24    About Mike Tatton02:14    How standards are changed03:43    Drivers of change for electrification standards05:33    Who will be using these standards06:42    What's changed in GLRT1210, issue 3 12:03    What's new in RIS-1853-ENE13:43    The new energy standards summarised14:29    About Darren Fitzgerald15:05    Key changes to the rolling stock RGS and the new RIS16:21    New vehicle bonding requirements17:25    Change to the cant rail warning line requirement18:38    Main benefits from changes to these standards19:45    Potential financial benefits from the changes21:00    Summary and close Resources mentioned in this episode:December 2022 webinar recording  https://rssb.videomarketingplatform.co/video/81831824/10:57/ac-current-collection-standards Register for the extended webinar at 11.00, 20 February 2023 https://www.eventbrite.co.uk/e/ac-standards-rolling-stock-and-electrification-registration-477392863907?ReturnUrl=https%3a%2f%2fwww.rssb.co.uk%2fservices-and-resources%2fservices%2fevents-and-webinars GLRT1210, AC Energy Subsystem and Interfaces to Rolling Stock Subsystem, issue 3 https://www.rssb.co.uk/standards-catalogue/CatalogueItem/glrt1210-iss-3 RIS-1853-ENE, AC Energy Subsystem and Interfaces to Rolling Stock Subsystem, issue 1 https://www.rssb.co.uk/standards-catalogue/CatalogueItem/ris-1853-ene-iss-1 RGS-2111, Rolling Stock Subsystem and Interfaces to AC Energy Subsystem, issue 3 https://www.rssb.co.uk/standards-catalogue/CatalogueItem/gmrt2111-iss-3 RIS-2715-RST, Rolling Stock Subsystem and Interfaces to AC Energy Subsystem, issue 1 https://www.rssb.co.uk/standards-catalogue/CatalogueItem/ris-2715-rst-iss-1 

This week the Daily Pause will take on a little different format fitting for the season we are in. Each day we will open with prayer to immerse in the presence and love of God … then we will engage with a well-known Christmas Carol, hearing something of the story behind the carol as well as the deep soul stirring theology of the lyrics. We will get to embrace these age tested songs in a fresh way giving the Holy Spirit ample space time and truth to restore our souls in this unique season. - Hark! the herald angels sing, “Glory to the new-born King; Peace on earth, and mercy mild; God and sinners reconciled.” Joyful, all ye nations, rise, Join the triumph of the skies; With angelic hosts proclaim, “Christ is born in Bethlehem.” 2 Christ, by highest heav'n adored, Christ, the everlasting Lord: Late in time behold Him come, Offspring of a virgin's womb. Veiled in flesh the Godhead see, Hail th' incarnate Deity! Pleased as man with man to dwell, Jesus our Immanuel. 3 Hail the heav'n-born Prince of Peace! Hail the Sun of righteousness! Light and life to all He brings, Ris'n with healing in His wings: Mild He lays His glory by, Born that man no more may die; Born to raise the sons of earth; Born to give them second birth.

Marco Aurélio Mello, Jair Bolsonaro, Luiz Felipe Pondé, Augusto de Franco e Antônio Risério. Esta é a escalação do primeiro dos dois episódios da retrospectiva da primeira temporada do podcast Claudio Dantas Talks, que reúne o melhor dos programas sobre política do ano.  O ex-ministro do Supremo fala sobre como "a sociedade não se conformou com o sepultamento da Lava Jato", enquanto o presidente da República antecipa seus planos para o caso da derrota que viria a ocorrer semanas depois. O filósofo analisa a ascensão dos movimentos de direita no Brasil, o escritor explica como "Bolsonaro desorganizou o sistema imunológico da democracia brasileira” e o antropólogo sugere ao presidente eleito Lula que crie o "Ministério dos Povos Imaginários”. Inscreva-se e receba a newsletter:  https://bit.ly/2Gl9AdL Confira mais notícias em nosso site:  https://www.oantagonista.com​ Acompanhe nossas redes sociais:  https://www.fb.com/oantagonista​ https://www.twitter.com/o_antagonista ​https://www.instagram.com/o_antagonista https://www.tiktok.com/@oantagonista_oficial No Youtube deixe seu like e se inscreva no canal: https://www.youtube.com/c/OAntagonista  

For our final episode of 2022 and Christmas special, Panfa and Papa are joined by cult hero The Weg for a discussion on the year, instagram heroes and the ultimate discussion. Which biccies pair best with RIS? There are opinions. There are disagreements. But most of all...there is grog.Become a Friend Of The Show and support us on our Patreon! If you're listening on Spotify or  Apple Podcasts, please be sure to rate, subscribe and leave us a review.  It's free and helps other beer lovers discover the podcast!

durée : 00:20:59 - Côté Saveurs - France Bleu Cotentin

Nas ruas, nas instituições de ensino, nas empresas, em todos os lugares durante todo o mês de dezembro o Natal é celebrado neste pequeno país Nórdico de quase 6 milhões de habitantes. Fernanda Melo Larsen, correspondente da RFI em Copenhague O Jul, Natal em dinamarquês, é anterior à celebração de Natal do mundo cristão. Antes do cristianismo, Jul era festejado pelos dinamarqueses e escandinavos na lua cheia mais fria do ano. O cristianismo foi introduzido na Dinamarca por volta do ano de 965, e a partir disso, o Natal cristão e as tradições pagãs dinamarqueses se fundiram. O primeiro dia do advento, que acontece quatro domingos antes do Natal, marca o início da temporada natalina. É quando muitas famílias vão para a floresta escolher o próprio pinheiro que será cortado e ficará no quintal esperando a semana do Natal para ser decorado e colocado na sala de estar. Dentro de casa a vela do advento é acesa todos os dias, e outras velas iluminam o ambiente. A decoração natalina é feita com corações de papel, com muitos duendes e elfos. Já os anjos e os presépios com a figura do menino Jesus são raros por aqui. De acordo com Marie Nielsen, professora associada e vice-diretora da Escola de Cultura e Sociedade do Departamento de Estudos de Religião da Universidade de Aarhus, a maioria dos dinamarqueses vê suas próprias práticas como algo relacionado às tradições familiares e nacionais. “Umas das coisas que nós vemos na atualidade no país é que muitos muçulmanos que vivem na Dinamarca celebram o Natal, porque o Natal é algo grandioso na Dinamarca. Você não tem como evitar, é celebrado nas escolas, as crianças nos jardins de infância visitam as igrejas. É impossível não viver o Natal na Dinamarca, ele está nas lojas, no trabalho, na mídia, em todos os lugares”, explica Marie Nilsen. Celebração em sociedade Nas ruas, os mercados de Natal são um convite para quem passa tomar um Gløgg, uma bebida feita com vinho misturado a amêndoas e passas, que é servido quente. Nos cafés de todo o país é possível consumir o æbleskiver, um bolinho de maçã que se come com geleia e açúcar de confeiteiro. Já no ambiente de trabalho dinamarquês, o Julefrokost – almoço de Natal – pode durar o dia todo começando na hora do almoço com muita comida e bebida. Discretos e silenciosos no cotidiano, nestes eventos regados a muito álcool os dinamarqueses desfrutam o momento numa atmosfera – hyggeligt – que significa aconchegante em tradução livre. As instituições de ensino celebram o mês natalino com canções tradicionais deste período do ano.   As crianças recebem também um calendário do Advento, que contém 24 presentes simbólicos. A brasileira Miriam Jakobsen, casada com um dinamarquês e mãe de duas filhas, diz gostar do estilo de celebração de Natal do país que ela escolheu para viver há 12 anos. “Hoje com as meninas eu acho maravilhoso porque a gente vive aqui, porque mais que elas tenham muita coisa do Brasil aqui em casa, a gente faz muita coisa brasileira, mas o que pega mesmo é a cultura dinamarquesa, porque é aqui que elas vivem. É o que elas compartilham na escola, é o que elas conversam com as amiguinhas, e elas adoram dançar ao redor da árvore, é um momento divertido, eu gosto também” conclui Miriam Jakobsen. Feriado de Natal Lojas, estabelecimentos comerciais, empresas encerram as atividades nos dias 24, 25 e 26 de dezembro. Até mesmo o transporte público funciona com capacidade reduzida no dia 24, parando às 22h para que todas as pessoas tenham a chance de participar do jantar em família. A Ceia de Natal neste país escandinavo é o ponto mais tradicional da festa, a comida é servida depois das cinco da tarde. No cardápio o pato assado, o Flæskesteg – o lombo de porco assado com torresmo crocante e ameixas, batatas cozidas, com um molho escuro, batatas caramelizadas, e repolho vermelho em conserva. O jantar é seguido pela sobremesa. Ris a l'Amande - um tipo de arroz doce feito com creme de leite, molho de cereja e amêndoas. Depois do jantar e antes da troca de presentes, é o momento de adultos e crianças dançarem de mãos dadas ao redor da árvore de Natal e cantarem canções natalinas como Noite Feliz. O dia de Natal é um momento muito tranquilo para a maioria das famílias, pois as visitas mais formais e outras atividades só são agendadas a partir do dia 26 de dezembro.

Major sits down with colleagues Cara Korte and Bo Erickson, the creative forces behind "Missing Justice," a new CBS News podcast that delves into the missing and murdered indigenous peoples crisis in the United States. The podcast focuses on Christy Woodenthigh, a mother and member of the Northern Cheyenne Tribe in Montana, who died in March 2020. Korte and Erickson explain why her family and friends say justice was not served. Join us at Ris in Washington, DC's West End neighborhood.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

I det här avsnittet kommer vi att lära känna 9-åriga Therese Johannessen från Drammen, cirka 20 mil från Mariannes hemstad Risör. Kvällen den tredje juli 1988 försvinner Therese Johannessen från sitt bostadsområde Fjell. Manus av Sofie Karlsson.Du hittar Mördarpodden där du hittar Olösta Mord. Du kan också följa Mördarpoddens instagram här: https://www.instagram.com/mordarpodden/Vill du att Olösta mord ska komma ut varje vecka? Du kan påverka genom att dela podden med alla du känner som kan tänkas vara intresserade och/eller sponsra via Patreon; https://www.patreon.com/olostamord Välj valfri summa du vill sponsra med per avsnitt på Patreon. Når vi 2000 kr per avsnitt kommer podden att komma ut varje torsdag istället för varannan vecka.Swishdonationer till 070-7715864 fungerar fortfarande. Märk swishen "Olösta mord".Har du teorier om vad som hänt i fallen som vi tagit upp i podden? Skicka dem till: zimwaypodcast@gmail.com så kommer vi ta upp dem i kommande avsnitt. Det här är en podd av Dan Hörning.Följ Dan Hörning här:Twitter: @danhorningInstagram: https://www.instagram.com/dan_horning/?hl=enYoutube: https://www.youtube.com/channel/UCV2Qb7SmL9mejE5RCv1chwgMail: zimwaypodcast@gmail.comFacebook: https://www.facebook.com/Olostamord/ Hosted on Acast. See acast.com/privacy for more information.

This week Dusty and Matt sit down with the Queen of Sales, Risë Labig who has worked at the Ohio Ag Net and Ohio Country journal for the past several years as the marketing specialist. Risë talks about her journey of being a woman in agriculture and how she kept her faith during her career. Matt also chats with Anne Thompson of the National Corn Growers Association and Luke Crumley of the Ohio Corn and Wheat Growers Association on politics and policy. The folks at Farm Credit Mid-America talk with Dale about their Fight Hunger – Stock the Trailer event. Finally, Joel chats with the Lorain County Junior Fair Board who were the winners of the 2022 Fight Hunger – Stock the Trailer event. All this and more in this week's episode of the podcast!   00:00 Intro and OCJ/OAN Staff Update 04:42 Luke Crumley and Anne Thompson – Policy 10:11 Farm Credit Mid – America – Stock the Trailer Event   25:32 Stock the Trailer Event 2022 Winner 29:58 Back with Risë Labig 

Molti ricorderanno la drammatica vicenda dei due fratellini, scomparsi nel 2006 e ritrovati morti due anni dopo, in fondo a una cisterna abbandonata, nel centro di Gravina, in Puglia. Ne ripercorriamo la storia con il giornalista Mauro Valentini e Luciano Garofano, già comandante dei RIS di Parma e consulente tecnico per l'Autorità Giudiziaria e gli studi legali, autori di un libro che finalmente prova a fare chiarezza sui tanti misteri del caso.

Det er nytelsesfredag og Christer lager Ris à la Malta, en svensk variant av riskrem. Vi snakker om julemat, Harry og Meghan, kjønnskvotering på studier og er det egentlig lov å løfte en katt etter nakkeskinnet? Episoden kan inneholde målrettet reklame, basert på din IP-adresse, enhet og posisjon. Se smartpod.no/personvern for informasjon og dine valg om deling av data.

durée : 00:42:22 - Côté saveurs - France Bleu Picardie

Join The OSINT Curious Project team as we talk about some news and tools in #OSINT. This week, Micah (@WebBreacher) and Christina (@ChristinaLekati) put some extra emphasis on demonstrating new tools and search techniques. They started by discussing SMART (Start Me Aggregated Resource Tool), an OSINT Start.me page parser and aggregator. Bash scripting came into the conversation shortly after and along with it, Sinwindie's (@OSINTDojo) video tutorial. OSINT on Mastodon had it's special place on this episode, as it is a social media platform that has been growing exponentially the past few weeks. We discussed what is different from other social media platforms and shared an introductory guide on how to conduct OSINT investigations on it. We also demonstrated 3 different ways & tools one can use to find usernames and accounts on Mastodon. Micah and Christina moved on to discuss the role cryptography can play in certain investigations and shared a blog post that acts as a useful introduction into this intersection of disciplines. Micah demonstrated the project "Backmoji", a resource that keeps historical data on the bitmoji's someone has historically used, based on their user ID. This database can reflect changes people have made in their appearance over time. Speaking of appearances and images, we also shared a twitter thread that lists a number of resources that help conduct and improve reverse image searches. The list does not only contain tools that conduct RIS, but also editing tools that help this process. Thank you for joining us for another episode, we wish everyone a happy holiday season and a happy new year! See you next time!

#174. Spectrum-Kasım'22: Biyomühendislik, Yapay Zeka, Kuantum Şifreleme ve Haberleşme - 27/11/2022 Prof. Dr. Serhan Yarkan ve Halil Said Cankurtaran'ın yer aldığı IEEE Spectrum serimizin bu bölümünde, IEEE Spectrum dergisinin Kasım 2022 sayısı ele alınmıştır. Bölümümüze IEEE Spectrum dergisinde son zamanlarda sıkça yer alan biyomühendislik çalışmaları üzerine konuşarak başlıyoruz. Sonrasında, derginin Kasım 2022 sayısının kapağında yer alan yapay/biyonik burun üzerine konuşup, bu çalışma ile başta korona sonrası koku kaybı yaşayan hastalar olmak üzere koku duyusu sağlıklı çalışmayan bireylere, koku duyusunun tekrar kazandırılabileceğine değiniyoruz. Ardından, biyomühendislik çalışmalarının sürdürülebilirliği ve çalışmaların fonlanmasının sürdürülebilirliğe olan etkisi üzerine konuşuyoruz. Sonrasında, Dragon Robot olarak adlandırılan ve insan hayatını tehlikeye atabilecek durumlarda insanların yerine kullanılabilen ve yeniden yapılandırılabilen Drone'dan bahsedip, Drone'nun barındırdığı işaret işleme ve kontrol algoritmalarına, yapay zekaya ve gerçek zamanlı işleyişe değiniyoruz. Sonrasında, yapay zeka ile yazılım geliştirme ve yapay zekanın kodlamadaki kullanımı üzerine konuşuyoruz. Interplanetary File System'i açıklayıp, şifrelemede ve kuantum bilgisayarların geliştirilmesi ile oluşacak açığın nasıl etkileri olacağı üzerine tartışıyoruz. Kuantum teknolojisinin uzay çalışmalarındaki kullanımının artışına dikkat çekip, son olarak, elektromanyetik dalgaların yayılımını kontrol etmek amacı ile geliştirilen Reconfigurable Intelligent Surfaces (RIS)'i örneklerle açıklayarak bölümümüzü sonlandırıyoruz. Keyifli dinlemeler! Hans Niemann'ın World Team Championship'te Amerika'ya lider olarak seçilmesi: https://www.theguardian.com/sport/2022/oct/28/chess-hans-niemann-chosen-to-lead-usa-at-world-team-championship --- 00:00 Giriş 00:57 IEEE Spectrum'da biyomühendislik çalışmaları 01:31 Biyonik burun: Koku alma duyusunun geri kazandırılması 03:17 Gerçekleştirilen çalışmaların sürdürülebilirliği ve fonlanmanın etkileri 05:21 Dragon Drone: İnsan yaşamına katkısı ve etkileri 07:32 Mühendislik bakış açısıyla Dragon Drone: Hesaplama karmaşıklığı, gerçek zamanlı işleyiş, çip tasarımı ve yapay zeka 09:19 Yapay zeka ile yazılım geliştirme 11:11 Yapay zekanın insan yaşamında kullanımına örnekler 14:12 Interplanetary File System 19:13 Mevcut şifreleme algoritmalarının kuantum bilgisayarların kullanımıyla değişmesi 22:01 Kuantum teknolojisinin uzay teknolojilerinde yer alışındaki artış ve ardında yer alan matematik 23:48 Reconfigurable Intelligent Surfaces (RIS): Elektromanyetik dalgalarının yayılımını kolaylaştıran yüzeyler 26:43 RIS'in madenlerde basit bir şekilde kullanımı 28:15 Tapir Lab.'ın da yer aldığı, terahertz bandında gerçekleştirilen deneysel kanal çalışması 29:54 Kapanış --- Bağlantılar: IEEE Spectrum: https://spectrum.ieee.org/ IEEE Spectrum Kasım 2022 Sayısı: https://spectrum.ieee.org/magazine/2022/november/ TapirCast - Bilimsel ve Teknolojik Gelişmeler: https://youtube.com/playlist?list=PLwvStmyxv70_rnTR_kItlrZvaIdxWgfIN TapirCast - Mühendislik Kavramları: https://youtube.com/playlist?list=PLwvStmyxv708xJad4QY9ZueBMGdLSz3m6 Apple Podcasts: @TapirCast, https://podcasts.apple.com/tr/podcast/tapircast/id1485098931 Spotify: @TapirCast, https://open.spotify.com/show/1QJduW17Sgvs1sofFgJN8L?si=6378c7e84186419e Tapir Lab. GitHub: @TapirLab, https://github.com/TapirLab Tapir Lab. Instagram: @tapirlab, https://www.instagram.com/tapirlab/ Tapir Lab. Twitter: @tapirlab, https://twitter.com/tapirlab?s=20 Tapir Lab.: http://tapirlab.com/

Sono stati trovati dei resti umani in un casolare a Novellara (Reggio Emilia) in un posto non lontano rispetto a dove viveva la famiglia di Saman Abbas, la 18enne pakistana scomparsa la notte del 30 aprile 2021 dopo aver rifiutato un matrimonio combinato.

Un sopralluogo dei Ris è in corsoa Novellara (Reggio Emilia) non lontano dal casolare dove vivevala famiglia di Saman Abbas. Sarebbero stati trovati dei restiumani e sono in corso accertamenti dei carabinieri per capire sesi tratti della giovane. La 18enne pakistana che rifiutò unmatrimonio combinato è scomparsa dalla notte del 30 aprile 2021e per l'omicidio sono indagati cinque parenti. Nei giorni scorsiil padre, Shabbar Abbas, è stato arrestato in Pakistan.

Bu video 14/08/2016 tarihinde yayınlanan "“DERDİ DÜNYA OLANIN DÜNYA KADAR DERDİ OLUR!..”" isimli bamtelinden alınmıştır. Tamamı burada: https://www.herkul.org/bamteli/bamtel... Müslümanlık, İnsanlığın İftihar Tablosu'nun ve Raşid Halifelerin temsil ettiği hayattır; Müslümanlığın lafını eden ama ondan uzak yaşayanlara inanmayın!.. Hazreti Ebu Bekir efendimiz, Efendimiz'in yanında ikinci derecede efendiler efendisi.. Ona “sıddîk-i ekber” demişler, “en doğru, en doğruların en büyüğü, en doğruların en büyüğü, en doğruların en büyüğü…” Bir gün bir bardak soğuk su veriyorlar. Böyle dudağına götürdüğü zaman, eliyle itiyor ve hıçkıra hıçkıra ağlıyor. (Yâ Rabbî ne olur, o kalbi bize de ver! Bahtına düştük..) Neden sonra soruyorlar: “Yâ emire'l-mü'minin, niye ağlıyorsun?” Diyor ki: “Bir gün Hazret-i Risâletpenâh Efendimiz'in yanında oturuyordum; elleriyle bir şeyi reddediyor ve itiyormuş gibi bir hareket yaptı. Neden sonra dedim ki: Yâ Rasûlullah, ne yaptınız öyle? Buyurdular ki: Dünya, câzibedâr güzellikleriyle, hezâfiriyle temessül etti, karşıma dikildi. (Yalı, villa, yat, gemi, filo, düşünebilirsiniz) Bana kendini kabul ettirmek istedi. Ben de elimin tersiyle ittim, ‘Bana kendini kabul ettiremezsin, git!' dedim. Döndü bana dedi ki dünya (şahs-ı mânevî olarak) ‘Sana kabul ettiremedim ama senden sonrakilere kabul ettiririm!' İşte bu soğuk soğuk suyu böyle içmek suretiyle, korktum ki, O'ndan (sallallâhu aleyhi ve sellem) sonrakilerden (dünyanın kendisini kabul ettirdiklerinden) birisi ben olabilirim!..” Ebu Bekir-i Sıddîk diyor bunu.. kurban olayım sana… Ama üç senede Devlet-i Aliyye'nin (ki Devlet-i Aliyye gibi mübarek bir devlet, Râşit halifelerden sonra onun eşi yok) yüz senede yaptığını, “iki sene, üç ay, on küsur gün”de yapmış. Tekrara gerek var mı? “İki sene, üç ay, on küsur gün”de yapmış. Fakat hayret ediyorum, bu yaptığı şeylerden, şu iki buçuk senede yaptığı yüz senelik şeyden, bir tek kelime ile bahsettiğini bilmiyorum. Bir gün bir yerde Siyer ve Meğazi kitaplarında görürseniz, Allah aşkına benim bu merakımı giderme adına söyleyin onu.. “Ben şunu yaptım!” şeklindeki bir tek kelimesini bana söyleyin.. Bir ev bırakmadı.. Oğlunu nazara vermedi, kızını da nazara vermedi. Diyemez miydi, böyle bir sultan, sultanlar sultanı, sultan Süleyman'a bir yönüyle taç giydiren sultanlar sultanı?!.

Congressus Sīnēnsium Congressī sunt dūcēs Commūnistārum factiōnis Sērum, quī Xī Jinping tertium creāvērunt principem factiōnis. Xī deinde summum et polīticum concilium sēlēgit, quod dē summīs rēbus constituendīs in quinquennium dēlīberāret. Quod in concilium cōnscriptī sunt senēs, quōrum propter prōvectam aetātem nēmō in locum Xī Jinping successūrus vidētur. Itaque dominātiō, quam Xī iam exercet, vidētur fore perpetua. Diurnāriīs peregrīnīs in congressūs aulam inductīs, Hū Jintaō, pristinus praeses Sērum, capite sine falsīs colōribus cānō, nōlēns sublātus atque ēductus est, quod Sīnēnsēs magistrātūs referunt propter senectūtis dēbilitātem necesse fuisse; forīs autem id putātur significāre Xī vestīgia pristinōrum magistrātuum ēverrere. Quod intrā Sīnās cēnsōria omnium spectāculōrum colloquendīque ratiōnum disciplīna prōhibuit, nē dīvulgārētur. Inter alia auctoritātis signa, singulīs poculīs theae ante omnēs aliōs positīs, ante Xī pocula sunt apposita bīna. Itaque vidētur Xī voluisse omnibus gentibus ostendere sēmet ipsum sine aemulō, sine dissēnsiōne, sine successōre perpetuam dominātiōnem consecūtum esse. Quod ad rēs futūrās attinet, Sīnēnsium cōnsilium oeconomicum, quod “duālis circulātiō” appellātur, quō Sērēs suās mercēs exportāre nōn recūsant, quamvīs internum cīvium Sīnēnsium dēsīderium mercium augēre augendā mercēde opificum mālint, nōn solum probātum est sed etiam rōborātur nōvō cōnsiliō, quod “commūnis prosperitās” dīcitur. Nam immēnsa pecūnia, quae commerciō omnium gentium comparātur, nunc magis aequaliter inter Sērēs distribuenda vidētur, nē opificī fiant tumultuōsī. Nguyen Phu Trong Sīnās vīset Nguyen Phu Trong, generālis sēcrētārius factiōnis Commūnistārum Vietnamēnsium, quī rārissimē suōs fīnēs ēgreditur, iter factūrus est diē trīcēsimō in Sīnās, ubi Xī Jinping gratulābitur. Vietnamēnsēs enim tam cum Sīnēnsibus quam cum Americānīs amīcitiam colunt. Timētur nē doctrīna āeria Sīnēnsibus tradātur Daniēl Duggan, ōlim mīlēs classicus et āerius et Americānus quī nōn solum bellica āeroplāna gubernābat sed stiam aliōs mīlitēs mīlitārem artem volandī docēbat, iussū Americānōrum ab Austrāliānīs est comprehēnsus atque in diciōnem Americānōrum reddētur. Nam Duggan ille annō bis millēsimō septimō decimō in Sīnās sē contulit, ubi trēs annōs operam dābat rēbus āeriīs Sīnēnsibus. Timētur nē Sīnēnsēs mercēde condūcant mīlitēs veterānōs Americānōs sociōsque, ut Britannōs Austrāliānōsve, quī Sinēnsēs tīrōnēs īnforment atque artibus mīlitāribus instituant. Etiam hāc hebdomade magistrātūs Britannōrum suōs mīlitēs āeriōs monuērunt ne artēs mīlitārēs Sīnēnsēs docērent, atque Austrāliānī adhūc pervestīgant utrum suī cīvēs ullī Sīnēnsibus mīlitārem doctrīnam trādant. Mīlitēs in Haitiam mittendī In Coëtū Omnium Gentium strenuē cōnantur lēgātī Americānī agere, ut mīlitēs in Haitiam mittantur. Nam Antoniō Guterres, secretāriō generālī Coëtūs, vidētur auxilium custōdibus pūblicīs Haitiēnsium immittere, quī latrōnēs populum petroleō arcentēs dēturbent et pācem redintegrant. Nulla vērō gēns dīxit sē velle mīlitēs dūcere, sed Americānī dē rē cum Canadēnsibus, quī lēgātōs diē Iōvis in Haitiam mīsērunt, et Mexicānīs et Bahamēnsibus colloquuntur. Propter inopiam petroleī et aquae dulcis pūraeque, perīculum cholerae imminet Haitiēnsibus. Fierī potest ut cōnsilium mīlitāris auxiliī mittendī mēnse Novembrī ineunte capiātur. Risīus Sūnac sēlectus Risīus Sūnac creātus est novus minister prīmārius Britannōrum. Sūnac breviter cancellārius fuit, cum Boris Johnson minister prīmārius esset, sed ēius abdicātiō cancellāriātūs coēgit Johnson etiam suum ipsīus magistrātum dēpōnere. Sūnac fertur velle stabilitātem tuērī et integrum facere fiscum, quem Elizābētha Truss turbāvit. Vir ipse, quī argentārius fuit, inter dītissimōs Britannōs numerātur, ūnā cum uxōre, quam prīmum cognōvit Stanfordī in Californiā cīvitāte, ubī studia colēbant. Pepōnēs pictī Ante ultimam Octōbris mēnsis diem, quō veneficae phasmataque atque alia monstra apertius saltem quam aliīs diēbus per viās Bellinghamiae grassantur, discipulōrum societas “Mēnsa Latīna” dicta, cui praesumus ego et Michaēla, parvās cucurbitās mīrīs terrificīsque imāginibus pinxit—necnōn colōrum nōmina tractāvit. Mēnsa Latīna hōrā quartā diē Lūnae convocātur. Proximā in contiōne fortasse aliās rēs pingēmus.

Det är en varm och solig fredag i idylliska Risör i sydNorge. Nina passar sin 6-åriga kusin Marianne Rugaas Knutsen. Marianne har fått en liten peng av sin mamma för att köpa glass och godis. Omkring klockan 14.30 vinkar hon till sin kusin och beger sig mot den närliggande butiken. Manus av Sofie Karlsson.Du hittar Mördarpodden där du hittar Olösta Mord. Du kan också följa Mördarpoddens instagram här: https://www.instagram.com/mordarpodden/Vill du att Olösta mord ska komma ut varje vecka? Du kan påverka genom att dela podden med alla du känner som kan tänkas vara intresserade och/eller sponsra via Patreon; https://www.patreon.com/olostamord Välj valfri summa du vill sponsra med per avsnitt på Patreon. Når vi 2000 kr per avsnitt kommer podden att komma ut varje torsdag istället för varannan vecka.Swishdonationer till 070-7715864 fungerar fortfarande. Märk swishen "Olösta mord".Har du teorier om vad som hänt i fallen som vi tagit upp i podden? Skicka dem till: zimwaypodcast@gmail.com så kommer vi ta upp dem i kommande avsnitt. Det här är en podd av Dan Hörning.Följ Dan Hörning här:Twitter: @danhorningInstagram: https://www.instagram.com/dan_horning/?hl=enYoutube: https://www.youtube.com/channel/UCV2Qb7SmL9mejE5RCv1chwgMail: zimwaypodcast@gmail.comFacebook: https://www.facebook.com/Olostamord/ Hosted on Acast. See acast.com/privacy for more information.

La position du continent africain à l'égard du conflit russo-ukrainien interpelle les Occidentaux. Tandis que certains pays, tels que l'Afrique du Sud, ont longtemps entretenu des liens stratégiques et économiques avec les États-Unis, leurs positions diplomatiques s'éloignent désormais de celle de Washington et plus largement des Occidentaux. En mars dernier, les pays africains n'adoptaient certes pas une position commune s'agissant du vote pour la condamnation de l'agression russe contre l'Ukraine à l'Assemblée générale des Nations unies mais ces derniers se sont distancés des prises de décisions occidentales puisqu'aucun pays africain n'a adopté de sanctions contre Moscou. Une orientation qui semble s'expliquer notamment par l'accroissement de l'influence russe sur le continent. Cette tendance s'illustre notamment à travers le rapprochement de l'Afrique du Sud, qui tente, sans grand succès jusqu'à présent, de s'imposer comme leader du continent, avec la Russie et la Chine. Comment se positionnent les pays africains vis-à-vis du conflit russo-ukrainien ? Quelle relation entretien l'Afrique du Sud et plus largement le continent africain avec la Russie ? L'Afrique du Sud doit-elle être considérée comme le partenaire "dormant" des BRICS ? L'Afrique du Sud est-elle en train de perdre de vue le statut de leader du continent africain qu'elle espérait un jour atteindre ? En quelle mesure l'influence de Moscou progresse-t-elle en Afrique ? Dans ce podcast, Francis Laloupo, journaliste et chercheur associé à l'IRIS revient sur la perception du conflit russo-ukrainien par les pays africains. Pour aller plus loin :

Alt utstyret mitt til podcast og video er pakket ned, og jeg har ikke lenger et eget kontor her hjemme. Det blir en stund til jeg får det på plass igjen og jeg forteller hvorfor.. Anbefalinger:-«Monster: The Jeffrey Dahmer Story» (Netflix)-Min andre podcast "Virkelig Grusomt" finnes i alle podcast apper-YouTube: www.youtube.com/tonesabro-Støtt meg på Patreon: www.patreon.com/tonesabro-Ris og ros: nervemedtone@gmail.com -Sosiale medier: @nervemedtone / @tonesabro

Former Trump White House lawyer Ty Cobb suspects the Justice Department investigation into the former president's mishandling of documents – some of them highly classified – is about a broader inquiry into potential crimes related to the January 6th Capitol riot and efforts to overturn the 2020 election.Cobb worked closely with the former president, defending the White House during Special Counsel Robert Mueller's investigation. “I believe former President Trump to be a deeply wounded narcissist and he is often incapable of acting other than in his perceived self-interest or for revenge,” Cobb said. “I think those are the two compelling instincts that guide his actions.”Join us for lunch at Ris in DC's West End. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Døden er det mest naturlige i livet, likevel er det et tabu. Hvorfor er det så vanskelig å prate om døden og hva som skjer med kroppene våre? Jeg synes døden kan være veldig fascinerende, og ikke minst også hvilke prosesser og tradisjoner som finnes rundt dette. Det er folk som har som jobb å behandle kroppene våre etter at vi dør, men hva gjør de egentlig? Hvordan begraves folk i andre kulturer? Hva vil du at skal skje med din kropp etter at du er død?Anbefalinger:-De Usynlige (film, norsk, 2021)-Ologies, podcast (engelsk)-Dark Tourist, tv-serie (Netflix)-Min andre podcast "Virkelig Grusomt" finnes i alle podcast apper-YouTube: www.youtube.com/tonesabro-Støtt meg på Patreon: www.patreon.com/tonesabro-Ris og ros: nervemedtone@gmail.com -Sosiale medier: @nervemedtone / @tonesabro

About AlexAlex holds a Ph.D. in Computer Science and Engineering from UC San Diego, and has spent over a decade building high-performance, robust data management and processing systems. As an early member of a couple fast-growing startups, he's had the opportunity to wear a lot of different hats, serving at various times as an individual contributor, tech lead, manager, and executive. He also had a brief stint as a Cloud Economist with the Duckbill Group, helping AWS customers save money on their AWS bills. He's currently a freelance data engineering consultant, helping his clients build, manage, and maintain their data infrastructure. He lives in Los Angeles, CA.Links Referenced: Company website: https://bitsondisk.com Twitter: https://twitter.com/alexras LinkedIn: https://www.linkedin.com/in/alexras/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: I come bearing ill tidings. Developers are responsible for more than ever these days. Not just the code that they write, but also the containers and the cloud infrastructure that their apps run on. Because serverless means it's still somebody's problem. And a big part of that responsibility is app security from code to cloud. And that's where our friend Snyk comes in. Snyk is a frictionless security platform that meets developers where they are - Finding and fixing vulnerabilities right from the CLI, IDEs, Repos, and Pipelines. Snyk integrates seamlessly with AWS offerings like code pipeline, EKS, ECR, and more! As well as things you're actually likely to be using. Deploy on AWS, secure with Snyk. Learn more at Snyk.co/scream That's S-N-Y-K.co/screamCorey: DoorDash had a problem. As their cloud-native environment scaled and developers delivered new features, their monitoring system kept breaking down. In an organization where data is used to make better decisions about technology and about the business, losing observability means the entire company loses their competitive edge. With Chronosphere, DoorDash is no longer losing visibility into their applications suite. The key? Chronosphere is an open-source compatible, scalable, and reliable observability solution that gives the observability lead at DoorDash business, confidence, and peace of mind. Read the full success story at snark.cloud/chronosphere. That's snark.cloud slash C-H-R-O-N-O-S-P-H-E-R-E.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I am joined this week by a returning guest, who… well, it's a little bit complicated and more than a little bittersweet. Alex Rasmussen was a principal cloud economist here at The Duckbill Group until he committed an unforgivable sin. That's right. He gave his notice. Alex, thank you for joining me here, and what have you been up to, traitor?Alex: [laugh]. Thank you for having me back, Corey.Corey: Of course.Alex: At time of recording, I am restarting my freelance data engineering business, which was dormant for the sadly brief time that I worked with you all at The Duckbill Group. And yeah, so that's really what I've been up to for the last few days. [laugh].Corey: I want to be very clear that I am being completely facetious when I say this. When someone is considering, “Well, am I doing what I really want to be doing?” And if the answer is no, too many days in a row, yeah, you should find something that aligns more with what you want to do. And anyone who's like, “Oh, you're leaving? Traitor, how could you do that?” Yeah, those people are trash. You don't want to work with trash.I feel I should clarify that this is entirely in jest and I could not be happier that you are finding things that are more aligned with aspects of what you want to be doing. I am serious when I say that, as a company, we are poorer for your loss. You have been transformative here across a number of different axes that we will be going into over the course of this episode.Alex: Well, thank you very much, I really appreciate that. And I came to a point where I realized, you know, the old saying, “You don't know what you got till it's gone?” I realized, after about six months of working with Duckbill Group that I missed building stuff, I missed building data systems, I missed being a full-time data person. And I'm really excited to get back to that work, even though I'll definitely miss working with everybody on the team. So yeah.Corey: There are a couple of things that I found really notable about your time working with us. One of them was that even when you wound up applying to work here, you were radically different than—well, let's be direct here—than me. We are almost polar opposites in a whole bunch of ways. I have an eighth-grade education; you have a PhD in computer science and engineering from UCSD. And you are super-deep into the world of data, start to finish, whereas I have spent my entire career on things that are stateless because I am accident prone, and when you accidentally have a problem with the database, you might not have a company anymore, but we can all laugh as we reprovision the web server fleet.We just went in very different directions as far as what we found interesting throughout our career, more or less. And we were not quite sure how it was going to manifest in the context of cloud economics. And I can say now that we have concluded the experiment, that from my perspective, it went phenomenally well. Because the exact areas that I am weak at are where you excel. And, on some level, I would say that you're not necessarily as weak in your weak areas as I am in mine, but we want to reinforce it and complementing each other rather than, “Well, we now have a roomful of four people who are all going to yell at you about the exact same thing.” We all went in different directions, which I thought was really neat.Alex: I did too. And honestly, I learned a tremendous, tremendous amount in my time at Duckbill Group. I think the window into just how complex and just how vast the ecosystem of services within AWS is, and kind of how they all ping off of each other in these very complicated ways was really fascinating, fascinating stuff. But also just an insight into just what it takes to get stuff done when you're talking with—you know, so most of my clientele to date have been small to medium-sized businesses, you know, small as two people; as big as a few hundred people. But I wasn't working with Fortune 1000 companies like Duckbill Group regularly does, and an insight into just, number one, what it takes to get things done inside of those organizations, but also what it takes to get things done with AWS when you're talking about, you know, for instance, contracts that are tens, or hundreds of millions of dollars in total contract value. And just what that involves was just completely eye-opening for me.Corey: From my perspective, what I found—I guess, in hindsight, it should have been more predictable than it was—but you talk about having a background and an abiding passion for the world of data, and I'm sitting here thinking, that's great. We have all this data in the form of the Cost and Usage Reports and the bills, and I forgot the old saw that yeah, if it fits in RAM, it's not a big data problem. And yeah, in most cases, what we have tends to fit in RAM. I guess you don't tend to find things interesting until Microsoft Excel gives up and calls uncle.Alex: I don't necessarily know that that's true. I think that there are plenty of problems to be had in the it fits in RAM space, precisely because so much of it fits in RAM. And I think that, you know, particularly now that, you know—I think there's it's a very different world that we live in from the world that we lived in ten years ago, where ten years ago—Corey: And right now I'm talking to you on a computer with 128 gigs of RAM, and it—Alex: Well, yeah.Corey: —that starts to look kind of big data-y.Alex: Well, not only that, but I think on the kind of big data side, right? When you had to provision your own Hadoop cluster, and after six months of weeping tears of blood, you managed to get it going, right, at the end of that process, you went, “Okay, I've got this big, expensive thing and I need this group of specialists to maintain it all. Now, what the hell do I do?” Right? In the intervening decade, largely due to the just crushing dominance of the public clouds, that problem—I wouldn't call that problem solved, but for all practical purposes, at all reasonable scales, there's a solution that you can just plug in a credit card and buy.And so, now the problem, I think, becomes much more high level, right, than it used to be. Used to be talking about how well you know, how do I make this MapReduce job as efficient as it possibly can be made? Nobody really cares about that anymore. You've got a query planner; it executes a query; it'll probably do better than you can. Now, I think the big challenges are starting to be more in the area of, again, “How do I know what I have? How do I know who's touched it recently? How do I fix it when it breaks? How do I even organize an organization that can work effectively with data at petabyte scale and say anything meaningful about it?”And so, you know, I think that the landscape is shifting. One of the reasons why I love this field so much is that the landscape is shifting very rapidly and as soon as we think, “Ah yes. We have solved all of the problems.” Then immediately, there are a hundred new problems to solve.Corey: For me, what I found, I guess, one of the most eye-opening things about having you here is your actual computer science background. Historically, we have biased for folks who have come up from the ops side of the world. And that lends itself to a certain understanding. And, yes, I've worked with developers before; believe it or not, I do understand how folks tend to think in that space. I have not a complete naive fool when it comes to these things.But what I wasn't prepared for was the nature of our internal, relatively casual conversations about a bunch of different things, where we'll be on a Zoom chat or something, and you will just very casually start sharing your screen, fire up a Jupyter Notebook and start writing code as you're talking to explain what it is you're talking about and watching it render in real time. And I'm sitting here going, “Huh, I can't figure out whether we should, like, wind up giving him a raise or try to burn him as a witch.” I could really see it going either way. Because it was magic and transformative from my perspective.Alex: Well, thank you. I mean, I think that part of what I am very grateful for is that I've had an opportunity to spend a considerable period of time in kind of both the academic and industrial spaces. I got a PhD, basically kept going to school until somebody told me that I had to stop, and then spent a lot of time at startups and had to do a lot of different kinds of work just to keep the wheels attached to the bus. And so, you know, when I arrived at Duckbill Group, I kind of looked around and said, “Okay, cool. There's all the stuff that's already here. That's awesome. What can I do to make that better?” And taking my lens so to speak, and applying it to those problems, and trying to figure out, like, “Okay, well as a cloud economist, what do I need to do right now that sucks? And how do I make it not suck?”Corey: It probably involves a Managed NAT Gateway.Alex: Whoa, God. And honestly, like, I spent a lot of time developing a bunch of different tools that were really just there in the service of that. Like, take my job, make it easier. And I'm really glad that you liked what you saw there.Corey: It was interesting watching how we wound up working together on things. Like, there's a blog post that I believe is out by the time this winds up getting published—but if not, congratulations on listening to this, you get a sneak preview—where I was looking at the intelligent tiering changes in pricing, where any object below 128 kilobytes does not have a monitoring charge attached to it, and above it, it does. And it occurred to me on a baseline gut level that, well wait a minute, it feels like there is some object sizes, where regardless of how long it lives in storage and transition to something cheaper, it will never quite offset that fee. So, instead of having intelligent tiering for everything, that there's some cut-off point below which you should not enable intelligent tiering because it will always cost you more than it can possibly save you.And I mentioned that to you and I had to do a lot of articulating with my hands because it's all gut feelings stuff and this stuff is complicated at the best of times. And your response was, “Huh.” Then it felt like ten minutes later you came back with a multi-page blog post written—again—in a Python notebook that has a dynamic interactive graph that shows the breakeven and cut-off points, a deep dive math showing exactly where in certain scenarios it is. And I believe the final takeaway was somewhere between 148 to 161 kilobytes, somewhere in that range is where you want to draw the cut-off. And I'm just looking at this and marveling, on some level.Alex: Oh, thanks. To be fair, it took a little bit more than ten minutes. I think it was something where it kind of went through a couple of stages where at first I was like, “Well, I bet I could model that.” And then I'm like, “Well, wait a minute. There's actually, like—if you can kind of put the compute side of this all the way to the side and just remove all API calls, it's a closed form thing. Like, you can just—this is math. I can just describe this with math.”And cue the, like, Beautiful Mind montage where I'm, like, going onto the whiteboard and writing a bunch of stuff down trying to remember the point intercept form of a line from my high school algebra days. And at the end, we had that blog post. And the reason why I kind of dove into that headfirst was just this, I have this fascination for understanding how all this stuff fits together, right? I think so often, what you see is a bunch of little point things, and somebody says, “You should use this at this point, for this reason.” And there's not a lot in the way of synthesis, relatively speaking, right?Like, nobody's telling you what the kind of underlying thing is that makes it so that this thing is better in these circumstances than this other thing is. And without that, it's a bunch of, kind of, anecdotes and a bunch of kind of finger-in-the-air guesses. And there's a part of that, that just makes me sad, fundamentally, I guess, that humans built all of this stuff; we should know how all of it fits together. And—Corey: You would think, wouldn't you?Alex: Well, but the thing is, it's so enormously complicated and it's been developed over such an enormously long period of time, that—or at least, you know, relatively speaking—it's really, really hard to kind of get that and extract it out. But I think when you do, it's very satisfying when you can actually say like, “Oh no, no, we've actually done—we've done the analysis here. Like, this is exactly what you ought to be doing.” And being able to give that clear answer and backing it up with something substantial is, I think, really valuable from the customer's point of view, right, because they don't have to rely on us kind of just doing the finger-in-the-air guess. But also, like, it's valuable overall. It extends the kind of domain where you don't have to think about whether or not you've got the right answer there. Or at least you don't have to think about it as much.Corey: My philosophy has always been that when I have those hunches, they're useful, and it's an indication that there's something to look into here. Where I think it goes completely off the rails is when people, like, “Well, I have a hunch and I have this belief, and I'm not going to evaluate whether or not that belief is still one that is reasonable to hold, or there has been perhaps some new information that it would behoove me to figure out. Nope, I've just decided that I know—I have a hunch now and that's enough and I've done learning.” That is where people get into trouble.And I see aspects of it all the time when talking to clients, for example. People who believe things about their bill that at one point were absolutely true, but now no longer are. And that's one of those things that, to be clear, I see myself doing this. This is not something—Alex: Oh, everybody does, yeah.Corey: —I'm blaming other people for it all. Every once in a while I have to go on a deep dive into our own AWS bill just to reacquaint myself with an understanding of what's going on over there.Alex: Right.Corey: And I will say that one thing that I was firmly convinced was going to happen during your tenure here was that you're a data person; hiring someone like you is the absolute most expensive thing you can ever do with respect to your AWS bill because hey, you're into the data space. During your tenure here, you cut the bill in half. And that surprises me significantly. I want to further be clear that did not get replaced by, “Oh, yeah. How do you cut your AWS bill by so much?” “We moved everything to Snowflake.” No, we did not wind up—Alex: [laugh].Corey: Just moving the data somewhere else. It's like, at some level, “Great. How do I cut the AWS bill by a hundred percent? We migrate it to GCP.” Technically correct; not what the customer is asking for.Alex: Right? Exactly, exactly. I think part of that, too—and this is something that happens in the data part of the space more than anywhere else—it's easy to succumb to shiny object syndrome, right? “Oh, we need a cloud data warehouse because cloud data warehouse, you know? Snowflake, most expensive IPO in the history of time. We got to get on that train.”And, you know, I think one of the things that I know you and I talked about was, you know, where should all this data that we're amassing go? And what should we be optimizing for? And I think one of the things that, you know, the kind of conclusions that we came to there was, well, we're doing some stuff here, that's kind of designed to accelerate queries that don't really need to be accelerated all that much, right? The difference between a query taking 500 milliseconds and 15 seconds, from our point of view, doesn't really matter all that much, right? And that realization alone, kind of collapsed a lot of technical complexity, and that, I will say we at Duckbill Group still espouse, right, is that cloud cost is an architectural problem, it's not a right-sizing your instances problem. And once we kind of got past that architectural problem, then the cost just sort of cratered. And honestly, that was a great feeling, to see the estimate in the billing console go down 47% from last month, and it's like, “Ah, still got it.” [laugh].Corey: It's neat to watch that happen, first off—Alex: For sure.Corey: But it also happened as well, with increasing amounts of utility. There was a new AWS billing page that came out, and I'm sure it meets someone's needs somewhere, somehow, but the things that I always wanted to look at when I want someone to pull up their last month's bill is great, hit the print button—on the old page—and it spits out an exploded pdf of every type of usage across their entire AWS estate. And I can skim through that thing and figure out what the hell's going on at a high level. And this new thing did not let me do that. And that's a concern, not just for the consulting story because with our clients, we have better access than printing a PDF and reading it by hand, but even talking to randos on the internet who were freaking out about an AWS bill, they shouldn't have to trust me enough to give me access into their account. They should be able to get a PDF and send it to me.Well, I was talking with you about this, and again, in what felt like ten minutes, you wound up with a command line tool, run it on an exported CSV of a monthly bill and it spits it out as an HTML page that automatically collapses in and allocates things based upon different groups and service type and usage. And congratulations, you spent ten minutes to create a better billing experience than AWS did. Which feels like it was probably, in fairness to AWS, about seven-and-a-half minutes more time than they spent on it.Alex: Well, I mean, I think that comes back to what we were saying about, you know, not all the interesting problems in data are in data that doesn't fit in RAM, right? I think, in this case, that came from two places. I looked at those PDFs for a number of clients, and there were a few things that just made my brain hurt. And you and Mike and the rest of the folks at Duckbill could stare at the PDF, like, reading the matrix because you've seen so many of them before and go, ah, yes, “Bill spikes here, here, here.” I'm looking at this and it's just a giant grid of numbers.And what I wanted was I wanted to be able to say, like, don't show me the services in alphabetical order; show me the service is organized in descending order by spend. And within that, don't show me the operations in alphabetical order; show me the operations in decreasing order by spend. And while you're at it, group them into a usage type group so that I know what usage type group is the biggest hitter, right? The second reason, frankly, was I had just learned that DuckDB was a thing that existed, and—Corey: Based on the name alone, I was interested.Alex: Oh, it was an incredible stroke of luck that it was named that. And I went, “This thing lets me run SQL queries against CSV files. I bet I can write something really fast that does this without having to bash my head against the syntactic wall that is Pandas.” And at the end of the day, we had something that I was pretty pleased with. But it's one of those examples of, like, again, just orienting the problem toward, “Well, this is awful.”Because I remember when we first heard about the new billing experience, you kind of had pinged me and went, “We might need something to fix this because this is a problem.” And I went, “Oh, yeah, I can build that.” Which is kind of how a lot of what I've done over the last 15 years has been. It's like, “Oh. Yeah, I bet I could build that.” So, that's kind of how that went.Corey: This episode is sponsored in part by our friend EnterpriseDB. EnterpriseDB has been powering enterprise applications with PostgreSQL for 15 years. And now EnterpriseDB has you covered wherever you deploy PostgreSQL on-premises, private cloud, and they just announced a fully-managed service on AWS and Azure called BigAnimal, all one word. Don't leave managing your database to your cloud vendor because they're too busy launching another half-dozen managed databases to focus on any one of them that they didn't build themselves. Instead, work with the experts over at EnterpriseDB. They can save you time and money, they can even help you migrate legacy applications—including Oracle—to the cloud. To learn more, try BigAnimal for free. Go to biganimal.com/snark, and tell them Corey sent you.Corey: The problem that I keep seeing with all this stuff is I think of it in terms of having to work with the tools I'm given. And yeah, I can spin up infrastructure super easily, but the idea of, I'm going to build something that manipulates data and recombines it in a bunch of different ways, that's not something that I have a lot of experience with, so it's not my instinctive, “Oh, I bet there's an easier way to spit this thing out.” And you think in that mode. You effectively wind up automatically just doing those things, almost casually. Which does make a fair bit of sense, when you understand the context behind it, but for those of us who don't live in that space, it's magic.Alex: I've worked in infrastructure in one form or another my entire career, data infrastructure mostly. And one of the things—I heard this from someone and I can't remember who it was, but they said, “When infrastructure works, it's invisible.” When you walk in the room and flip the light switch, the lights come on. And the fact that the lights come on is a minor miracle. I mean, the electrical grid is one of the most sophisticated, globally-distributed engineering systems ever devised, but we don't think about it that way, right?And the flip side of that, unfortunately, is that people really pay attention to infrastructure most when it breaks. But they are two edges of the same proverbial sword. It's like, I know, when I've done a good job, if the thing got built and it stayed built and it silently runs in the background and people forget it exists. That's how I know that I've done a good job. And that's what I aim to do really, everywhere, including with Duckbill Group, and I'm hoping that the stuff that I built hasn't caught on fire quite yet.Corey: The smoke is just the arising of the piles of money it wound up spinning up.Alex: [laugh].Corey: It's like, “Oh yeah, turns out that maybe we shouldn't have built a database out of pure Managed NAT Gateways. Yeah, who knew?”Alex: Right, right. Maybe I shouldn't have filled my S3 bucket with pure unobtainium. That was a bad idea.Corey: One other thing that we do here that I admit I don't talk about very often because people get the wrong idea, but we do analyst projects for vendors from time to time. And the reason I don't say that is, when people hear about analysts, they think about something radically different, and I do not self-identify as an analyst. It's, “Oh, I'm not an analyst.” “Really? Because we have analyst budget.” “Oh, you said analyst. I thought you said something completely different. Yes, insert coin to continue.”And that was fine, but unlike the vast majority of analysts out there, we don't form our opinions based upon talking to clients and doing deeper dive explorations as our primary focus. We're a team of engineers. All right, you have a product. Let's instrument something with it, or use your product for something and we'll see how it goes along the way. And that is something that's hard for folks to contextualize.What was really fun was bringing you into a few of those engagements just because it was interesting; at the start of those calls. “It was all great, Corey is here and—oh, someone else's here. Is this a security problem?” “It's no, no, Alex is with me.” And you start off those calls doing what everyone should do on those calls is, “How can we help?” And then we shut up and listen. Step one, be a good consultant.And then you ask some probing questions and it goes a little bit deeper and a little bit deeper, and by the end of that call, it's like, “Wow, Alex is amazing. I don't know what that Corey clown is doing here, but yeah, having Alex was amazing.” And every single time, it was phenomenal to watch as you, more or less, got right to the heart of their generally data-oriented problems. It was really fun to be able to think about what customers are trying to achieve through the lens that you see the world through.Alex: Well, that's very flattering, first of all. Thank you. I had a lot of fun on those engagements, honestly because it's really interesting to talk to folks who are building these systems that are targeting mass audiences of very deep-pocketed organizations, right? Because a lot of those organizations, the companies doing the building are themselves massive. And they can talk to their customers, but it's not quite the same as it would be if you or I were talking to the customers because, you know, you don't want to tell someone that their baby is ugly.And note, now, to be fair, we under no circumstances were telling people that their baby was ugly, but I think that the thing that is really fun for me is to kind of be able to wear the academic database nerd hat and the practitioner hat simultaneously, and say, like, “I see why you think this thing is really impressive because of this whiz-bang, technical thing that it does, but I don't know that your customers actually care about that. But what they do care about is this other thing that you've done as an ancillary side effect that actually turns out is a much more compelling thing for someone who has to deal with this stuff every day. So like, you should probably be focusing attention on that.” And the thing that I think was really gratifying was when you know that you're meeting someone on their level and you're giving them honest feedback and you're not just telling them, you know, “The Gartner Magic Quadrant says that in order to move up and to the right, you must do the following five features.” But instead saying, like, “I've built these things before, I've deployed them before, I've managed them before. Here's what sucks that you're solving.” And seeing the kind of gears turn in their head is a very gratifying thing for me.Corey: My favorite part of consulting—and I consider analyst style engagements to be a form of consulting as well—is watching someone get it, watching that light go on, and they suddenly see the answer to a problem that's been vexing them I love that.Alex: Absolutely. I mean, especially when you can tell that this is a thing that has been keeping them up at night and you can say, “Okay. I see your problem. I think I understand it. I think I might know how to help you solve it. Let's go solve it together. I think I have a way out.”And you know, that relief, the sense of like, “Oh, thank God somebody knows what they're doing and can help me with this, and I don't have to think about this anymore.” That's the most gratifying part of the job, in my opinion.Corey: For me, it has always been twofold. One, you've got people figuring out how to solve their problem and you've made their situation better for it. But selfishly, the thing I like the most personally has been the thrill you get from solving a puzzle that you've been toying with and finally it clicks. That is the endorphin hit that keeps me going.Alex: Absolutely.Corey: And I didn't expect when I started this place is that every client engagement is different enough that it isn't boring. It's not the same thing 15 times. Which it would be if it were, “Hi, thanks for having us. You haven't bought some RIs. You should buy some RIs. And I'm off.” It… yeah, software can do that. That's not interesting.Alex: Right. Right. But I think that's the other thing about both cloud economics and data engineering, they kind of both fit into that same mold. You know, what is it? “All happy families are alike, but each unhappy family is unhappy in its own way.” I'm butchering Chekhov, I'm sure. But like—if it's even Chekhov.But the general kind of shape of it is this: everybody's infrastructure is different. Everybody's organization is different. Everybody's optimizing for a different point in the space. And being able to come in and say, “I know that you could just buy a thing that tells you to buy some RIs, but it's not going to know who you are; it's not going to know what your business is; it's not going to know what your challenges are; it's not going to know what your roadmap is. Tell me all those things and then I'll tell you what you shouldn't pay attention to and what you should.”And that's incredibly, incredibly valuable. It's why, you know, it's why they pay us. And that's something that you can never really automate away. I mean, you hear this in data all the time, right? “Oh, well, once all the infrastructure is managed, then we won't need data infrastructure people anymore.”Well, it turns out all the infrastructure is managed now, and we need them more than we ever did. And it's not because this managed stuff is harder to run; it's that the capabilities have increased to the point that they're getting used more. And the more that they're getting used, the more complicated that use becomes, and the more you need somebody who can think at the level of what does the business need, but also, what the heck is this thing doing when I hit the run key? You know? And that I think, is something, particularly in AWS where I mean, my God, the amount and variety and complexity of stuff that can be deployed in service of an organization's use case is—it can't be contained in a single brain.And being able to make sense of that, being able to untangle that and figure out, as you say, the kind of the aha moment, the, “Oh, we can take all of this and just reduce it down to nothing,” is hugely, hugely gratifying and valuable to the customer, I'd like to think.Corey: I think you're right. And again, having been doing this in varying capacities for over five years—almost six now; my God—the one thing has been constant throughout all of that is, our number one source for new business has always been word of mouth. And there have been things that obviously contribute to that, and there are other vectors we have as well, but by and large, when someone winds up asking a colleague or a friend or an acquaintance about the problem of their AWS bill, and the response almost universally, is, “Yeah, you should go talk to The Duckbill Group,” that says something that validates that we aren't going too far wrong with what we're approaching. Now that you're back on the freelance data side, I'm looking forward to continuing to work with you, if through no other means and being your customer, just because you solve very interesting and occasionally very specific problems that we periodically see. There's no reason that we can't bring specialists in—and we do from time to time—to look at very specific aspects of a customer problem or a customer constraint, or, in your case for example, a customer data set, which, “Hmm, I have some thoughts on here, but just optimizing what storage class that three petabytes of data lives within seems like it's maybe step two, after figuring what the heck is in it.” Baseline stuff. You know, the place that you live in that I hand-wave over because I'm scared of the complexity.Alex: I am very much looking forward to continuing to work with you on this. There's a whole bunch of really, really exciting opportunities there. And in terms of word of mouth, right, same here. Most of my inbound clientele came to me through word of mouth, especially in the first couple years. And I feel like that's how you know that you're doing it right.If someone hires you, that's one thing, and if someone refers you, to their friends, that's validation that they feel comfortable enough with you and with the work that you can do that they're not going to—you know, they're not going to pass their friends off to someone who's a chump, right? And that makes me feel good. Every time I go, “Oh, I heard from such and such that you're good at this. You want to help me with this?” Like, “Yes, absolutely.”Corey: I've really appreciated the opportunity to work with you and I'm super glad I got the chance to get to know you, including as a person, not just as the person who knows the data, but there's a human being there, too, believe it or not.Alex: Weird. [laugh].Corey: And that's the important part. If people want to learn more about what you're up to, how you think about these things, potentially have you looked at a gnarly data problem they've got, where's the best place to find you now?Alex: So, my business is called Bits on Disk. The website is bitsondisk.com. I do write occasionally there. I'm also on Twitter at @alexras. That's Alex-R-A-S, and I'm on LinkedIn as well. So, if your lovely listeners would like to reach me through any of those means, please don't hesitate to reach out. I would love to talk to them more about the challenges that they're facing in data and how I might be able to help them solve them.Corey: Wonderful. And we will of course, put links to that in the show notes. Thank you again for taking the time to speak with me, spending as much time working here as you did, and honestly, for a lot of the things that you've taught me along the way.Alex: My absolute pleasure. Thank you very much for having me.Corey: Alex Rasmussen, data engineering consultant at Bits on Disk. I'm Cloud Economist Corey Quinn. This is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment that is so large it no longer fits in RAM.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

For well over one hundred years, people have been attempting to make American colleges and universities more efficient and more accountable. Indeed, Ethan Ris argues in Other People's Colleges: The Origins of American Higher Education Reform (U Chicago Press, 2022), the reform impulse is baked into American higher education, the result of generations of elite reformers who have called for sweeping changes in the sector and raised existential questions about its sustainability. When that reform is beneficial, offering major rewards for minor changes, colleges and universities know how to assimilate it. When it is hostile, attacking autonomy or values, they know how to resist it. The result is a sector that has learned to accept top-down reform as part of its existence. In the early twentieth century, the “academic engineers,” a cadre of elite, external reformers from foundations, businesses, and government, worked to reshape and reorganize the vast base of the higher education pyramid. Their reform efforts were largely directed at the lower tiers of higher education, but those efforts fell short, despite the wealth and power of their backers, leaving a legacy of successful resistance that affects every college and university in the United States. Today, another coalition of business leaders, philanthropists, and politicians is again demanding efficiency, accountability, and utility from American higher education. But, as Ris argues, top-down design is not destiny. Drawing on extensive and original archival research, Other People's Colleges offers an account of higher education that sheds light on today's reform agenda. Joao Souto-Maior is PhD Student in Sociology of Education at the New York University. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/history

For well over one hundred years, people have been attempting to make American colleges and universities more efficient and more accountable. Indeed, Ethan Ris argues in Other People's Colleges: The Origins of American Higher Education Reform (U Chicago Press, 2022), the reform impulse is baked into American higher education, the result of generations of elite reformers who have called for sweeping changes in the sector and raised existential questions about its sustainability. When that reform is beneficial, offering major rewards for minor changes, colleges and universities know how to assimilate it. When it is hostile, attacking autonomy or values, they know how to resist it. The result is a sector that has learned to accept top-down reform as part of its existence. In the early twentieth century, the “academic engineers,” a cadre of elite, external reformers from foundations, businesses, and government, worked to reshape and reorganize the vast base of the higher education pyramid. Their reform efforts were largely directed at the lower tiers of higher education, but those efforts fell short, despite the wealth and power of their backers, leaving a legacy of successful resistance that affects every college and university in the United States. Today, another coalition of business leaders, philanthropists, and politicians is again demanding efficiency, accountability, and utility from American higher education. But, as Ris argues, top-down design is not destiny. Drawing on extensive and original archival research, Other People's Colleges offers an account of higher education that sheds light on today's reform agenda. Joao Souto-Maior is PhD Student in Sociology of Education at the New York University. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/american-studies

For well over one hundred years, people have been attempting to make American colleges and universities more efficient and more accountable. Indeed, Ethan Ris argues in Other People's Colleges: The Origins of American Higher Education Reform (U Chicago Press, 2022), the reform impulse is baked into American higher education, the result of generations of elite reformers who have called for sweeping changes in the sector and raised existential questions about its sustainability. When that reform is beneficial, offering major rewards for minor changes, colleges and universities know how to assimilate it. When it is hostile, attacking autonomy or values, they know how to resist it. The result is a sector that has learned to accept top-down reform as part of its existence. In the early twentieth century, the “academic engineers,” a cadre of elite, external reformers from foundations, businesses, and government, worked to reshape and reorganize the vast base of the higher education pyramid. Their reform efforts were largely directed at the lower tiers of higher education, but those efforts fell short, despite the wealth and power of their backers, leaving a legacy of successful resistance that affects every college and university in the United States. Today, another coalition of business leaders, philanthropists, and politicians is again demanding efficiency, accountability, and utility from American higher education. But, as Ris argues, top-down design is not destiny. Drawing on extensive and original archival research, Other People's Colleges offers an account of higher education that sheds light on today's reform agenda. Joao Souto-Maior is PhD Student in Sociology of Education at the New York University. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network

For well over one hundred years, people have been attempting to make American colleges and universities more efficient and more accountable. Indeed, Ethan Ris argues in Other People's Colleges: The Origins of American Higher Education Reform (U Chicago Press, 2022), the reform impulse is baked into American higher education, the result of generations of elite reformers who have called for sweeping changes in the sector and raised existential questions about its sustainability. When that reform is beneficial, offering major rewards for minor changes, colleges and universities know how to assimilate it. When it is hostile, attacking autonomy or values, they know how to resist it. The result is a sector that has learned to accept top-down reform as part of its existence. In the early twentieth century, the “academic engineers,” a cadre of elite, external reformers from foundations, businesses, and government, worked to reshape and reorganize the vast base of the higher education pyramid. Their reform efforts were largely directed at the lower tiers of higher education, but those efforts fell short, despite the wealth and power of their backers, leaving a legacy of successful resistance that affects every college and university in the United States. Today, another coalition of business leaders, philanthropists, and politicians is again demanding efficiency, accountability, and utility from American higher education. But, as Ris argues, top-down design is not destiny. Drawing on extensive and original archival research, Other People's Colleges offers an account of higher education that sheds light on today's reform agenda. Joao Souto-Maior is PhD Student in Sociology of Education at the New York University. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/education

For well over one hundred years, people have been attempting to make American colleges and universities more efficient and more accountable. Indeed, Ethan Ris argues in Other People's Colleges: The Origins of American Higher Education Reform (U Chicago Press, 2022), the reform impulse is baked into American higher education, the result of generations of elite reformers who have called for sweeping changes in the sector and raised existential questions about its sustainability. When that reform is beneficial, offering major rewards for minor changes, colleges and universities know how to assimilate it. When it is hostile, attacking autonomy or values, they know how to resist it. The result is a sector that has learned to accept top-down reform as part of its existence. In the early twentieth century, the “academic engineers,” a cadre of elite, external reformers from foundations, businesses, and government, worked to reshape and reorganize the vast base of the higher education pyramid. Their reform efforts were largely directed at the lower tiers of higher education, but those efforts fell short, despite the wealth and power of their backers, leaving a legacy of successful resistance that affects every college and university in the United States. Today, another coalition of business leaders, philanthropists, and politicians is again demanding efficiency, accountability, and utility from American higher education. But, as Ris argues, top-down design is not destiny. Drawing on extensive and original archival research, Other People's Colleges offers an account of higher education that sheds light on today's reform agenda. Joao Souto-Maior is PhD Student in Sociology of Education at the New York University. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/public-policy

For well over one hundred years, people have been attempting to make American colleges and universities more efficient and more accountable. Indeed, Ethan Ris argues in Other People's Colleges: The Origins of American Higher Education Reform (U Chicago Press, 2022), the reform impulse is baked into American higher education, the result of generations of elite reformers who have called for sweeping changes in the sector and raised existential questions about its sustainability. When that reform is beneficial, offering major rewards for minor changes, colleges and universities know how to assimilate it. When it is hostile, attacking autonomy or values, they know how to resist it. The result is a sector that has learned to accept top-down reform as part of its existence. In the early twentieth century, the “academic engineers,” a cadre of elite, external reformers from foundations, businesses, and government, worked to reshape and reorganize the vast base of the higher education pyramid. Their reform efforts were largely directed at the lower tiers of higher education, but those efforts fell short, despite the wealth and power of their backers, leaving a legacy of successful resistance that affects every college and university in the United States. Today, another coalition of business leaders, philanthropists, and politicians is again demanding efficiency, accountability, and utility from American higher education. But, as Ris argues, top-down design is not destiny. Drawing on extensive and original archival research, Other People's Colleges offers an account of higher education that sheds light on today's reform agenda. Joao Souto-Maior is PhD Student in Sociology of Education at the New York University. Learn more about your ad choices. Visit megaphone.fm/adchoices

I anledning Nerves episode 100 har jeg rett og slett slått meg sammen med en annen jubilant! Min samboer Gunnar Tjomlid har jubileum med sin podcast Tomprat episode 300(!) og derfor bestemte vi oss for å lage en felles prat som publiseres i begge våre podcaster. Det blir en lang prat om hvordan våre respektive podcaster har utviklet seg med både oppturer og nedturer, samt en gjennomgang av de siste seriene og filmene som har gjort inntrykk på oss.. -Både gode og dårlige. Gratulerer med jubileum til Tomprat og Nerve!-"Tomprat" finner du i din podcast app-Serier/filmer omtalt i episoden:"It comes at Night" film"Mr. Good?" på Netflix om Eirik Jensen"Hacks" på HBO"Next Level Chef" m Gordon Ramsay på NRK"Prehistoric Planet" Apple tv+"Black Bird" på Apple tv+"Barry" på HBO-Min andre podcast "Virkelig Grusomt" finnes i alle podcast apper-YouTube: www.youtube.com/tonesabro-Støtt meg på Patreon: www.patreon.com/tonesabro-Ris og ros: nervemedtone@gmail.com -Sosiale medier: @nervemedtone / @tonesabro

Går det an å tilnærme seg mediatasjon på en vitenskapelig måte? Jeg har tidligere assosiert meditasjon med de alternative og spiritualistiske hippie-veganerne jeg helst ikke vil sammenligne meg med, men har nylig fått en slags oppvåkning med hjelp av filosof og nevrobiolog Sam Harris. Utenom det har store deler av min tid i det siste gått i å fordype meg enda mer i Baneheia-saken. En utrolig grusom sak, men som også blir mer og mer fascinerende og sjokkerende etterhvert som sannheten belyses. En sak og prosess jeg mener vi alle bør få med oss.App-anbefaling for meditasjon: "Waking Up" med Sam HarrisBokanbefalinger: "Prosessen mot Viggo Kristiansen" av Bjørn Olav Jahr og "savnet i Baneheia" av Hilde Moi Østbø-Min andre podcast "Virkelig Grusomt" finnes i alle podcast apper-YouTube: www.youtube.com/tonesabro-Støtt meg på Patreon: www.patreon.com/tonesabro-Ris og ros: nervemedtone@gmail.com -Sosiale medier: @nervemedtone / @tonesabro

Hvordan går det an å skamme seg for å være "normalvektig"? Det å være spiseforstyrret forvrenger virkeligheten og snur opp-ned på "bra" og "dårlig", og det er utrolig vanskelig å komme seg ut av. Jeg deler mine tanker om hvordan det går nå, og hvorfor skammen fortsatt følger meg selv om vekten er "normal". Etter pandemi i flere år har også reisegleden fått seg en knekk.. Det er drit når man endelig har bestilt seg ferie.Bokanbefalinger om Alvdal-saken: "Mammas svik" og "I et hus i Alvdal: eldstesønnens historie"-Min andre podcast "Virkelig Grusomt" finnes i alle podcast apper-YouTube: www.youtube.com/tonesabro-Støtt meg på Patreon: www.patreon.com/tonesabro-Ris og ros: nervemedtone@gmail.com -Sosiale medier: @nervemedtone / @tonesabro

SD151 - GRUPO DEDALUS: líder mundial em software de saúde. Neste episódio, a conversa é com o CEO da DGS Brasil, Paulo Banevicius, para contar sobre a proposta de interoperabilidade do principal fornecedor de software de saúde e diagnóstico da Europa e que vem se consolidando no Brasil. A DEDALUS BRASIL faz parte do GRUPO DEDALUS, que é provedor líder de soluções de diagnóstico e gestão hospitalar na Europa e um dos maiores do mundo, entendendo que tem uma abrangência global, mas deve ter foco nas necessidades locais. Neste episódio, o que você vai encontrar: O background do Paulo  Ele atua na área de saúde há mais de 30 anos em diversos segmentos: tanto na área de equipamentos quanto na área de software. Fez Gestão Hospitalar pela FGV. Líder da DGS Brasil desde final de 2020. O desafio DEDALUS e sua trajetória de crescimento Crescimento inorgânico via aquisições de TIC Saúde da AGFA e da DXC Technology para consolidar mercado: manter a cultura e extrair valor da aquisição; Construção de identidade e de marca e coordenação da forma não monolítica das soluções adquiridas e na diversidade de formas de pensar que vem com a aquisição; encontrar soluções mais inteligentes, ágeis e melhores para o sistema de saúde. Interoperabilidade Plataforma poderosa que coordena a integração de ferramentas e softwares distintos. Resultados Resultados no mundo: aproximadamente $750 milhões/ano; 5ª maior cia. de software na indústria no segmento de saúde, sendo a maior da Europa; presente em aproximadamente 45 países com operação direta; fábrica de softwares em diferentes pólos, inclusive no Brasil; Clientes:  Rede D'Or; HC de Porto Alegre; HC de São Paulo para citar alguns. Algumas soluções Soluções para a Radiologia com software de arquivamento de imagens; Software para trabalhar a informação (RIS); Software para trabalhar a informação do hospital (HIS); Chegando: a gestão de escalas e turnos com a AIDA , gestão de agenda enterprise, entre outros; Engage4me para trazer engajamento do paciente e rastreamento por parte dos médicos e instituições. Futuro   Um modelo open health para o sistema de saúde > Estamos caminhando para isso? Comunidade Online Saúde Digital Podcast Você é médico e quer interagir comigo e com outros colegas inovadores da medicina digital?  Entre na Comunidade do Podcast Saúde Digital no SDConecta! Assista este episódio também em vídeo no YouTube no nosso canal Saúde Digital Ecossistema! Clique aqui! Episódios Anteriores - Acesse! SD150 - ISA LAB: A Descentralização do Home Care SD149 - A carreira do Médico Militar SD148 – Cardiopapers - A escola digital de 35 milhões de reais. SD147 - HackTown - O maior festival de inovação e criatividade da América Latina. SD146 - Escala App: Intraempreendedorismo de sucesso Música | Declan DP - With You "Music © Copyright Declan DP 2018 - Present. https://license.declandp.info | License ID: DDP1590665"

Nessa semana, a Camilla de Azevedo Pereira e a Bruna Karoline Pinto da Silva (PUC-Rio) vieram nos contar sobre o recém-fundado GEIRI Brasil: Grupo de Estudos sobre Infância e Relações Internacionais. As duas nos contaram como o grupo propõe trazer para o centro do debate sobre diversos temas das RIs as vozes e as situações vividas por crianças e jovens em todo o mundo a partir da sua multiplicidade. The post Infância nas relações internacionais appeared first on Chutando a Escada.

https://give.cornerstone.cc/wholesoulmasterydonatePart 1 of this 2-Part Video Series is the June 2022 Energy Update from The Arcturian Collective. In this transmission, the Guides spotlight The Unity Star & States of Sovereignty. June 2022 is a Tipping Point into Sovereignty!  The Guides spotlight our emerging awareness of Self Sovereignty, Divinity as an Inalienable Right, and our Infinite Soul Presence that is returning to us.  The Spiritual Battle on Planet Earth continues to play on and play out, but those with Higher Soul Sight and Big Picture Vision can see that this is The Resurrection Time, The Rising Time, and the Ascension Time that is ushering in This Great Shift of the Ages.  It is indeed an Epic Time.  Thank you for joining me and please do share with others who would benefit from these insights and positive energies.In Part 2 of this 2-Part Video Series, I share timely insights & soulful messages about this latest Energy Update and the frequencies that many are feeling at this time.  This marinades video will release on Saturday, June 4th.  So stay tuned to this channel for that release!Please like, subscribe, and share!Interested in a Soul Reading?  Or Vibration Coaching?  More Inspirational Messages and Products?  Please visit:https://frequencywriter.com​​​​Or email: info@frequencywriter.comTo listen to more amazing podcasts and insightful broadcasts, or to make a donation, visit:  http://www.wholesoulschoolandfoundation.orgTo donate: https://give.cornerstone.cc/wholesoulschoolandfoundationTo shop our apparel: https://www.bonfire.com/store/whole-soul-school-and-foundation/Thank you!Follow me via Whole Soul Mastery:Twitter: https://twitter.com/MasteryWholeFacebook: https://www.facebook.com/wholesoulmasteryRumble.com: https://rumble.com/c/c-353585​​​​UgeTube: https://ugetube.com/@wholesoulmastery​​​​Telegram: https://t.me/wholesoulmasteryTune into Frequency Writer Transmissions & Marinades, Whole Soul Mastery Podcasts with Amazing Guests, and Whole Soul School and Foundation's variety of inspiring podcasts via:Spotify, Apple iTunes, Buzzsprout, Stitcher, iHeartRadio, Google Play Music + other favorite podcast platforms Search:  Whole Soul Mastery or Whole Soul School and FoundationIf would like to support me and my work directly, please send donations to: https://give.cornerstone.cc/wholesoulmasterydonateYou can also mail donations to:Marie Mohler/Whole Soul Mastery1289 Fordham Blvd., Suite 259Chapel Hill, NC 27514Every donation is appreciated! Thank you

Microsoft had confusion in the Windows 2000 marketing and disappointment with Millennium Edition, which was built on a kernel that had run its course. It was time to phase out the older 95, 98, and Millennium code. So in 2001, Microsoft introduced Windows NT 5.1, known as Windows XP (eXperience). XP came in a Home or Professional edition.  Microsoft built a new interface they called Whistler for XP. It was sleeker and took more use of the graphics processors of the day. Jim Allchin was the Vice President in charge of the software group by then and helped spearhead development. XP had even more security options, which were simplified in the home edition. They did a lot of work to improve the compatibility between hardware and software and added the option for fast user switching so users didn't have to log off completely and close all of their applications when someone else needed to use the computer. They also improved on the digital media experience and added new libraries to incorporate DirectX for various games.  Professional edition also added options that were more business focused. This included the ability to join a network and Remote Desktop without the need of a third party product to take control of the keyboard, video, and mouse of a remote computer. Users could use their XP Home Edition computer to log into work, if the network administrator could forward the port necessary. XP Professional also came with the ability to support multiple processors, send faxes, an encrypted file system, more granular control of files and other objects (including GPOs), roaming profiles (centrally managed through Active Directory using those GPOs), multiple language support, IntelliMirror (an oft forgotten centralized management solution that included RIS and sysprep for mass deployments), an option to do an Automated System Recovery, or ASR restore of a computer. Professional also came with the ability to act as a web server, not that anyone should run one on a home operating system. XP Professional was also 64-bit given the right processor. XP Home Edition could be upgraded to from Windows 98, Windows 98 Second Edition, Millineum, and XP Professional could be upgraded to from any operating system since Windows 98 was released., including NT 4 and Windows 2000 Professional. And users could upgrade from Home to Professional for an additional $100.   Microsoft also fixed a few features. One that had plagued users was that they had to gracefully unmount a drive before removing it; Microsoft got in front of this when they removed the warning that a drive was disconnected improperly and had the software take care of that preemptively. They removed some features users didn't really use like NetMeeting and Phone Dialer and removed some of the themes options. The 3D Maze was also sadly removed. Other options just cleaned up the interface or merged technologies that had become similar, like Deluxe CD player and DVD player were removed in lieu of just using Windows Media Player. And chatty network protocols that caused problems like NetBEUI and AppleTalk were removed from the defaults, as was the legacy Microsoft OS/2 subsystem. In general, Microsoft moved from two operating system code bases to one. Although with the introduction of Windows CE, they arguably had no net-savings. However, to the consumer and enterprise buyer, it was a simpler licensing scheme. Those enterprise buyers were more and more important to Microsoft. Larger and larger fleets gave them buying power and the line items with resellers showed it with an explosion in the number of options for licensing packs and tiers. But feature-wise Microsoft had spent the Microsoft NT and Windows 2000-era training thousands of engineers on how to manage large fleets of Windows machines as Microsoft Certified Systems Engineers (MCSE) and other credentials. Deployments grew and by the time XP was released, Microsoft had the lions' share of the market for desktop operating systems and productivity apps. XP would only cement that lead and create a generation of systems administrators equipped to manage the platform, who never knew a way other than the Microsoft way. One step along the path to the MCSE was through servers. For the first couple of years, XP connected to Windows 2000 Servers. Windows Server 2003, which was built on the Windows NT 5.2 kernel, was then released in 2003. Here, we saw Active Directory cement a lead created in 2000 over servers from Novell and other vendors. Server 2003 became the de facto platform for centralized file, print, web, ftp, software  time, DHCP, DNS, event, messeging, and terminal services (or shared Remote Desktop services through Terminal Server). Server 2003 could also be purchased with Exchange 2003. Given the integration with Microsoft Outlook and a number of desktop services, Microsoft Exchange.  The groupware market in 2003 and the years that followed were dominated by Lotus Notes, Novell's GroupWise, and Exchange. Microsoft was aggressive. They were aggressive on pricing. They released tools to migrate from Notes to Exchange the week before IBM's conference. We saw some of the same tactics and some of the same faces that were involved in Microsoft's Internet Explorer anti-trust suit from the 1990s. The competition to Change never recovered and while Microsoft gained ground in the groupware space through the Exchange Server 4.0, 5.0, 5.5, 2000, 2003, 2007, 2010, 2013, and 2016 eras, by Exchange 2019 over half the mailboxes formerly hosted by on premises Exchange servers had moved to the cloud and predominantly Microsoft's Office 365 cloud service. Some still used legacy Unix mail services like sendmail or those hosted by third party providers like GoDaddy with their domain or website - but many of those ran on Exchange as well. The only company to put up true competition in the space has been Google. Other companies had released tools to manage Windows devices en masse. Companies like Altiris sprang out of needs for companies who did third party software testing to manage the state of Windows computers. Microsoft had a product called Systems Management Server but Altiris built a better product, so Microsoft built an even more robust solution called System Center Configuration Management server, or SCCM for short, and within a few years Altiris lost so much business they were acquired by Symantec. Other similar stories played out across other areas where each product competed with other vendors and sometimes market segments - and usually won. To a large degree this was because of the tight hold Windows had on the market. Microsoft had taken the desktop metaphor and seemed to own the entire stack by the end of the Windows XP era. However, the technology we used was a couple of years after the product management and product development teams started to build it. And by the end of the XP era, Bill Gates had been gone long enough, and many of the early stars that almost by pure will pushed products through development cycles were as well. Microsoft continued to release new versions of the operating systems but XP became one of the biggest competitors to later operating systems rather than other companies. This reluctance to move to Vista and other technologies was the main reason extended support for XP through to 2012, around 11 years after it was released. 

Order of Service: - Prelude - Hymn 351 - I Know That My Redeemer Lives: vv. 1-3, 6 & 8 - 1 Kings 17: 17-24: Now it happened after these things that the son of the woman who owned the house became sick. And his sickness was so serious that there was no breath left in him. So she said to Elijah, “What have I to do with you, O man of God? Have you come to me to bring my sin to remembrance, and to kill my son?” And he said to her, “Give me your son.” So he took him out of her arms and carried him to the upper room where he was staying, and laid him on his own bed. Then he cried out to the Lord and said, “O Lord my God, have You also brought tragedy on the widow with whom I lodge, by killing her son?” And he stretched himself out on the child three times, and cried out to the Lord and said, “O Lord my God, I pray, let this child's soul come back to him.” Then the Lord heard the voice of Elijah; and the soul of the child came back to him, and he revived. And Elijah took the child and brought him down from the upper room into the house, and gave him to his mother. And Elijah said, “See, your son lives!” Then the woman said to Elijah, “Now by this I know that you are a man of God, and that the word of the Lord in your mouth is the truth.” - Devotion - Prayer - Hymn 352 - Jesus Christ is Ris'n Today: vv. 1 & 2 - Blessing - Postlude Service Participants: Max Kerr (Preacher), Kaleb Schmidt (Organist)

About CaseyCasey spends his days leveraging AWS to help organizations improve the speed at which they deliver software. With a background in software development, he has spent the past 20 years architecting, building, and supporting software systems for organizations ranging from startups to Fortune 500 enterprises.Links Referenced: “17 Ways to Run Containers in AWS”: https://www.lastweekinaws.com/blog/the-17-ways-to-run-containers-on-aws/ “17 More Ways to Run Containers on AWS”: https://www.lastweekinaws.com/blog/17-more-ways-to-run-containers-on-aws/ kubernetestheeasyway.com: https://kubernetestheeasyway.com snark.cloud/quinntainers: https://snark.cloud/quinntainers ECS Chargeback: https://github.com/gaggle-net/ecs-chargeback  twitter.com/nektos: https://twitter.com/nektos TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored by our friends at Revelo. Revelo is the Spanish word of the day, and its spelled R-E-V-E-L-O. It means “I reveal.” Now, have you tried to hire an engineer lately? I assure you it is significantly harder than it sounds. One of the things that Revelo has recognized is something I've been talking about for a while, specifically that while talent is evenly distributed, opportunity is absolutely not. They're exposing a new talent pool to, basically, those of us without a presence in Latin America via their platform. It's the largest tech talent marketplace in Latin America with over a million engineers in their network, which includes—but isn't limited to—talent in Mexico, Costa Rica, Brazil, and Argentina. Now, not only do they wind up spreading all of their talent on English ability, as well as you know, their engineering skills, but they go significantly beyond that. Some of the folks on their platform are hands down the most talented engineers that I've ever spoken to. Let's also not forget that Latin America has high time zone overlap with what we have here in the United States, so you can hire full-time remote engineers who share most of the workday as your team. It's an end-to-end talent service, so you can find and hire engineers in Central and South America without having to worry about, frankly, the colossal pain of cross-border payroll and benefits and compliance because Revelo handles all of it. If you're hiring engineers, check out revelo.io/screaming to get 20% off your first three months. That's R-E-V-E-L-O dot I-O slash screaming.Corey: Couchbase Capella Database-as-a-Service is flexible, full-featured and fully managed with built in access via key-value, SQL, and full-text search. Flexible JSON documents aligned to your applications and workloads. Build faster with blazing fast in-memory performance and automated replication and scaling while reducing cost. Capella has the best price performance of any fully managed document database. Visit couchbase.com/screaminginthecloud to try Capella today for free and be up and running in three minutes with no credit card required. Couchbase Capella: make your data sing.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. My guest today is someone that I had the pleasure of meeting at re:Invent last year, but we'll get to that story in a minute. Casey Lee is the CTO with a company called Gaggle, which is—as they frame it—saving lives. Now, that seems to be a relatively common position that an awful lot of different tech companies take. “We're saving lives here.” It's, “You show banner ads and some of them are attack platforms for JavaScript malware. Let's be serious here.” Casey, thank you for joining me, and what makes the statement that Gaggle saves lives not patently ridiculous?Casey: Sure. Thanks, Corey. Thanks for having me on the show. So Gaggle, we're ed-tech company. We sell software to school districts, and school districts use our software to help protect their students while the students use the school-issued Google or Microsoft accounts.So, we're looking for signs of bullying, harassment, self-harm, and potentially suicide from K-12 students while they're using these platforms. They will take the thoughts, concerns, emotions they're struggling with and write them in their school-issued accounts. We detect that and then we notify the school districts, and they get the students the help they need before they can do any permanent damage to themselves. We protect about 6 million students throughout the US. We ingest a lot of content.Last school year, over 6 billion files, about the equal number of emails ingested. We're looking for concerning content and then we have humans review the stuff that our machine learning algorithms detect and flag. About 40 million items had to go in front of humans last year, resulted in about 20,000 what we call PSSes. These are Possible Student Situations where students are talking about harming themselves or harming others. And that resulted in what we like to track as lives saved. 1400 incidents last school year where a student was dealing with suicide ideation, they were planning to take their own lives. We detect that and get them help within minutes before they can act on that. That's what Gaggle has been doing. We're using tech, solving tech problems, and also saving lives as we do it.Corey: It's easy to lob a criticism at some of the things you're alluding to, the idea of oh, you're using machine learning on student data for young kids, yadda, yadda, yadda. Look at the outcome, look at the privacy controls you have in place, and look at the outcomes you're driving to. Now, I don't necessarily trust the number of school administrations not to become heavy-handed and overbearing with it, but let's be clear, that's not the intent. That is not what the success stories you have alluded to. I've got to say I'm a fan, so thanks for doing what you're doing. I don't say that very often to people who work in tech companies.Casey: Cool. Thanks, Corey.Corey: But let's rewind a bit because you and I had passed like ships in the night on Twitter for a while, but last year at re:Invent something odd happened. First, my business partner procrastinated at getting his ticket—that's not the odd part; he does that a lot—but then suddenly ticket sales slammed shut and none were to be had anywhere. You reached out with a, “Hey, I have a spare ticket because someone can't go. Let me get it to you.” And I said, “Terrific. Let me pay you for the ticket and take you to dinner.”You said, “Yes on the dinner, but I'd rather you just look at my AWS bill and don't worry about the cost of the ticket.” “All right,” said I. I know a deal when I see one. We grabbed dinner at the Venetian. I said, “Bust out your laptop.” And you said, “Oh, I was kidding.” And I said, “Great. I wasn't. Bust it out.”And you went from laughing to taking notes in about the usual time that happens when I start looking at these things. But how was your recollection of that? I always tend to romanticize some of these things. Like, “And then everyone's restaurant just turned, stopped, and clapped the entire time.” Maybe that part didn't happen.Casey: Everything was right up until the clapping part. That was a really cool experience. I appreciate you walking through that with me. Yeah, we've got lots of opportunity to save on our AWS bill here at Gaggle, and in that little bit of time that we had together, I think I walked away with no more than a dozen ideas for where to shave some costs. The most obvious one, the first thing that you keyed in on, is we had RIs coming due that weren't really well-optimized and you steered me towards savings plans. We put that in place and we're able to apply those savings plans not just to our EC2 instances but also to our serverless spend as well.So, that was a very worthwhile and cost-effective dinner for us. The thing that was most surprising though, Corey, was your approach. Your approach to how to review our bill was not what I thought at all.Corey: Well, what did you expect my approach was going to be? Because this always is of interest to me. Like, do you expect me to, like, whip a portable machine learning rig out of my backpack full of GPUs or something?Casey: I didn't know if you had, like, some secret tool you were going to hit, or if nothing else, I thought you were going to go for the Cost Explorer. I spend a lot of time in Cost Explorer, that's my go-to tool, and you wanted nothing to do with Cost Exp—I think I was actually pulling up Cost Explorer for you and you said, “I'm not interested. Take me to the bills.” So, we went right to the billing dashboard, you started opening up the invoices, and I thought to myself, “I don't remember the last time I looked at an AWS invoice.” I just, it's noise; it's not something that I pay attention to.And I learned something, that you get a real quick view of both the cost and the usage. And that's what you were keyed in on, right? And you were looking at things relative to each other. “Okay, I have no idea about Gaggle or what they do, but normally, for a company that's spending x amount of dollars in EC2, why is your data transfer cost the way it is? Is that high or low?” So, you're looking for kind of relative numbers, but it was really cool watching you slice and dice that bill through the dashboard there.Corey: There are a few things I tie together there. Part of it is that this is sort of a surprising thing that people don't think about but start with big numbers first, rather than going alphabetically because I don't really care about your $6 Alexa for Business spend. I care a bit more about the $6 million, or whatever it happens to be at EC2—I'm pulling numbers completely out of the ether, let's be clear; I don't recall what the exact magnitude of your bill is and it's not relevant to the conversation.And then you see that and it's like, “Huh. Okay, you're spending $6 million on EC2. Why are you spending 400 bucks on S3? Seems to me that those two should be a little closer aligned. What's the deal here? Oh, God, you're using eight petabytes of EBS volumes. Oh, dear.”And just, it tends to lead to interesting stuff. Break it down by region, service, and use case—or usage type, rather—is what shows up on those exploded bills, and that's where I tend to start. It also is one of the easiest things to wind up having someone throw into a PDF and email my way if I'm not doing it in a restaurant with, you know, people clapping standing around.Casey: [laugh]. Right.Corey: I also want to highlight that you've been using AWS for a long time. You're a Container Hero; you are not bad at understanding the nuances and depths of AWS, so I take praise from you around this stuff as valuing it very highly. This stuff is not intuitive, it is deeply nuanced, and you have a business outcome you are working towards that invariably is not oriented day in day out around, “How do I get these services for less money than I'm currently paying?” But that is how I see the world and I tend to live in a very different space just based on the nature of what I do. It's sort of a case study and the advantage of specialization. But I know remarkably little about containers, which is how we wound up reconnecting about a week or so before we did this recording.Casey: Yeah. I saw your tweet; you were trying to run some workload—container workload—and I could hear the frustration on the other end of Twitter when you were shaking your fist at—Corey: I should not tweet angrily, and I did in this case. And, eh, every time I do I regret it. But it played well with the people, so that does help. I believe my exact comment was, “‘me: I've got this container. Run it, please.' ‘Google Cloud: Run. You got it, boss.' AWS has 17 ways to run containers and they all suck.”And that's painting with an overly broad brush, let's be clear, but that was at the tail end of two or three days of work trying to solve a very specific, very common, business problem, that I was just beating my head off of a wall again and again and again. And it took less than half an hour from start to finish with Google Cloud Run and I didn't have to think about it anymore. And it's one of those moments where you look at this and realize that the future is here, we just don't see it in certain ways. And you took exception to this. So please, let's dive in because 280 characters of text after half a bottle of wine is not the best context to have a nuanced discussion that leaves friendships intact the following morning.Casey: Nice. Well, I just want to make sure I understand the use case first because I was trying to read between the lines on what you needed, but let me take a guess. My guess is you got your source code in GitHub, you have a Docker file, and you want to be able to take that repo from GitHub and just have it continuously deployed somewhere in Run. And you don't want to have headaches with it; you just want to push more changes up to GitHub, Docker Build runs and updates some service somewhere. Am I right so far?Corey: Ish, but think a little further up the stack. It was in service of this show. So, this show, as people who are listening to this are probably aware by this point, periodically has sponsors, which we love: We thank them for participating in the ongoing support of this show, which empowers conversations like this. Sometimes a sponsor will come to us with, “Oh, and here's the URL we want to give people.” And it's, “First, you misspelled your company name from the common English word; there are three sublevels within the domain, and then you have a complex UTM tagging tracking co—yeah, you realize people are driving to work when they're listening to this?”So, I've built a while back a link shortener, snark.cloud because is it the shortest thing in the world? Not really, but it's easily understandable when I say that, and people hear it for what it is. And that's been running for a long time as an S3 bucket with full of redirects, behind CloudFront. So, I wind up adding a zero-byte object with a redirect parameter on it, and it just works.Now, the challenge that I have here as a business is that I am increasingly prolific these days. So, anything that I am not directly required to be doing, I probably shouldn't necessarily be the one to do it. And care and feeding of those redirect links is a prime example of this. So, I went hunting, and the things that I was looking for were, obviously, do the redirect. Now, if you pull up GitHub, there are hundreds of solutions here.There are AWS blog posts. One that I really liked and almost got working was Eric Johnson's three-part blog post on how to do it serverlessly, with API Gateway, and DynamoDB, no Lambdas required. I really liked aspects of what that was, but it was complex, I kept smacking into weird challenges as I went, and front end is just baffling to me. Because I needed a front end app for people to be able to use here; I need to be able to secure that because it turns out that if you just have a, anyone who stumbles across the URL can redirect things to other places, well, you've just empowered a whole bunch of spam email, and you're going to find that service abused, and everyone starts blocking it, and then you have trouble. Nothing lasts the first encounter with jerks.And I was getting more and more frustrated, and then I found something by a Twitter engineer on GitHub, with a few creative search terms, who used to work at Google Cloud. And what it uses as a client is it doesn't build any kind of custom web app. Instead, as a database, it uses not S3 objects, not Route 53—the ideal database—but a Google sheet, which sounds ridiculous, but every business user here knows how to use that.Casey: Sure.Corey: And it looks for the two columns. The first one is the slug after the snark.cloud, and the second is the long URL. And it has a TTL of five seconds on cache, so make a change to that spreadsheet, five seconds later, it's live. Everyone gets it, I don't have to build anything new, I just put it somewhere around the relevant people can access it, I gave him a tutorial and a giant warning on it, and everyone gets that. And it just works well. It was, “Click here to deploy. Follow the steps.”And the documentation was a little, eh, okay, I had to undo it once and redo it again. Getting the domain registered was getting—ported over took a bit of time, and there were some weird SSL errors as the certificates were set up, but once all of that was done, it just worked. And I tested the heck out of it, and cold starts are relatively low, and the entire thing fits within the free tier. And it is reminiscent of the magic that I first saw when I started working with some of the cloud providers services, years ago. It's been a long time since I had that level of delight with something, especially after three days of frustration. It's one of the, “This is a great service. Why are people not shouting about this from the rooftops?” That was my perspective. And I put it out on Twitter and oh, Lord, did I get comments. What was your take on it?Casey: Well, so my take was, when you're evaluating a platform to use for running your applications, how fast it can get you to Hello World is not necessarily the best way to go. I just assumed you're wrong. I assumed of the 17 ways AWS has to run containers, Corey just doesn't understand. And so I went after it. And I said, “Okay, let me see if I can find a way that solves his use case, as I understand it, through a quick tweet.”And so I tried to App Runner; I saw that App Runner does not meet your needs because you have to somehow get your Docker image pushed up to a repo. App Runner can take an image that's already been pushed up and deployed for you or it can build from source but neither of those were the way I understood your use case.Corey: Having used App Runner before via the Copilot CLI, it is the closest as best I can tell to achieving what I want. But also let's be clear that I don't believe there's a free tier; there needs to be a load balancer in front of it, so you're starting with 15 bucks a month for this thing. Which is not the end of the world. Had I known at the beginning that all of this was going to be there, I would have just signed up for a bit.ly account and called it good. But here we are.Casey: Yeah. I tried Copilot. Copilot is a great developer experience, but it also is just pulling together tons of—I mean just trying to do a Copilot service deploy, VPCs are being created and tons IAM roles are being created, code pipelines, there's just so much going on. I was like 20 minutes into it, and I said, “Yeah, this is not fitting the bill for what Corey was looking for.” Plus, it doesn't solve my the way I understood your use case, which is you don't want to worry about builds, you just want to push code and have new Docker images get built for you.Corey: Well, honestly, let's be clear here, once it's up and running, I don't want to ever have to touch the silly thing again.Casey: Right.Corey: And that's so far has been the case, after I forked the repo and made a couple of changes to it that I wanted to see. One of them was to render the entire thing case insensitive because I get that one wrong a lot, and the other is I wanted to change the permanent 301 redirect to a temporary 302 redirect because occasionally, sponsors will want to change where it goes in the fullness of time. And that is just fine, but I want to be able to support that and not have to deal with old cached data. So, getting that up and running was a bit of a challenge. But the way that it worked, was following the instructions in the GitHub repo.The developer environment had spun up in the Google's Cloud Shell was just spectacular. It prompted me for a few things and it told me step by step what to do. This is the sort of thing I could have given a basically non-technical user, and they would have had success with it.Casey: So, I tried it as well. I said, “Well, okay, if I'm going to respond to Corey here and challenge him on this, I need to try Cloud Run.” I had no experience with Cloud Run. I had a small example repo that loosely mapped what I understood you were trying to do. Within five minutes, I had Cloud Run working.And I was surprised anytime I pushed a new change, within 45 seconds the change was built and deployed. So, here's my conclusion, Corey. Google Cloud Run is great for your use case, and AWS doesn't have the perfect answer. But here's my challenge to you. I think that you just proved why there's 17 different ways to run containers on AWS, is because there's that many different types of users that have different needs and you just happen to be number 18 that hasn't gotten the right attention yet from AWS.Corey: Well, let's be clear, like, my gag about 17 ways to run containers on AWS was largely a joke, and it went around the internet three times. So, I wrote a list of them on the blog post of “17 Ways to Run Containers in AWS” and people liked it. And then a few months later, I wrote “17 More Ways to Run Containers on AWS” listing 17 additional services that all run containers.And my favorite email that I think I've ever received in feedback was from a salty AWS employee, saying that one of them didn't really count because of some esoteric reason. And it turns out that when I'm trying to make a point of you have a sarcastic number of ways to run containers, pointing out that well, one of them isn't quite valid, doesn't really shatter the argument, let's be very clear here. So, I appreciate the feedback, I always do. And it's partially snark, but there is an element of truth to it in that customers don't want to run containers, by and large. That is what they do in service of a business goal.And they want their application to run which is in turn to serve as the business goal that continues to abstract out into, “Remain a going concern via the current position the company stakes out.” In your case, it is saving lives; in my case, it is fixing horrifying AWS bills and making fun of Amazon at the same time, and in most other places, there are somewhat more prosaic answers to that. But containers are simply an implementation detail, to some extent—to my way of thinking—of getting to that point. An important one [unintelligible 00:18:20], let's be clear, I was very anti-container for a long time. I wrote a talk, “Heresy in the Church of Docker” that then was accepted at ContainerCon. It's like, “Oh, boy, I'm not going to leave here alive.”And the honest answer is many years later, that Kubernetes solves almost all the criticisms that I had with the downside of well, first, you have to learn Kubernetes, and that continues to be mind-bogglingly complex from where I sit. There's a reason that I've registered kubernetestheeasyway.com and repointed it to ECS, Amazon's container service that is not requiring you to cosplay as a cloud provider yourself. But even ECS has a number of challenges to it, I want to be very clear here. There are no silver bullets in this.And you're completely correct in that I have a large, complex environment, and the application is nuanced, and I'm willing to invest a few weeks in setting up the baseline underlying infrastructure on AWS with some of these services, ideally not all of them at once because that's something a lunatic would do, but getting them up and running. The other side of it, though, is that if I am trying to evaluate a cloud provider's handling of containers and how this stuff works, the reason that everyone starts with a Hello World-style example is that it delivers ideally, the meantime to dopamine. There's a reason that Hello World doesn't have 18 different dependencies across a bunch of different databases and message queues and all the other complicated parts of running a modern application. Because you just want to see how it works out of the gate. And if getting that baseline empty container that just returns the string ‘Hello World' is that complicated and requires that much work, my takeaway is not that this user experience is going to get better once I'd make the application itself more complicated.So, I find that off-putting. My approach has always been find something that I can get the easy, minimum viable thing up and running on, and then as I expand know that you'll be there to catch me as my needs intensify and become ever more complex. But if I can't get the baseline thing up and running, I'm unlikely to be super enthused about continuing to beat my head against the wall like, “Well, I'll just make it more complex. That'll solve the problem.” Because it often does not. That's my position.Casey: Yeah, I agree that dopamine hit is valuable in getting attached to want to invest into whatever tech stack you're using. The challenge is your second part of that. Your second part is will it grow with me and scale with me and support the complex edge cases that I have? And the problem I've seen is a lot of organizations will start with something that's very easy to get started with and then quickly outgrow it, and then come up with all sorts of weird Rube Goldberg-type solutions. Because they jumped all in before seeing—I've got kind of an example of that.I'm happy to announce that there's now 18 ways to run containers on AWS. Because in your use case, in the spirit of AWS customer obsession, I hear your use case, I've created an open-source project that I want to share called Quinntainers—Corey: Oh, no.Casey: —and it solves—yes. Quinntainers is live and is ready for the world. So, now we've got 18 ways to run containers. And if you have Corey's use case of, “Hey, here's my container. Run it for me,” now we've got a one command that you can run to get things going for you. I can share a link for you and you could check it out. This is a [unintelligible 00:21:38]—Corey: Oh, we're putting that in the [show notes 00:21:37], for sure. In fact, if you go to snark.cloud/quinntainers, you'll find it.Casey: You'll find it. There you go. The idea here was this: There is a real use case that you had, and I looked at AWS does not have an out-of-the-box simple solution for you. I agree with that. And Google Cloud Run does.Well, the answer would have been from AWS, “Well, then here, we need to make that solution.” And so that's what this was, was a way to demonstrate that it is a solvable problem. AWS has all the right primitives, just that use case hadn't been covered. So, how does Quinntainers work? Real straightforward: It's a command-line—it's an NPM tool.You just run a [MPX 00:22:17] Quinntainer, it sets up a GitHub action role in your AWS account, it then creates a GitHub action workflow in your repo, and then uses the Quinntainer GitHub action—reusable action—that creates the image for you; every time you push to the branch, pushes it up to ECR, and then automatically pushes up that new version of the image to App Runner for you. So, now it's using App Runner under the covers, but it's providing that nice developer experience that you are getting out of Cloud Run. Look, is container really the right way to go with running containers? No, I'm not making that point at all. But the point is it is a—Corey: It might very well be.Casey: Well, if you want to show a good Hello World experience, Quinntainer's the best because within 30 seconds, your app is now set up to continuously deliver containers into AWS for your very specific use case. The problem is, it's not going to grow for you. I mean that it was something I did over the weekend just for fun; it's not something that would ever be worthy of hitching up a real production workload to. So, the point there is, you can build frameworks and tools that are very good at getting that initial dopamine hit, but then are not going to be there for you unnecessarily as you mature and get more complex.Corey: And yet, I've tilted a couple of times at the windmill of integrating GitHub actions in anything remotely resembling a programmatic way with AWS services, as far as instance roles go. Are you using permanent credentials for this as stored secrets or are you doing the [OICD 00:23:50][00:23:50] handoff?Casey: OIDC. So, what happens is the tool creates the IAM role for you with the trust policy on GitHub's OIDC provider, sets all that up for you in your account, locks it down so that just your repo and your main branch is able to push or is able to assume the role, the role is set up just to allow deployments to App Runner and ECR repository. And then that's it. At that point, it's out of your way. And you're just git push, and couple minutes later, your updates are now running an App Runner for you.Corey: This episode is sponsored in part by our friends at Vultr. Optimized cloud compute plans have landed at Vultr to deliver lightning fast processing power, courtesy of third gen AMD EPYC processors without the IO, or hardware limitations, of a traditional multi-tenant cloud server. Starting at just 28 bucks a month, users can deploy general purpose, CPU, memory, or storage optimized cloud instances in more than 20 locations across five continents. Without looking, I know that once again, Antarctica has gotten the short end of the stick. Launch your Vultr optimized compute instance in 60 seconds or less on your choice of included operating systems, or bring your own. It's time to ditch convoluted and unpredictable giant tech company billing practices, and say goodbye to noisy neighbors and egregious egress forever.Vultr delivers the power of the cloud with none of the bloat. "Screaming in the Cloud" listeners can try Vultr for free today with a $150 in credit when they visit getvultr.com/screaming. That's G E T V U L T R.com/screaming. My thanks to them for sponsoring this ridiculous podcast.Corey: Don't undersell what you've just built. This is something that—is this what I would use for a large-scale production deployment, obviously not, but it has streamlined and made incredibly accessible things that previously have been very complex for folks to get up and running. One of the most disturbing themes behind some of the feedback I got was, at one point I said, “Well, have you tried running a Docker container on Lambda?” Because now it supports containers as a packaging format. And I said no because I spent a few weeks getting Lambda up and running back when it first came out and I've basically been copying and pasting what I got working ever since the way most of us do.And response is, “Oh, that explains a lot.” With the implication being that I'm just a fool. Maybe, but let's be clear, I am never the only person in the room who doesn't know how to do something; I'm just loud about what I don't know. And the failure mode of a bad user experience is that a customer feels dumb. And that's not okay because this stuff is complicated, and when a user has a bad time, it's a bug.I learned that in 2012. From Jordan Sissel the creator of LogStash. He has been an inspiration to me for the last ten years. And that's something I try to live by that if a user has a bad time, something needs to get fixed. Maybe it's the tool itself, maybe it's the documentation, maybe it's the way that GitHub repo's readme is structured in a way that just makes it accessible.Because I am not a trailblazer in most things, nor do I intend to be. I'm not the world's best engineer by a landslide. Just look at my code and you'd argue the fact that I'm an engineer at all. But if it's bad and it works, how bad is it? Is sort of the other side of it.So, my problem is that there needs to be a couple of things. Ignore for a second the aspect of making it the right answer to get something out of the door. The fact that I want to take this container and just run it, and you and I both reach for App Runner as the default AWS service that does this because I've been swimming in the AWS waters a while and you're a frickin AWS Container Hero, where it is expected that you know what most of these things do. For someone who shows up on the containers webpage—which by the way lists, I believe 15 ways to run containers on mobile and 19 ways to run containers on non-mobile, which is just fascinating in its own right—and it's overwhelming, it's confusing, and it's not something that makes it is abundantly clear what the golden path is. First, get it up and working, get it running, then you can add nuance and flavor and the rest, and I think that's something that's gotten overlooked in our mad rush to pretend that we're all Google engineers, circa 2012.Casey: Mmm. I think people get stressed out when they tried to run containers in AWS because they think, “What is that golden path?” You said golden path. And my advice to people is there is no golden path. And the great thing about AWS is they do continue to invest in the solutions they come up with. I'm still bitter about Google Reader.Corey: As am I.Casey: Yeah. I built so much time getting my perfect set of RSS feeds and then I had to find somewhere else to—with AWS, the different offerings that are available for running containers, those are there intentionally, it's not by accident. They're there to solve specific problems, so the trick is finding what works best for you and don't feel like one is better than the other is going to get more attention than others. And they each have different use cases.And I approach it this way. I've seen a couple of different people do some great flowcharts—I think Forrest did one, Vlad did one—on ways to make the decision on how to run your containers. And I break it down to three questions. I ask people first of all, where are you going to run these workloads? If someone says, “It has to be in the data center,” okay, cool, then ECS Anywhere or EKS Anywhere and we'll figure out if Kubernetes is needed.If they need specific requirements, so if they say, “No, we can run in the cloud, but we need privileged mode for containers,” or, “We need EBS volumes,” or, “We want really small container sizes,” like, less than a quarter-VCP or less than half a gig of RAM—or if you have custom log requirements, Fargate is not going to work for you, so you're going to run on EC2. Otherwise, run it on Fargate. But that's the first question. Figure out where are you going to run your containers. That leads to the second question: What's your control plane?But those are different, sort of related but different questions. And I only see six options there. That's App Runner for your control plane, LightSail for your control plane, Rosa if you're invested in OpenShift already, EKS either if you have Momentum and Kubernetes or you have a bunch of engineers that have a bunch of experience with Kubernetes—if you don't have either, don't choose it—or ECS. The last option Elastic Beanstalk, but let's leave that as a—if you're not currently invested in Elastic Beanstalk don't start today. But I look at those as okay, so I—first question, where am I going to run my containers? Second question, what do I want to use for my control plane? And there's different pros and cons of each of those.And then the third question, how do I want to manage them? What tools do I want to use for managing deployment? All those other tools like Copilot or App2Container or Proton, those aren't my control plane; those aren't where I run my containers; that's how I manage, deploy, and orchestrate all the different containers. So, I look at it as those three questions. But I don't know, what do you think of that, Corey?Corey: I think you're onto something. I think that is a terrific way of exploring that question. I would argue that setting up a framework like that—one or very similar—is what the AWS containers page should be, just coming from the perspective of what is the neophyte customer experience. On some level, you almost need a slide of have choose your level of experience ranging from, “What's a container?” To, “I named my kid Kubernetes because I make terrible life decisions,” and anywhere in between.Casey: Sure. Yeah, well, and I think that really dictates the control plane level. So, for example, LightSail, where does LightSail fit? To me, the value of LightSail is the simplicity. I'm looking at a monthly pricing: Seven bucks a month for a container.I don't know how [unintelligible 00:30:23] works, but I can think in terms of monthly pricing. And it's tailored towards a console user, someone just wants to click in, point to an image. That's a very specific user, there's thousands of customers that are very happy with that experience, and they use it. App Runner presents that scale to zero. That's one of the big selling points I see with App Runner. Likewise, with Google Cloud Run. I've got that scale to zero. I can't do that with ECS, or EKS, or any of the other platforms. So, if you've got something that has a ton of idle time, I'd really be looking at those. I would argue that I think I did the math, Google Cloud Run is about 30% more expensive than App Runner.Corey: Yeah, if you disregard the free tier, I think that's have it—running persistently at all times throughout the month, the drop-out cold starts would cost something like 40 some odd bucks a month or something like that. Don't quote me on it. Again and to be clear, I wound up doing this very congratulatory and complimentary tweet about them on I think it was Thursday, and then they immediately apparently took one look at this and said, “Holy shit. Corey's saying nice things about us. What do we do? What do we do?” Panic.And the next morning, they raised prices on a bunch of cloud offerings. Whew, that'll fix it. Like—Casey: [laugh].Corey: Di-, did you miss the direction you're going on here? No, that's the exact opposite of what you should be doing. But here we are. Interestingly enough, to tie our two conversation threads together, when I look at an AWS bill, unless you're using Fargate, I can't tell whether you're using Kubernetes or not because EKS is a small charge. And almost every case for the control plane, or Fargate under it.Everything else just manifests as EC2 spend. From the perspective of the cloud provider. If you're running a Kubernetes cluster, it is a single-tenant application that can have some very funky behaviors like cross-AZ chatter back and fourth because there's no internal mechanism to say talk to the free thing, rather than the two cents a gigabyte thing. It winds up spinning up and down in a bunch of different ways, and the behavior patterns, because of how placement works are not necessarily deterministic, depending upon workload. And that becomes something that people find odd when, “Okay, we look at our bill for a week, what can you say?”“Well, first question. Are you running Kubernetes at all?” And they're like, “Who invited these clowns?” Understand, we're not prying into your workloads for a variety of excellent legal and contractual reasons, here. We are looking at how they behave, and for specific workloads, once we have a conversation engineering team, yeah, we're going to dive in, but it is not at all intuitive from the outside to make any determination whether you're running containers, or whether you're running VMs that you just haven't done anything with in 20 years, or what exactly is going on. And that's just an artifact of the billing system.Casey: We ran into this challenge in Gaggle. We don't use EKS, we use ECS, but we have some shared clusters, lots of EC2 spend, hard to figure out which team is creating the services that's running that up. We actually ended up creating a tool—we open-sourced it—ECS Chargeback, and what it does is it looks at the CPU memory reservations for each task definition, and then prorates the overall charge of the ECS cluster, and then creates metrics in Datadog to give us a breakdown of cost per ECS service. And it also measures what we like to refer to as waste, right? Because if you're reserving four gigs of memory, but your utilization never goes over two gigs, we're paying for that reservation, but you're underutilizing.So, we're able to also show which services have the highest degree of waste, not just utilization, so it helps us go after it. But this is a hard problem. I'd be curious, how do you approach these shared ECS resources and slicing and dicing those bills?Corey: Everyone has a different approach, too. This there is no unifiable, correct answer. A previous show guest, Peter Hamilton, over at Remind had done something very similar, open-sourced a bunch of these things. Understanding what your spend is important on this, and it comes down to getting at the actual business concern because in some cases, effectively dead reckoning is enough. You take a look at the cluster that is really hard to attribute because it's a shared service. Great. It is 5% of your bill.First pass, why don't we just agree that it is a third for Service A, two-thirds for Service B, and we'll call it mostly good at that point? That can be enough in a lot of cases. With scale [laugh] you're just sort of hand-waving over many millions of dollars a year there. How about we get into some more depth? And then you start instrumenting and reporting to something, be it CloudWatch, be a Datadog, be it something else, and understanding what the use case is.In some cases, customers have broken apart shared clusters for that specific reason. I don't think that's necessarily the best approach from an engineering perspective, but again, this is not purely an engineering decision. It comes down to serving the business need. And if you're taking up partial credits on that cluster, for a tax credit for R&D for example, you want that position to be extraordinarily defensible, and spending a few extra dollars to ensure that it is the right business decision. I mean, again, we're pure advisory; we advise customers on what we would do in their position, but people often mistake that to be we're going to go for the lowest possible price—bad idea, or that we're going to wind up doing this from a purely engineering-centric point of view.It's, be aware of that in almost every case, with some very notable weird exceptions, the AWS Bill costs significantly less than the payroll expense that you have of people working on the AWS environment in various ways. People are more expensive, so the idea of, well, you can save a whole bunch of engineering effort by spending a bit more on your cloud, yeah, let's go ahead and do that.Casey: Yeah, good point.Corey: The real mark of someone who's senior enough is their answer to almost any question is, “It depends.” And I feel I've fallen into that trap as well. Much as I'd love to sit here and say, “Oh, it's really simple. You do X, Y, and Z.” Yeah… honestly, my answer, the simple answer, is I think that we orchestrate a cyber-bullying campaign against AWS through the AWS wishlist hashtag, we get people to harass their account managers with repeated requests for, “Hey, could you go ahead and [dip 00:36:19] that thing in—they give that a plus-one for me, whatever internal system you're using?”Just because this is a problem we're seeing more and more. Given that it's an unbounded growth problem, we're going to see it more and more for the foreseeable future. So, I wish I had a better answer for you, but yeah, that's stuff's super hard is honest, but it's also not the most useful answer for most of us.Casey: I'd love feedback from anyone from you or your team on that tool that we created. I can share link after the fact. ECS Chargeback is what we call it.Corey: Excellent. I will follow up with you separately on that. That is always worth diving into. I'm curious to see new and exciting approaches to this. Just be aware that we have an obnoxious talent sometimes for seeing these things and, “Well, what about”—and asking about some weird corner edge case that either invalidates the entire thing, or you're like, “Who on earth would ever have a problem like that?” And the answer is always, “The next customer.”Casey: Yeah.Corey: For a bounded problem space of the AWS bill. Every time I think I've seen it all, I just have to talk to one more customer.Casey: Mmm. Cool.Corey: In fact, the way that we approached your teardown in the restaurant is how we launched our first pass approach. Because there's value in something like that is different than the value of a six to eight-week-long, deep-dive engagement to every nook and cranny. And—Casey: Yeah, for sure. It was valuable to us.Corey: Yeah, having someone come in to just spend a day with your team, diving into it up one side and down the other, it seems like a weird thing, like, “How much good could you possibly do in a day?” And the answer in some cases is—we had a Honeycomb saying that in a couple of days of something like this, we wound up blowing 10% off their entire operating budget for the company, it led to an increased valuation, Liz Fong-Jones says that—on multiple occasions—that the company would not be what it was without our efforts on their bill, which is just incredibly gratifying to hear. It's easy to get lost in the idea of well, it's the AWS bill. It's just making big companies spend a little bit less to another big company. And that's not exactly, you know, saving the lives of K through 12 students here.Casey: It's opening up opportunities.Corey: Yeah. It's about optimizing for the win for everyone. Because now AWS gets a lot more money from Honeycomb than they would if Honeycomb had not continued on their trajectory. It's, you can charge customers a lot right now, or you can charge them a little bit over time and grow with them in a partnership context. I've always opted for the second model rather than the first.Casey: Right on.Corey: But here we are. I want to thank you for taking so much time out of well, several days now to argue with me on Twitter, which is always appreciated, particularly when it's, you know, constructive—thanks for that—Casey: Yeah.Corey: For helping me get my business partner to re:Invent, although then he got me that horrible puzzle of 1000 pieces for the Cloud-Native Computing Foundation landscape and now I don't ever want to see him again—so you know, that happens—and of course, spending the time to write Quinntainers, which is going to be at snark.cloud/quinntainers as soon as we're done with this recording. Then I'm going to kick the tires and send some pull requests.Casey: Right on. Yeah, thanks for having me. I appreciate you starting the conversation. I would just conclude with I think that yes, there are a lot of ways to run containers in AWS; don't let it stress you out. They're there for intention, they're there by design. Understand them.I would also encourage people to go a little deeper, especially if you got a significantly large workload. You got to get your hands dirty. As a matter of fact, there's a hands-on lab that a company called Liatrio does. They call it their Night Lab; it's a one-day free, hands-on, you run legacy monolithic job applications on Kubernetes, gives you first-hand experience on how to—gets all the way up into observability and doing things like Canary deployments. It's a great, great lab.But you got to do something like that to really get your hands dirty and understand how these things work. So, don't sweat it; there's not one right way. There's a way that will probably work best for each user, and just take the time and understand the ways to make sure you're applying the one that's going to give you the most runway for your workload.Corey: I will definitely dig into that myself. But I think you're right, I think you have nailed a point that is, again, a nuanced one and challenging to put in a rage tweet. But the services don't exist in a vacuum. They're not there because, despite the joke, someone wants to get promoted. It's because there are customer needs that are going on that, and this is another way of meeting those needs.I think there could be better guidance, but I also understand that there are a lot of nuanced perspectives here and that… hell is someone else's workflow—Casey: [laugh].Corey: —and there's always value in broadening your perspective a bit on those things. If people want to learn more about you and how you see the world, where's the best place to find you?Casey: Probably on Twitter: twitter.com/nektos, N-E-K-T-O-S.Corey: That might be the first time Twitter has been described as a best place for anything. But—Casey: [laugh].Corey: Thank you once again, for your time. It is always appreciated.Casey: Thanks, Corey.Corey: Casey Lee, CTO at Gaggle and AWS Container Hero. And apparently writing code in anger to invalidate my points, which is always appreciated. Please do more of that, folks. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, or the YouTube comments, which is always a great place to go reading, whereas if you've hated this podcast, please leave a five-star review in the usual places and an angry comment telling me that I'm completely wrong, and then launching your own open-source tool to point out exactly what I've gotten wrong this time.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.