Podcasts about gp3

Aucun garde suisse n'a été blessé pendant l'enregistrement de cet épisode. Et pourtant, ca ferait un super déguisement dans Mask Singer. Autour d'Alex malade, Arnaud, Bastien et Jérémy débattent du costume le mieux réussi entre la Cheminée du Vatican, Jacques Legros (mais sans le hamster) ou Sophie Tapie (sans son tapis). Enfin, tout ce qui a été vu & entendu. Mais aussi dans l'actu, le caillou dans la chaussure de Delphine Ernotte, RMChérie 25, des nouveaux départs à RMC, RMC Découverte qui ne documente plus, du foute (mais sans la ligue), des primes à 20h45 de T18, des promesses non tenues de Novo 19 et, avec le chat, GP3. Et dans tout ca, pêle-mêle, Natacha Amal & Paul Amar, Habemus Platane, Jacques Legros dans la ligne 9, Les traites de vache, la sarcleuse, RMC Girlz, Thibaut Djiangrandé, Toobo tout neuf et l'absence de Le Mouv' dans les paddocks. Au sommaire : 0:00 - Introduction 8:15 - Vu & Entendu 53:31 - L'Actu 1:51:41 - Conclu Les sources : TikTok - David Unal - Coulisses annonce nouveau Pape BFMTV Puremédias - Audiences access : Quel score pour les éditions spéciales des commémorations du 8 mai 1945, bousculées par l'élection du nouveau pape Léon XIV, sur TF1 et France 2 ? TF1 + - Une surprise d'Isabelle Ithurburu et un bel hommage en vidéo : les adieux au 13H de Jacques Legros 20 minutes - TF1 : Pour son dernier JT, Jacques Legros rassemble 4,7 millions de téléspectateurs Puremédias - Audiences : Quel bilan pour la saison 4 des “Traîtres”, pour la première fois diffusé au printemps, sur M6 ? TéléStar - EXCLU. Les Traîtres (M6) : voici le casting complet de la saison 5 Libération - Dix ans de règne sur la télé publique (1/3) / France Télévisions : comment la PDG Delphine Ernotte-Cunci veut rester au pouvoir Libération - Dix ans de règne sur la télé publique (2/3) / France Télévisions : avec Delphine Ernotte-Cunci, on ne change pas des programmes qui marchent Libération - Dix ans de règne sur la télé publique (3/3) / Delphine Ernotte-Cunci à France Télévisions, du dialogue social attentif à la verticalité patronale X - SDJ France 3 RN Le Figaro - «Négociations exclusives» entre NRJ et CMA Média pour la cession de la chaîne Chérie 25 Radioscope - NRJ Hits L'Equipe - Nicolas Vilas et Thibaut Giangrande vont quitter RMC Le Figaro - Suppression de la LFP, droits TV, masse salariale… Le plan choc du président de la FFF Philippe Diallo pour révolutionner le football français Le Monde - RMC Découverte sanctionnée d'une amende de 100 000 euros pour n'avoir pas diffusé assez de documentaires Le Parisien - T18 : Laurent Ruquier inaugurera la nouvelle chaîne le 6 juin à 19h45 Le Parisien - Claire Arnoux, journal de 15 minutes, streaming… la chaîne NOVO19 prépare son lancement sur la TNT GP Explorer - Dossier de presse Description alternative : Cof cof (pas Jean-Pierre), Alex est malade ou quoi ? Feur. Kyiv Kyiv (pas le Pape), ah oui (on est fatigués). Rejoignez le Discord d'Alex Arbey, suivez @jplussept sur X/Twitter et sur Instagram ou @jplus7.fr sur Bluesky Laissez-nous vos avis sur ce que vous avez vous aussi vu & entendu tout au long de la semaine sur repondeur.jplus7.fr Une émission animée par Alex Arbey, en direct sur Twitch tous les lundi à 20h35 : twitch.tv/alexarbey

Lewis Hamilton, Charles Leclerc, Oscar Piastri and George Russell are just a handful of the Formula 1 stars born in Bruno Michel's racing series. Multiple F1 World Champions and Grand Prix-winners have risen from Formula 2 and Formula 3, previously known as GP2 and GP3. From the very first GP2 champion, Nico Rosberg, to Lando Norris, Nico Hulkenberg, Pierre Gasly, Valtteri Bottas and many more, Bruno has been supporting young drivers in their journey to the pinnacle of motorsport for two decades. He tells Tom Clarkson how he built the ladder to Formula 1, why Hamilton and Leclerc particularly stood out, and his prior work as manager to drivers including Fernando Alonso and Mark Webber. As F1 teams look to sign stars for the 2025 season, Bruno explains why future Haas driver Ollie Bearman is ready to step up to the top level, and what Mercedes junior driver Andrea Kimi Antonelli can do to claim his place in F1. Plus, how F1 Academy will become a pathway to F3 and beyond. Experience F1, F2 + F3 live in 2024 Book your seat at a Grand Prix today. The second half of the season is on sale now at tickets.formula1.com This episode is sponsored by: Indochino: go to indochino.com and use code GRID to get 10% off any purchase of $399 or more Fitbod: join Fitbod today to get your personalized workout plan. Get 25% off your subscription or try the app FREE at Fitbod.me/GRID

My very first driver interview!Join me for an exclusive, in-depth interview with racing sensation Luca Ghiotto! In this video, Luca opens up about his incredible journey from GP3 vice-champion to Formula 2 star and shares his dreams of conquering iconic races like the 24 Hours of Le Mans and the Indy 500. Discover Luca's passions off the track, including his love for simulator racing and his involvement in his family's RC car business. We delve into the challenges of breaking into Formula 1, highlighting the crucial role of financial backing and the power of social media in today's racing world. Luca reflects on his thrilling experiences in IndyCar, discussing the physical demands and the exciting potential for future opportunities, especially with his local team, Prema. Don't miss this engaging and insightful conversation with one of motorsport's brightest talents. Watch now to hear firsthand from Luca Ghiotto about his career, ambitions, and what it takes to succeed in the fast-paced world of racing. Subscribe for more exclusive content and stay tuned for upcoming interviews and behind-the-scenes access!Luca Ghiotto: From F2 Veteran to Indycar Supersub (My First Ever Driver Interview!)https://youtu.be/xSUrWl5PXYg#lucaghiotto #ghiotto #f2 #formula2 #indycar Hosted on Acast. See acast.com/privacy for more information.

2017, Gran Premio del Bahrein: la nuova F2 parte con molti occhi degli addetti ai lavori puntati sul nuovo pilota della Prema, Charles Leclerc, fresco campione della GP3. Al primo appuntamento stagionale, il monegasco fa subito capire a tutti che non è lì per caso, con una sprint race impressionante che non lascia spazio a dubbi su come andrà il resto del campionato.

In this episode, we provide an overview of Amazon EBS, which stands for Elastic Block Storage. We explain what block storage is and how EBS provides highly available and high-performance storage volumes that can be attached to EC2 instances. We discuss the various EBS volume types, including GP3, GP2, provisioned IOPS, and HDD volumes, and explain how they differ in performance characteristics like IOPS and throughput. We go over important concepts like IOPS, throughput, and volume types so listeners can make informed decisions when provisioning EBS. We also cover EBS features like snapshots, encryption, direct API access, and ECS integration. Overall, this is a comprehensive guide to understanding EBS and choosing the right options based on your workload needs.

We interrupt our regular scheduling to bring you a special episode of Performance Process to coincide with the start of the Formula 1 season. In this special episode we focus less on the processes of going faster and more on the transferable skills, processes, and obsessions between F1 and cycling with former F1 driver and Escape Collective member, Jack Aitken.Jack was the 2015 Formula Renault Eurocup champion and he competed in GP3 and FIA Formula 2 before becoming test drive at Renault F1. He is best known in F1 circles for his time with Williams F1, whom he drove for in the 2020 Sakhir Gand Prix. We recorded this episode last July when he was doubling up driving duties with IMSA's Whelen Cadillac and DTM's Emil Frey racing. Jack is back in IMSA (International Motor Sports Association) this year with the number 31 car Whelen Engineering Cadillac.Jack also takes to two wheels as often as any of us and has competed in both criteriums and gran fondos. We ask Jack what the fascination is with cycling for F1 drivers, and discuss the transferable skills, the leakage of talent that is F1's loss and cycling's gain, environmental endeavours of both sports, how breathable his underwear is, and finally rules … but of course.

Silvia Bellot, Senior Director of Sporting and Race Operations at Las Vegas Grand Prix, Inc. Bellot manages the relationship with the governing body, the FIA, and oversees the track marshals, track set up and repairs, as well as the pit building area. Bellot has been a steward in several championships including WRC, WTCC, FE, F2, F3, GP2, GP3, DTM, and more, and in 2020 she became the first ever FIA female race director, being responsible for the FIA F2 and F3 Championships. https://www.epartrade.com/more/onlineraceindustryweek From EPARTRADE, RACER.com, & SPEED SPORT. Presented by ETS Racing Fuels, Fifth Third Bank Motorsports, Peak, Penske Racing Shocks, Scott Lewis Associates, and Total Seal Piston Rings. Sponsored by ARP, Performance Plus Global Logistics, and Shopmonkey.

In episode 111 your host, Fiona Pawley, interviews Leon Price - Team & Sporting Director at Envision Racing. Listen as Leon walks us through his career in motorsport from sweeping floors and making tea at DPR racing, Head of Operations at GP3, to becoming Formula E World Champions with Envision Racing. For Leon racing is a family affair. We talk about fond memories of his dad's (David Price - "Pricey") career, winning Le Mans in the 80's with Mercedes. A touching reflection on losing his best friend with the passing of Pricey. The importance of talking about how we are feeling in the tough times, finding something you enjoy for your wellbeing and looking after your people at work. Taking a leaf out of Pricey's book – “be a nice bloke, have a lot of fun and find something to do that you love.”   Links: Leon Price, Envision Racing Leave a review!   Don't forget to check out the Inside Silverstone website for more great content. Would you like to appear on the podcast? Own a business or work in/around the Silverstone business or motorsport region? Have a story or/and knowledge to share? Get in contact with Chris on insidesilverstone@longhurst.co.uk, or reach out on Twitter @SilverstonePod.   ABOUT THE HOSTS Chris Broome Chris is first and foremost a big tech, motor-sport, and gaming fan. So the opportunity to host a podcast focusing on these topics was too good to turn down. In his day-to-day life Chris is a Chartered Financial Planner and Fellow of the Chartered Institute of Insurers. His business, Longhurst, has a niche providing financial advice to clients and businesses who work in the tech, innovation, and engineering sectors. Their head office is located on Silverstone Park, Northamptonshire. 'A business plan without a personal plan is pointless.'    Fiona Pawley Fiona brings a unique perspective to leadership and management, drawing from her personal motorsport experience to help people learn how to better tap into their personal power, improve relationships, and establish themselves as leaders in their industry. With a focus on practical techniques and actionable strategies, Fiona's coaching and training is a valuable resource for anyone looking to improve their leadership and management skills. Her aim is to provide a bespoke and enjoyable coaching or training experience, tailored for personal and business needs, helping individuals unleash their potential and make the key changes they need. Whether you're a seasoned business owner or just starting out, the Inside Silverstone podcast is for you. So, tune in and let's explore the world of business together.

On episode 82 of Driven to Compete Carey met with Jacob Hiller. Jacob is an alignment and car setup specialist, driver, and race engineer. He drives and engineers for a WRL endurance team called Open Throttle Racing in the GP3 class. He also works part-time for some of the professional series and he also has a full-time job so he's a busy guy. Our sponsor for this episode is Chris Taylor Racing Chris Taylor Racing Services is a longtime provider of storage, transportation, and maintenance work on a variety of racecars in the Austin area. On the same site since 2003, located across the street from the world-famous Circuit of the Americas. Chris is a veteran of the motorsports industry, working on everything from B-Specs (TCB), Formula cars, Trans-Am cars, and a Championship winning SRO TC Americas crew chief for Skip Barber Racing Team. Our goal is to bring Professional level service and support to your club race or track day! Website: https://christaylorracing.com Email: christaylorracing@gmail.com Connect with Driven To Compete for sponsorship opportunities Website: www.DrivenToCompete.com Newsletter: https://manage.kmail-lists.com/subscriptions/subscribe?a=R9E7pX&g=VHesvQ YouTube: https://www.youtube.com/channel/UCnWO0ybrgN1mPDH_HxUswsA Email: info@driventocompete.com Phone: (512) 222-3402 --- Support this podcast: https://podcasters.spotify.com/pod/show/racingwire/support

On episode 5 of Driven to Compete Carey sat down with Austin, TX driver Travis Wiley. He's currently enrolled at UNC Charlotte in mechanical engineering but he's been racing for years. Travis is an experienced US National Karting driver and he's currently driving Spec Miata at NASA and SCCA races. He's got a really cool story and high aspirations. Today's episode is sponsored by Valdez Motorsport. They have 3 seats available (1 GP2 and 2 GP3) for the upcoming 14-hour WRL endurance race at Daytona International Speedway on June 9-10, 2023. Website: www.valdezmotorsport.com Email: race@valdezmotorsport.com This is your chance to get in an awesome race, with a great team, at a super event. Connect with Driven To Compete for sponsorship opportunities Website: www.DrivenToCompete.com Newsletter: https://manage.kmail-lists.com/subscriptions/subscribe?a=R9E7pX&g=VHesvQ YouTube: https://www.youtube.com/channel/UCnWO0ybrgN1mPDH_HxUswsA Email: info@driventocompete.com Phone: (512) 222-3402 --- Support this podcast: https://podcasters.spotify.com/pod/show/racingwire/support

History has been made in multiple ways at #GP3 of Marbula One at Sakura Garden! Join us as we discuss the third race of the M1 Season, the downfalls of certain teams, the unexpected success from others, Where's Roldo, Ramen, Trashbags, and everything in between! We also read your Overreactions and Mailbags, and get an update on Predictions and Fantasy! This is THE Number 1 Podcast in Marble Sports, Let it Roll!Follow us on Twitter:Dekker: https://twitter.com/DoubleDekksHector: https://twitter.com/hwalkermusicTerm: https://twitter.com/BigGetsBigTermSky: https://twitter.com/Skyfall_707Nonagon: https://twitter.com/Nonagon_VioletPippin: https://twitter.com/Virgo_The_Star---------------------------------If you have a big take of your own DM the show on Twitter,find us on Twitter: (https://t.co/OhU31PKZw0)YouTube: (https://www.youtube.com/c/biggetsbigt...)iTunes: (https://t.co/hLrQK71k4z)Spotify: (https://t.co/dFsujO5h5v)

Our favorite asian fusion restaurant may have disappointed, but the track at Sakura Garden did not! Also, HAPPY BIRTHDAY PIPPEN! Use #BlackAndBlueEye to make your prediction for fastest lap and race winner of GP3 at #SakuraGarden!See ya after the race. Let's have an awesome weekend!This is THE Number 1 Podcast in Marble Sports, Let it Roll!Follow us on Twitter:Dekker: https://twitter.com/DoubleDekksHector: https://twitter.com/hwalkermusicTerm: https://twitter.com/BigGetsBigTermSky: https://twitter.com/Skyfall_707Nonagon: https://twitter.com/Nonagon_VioletPippin: https://twitter.com/Virgo_The_Star---------------------------------If you have a big take of your own DM the show on Twitter,find us on Twitter: (https://t.co/OhU31PKZw0)YouTube: (https://www.youtube.com/c/biggetsbigt...)iTunes: (https://t.co/hLrQK71k4z)Spotify: (https://t.co/dFsujO5h5v)

Thanks to the over 42,000 latent space explorers who checked out our Replit episode! We are hosting/attending a couple more events in SF and NYC this month. See you if in town!Lexica.art was introduced to the world 24 hours after the release of Stable Diffusion as a search engine for prompts, gaining instant product-market fit as a world discovering generative AI also found they needed to learn prompting by example.Lexica is now 8 months old, serving 5B image searches/day, and just shipped V3 of Lexica Aperture, their own text-to-image model! Sharif Shameem breaks his podcast hiatus with us for an exclusive interview covering his journey building everything with AI!The conversation is nominally about Sharif's journey through his three startups VectorDash, Debuild, and now Lexica, but really a deeper introspection into what it takes to be a top founder in the fastest moving tech startup scene (possibly ever) of AI. We hope you enjoy this conversation as much as we did!Full transcript is below the fold. We would really appreciate if you shared our pod with friends on Twitter, LinkedIn, Mastodon, Bluesky, or your social media poison of choice!Timestamps* [00:00] Introducing Sharif* [02:00] VectorDash* [05:00] The GPT3 Moment and Building Debuild* [09:00] Stable Diffusion and Lexica* [11:00] Lexica's Launch & How it Works* [15:00] Being Chronically Early* [16:00] From Search to Custom Models* [17:00] AI Grant Learnings* [19:30] The Text to Image Illuminati?* [20:30] How to Learn to Train Models* [24:00] The future of Agents and Human Intervention* [29:30] GPT4 and Multimodality* [33:30] Sharif's Startup Manual* [38:30] Lexica Aperture V1/2/3* [40:00] Request for AI Startup - LLM Tools* [41:00] Sequencing your Genome* [42:00] Believe in Doing Great Things* [44:30] Lightning RoundShow Notes* Sharif's website, Twitter, LinkedIn* VectorDash (5x cheaper than AWS)* Debuild Insider, Fast company, MIT review, tweet, tweet* Lexica* Introducing Lexica* Lexica Stats* Aug: “God mode” search* Sep: Lexica API * Sept: Search engine with CLIP * Sept: Reverse image search* Nov: teasing Aperture* Dec: Aperture v1* Dec - Aperture v2* Jan 2023 - Outpainting* Apr 2023 - Aperture v3* Same.energy* AI Grant* Sharif on Agents: prescient Airpods tweet, Reflection* MiniGPT4 - Sharif on Multimodality* Sharif Startup Manual* Sharif Future* 23andMe Genome Sequencing Tool: Promethease* Lightning Round* Fave AI Product: Cursor.so. Swyx ChatGPT Menubar App.* Acceleration: Multimodality of GPT4. Animated Drawings* Request for Startup: Tools for LLMs, Brex for GPT Agents* Message: Build Weird Ideas!TranscriptAlessio: Hey everyone, welcome to the Latent Space podcast. This is Alessio, partner and CTO on Residence at Decibel Partners. I'm joined by my co-host Wix, writer and editor of Latent Space. And today we have Sharish Amin. Welcome to the studio. Sharif: Awesome. Thanks for the invite.Swyx: Really glad to have you. [00:00] Introducing SharifSwyx: You've been a dream guest, actually, since we started drafting guest lists for this pod. So glad we could finally make this happen. So what I like to do is usually introduce people, offer their LinkedIn, and then prompt you for what's not on your LinkedIn. And to get a little bit of the person behind the awesome projects. So you graduated University of Maryland in CS. Sharif: So I actually didn't graduate, but I did study. Swyx: You did not graduate. You dropped out. Sharif: I did drop out. Swyx: What was the decision behind dropping out? Sharif: So first of all, I wasn't doing too well in any of my classes. I was working on a side project that took up most of my time. Then I spoke to this guy who ended up being one of our investors. And he was like, actually, I ended up dropping out. I did YC. And my company didn't end up working out. And I returned to school and graduated along with my friends. I was like, oh, it's actually a reversible decision. And that was like that. And then I read this book called The Case Against Education by Brian Kaplan. So those two things kind of sealed the deal for me on dropping out. Swyx: Are you still on hiatus? Could you still theoretically go back? Sharif: Theoretically, probably. Yeah. Still on indefinite leave. Swyx: Then you did some work at Mitra? Sharif: Mitra, yeah. So they're lesser known. So they're technically like an FFRDC, a federally funded research and development center. So they're kind of like a large government contractor, but nonprofit. Yeah, I did some computer vision work there as well. [02:00] VectorDashSwyx: But it seems like you always have an independent founder bone in you. Because then you started working on VectorDash, which is distributed GPUs. Sharif: Yes. Yeah. So VectorDash was a really fun project that we ended up working on for a while. So while I was at Mitra, I had a friend who was mining Ethereum. This was, I think, 2016 or 2017. Oh my God. Yeah. And he was mining on his NVIDIA 1080Ti, making around like five or six dollars a day. And I was trying to train a character recurrent neural network, like a character RNN on my iMessage text messages to make it like a chatbot. Because I was just curious if I could do it. Because iMessage stores all your past messages from years ago in a SQL database, which is pretty nifty. But I wanted to train it. And I needed a GPU. And it was, I think, $60 to $80 for a T4 on AWS, which is really slow compared to a 1080Ti. If you normalize the cost and performance versus the 1080Ti when someone's mining Ethereum, it's like a 20x difference. So I was like, hey, his name was Alex. Alex, I'll give you like 10 bucks if you let me borrow your 1080Ti for a week. I'll give you 10 bucks per day. And it was like 70 bucks. And I used it to train my model. And it worked great. The model was really bad, but the whole trade worked really great. I got a really high performance GPU to train my model on. He got much more than he was making by mining Ethereum. So we had this idea. I was like, hey, what if we built this marketplace where people could rent their GPUs where they're mining cryptocurrency and machine learning researchers could just rent them out and pay a lot cheaper than they would pay AWS. And it worked pretty well. We launched in a few months. We had over 120,000 NVIDIA GPUs on the platform. And then we were the cheapest GPU cloud provider for like a solid year or so. You could rent a pretty solid GPU for like 20 cents an hour. And cryptocurrency miners were making more than they would make mining crypto because this was after the Ethereum crash. And yeah, it was pretty cool. It just turns out that a lot of our customers were college students and researchers who didn't have much money. And they weren't necessarily the best customers to have as a business. Startups had a ton of credits and larger companies were like, actually, we don't really trust you with our data, which makes sense. Yeah, we ended up pivoting that to becoming a cloud GPU provider for video games. So we would stream games from our GPUs. Oftentimes, like many were located just a few blocks away from you because we had the lowest latency of any cloud GPU provider, even lower than like AWS and sometimes Cloudflare. And we decided to build a cloud gaming platform where you could pretty much play your own games on the GPU and then stream it back to your Mac or PC. Swyx: So Stadia before Stadia. Sharif: Yeah, Stadia before Stadia. It's like a year or so before Stadia. Swtx: Wow. Weren't you jealous of, I mean, I don't know, it sounds like Stadia could have bought you or Google could have bought you for Stadia and that never happened? Sharif: It never happened. Yeah, it didn't end up working out for a few reasons. The biggest thing was internet bandwidth. So a lot of the hosts, the GPU hosts had lots of GPUs, but average upload bandwidth in the United States is only 35 megabits per second, I think. And like a 4K stream needs like a minimum of 15 to 20 megabits per second. So you could really only utilize one of those GPUs, even if they had like 60 or 100. [05:00] The GPT3 Moment and Building DebuildSwyx: And then you went to debuild July 2020, is the date that I have. I'm actually kind of just curious, like what was your GPT-3 aha moment? When were you like GPT-3-pilled? Sharif: Okay, so I first heard about it because I was also working on another chatbot. So this was like after, like everything ties back to this chatbot I'm trying to make. This was after working on VectorDash. I was just like hacking on random projects. I wanted to make the chatbot using not really GPT-2, but rather just like it would be pre-programmed. It was pretty much you would give it a goal and then it would ask you throughout the week how much progress you're making to that goal. So take your unstructured response, usually a reply to a text message, and then it would like, plot it for you in like a table and you could see your progress over time. It could be for running or tracking calories. But I wanted to use GPT-3 to make it seem more natural because I remember someone on Bookface, which is still YC's internal forum. They posted and they were like, OpenAI just released AGI and it's GPT-3. I asked it like a bunch of logic puzzles and it solved them all perfectly. And I was like, what? How's no one else talking about this? Like this is either like the greatest thing ever that everyone is missing or like it's not that good. So like I tweeted out if anyone could get me access to it. A few hours later, Greg Brockman responded. Swyx: He is everywhere. Sharif: He's great. Yeah, he's on top of things. And yeah, by that afternoon, I was like messing around with the API and I was like, wow, this is incredible. You could chat with fake people or people that have passed away. You could like, I remember the first conversation I did was this is a chat with Steve Jobs and it was like, interviewer, hi. What are you up to today on Steve? And then like you could talk to Steve Jobs and it was somewhat plausible. Oh, the thing that really blew my mind was I tried to generate code with it. So I'd write the function for a JavaScript header or the header for a JavaScript function. And it would complete the rest of the function. I was like, whoa, does this code actually work? Like I copied it and ran it and it worked. And I tried it again. I gave more complex things and like I kind of understood where it would break, which was like if it was like something, like if it was something you couldn't easily describe in a sentence and like contain all the logic for in a single sentence. So I wanted to build a way where I could visually test whether these functions were actually working. And what I was doing was like I was generating the code in the playground, copying it into my VS code editor, running it and then reloading the react development page. And I was like, okay, cool. That works. So I was like, wait, let me just put this all in like the same page so I can just compile in the browser, run it in the browser and then submit it to the API in the browser as well. So I did that. And it was really just like a simple loop where you just type in the prompt. It would generate the code and then compile it directly in the browser. And it showed you the response. And I did this for like very basic JSX react components. I mean, it worked. It was pretty mind blowing. I remember staying up all night, like working on it. And it was like the coolest thing I'd ever worked on at the time so far. Yeah. And then I was like so mind blowing that no one was talking about this whole GPT three thing. I was like, why is this not on everyone's minds? So I recorded a quick 30 second demo and I posted on Twitter and like I go to bed after staying awake for like 20 hours straight. When I wake up the next morning and I had like 20,000 likes and like 100,000 people had viewed it. I was like, oh, this is so cool. And then I just kept putting demos out for like the next week. And yeah, that was like my GPT three spark moment. Swyx: And you got featured in like Fast Company, MIT Tech Review, you know, a bunch of stuff, right? Sharif: Yeah. Yeah. I think a lot of it was just like the API had been there for like a month prior already. Swyx: Not everyone had access. Sharif: That's true. Not everyone had access. Swyx: So you just had the gumption to tweet it out. And obviously, Greg, you know, on top of things as always. Sharif: Yeah. Yeah. I think it also makes a lot of sense when you kind of share things in a way that's easily consumable for people to understand. Whereas if you had shown a terminal screenshot of a generating code, that'd be pretty compelling. But whereas seeing it get rendered and compiled directly in front of you, there's a lot more interesting. There's also that human aspect to it where you want to relate things to the end user, not just like no one really cares about evals. When you can create a much more compelling demo explaining how it does on certain tasks. [09:00] Stable Diffusion and LexicaSwyx: Okay. We'll round it out soon. But in 2022, you moved from Debuild to Lexica, which was the search engine. I assume this was inspired by stable diffusion, but I can get the history there a little bit. Sharif: Yeah. So I was still working on Debuild. We were growing at like a modest pace and I was in the stable... Swyx: I was on the signup list. I never got off. Sharif: Oh yeah. Well, we'll get you off. It's not getting many updates anymore, but yeah, I was in the stable diffusion discord and I was in it for like many hours a day. It was just like the most exciting thing I'd ever done in a discord. It was so cool. Like people were generating so many images, but I didn't really know how to write prompts and people were like writing really complicated things. They would be like, like a modern home training on our station by Greg Rutkowski, like a 4k Unreal Engine. It's like that there's no way that actually makes the images look better. But everyone was just kind of copying everyone else's prompts and like changing like the first few words. Swyx: Yeah. Yeah. Sharif: So I was like using the discord search bar and it was really bad because it showed like five images at a time. And I was like, you know what? I could build a much better interface for this. So I ended up scraping the entire discord. It was like 10 million images. I put them in a database and I just pretty much built a very basic search engine where you could just type for type a word and then it returned all the prompts that had that word. And I built the entire website for it in like 20, in like about two days. And we shipped it the day I shipped it the day after the stable diffusion weights were open sourced. So about 24 hours later and it kind of took off in a way that I never would have expected. Like I thought it'd be this cool utility that like hardcore stable diffusion users would find useful. But it turns out that almost anyone who mentioned stable diffusion would also kind of mention Lexica in conjunction with it. I think it's because it was like it captured the zeitgeist in an easy to share way where it's like this URL and there's this gallery and you can search. Whereas running the model locally was a lot harder. You'd have to like to deploy it on your own GPU and like set up your own environment and like do all that stuff. Swyx: Oh, my takeaway. I have two more to add to the reasons why Lexica works at the time. One is lower latency is all you need. So in other words, instead of waiting a minute for your image, you could just search and find stuff that other people have done. That's good. And then two is everyone knew how to search already, but people didn't know how to prompt. So you were the bridge. Sharif: That's true. Yeah. You would get a lot better looking images by typing a one word prompt versus prompting for that one word. Yeah. Swyx: Yeah. That is interesting. [11:00] Lexica's Explosion at LaunchAlessio: The numbers kind of speak for themselves, right? Like 24 hours post launch, 51,000 queries, like 2.2 terabytes in bandwidth. Going back to the bandwidth problem that you have before, like you would have definitely run into that. Day two, you doubled that. It's like 111,000 queries, four and a half terabytes in bandwidth, 22 million images served. So it's pretty crazy. Sharif: Yeah. I think we're, we're doing like over 5 billion images served per month now. It's like, yeah, that's, it's pretty crazy how much things have changed since then. Swyx: Yeah. I'm still showing people like today, even today, you know, it's been a few months now. This is where you start to learn image prompting because they don't know. Sharif: Yeah, it is interesting. And I, it's weird because I didn't really think it would be a company. I thought it would just be like a cool utility or like a cool tool that I would use for myself. And I really was just building it for myself just because I didn't want to use the Discord search bar. But yeah, it was interesting that a lot of other people found it pretty useful as well. [11:00] How Lexica WorksSwyx: So there's a lot of things that you release in a short amount of time. The God mode search was kind of like, obviously the first thing, I guess, like maybe to talk about some of the underlying technology you're using clip to kind of find, you know, go from image to like description and then let people search it. Maybe talk a little bit about what it takes to actually make the search magic happen. Sharif: Yeah. So the original search was just using Postgres' full text search and it would only search the text contents of the prompt. But I was inspired by another website called Same Energy, where like a visual search engine. It's really cool. Do you know what happened to that guy? I don't. Swyx: He released it and then he disappeared from the internet. Sharif: I don't know what happened to him, but I'm sure he's working on something really cool. He also worked on like Tabnine, which was like the very first version of Copilot or like even before Copilot was Copilot. But yeah, inspired by that, I thought like being able to search images by their semantics. The contents of the image was really interesting. So I pretty much decided to create a search index on the clip embeddings, the clip image embeddings of all the images. And when you would search it, we would just do KNN search on pretty much the image embedding index. I mean, we had way too many embeddings to store on like a regular database. So we had to end up using FAISS, which is a Facebook library for really fast KNN search and embedding search. That was pretty fun to set up. It actually runs only on CPUs, which is really cool. It's super efficient. You compute the embeddings on GPUs, but like you can serve it all on like an eight core server and it's really, really fast. Once we released the semantic search on the clip embeddings, people were using the search way more. And you could do other cool things. You could do like similar image search where if you found like a specific image you liked, you could upload it and it would show you relevant images as well. Swyx: And then right after that, you raised your seed money from AI grant, NetFreedman, then Gross. Sharif: Yeah, we raised about $5 million from Daniel Gross. And then we also participated in AI grant. That was pretty cool. That was kind of the inflection point. Not much before that point, Lexic was kind of still a side project. And I told myself that I would focus on it full time or I'd consider focusing on it full time if we had broke like a million users. I was like, oh, that's gonna be like years away for sure. And then we ended up doing that in like the first week and a half. I was like, okay, there's something here. And it was kind of that like deal was like growing like pretty slowly and like pretty linearly. And then Lexica was just like this thing that just kept going up and up and up. And I was so confused. I was like, man, people really like looking at pictures. This is crazy. Yeah. And then we decided to pivot the entire company and just focus on Lexica full time at that point. And then we raised our seed round. [15:00] Being Chronically EarlySwyx: Yeah. So one thing that you casually dropped out, the one that slip, you said you were working on Lexica before the launch of Stable Diffusion such that you were able to launch Lexica one day after Stable Diffusion. Sharif: Yeah.Swyx: How did you get so early into Stable Diffusion? Cause I didn't hear about it. Sharif: Oh, that's a good question. I, where did I first hear about Stable Diffusion? I'm not entirely sure. It must've been like somewhere on Twitter or something. That changed your life. Yeah, it was great. And I got into the discord cause I'd used Dolly too before, but, um, there were a lot of restrictions in place where you can generate human faces at the time. You can do that now. But when I first got access to it, like you couldn't do any faces. It was like, there were like a, the list of adjectives you couldn't use was quite long. Like I had a friend from Pakistan and it can generate anything with the word Pakistan in it for some reason. But Stable Diffusion was like kind of the exact opposite where there were like very, very few rules. So that was really, really fun and interesting, especially seeing the chaos of like a bunch of other people also using it right in front of you. That was just so much fun. And I just wanted to do something with it. I thought it was honestly really fun. Swyx: Oh, well, I was just trying to get tips on how to be early on things. Cause you're pretty consistently early to things, right? You were Stadia before Stadia. Um, and then obviously you were on. Sharif: Well, Stadia is kind of shut down now. So I don't know if being early to that was a good one. Swyx: Um, I think like, you know, just being consistently early to things that, uh, you know, have a lot of potential, like one of them is going to work out and you know, then that's how you got Lexica. [16:00] From Search to Custom ModelsAlessio: How did you decide to go from search to running your own models for a generation? Sharif: That's a good question. So we kind of realized that the way people were using Lexica was they would have Lexica open in one tab and then in another tab, they'd have a Stable Diffusion interface. It would be like either a discord or like a local run interface, like the automatic radio UI, um, or something else. I just, I would watch people use it and they would like all tabs back and forth between Lexica and their other UI. And they would like to scroll through Lexica, click on the prompt, click on an image, copy the prompt, and then paste it and maybe change a word or two. And I was like, this should really kind of just be all within Lexica. Like, it'd be so cool if you could just click a button in Lexica and get an editor and generate your images. And I found myself also doing the all tab thing, or it was really frustrating. I was like, man, this is kind of tedious. Like I really wish it was much simpler. So we just built generations directly within Lexica. Um, so we do, we deployed it on, I don't remember when we first launched, I think it was November, December. And yeah, people love generating directly within it. [17:00] AI Grant LearningsSwyx: I was also thinking that this was coming out of AI grants where, you know, I think, um, yeah, I was like a very special program. I was just wondering if you learned anything from, you know, that special week where everyone was in town. Sharif: Yeah, that was a great week. I loved it. Swyx: Yeah. Bring us, bring us in a little bit. Cause it was awesome. There. Sharif: Oh, sure. Yeah. It's really, really cool. Like all the founders in AI grants are like fantastic people. And so I think the main takeaway from the AI grant was like, you have this massive overhang in compute or in capabilities in terms of like these latest AI models, but to the average person, there's really not that many products that are that cool or useful to them. Like the latest one that has hit the zeitgeist was chat GPT, which used arguably the same GPT three model, but like RLHF, but you could have arguably built like a decent chat GPT product just using the original GPT three model. But no one really did it. Now there were some restrictions in place and opening. I like to slowly release them over the few months or years after they release the original API. But the core premise behind AI grants is that there are way more capabilities than there are products. So focus on building really compelling products and get people to use them. And like to focus less on things like hitting state of the art on evals and more on getting users to use something. Swyx: Make something people want.Sharif: Exactly. Host: Yeah, we did an episode on LLM benchmarks and we kind of talked about how the benchmarks kind of constrain what people work on, because if your model is not going to do well, unlike the well-known benchmarks, it's not going to get as much interest and like funding. So going at it from a product lens is cool. [19:30] The Text to Image Illuminati?Swyx: My hypothesis when I was seeing the sequence of events for AI grants and then for Lexica Aperture was that you had some kind of magical dinner with Emad and David Holtz. And then they taught you the secrets of training your own model. Is that how it happens? Sharif: No, there's no secret dinner. The Illuminati of text to image. We did not have a meeting. I mean, even if we did, I wouldn't tell you. But it really boils down to just having good data. If you think about diffusion models, really the only thing they do is learn a distribution of data. So if you have high quality data, learn that high quality distribution. Or if you have low quality data, it will learn to generate images that look like they're from that distribution. So really it boils down to the data and the amount of data you have and that quality of that data, which means a lot of the work in training high quality models, at least diffusion models, is not really in the model architecture, but rather just filtering the data in a way that makes sense. So for Lexica, we do a lot of aesthetic scoring on images and we use the rankings we get from our website because we get tens of millions of people visiting it every month. So we can capture a lot of rankings. Oh, this person liked this image when they saw this one right next to it. Therefore, they probably preferred this one over that. You can do pairwise ranking to rank images and then compute like ELO scores. You can also just train aesthetic models to learn to classify a model, whether or not someone will like it or whether or not it's like, rank it on a scale of like one to ten, for example. So we mostly use a lot of the traffic we get from Lexica and use that to kind of filter our data sets and use that to train better aesthetic models. [20:30] How to Learn to Train ModelsSwyx: You had been a machine learning engineer before. You've been more of an infrastructure guy. To build, you were more of a prompt engineer with a bit of web design. This was the first time that you were basically training your own model. What was the wrap up like? You know, not to give away any secret sauce, but I think a lot of people who are traditional software engineers are feeling a lot of, I don't know, fear when encountering these kinds of domains. Sharif: Yeah, I think it makes a lot of sense. And to be fair, I didn't have much experience training massive models at this scale before I did it. A lot of times it's really just like, in the same way when you're first learning to program, you would just take the problem you're having, Google it, and go through the stack overflow post. And then you figure it out, but ultimately you will get to the answer. It might take you a lot longer than someone who's experienced, but I think there are enough resources out there where it's possible to learn how to do these things. Either just reading through GitHub issues for relevant models. Swyx: Oh God. Sharif: Yeah. It's really just like, you might be slower, but it's definitely still possible. And there are really great courses out there. The Fast AI course is fantastic. There's the deep learning book, which is great for fundamentals. And then Andrej Karpathy's online courses are also excellent, especially for language modeling. You might be a bit slower for the first few months, but ultimately I think if you have the programming skills, you'll catch up pretty quickly. It's not like this magical dark science that only three people in the world know how to do well. Probably was like 10 years ago, but now it's becoming much more open. You have open source collectives like Eleuther and LAION, where they like to share the details of their large scale training runs. So you can learn from a lot of those people. Swyx: Yeah. I think what is different for programmers is having to estimate significant costs upfront before they hit run. Because it's not a thing that you normally consider when you're coding, but yeah, like burning through your credits is a fear that people have. Sharif: Yeah, that does make sense. In that case, like fine tuning larger models gets you really, really far. Even using things like low rank adaptation to fine tune, where you can like fine tune much more efficiently on a single GPU. Yeah, I think people are underestimating how far you can really get just using open source models. I mean, before Lexica, I was working on Debuild and we were using the GP3 API, but I was also like really impressed at how well you could get open source models to run by just like using the API, collecting enough samples from like real world user feedback or real world user data using your product. And then just fine tuning the smaller open source models on those examples. And now you have a model that's pretty much state of the art for your specific domain. Whereas the runtime cost is like 10 times or even 100 times cheaper than using an API. Swyx: And was that like GPT-J or are you talking BERT? Sharif: I remember we tried GPT-J, but I think FLAN-T5 was like the best model we were able to use for that use case. FLAN-T5 is awesome. If you can, like if your prompt is small enough, it's pretty great. And I'm sure there are much better open source models now. Like Vicuna, which is like the GPT-4 variant of like Lama fine tuned on like GPT-4 outputs. Yeah, they're just going to get better and they're going to get better much, much faster. Swyx: Yeah. We're just talking in a previous episode to the creator of Dolly, Mike Conover, which is actually commercially usable instead of Vicuna, which is a research project. Sharif: Oh, wow. Yeah, that's pretty cool. [24:00] Why No Agents?Alessio: I know you mentioned being early. Obviously, agents are one of the hot things here. In 2021, you had this, please buy me AirPods, like a demo that you tweeted with the GPT-3 API. Obviously, one of the things about being early in this space, you can only do one thing at a time, right? And you had one tweet recently where you said you hoped that that demo would open Pandora's box for a bunch of weird GPT agents. But all we got were docs powered by GPT. Can you maybe talk a little bit about, you know, things that you wish you would see or, you know, in the last few, last few weeks, we've had, you know, Hugging GPT, Baby AGI, Auto GPT, all these different kind of like agent projects that maybe now are getting closer to the, what did you say, 50% of internet traffic being skips of GPT agents. What are you most excited about, about these projects and what's coming? Sharif: Yeah, so we wanted a way for users to be able to paste in a link for the documentation page for a specific API, and then describe how to call that API. And then the way we would need to pretty much do that for Debuild was we wondered if we could get an agent to browse the docs page, read through it, summarize it, and then maybe even do things like create an API key and register it for that user. To do that, we needed a way for the agent to read the web page and interact with it. So I spent about a day working on that demo where we just took the web page, serialized it into a more compact form that fit within the 2048 token limit of like GPT-3 at the time. And then just decide what action to do. And then it would, if the page was too long, it would break it down into chunks. And then you would have like a sub prompt, decide on which chunk had the best action. And then at the top node, you would just pretty much take that action and then run it in a loop. It was really, really expensive. I think that one 60 second demo cost like a hundred bucks or something, but it was wildly impractical. But you could clearly see that agents were going to be a thing, especially ones that could read and write and take actions on the internet. It was just prohibitively expensive at the time. And the context limit was way too small. But yeah, I think it seems like a lot of people are taking it more seriously now, mostly because GPT-4 is way more capable. The context limit's like four times larger at 8,000 tokens, soon 32,000. And I think the only problem that's left to solve is finding a really good representation for a webpage that allows it to be consumed by a text only model. So some examples are like, you could just take all the text and pass it in, but that's probably too long. You could take all the interactive only elements like buttons and inputs, but then you miss a lot of the relevant context. There are some interesting examples, which I really like is you could run the webpage or you could run the browser in a terminal based browser. So there are some browsers that run in your terminal, which serialize everything into text. And what you can do is just take that frame from that terminal based browser and pass that directly to the model. And it's like a really, really good representation of the webpage because they do things where for graphical elements, they kind of render it using ASCII blocks. But for text, they render it as actual text. So you could just remove all the weird graphical elements, just keep all the text. And that works surprisingly well. And then there are other problems to solve, which is how do you get the model to take an action? So for example, if you have a booking page and there's like a calendar and there are 30 days on the calendar, how do you get it to specify which button to press? It could say 30, and you can match string based and like find the 30. But for example, what if it's like a list of friends in Facebook and trying to delete a friend? There might be like 30 delete buttons. How do you specify which one to click on? The model might say like, oh, click on the one for like Mark. But then you'd have to figure out the delete button in relation to Mark. And there are some ways to solve this. One is there's a cool Chrome extension called Vimium, which lets you use Vim in your Chrome browser. And what you do is you can press F and over every interactive element, it gives you like a character or two characters. Or if you type those two characters, it presses that button or it opens or focuses on that input. So you could combine a lot of these ideas and then get a really good representation of the web browser in text, and then also give the model a really, really good way to control the browser as well. And I think those two are the core part of the problem. The reasoning ability is definitely there. If a model can score in the top 10% on the bar exam, it can definitely browse a web page. It's really just how do you represent text to the model and how do you get the model to perform actions back on the web page? Really, it's just an engineering problem. Swyx: I have one doubt, which I'd love your thoughts on. How do you get the model to pause when it doesn't have enough information and ask you for additional information because you under specified your original request? Sharif: This is interesting. I think the only way to do this is to have a corpus where your training data is like these sessions of agents browsing the web. And you have to pretty much figure out where the ones that went wrong or the agents that went wrong, or did they go wrong and just replace it with, hey, I need some help. And then if you were to fine tune a larger model on that data set, you would pretty much get them to say, hey, I need help on the instances where they didn't know what to do next. Or if you're using a closed source model like GPT-4, you could probably tell it if you're uncertain about what to do next, ask the user for help. And it probably would be pretty good at that. I've had to write a lot of integration tests in my engineering days and like the dome. Alessio: They might be over. Yeah, I hope so. I hope so. I don't want to, I don't want to deal with that anymore. I, yeah, I don't want to write them the old way. Yeah. But I'm just thinking like, you know, we had the robots, the TXT for like crawlers. Like I can definitely see the DOM being reshaped a little bit in terms of accessibility. Like sometimes you have to write expats that are like so long just to get to a button. Like there should be a better way to do it. And maybe this will drive the change, you know, making it easier for these models to interact with your website. Sharif: There is the Chrome accessibility tree, which is used by screen readers, but a lot of times it's missing a lot of, a lot of useful information. But like in a perfect world, everything would be perfectly annotated for screen readers and we could just use that. That's not the case. [29:30] GPT4 and MultimodalitySwyx: GPT-4 multimodal, has your buddy, Greg, and do you think that that would solve essentially browser agents or desktop agents? Sharif: Greg has not come through yet, unfortunately. But it would make things a lot easier, especially for graphically heavy web pages. So for example, you were using Yelp and like using the map view, it would make a lot of sense to use something like that versus a text based input. Where, how do you serialize a map into text? It's kind of hard to do that. So for more complex web pages, that would make it a lot easier. You get a lot more context to the model. I mean, it seems like that multimodal input is very dense in the sense that it can read text and it can read it really, really well. So you could probably give it like a PDF and it would be able to extract all the text and summarize it. So if it can do that, it could probably do anything on any webpage. Swyx: Yeah. And given that you have some experience integrating Clip with language models, how would you describe how different GPT-4 is compared to that stuff? Sharif: Yeah. Clip is entirely different in the sense that it's really just good at putting images and text into the same latent space. And really the only thing that's useful for is similarity and clustering. Swyx: Like literally the same energy, right? Sharif: Yeah. Swyx: Yeah. And then there's Blip and Blip2. I don't know if you like those. Sharif: Yeah. Blip2 is a lot better. There's actually a new project called, I think, Mini GPT-4. Swyx: Yes. It was just out today. Sharif: Oh, nice. Yeah. It's really cool. It's actually really good. I think that one is based on the Lama model, but yeah, that's, that's like another. Host: It's Blip plus Lama, right? So they, they're like running through Blip and then have Lama ask your, interpret your questions so that you do visual QA. Sharif: Oh, that's cool. That's really clever. Yeah. Ensemble models are really useful. Host: Well, so I was trying to articulate, cause that was, that's, there's two things people are talking about today. You have to like, you know, the moment you wake up, you open Hacker News and go like, all right, what's, what's the new thing today? One is Red Pajama. And then the other one is Mini GPT-4. So I was trying to articulate like, why is this not GPT-4? Like what is missing? And my only conclusion was it just doesn't do OCR yet. But I wonder if there's anything core to this concept of multimodality that you have to train these things together. Like what does one model doing all these things do that is separate from an ensemble of models that you just kind of duct tape together? Sharif: It's a good question. This is pretty related to interoperability. Like how do we understand that? Or how, how do we, why do models trained on different modalities within the same model perform better than two models perform or train separately? I can kind of see why that is the case. Like, it's kind of hard to articulate, but when you have two different models, you get the reasoning abilities of a language model, but also like the text or the vision understanding of something like Clip. Whereas Clip clearly lacks the reasoning abilities, but if you could somehow just put them both in the same model, you get the best of both worlds. There were even cases where I think the vision version of GPT-4 scored higher on some tests than the text only version. So like there might even be some additional learning from images as well. Swyx: Oh yeah. Well, uh, the easy answer for that was there was some chart in the test. That wasn't translated. Oh, when I read that, I was like, Oh yeah. Okay. That makes sense. Sharif: That makes sense. I thought it'd just be like, it sees more of the world. Therefore it has more tokens. Swyx: So my equivalent of this is I think it's a well-known fact that adding code to a language model training corpus increases its ability to do language, not just with code. So, the diversity of datasets that represent some kind of internal logic and code is obviously very internally logically consistent, helps the language model learn some internal structure. Which I think, so, you know, my ultimate test for GPT-4 is to show the image of like, you know, is this a pipe and ask it if it's a pipe or not and see what it does. Sharif: Interesting. That is pretty cool. Yeah. Or just give it a screenshot of your like VS code editor and ask it to fix the bug. Yeah. That'd be pretty wild if it could do that. Swyx: That would be adult AGI. That would be, that would be the grownup form of AGI. [33:30] Sharif's Startup ManualSwyx: On your website, you have this, um, startup manual where you give a bunch of advice. This is fun. One of them was that you should be shipping to production like every two days, every other day. This seems like a great time to do it because things change every other day. But maybe, yeah, tell some of our listeners a little bit more about how you got to some of these heuristics and you obviously build different projects and you iterate it on a lot of things. Yeah. Do you want to reference this? Sharif: Um, sure. Yeah, I'll take a look at it. Swyx: And we'll put this in the show notes, but I just wanted you to have the opportunity to riff on this, this list, because I think it's a very good list. And what, which one of them helped you for Lexica, if there's anything, anything interesting. Sharif: So this list is, it's pretty funny. It's mostly just like me yelling at myself based on all the mistakes I've made in the past and me trying to not make them again. Yeah. Yeah. So I, the first one is like, I think the most important one is like, try when you're building a product, try to build the smallest possible version. And I mean, for Lexica, it was literally a, literally one screen in the react app where a post-process database, and it just showed you like images. And I don't even know if the first version had search. Like I think it did, but I'm not sure. Like, I think it was really just like a grid of images that were randomized, but yeah, don't build the absolute smallest thing that can be considered a useful application and ship it for Lexica. That was, it helps me write better prompts. That's pretty useful. It's not that useful, but it's good enough. Don't fall into the trap of intellectual indulgence with over-engineering. I think that's a pretty important one for myself. And also anyone working on new things, there's often times you fall into the trap of like thinking you need to add more and more things when in reality, like the moment it's useful, you should probably get in the hands of your users and they'll kind of set the roadmap for you. I know this has been said millions of times prior, but just, I think it's really, really important. And I think if I'd spent like two months working on Lexica, adding a bunch of features, it wouldn't have been anywhere as popular as it was if I had just released the really, really boiled down version alongside the stable diffusion release. Yeah. And then there are a few more like product development doesn't start until you launch. Think of your initial product as a means to get your users to talk to you. It's also related to the first point where you really just want people using something as quickly as you can get that to happen. And then a few more are pretty interesting. Create a product people love before you focus on growth. If your users are spontaneously telling other people to use your product, then you've built something people love. Swyx: So this is pretty, it sounds like you've internalized Paul Graham's stuff a lot. Yeah. Because I think he said stuff like that. Sharif: A lot of these are just probably me taking notes from books I found really interesting or like PG essays that were really relevant at the time. And then just trying to not forget them. I should probably read this list again. There's some pretty personalized advice for me here. Oh yeah. One of my favorite ones is, um, don't worry if what you're building doesn't sound like a business. Nobody thought Facebook would be a $500 billion company. It's easy to come up with a business model. Once you've made something people want, you can even make pretty web forms and turn that into a 200 person company. And then if you click the link, it's to LinkedIn for type form, which is now, uh, I think they're like an 800 person company or something like that. So they've grown quite a bit. There you go. Yeah. Pretty web forms are pretty good business, even though it doesn't sound like it. Yeah. It's worth a billion dollars. [38:30] Lexica Aperture V1/2/3Swyx: One way I would like to tie that to the history of Lexica, which we didn't go over, which was just walk us through like Aperture V1, V2, V3, uh, which you just released last week. And how maybe some of those principles helped you in that journey.Sharif: Yeah. So, um, V1 was us trying to create a very photorealistic version of our model of Sable to Fusion. Uh, V1 actually didn't turn out to be that popular. It turns out people loved not generating. Your marketing tweets were popular. They were quite popular. So I think at the time you couldn't get Sable to Fusion to generate like photorealistic images that were consistent with your prompt that well. It was more so like you were sampling from this distribution of images and you could slightly pick where you sampled from using your prompt. This was mostly just because the clip text encoder is not the best text encoder. If you use a real language model, like T5, you get much better results. Like the T5 XXL model is like a hundred times larger than the clip text encoder for Sable to Fusion 1.5. So you could kind of steer it into like the general direction, but for more complex prompts, it just didn't work. So a lot of our users actually complained that they preferred the 1.5, Sable to Fusion 1.5 model over the Aperture model. And it was just because a lot of people were using it to create like parts and like really weird abstract looking pictures that didn't really work well with the photorealistic model trained solely on images. And then for V2, we kind of took that into consideration and then just trained it more on a lot of the art images on Lexica. So we took a lot of images that were on Lexica that were art, used that to train aesthetic models that ranked art really well, and then filtered larger sets to train V2. And then V3 is kind of just like an improved version of that with much more data. I'm really glad we didn't spend too much time on V1. I think we spent about one month working on it, which is a lot of time, but a lot of the things we learned were useful for training future versions. Swyx: How do you version them? Like where do you decide, okay, this is V2, this is V3? Sharif: The versions are kind of weird where you can't really use semantic versions because like if you have a small update, you usually just make that like V2. Versions are kind of used for different base models, I'd say. So if you have each of the versions were a different base model, but we've done like fine tunes of the same version and then just release an update without incrementing the version. But I think when there's like a clear change between running the same prompt on a model and you get a different image, that should probably be a different version. [40:00] Request for AI Startup - LLM ToolsAlessio: So the startup manual was the more you can actually do these things today to make it better. And then you have a whole future page that has tips from, you know, what the series successor is going to be like to like why everyone's genome should be sequenced. There's a lot of cool stuff in there. Why do we need to develop stimulants with shorter half-lives so that we can sleep better. Maybe talk a bit about, you know, when you're a founder, you need to be focused, right? So sometimes there's a lot of things you cannot build. And I feel like this page is a bit of a collection of these. Like, yeah. Are there any of these things that you're like, if I were not building Lexica today, this is like a very interesting thing. Sharif: Oh man. Yeah. There's a ton of things that I want to build. I mean, off the top of my head, the most exciting one would be better tools for language models. And I mean, not tools that help us use language models, but rather tools for the language models themselves. So things like giving them access to browsers, giving them access to things like payments and credit cards, giving them access to like credit cards, giving them things like access to like real world robots. So like, it'd be cool if you could have a Boston dynamic spot powered by a language model reasoning module and you would like to do things for you, like go and pick up your order, stuff like that. Entirely autonomously given like high level commands. That'd be like number one thing if I wasn't working on Lexica. [40:00] Sequencing your GenomeAnd then there's some other interesting things like genomics I find really cool. Like there's some pretty cool things you can do with consumer genomics. So you can export your genome from 23andMe as a text file, like literally a text file of your entire genome. And there is another tool called Prometheus, I think, where you upload your 23andMe text file genome and then they kind of map specific SNPs that you have in your genome to studies that have been done on those SNPs. And it tells you really, really useful things about yourself. Like, for example, I have the SNP for this thing called delayed sleep phase disorder, which makes me go to sleep about three hours later than the general population. So like I used to always be a night owl and I never knew why. But after using Prometheus it pretty much tells you, oh, you have the specific genome for specific SNP for DSPS. It's like a really tiny percentage of the population. And it's like something you should probably know about. And there's a bunch of other things. It tells you your likelihood for getting certain diseases, for certain cancers, oftentimes, like even weird personality traits. There's one for like, I have one of the SNPs for increased risk taking and optimism, which is pretty weird. That's an actual thing. Like, I don't know how. This is the founder gene. You should sequence everybody. It's pretty cool. And it's like, it's like $10 for Prometheus and like 70 bucks for 23andMe. And it explains to you how your body works and like the things that are different from you or different from the general population. Wow. Highly recommend everyone do it. Like if you're, if you're concerned about privacy, just purchase a 23andMe kit with a fake name. You don't have to use your real name. I didn't use my real name. Swyx: It's just my genes. Worst you can do is clone me. It ties in with what you were talking about with, you know, we want the future to be like this. And like people are building uninspired B2B SaaS apps and you and I had an exchange about this. [42:00] Believe in Doing Great ThingsHow can we get more people to believe they can do great things? Sharif: That's a good question. And I like a lot of the things I've been working on with GP3. It has been like trying to solve this by getting people to think about more interesting ideas. I don't really know. I think one is just like the low effort version of this is just putting out really compelling demos and getting people inspired. And then the higher effort version is like actually building the products yourself and getting people to like realize this is even possible in the first place. Like I think the baby AGI project and like the GPT Asian projects on GitHub are like in practice today, they're not super useful, but I think they're doing an excellent job of getting people incredibly inspired for what can be possible with language models as agents. And also the Stanford paper where they had like the mini version of Sims. Yeah. That one was incredible. That was awesome. Swyx: It was adorable. Did you see the part where they invented day drinking? Sharif: Oh, they did? Swyx: Yeah. You're not supposed to go to these bars in the afternoon, but they were like, we're going to go anyway. Nice. Sharif: That's awesome. Yeah. I think we need more stuff like that. That one paper is probably going to inspire a whole bunch of teams to work on stuff similar to that. Swyx: And that's great. I can't wait for NPCs to actually be something that you talk to in a game and, you know, have their own lives and you can check in and, you know, they would have their own personalities as well. Sharif: Yeah. I was so kind of off topic. But I was playing the last of us part two and the NPCs in that game are really, really good. Where if you like, point a gun at them and they'll beg for their life and like, please, I have a family. And like when you kill people in the game, they're like, oh my God, you shot Alice. Like they're just NPCs, but they refer to each other by their names and like they plead for their lives. And this is just using regular conditional rules on NPC behavior. Imagine how much better it'd be if it was like a small GPT-4 agent running in every NPC and they had the agency to make decisions and plead for their lives. And I don't know, you feel way more guilty playing that game. Alessio: I'm scared it's going to be too good. I played a lot of hours of Fallout. So I feel like if the NPCs were a lot better, you would spend a lot more time playing the game. Yeah. [44:30] Lightning RoundLet's jump into lightning round. First question is your favorite AI product. Sharif: Favorite AI product. The one I use the most is probably ChatGPT. The one I'm most excited about is, it's actually a company in AI grants. They're working on a version of VS code. That's like an entirely AI powered cursor, yeah. Cursor where you would like to give it a prompt and like to iterate on your code, not by writing code, but rather by just describing the changes you want to make. And it's tightly integrated into the editor itself. So it's not just another plugin. Swyx: Would you, as a founder of a low code prompting-to-code company that pivoted, would you advise them to explore some things or stay away from some things? Like what's your learning there that you would give to them?Sharif: I would focus on one specific type of code. So if I'm building a local tool, I would try to not focus too much on appealing developers. Whereas if I was building an alternative to VS code, I would focus solely on developers. So in that, I think they're doing a pretty good job focusing on developers. Swyx: Are you using Cursor right now? Sharif: I've used it a bit. I haven't converted fully, but I really want to. Okay. It's getting better really, really fast. Yeah. Um, I can see myself switching over sometime this year if they continue improving it. Swyx: Hot tip for, for ChatGPT, people always say, you know, they love ChatGPT. Biggest upgrade to my life right now is the, I forked a menu bar app I found on GitHub and now I just have it running in a menu bar app and I just do command shift G and it pops it up as a single use thing. And there's no latency because it just always is live. And I just type, type in the thing I want and then it just goes away after I'm done. Sharif: Wow. That's cool. Big upgrade. I'm going to install that. That's cool. Alessio: Second question. What is something you thought would take much longer, but it's already here? Like what, what's your acceleration update? Sharif: Ooh, um, it would take much longer, but it's already here. This is your question. Yeah, I know. I wasn't prepared. Um, so I think it would probably be kind of, I would say text to video. Swyx: Yeah. What's going on with that? Sharif: I think within this year, uh, by the end of this year, we'll have like the jump between like the original DALL-E one to like something like mid journey. Like we're going to see that leap in text to video within the span of this year. Um, it's not already here yet. So I guess the thing that surprised me the most was probably the multi-modality of GPT four in the fact that it can technically see things, which is pretty insane. Swyx: Yeah. Is text to video something that Aperture would be interested in? Sharif: Uh, it's something we're thinking about, but it's still pretty early. Swyx: There was one project with a hand, um, animation with human poses. It was also coming out of Facebook. I thought that was a very nice way to accomplish text to video while having a high degree of control. I forget the name of that project. It was like, I think it was like drawing anything. Swyx: Yeah. It sounds familiar. Well, you already answered a year from now. What will people be most surprised by? Um, and maybe the, uh, the usual requests for startup, you know, what's one thing you will pay for if someone built it? Sharif: One thing I would pay for if someone built it. Um, so many things, honestly, I would probably really like, um, like I really want people to build more, uh, tools for language models, like useful tools, give them access to Chrome. And I want to be able to give it a task. And then just, it goes off and spins up a hundred agents that perform that task. And like, sure. Like 80 of them might fail, but like 20 of them might kind of succeed. That's all you really need. And they're agents. You can spin up thousands of them. It doesn't really matter. Like a lot of large numbers are on your side. So that'd be, I would pay a lot of money for that. Even if it was capable of only doing really basic tasks, like signing up for a SAS tool and booking a call or something. If you could do even more things where it could have handled the email, uh, thread and like get the person on the other end to like do something where like, I don't even have to like book the demo. They just give me access to it. That'd be great. Yeah. More, more. Like really weird language model tools would be really fun.Swyx: Like our chat, GPT plugins, a step in the right direction, or are you envisioning something else? Sharif: I think GPT, chat GPT plugins are great, but they seem to only have right-only access right now. I also want them to have, I want these like theoretical agents to have right access to the world too. So they should be able to perform actions on web browsers, have their own email inbox, and have their own credit card with their own balance. Like take it, send emails to people that might be useful in achieving their goal. Ask them for help. Be able to like sign up and register for accounts on tools and services and be able to like to use graphical user interfaces really, really well. And also like to phone home if they need help. Swyx: You just had virtual employees. You want to give them a Brex card, right? Sharif: I wouldn't be surprised if, a year from now there was Brex GPT or it's like Brex cards for your GPT agents. Swyx: I mean, okay. I'm excited by this. Yeah. Kind of want to build it. Sharif: You should. Yeah. Alessio: Well, just to wrap up, we always have like one big takeaway for people, like, you know, to display on a signboard for everyone to see what is the big message to everybody. Sharif: Yeah. I think the big message to everybody is you might think that a lot of the time the ideas you have have already been done by someone. And that may be the case, but a lot of the time the ideas you have are actually pretty unique and no one's ever tried them before. So if you have weird and interesting ideas, you should actually go out and just do them and make the thing and then share that with the world. Cause I feel like we need more people building weird ideas and less people building like better GPT search for your documentation. Host: There are like 10 of those in the recent OST patch. Well, thank you so much. You've been hugely inspiring and excited to see where Lexica goes next. Sharif: Appreciate it. Thanks for having me. Get full access to Latent Space at www.latent.space/subscribe

Welcome back to another episode of Chasing the Apex, today I'm sitting down with IndyCar driver Devlin DeFrancesco. Devlin first got into a go-kart at the age of 6 and quickly became a competitive young driver, racing in several karting series in the United States, Canada, and Italy. After graduating from karts Devlin spent a year in the Italian and British F4 championships before coming 3rd in the 2017 Euroformula Championship and winning the Spanish F3 series. Devlin then spent time in the GP3 and FIA F3 series before coming back to the states and placing 2nd in the 2020 Indy Pro championship. From there, he joined the Andretti family, spending one year in the Indy Lights series before entering his rookie IndyCar season with Andretti Steinbrenner Racing in 2022. Social Media Links: https://linktr.ee/chasingtheapex

The Christmas edition of Speed Street is here as Conor Daly and Joey Mulinaro wrap up the last episode of 2022. Conor shares stories from his trip to Ireland, then, the guys break down IndyCar's new documentary series for the 2023 Indy 500, iRacing and IndyCar not renewing their contract, and give their podium for the best Christmas desserts and movies. Finally, Conor talks with former Red Bull junior driver and Formula E champion Antonio Felix da Costa about racing against him in GP3, falling short of an F1 ride, and turning down two IndyCar ride opportunities. Follow @SpeedStreetpod and @Dirtymomedia on Instagram and Twitter. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

The Christmas edition of Speed Street is here as Conor Daly and Joey Mulinaro wrap up the last episode of 2022. Conor shares stories from his trip to Ireland, then, the guys break down IndyCar's new documentary series for the 2023 Indy 500, iRacing and IndyCar not renewing their contract, and give their podium for the best Christmas desserts and movies. Finally, Conor talks with former Red Bull junior driver and Formula E champion Antonio Felix da Costa about racing against him in GP3, falling short of an F1 ride, and turning down two IndyCar ride opportunities.  Follow @SpeedStreetpod and @Dirtymomedia on Instagram and Twitter. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

In episode 19 of Complacency Kills - A Kontek Podcast, Michael Witt and Matt Scott sit down and have a chat on weapons ports, their utility, and where they think weapons ports could be put to use in different markets. Topics include: - Definition of weapons ports - Types of weapons ports (GP1 to GP3 - M) - Recommendations for nuclear security, law enforcement, and military Kontek Industries specializes in gun ports and weapons system solutions for DOD, nuclear facilities, law enforcement, and a wide range of other organizations. Our custom fabricated enclosures are designed to protect your staff from attacks while providing a clear field of vision for counterattacks. The GP1 enhanced sliding door weapons port engagement system gives operators industry standard ballistics and blast protection while providing enhanced fields of view and fields of fire when compared to other weapons ports. The GP2 is Kontek's hands free flush mounted weather resistant construction that helps prevent the intrusion of water, wind, and debris. The GP3 turret weapons port includes a ball module that provides complete protection to operators while allowing them to return fire from cover. The GP3-M turret-port weapon engagement system also provides industry-leading ballistic and blast protection and can be integrated into guard booths, barricades, walls, doors, windows, and armored vehicles.

Tatiana Calderon is the first female driver to campaign for the A.J. Foyt Racing Team in its 56-year history. She brings a tremendous amount of experience into the cockpit. She's been a test driver for the Alfa Romeo F1 Team for the last four years and has also raced in British and European F3, F2, GP3 and Renault Series Formula V8 3.5 where she became the first female to stand on the podium in 2017. In the two seasons prior to this year, she honed her craft in the Super Formula Series in Japan, as well as the World Endurance Championship. The plan for 2022 has been to compete in all of the road and street courses in the NTT IndyCar Series for Foyt. In this interview she talks about how the different classes of cars she's raced compare to each other and how she prepares for her races. Enjoy! NOTE: Just over halfway through the season, a sponsor issue saw Calderon sidelined. Hopefully she can return to her seat, if not this year, then next year. . . By Larry Mason Copyright © 2022 Larry Mason

As drivers follow their trajectory through motorsports, they are often faced with potentially life-changing decisions. On episode 397 of the Dale Jr. Download, Indycar talent Conor Daly joins Dale Earnhardt Jr. and co-host Mike Davis to discuss a crossroads he faced and how his choice affected his career path. After winning the Star Mazda Championship in 2010 and securing a hefty scholarship fund to invest in his future racing endeavors, Daly had to make the selection of a lifetime: pursue Formula One or Indycar?  Son of former Formula One driver Derek Daly and Indianapolis Motor Speedway employee Beth Boles, Conor was no stranger to auto racing. In fact, he begins by saying that he has hardly any early-life memories that don't involve racing. He recalled his time spent at the Racing Babies childcare facility at IMS and his early infatuation with the sport. He also spoke of his father's racing career, which ended when he was born in 1991, and how he has been able to uncover more of his accomplishments through the digital age. Up to that point in 2010, Conor had rapidly progressed up the opening rungs of the motorsports ladder. From his first time behind the wheel of a go-kart at age 10 to winning the 2006 World Karting Association Grand Nationals, he and his father Derek worked tirelessly on his burgeoning career. From karts, he took on car racing through the Skip Barber National Championship, which he won in his first year in 2008. Then came the Star Mazda circuit, which of course brings the story to that crossroads at the end of the 2010 season. A stipulation of Conor's scholarship and the Road to Indy program was that while he could take part of the money and pursue GP3 racing in Europe, he still needed to enter a handful of Indy Lights events. After the first three events of the schedule, competing for Sam Schmidt Motorsports, Conor found himself with a 2nd place finish and a victory and leading the season points. His prospects in the world of Indycar were so high, that he revealed he actually got a call from Graham Rahal as he was about to depart for Europe, asking him, “are you sure you want to do this?” Ultimately, Conor left the United States and departed for England, where he'd stay with Rahal's stepfather Chris Berry and set up a home base for his time spent racing in GP3. Daly explained that in his debut GP3 race he qualified 29th and was immediately hit with the regret of his decision. In his absence in the Indy Lights series, Josef Newgarden would go on to win the championship and sign a three-year contract with Sarah Fisher Hartman Racing. And while Daly would wind up inking a deal with the Force India Formula One team that would have him serve as a test and reserve driver, his time overseas would prove unfruitful, and he returned home to pursue a path in Indycar. Conor and Dale Jr. discuss Europe's perspective on American racers and theorize as to why it is difficult for them to break into the Formula racing ladder. After returning home, Daly did whatever he could to be at the tracks on race weekends, even at one point driving the Indycar two-seater for fan experiences. His perseverance would eventually win out, as he rose from filling in for injured drivers to racing part-time and now full-time for Ed Carpenter Racing. Daly took time to speak on the ascension from spending his childhood at IMS to racing in the Indianapolis 500. Just this past May in the 106th running of the “Greatest Spectacle in Racing”, the hometown hero brought home his best finish to date, sixth place. DIRTY AIRBefore Conor joins the show, Dale, Mike, Alex, and Hannah chat about: Kelley's birthday bash Long weekend in Daytona The great Cup race rain debacle  Kurt Busch's injury progress ASKJR presented by XfinityThis week the fans asked questions about: Strangest excuse to explain a crash Feelings on Greg Ives' leaving as crew chief Updates on his ongoing car projects Championship Four predictions To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

As drivers follow their trajectory through motorsports, they are often faced with potentially life-changing decisions. On episode 397 of the Dale Jr. Download, Indycar talent Conor Daly joins Dale Earnhardt Jr. and co-host Mike Davis to discuss a crossroads he faced and how his choice affected his career path. After winning the Star Mazda Championship in 2010 and securing a hefty scholarship fund to invest in his future racing endeavors, Daly had to make the selection of a lifetime: pursue Formula One or Indycar?   Son of former Formula One driver Derek Daly and Indianapolis Motor Speedway employee Beth Boles, Conor was no stranger to auto racing. In fact, he begins by saying that he has hardly any early-life memories that don't involve racing. He recalled his time spent at the Racing Babies childcare facility at IMS and his early infatuation with the sport. He also spoke of his father's racing career, which ended when he was born in 1991, and how he has been able to uncover more of his accomplishments through the digital age.  Up to that point in 2010, Conor had rapidly progressed up the opening rungs of the motorsports ladder. From his first time behind the wheel of a go-kart at age 10 to winning the 2006 World Karting Association Grand Nationals, he and his father Derek worked tirelessly on his burgeoning career. From karts, he took on car racing through the Skip Barber National Championship, which he won in his first year in 2008. Then came the Star Mazda circuit, which of course brings the story to that crossroads at the end of the 2010 season.  A stipulation of Conor's scholarship and the Road to Indy program was that while he could take part of the money and pursue GP3 racing in Europe, he still needed to enter a handful of Indy Lights events. After the first three events of the schedule, competing for Sam Schmidt Motorsports, Conor found himself with a 2nd place finish and a victory and leading the season points. His prospects in the world of Indycar were so high, that he revealed he actually got a call from Graham Rahal as he was about to depart for Europe, asking him, “are you sure you want to do this?”  Ultimately, Conor left the United States and departed for England, where he'd stay with Rahal's stepfather Chris Berry and set up a home base for his time spent racing in GP3. Daly explained that in his debut GP3 race he qualified 29th and was immediately hit with the regret of his decision. In his absence in the Indy Lights series, Josef Newgarden would go on to win the championship and sign a three-year contract with Sarah Fisher Hartman Racing. And while Daly would wind up inking a deal with the Force India Formula One team that would have him serve as a test and reserve driver, his time overseas would prove unfruitful, and he returned home to pursue a path in Indycar.  Conor and Dale Jr. discuss Europe's perspective on American racers and theorize as to why it is difficult for them to break into the Formula racing ladder. After returning home, Daly did whatever he could to be at the tracks on race weekends, even at one point driving the Indycar two-seater for fan experiences. His perseverance would eventually win out, as he rose from filling in for injured drivers to racing part-time and now full-time for Ed Carpenter Racing.  Daly took time to speak on the ascension from spending his childhood at IMS to racing in the Indianapolis 500. Just this past May in the 106th running of the “Greatest Spectacle in Racing”, the hometown hero brought home his best finish to date, sixth place.  DIRTY AIR Before Conor joins the show, Dale, Mike, Alex, and Hannah chat about: Kelley's birthday bash Long weekend in Daytona The great Cup race rain debacle  Kurt Busch's injury progress ASKJR presented by Xfinity This week the fans asked questions about: Strangest excuse to explain a crash Feelings on Greg Ives' leaving as crew chief Updates on his ongoing car projects Championship Four predictions To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

Jehan Daruvala and Will Buxton join the F1 Feeder Series podcast and shockingly make Jim and Floris converse about something called Formula One... However, with Daruvala testing the McLaren MCL35M at Silverstone, we can excuse them! In this episode, we dive into:

If a young Valtteri Bottas and his dad hadn't spotted the sign for a go-kart race in Finland, then the Alfa Romeo driver may never have got on track, let alone partnered Lewis Hamilton at Mercedes.In the latest podcast from our My big break series, Bottas joins Chris Medland to reveal the make-or-break moments that brought him to Formula 1. He explains the key role that porridge power played ahead of his go kart debut, the local sponsors that bankrolled his fresh tyres, and the tests that took him from the Finnish go-karting championship to an F1 seat with Williams — via a rocky GP3 season. When Nico Rosberg retired from F1, Bottas moved from to Mercedes — and he suggests that he used his own money to buy out the Williams contract — only to be handed the Herculean task of being team-mate to Hamilton. Bottas describes how it took its toll, and reveals that he was on the brink of quitting at the end of the 2018 season before a restorative walk in a Finnish forest saw him change his mind.Now at Alfa Romeo, Bottas talks of the hope that he can win again with the team. "I don't see a limit," he says. "I'm absolutely loving F1." See acast.com/privacy for privacy and opt-out information.

About JamesJames has been part of AWS for over 15 years. During that time he's led software engineering for Amazon EC2 and more recently leads the AWS Commerce Platform group that runs some of the largest systems in the world, handling volumes of data and request rates that would make your eyes water. And AWS customers trust us to be right all the time so there's no room for error.Links Referenced:Email: jamesg@amazon.comTranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Vultr. Optimized cloud compute plans have landed at Vultr to deliver lightning-fast processing power, courtesy of third-gen AMD EPYC processors without the IO or hardware limitations of a traditional multi-tenant cloud server. Starting at just 28 bucks a month, users can deploy general-purpose, CPU, memory, or storage optimized cloud instances in more than 20 locations across five continents. Without looking, I know that once again, Antarctica has gotten the short end of the stick. Launch your Vultr optimized compute instance in 60 seconds or less on your choice of included operating systems, or bring your own. It's time to ditch convoluted and unpredictable giant tech company billing practices and say goodbye to noisy neighbors and egregious egress forever. Vultr delivers the power of the cloud with none of the bloat. “Screaming in the Cloud” listeners can try Vultr for free today with a $150 in credit when they visit getvultr.com/screaming. That's G-E-T-V-U-L-T-R dot com slash screaming. My thanks to them for sponsoring this ridiculous podcast.Corey: Finding skilled DevOps engineers is a pain in the neck! And if you need to deploy a secure and compliant application to AWS, forgettaboutit! But that's where DuploCloud can help. Their comprehensive no-code/low-code software platform guarantees a secure and compliant infrastructure in as little as two weeks, while automating the full DevSecOps lifestyle. Get started with DevOps-as-a-Service from DuploCloud so that your cloud configurations are done right the first time. Tell them I sent you and your first two months are free. To learn more visit: snark.cloud/duplo. Thats's snark.cloud/D-U-P-L-O-C-L-O-U-D. Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. And I've been angling to get someone from a particular department at AWS on this show for nearly its entire run. If you were to find yourself in an Amazon building and wander through the various dungeons and boiler rooms and subterranean basements—I presume; I haven't seen nearly as many of you inside of those buildings as people might think—you pass interesting departments labeled things like ‘Spline Reticulation,' or whatnot. And then you come to a very particular group called Commerce Platform.Now, I'm not generally one to tell other people's stories for them. My guest today is James Greenfield, the VP of Commerce Platform at AWS. James, thank you for joining me and suffering the slings and arrows I will no doubt be hurling at you.James: Thanks for having me. I'm looking forward to it.Corey: So, let's start at the very beginning—because I guarantee you, you're going to do a better job of giving the chapter and verse answer than I would from a background mired deeply in snark—what is Commerce Platform? It sounds almost like it's the retail website that sells socks, books, and underpants.James: So, Commerce Platform actually spans a bunch of different things. And so, I'm going to try not to bore you with a laundry list of all of the things that we do—it's a much longer list than most people assume even internal to AWS—at its core, Commerce Platform owns all of the infrastructure and processes and software that takes the fact that you've been running an EC2 instance, or you're storing an object in S3 for some period of time, and turns it into a number at the end of the month. That is what you asked for that service and then proceeds to try to give you as many ways to pay us as easily as possible. There are a few other bits in there that are maybe less obvious. One is we're also responsible for protecting the platform and our customers from fraudulent activity. And then we're also responsible for helping collect all of the data that we need for internal reporting to support some of the back-ends services that a business needs to do things like revenue recognition and general financial reporting.Corey: One of the interesting aspects about the billing system is just how deeply it permeates everything that happens within AWS. I frequently say that when it comes to cloud, cost and architecture are foundationally and fundamentally the same exact thing. If your entire service goes down, a few interesting things happen. One, I don't believe a single customer is going to complain other than maybe a few accountants here and there because the books aren't reconciling, but also you've removed a whole bunch of constraints around why things are the way that they are. Like, what is the most efficient way to run this workload?Well, if all the computers suddenly become free, I don't really care about efficiency, so much is, “Oh, hey. There's a fly, what do I have as a flyswatter? That's right, I'm going to drop a building on it.” And those constraints breed almost everything. I've said, for example, that S3 has infinite storage because it does.They can add drives faster than we're able to fill them—at least historically; they added some more replication services—but they're going to be able to buy hard drives faster than the rest of us are going to be able to stretch our budgets. If that constraint of the budget falls away, all bets are really off, and more or less, we're talking about the destruction of the cloud as a viable business entity. No pressure or anything.James: [laugh].Corey: You're also a recent transplant into AWS billing as a whole, Commerce Platform in general. You spent 15 years at the company, the vast majority of that over an EC2. So, either it was you've been exiled to a basically digital Siberia or it was one of those, “Okay, keeping all the EC2 servers up, this is easy. I don't see what people stress about.” And they say, “Oh, ho ho, try this instead.” How did you find yourself migrating over to the Commerce Platform?James: That's actually one I've had a lot from folks that I've worked with. You're right, I spent the first 15 or so years of my career at AWS in EC2, responsible for various things over there. And when the leadership role in Commerce Platform opened up, the timing was fortuitous, and part of it, I was in the process of relocating my family. We moved to Vancouver in the middle of last year. And we had an opening in the role and started talking about, potentially, me stepping into that role.The reason that I took it—there's a few reasons, but the primary reason is that if I look back over my career, I've kind of naturally gravitated towards owning things where people only really remember that they exist when they're not working. And for some reason, you know, I enjoy the opportunity to try to keep those kinds of services ticking over to the point where people don't notice them. And so, Commerce Platform lands squarely in that space. I've always been attracted to opportunities to have an impact, and it's hard to imagine having much more of an impact than in the Commerce Platform space. It underpins everything, as you said earlier.Every single one of our customers depends on the service, whether they think about it or realize it. Every single service that we offer to customers depends on us. And so, that really is the sort of nexus within AWS. And I'm a platform guy, I've always been a platform guy. I like the force multiplier nature of platforms, and so Commerce Platform, you know, as I kind of thought through all of those elements, really was a great opportunity to step in.And I think there's something to be said for, I've been a customer of Commerce Platform internally for a long time. And so, a chance to cross over and be on the other side of that was something that I didn't want to pass up. And so, you know, I'm digging in, and learning quickly, ramping up. By no means an expert, very dependent on a very smart, talented, committed group of people within the team. That's kind of the long and short of how and why.Corey: Let's say that I am taking on the role of an AWS product team, for the sake of argument. I know, keep the cringe down for a second, as far as oh, God, the wince is just inevitable when the idea of me working there ever comes up to anyone. But I have an idea for a service—obviously, it runs containers, and maybe it does some other things as well—going from idea to six-pager to MVP to barely better than MVP day-one launch, and at some point, various things happen to that service. It gets staff with a team, objectives and a roadmap get built, a P&L and budget, and a pricing model and the rest. One the last thing that happens, apparently, is someone picks the worst name off of a list of candidates, slaps it on the product, and ships it off there.At what point does the billing system and figuring out the pricing dimensions for a given service tend to factor in? Is that a last-minute story? Is that almost from the beginning? Where along that journey does, “Oh, by the way, we're building this thing. Maybe we should figure out, I don't know, how to make money from it.” Factor into the conversation?James: There are two parts to that answer. Pretty early on as we're trying to define what that service is going to look like, we're already typically thinking about what are the dimensions that we might charge along. The actual pricing discussions typically happen fairly late, but identifying those dimensions and, sort of, the right way to present it to customers happens pretty early on. The thing that doesn't happen early enough is actually pulling the Commerce Platform team in. but it is something that we're going to work this year to try to get a little bit more in front of.Corey: Have you found historically that you have a pretty good idea of how a service is going to be priced, everything is mostly thought through, a service goes to either private preview or you're discussing about a launch, and then more or less, I don't know, someone like me crops up with a, “Hey, yeah, let's disregard 90% of what the service does because I see a way to misuse the remaining 10% of it as a database.” And you run some mental math and realize, “Huh. We're suddenly giving, like, eight petabytes of storage per customer away for free. Maybe we should guard against that because otherwise, it's rife with misuse.” It used to be that I could find interesting ways to sneak through the cracks of various services—usually in pursuit of a laugh—those are getting relatively hard to come by and invariably a lot more trouble than they're worth. Is that just better comprehensive diligence internally, is that learning from customers, or am I just bad at this?James: No, I mean, what you're describing is almost a variant of the Defender's Dilemma. They are way more ways to abuse something than you can imagine, and so defending against that is pretty challenging. And it's important because, you know, if you turn the economics of something upside down, then it just becomes harder for us to offer it to customers who want to use it legitimately. I would say 90% of that improvement is us learning. We make plenty of mistakes, but I think, you know, one of the things that I've always been impressed by over my time here is how intentional we are trying to learn from those mistakes.And so, I think that's what you're seeing there. And then we try very hard to listen to customers, talk to folks like you, because one of the best ways to tackle anything it smells of the Defender's Dilemma is to harness that collective creativity of a large number of smart people because you really are trying to cover as much ground as possible.Corey: There was a fun joke going around a while back of what is the most expensive environment you can get running on a free tier account before someone from AWS steps in, and I think I got it to something like half a billion dollars in the first month. Now, I haven't actually tested this for reasons that mostly have to do with being relatively poor compared to, you know, being able to buy Guam. And understanding as well the fraud protections built into something like AWS are largely built around defending against getting service usage for free that in some way, shape or form, benefits the attacker. The easy example of that would be mining cryptocurrency, which is just super-economic as long as you use someone else's AWS account to do it. Whereas a lot of my vectors are, “Yeah, ignore all of that. How do I just make the bill artificially high? What can I do to misuse data transfer? And passing a single gigabyte through, how much can I make that per gigabyte cost be?” And, “Oh, circular replication and the Lambda invokes itself pattern,” and basically every bad architectural decision you can possibly make only this time, it's intentional.And that shines some really interesting light on it. And I have to give credit where due, a lot of that didn't come from just me sitting here being sick and twisted nearly so much as it did having seen examples of that type of misconfiguration—by mistake—in a variety of customer accounts, most confidently my own because it turns out that the way I learn things is by screwing them up first.James: Yeah, you've touched on a couple of different things in there. So, you know, maybe the first one is, I typically try to draw a line between fraud and abuse. And fraud is essentially trying to spend somebody else's money to get something for free. And we spent a lot of time trying to shut that down, and we're getting really good at catching it. And then abuse is either intentional or unintentional. There's intentional abuse: You find a chink in our armor and you try to take advantage of it.But much more commonly is unintentional abuse. It's not really abuse, you know. Abuse has very negative connotations, but it's unintentionally setting something up so that you run up a much larger bill than you intended. And we have a number of different internal efforts, and we're working on a bunch more this year, to try to catch those early on because one of my personal goals is to minimize the frequency with which we surprise customers. And the least favorite kind of surprise for customers is a [laugh] large bill. And so, what you're talking about there is, in a sufficiently complex system, there's always going to be weaknesses and ways to get yourself tied up in knots.We're trying both at the service team level, but also within my teams to try to find ways to make it as hard as possible to accidentally do that to yourself and then catch when you do so that we can stop it. And even more on the intentional abuse side of things, if somebody's found a way to do something that's problematic for our services, then you know, that's pretty much on us. But we will often reach out and engage with whoever's doing and try to understand what they're trying to do and why. Because often, somebody's trying to do something legitimate, they've got a problem to solve, they found a creative way to solve it, and it may put strain on the service because it's just not something we designed for, and so we'll try to work with them to use that to feed into either new services, or find a better place for that workload, or just bolster what they're using. And maybe that's something that eventually becomes a fully-fledged feature that we offer the customers. We're always open to learning from our customers. They have found far more creative ways to get really cool things done with our services than we've ever imagined. And that's true today.Corey: I mean, most of my service criticisms come down to the fact that you have more-or-less built a very late model, high performing iPad, and I'm out there complaining about, “What a shitty hammer this thing is, it barely works at all, and then it breaks in my hand. What gives?” I would also challenge something you said a minute ago that the worst day for some customers is to get a giant surprise bill, but [unintelligible 00:13:53] to that is, yeah, but, on some level, that kind of only money; you do have levers on your side to fix those issues. A worse scenario is you have a customer that exhibits fraud-like behavior, they're suddenly using far more resources than they ever did before, so let's go ahead and turn them off or throttle them significantly, and you call them up to tell them you saved them some money, and, “Our Superbowl ad ran. What exactly do you think you're doing?” Because they don't get a second bite at that kind of Apple.So, there's a parallel on both sides of this. And those are just two examples. The world is full of nuances, and at the scale that you folks operate at. The one-in-a-million events happen multiple times a second, the corner cases become common cases, and I'm surprised—to be direct—how little I see you folks dropping the ball.James: Credit to all of the teams. I think our secret sauce, if anything, really does come down to our people. Like, a huge amount of what you see as hopefully relatively consistent, good execution comes down to people behind the scenes making sure. You know, like, some of it is software that we built and made sure it's robust and tested to scale, but there's always an element of people behind the scenes, when you hit those edge cases or something doesn't quite go the way that you planned, making sure that things run smoothly. And that, if anything, is something that I'm immensely proud of and is kind of amazing to watch from the inside.Corey: And, on some level, it's the small errors that are the bigger concern than the big ones. Back a couple years ago, when they announced GP3 volumes at re:Invent, well, great, well spin up a test volume and kick the tires on it for an hour. And I think it was 80 or 100 gigs or whatnot, and the next day in the bill, it showed up as about $5,000. And it was, “Okay, that's not great. Not great at all.” And it turned out that it was a mispricing error by I think a factor of a million.And okay, at least it stood out. But there are scenarios where we were prepared to pay it because, oops, you got one over on us. Good job. That's never been the mindset I've gotten about AWS's philosophy for pricing. The better example that I love because no one took it seriously, was a few years before that when there was a LightSail bug in the billing system, and it made the papers because people suddenly found that for their LightSail instance, they were getting predicted bills of $4 billion.And the way I see it, you really only had to make that work once and then you've made your numbers for the year, so why not? Someone's going to pay for it, probably. But that was such out-of-the-world numbers that no one saw that and ever thought it was anything other than a bug. It's the small pernicious things that creep in. Because the billing system is vast; I had no idea when I started working with AWS bills just how complicated it really was.James: Yeah, I remember both of those, and there's something in there that you touched on that I think is really important. That's something that I realized pretty early on at Amazon, and it's why customer obsession is our flagship leadership principle. It's not because it's love and butterflies and unicorns; customer obsession is key to us because that's how you build a long-term sustainable business is your customers depend on you. And it drives how we think about everything that we do. And in the billing space, small errors, even if there are small errors in the customer's favor, slowly erode that trust.So, we take any kind of error really seriously and we try to figure out how we can make sure that it doesn't happen again. We don't always get that right. As you said, we've built an enormous, super-complex business to growing really quickly, and really quick growth like that always acts as kind of a multiplier on top of complexity. And on the pricing points, we're managing millions of pricing points at the moment.And our tools that we use internally, there's always room for improvement. It's a huge area of focus for us. We're in the beginning of looking at applying things like formal methods to make sure that we can make very hard guarantees about the correctness of some of those. But at the end of the day, people are plugging numbers in and you need as many belts and braces as possible to make sure that you don't make mistakes there.Corey: One of the things that struck me by surprise when I first started getting deep into this space was the fact that the finalized bill was—what does it mean to have this be ‘finalized?' It can hit the Cost and Usage Report in an S3 bucket and it can change retroactively after the month closed periodically. And that's when I started to have an inkling of a few things: Not just the sheer scale and complexity inherent to something like the billing system that touches everything, but the sheer data retention stories where you clearly have to be able to go back and reconstruct a bill from the raw data years ago. And I know what the output of all of those things are in the form of Cost and Usage Reports and the billing data from our client accounts—which is the single largest expense in all of our AWS accounts; we spent thousands and thousands and thousands of dollars a year just on storing all of that data, let alone the processing piece of it—the sheer scale is staggering. I used to wonder why does it take you a day to record me using something to it's showing up in the bill? And the more I learned the more it became a how can you do that in only a day?James: Yes, the scale is actually mind-boggling. I'm pretty sure that the core of our billing system is—I'm reasonably confident it's the largest or one of the largest data processing systems on the planet. I remember pretty early on when I joined Commerce Platform and was still starting to wrap my head around some of these things, Googling the definition of quadrillion because we measured the number of metering events, which is how we record usage in services, on a daily basis in the quadrillions, which is a billion billions. So, it's just an absolutely staggering number. And so, the scale here is just out of this world.That's saying something because it's not like other services across AWS are small in their own right. But I'm still reasonably sure that being one of a handful of services that is kind of at the nexus of AWS and kind of deals with the aggregate of AWS's scale, this is probably one of the biggest systems on the planet. And that shows up in all sorts of places. You start with that input, just the sheer volume of metering events, but that has to produce as an output pretty fine-grained line item detailed information, which ultimately rolls up into the total that a customer will see in their bill. But we have a number of different systems further down the pipeline that try to do things like analyze your usage, make sensible recommendations, look for opportunities to improve your efficiency, give you the ability to slice and dice your data and allocate it out to different parts of your business in whatever way it makes sense for your business. And so, those systems have to deal with anywhere from millions to billions to recently, we were talking about trillions of data points themselves. And so, I was tangentially aware of some of the scale of this, but being in the thick of it having joined the team really just does underscore just how vast the systems are.Corey: I think it's, on some level, more than a little unfortunate that that story isn't being more widely told, more frequently. Because when Commerce Platform has job postings that are available on the website, you read it and it's very vague. It doesn't tend to give hard numbers about a lot of these things, and people who don't play in these waters can easily be forgiven for thinking the way that you folks do your job is you fire up one of those 24 terabyte of RAM instances that—you know, those monstrous things that you folks offer—and what do you do next? Well, Microsoft Excel. We have a special high memory version that we've done some horse-trading with our friends over at Microsoft for.It's, yeah, you're several steps beyond that, at this point. It's a challenging problem that every one of your customers has to deal with, on some level, as well. But we're only dealing with the output of a lot of the processing that you folks are doing first.James: You're exactly right. And a big focus for some of my teams is figuring out how to help customers deal with that output. Because even if you're talking about couple of orders of magnitude reduction, you're still talking about very large numbers there. So, to help customers make sense of that, we have a range of tools that exist, we're investing in.There's another dimension of complexity in the space that I think is one that's also very easy to miss. And I think of it as arbitrary complexity. And it's arbitrary because some of the rules that we have to box within here are driven by legislative changes. As you operate more and more countries around the world, you want to make sure that we're tax compliant, that we help our customers be tax compliant. Those rules evolve pretty rapidly, and Country A may sit next to Country B, but that doesn't mean that they're talking to one another. They've all got their own ideas. They're trying to accomplish r—00:22:47Corey: A company is picking up and relocating from India to Germany. How do we—James: Exactly.Corey: —change that on the AWS side and the rest? And it's, “Hoo boy, have you considered burning it all down and filing an insurance claim to start over?” And, like, there's a lot of complexity buried underneath that that just doesn't rise to the notice of 99% of your customers.James: And the fact that it doesn't rise to the notice is something that we strive for. Like, these shouldn't be things that customers have to worry about. Because it really is about clearing away the things that, as far as possible, you don't want to have to spend time thinking about so that you can focus on the thing that your business does that differentiates you. It's getting rid of that undifferentiated heavy lifting. And there's a ton of that in this space, and if you're blissfully unaware of it, then hopefully that means that we're doing our job.Corey: What I'm, I think, the most surprised about, and I have been for a long time. And please don't take this as an insult to various other folks—engineers, the rest, not just in other parts of AWS but throughout the other industry—but talking to the people who work within Commerce Platform has always been just a fantastic experience. The caliber of people that you have managed to attract and largely retain—we don't own people, they do matriculate out eventually—but the caliber of people that you've retained on your teams has just been out of this world. And at first, I wondered, why are these awesome people working on something as boring and prosaic as billing? And then I started learning a little bit more as I went, and, “Oh, wow. How did they learn all the stuff that they have to hold in their head in tension at once to be able to build things like this?” It's incredibly inspiring just watching the caliber of the people that you've been able to bring in.James: I've been really, really excited joining this team, as I've gotten other folks on the team because there's some super-smart people here. But what's really jumped out to me is how committed the team is. This is, for the most part, a team that has been in the space for many years. Many of them have—we talk about boomerangs, folks who live AWS, go spend some time somewhere else and come back and there's a surprisingly high proportion of folks in Commerce Platform who have spent time somewhere else and then come back because they enjoy the space, they find that challenging, folks are attracted to the ability to have an impact because it is so foundational. But yeah, there's a super-committed core to this team. And I really enjoy working with teams where you've got that because then you really can take the long view and build something great. And I think we have tons of opportunities to do that here.Corey: It sounds ridiculous, but I've reached out to team members before to explain two-cent variances in my bill, and never once have I been confronted with a, “It's two cents. What do you care?” They understand the requirement that these things be accurate, not just, “Eh, take our word for it.” And also, frankly, they understand that two cents on a $20 bill looks a little different on a $20 million bill. So yeah, let us figure out if this is systemic or something I have managed to break.It turns out the Cost and Usage Report processing systems don't love it when there's a cost allocation tag whose name contains an emoji. Who knew? It's the little things in life that just have this fun way of breaking when you least expect it.James: They're also a surprisingly interesting problem. So like, it turns out something as simple as rounding numbers consistently across a distributed system at this scale, is a non-trivial problem. And if you don't, then you do get small seventh or eighth decimal place differences that add up to something that then shows up as a two-cent difference somewhere. And so, there's some really, really interesting problems in the space. And I think the team often takes these kinds of things as a personal challenge. It should be correct, and it's not, so we should go make sure it is correct. The interesting problems abound here, but at the end of the day, it's the kind of thing that any engineering team wants to go and make sure it's correct because they know that it can be.Corey: This episode is sponsored in parts by our friend EnterpriseDB. EnterpriseDB has been powering enterprise applications with PostgreSQL for 15 years. And now EnterpriseDB has you covered wherever you deploy PostgreSQL on premises, private cloud, and they just announced a fully managed service on AWS and Azure called BigAnimal, all one word. Don't leave managing your database to your cloud vendor because they're too busy launching another half dozen manage databases to focus on any one of them that they didn't build themselves. Instead, work with the experts over at EnterpriseDB. They can save you time and money, they can even help you migrate legacy applications, including Oracle, to the cloud.To learn more, try BigAnimal for free. Go to biganimal.com/snark, and tell them Corey sent you.Corey: On the one hand, I love people who just round and estimate—we all do that, let's be clear; I sit there and I back-of-the-envelope everything first. But then I look at some of your pricing pages and I count the digits after the zeros. Like, you're talking about trillionths of a dollar on some of your pricing points. And you add it up in the course of a given hour and it's like, oh, it's $250 a month, most months. And it's you work backwards to way more decimal places of precision than is required, sometimes.I'm also a personal fan of the bill that counts, for example, number of Route 53 zones. Great. And it counts them to four decimal places of precision. Like, I don't even know what half of it Route 53 zone is at this point, let alone something to, like, ah the 1,000th of the zone is going to cause this. It's all an artifact of what the underlying systems are.Can you by any chance shed a little light on what the evolution of those systems has been over a period of time? I have to imagine that anything you built in the early days, 16 years ago or so from the time of this recording when S3 launched to general availability, you probably didn't have to worry about this scope and scale of what you do, now. In fact, I suspect if you tried to funnel this volume through S3 back then, the whole thing would have collapsed under its own weight. What's evolved over the time that you had the billing system there? Because changes come slowly to your environment. And frankly, I appreciate that as a customer. I don't like surprising people in finance.James: Yeah, you're totally right. So, I joined the EC2 team as an engineer myself, some 16 years ago, and the very first thing that I did was our billing integration. And so, my relationship with the Commerce Platform organization—what was the billing team way back when—it goes back over my entire career at AWS. And at the time, the billing team was similar, you know, [unintelligible 00:28:34] eight people. And that was everything. There was none of the scale and complexity; it was all one system.And much like many of our biggest, oldest services—EC2 is very similar, S3 is as well—there's been significant growth over the last decade-and-a-half. A lot of that growth has been rapid, and rapid growth presents its own challenges. And you live with decisions that you make early on that you didn't realize were significant decisions that have pretty deep implications 15 years later. We're still working through some of those; they present their own challenges. Evolving an existing system to keep up with the growth of business and a customer base that's as varied and complex as ours is always challenging.And also harder but I also think more fun than a clean sheet redo at this point. Like, that's a great thought exercise for, well, if we got to do this again today, what would we do now that we've learned so much over the last 15 years? But there's this—I find it personally fascinating challenge with evolving a live system where it's like, “No, no, like, things exist, so how do we go from there to where we want to be next?”Corey: Turn the billing system off for 18 months, rebuild—James: Yeah. [laugh].Corey: The whole thing from first principles. Light it up. I'm sure you'd have a much better billing system, and also not a company left anymore.James: [laugh]. Exactly, exactly. I've always enjoyed that challenge. You know, even prior to AWS, my previous careers have involved similar kinds of constraints where you've got a live system, or you've got an existing—in the one case, it was an existing SDK that was deployed to tens of thousands of customers around the world, and so backwards compatibility was something that I spent the first five years of my career thinking about it way more detail than I think most people do. And it's a very similar mindset. And I enjoy that challenge. I enjoy that: How do I evolve from here to there without breaking customers along the way?And that's something that we take pretty seriously across AWS. I think SimpleDB is the poster child for we never turn things off. But that applies equally to the services that are maybe less visible to customers, and billing is definitely one of them. Like, we don't get to switch stuff off. We don't get to throw things away and start again. It's this constant state of evolution.Corey: So, let's say that I were to find a way to route data through a series of two Managed NAT Gateways and then egress to internet, and the sheer density of the expense of that traffic tears a hole in the fabric of space-time, it goes back 15 years ago, and you can make a single change to how the billing system was built. What would it be? What pisses you off the most about the current constraints that you have to work within or around?James: I think one of the biggest challenges we've got, actually, is the concept of an account. Because an account means half-a-dozen different things. And way back, when it seemed like a great idea, you just needed an account; an account was your customer, and it was the same thing as the boundary that you put all your resources inside. And of course, it's the same thing that you're going to roll all of your usage up and issue a bill against. And that has been one of the areas that's seen the most evolution and probably still has a pretty long way to go.And what's interesting about that is, that's probably something we could have seen coming because we watched the retail business go through, kind of, the same evolution because they started with, well, a customer is a customer is a customer and had to evolve to support the concept of sellers and partners. And then users are different than customers, and you want to log in and that's a different thing. So, we saw that kind of bifurcation of a single entity into a wide range of different related but separate entities, and I think if we'd looked at that, you know, thought out 15 years, then yeah, we could probably have learned something from that. But at the same time, when AWS first kicked off, we had wild ambitions for it, but there was no guarantee that it was going to be the monster that it is today. So, I'm always a little bit reluctant to—like, it's a great thought exercise, but it's easy to end up second-guessing a pretty successful 15 years, so I'm always a little bit careful to walk that line. But I think account is one of the things that we would probably go back and think about a little bit more.Corey: I want to be very clear with this next question that it is intentionally setting up a question I suspect you get a lot. It does not mirror my own thinking on the matter even slightly, but I get a version of it myself all the time. “AWS bills, that sounds boring as hell. Why would you choose to work on such a thing?” Now, I have a laundry list of answers to that aren't nearly as interesting as I suspect yours are going to be. What makes working on this problem space interesting to you?James: There's a bunch of different things. So, first and foremost, the scale that we're talking about here is absolutely mind-blowing. And for any engineer who wants to get stuck into problems that deal with mind-blowingly large volumes of data, incredibly rich dimensions, problems where, honestly, applying techniques like statistical reasoning or machine learning is really the only way to chip away at it, that exists in spades in the space. It's not always immediately obvious, and I think from the outside, it's easy to assume this is actually pretty simple. So, the scale is a huge part of that.Corey: “Oh, petabytes. How quaint.”James: [laugh]. Exactly. Exactly I mean, it's mind-blowing every time I see some of the numbers in various parts of the Commerce Platform space. I talked about quadrillions earlier. Trillions is a pretty common unit of measure.The complexity that I talked about earlier, that's a result of external environments is another one. So, imposed by external entities, whether it's a government or a tax authority somewhere, or a business requirement from customers, or ourselves. I enjoy those as well. Those are different kinds of challenge. They really keep you on your toes.I enjoy thinking of them as an engineering problem, like, how do I get in front of them? And that's something we spend a lot of time doing in Commerce Platform. And when we get it right, customers are just unaware of it. And then the third one is, I personally am always attracted to the opportunity to have an impact. And this is a space where we get to hopefully positively impact every single customer every day. And that, to me is pretty fulfilling.Those are kind of the three standout reasons why I think this is actually a super-exciting space. And I think it's often an underestimated space. I think once folks join the team and sort of start to dig in, I've never heard anybody after they've joined, telling me that what they're doing is boring. Challenging, yes. Is frustrating, sometimes. Hard, absolutely, but boring never comes up.Corey: There's almost no service, other than IAM, that I can think of that impacts every customer simultaneously. And it's easy for me to sit in the cheap seats and say, “Oh, you should change this,” or, “You should change that.” But every change you have is so massive in scale that it's going to break a whole bunch of companies' automations around the bill processing in different ways. You have an entire category of user persona who is used to clicking a certain button in this certain place in the console to generate the report every month, and if that button moves or changes color, or has a different font, suddenly that renders their documentation invalid, and they're scrambling because it's not their core competency—nor should it be—and every change you make is so constricted, just based upon all the different concerns that you've got to be juggling with. How do you get anything done at all? I find that to be one of the most impressive aspects about your organization, bar none.James: Yeah, I'm not going to lie and say that it isn't a challenge, but a lot of it comes down to the talent that we have on the team. We have a super-motivated, super-smart, super-engaged team, and we spend a lot of time figuring out how to make sure that we can keep moving, keep up with the business, keep up with a world that's getting more complicated [laugh] with every passing day. So, you've kind of hit on one of the core challenges there, which is, how do we keep up with all of those different dimensions that are demanding an increasing amount of engineering and new support and new investment from us, while we keep those customers happy?And I think you touched on something else a little bit indirectly there, which is, a lot of our customers are actually pretty technical across AWS. The customers that Commerce Platform supports, are often the least technical of our customers, and so often need the most help understanding why things are the way they are, where the constraints are.Corey: “A big bill from Amazon. How many books did you people buy last month?”—James: [laugh]. Exactly.Corey: —is still very much level of understanding in some cases. And it's not because they're dumb; far from it. It's just, imagine that some people view there as being more to life than understanding the nuances and intricacies of cloud computing. How dare they?James: Exactly. Who would have thought?Corey: So, as you look now over all of your domain, such as it is, what sucks the most? What are you looking to fix as far as impactful changes that the rest of the world might experience? Because I'm not going to accept one of those questions like, “Oh, yeah, on the back-end, we have this storage subsystem for a tertiary thing that just annoys me because it wakes us up once in a whi”—no, no, I want something customer-facing. What's the painful thing you're looking at fixing next?James: I don't like surprising customers. And free tier is, sort of, one of those buckets of surprises, but there are others. Another one that's pretty squarely in my sights is, whether we like it or not, customer accounts get compromised. Usually, it's a password got reused somewhere or was accidentally committed into a GitHub repository somewhere.And we have pretty established, pretty effective mechanisms for finding all of those, we'll scan for passwords and credentials, and alert customers to those, and help them correct that pretty quickly. We're also actually pretty good at detecting when an account does start to do something that suggests that it's been compromised. Usually, the first thing that a compromised account starts to do is cryptocurrency mining. We're pretty quick to catch those; we catch those within a matter of hours, much faster most days.What we haven't really cracked and where I'm focused at the moment is getting back to the customer in a way that's effective. And by that I mean specifically, we detect an account compromised super-quickly, we reach out automatically. And so, you know, a customer has got some kind of contact from us usually within a couple of hours. It's not having the effect that we need it to. Customers are still being surprised a month later by a large bill. And so, we're digging into how much of that is because they never saw the contact, they didn't know what to do with the contact.Corey: It got buried with all the other, “Hey, we saw you spun up an S3 bucket. Have you heard of what S3 is?” Again, that's all valuable, but you have 300-some-odd services. If you start doing that for every service, you're going to hit mail sending limits for Gmail.James: Exactly. It's not just enough that we detect those and notify customers; we have to reduce the size of the surprise. It's one thing to spend 100 bucks a month on average, and then suddenly find that your spend has jumped $250 because you reused the password somewhere and somebody got ahold of it and it's cryptocurrency-mining your account. It's a whole different ballgame to spend 100 bucks a month and then at the end of the month discover that your bill is suddenly $2,000 or $20,000. And so, that's something that I really wanted to make some progress on this year. Corey: I've really enjoyed our conversation. If people want to learn more about how you view these things, how you're approaching some of these problems, or potentially are just the right kind of warped to consider joining up, where's the best place for them to go?James: They should drop me an email at jamesg@amazon.com. That is the most direct way to get hold of me, and I promise I will get back to you. I try to stay on top of my email as much as possible. But that will come straight to me, and I'm always happy to talk to folks about the space, talk to folks about opportunities in this team, opportunities across AWS, or just hear what's not working, make sure that it's something that we're aware of and looking at.Corey: Throughout Amazon, but particularly within Commerce Platform, I've always appreciated the response of, whenever I report something, no matter how ridiculous it is—and I assure you there's an awful lot of ridiculousness in my bug reports—the response has always been the same: “Tell me more. Help me understand what it is you're trying to achieve—even if it is ridiculous—so we can look at this and see what is actually going on.” Every Amazonian team has been great about that or you're not at Amazon very long, but you folks have taken that to an otherworldly level. I just want to thank you for doing that.James: I appreciate you for calling that out. We try, you know, we really do. We take listening to our customers very seriously because, at the end of the day, that's what makes us better, and that's how we make sure we're in it for the long haul.Corey: Thanks once again for being so generous with your time. I really appreciate it.James: Yeah, thanks for having me on. I've enjoyed it.Corey: James Greenfield, VP of Commerce Platform at AWS. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment—possibly on YouTube as well—about how you aren't actually giving this five-stars at all; you have taken three trillions of a star off of the rating.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Welcome to episode 9 of the Lovecars On The Grid Podcast! Tiff Needell and Paul Woodman are back again to give you a roundup of the motorsport events from the past week! We of course have to kick off with Formula 1, where we've had testing in Barcelona for the 2022 season. Meanwhile, both Max Verstappen and Lewis Hamilton have been voicing their opinions over the Michael Masi saga. Hamilton has been voicing his opinions on having non-biased stewards, while Verstappen has been expressing his opinion that race director, Michael Masi has been thrown under the bus! In the testing, we saw some good lap times from Ferrari, Mercedes and the other teams, but Alpine didn't seem to set any lap times, with Fernando Alonso even catching fire during testing! There's lots of talk about Nikita Mazepin not being part of the opening Grand Prix, and Pietro Fittipaldi replacing him temporarily. We don't think Russian drivers should be penalised for the horrible events in Ukraine! What would you do with the Mazepin situation? Haas have of course lost their main Russian sponsor already. The World Rally Championship was taking place out in Sweden this weekend too. With 21 year old, Kalle Rovanpera winning with his co-driver Jonne Haltunen. Indycar had an eventful weekend at St. Petersburg. With Kiwi driver, Scott McLaughlin taking the first win of the season. Following Tiff's return from Daytona, NASCAR was at the Auto Club Speedway in Fontana, California. We had some spins at 180MPH. With Tiff's favourite, Kyle Larson fighting for 1st place and ended up putting his team mate, Chase Elliot into the wall! Coming up, we have NASCAR in Las Vegas! Moto GP is back at the Qatar GP, without Valentino Rossi sadly! We also have GP2 and GP3!

GHiT 0296: Mo Dadkhah from Hagerty's The Drive Within We first were introduced to Mo Dadkhah during our episode with Loni Unser and then we saw that he was on "The Drive Within" with the rest of the Round Three Racing  team (R3R) as they competed in the WRL endurance racing series.  The show is sponsored by Hagerty and appears on their site as well as the Motor Trend channel.  Mo is one of the drivers of the #701 Porsche Cayman that competes in the GP1 class within WRL.  During this episode, we go over Mo's racing history, the WRL series, the R3R team, and tons of details on the making of the show.  This show is being released ahead of the season ending episode that should be released this Friday.  "The Drive Within" is the first show that we have found that accurately depicts the highs and lows that each team and driver experiences during a race weekend.  It is a can't miss show and has a permanent spot on our DVR. A link to the episode is: https://tinyurl.com/MoDadkhah If you would like to help grow our sport and this podcast: You can subscribe to our podcast on the podcast provider of your choice, including the Apple podcast app, Google music, Amazon, and YouTube etc. Also, if you could give our podcast a (5-star?) rating, that would be greatly appreciated.  Even better, a podcast review, would help us to grow the passion and sport of high performance driving and we would greatly appreciate it. For instance, leaving an Apple Podcast rating is very easy.  If you go to your podcast library, look under shows.  Then click on this podcast.  Here you can leave a (5?) star rating and enter your review.  We hope you enjoy this episode! PS  Please don't forget that if you are looking to add an Apex Pro to your driving telemetry system, don't forget to use our discount code for all Apex Pro systems you will receive a free Windshield Suction Cup Mount for the system, a savings of $40.  Just enter the code “ghitlikesapex!” when you order.  They are a great system and truly invaluable in safely increasing your speed on track and/or autocross etc.  The recently released second generation systems and app increases the capability of the system greatly. Best regards, Vicki, Jennifer, Alan, and Bill Hosts of the Garage Heroes In Training Podcast and Garage Heroes In Training racing team drivers Highlights for this episode include: 1)  How endurance racing and consistency of effort has led to Mo's growth as a driver and allowed him to reach his current level. 2)  We go into how the Cayman #701 race car came to be the tool of choice that Mo drives with his team in WRL's GP1 class primarily against other Caymans and E46 BMW's. 3)  What Mo gets from his racing and how drivers are "compensated" even at the higher levels in the US.  Spoiler, none of us will likely be making a mortgage payment anytime soon. 4)  How the R3R racing team works and interacts at the races and what you can learn from them that will help your endurance racing team. 5)  Mo gives a great summary of the way that the WRL series classifications work and his thoughts on the way the series functions and keeps the competition level high but still more reliant on the driver, as opposed to the budget/checkbook.  6)  We also go into starting and filming "The Drive Within" and we start to feel a bit better about our iPhone and Android race weekend videos not being quite up to this level, lol.  7)  The R3R team is a perfect example that the team is not just about the drivers, it depends on each and every team member, both before and at the track, and when operating properly, it becomes a family. 8)  Tips on how to improve as a driver and tons of little items that R3R does as a team that everyone can incorporate into their racing program and team, even if it is a "team" of one. 9)  Mo uses a coach personally and we review his opinions on how a coach can help your driving and the differences between an instructor and a coach.  We need to try this in 2022. 10)  We come up with a new business plan.  No stealing please.   PS Don't tease Mo too hard after the least episode airing this Friday. PS2  Please let everyone know about the show and hopefully we can get a second season PS3  We gladly welcome Mo's repeated offers to become a "producer" of the show and secure some great episodes PS4  Let us know if you want to hear Mo subjected to the our fast and furious story time questions.  We have a bunch of other racing and driving questions for him as well.   To follow Mo further:  Instagram: @therealmodadkhah The Drive Within:  https://www.hagerty.com/media/series/drive-within/  Round Three Racing:  https://www.round3racing.com/ 

Its another double whammy! A Jaguar duo! This week our first guest is Sam Bird, he's a race winner in every season of the Formula E World Championship to date and has been in the Series since it's very first race. He first appeared in karting before Formula BMW, he's been a reserve driver for Mercedes F1, before signing up to race in the first ever Formula E season in 2014 with Virgin Racing and we find him now of course, with Jaguar Racing. His teammate is Mitch Evans, and we're lucky enough to have him here as well. Mitch also started in karts and under the mentorship of Mark Webber, he went onto win the 2012 GP3 title. His electric career started in 2016 when he signed for Jaguar where he remains to this very day after a strong showing in Season 7 when he finished 4th in the Championship just a few points off the winning drive of Nyck De Vries. This episode is powered by our partners at Rodin Cars - thank you so much to Shannon, David, Cliff and the team for trusting in us and joining Season 10.Subscribe to MotorMouth on YouTube for loads more content: https://bit.ly/3qVXP0RFollow MotorMouth:Twitter - https://twitter.com/MotorMouth_ Instagram - https://www.instagram.com/MotorMouth_official/Facebook - https://www.facebook.com/MotorMouthClub/Website - https://www.motormouth.club/Download our App:iOS - https://apple.co/3scnns2 Android - https://bit.ly/3cf9yU2 Much love,Tim and Harry! Get bonus content on Patreon See acast.com/privacy for privacy and opt-out information.

Host, Sue Stockdale talks to Jim Morris, founder of Lifeline Fire & Safety Systems about the latest changes in safety regulations for fire extinguishers, and how technology advances such as biofuels and electrification impact the design and manufacture of safety equipment for race cars. Jim is also a keen amateur competitor and shares some highlights from racing his dad's original Volkswagen Golf GTI from the 1981–1982 season, including winning the small class Gerry Marshall Trophy race at the 2021 Goodwood Members meeting.Lifeline Fire & Safety Systems is a specialist motorsport fire suppression & safety company that employs 30 people. It supplies an ever-increasing range of safety equipment, fire extinguishing systems, safety harnesses, crash and roll cage paddings, rain lights and steering mechanisms to the global motorsport market, with blue chip customers such as Bentley, Ferrari, McLaren, Porsche, VW, Audi, Aston Martin, Dallara, Ligier, Mygale, Ford, Citroen, Peugeot, Hyundai and Ginetta. Lifeline products have, and are being used in just about every category of global motorsports, including Formula 1, Indy Car, GP2, GP3, F3, WRC, BTCC, WTCC, Supercars, Formula E, Rallycross, IMSA, WEC, GT3, and GT4. In 2019 80% of the Le Mans 24-hour field used Lifeline products. Lifeline has also designed and manufacture fire suppression systems for many of the tracked and wheeled vehicles used in the defence industry. The company has a global network of dealer's, service agents and re-sellers, and in 2015 opened a dedicated facility, Lifeline USA, in Virginia North America. Find out more at https://www.lifeline-fire.co.uk YouTube: https://www.youtube.com/user/lifelinefiresafety Leave your feedback about the podcast https://sports2000.co.uk/podcasts/The Sports2000 Championship has been established since 1977 and features four championships - Duratecs, Pintos, Historic Pintos and Mini Enduro. Connect with us at www.sports2000.co.uk or on social mediaInstagram https://www.instagram.com/srcc_sports2000/ Facebook https://www.facebook.com/Sports-2000-Championships-327158720703344Twitter https://twitter.com/SportsCarChamp Sound Editor: Rob Lawrence (he/him)Producer: Sue Stockdale (she/her)

Alex Albon has a second shot at Formula 1 with Williams this year, continuing his rocky journey from karting champion to the grand prix paddock.In our latest My Big Break podcast, he tells Chris Medland how he rose through the ranks of F3 and F2, battling for race wins and championships with Charles Leclerc, George Russell and Lando Norris.Albon recounts losing Red Bull backing after a tricky first year in Formula Renault, before picking himself up, graduating to GP3 and challenging Leclerc for the 2015 title. He explains why his friendship with George Russell resulted in a broken collarbone that wrecked his debut F2 season; the goodwill that brought him a second year in the championship; and the bold move — combined with a timely win — that brought him back into the Red Bull fold and into an F1 seat just before a switch to Formula E.Ahead of the 2022 F1 season, the upbeat, grounded Albon shows since again why he's one of racing's most popular figures. See acast.com/privacy for privacy and opt-out information.

Join 22 Panels as we dive deep into R Sikoryak's work! Sikoryak specializes in making comic adaptations of literature classics.  Tyler and Tad were lucky enough to pick his brain for close to 2 hours! Consider becoming a patron!

2020-21 Formula E title contender Jake Dennis joins the show this week, as Alejandro Alonso Lopez caught up with the British driver during his final race of the GT World Challenge Europe season at Barcelona. Dennis was part of the famous 2014 European Formula 3 class of drivers, finished third a year later, and also impressed in GP3 before switching to sportscars and then DTM. But it was a surprise switch to FE which paid off for him this year, nearly taking the title from Nyck de Vries despite his rookie status.

My guest today is a racer through and through. Tatiana Calderon has driven karts, single-seaters, GT and LMP cars across the world and has been the ‘first woman' in so many instances that I lost count. Born in Colombia, karting since nine-years-old, her path has taken her to British F3, European F3, Macau, World Series 3.5, GP3, Formula E, Formula 2, Le Mans… If it's on a track and has four wheels, I'm pretty sure she's driven it. Her reputation as a fierce competitor precedes her, though our common friends are united in saying that she is one of the nicest people you could ever meet. I hope you enjoy our chat together, I learnt so much about determination, strength, passion and kindness while talking to Tatiana. I hope you will too. Check out Tatiana online:Twitter: @TataCaldeInstagram: @tatacalde7Website: www.tatianacalderon.comYou can contact me via @Pandea on Instagram.You can support the podcast via supporter.acast.com/racinglives.Support this show http://supporter.acast.com/racinglives. See acast.com/privacy for privacy and opt-out information.

He came with speed, and he came with gifts. IndyCar Series Champion Alex Palou, the young champion, sits at the table with Dale Earnhardt Jr. to talk about his sudden rise to the pinnacles of motorsport. The colorful Spaniard didn't come from a racing family. It was a local go-kart track near his home village of Sant Antoni de Vilamajor Spain, that sparked his interest in becoming a racecar driver. From there, a path of persistence, raw speed, and opportunity led him to eventually become the 2021 NTT Indycar Series Champion.Palou connects with Dale Jr. and co-host Mike Davis about life in Spain and what it was like to grow up overseas. A racing path that took him far from home at a young age to Japan, Palou had to get used to different cultures as he tried to find himself as a racer and a man. That path didn't come without disappointment and setback. From homemade mountain dynos to racing for big teams in GP3 and F3, it's a true racing story.Alex Palou came on the scene with success in his rookie IndyCar season with Dale Coyne Racing. But it was his sophomore season that set the stage for his meteoric rise. An opportunity came with Chip Ganassi Racing and he took full advantage of it. Leaning on veteran leadership of teammates Scott Dixon and Jimmie Johnson, the youngster made a name for himself with three victories and the series title. To boot, he nearly won the Indianapolis 500. The near-miss in the world's biggest race didn't set him back though. Palou shares how the 7-time NASCAR Champion, Johnson, helped him mentally break through setbacks.Palou also came into the Bojangles studio with gifts, for Dale's Birthday and also some keepsakes for the crew. The 24-year old shares his personality as he and Dale Jr. talk about the dynamic personalities of the international scene that IndyCar presents. Dale Jr. first experienced it in iRacing, and it is why he and Mike on fire for the open-wheel brand of racing.Before Palou's arrival, Dale Jr. took control of the room. We're joking. Actually, an energy drink and a spunky mood had the whole gang wondering where Dale Jr. would go next. From Frankenstein to Cash-only soda machines... Dale Jr. held court in ways only Dale Jr. can. He and Mike also touched on the hottest topic in NASCAR today, the ongoing rivalry between Chase Elliott and Kevin Harvick.In Ask Jr. it's all about the triangle... of the tasty kind! Dave Portnoy's latest Dale Jr. invoked Pizza review brings up some questions about how it went down and the Key West drunken pizza hotspot. We also learn about Dale Jr's latest Chevy Silverado and how he decided the wild graphics he put on it.That and much more in this entertaining version of The Dale Jr. Download. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

He came with speed, and he came with gifts. IndyCar Series Champion Alex Palou, the young champion, sits at the table with Dale Earnhardt Jr. to talk about his sudden rise to the pinnacles of motorsport. The colorful Spaniard didn't come from a racing family. It was a local go-kart track near his home village of Sant Antoni de Vilamajor Spain, that sparked his interest in becoming a racecar driver. From there, a path of persistence, raw speed, and opportunity led him to eventually become the 2021 NTT Indycar Series Champion. Palou connects with Dale Jr. and co-host Mike Davis about life in Spain and what it was like to grow up overseas. A racing path that took him far from home at a young age to Japan, Palou had to get used to different cultures as he tried to find himself as a racer and a man. That path didn't come without disappointment and setback. From homemade mountain dynos to racing for big teams in GP3 and F3, it's a true racing story. Alex Palou came on the scene with success in his rookie IndyCar season with Dale Coyne Racing. But it was his sophomore season that set the stage for his meteoric rise. An opportunity came with Chip Ganassi Racing and he took full advantage of it. Leaning on veteran leadership of teammates Scott Dixon and Jimmie Johnson, the youngster made a name for himself with three victories and the series title. To boot, he nearly won the Indianapolis 500. The near-miss in the world's biggest race didn't set him back though. Palou shares how the 7-time NASCAR Champion, Johnson, helped him mentally break through setbacks. Palou also came into the Bojangles studio with gifts, for Dale's Birthday and also some keepsakes for the crew. The 24-year old shares his personality as he and Dale Jr. talk about the dynamic personalities of the international scene that IndyCar presents. Dale Jr. first experienced it in iRacing, and it is why he and Mike on fire for the open-wheel brand of racing. Before Palou's arrival, Dale Jr. took control of the room. We're joking. Actually, an energy drink and a spunky mood had the whole gang wondering where Dale Jr. would go next. From Frankenstein to Cash-only soda machines... Dale Jr. held court in ways only Dale Jr. can. He and Mike also touched on the hottest topic in NASCAR today, the ongoing rivalry between Chase Elliott and Kevin Harvick. In Ask Jr. it's all about the triangle... of the tasty kind! Dave Portnoy's latest Dale Jr. invoked Pizza review brings up some questions about how it went down and the Key West drunken pizza hotspot. We also learn about Dale Jr's latest Chevy Silverado and how he decided the wild graphics he put on it. That and much more in this entertaining version of The Dale Jr. Download. Learn more about your ad choices. Visit podcastchoices.com/adchoices

It's Monday 6th September and a breaking news episode on today's podcast. Ariana is currently flying from the Netherlands to Italy to prepare for hosting this weekend's TV coverage, so you've got Martyn to introduce the news today. Well it's the announcement we thought was coming but you never know until it's a done deal. George Russell will be driving the Mercedes-Benz next to Lewis Hamiton and Valtteri Bottas will join the Alfa Romeo Formula 1 team in 2022 at the start of what the Swiss outfit says is a multi-year deal. The Finn's departure from Mercedes has been expected for some weeks, and a return to Williams was also a potential option before it became clear that his destination was Alfa Romeo. Kimi Raikkonen's retirement announcement on Wednesday was the first in a series of pieces of the driver market puzzle fall into place. Confirmation from Mercedes that George Russell is to join the world champion team as replacement for Bottas will follow this week. Bottas is reunited at Alfa Romeo with team principal Fred Vasseur, with whom he worked at ART in F3 in 2009 and 2010, and in GP3 in 2011, when he won the championship. Despite the strong contribution of Bottas over the years, the prospect of promoting Russell from Williams ultimately proved irresistible for Mercedes and team boss Toto Wolff. The Austrian was involved in Bottas's management before a conflict of interest obliged him to step back. Wolff has long stressed that he wanted to ensure that his former protege found a new seat should Russell be given the nod for the Mercedes drive, and said after Bottas's move to Alfa was announced that "he would absolutely have deserved to stay" in 2022. The news that Mercedes driver Valtteri Bottas will join Alfa Romeo next year is the first key move in Formula 1's 2022 driver market. In an exclusive interview with Autosport, team boss Fred Vasseur explains why the Finn he last worked with a decade ago has the traits his team needs for 2022, as F1 enters its brave new era. You can read all of that in the Plus section of Autosport.com. We think it's the best motorsport writing out there, but judge for yourself with half price access. New subscribers who sign up today can use the promo code PODCAST during checkout to save 50% off their first payment.  Go to Autosport.com/plus and click ‘Sign In' at the top of the page, then use promo code PODCAST for that 50% discount. Thanks for listening today, we'll be back soon. Read more: https://www.autosport.com/f1/news/valtteri-bottas-to-drive-for-alfa-romeo-f1-team-in-2022/6661658/ Wolff: Bottas would have deserved 2022 Mercedes F1 drive https://www.autosport.com/f1/news/wolff-says-bottas-would-have-deserved-2022-mercedes-f1-drive/6661703/ Why Alfa Romeo has picked Bottas to be its 2022 F1 "leader" https://www.autosport.com/f1/news/why-alfa-romeo-has-picked-bottas-to-be-its-2022-f1-leader/6661657/

It's good to be back. All MINIs, all the time here this week. I have joined the F56 club, Gabe has added an to his garage, and Todd just ordered 2 JCW MINIs because he says he isn't getting a GP3. We talked about quite a bit this episode, links are below. Don't forget to click over to and check out the products. Cool stuff there for your MINI! Because blank is boring! And you guys keep going to and eventhough we haven't reminded you since last year? , right? Ok, cool. Appreciate you folks sticking around, especially through all of my bullsh*t. We will be getting back to a regular schedule, starting with 2 shows per month. Appreciate your thoughts on any of this, comments are open or you can ping us on or . Please do not message us on Facebook, we aren't monitoring that any longer. If you are following us elsewhere, you can unfollow that page. We won't be sneaking anything there, promise!

In this week's episode, Nathan spoke to Ryan Tveter, Managing Director USA at Veloce, the world's leading esports & racing growth platform.Ryan is himself an internationally accomplished racing driver, having participated in Formula Renault, Formula 3, GP3 and most recently raced for Trident in the 2019 FIA Formula 2 Championship.Ryan told Nathan about how Veloce are changing the esports landscape, being the world's first esports organization to acquire a real-life sporting franchise in Extreme E and partnering with Alfa-Romeo, McLaren and Mercedes. Veloce have also played a major role in the launch of Lando Norris' Quadrant brand.They also discussed the unusual route he took to get into motorsport, the future of F1 esports and much more!

On today’s very special episode, Oli and Matt are joined by F1’s best-connected man: Mark Gallagher. From corporate board rooms, to operations, commentating, and even Hollywood, Mark has done it all. The list of teams and drivers Mark has been involved with is truly staggering. From the likes of Senna, Schumacher,  and Häkkinen, Mark has worked with and been around them all.On the team side Mark worked with Jordan, Jaguar, and subsequently Red Bull.    He founded his own team in Status Grand Prix that competed in GP2, GP3, world endurance and won the A1 Grand Prix in 2009. Oli and Matt are given a brilliant insight to Mark’s perception of drivers like Hamilton and Vettel in the modern age compared to the heroes of old.    Our team gets Mark to open up on the perception of drivers in the social media age. Have we lost some of the ability to TRULY see and know our drivers through modern content creation practices? Are Lewis Hamilton and Sebastian Vettel that dissimilar in their mindset when it comes to the fans in their personal lives?    The panel also does a little bit of deep diving into the corporate side of things by comparing Haas and Aston Martin’s way of doing business. From PR, to sponsorships, to financials a little bit of everything is discussed.Lastly, our trio looks at Red Bull vs Ferrari and how the 2022 regulations could hurt or help the teams. Mark gives his predictions for the 2021 season but gives us a fresh new perspective on how teams may or may not be focusing on the future.   Follow FormulaNerds www.Facebook.com/FormulaNerds www.twitter.com/FormulaNerds www.instagram.com/FormulaNerds www.formulanerds.com

In hour 3 the GP3 gives the top 5 at 5, and the guys play hot take cold take

Peter (@petrol_ped) returns for the second time to tell us what he's been up to in the last year. We chat cars, bikes, podcasting and more. Check out the video here: https://youtu.be/hOwO-8JaS6A Peter's Channel: https://www.youtube.com/user/greavsie6672 Hope You Enjoy, SamSupport The Podcast:https://www.sammoores.com/shop/buy-sam-a-pintPodcast Sponsors:www.TheMarket.co.ukwww.Rimblades.com - Use discount code "CARCHAT" at checkoutShow Notes0:00 - Intro2:55 - What have you been up to?12:01 - Cycling Content and starting a Podcast19:21 - Mini GP322:39 - Electric Car Chat33:39 - Vintage Voltage45:18 - Hendy Performance Focus RS51:12 - Do car journalists buy new cars?1:02:28 - Caterham Racing1:10:04 - Institute of Advanced Motorists Masters Course1:14:39 - Driving the M2 CS1:22:15 - 5 Questions

Peter (@petrol_ped) returns for the second time to tell us what he's been up to in the last year. We chat cars, bikes, podcasting and more. Check out the video here: https://youtu.be/hOwO-8JaS6A Peter's Channel: https://www.youtube.com/user/greavsie6672 Hope You Enjoy, SamSupport The Podcast:https://www.sammoores.com/shop/buy-sam-a-pintPodcast Sponsors:www.TheMarket.co.ukwww.Rimblades.com - Use discount code "CARCHAT" at checkoutShow Notes0:00 - Intro2:55 - What have you been up to?12:01 - Cycling Content and starting a Podcast19:21 - Mini GP322:39 - Electric Car Chat33:39 - Vintage Voltage45:18 - Hendy Performance Focus RS51:12 - Do car journalists buy new cars?1:02:28 - Caterham Racing1:10:04 - Institute of Advanced Motorists Masters Course1:14:39 - Driving the M2 CS1:22:15 - 5 Questions

Alt tegnede lyst for Michael Christensen, der som kartingkører tog sejre og podier internationalt og herhjemme – herunder EM-titlen i 2005 og VM-sølv i 2006. En managerkontrakt med Harald Huysman og Jan Ove Nystuen, der bl.a. havde ført Jenson Button og Kimi Räikkönen frem, og titel som BMW-junior fulgte, og alt tegnede lyst for køreren fra Karlslunde, der havde sigtet rettet mod Formel 1. Men sådan skulle det som bekendt ikke gå for den sympatiske danske verdensmester. Et bagland i absolut topklasse og resultater fra øverste hylde i karting og senere også i Formel BMW, og så gik turen til GP3, en klasse der skulle lede videre til GP2 og Formel 1. Men alt gik galt trods et team ledet af så prominente navne som Mark Webber og Christian Horner, pengene slap op og Christensen karriere kørte af sporet. Men en bekendt fra Formel BMW-dagene var nu rykket til Porsche – og Christensen blev inviteret til en shootout, da det tyske mærke skulle genoptage deres juniorprogram. Danskeren vandt, og resten, som man siger, er nu historie. Det er da lige indtil 2020, hvor Christensen som regerende verdensmester får en fyreseddel – og senere bliver hentet tilbage til Stuttgart-mærket. Hør den åbne og ærlige beretning fra Michael Christensen selv i denne udgave af podcasten Det ternede flag. Bo Baltzer Nielsen og Bo Skovfoged er i studiet med verdensmesteren og Le Mans-vinderen.

The Season Finale! It's the last show of the season and we're joined by Alexander Rossi, the Nevada City born American star, has the rare honour and addition to his CV as a winner of one of the biggest races in the world, if not, THE BIGGEST, the Indy 500. He's won races and Championships in multiple categories, including Formula BMW where he got the most poles and victories and was the youngest open-wheel racing champ in US History. He's had success in GP3, GP2 and has even made it to the “arguably” pinnacle of motor racing in Formula One and even has his own podcast alongside fellow racer, James Hinchcliffe.As we reach the final show of the season we must give our massive thanks to our S6 partners, GridRival, THE place for your fantasy racing. Go download it, NOW here - or join our very own GridRival league here: https://gridrival.app.link/N62I8ox5Reb Subscribe to MotorMouth on YouTube for loads more content: https://bit.ly/3qVXP0R Follow MotorMouth:Twitter - https://twitter.com/MotorMouth_ Instagram - https://www.instagram.com/MotorMouth_official/Facebook - https://www.facebook.com/MotorMouthClub/Website - https://www.motormouth.club/Download our App:iOS - https://apple.co/3scnns2 Android - https://bit.ly/3cf9yU2 Join our 2021 Fantasy #F1 League:https://gridrival.app.link/N62I8ox5Reb Get bonus content on Patreon See acast.com/privacy for privacy and opt-out information.

+++WERBUNG+++ F1 22 ist das offizielle Videospiel zur FIA Formel 1 Weltmeisterschaft von Codemasters und EA Sports. So nah warst du noch nie dran! Noch immersivere Spielmodi, Kompatibilität mit Virtual Reality und dem neuen Modus F1 Life - mehr Formel 1 geht nicht. F1 22 ist ab dem 01.07. erhältlich für PlayStation 5, Xbox Series X|S, PlayStation 4, Xbox One und PC über Origin und Steam. Mehr Infos: F1 22. Starting Grid empfiehlt: ExpressVPN. Wenn du auf kein Rennen der Saison 2022 verzichten möchtest, dann hol dir jetzt ExpressVPN. Als Hörer:in meines Podcasts bekommst du auf dein Jahresabo noch 3 Monate kostenlos oben drauf. Gehe dazu einfach auf expressvpn.com/STARTINGGRID. +++ENDE DER WERBUNG+++ Wir starten in Runde 2 unserer Serie zu den Frauen im Motorsport. Heute wird es international, denn Tatiana Calderon ist zu Gast. Die 27-jährige fährt in der ELMS u.a. mit der Deutschen Sophia Flörsch für das Richard Mille Racing Team und in der japanischen Super Formula. Nebenbei ist sie auch Entwicklungsfahrerin beim Formel 1 Team Alfa Romeo Sauber Orlen. Mit Kevin Scheuren spricht sie heute ausführlich über ihre Karriere, ihre starken und schwachen Momente, Probleme und Chancen und wirft einen Blick voraus auf das, was es für sie noch braucht, um den Traum der Formel 1 wirklich real werden zu lassen. Das Interview ist auf Englisch geführt worden. Aus Kolumbien in die Welt Tatiana Calderon wuchs in Kolumbien auf. Juan Pablo Montoya war und ist dort ein Volksheld, ein Vorbild für den Motorsport. Der ehemalige Formel 1-Fahrer war auch für Calderon eine Inspiration, den harten Weg zur Königsklasse einzuschlagen. Von den nationalen Kartturnieren ihrer Heimat bis zum Aufbruch nach Amerika, in die USA, vergingen einige Jahre. Ihre Schwester war immer an ihrer Seite, entweder in ihrem Team oder als Konkurrentin auf der Strecke. Heute begleitet sie Tatianas Weg als ihre Managerin, ein unzertrennliches Duo. Familie ist auch ein Thema, über das wir heute im Podcast sprechen. In Europa den Durchbruch geschafft Wenn man in die Formel 1 will, muss man zwangsläufig nach Europa kommen. Das war auch Tatiana Calderon klar. Dort lernte sie u.a. Susie Wolff kennen, die für die FIA mittlerweile eine Botschafterin für Frauen im Motorsport ist. Auf dem europäischen Festland und der Insel, in Großbritannien, konnte sie Fuß fassen und erste Erfolge einfahren. Aber es war auch eine schwere Zeit für sie. Weit weg von der Heimat, nur ihre Schwester dabei, die Teams waren ihr nicht immer super wohlgesonnen. Da musste man mentale Stärke aufbauen, um durch diese Täler durchzukommen. Wie sie das geschafft hat, erzählt sie in der heutigen Sendung. Der steinige Weg in die Formel 2 Nach vielen Jahren des Durchboxens und der Entbehrung, aber auch den Erfolgen, kam der Schritt, auf den sie lange gewartet hat. Über diverse Junioserien schaffte sie den Sprung in die Formel 2. 2019 war sie Teamkollegin von Anthoine Hubert beim BWT Arden-Team. Es war eine harte Saison für sie. Nicht nur waren ihre Leistungen nicht auf dem Level, das sie sich selber gesetzt hat, im Spa-Franchorchamps verunglückte Hubert tödlich - ein Schock für die ganze Szene. Sie spricht heute sehr herzlich von Anthoine Hubert, auch im Podcast. Absolute Gänsehaut! 24 Stunden von Le Mans und Japan 2020 konnte sie leider kein Cockpit in der Formel 2 abstauben. Dafür hat sie sich anderen Aufgaben gewidmet. Ihre Leidenschaft für das Endurance-Racing kann sie in der European-Le-Mans-Series ausleben, wo sie für das Richard Mille-Racing Team an den Start geht und zwar in einem Team, bei dem nur Frauen am Steuer sitzen. Ebenso hat sie, wie u.a. bereits Pierre Gasly (AlphaTauri), den Schritt nach Japan gewagt. In der Super Formula ist sie am Start...naja...sie wäre es gerne öfter, aber Corona hat auch diese Saison durcheinandergewürfelt. Wir sprechen aber auch über die neuen Stationen und das Ziel Formel 1, das sie nicht aus den Augen verloren hat. Vielen Dank an Tatiana Calderon für die Zeit und euch viel Vergnügen beim Zuhören. Folgt Tatiana gerne zudem noch bei Facebook und Instagram. Schreibt uns gerne eure Meinung zum Interview und zur Serie. Wir freuen uns! Euer Feedback ist uns wichtig Schickt uns gerne für die nächsten Sendungen eure WhatsApp-Sprachnachricht an folgende Nummer: +49 331 298 50 28 GANZ WICHTIG: bitte sendet an diese Nummer NUR SPRACHNACHRICHTEN ein und beginnt eure Sprachnachricht mit den Worten STARTING GRID und eurem Namen, damit das zugeordnet werden kann! Bitte haltet die Sprachnachrichten bei maximal 1:30 Minute, danke euch. Ihr könnt uns über verschiedene Kanäle erreichen und mich anderen F1-Fans in Verbindung bleiben: Facebook-Seite Facebook-Gruppe Twitter  Telegram-Gruppe Mail YouTube Sehr gerne würden wir auch eure Rezensionen auf iTunes lesen, bitte nehmt euch 3 Minuten Zeit für 5 Sterne und ein paar warme Worte, vielen Dank! Keep Racing! 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.

Wir starten in Runde 2 unserer Serie zu den Frauen im Motorsport. Heute wird es international, denn Tatiana Calderon ist zu Gast. Die 27-jährige fährt in der ELMS u.a. mit der Deutschen Sophia Flörsch für das Richard Mille Racing Team und in der japanischen Super Formula. Nebenbei ist sie auch Entwicklungsfahrerin beim Formel 1 Team Alfa Romeo Sauber Orlen. Mit Kevin Scheuren spricht sie heute ausführlich über ihre Karriere, ihre starken und schwachen Momente, Probleme und Chancen und wirft einen Blick voraus auf das, was es für sie noch braucht, um den Traum der Formel 1 wirklich real werden zu lassen. Das Interview ist auf Englisch geführt worden. Aus Kolumbien in die Welt Tatiana Calderon wuchs in Kolumbien auf. Juan Pablo Montoya war und ist dort ein Volksheld, ein Vorbild für den Motorsport. Der ehemalige Formel 1-Fahrer war auch für Calderon eine Inspiration, den harten Weg zur Königsklasse einzuschlagen. Von den nationalen Kartturnieren ihrer Heimat bis zum Aufbruch nach Amerika, in die USA, vergingen einige Jahre. Ihre Schwester war immer an ihrer ...

Wir starten in Runde 2 unserer Serie zu den Frauen im Motorsport. Heute wird es international, denn Tatiana Calderon ist zu Gast. Die 27-jährige fährt in der ELMS u.a. mit der Deutschen Sophia Flörsch für das Richard Mille Racing Team und in der japanischen Super Formula. Nebenbei ist sie auch Entwicklungsfahrerin beim Formel 1 Team Alfa Romeo Sauber Orlen. Mit Kevin Scheuren spricht sie heute ausführlich über ihre Karriere, ihre starken und schwachen Momente, Probleme und Chancen und wirft einen Blick voraus auf das, was es für sie noch braucht, um den Traum der Formel 1 wirklich real werden zu lassen. Das Interview ist auf Englisch geführt worden. Aus Kolumbien in die Welt Tatiana Calderon wuchs in Kolumbien auf. Juan Pablo Montoya war und ist dort ein Volksheld, ein Vorbild für den Motorsport. Der ehemalige Formel 1-Fahrer war auch für Calderon eine Inspiration, den harten Weg zur Königsklasse einzuschlagen. Von den nationalen Kartturnieren ihrer Heimat bis zum Aufbruch nach Amerika, in die USA, vergingen einige Jahre. Ihre Schwester war immer an ihrer ...

Poor old Harry was laid up in bed for this episode, so Tim is joined by racing driver, trans pioneer and LGBTQ+ spokesperson, Charlie Martin as co-host. Huge thanks to Charlie for jumping in last minute and experiencing what it's like to be on the other side of the mic! We had a chat with Alexander Sims, the 5th Formula E driver we've had on the show, we're slowly working our way through the entire grid! He's a former McLaren Autosport BRDC Young Driver of the Year winner, he's raced in F3, GP3, LMP2 and GTs all over the world before finding himself in Formula E with Andretti and now Mahindra for Season 7. We go back through Alexander's career, his life, his thoughts and opinions and importantly, see how he performs in the famous MotorMouth Quiz, can he beat his new team boss, Dilbagh Gill? For more content and to join the MotorMouth community, download the MotorMouth app:Apple: https://apple.co/2OOB2pR Android: http://bit.ly/2ZnuakcDesktop: https://www.motormouth.club The MotorMouth App is the newest platform where you can find motorsport news, live race times, and discuss your views with fellow motorsport enthusiasts!Give us your feedback across all our social media profiles https://linktr.ee/_motormouth Don't forget to Subscribe to get the latest episodes in your podcast platform! Get bonus content on Patreon See acast.com/privacy for privacy and opt-out information.

Joey Mawson is one of the most exciting talents from Australia, currently trying to break into the European racing scene. Mawson was a 3 x Australian Karting Champion before setting his goals to race in Europe as a teenager.A podium finish at the Rotax World Finals in the UAE, and winning a round at the Under 18 CIK FIA World Championships were highlights before stepping into Formula 4. Joey was able to take it to Mick Schumacher in the German F4 championship beating the German driver to the championship, where he then made the jump into Formula 3 & GP3 following the F1 calendar.Mawson scored a podium in GP3 and then moved to the Porsche SuperCup where he also claimed a maiden podium. Not many teenagers would have the courage and determination to pack their bags and leave their family behind, to pursue their goals like Joey did. A great story of a driver who didn't pave his way from family financial backing, but the talent, desire and never give up attitude.If you wish to follow Joey's journey, be sure to give him a follow:FacebookInstagram

This goes down as one of our favourite ever interviews. There is so much more to Esteban Gutierrez that you know.Esteban started showing potential to race at the top of the sport as soon as he set foot in a kart, he was immediately quick. He's currently the development driver for Mercedes-AMG Petronas Motorsport, to give it its full name. He's found his way there through karting, Formula BMW USA and Europe, GP3, GP2 and of course Formula One with Sauber, Ferrari, Haas and Mercedes, with a little dabble in Formula E and IndyCar.As you'll hear there is something exciting bubbling away in his future and we can't wait to find out what it is!For more content and to join the MotorMouth community, download the MotorMouth app:Apple: https://apple.co/2OOB2pR Android: http://bit.ly/2ZnuakcDesktop: https://www.motormouth.club The MotorMouth App is the newest platform where you can find motorsport news, live race times, and discuss your views with fellow motorsport enthusiasts!Give us your feedback across all our social media profiles:FacebookTwitterInstagramYouTubeDon't forget to Subscribe to get the latest episodes in your podcast platform! Get bonus content on Patreon See acast.com/privacy for privacy and opt-out information.

¡¡¡Bienvenidos a un nuevo episodio de BANDERA A CUADROS!!! En esta ocasión vamos a tener el privilegio de entrevista a la piloto probador de la escudería de F1 Alfa Romeo Sauber y GP3. Dirigen Ángel Castillo y Julio Romero Presenta Ángel Castillo Marcos Música con licencia Creative Common Artísta: Steep y Carlos Saura. Como siempre, esperamos que disfrutéis de este episodio y le deis a Me Gusta en IVOOX, lo compartáis en las redes sociales y si sois de Apple, que nos dejéis una reseña positiva en ITUNES. Os esperamos en http://www.banderaacuaros.com con la mejor información sobre la Formula 1. Medios de contacto: Facebook: https://facebook.com/banderaacuadrospodcast Twitter: BANDERA A CUADROS podcast: @cuadrosbandera Ángel Castillo: @acastillomarcos Julio Romero: @ilovecoches David Moreno: @drizzt699 David Gomez Gallardo: @DavidGmezGall

Subtitle: Everything is Verstappening The Grid Girls catch up to talk about Max Verstappen's record breaking race, Tatiana Calderon's first weekend of GP3 and chat to IndyCar driver and all around #BadassLadyDriver Pippa Mann about the upcoming 100th Indy500.