Podcasts about cdp

This week, host Mandi McReynolds is joined by Paul Dickinson, founder and chair of CDP, the not-for-profit organization that runs the global environmental disclosure system for investors, companies, cities, states, and regions. Paul and Mandi discuss announcements from COP27, the importance of data, and what lies ahead for ESG. Resources: 1) Federal Supplier Climate Risks and Resilience Proposed Rule - https://www.sustainability.gov/federalsustainabilityplan/fed-supplier-rule.html  2) CDP questionnaire to add ISSB's climate disclosure standard - https://www.corporatesecretary.com/articles/esg/33225/cdp-questionnaire-add-issb%E2%80%99s-climate-disclosure-standard  3) The Chat: Questions Emerge at COP27 - https://podcasts.apple.com/us/podcast/esg-talk/id1622905439?i=1000586406377  4) Shaping the Global Climate Transition for All ft. Simon Mundy - https://podcasts.apple.com/us/podcast/esg-talk/id1622905439?i=1000578677697

Highlights from this week's conversation include:Ashwin's background in the data space (2:43)The unique nature of working with data in finance (7:32)Technological challenges of working in the finance data space (13:55)The third-party data factor and judging if it is reliable enough (17:07)What made Ashwin decide to go out and build his own company? (31:47)Defining data decay and data storing and why both are important (37:52)Advice on the importance of data quality (42:10)Final takeaways and wrap-up (50:49)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com.

In this week's episode of Data Unlocked, Jason sits down with Darren Rankine, Partner of Marketing Technology at Transparent Partners.Darren started his career in marketing technology over two decades ago. He has worked with big brand names, including McDonalds, Accenture, and Plexure.For the last four years, he's been using his expertise to help Transparent Partners grow. Transparent Partners is a media and marketing technology consultancy dedicated to helping clients navigate the complex digital landscape. Their work is all about helping brands become familiar with the latest media and marketing technologies and implement these technologies for better returns.In this episode, Darren and Jason discuss the main complexities in martech, how to choose the right CDP for your business, the marketing challenges CDPs can solve, and more.Ready to learn?Let's dive in.Key Takeaways:Intro (00:00)Meet Darren (00:39)How to choose the right CDP (01:37)Marketing challenges solved with a CDP (05:54)A quick visual for you (09:15)First gen vs second gen (13:34)The importance of a good operating model (20:31)One final question (25:06)Additional Resources:Get in contact with Darren here.Learn more about Transparent Partners here.>>Learn more about us here.Follow us on LinkedIn, Twitter, and Instagram.If you enjoyed this episode, please follow, rate, and leave a review on your favorite podcast platform!

Our guest in this 31st interview episode with a unicorn start-up leader is the CEO of Tealium, Jeff Lunsford.  Tealium is a leading customer data platform (CDP), connecting you with your customers, through your data. For companies to better connect with their customers, Tealium combines customer data across web, mobile, offline, and IoT. With more than 1,300 built-in connections supported by Tealium's turnkey integration ecosystem, brands can build a complete and up-to-date consumer data framework.     The company was founded in 2008 by Mike Anderson and Ali Behnam, with Jeff Lunsford taking the position of CEO in 2013.  The company reached unicorn status in February 2021, with a valuation of $1.2 billion. Today, more than a thousand top companies around the globe rely on Tealium to power their consumer data strategy.  Tealium have reached unicorn status thanks to their focus and care for their customers- with a company culture that is “one of winning”, Jeff states that they “win together as a team, holding each other accountable for performance,” acknowledging that although every deal can't be won, you can still learn from these instances and keep improving. Thanks to this commitment to improvement, Tealium have built a culture of trust and an extensive portfolio of repeat customers.  Jeff Lunsford has more than two decades of experience as a technology and internet executive and leader. Jeff says “success in business is never a straight line. It is always ups and downs”, and highlights how important it is as leaders, to always have a “positive bounce” in your step. He also believes that the most important thing in business is not IPOs or unicorn statuses, but rather “building great solutions and taking great care of customers so they can deliver true business value.”   The interview, as usual, was co-hosted with Russell Goldsmith of the csuite podcast. Alongside Holly Justice, Senior Partner at Tyto PR .   We have distilled the most valuable, actionable insights from our first 15 interviews with leaders of unicorn companies and bottled them in our book ‘Growing without borders: The unicorn CEO guide to communication and culture'. You can download it here. 

Hello! In this episode of Just Making Conversation, not ones to pass up a free lunch, James and Malcolm discuss their visit to the plastic injection molding factory where the new scale model 1/24 Airfix Spitfire MkIXc is being made. Show Link: https://anchor.fm/justmakingconversation Show Notes: Airfix: https://uk.airfix.com/products/supermarine-spitfire-mkixc-a17001 Find other model podcasts on: http://modelpodcasts.com Support us: https://www.buymeacoffee.com/jmcpodcast "Happy Boy Theme" Kevin MacLeod (incompetech.com) Licensed under Creative Commons: By Attribution 4.0 License creativecommons.org/licenses/by/4.0/ This is an excerpt from the second track of the 1968 “Romeo & Juliet” original soundtrack recording album, composed and conducted by Nino Rota.The complete soundtrack album has been originally released as ST-2993 on October 7, 1968. (p) (c) 1989 Capitol Records, Inc. CDP 7 92057 2 Additional information regarding the musical work contained herein can be found at http://www.capitolrecords.com/ UMG (on behalf of Tooth & Nail (TNN)); Sony Music Publishing, SOCAN RR, and 10 music rights societies

Con el objetivo de ratificar su presencia en el país y mostrar sus nuevas divisiones y productos, Chicago Digital Power (CDP), líder mundial en el suministro de energía segura, almacenamiento y equipos de acondicionamiento, presenta soluciones innovadoras al mercado venezolano, especialmente su líneas UPS online y generación solar. La primera línea presentada por CDP fue UPS On line, una solución que suministra energía a la carga de corriente alterna (CA) a través de un puente rectificador y un inversor que surte energía de CA durante una falla energética. Por lo tanto, la fuente de alimentación de salida siempre permanece encendida y sin tiempo de transferencia. Este diseño ofrece el voltaje y la frecuencia más consistentes para cargar con una variación mínima, perfectos para todo tipo de usuario. Conversamos con orge Tovar, Country Manager de CDP Venezuela y Region del Caribe --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/it-news-latinoamerica/message Support this podcast: https://anchor.fm/it-news-latinoamerica/support

Jason Lambert, VP of Beyond Labs and BEES at AB InBev, thinks of a customer data platform (CDP) as a circulatory system: it powers the instantaneous flow of data to all business functions.  It's not the “perfect” metaphor, he says, but it does summarize the impact of a platform that's become a buzzword for marketers. Part of Jason's role at the largest and oldest brewing company in the world involves a few more buzzwords that we can definitely get behind — empowerment, transparency, and inclusivity within the B2B e-commerce space. With over 500 iconic brands and 10 million small-to-medium-sized businesses (SMB) in the AB InBev portfolio, Jason wants to solve pain points and elevate the experiences of these worldwide retail partners.Enter BEES: it's a B2B e-commerce and SaaS platform co-created by AB InBev and Ambev that is reinventing the digital ecosystem for retailers through highly personalized reward and loyalty programs, expanded portfolio visibility, flexible fulfillment, and more. As the platform matures, Jason creates space for even more tech innovation at BEES' incubator, Beyond Labs, and in his role as an adjunct professor of product management at the Columbia Business School.        Here, Billy and Jason discuss best-in-class, consumer-grade platforms, and processes in the massive yet oft-neglected B2B market. Our host and guest also explore the hyper-local yet global nuances of the beverage industry, and how to incorporate a modern tech stack and business development strategy into a 650-year-old commercial business. It's a deep dive into MarTech that will leave you feeling all the Budweiser. Hot topics discussed:Taking a problem-first approach to investing in CDPs, data analytics, and broader strategic digital transformationElevating online and offline B2B experiences through technology and process improvementsHow — and why — marketers must bring the best practices of B2C into the B2B spaceTraining and upskilling the next generation of great product leadersKeep the growth going:Read the episode transcriptionConnect with Jason Lambert, VP of Beyond Labs and BEES on LinkedInFollow Billie Loewen, WillowTree Partner & VP of Growth Marketing on LinkedInFollow Billy Fischer, WillowTree Partner & VP of Business Development on LinkedInFollow WillowTree on LinkedIn

Highlights from this week's conversation include:Max's career journey (2:54)Going from a small startup to a big enterprise (11:15)Dynamics of a switchboard operator (17:09)Common threads through different companies (20:53)When data is not the answer (26:57)The evolution of CDP (29:38)Data sources to include in a CDP (35:16)Working with event data (37:19)Max's take on other tools (41:18)The cutting edge in data (43:09)Building your data company in an evolving environment (49:28)Find Max: https://www.obsessiveanalytics.com/The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com..

Host Steffan Hostetter welcomes Sean Holman for a conversation exploring information, democracy and how his work with the Climate Disaster Project is helping climate disaster survivors to share their stories, creating community and change. Find the show's sprawling archives at http://www.greenmajority.ca/ Find out more about the CDP at https://climatedisasterproject.com/

Highlights from this week's conversation include:Ryan's background and career journey (2:49)Quine and where it came from (4:36)Graph databases 101 (7:17)Use cases for graph databases (13:44)Purposes for graphs (22:27)How to use Quine (31:49)Quine's performance and scale (43:06)Educating users about a new product (49:13)The team that would optimize Quine (52:23)When graph will gain popularity (56:15)Quine: https://quine.io/The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com.

GDPR is an opportunity for the companies to be transparent about what they are collecting and lettings consumers know what are their data be use for. If you play the long game, build trust with their consumers, customers will willingly give the needed information. Want to know more, take a listen to this latest conversation between Zack Wenthe and Punit Bhatia. KEY CONVERSATION POINTS 00:00:00 Intro 00:01:48 GDPR in one word is “Opportunity” 00:04:46 Play the long game, build trust with customers. 00:06:32 Managing trackers 00:11:27 Technical and cultural aspects of data collection 00:15:56 Corporate governance vs Culture & ethics 00:20:36 Future-proof data governance strategy 00:29:45 Thank you ABOUT THE GUEST Zack Wenthe is the Customer Data Platform Evangelist for Treasure Data. He often speaks about the marketing and customer data industry at industry events, webinars, and virtual conferences. Having spent a majority of his career in marketing and marketing consulting working with large enterprise brands like Walmart, Nationwide Insurance, FedEx, and many more, Zack now gets to tell the CDP story to help marketing teams eliminate the friction caused by silos, inefficiencies, and lack of understanding of their true customers. Zack lives with his amazing wife and two kids and one more who is away at college. Though they currently live in Texas they are moving to the bluffs of the Mississippi River to be closer to family. Fun fact: Zack met Daniel Radcliffe, Teresa Palmer, and a few other prominent actors at a mov ie premiere hosted by the Australian Film Festival. Outside of work, Zack enjoys cooking, spending time with his kids, writing comedy, and maybe someday a screenplay. ABOUT THE HOST Punit Bhatia is one of the leading privacy experts who works independently and has worked with professionals in over 30 countries. Punit works with business and privacy leaders to create an organization culture with high privacy awareness and compliance as a business priority. Selectively, Punit is open to mentor and coach privacy professionals. Punit is the author of books “Be Ready for GDPR” which was rated as the best GDPR Book, “AI & Privacy – How To Find Balance”, “Intro To GDPR”, and “Be an Effective DPO”. Punit is a global speaker who has spoken at over 30 global events. Punit is the creator and host of the FIT4PRIVACY Podcast. This podcast has been featured amongst top GDPR and privacy podcasts. As a person, Punit is an avid thinker and believes in thinking, believing, and acting in line with one's value to have joy in life. He has developed the philosophy named ‘ABC for joy of life' which passionately shares. Punit is based out of Belgium, the heart of Europe. RESOURCES Podcast https://www.fit4privacy.com/podcast Blog https://www.fit4privacy.com/blog YouTube http://youtube.com/fit4privacy --- Send in a voice message: https://anchor.fm/fit4privacy/message

The UN climate conference known as COP27 is underway, and today (Nov. 11) is Decarbonization Day. In this episode of the ESG Insider podcast, we explore how companies are setting decarbonization targets in their operations and across their supply chains.     To understand how companies are engaging with suppliers, we talk with Simon Fischweicher, who is Head of Corporations and Supply Chains for CDP North America. CDP is a nonprofit environmental disclosure platform that has a program aimed at helping companies gather concrete details from suppliers about their emissions and other climate-related activities.  Simon tells us that companies are increasingly collaborating on their approach to suppliers. "When you have a single customer voice asking for better climate disclosure or more investment in renewable energy or setting emission reduction targets for a specific supplier, that voice might not be loud enough to drive change," he says. But when the entire sector is pushing for better practices, "that supplier may listen." Listen to our episode about what to expect from COP27 here: https://www.spglobal.com/esg/podcasts/at-cop27-how-to-make-progress-in-the-face-of-uncertainty   Listen to our episode about a proposed U.S. climate disclosure rule here: https://www.spglobal.com/esg/podcasts/unpacking-the-sec-s-proposed-esg-fund-rules   We'd love to hear from you. To give us feedback on this episode or share ideas for future episodes, please contact hosts Lindsey Hall (lindsey.hall@spglobal.com) and Esther Whieldon (esther.whieldon@spglobal.com).   Copyright © 2022 by S&P Global   DISCLAIMER   By accessing this Podcast, I acknowledge that S&P GLOBAL makes no warranty, guarantee, or representation as to the accuracy or sufficiency of the information featured in this Podcast. The information, opinions, and recommendations presented in this Podcast are for general information only and any reliance on the information provided in this Podcast is done at your own risk. This Podcast should not be considered professional advice. Unless specifically stated otherwise, S&P GLOBAL does not endorse, approve, recommend, or certify any information, product, process, service, or organization presented or mentioned in this Podcast, and information from this Podcast should not be referenced in any way to imply such approval or endorsement. The third party materials or content of any third party site referenced in this Podcast do not necessarily reflect the opinions, standards or policies of S&P GLOBAL. S&P GLOBAL assumes no responsibility or liability for the accuracy or completeness of the content contained in third party materials or on third party sites referenced in this Podcast or the compliance with applicable laws of such materials and/or links referenced herein. Moreover, S&P GLOBAL makes no warranty that this Podcast, or the server that makes it available, is free of viruses, worms, or other elements or codes that manifest contaminating or destructive properties.   S&P GLOBAL EXPRESSLY DISCLAIMS ANY AND ALL LIABILITY OR RESPONSIBILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF ANY INDIVIDUAL'S USE OF, REFERENCE TO, RELIANCE ON, OR INABILITY TO USE, THIS PODCAST OR THE INFORMATION PRESENTED IN THIS PODCAST. 

Are you struggling to find a way to connect with your customers? Do you have all of your data scattered across different platforms and software? If your answer is YES, you'll get a lot of value from this conversation. In today's episode of the Growth Marketers Podcast, we have Zach Wenthe with us as our guest. Zach is a CDP evangelist for Treasure Data, a customer data platform helping enterprises overcome the data disconnect. We discuss what a customer data platform is and how it can be used to improve customer experience. We also dive into the meaning of "data" and "data points," and some great examples of how businesses are using data to connect with their customers. This podcast is a great starting point if you're looking for ways to improve customer experience using data. Learn more about Treasure Data at https://www.treasuredata.com/

Highlights from this week's conversation include:Zander's background and career journey (2:32)Introducing bytewax (5:16)The difference between systems (10:57)Bytewax's most common use cases (16:15)How bytewax integrates with other systems (20:25)The technology that makes up bytewax (24:31)Comparing bytewax to other systems (34:17)What's next for bytewax (36:31)Try it out: bytewax.ioThe Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com.

Was ein Spieltag mit nicht einem, nicht zwei, sondern gleich drei absoluten Topspielen! Der Tabellenzweite aus Bergamo empfing den amtierenden Spitzenreiter vom Golf aus Neapel, die ewige Stadt suchte im Derby della Capitale einen neuen Caesar und Juventus bekam es mit Simone Inzaghis Inter Mailand zu tun! Ein gefundenes Fressen für David und Max, die untereinander ein kleines Derby austrugen! Wer in der Folge zuletzt lachen darf, erfahrt ihr in der neuen Episode von CDP! Die Sechzehntel- und Achtelfinalgegner unserer italienischen Vertreter in Europa stehen fest! Wie wir diese einschätzen und welche Überraschungen es geben könnte, besprechen Max und David für Euch! Also ...Du möchtest deinen Podcast auch kostenlos hosten und damit Geld verdienen? Dann schaue auf www.kostenlos-hosten.de und informiere dich. Dort erhältst du alle Informationen zu unseren kostenlosen Podcast-Hosting-Angeboten.

È morto a 78 anni Giuseppe Bono, ex amministratore delegato di Fincantieri e figura storica dell industria italiana. Pochi mesi fa era stato sostituito al vertice del gruppo con sede a Trieste da Pierroberto Folgiero. Il manager che ha saputo mettere d'accordo governi e maggioranze di tutti i tipi, difeso persino dai sindacati tre anni fa, quando i 5 stelle al governo provarono a depotenziarlo con l'idea di affidare alcune deleghe al candidato presidente. A non riconfermarlo è stato il governo Draghi, che ha interrotto il suo controllo assoluto di Fincantieri. Lo chiamavano l ultimo boiardo di Stato, e lui faceva finta di indignarsi: Boiardo a me? Ma per favore... Io nell industria ci sono nato, le mani me le sono sporcate davvero. Mica come quelli che non sono mai usciti dal salotto e un cantiere lo hanno visto solo al telegiornale. Calabrese di Pizzoni, classe 1944, In fabbrica sono entrato quando avevo 18 anni raccontava di sé - Da operaio, a Torino, a 1.300 chilometri da casa. Non avevo molta scelta: papà morì quando ero piccolo, e al nostro paese lavoro non ce n'era. Ne parliamo con Paolo Bricco de Il Sole 24 Ore. Superbonus: Ance, speculazione pazzesca, partecipate sblocchino "E' in corso una speculazione pazzesca. Stiamo chiedendo da tempo lo sblocco di Cdp e Poste e di tutte le partecipate pubbliche, per dare un segnale di fiducia e per rimettere in moto il mercato". Così la presidente dell'Ance, Federica Brancaccio, commentando la sospensione da parte di Poste dell'acquisto dei crediti del Superbonus. Brancaccio denuncia come chi ancora acquista lo stia facendo a percentuali bassissime, sfruttando la "disperazione delle imprese": se prima il credito al 110% veniva acquistato in media al 102%, ora si arriva anche all'85%. "Chi compra specula. Serve un segnale, senza si fanno saltare migliaia di imprese". La circolare dell'Agenzia delle Entrate che ha "ammorbidito le norme, purtroppo ha sbloccato ben poco", sottolinea la presidente, secondo cui Poste sarebbe ferma praticamente da un anno nell'acquisto dalle imprese ed ora avrebbe chiuso i rubinetti anche nei confronti dei privati che hanno crediti di minore entità, tra i 100.000 e i 150.000 euro. "Le banche affermano di aver esaurito la capacità fiscale, ma Poste, Cdp e le altre partecipate non hanno questo problema - spiega Brancaccio - la capacità loro la hanno, ma non comprano. E' un problema grave. Ci dicano se vogliono distruggere la misura". Approfondiamo il tema proprio con Federica Brancaccio, presidente dell'Ance. Dal riciclo un miliardo e mezzo di euro di benefici ambientali Si è aperto nei giorni scorsi a Sharm el-Sheikh, in Egitto, il summit Cop27 sul Clima che vede la partecipazione di circa 200 delegati provenienti da circa 200 Paesi. A Rimini invece si sta tenendo la 25a edizione di Ecomondo e la 15a di Key Energy, da oggi (8 novembre) a venerdì (11 novembre) prossimo le due manifestazioni di Italian Exhibition Group segneranno lo stato dell'arte sia dal punto di vista dell'innovazione tecnologica ed economica, sia sul fronte convegnistico, con i tanti incontri scientifici della transizione ecologica ed energetica per l'Europa e il bacino del Mediterraneo. Nel frattempo secondo il rapporto presentato ieri da Conai - consorzio nazionale degli imballaggi- nel 2021 in Italia il riciclo e il recupero degli imballaggi ha generato un miliardo e 525 milioni di euro di benefici ambientali". Ne parliamo con Luca Ruini, Presidente Conai.

In this podcast, Doug Green and Infobip's Ted Franz discuss omnichannel, conversational commence, and how the overall customer experience is evolving. How can companies engage with customers beyond phone calls, email, and their websites? Many SMBs and middle market companies are still new to messaging or are only sending basic one-way alerts. Others have siloed data that limits their ability to deliver a coherent customer journey. Brands are now beginning to understand that true two-way conversational messaging across popular social media channels and chatapps like WhatsApp are desired, the same tools used by many to connect with friends and family. “You need to meet the customer where they are today, and service them either on the revenue side or the service support side on the preferred channel that they like to use. We see a big shift in brands now recognizing this,” says Ted Franz, Director of Product Strategy at Infobip. Within companies there is also a heightened focus on providing contact center agents with more sophisticated tools to help them better support customers. If the agent has incomplete visibility and context in a customer interaction, we have the beginnings of a poor customer experience where agents lack the information needed to meet the customer where they are with an issue and then to resolve the issue. “Enterprises are starting to deploy customer data platforms or CDP,” Franz adds. Infobip offers this type of platform, and we learn how a CDP helps an organization segment their audience and deliver hyper-personalized, relevant content at the right time and on the customers' preferred channel. One more particularly exciting aspect of our conversation is learning about the accessibility of these solutions for smaller and middle-sized firms. Hyper-personalizing the customer experience is now vital to maintaining customer brand expectations, curbing costly customer defections, and creating deeper connections with customers. To learn more, visit www.infobip.com.

Meta prepara la prima ondata di tagli della sua storia: migliaia di licenziamenti in settimana. Secondo il Wall Street Journal la holding di Facebook vuole ridurre i costi del 10%: a pesare sono la crisi economica e le ricadute dell' investimento sul metaveso. Mark Zuckerberg tiene la barra dritta sulla sua strategia focalizzata sul metaverso. Ma la scommessa sulla realtà virtuale potrebbe tramutarsi a breve in un ondata di tagli occupazionali, la prima nei diciotto anni di storia di quella che oggi si chiama Meta. I tagli, secondo il WSJ saranno annunciati mercoledì 9 novembre. Si tratterebbe della prima operazione del genere nella storia della compagnia e, sebbene in proporzione di dimensione inferiori al maxi licenziamento avvenuto all interno di Twitter (7.500), potrebbe essere il numero più alto di persone cacciata da una Big Tech in un anno che ha visto una contrazione del settore. Ne parliamo con Alessandro Plateroti, direttore di Notizie.it.Tim corre a Piazza Affari in attesa dell'incontro governo-azionisti Piazza Affari svetta Telecom Italia con un +9,64% (alle 16.15), sull ipotesi che Cassa Depositi e Prestiti lancerà un opa sulla compagnia, come previsto dal piano Minerva ideato nei mesi scorsi dal sottosegretario alla presidenza del consiglio Alessio Butti. Il senatore di Fratelli d Italia con deleghe all'innovazione digitale ha preannunciato un imminente incontro con gli stakeholder dell azienda. Il suo piano prevederebbe un offerta lanciata da Cdp su Tim e la successiva dismissione degli asset brasiliani e delle attività retail. Fonti vicine al gruppo francese hanno detto ieri all'Ansa come «confermiamo la volontà dell'azionista di sedersi a un tavolo di confronto». In attesa di capire cosa uscirà dai colloqui fra l'esecutivo, Cdp e Vivendi, la scadenza formale per il momento è quella del 30 novembre quando scadrà la proroga concessa da Tim a Cassa (senza l'esclusiva) sull'offerta non vincolante per l'acquisto della sua infrastruttura di rete. Proroga che ha superato il memorandum of understanding di fine maggio tra la stessa Tim, Cdp e Open Fiber. Approfondiamo il tema con Andrea Biondi, Il Sole 24 Ore.

Lunedì 31 ottobre scorso è arrivata la comunicazione ufficiale del Mef sulla cessazione dell'esclusiva concessa a Certares, Air France-Klm e Delta per la cessione del controllo di Ita. Potrebbe quindi tornare in scena la cordata tra Msc-Lufthansa che aveva partecipato alla gara la scorsa estate, e Indigo Partners che aveva manifestato interesse lo scorso marzo. Intanto c'è attesa per l'8 novembre, giorno per il quale è in calendario l'assemblea dei soci di Ita che darà il via libera all'aumento di capitale da 400 milioni. Si tratta della seconda tranche del finanziamento complessivo da 1,35 miliardi di euro già autorizzato dall'Ue e suddiviso in tre tranche: 700 milioni per il 2021, 400 per il 2022 e 250 per il 2023. Nell'odg di quel giorno è previsto anche la revoca dell'incarico di presidente ad Alfredo Altavilla. Infine da indiscrezioni nell'assemblea del prossimo 8 novembre all'ordine del giorno ci sarebbe il cambiamento dello statuto della compagnia per la revisione del numero minimo di consiglieri, che da sette passerebbero a cinque per iniziare ad allineare il cda verso la privatizzazione. Ne parliamo con Giorgio Pogliotti de il Sole 24 Ore. Indice Cosulich. Furto del carico per la nave bloccata a Mariupol. Questa mattina sono salpate sette navi cariche di prodotti agricoli dai porti dell'Ucraina nell'ambito dell'accordo sul grano firmato lo scorso 22 luglio a Istanbul. È la conseguenza del ritorno della Russia nell'accordo di quest'estate dopo una sospensione di quattro giorni. Le navi sono state caricate con 290mila tonnellate di prodotti alimentari e sono dirette verso paesi europei e asiatici. Rimane però bloccata la nave del nostro Augusto Cosulich che negli scorsi giorni ha addirittura subito un furto al proprio cargo di 14mila tonnellate di bramme. Nel frattempo un pool di istituti composto da Crédit Agricole Italia, nel ruolo di Arranger, Lender e Banca Agente, e UniCredit, Cdp, Banco Bpm nei ruoli di Arranger e Lender, ha erogato un finanziamento di 29,5 milioni di euro, assistito dalla Garanzia Sace, a Fratelli Cosulich per la costruzione di una nave gasiera. Approfondiamo il tema con Augusto Cosulich, l'agente marittimo genovese, presidente e amministratore delegato della "Fratelli Cosulich". BoE: tassi a top da 2008, attesa recessione "per periodo prolungato" La Bank of England prevede "un outlook molto problematico per l'economia britannica, con una recessione per un periodo prolungato e l'inflazione a livelli elevati sopra il 10% nel breve termine". Questo anche a causa della contrazione dei redditi reali a causa dell'aumento dei costi dell'energia globale, cosa che ha un impatto negativo sui consumi e sulla spesa delle famiglie. La Banca centrale britannica ha alzato i tassi di interesse di 75 punti base, il rialzo maggiore dal 1989, portandoli dal 2,25% al 3%, il livello più alto da novembre 2008. In particolare, come si legge nel documento diffuso al termine della riunione della Monetary Policy Committee (Mpc), il Pil del Regno Unito e' atteso in calo nel 2023 (-1,9% a fine anno) e nel primo semestre 2024, per chiudere l'anno a -0,1% e risalire a +0,7% a fine 2025. La Boe prevede una fase "problematica" protratta, evocando la recessione più lunga della storia recente del Paese fin dagli anni '20 - ossia da quando si registrano i dati sul Pil - sebbene non la più pesante in termini di percentuali. Giorgia Scaturro de Il Sole 24 Ore.

Do you know an eCommerce platform that is designed for enterprise-grade websites? Do you know an eCommerce platform that is primarily designed for B2C experiences with the ability to build composable experiences? Do you know an eCommerce platform that is? Net-based? Do you know an eCommerce platform that can accommodate up to five rules to provide personalized experiences through deterministic identity? Do you know an eCommerce platform that has support for GraphQL? If you guessed Sitecore, then you are right.In today's episode, we invited a panel of industry experts for a live discussion on LinkedIn to conduct an independent review of Sitecore's capabilities. We covered many grounds including its unique position in the market with B2C companies and its strength in all layers of commerce, from content to experience management, to commerce. Finally, we discussed how the layers of deterministic identity work with CDP platforms, and why that is important for the personalized experience in the B2C market.For more information on growth strategies for SMBs using ERP and digital transformation, visit our community at wbs.rocks or elevatiq.com. To ensure that you never miss an episode of the WBS podcast, subscribe on your favorite podcasting platform.

Ever get the feeling that Instagram is listening to you? It might be — or it might not. In the words of one of our favorite Facebook relationship statuses, it's complicated. Here, our experts explore how customer data platforms (CDPs) can take out the “ick” factor for brands in search of more personalized, automated customer experiences.Guided by the use cases proposed in the MarTech article “19 CDP Use Cases That Can Annoy or Engage Your Audiences,” Billie and Billy break down when marketing and re-marketing tactics are creepy vs. cool, and when they're annoying vs. appreciated. We'll explore how to take the pushy out of push notifications, the differences between CDPs and CRMs and CEPs, and examples of when location tracking works like gangbusters — or when it breaks up the party. Let's not make it weird, k?Hot topics:The power of content to change intentHow investing in a CDP is like building a houseWhich brand Billy recently bought a shirt from — and is now already on his way toward VIP statusWhat kind of push will send you to Burger King instead of McDonald's What kind of push will not send you to the movies instead of driving on the freewayKeep the growth going:Read the episode transcriptionFollow Billie Loewen, WillowTree Partner & VP of Growth Marketing on LinkedInFollow Billy Fischer, WillowTree Partner & VP of Business Development on LinkedInFollow WillowTree on LinkedIn

In the third episode of Road to COP27, a special series as part of India Speak: The CPR Podcast, Navroz K. Dubash speaks to Rachel Kyte, Dean of The Fletcher School at Tufts University on the geopolitical context for COP27 and its implications. This series will bring leading experts in the lead up to Conference of the Parties (COP) 27, being held from 6-18 November 2022 at Sharm el-Sheikh, Egypt. They discuss the Inflation Reduction Act, the new climate legislation passed by the United States, and what it could mean for climate diplomacy. The episode also explores questions on climate finance, whether there is a landing zone for negotiations on loss and damage and what that looks like, and delves into questions around carbon markets. About the speakers: Rachel Kyte is the 14th dean of The Fletcher School at Tufts University. Kyte is the first woman to lead the United States' oldest graduate-only school of international affairs, which attracts students from all corners of the world and at all stages of their careers. Prior to joining Fletcher, Kyte served as special representative of the UN secretary-general and chief executive officer of Sustainable Energy for All (SEforALL). She previously was the World Bank Group vice president and special envoy for climate change, leading the run-up to the Paris Agreement. She was also vice president at the International Finance Corporation responsible for ESG risk and business advisory services. In her UN role and as CEO of SEforAll, a public-private platform created by the UN and World Bank, Kyte led efforts to promote and finance clean, reliable and affordable energy as part of the UN Sustainable Development Goals. She served as co-chair of UN Energy. In the 2020 UK New Year Honours, Rachel was appointed as CMG for her services to sustainable energy and combating climate change. Kyte is a member of the UN secretary-general's high-level advisory group on climate action and an advisor to the UK presidency of the UN climate talks. Kyte is co-chair of the Voluntary Carbon Markets Integrity Initiative (VCMI), and chair of the FONERWA, the Rwanda Green Fund. She serves on the boards of the Private Infrastructure Development Group (PIDG), the Climate Policy Institute and CDP. She advises investors, governments, and not-for-profits on climate, energy, and finance for sustainable development. Navroz K Dubash is a Professor at the Centre for Policy Research, a New Delhi based think-tank and an Adjunct Senior Research Fellow at the Lee Kuan Yew School of Public Policy, NUS. He has been actively engaged in debates on climate change, air quality, energy and water as a researcher, policy advisor and activist for over 25 years. Navroz has been a Coordinating Lead Author for the Sixth Assessment Report of the Intergovernmental Panel on Climate Change and has advised Indian government policy-making on climate change, energy, and air and water policy over the last decade. In the early 1990s, he helped establish the global Climate Action Network as its first international coordinator.

Highlights from this week's conversation include:Erik's background and career journey (2:51)Managing scale in a rapidly changing environment (6:35)The people side of hypergrowth (12:36)Coding competitions (17:50)Introducing Modal Labs (19:02)How Erik got into building Modal (21:45)The employee experience at Modal (28:09)How a data engineering team would use Modal (31:21)What it takes to build a platform like Modal (36:27)What makes Modal different (42:49)Evolution coming for the data world (45:52)Untapped areas in the data world (48:46)Spotify playlists (52:03)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com..

Join me and Nicolle Lamb from Outsell as we discuss the rise of Customer Data Platforms (CDPs) in the automotive industry. Outsell has been developing their CDP for over 4 years and has some impressive clients including Germain Automotive Group and Southeast Toyota Distributors (SET). Learn more about their Customer Data Engagement Platform which gives dealers the ability update each customer record based on engagement activities online and in the store. 

Have you ever thought, “I want to implement EBP's effectively with my clients, but I'm running into barriers!”. Well, help is here! Listen in as we sit down with Dr. Lisa Cuccurullo, whose job it is to help solve the problems people face every day in their clinical practice. We dig into some clinical barriers, what mechanisms need to be in place administratively to do these treatments with fidelity, and how to do these treatments in the real world with all of the chaos of day-to-day life. We all need that “clinical family” to support our work, so join us to find out about resources to expand yours! Come hear about common challenges, potential solutions, and Dr. Cuccurullo's uplifting consultation story! Lisa-Ann Cuccurullo, Ph.D., is a clinical psychologist at the National Center for PTSD, where she works on a team that facilitates the use of empirically supported treatments for veterans in rural areas. Her clinical work has focused on cognitive behavioral treatments for PTSD (and other post-trauma-related symptoms), such as Prolonged Exposure, Cognitive Processing Therapy, Acceptance and Commitment Therapy, and Dialectical Behavior Therapy. She is a national Prolonged Exposure consultant in VA. Before joining the staff of the National Center for PTSD, she was the Military Sexual Trauma Coordinator and Assistant Director of Psychology Clinical Training at the Southeast Louisiana Veteran's Health Care System and a clinical instructor at Tulane University School of Medicine. Dr. Cuccurullo's current research interests focus on the implementation of empirically supported treatments and posttraumatic symptom presentation. Dr. Cuccurullo received her doctorate in clinical psychology from La Salle University and completed her clinical internship and a PTSD-focused fellowship at the Southeast Louisiana Veteran's Health Care System.Resources mentioned in this episode: VA's Consultation Service: https://www.ptsd.va.gov/professional/consult/index.asp CDP's Consultation Service: https://deploymentpsych.org/resources/consultation-servicesNCPTSD Patient Education tools: https://www.ptsd.va.gov/publications/print/index.aspGet EBP training from CDP: https://deploymentpsych.org/training Calls-to-action: Subscribe to the Practical for Your Practice PodcastSubscribe to The Center for Deployment Psychology Monthly Email Take one of CDP's EBP's (PE, CPT, CBT-SP, CBTi, ACT and more!): https://deploymentpsych.org/training

Suzanne is joined by Ignacio Lopez III, CDP, dementia resident expert at MorningStar Senior Living's new community, MorningStar at West Valley in San José, California. They have a dedicated art studio, fitness studio, living areas, two dining rooms, and a sky terrace. The Lavender Sky approach is to serve them, enter their world and embrace them where they are. The community is set up for person-centric care.  They are scheduled to open in January and taking reservations, with Founder's Club members having many perks. Learn more at https://www.morningstarseniorliving.com/communities/memory-care-san-jose-west-valley/. Their information center is located at 3920 Williams Rd, Suite B in San José.

In this episode of the Futurum Tech Webcast, I'm joined by Matt Nolan, Senior Director of Product Marketing, Decision Sciences, to talk about one of my favorite topics: data, analytics, and how you can use them to provide customers with top notch experiences. We also explore Pega's latest product release: Pega Customer Data Connectors — which I see as a definite gamechanger for organizations in every industry. For consumers, whether B2B or B2C, experiences can be the difference between a closed sale and a lost revenue opportunity, and sometimes even the difference between a loyal customer who touts a brand to friends and family and one who spreads a negative word because of a less than stellar customer experience. In a word, customer experiences are everything. This is not new news for many organizations, which is why customer data platforms (CDPs) are quickly becoming a ‘must have' part of the MarTech stack. They help organizations manage massive amounts of customer data from a number of different channels, with the goal of providing insights to deliver better customer experiences. But CDPs alone aren't a holy grail and unfortunately in many instances they can be siloed and/or data can go unused. So, what do businesses need to know or what other technologies do they need to adopt to avoid common CDP pitfalls and serve up experiences that will be a key differentiator in today's marketplace. That's exactly what Matt and I talked about. Here are just a few of the things we covered: The current state of marketing and why first party data is king Why CDPs are that are connected and accessible throughout the organization are so immensely important for today's organizations The common challenges organizations face with their CDPs How organizations can maximize their data to make customer interactions more meaningful We wrapped up the conversation by exploring Pega's newest release, Pega Customer Data Connectors. This new solution is an exciting one, as it integrates data and decision-making in near real time. Organizations can tap into their data to provide just what the customer needs exactly when they need it — which is a fundamental element of delivering unparalleled customer experiences. And if you'd like more information on Pega and the Pega Customer Data Connectors, you'll find it here.  

Highlights from this week's conversation include:Shinji's background and career journey (3:35)Defining “data discovery” (6:03)The best conditions to use Select Star (8:45)Where Select Star fits on the data spectrum (13:38)Why Select Star is needed (17:35)How Select Star uses metadata (21:02)Exposing data queries (27:04)Composing queries into metadata (33:27)Automating BI tools (37:28)Limits to data governance (41:39)Maintaining economies of scale (48:56)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com.

Discover how the right CDP can deliver exceptional customer experiences now—and in the future. This offer covers: What a CDP is and why you need one How CDPs create great customer experiences What capabilities are essential in a future-proof CDP Key stats: 58% of marketers said the leading obstacle to marketing success was getting a single view of the customer. - MarTech Today 76% of customers prefer to use different channels to communicate with brands, but they still expect connected experiences. - MarTech Today You can read this content here: https://business.adobe.com/resources/sdk/anatomy-of-a-future-proof-cdp.html

Highlights from this week's conversation include:The context of Headless BI (3:31)What Cube Dev does (9:24)How Headless BI works with other tools (13:03)An analysis of LookML (18:04)User interaction with Cube Dev (23:40)Who manages data artifacts (25:22)Taking care of the developer experience (30:37)Levels of performance (30:37)Artyom and Pavel's background and career journey (35:47)Why you should use Cube Dev (43:38)Roles within a data organization (48:55)How Cube Dev impacts visualization (53:35)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com..

לדף הפודקאסט בבלוג במגזר העסקים הקטנים והבינוניים בחירה של מערכת דיוור או אוטומציה שיווקית נעשית לרוב כתהליך קצר וחפוז. טעות בבחירה בעסק קטן קל לתקן. אבל טעות בבחירה של מערכת דיוור ואוט' באנטרפרייז היא קטסטרופלית. אם אתם סקרנים לדעת כיצד ארגוני אנטרפרייז בוחרים מערכות דיוור (ESP) ואוטומציה שיווקית (Marketing Automation), הנה קטע וידאו קצר מראיון שבפודקאסט, עם Chris Marriott מנכ"ל Email Connect המלווה חברות ענק בארצות הברית בתהליכי RFP כבדים על מנת שחברות אלה יוכלו לקבל את ההחלטה הנכונה עבורם מבין שחקניות המרקטינג אוטומיישן והאימייל מרקטינג הגדולות. בפודקאסט כריס משתף מנסיונו הרב ונותן גם טיפים לבחירת מערכת דיוור או אוטומציה שיווקית שיכולים להתאים לעסקים קטנים ובינוניים.See omnystudio.com/listener for privacy information.

MakerDAO is the godfather of the stablecoin application, with the introduction of DAI to the blockchain space. Now they're aggressively expanding to address a multichain economy. DAI is a Collateralized Debt Position (CDP) based stablecoin that has recently been bridged over to the Cosmos ecosystem via the Osmosis DEX. Axelar has announced a retroactive airdrop to OSMO-DAI LPs who've bridged over net new DAI through the Axelar bridge within an (as yet) unspecified window of time.

Have you ever wondered what's missing? Then you think you find it and then you're on the hunt again. Chasing elusive things. What if you got your joy back?In this enlightening conversation with Rosemary Noe, Life Coach for women, mother of 5 and grandmother of 2 we chat about all the things. The things we wished we did when our kids were younger, the things we changed to live intentionally. There needs to be more joy in life. More conversations like this one. Please enjoy (pun intended) this ep. How to live your life intentionally Finding a calmer way to be and embodying it Reclaiming incidental joy  Bringing joy back into your life so it's easy Why gratitude practices are phenomenal How to be more like bamboo than a rigid tree with your life   “Self-care isn't a luxury, it's a necessity. “   Rosemary Noe is a life coach for women, a Mom of 5, Grandma of 2 and a CPA. Rosemary is passionate about supporting women who are Moms reclaim joy in their life and make space on their busy to-do list for things that light them up.  She is on a mission to create a world where women feel empowered to put themselves first and create the joyful life of their dreams.   She's a graduate of Coaching, Evolved, a multi-modality ICF credentialed program and is certified in the Conscious Consultant Certifcation ® method, a CDP certified program.  Additionally, she's certified in EFT and Breathwork for Coaches as well as the Conscious Energy Clearing Method™.   Follow Rosemary:   Website: https://rosemarynoe.com/  Facebook: https://www.facebook.com/iamrosemarynoe  Instagram: @iamrosemarynoe   Bounce Out of Bed hosted by Amanda Ewin, Lifestyle Coach.   Follow Amanda: Website: amandaewin.com Instagram: @amandaewin

Highlights from this week's conversation include:Gleb's background and career journey (2:51)The adoption problems (10:53)How Datafold solves these problems (18:08)The vision for Datafold (26:27)Incorporating Datafold as a data engineer (38:53)The importance of the data engineer (42:12)Something to keep in mind when designing data tools (46:46)Implementing new technology into your company (53:18) The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com..

Join me and Atul Patel from Orbee to discuss one of the hottest trends in automotive marketing: Customer Data Platforms. Dealers who have a CDP can lower operating costs by significantly reducing financial investments for customer retention and acquisition (i.e., marketing). CDPs are common outside the automotive industry but their use in our industry has been limited by the lack of robust API access to the dealer's CRM and DMS platforms.  Dealers who want to dive deeper into building their own CDP should attend the Modern Retailing Conference (MRC) in November.

If you're the type to wonder if that creaking sound is a restless soul, best to skip this episode. For all you horror fans, welcome! Author Thomas Smith joins me to talk about his book, “Something Stirs,” out on Oct. 13 through our friends at Cemetery Dance Publications. Here's a look at what lies within these pages:   Ben Chalmers is a successful novelist. His wife, Rachel, is a fledgling artist with a promising career, and their daughter Stacy is the joy of their life. His novels have made enough money for him to provide a dream home for his family. But there is a force at work in their lives. A dark, chilling, ruthless force that has become part of the very fabric of their new home.   A malevolent entity becomes trapped in the wood and stone of the house and it will do whatever it takes, to find a way to complete its bloody transference to our world.   Local Sheriff Elizabeth Cantrell, and former pastor-turned-cabinetmaker Jim Perry are drawn into the family's life as the entity manipulates the house with devastating results. And it won't stop until it gets what it wants. Even if it costs them their faith, their sanity, and their lives.   This is actually a re-release, since the book was originally published in 2011 through a different company. Thomas and I talk about what readers can expect in this updated version, as well as how he came work with the fine folks at CDP.   We dive deep into the story behind the book and how Thomas created the menacing presence within the Chalmers' home. This is a Christian horror novel, and if that's a new term for you, you're not alone. We look into what that genre is all about and what can—and cannot—be done in this kind of book.  

Highlights from this week's conversation include:Introducing our guests (3:05)Defining “data team” (4:40)How data teams emerge and evolve (14:11)The need that forces the creation of a data team (21:12)The backbone of the data team (26:23)Building a career within a data team (36:39)Advice for new data team managers (47:35)Question and answer time (52:38)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com..

In this week's episode of Data Unlocked, Jason sits down for a second time with Michael Katz, the co-founder and CEO of mParticle.Before founding mParticle, Michael was the CEO of interclick, a data-driven advertising network, before selling it to Yahoo for $270 million.Today, he's at the head of mParticle.mParticle is a customer data platform for multi-channel consumer brands. Their work helps the world's best brands unify data across all consumer touch points in order to optimize marketing outcomes and CX. In this episode, Michael discusses the future of CDP, the technology and market changes that are affecting today's CDP landscape, the driving forces shaping the CDP category, and more.Ready to learn?Let's dive in.Key Takeaways:Intro (00:00)Market changes affecting the CDP space (01:04)CDP trends (13:49)Why you need good access to data (21:48)Where to learn about mParticle (33:54)Additional Resources:Get in contact with Michael here.Learn more about mParticle here.Listen to Michael's first discussion on Data Unlocked here.>>Learn more about us here.Follow us on LinkedIn, Twitter, and Instagram.If you enjoyed this episode, please follow, rate, and leave a review on your favorite podcast platform!

The boys recap the Falcons first victory of 2022 by breaking down sterling efforts by A.J. Terrell, CDP and Grady. They also look ahead to the matchup against the Browns and how critical it is to stop Nick Chubb in order for the Falcons to win. They then turn their attention to the Braves who face the Mets in the final battle for NL East supremacy, breakdown the Spencer Strider injury, and lavish much deserved praise upon Kyle Wright. Draftkings Disclaimer If you or someone you know has a gambling problem, crisis counseling and referral services can be accessed by calling 1-800- GAMBLER (1-800-426-2537) (IL/IN/LA/MI/NJ/PA/WV/WY), 1-800-NEXT STEP (AZ), 1-800-522-4700 (CO/NH), 888-789-7777/visit http://ccpg.org/chat (CT), 1-800-BETS OFF (IA), 877-8-HOPENY/text HOPENY (467369) (NY), visit OPGR.org (OR), call/text TN REDLINE 1- 800-889-9789 (TN), or 1-888-532-3500 (VA). 21+ (18+ NH/WY). Physically present in AZ/CO/CT/IL/IN/IA/LA(select parishes)/MI/NH/NJ/ NY/OR/PA/TN/VA/WV/WY only. New customer offer void in NH/OR/ONT-CA. $200 in Free bets: New customers only. Valid 1 per new customer. Min. $5 deposit. Min $5 wager. $200 issued as eight (8) $25 free bets. Ends 9/19/22 @ 8pm. Early Win: 1 Early Win Token issued per eligible game. Opt in req. Token expires at start of eligible game. Min moneyline bet $1. Wagering limits apply. Wagers placed on both sides of moneyline will void bet. Ends 1/8/23 @ 8pm ET. See terms at sportsbook dot draftkings dot com slash football terms.  Learn more about your ad choices. Visit megaphone.fm/adchoices

As behavioral health providers, our jobs often are primarily helping patients heal when their worlds are in turmoil. But we don't often talk about doing that work while our own world or even the whole world is in turmoil. What can we learn from efforts to support mental health providers working in the heart of real-time geopolitical aggression? Join us as we discuss the experience of CDP's own Drs. Bill Brim and Andrea Israel partnering with UNM's ECHO project providing just-in-time training in psychological first aid and provider resilience to providers in Ukraine. William Brim, Psy.D., is the director of the Center for Deployment Psychology (CDP) at the Uniformed Services University of the Health Sciences in Bethesda, Maryland. He joined CDP in 2007, initially as a deployment behavioral health psychologist at Malcolm Grow Medical Center and served as deputy director until 2017. Prior to joining CDP, Dr. Brim served on active duty as a psychologist in the United States Air Force from 1997 to 2007. The focus of Dr. Brim's clinical work, supervision and training is on deployment and redeployment- related mental health issues, specifically assessment and treatment of posttraumatic stress disorder and insomnia. Additionally, Dr. Brim focuses on health psychology clinical practice, the integration of mental health services in primary care and offers forensic psychology expert consultation and witness services.Andrea Israel, Ph.D., is a clinical psychologist serving as a Military Behavioral Health Child Psychologist at the Center for Deployment Psychology (CDP) at the Uniformed Services University of the Health Sciences in Bethesda, Maryland. In this role, she supports a study to assess the feasibility and to identify best practices for enhancing and expanding capabilities to deliver telehealth services to youth (dependents of active duty military) with neurodevelopmental and behavioral health needs across a dispersed geographic area. In addition, she provides Evidence-Based Psychotherapy (EBP) training. Dr. Israel graduated with her doctorate in School Psychology from the University of North Carolina at Chapel Hill and completed her postdoctoral work at Duke University Medical Center. She earned her bachelor's degree in Spanish, with a minor in Psychology, from the University of Virginia.Resources mentioned in this episode: https://deploymentpsych.org/resources-for-providers-in-wartime Calls-to-action: Subscribe to the Practical for Your Practice PodcastSubscribe to The Center for Deployment Psychology Monthly Email

Can water risk disclosure move the needle on corporate water stewardship? And what does that risk mean for our own retirement funds? In this very special episode of What About Water? - recorded on location at World Water Week - Jay sits down with Cate Lamb in Stockholm, Sweden to discuss valuing water. We hear how companies with high water-related risks affect our own bottom line, and how pensions hang in the balance when the value of those companies erodes in the face of climate change.  Cate Lamb is the Global Director of Water Security for CDP, a non-profit organization once dubbed “the most powerful Green NGO you've never heard of” by the Harvard Business Review. CDP urges large businesses to disclose their environmental risks and reduce their water footprint, using the influence of investors to catalyze change. In a report released just last year, the NGO found the cost of ignoring water risks to businesses could be over five times greater than paying now to address those risks. CDP currently has around 3,500 companies that voluntarily disclose water risks, and a group of 680 investors with $130 trillion dollars in assets pushing for that information.

Highlights from this week's conversation include:Vinoo's background and career journey (2:43)How to benchmark cost (7:54)How Bluesky addresses rising Snowflake bills (14:01)“Workload” as defined by Bluesky (17:14)Space for BI optimization (22:55)How products manage bill growth (28:34)How to optimize your workloads (35:37)Bluesky's partnerships (39:53)Getting real-time feedback on your work (44:50)Where to begin reevaluating your Snowflake game (50:47)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com..

Join me and Aharon Horwitz from AutoLeadStar to discuss their expanded media platform that delives an automotive specific Customer Data Experience Platform (CDXP) to optimize all retention and acqusition campaigns. The CDP discussion will be one of the Top 5 topics that will be discussed at the Modern Retailing Conference in November. 

Highlights from this week's conversation include:Astasia's background and career journey (3:03)How Astasia evaluates data companies (5:25)Defining “modern data stack” (8:39)The limit of the complexity of a solution (18:44)How risky early-stage acquisition really is (26:15)Flashing headlight advice for investing (30:17)Signs you should do a product integration (33:38)The next data infrastructure opportunities (36:19)The likelihood of two data worlds merging (43:55)How important open source is (49:14)Data-centric ML (53:47)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com..

Welcome to Our Classroom! In this episode, Stacy Seward, Executive Director of The Dream Network in Lawrence Massachusetts, joins to discuss the school-to-prison pipeline and prison to community re-entry, including a healing-centered transformative model along with financial literacy and economic power. Focal points: Origins of The Dream Network Wish teachers would have known or cared to know School-to-prison pipeline The impact of financial literacy and economic power Stacy Seward holds a Masters Degree in Rehabilitation Psychology and Counseling from UNC Chapel Hill School of Medicine. She has earned a Certificate of Advanced Graduate Study (CAGS) in Counselor Education and is currently pursuing her Doctorate in Applied Social and Community Psychology. Stacy is a mediator and certified diversity professional (CDP) whose practice centers around the social and psychological dimensions of justice, equity, diversity, and inclusion (JEDI). Stacy has provided equity centered technical assistance for Department of Justice grantees in programs across the nation and provides reentry guidance to organizations across the Commonwealth. Finally, Stacy is the Executive Director of The Dream Network in Lawrence Massachusetts. Her role is to use asset-based ideologies to impact racial, social, economic, educational, and environmental justice for those impacted by the carceral system. Follow: @thedreamnetwork_tdn The Dream Network For more education resources subscribe to Multicultural Classroom. #education #schools #prison #financialliteracy #trauma #healing #transform #community #Lawrence #Massachusetts #OurClassroom #MulticulturalClassroom

Guest Geoff Harcourt, CTO of CommonLit, joins Joël to talk about a thing that comes up with a lot with clients: the performance of their test suite. It's often a concern because with test suites, until it becomes a problem, people tend to not treat it very well, and people ask for help on making their test suites faster. Geoff shares how he handles a scenario like this at CommonLit. This episode is brought to you by Airbrake (https://airbrake.io/?utm_campaign=Q3_2022%3A%20Bike%20Shed%20Podcast%20Ad&utm_source=Bike%20Shed&utm_medium=website). Visit Frictionless error monitoring and performance insight for your app stack. Geoff Harcourt (https://twitter.com/geoffharcourt) Common Lit (https://www.commonlit.org/) Cuprite driver (https://cuprite.rubycdp.com/) Chrome DevTools Protocol (CDP) (https://chromedevtools.github.io/devtools-protocol/) Factory Doctor (https://test-prof.evilmartians.io/#/profilers/factory_doctor) Joël's RailsConf talk (https://www.youtube.com/watch?v=LOlG4kqfwcg) Formal Methods (https://www.hillelwayne.com/post/formally-modeling-migrations/) Rails multi-database support (https://guides.rubyonrails.org/active_record_multiple_databases.html) Knapsack pro (https://knapsackpro.com/) Prior episode with Eebs (https://www.bikeshed.fm/353) Shopify article on skipping specs (https://shopify.engineering/spark-joy-by-running-fewer-tests) Transcript: JOËL: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Joël Quenneville. And today, I'm joined by Geoff Harcourt, who is the CTO of CommonLit. GEOFF: Hi, Joël. JOËL: And together, we're here to share a little bit of what we've learned along the way. Geoff, can you briefly tell us what is CommonLit? What do you do? GEOFF: CommonLit is a 501(c)(3) non-profit that delivers a literacy curriculum in English and Spanish to millions of students around the world. Most of our tools are free. So we take a lot of pride in delivering great tools to teachers and students who need them the most. JOËL: And what does your role as CTO look like there? GEOFF: So we have a small engineering team. There are nine of us, and we run a Rails monolith. I'd say a fair amount of the time; I'm hands down in the code. But I also do the things that an engineering head has to do, so working with vendors, and figuring out infrastructure, and hiring, and things like that. JOËL: So that's quite a variety of things that you have to do. What is new in your world? What's something that you've encountered recently that's been fun or interesting? GEOFF: It's the start of the school year in America, so traffic has gone from a very tiny amount over the summer to almost the highest load that we'll encounter all year. So we're at a new hosting provider this fall. So we're watching our infrastructure and keeping an eye on it. The analogy that we've been using to describe this is like when you set up a bunch of plumbing, it looks like it all works, but until you really pump water through it, you don't see if there are any leaks. So things are in good shape right now, but it's a very exciting time of year for us. JOËL: Have you ever done some actual plumbing yourself? GEOFF: I am very, very bad at home repair. But I have fixed a toilet or two. I've installed a water filter but nothing else. What about you? JOËL: I've done a little bit of it when I was younger with my dad. Like, I actually welded copper pipes and that kind of thing. GEOFF: Oh, that's amazing. That's cool. Nice. JOËL: So I've definitely felt that thing where you turn the water source back on, and it's like, huh, let's see, is this joint going to leak, or are we good? GEOFF: Yeah, they don't have CI for plumbing, right? JOËL: [laughs] You know, test it in production, right? GEOFF: Yeah. [laughs] So we're really watching right now traffic starting to rise as students and teachers are coming back. And we're also figuring out all kinds of things that we want to do to do better monitoring of our application, so some of this is watching metrics to see if things happen. But some of this is also doing some simulated user activity after we do deploys. So we're using some automated browsers with Cypress to log into our application and do some user flows, and then report back on the results. JOËL: So is this kind of like a feature test in CI, except that you're running it in production? GEOFF: Yeah. Smoke test is the word that we've settled on for it, but we run it against our production server every time we deploy. And it's a small suite. It's nowhere as big as our big Capybara suite that we run in CI, but we're trying to get feedback in less than six minutes. That's sort of the goal. In addition to running tests, we also take screenshots with a tool called Percy, and that's a visual regression testing tool. So we get to see the screenshots, and if they differ by more than one pixel, we get a ping that lets us know that maybe our CSS has moved around or something like that. JOËL: Has that caught some visual bugs for you? GEOFF: Definitely. The state of CSS at CommonLit was very messy when I arrived, and it's gotten better, but it still definitely needs some love. There are some false positives, but it's been really, really nice to be able to see visual changes on our production pages and then be able to approve them or know that there's something we have to go back and fix. JOËL: I'm curious, for this smoke test suite, how long does it take to run? GEOFF: We run it in parallel. It runs on Buildkite, which is the same tool that we use to orchestrate our CI, and the longest test takes about five minutes. It signs in as a teacher, creates an account. It creates a class; it invites the student to that class. It then logs out, logs in as that student creates the student account, signs in as the student, joins the class. It then assigns a lesson to the student then the student goes and takes the lesson. And then, when the student submits the lesson, then the test is over. And that confirms all of the most critical flows that we would want someone to drop what they were doing if it's broken, you know, account creation, class creation, lesson creation, and students taking a lesson. JOËL: So you're compressing the first few weeks of school into five minutes. GEOFF: Yes. And I pity the school that has thousands of fake teachers, all named Aaron McCarronson at the school. JOËL: [laughs] GEOFF: But we go through and delete that data every once in a while. But we have a marketer who just started at CommonLit maybe a few weeks ago, and she thought that someone was spamming our signup form because she said, "I see hundreds of teachers named Aaron McCarronson in our user list." JOËL: You had to admit that you were the spammer? GEOFF: Yes, I did. [laughs] We now have some controls to filter those people out of reports. But it's always funny when you look at the list, and you see all these fake people there. JOËL: Do you have any rate limiting on your site? GEOFF: Yeah, we do quite a bit of it, actually. Some of it we do through Cloudflare. We have tools that limit a certain flow, like people trying to credential stuffing our password, our user sign-in forms. But we also do some further stuff to prevent people from hitting key endpoints. We use Rack::Attack, which is a really nice framework. Have you had to do that in client work with clients setting that stuff up? JOËL: I've used Rack:Attack before. GEOFF: Yeah, it's got a reasonably nice interface that you can work with. And I always worry about accidentally setting those things up to be too sensitive, and then you get lots of stuff back. One issue that we sometimes find is that lots of kids at the same school are sharing an IP address. So that's not the thing that we want to use for rate limiting. We want to use some other criteria for rate limiting. JOËL: Right, right. Do you ever find that you rate limit your smoke tests? Or have you had to bypass the rate limiting in the smoke tests? GEOFF: Our smoke tests bypass our rate limiting and our bot detection. So they've got some fingerprints they use to bypass that. JOËL: That must have been an interesting day at the office. GEOFF: Yes. [laughter] With all of these things, I think it's a big challenge to figure out, and it's similar when you're making tests for development, how to make tests that are high signal. So if a test is failing really frequently, even if it's testing something that's worthwhile, if people start ignoring it, then it stops having value as a piece of signal. So we've invested a ton of time in making our test suite as reliable as possible, but you sometimes do have these things that just require a change. I've become a really big fan of...there's a Ruby driver for Capybara called Cuprite, and it doesn't control chrome with Chrome Driver or with Selenium. It controls it with the Chrome DevTools protocol, so it's like a direct connection into the browser. And we find that it's very, very fast and very, very reliable. So we saw that our Capybara specs got significantly more reliable when we started using this as our driver. JOËL: Is this because it's not actually moving the mouse around and clicking but instead issuing commands in the background? GEOFF: Yeah. My understanding of this is a little bit hazy. But I think that Selenium and ChromeDriver are communicating over a network pipe, and sometimes that network pipe is a little bit lossy. And so it results in asynchronous commands where maybe you don't get the feedback back after something happens. And CDP is what Chrome's team and I think what Puppeteer uses to control things directly. So it's great. And you can even do things with it. Like, you can simulate different time zone for a user almost natively. You can speed up or slow down the traveling of time and the direction of time in the browser and all kinds of things like that. You can flip it into mobile mode so that the device reports that it's a touch browser, even though it's not. We have a set of mobile specs where we flip it with CDP into mobile mode, and that's been really good too. Do you find when you're doing client work that you have a demand to build mobile-specific specs for system tests? JOËL: Generally not, no. GEOFF: You've managed to escape it. JOËL: For something that's specific to mobile, maybe one or two tests that have a weird interaction that we know is different on mobile. But in general, we're not doing the whole suite under mobile and the whole suite under desktop. GEOFF: When you hand off a project...it's been a while since you and I have worked together. JOËL: For those who don't know, Geoff used to be with us at thoughtbot. We were colleagues. GEOFF: Yeah, for a while. I remember my very first thoughtbot Summer Summit; you gave a really cool lightning talk about Eleanor of Aquitaine. JOËL: [laughs] GEOFF: That was great. So when you're handing a project off to a client after your ending, do you find that there's a transition period where you're educating them about the norms of the test suite before you leave it in their hands? JOËL: It depends a lot on the client. With many clients, we're working alongside an existing dev team. And so it's not so much one big handoff at the end as it is just building that in the day-to-day, making sure that we are integrating with the team from the outset of the engagement. So one thing that does come up a lot with clients is the performance of their test suite. That's often a concern because the test suite until it becomes a problem, people tend to not treat it very well. And by the time that you're bringing on an external consultant to help, generally, that's one of the areas of the code that's been a little bit neglected. And so people ask for help on making their test suite faster. Is that something that you've had to deal with at CommonLit as well? GEOFF: Yeah, that's a great question. We have struggled a lot with the speed that our test suite...the time it takes for our test suite to run. We've done a few things to improve it. The first is that we have quite a bit of caching that we do in our CI suite around dependencies. So gems get cached separately from NPM packages and browser assets. So all three of those things are independently cached. And then, we run our suites in parallel. Our Jest specs get split up into eight containers. Our Ruby non-system tests...I'd like to say unit tests, but we all know that some of those are actually integration tests. JOËL: [laughs] GEOFF: But those tests run in 15 containers, and they start the moment gems are built. So they don't wait for NPM packages. They don't wait for assets. They immediately start going. And then our system specs as soon as the assets are built kick off and start running. And we actually run that in 40 parallel containers so we can get everything finished. So our CI suite can finish...if there are no dependency bumps and no asset bumps, our specs suite you can finish in just under five minutes. But if you add up all of that time, cumulatively, it's something like 75 minutes is the total execution as it goes. Have you tried FactoryDoctor before for speeding up test suites? JOËL: This is the gem from Evil Martians? GEOFF: Yeah, it's part of TestProf, which is their really, really unbelievable toolkit for improving specs, and they have a whole bunch of things. But one of them will tell you how many invocations of FactoryBot factories each factory got. So you can see a user factory was fired 13,000 times in the test suite. It can even do some tagging where it can go in and add metadata to your specs to show which ones might be candidates for optimization. JOËL: I gave a talk at RailsConf this year titled Your Tests Are Making Too Many Database Calls. GEOFF: Nice. JOËL: And one of the things I talked about was creating a lot more data via factories than you think that you are. And I should give a shout-out to FactoryProf for finding those. GEOFF: Yeah, it's kind of a silent killer with the test suite, and you really don't think that you're doing a whole lot with it, and then you see how many associations. How do you fight that tension between creating enough data that things are realistic versus the streamlining of not creating extraneous things or having maybe mystery guests via associations and things like that? JOËL: I try to have my base factories be as minimal as possible. So if there's a line in there that I can remove, and the factory or the model still saves, then it should be removed. Some associations, you can't do that if there's a foreign key constraint, and so then I'll leave it in. But I am a very hardcore minimalist, at least with the base factory. GEOFF: I think that makes a lot of sense. We use foreign keys all over the place because we're always worried about somehow inserting student data that we can't recover with a bug. So we'd rather blow up than think we recorded it. And as a result, sometimes setting up specs for things like a student answering a multiple choice question on a quiz ends up being this sort of if you give a mouse a cookie thing where it's you need the answer options. You need the question. You need the quiz. You need the activity. You need the roster, the students to be in the roster. There has to be a teacher for the roster. It just balloons out because everything has a foreign key. JOËL: The database requires it, but the test doesn't really care. It's just like, give me a student and make it valid. GEOFF: Yes, yeah. And I find that that challenge is really hard. And sometimes, you don't see how hard it is to enforce things like database integrity until you have a lot of concurrency going on in your application. It was a very rude surprise to me to find out that browser requests if you have multiple servers going on might not necessarily be served in the order that they were made. JOËL: [laughs] So you're talking about a scenario where you're running multiple instances of your app. You make two requests from, say, two browser tabs, and somehow they get served from two different instances? GEOFF: Or not even two browser tabs. Imagine you have a situation where you're auto-saving. JOËL: Oooh, background requests. GEOFF: Yeah. So one of the coolest features we have at CommonLit is that students can annotate and highlight a text. And then, the teachers can see the annotations and highlights they've made, and it's actually part of their assignment often to highlight key evidence in a passage. And those things all fire in the background asynchronously so that it doesn't block the student from doing more stuff. But it also means that potentially if they make two changes to a highlight really quickly that they might arrive out of order. So we've had to do some things to make sure that we're receiving in the right order and that we're not blowing away data that was supposed to be there. Just think about in a Heroku environment, for example, which is where we used to be, you'd have four dynos running. If dyno one takes too long to serve the thing for dyno two, request one may finish after request two. That was a very, very rude surprise to learn that the world was not as clean and neat as I thought. JOËL: I've had to do something similar where I'm making a bunch of background requests to a server. And even with a single dyno, it is possible for your request to come back out of order just because of how TCP works. So if it's waiting for a packet and you have two of these requests that went out not too long before each other, there's no guarantee that all the packets for request one come back before all the packets from request two. GEOFF: Yeah, what are the strategies for on the client side for dealing with that kind of out-of-order response? JOËL: Find some way to effectively version the requests that you make. Timestamp is an easy one. Whenever a request comes in, you take the response from the latest timestamp, and that wins out. GEOFF: Yeah, we've started doing some unique IDs. And part of the unique ID is the browser's timestamp. We figure that no one would try to hack themselves and intentionally screw up their own data by submitting out of order. JOËL: Right, right. GEOFF: It's funny how you have to pick something to trust. [laughs] JOËL: I'd imagine, in this case, if somebody did mess around with it, they would really only just be screwing up their own UI. It's not like that's going to then potentially crash the server because of something, and then you've got a potential vector for a denial of service. GEOFF: Yeah, yeah, that's always what we're worried about, and we have to figure out how to trust these sorts of requests as what's a valid thing and what is, as you're saying, is just the user hurting themselves as opposed to hurting someone else's stuff? MID-ROLL AD: Debugging errors can be a developer's worst nightmare...but it doesn't have to be. Airbrake is an award-winning error monitoring, performance, and deployment tracking tool created by developers for developers that can actually help cut your debugging time in half. So why do developers love Airbrake? It has all of the information that web developers need to monitor their application - including error management, performance insights, and deploy tracking! Airbrake's debugging tool catches all of your project errors, intelligently groups them, and points you to the issue in the code so you can quickly fix the bug before customers are impacted. In addition to stellar error monitoring, Airbrake's lightweight APM helps developers to track the performance and availability of their application through metrics like HTTP requests, response times, error occurrences, and user satisfaction. Finally, Airbrake Deploy Tracking helps developers track trends, fix bad deploys, and improve code quality. Since 2008, Airbrake has been a staple in the Ruby community and has grown to cover all major programming languages. Airbrake seamlessly integrates with your favorite apps to include modern features like single sign-on and SDK-based installation. From testing to production, Airbrake notifiers have your back. Your time is valuable, so why waste it combing through logs, waiting for user reports, or retrofitting other tools to monitor your application? You literally have nothing to lose. Head on over to airbrake.io/try/bikeshed to create your FREE developer account today! GEOFF: You were talking about test suites. What are some things that you have found are consistently problems in real-world apps, but they're really, really hard to test in a test suite? JOËL: Difficult to test or difficult to optimize for performance? GEOFF: Maybe difficult to test. JOËL: Third-party integrations. Anything that's over the network that's going to be difficult. Complex interactions that involve some heavy frontend but then also need a lot of backend processing potentially with asynchronous workers or something like that, there are a lot of techniques that we can use to make all those play together, but that means there's a lot of complexity in that test. GEOFF: Yeah, definitely. I've taken a deep interest in what I'm sure there's a better technical term for this, but what I call network hostile environments or bandwidth hostile environments. And we see this a lot with kids. Especially during the pandemic, kids would often be trying to do their assignments from home. And maybe there are five kids in the house, and they're all trying to do their homework at the same time. And they're all sharing a home internet connection. Maybe they're in the basement because they're trying to get some peace and quiet so they can do their assignment or something like that. And maybe they're not strongly connected. And the challenge of dealing with intermittent connectivity is such an interesting problem, very frustrating but very interesting to deal with. JOËL: Have you explored at all the concept of Formal Methods to model or verify situations like that? GEOFF: No, but I'm intrigued. Tell me more. JOËL: I've not tried it myself. But I've read some articles on the topic. Hillel Wayne is a good person to follow for this. GEOFF: Oh yeah. JOËL: But it's really fascinating when you'll see, okay, here are some invariants and things. And then here are some things that you set up some basic properties for a system. And then some of these modeling languages will then poke holes and say, hey, it's possible for this 10-step sequence of events to happen that will then crash your server. Because you didn't think that it's possible for five people to be making concurrent requests, and then one of them fails and retries, whatever the steps are. So it's really good at modeling situations that, as developers, we don't always have great intuition, things like parallelism. GEOFF: Yeah, that sounds so interesting. I'm going to add that to my list of reading for the fall. Once the school year calms down, I feel like I can dig into some technical topics again. I've got this book sitting right next to my desk, Designing Data-Intensive Applications. I saw it referenced somewhere on Twitter, and I did the thing where I got really excited about the book, bought it, and then didn't have time to read it. So it's just sitting there unopened next to my desk, taunting me. JOËL: What's the 30-second spiel for what is a data-intensive app, and why should we design for it differently? GEOFF: You know, that's a great question. I'd probably find out if I'd dug further into the book. JOËL: [laughs] GEOFF: I have found at CommonLit that we...I had a couple of clients at thoughtbot that dealt with data at the scale that we deal with here. And I'm sure there are bigger teams doing, quote, "bigger data" than we're doing. But it really does seem like one of our key challenges is making sure that we just move data around fast enough that nothing becomes a bottleneck. We made a really key optimization in our application last year where we changed the way that we autosave students' answers as they go. And it resulted in a massive increase in throughput for us because we went from trying to store updated versions of the students' final answers to just storing essentially a draft and often storing that draft in local storage in the browser and then updating it on the server when we could. And then, as a result of this, we're making key updates to the table where we store a student's answers much less frequently. And that has a huge impact because, in addition to being one of the biggest tables at CommonLit...it's got almost a billion recorded answers that we've gotten from students over the years. But because we're not writing to it as often, it also means that reads that are made from the table, like when the teacher is getting a report for how the students are doing in a class or when a principal is looking at how a school is doing, now, those queries are seeing less contention from ongoing writes. And so we've seen a nice improvement. JOËL: One strategy I've seen for that sort of problem, especially when you have a very write-heavy table but that also has a different set of users that needs to read from it, is to set up a read replica. So you have your main that is being written to, and then the read replica is used for reports and people who need to look at the data without being in contention with the table being written. GEOFF: Yeah, Rails multi-DB support now that it's native to the framework is excellent. It's so nice to be able to just drop that in and fire it up and have it work. We used to use a solution that Instacart had built. It was great for our needs, but it wasn't native to the framework. So every single time we upgraded Rails, we had to cross our fingers and hope that it didn't, you know, whatever private APIs of ActiveRecord it was using hadn't broken. So now that that stuff, which I think was open sourced from GitHub's multi-database implementation, so now that that's all native in Rails, it's really, really nice to be able to use that. JOËL: So these kinds of database tricks can help make the application much more performant. You'd mentioned earlier that when you were trying to make your test performant that you had introduced parallelism, and I feel like that's maybe a bit of an intimidating thing for a lot of people. How would you go about converting a test suite that's just vanilla RSpec, single-threaded, and then moving it in a direction of being more parallel? GEOFF: There's a really, really nice tool called Knapsack, which has a free version. But the pro version, I feel like if you're spending any money at all on CI, it's immediately worth the cost. I think it's something like $75 a month for each suite that you run on it. And Knapsack does this dynamic allocation of tests across containers. And it interfaces with several of the popular CI providers so that it looks at environment variables and can tell how many containers you're splitting across. It'll do some things, like if some of your containers start early and some of them start late, it will distribute the work so that they all end at the same time, which is really nice. We've preferred CI providers that charge by the minute. So rather than just paying for a service that we might not be using, we've used services like Semaphore, and right now, we're on Buildkite, which charge by the minute, which means that you can decide to do as much parallelism as you want. You're just paying for the compute time as you run things. JOËL: So that would mean that two minutes of sequential build time costs just the same as splitting it up in parallel and doing two simultaneous minutes of build time. GEOFF: Yeah, that is almost true. There's a little bit of setup time when a container spins up. And that's one of the key things that we optimize. I guess if we ran 200 containers if we were like Shopify or something like that, we could technically make our CI suite finish faster, but it might cost us three times as much. Because if it takes a container 30 seconds to spin up and to get ready, that's 30 seconds of dead time when you're not testing, but you're paying for the compute. So that's one of the key optimizations that we make is figuring out how many containers do we need to finish fast when we're not just blowing time on starting and finishing? JOËL: Right, because there is a startup cost for each container. GEOFF: Yeah, and during the work day when our engineers are working along, we spin up 200 EC2 machines or 150 EC2 machines, and they're there in the fleet, and they're ready to go to run CI jobs for us. But if you don't have enough machines, then you have jobs that sit around waiting to start, that sort of thing. So there's definitely a tension between figuring out how much parallelism you're going to do. But I feel like to start; you could always break your test suite into four pieces or two pieces and just see if you get some benefit to running a smaller number of tests in parallel. JOËL: So, manually splitting up the test suite. GEOFF: No, no, using something like Knapsack Pro where you're feeding it the suite, and then it's dividing up the tests for you. I think manually splitting up the suite is probably not a good practice overall because I'm guessing you'll probably spend more engineering time on fiddling with which tests go where such that it wouldn't be cost-effective. JOËL: So I've spent a lot of time recently working to improve a parallel test suite. And one of the big problems that you have is trying to make sure that all of your parallel surfaces are being used efficiently, so you have to split the work evenly. So if you said you have 70 minutes worth of work, if you give 50 minutes to one worker and 20 minutes to the other, that means that your total test suite is still 50 minutes, and that's not good. So ideally, you split it as evenly as possible. So I think there are three evolutionary steps on the path here. So you start off, and you're going to manually split things out. So you're going to say our biggest chunk of tests by time are the feature specs. We'll make them almost like a separate suite. Then we'll make the models and controllers and views their own thing, and that's roughly half and half, and run those. And maybe you're off by a little bit, but it's still better than putting them all in one. It becomes difficult, though, to balance all of these because then one might get significantly longer than the other then, you have to manually rebalance it. It works okay if you're only splitting it among two workers. But if you're having to split it among 4, 8, 16, and more, it's not manageable to do this, at least not by hand. If you want to get fancy, you can try to automate that process and record a timing file of how long every file takes. And then when you kick off the build process, look at that timing file and say, okay, we have 70 minutes, and then we'll just split the file so that we have roughly 70 divided by number of workers' files or minutes of work in each process. And that's what gems like parallel_tests do. And Knapsack's Classic mode works like this as well. That's decently good. But the problem is you're working off of past information. And so if the test has changed or just if it's highly variable, you might not get a balanced set of workers. And as you mentioned, there's a startup cost, and so not all of your workers boot up at the same time. And so you might still have a very uneven amount of work done by each worker by statically determining the work to be done via a timing file. So the third evolution here is a dynamic or a self-balancing approach where you just put all of the tests or the files in a queue and then just have every worker pull one or two tests when it's ready to work. So that way, if something takes a lot longer than expected, well, it's just not pulling more from the queue. And everybody else still pulls, and they end up all balancing each other out. And then ideally, every worker finishes work at exactly the same time. And that's how you know you got the most value you could out of your parallel processes. GEOFF: Yeah, there's something about watching all the jobs finish in almost exactly, you know, within 10 seconds of each other. It just feels very, very satisfying. I think in addition to getting this dynamic splitting where you're getting either per file or per example split across to get things finishing at the same time, we've really valued getting fast feedback. So I mentioned before that our Jest specs start the moment NPM packages get built. So as soon as there's JavaScripts that can be executed in test, those kick-off. As soon as our gems are ready, the RSpec non-system tests go off, and they start running specs immediately. So we get that really, really fast feedback. Unfortunately, the browser tests take the longest because they have to wait for the most setup. They have the most dependencies. And then they also run the slowest because they run in the browser and everything. But I think when things are really well-oiled, you watch all of those containers end at roughly the same time, and it feels very satisfying. JOËL: So, a few weeks ago, on an episode of The Bike Shed, I talked with Eebs Kobeissi about dependency graphs and how I'm super excited about it. And I think I see a dependency graph in what you're describing here in that some things only depend on the gem file, and so they can start working. But other things also depend on the NPM packages. And so your build pipeline is not one linear process or one linear process that forks into other linear processes; it's actually a dependency graph. GEOFF: That is very true. And the CI tool we used to use called Semaphore actually does a nice job of drawing the dependency graph between all of your steps. Buildkite does not have that, but we do have a bunch of steps that have to wait for other steps to finish. And we do it in our wiki. On our repo, we do have a diagram of how all of this works. We found that one of the things that was most wasteful for us in CI was rebuilding gems, reinstalling NPM packages (We use Yarn but same thing.), and then rebuilding browser assets. So at the very start of every CI run, we build hashes of a bunch of files in the repository. And then, we use those hashes to name Docker images that contain the outputs of those files so that we are able to skip huge parts of our CI suite if things have already happened. So I'll give an example if Ruby gems have not changed, which we would know by the Gemfile.lock not having changed, then we know that we can reuse a previously built gems image that has the gems that just gets melted in, same thing with yarn.lock. If yarn.lock hasn't changed, then we don't have to build NPM packages. We know that that already exists somewhere in our Docker registry. In addition to skipping steps by not redoing work, we also have started to experiment...actually, in response to a comment that Chris Toomey made in a prior Bike Shed episode, we've started to experiment with skipping irrelevant steps. So I'll give an example of this if no Ruby files have changed in our repository, we don't run our RSpec unit tests. We just know that those are valid. There's nothing that needs to be rerun. Similarly, if no JavaScript has changed, we don't run our Jest tests because we assume that everything is good. We don't lint our views with erb-lint if our view files haven't changed. We don't lint our factories if the model or the database hasn't changed. So we've got all these things to skip key types of processing. I always try to err on the side of not having a false pass. So I'm sure we could shave this even tighter and do even less work and sometimes finish the build even faster. But I don't want to ever have a thing where the build passes and we get false confidence. JOËL: Right. Right. So you're using a heuristic that eliminates the really obvious tests that don't need to be run but the ones that maybe are a little bit more borderline, you keep them in. Shaving two seconds is not worth missing a failure. GEOFF: Yeah. And I've read things about big enterprises doing very sophisticated versions of this where they're guessing at which CI specs might be most relevant and things like that. We're nowhere near that level of sophistication right now. But I do think that once you get your test suite parallelized and you're not doing wasted work in the form of rebuilding dependencies or rebuilding assets that don't need to be rebuilt, there is some maybe not low, maybe medium hanging fruit that you can use to get some extra oomph out of your test suite. JOËL: I really like that you brought up this idea of infrastructure and skipping. I think in my own way of thinking about improving test suites, there are three broad categories of approaches you can take. One variable you get to work with is that total number of time single-threaded, so you mentioned 70 minutes. You can make that 70 minutes shorter by avoiding database writes where you don't need them, all the common tricks that we would do to actually change the test themselves. Then we can change...as another variable; we get to work with parallelism, we talked about that. And then finally, there's all that other stuff that's not actually executing RSpec like you said, loading the gems, installing NPM packages, Docker images. All of those, if we can skip work running migrations, setting up a database, if there are situations where we can improve the speed there, that also improves the total time. GEOFF: Yeah, there are so many little things that you can pick at to...like, one of the slowest things for us is Elasticsearch. And so we really try to limit the number of specs that use Elasticsearch if we can. You actually have to opt-in to using Elasticsearch on a spec, or else we silently mock and disable all of the things that happen there. When you're looking at that first variable that you were talking about, just sort of the overall time, beyond using FactoryDoctor and FactoryProf, is there anything else that you've used to just identify the most egregious offenders in a test suite and then figure out if they're worth it? JOËL: One thing you can do is hook into Active Support notification to try to find database writes. And so you can find, oh, here's where all of the...this test is making way too many database writes for some reason, or it's making a lot, maybe I should take a look at it; it's a hotspot. GEOFF: Oh, that's really nice. There's one that I've always found is like a big offender, which is people doing negative expectations in system specs. JOËL: Oh, for their Capybara wait time. GEOFF: Yeah. So there's a really cool gem, and the name of it is eluding me right now. But there's a gem that raises a special exception if Capybara waits the full time for something to happen. So it lets you know that those things exist. And so we've done a lot of like hunting for...Knapsack will report the slowest examples in your test suite. So we've done some stuff to look for the slowest files and then look to see if there are examples of these negative expectations that are waiting 10 seconds or waiting 8 seconds before they fail. JOËL: Right. Some files are slow, but they're slow for a reason. Like, a feature spec is going to be much slower than a model test. But the model tests might be very wasteful and because you have so many of them, if you're doing the same pattern in a bunch of them or if it's a factory that's reused across a lot of them, then a small fix there can have some pretty big ripple effects. GEOFF: Yeah, I think that's true. Have you ever done any evaluation of test suite to see what files or examples you could throw away? JOËL: Not holistically. I think it's more on an ad hoc basis. You find a place, and you're like, oh, these tests we probably don't need them. We can throw them out. I have found dead tests, tests that are not executed but still committed to the repo. GEOFF: [laughs] JOËL: It's just like, hey, I'm going to get a lot of red in my diff today. GEOFF: That always feels good to have that diff-y check-in, and it's 250 lines or 1,000 lines of red and 1 line of green. JOËL: So that's been a pretty good overview of a lot of different areas related to performance and infrastructure around tests. Thank you so much, Geoff, for joining us today on The Bike Shed to talk about your experience at CommonLit doing this. Do you have any final words for our listeners? GEOFF: Yeah. CommonLit is hiring a senior full-stack engineer, so if you'd like to work on Rails and TypeScript in a place with a great test suite and a great team. I've been here for five years, and it's a really, really excellent place to work. And also, it's been really a pleasure to catch up with you again, Joël. JOËL: And, Geoff, where can people find you online? GEOFF: I'm Geoff with a G, G-E-O-F-F Harcourt, @geoffharcourt. And that's my name on Twitter, and it's my name on GitHub, so you can find me there. JOËL: And we'll make sure to include a link to your Twitter profile in the show notes. The show notes for this episode can be found at bikeshed.fm. This show is produced and edited by Mandy Moore. If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. If you have any feedback, you can reach us at @_bikeshed or reach me at @joelquen on Twitter or at hosts@bikeshed.fm via email. Thank you so much for listening to The Bike Shed, and we'll see you next week. Byeeeeeee!!!!!! ANNOUNCER: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Highlights from this week's conversation include:Benn's background and career journey (2:28)The problem Benn sought to solve (4:48)Data engineering a decade ago (9:58)Technology inside vs. outside Silicon Valley (18:11)What's next for data (24:42)Mode's evolution and journey (29:31)Challenges of getting enough context to create (39:21)Current trends that won't see long-term benefits (48:44)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com.

It's that time of year: Q4 is typically when brands set their vision for the coming year and take a hard look at their loyalty programs. Is it time for an overhaul?Billie and Billy dive into the reasons why it may or may not be the right time to shake things up. Whether trying to regain market share, revisit your tech stack, or re-examine how loyalty programs play out across various platforms, this episode is all about unlocking an exceptional personalization and omnichannel strategy around loyalty.  Topics Discussed:Artificial boosts in loyalty metrics observed during Covid lockdownHow loyalty plays out across multiple tech platforms versus a single choiceWhat consumers care about in a loyalty programThe value of in-person loyalty experiences, especially for point of saleHow to design CDP architecture for loyalty program strategy 

Orthodent co-founder and CDP partner Dr. Tarek Aly shares his story of moving to the US as a young dentist, what he learned from growing not one but two DSOs (including a deep dive into the KPIs that every dental group needs to measure), and how to avoid the most common mistakes that DSOs make around culture. Website: https://www.orthodentllc.com/ Say Hello to Dr. Tarek! Facebook: https://www.facebook.com/LifeIsGreatToday Instagram: https://www.instagram.com/life.is.delightful/ Linkedin: https://www.linkedin.com/in/lead2success/ Twitter: https://twitter.com/TarekAly Orthodent Management Linkedin: https://www.linkedin.com/company/orthodentmanagement/