Podcasts about dut

Tu peux soutenir sur le podcast en mettant 5⭐️ sur Apple Podcasts ou Spotify !Benjamin est l'ancien Head of Design de Matera.Dès la sortie du collège, Benjamin se spécialise dans le Design via un CAP puis un Bac pro. Un parcours professionnalisant qui l'amène à découvrir de nombreuses facettes du design à travers ses stages : imprimerie, covering, web... Constatant l'essor du web, il poursuit en DUT, mais décide ensuite de se concentrer sur la gestion de projet et d'équipe plutôt que d'approfondir ses connaissances techniques déjà solides.Pendant ses études, il travaille pour My Witty Games, éditeur de jeux de société en crowdfunding, gérant l'identité visuelle, le site web et la communication. L'entreprise fermera suite à un conflit avec Asmodee, géant du secteur.Chez Criteo, Benjamin commence par créer des bannières publicitaires avant de s'intéresser à la data et aux aspects business. Sa carrière y évolue rapidement :Head of Design France pour le marché retailDesign Director EMEA d'un nouveau produit de retail mediaCe dernier poste s'avère difficile : départs d'équipiers, arrivée du Covid, mais aussi croissance rapide. Benjamin y développe ses compétences en management d'équipe et en Product Design, positionnant le design comme élément stratégique.Après 8 ans, il rejoint Matera (solution de gestion immobilière) comme Head of Design avec trois missions :Faire rayonner la culture design dans l'entrepriseDévelopper l'équipe DesignStructurer cette équipe en croissanceEnfin, Benjamin nous parle de la suite, car il a quitté Matera pour rejoindre Kolecto…Les ressources de l'épisodeMateraCriteoKolectoOverbookés, Rahaf HarfoushLes autres épisode de Design Journeys#38 Théo Kopf, Brand Designer @ Matera#73 Arthur Foliard, Creative Director @ Koto#76 Théo Rivière, consultant, auteur & éditeur de jeux de société Pour contacter BenjaminLinkedInHébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

Redefining Art & Culture at the KZN Art Gallery Hosts Nzu and Slu speak with DUT exchange students Gabriela Valdespino, Tabea Erhart, and Apath about their creative journeys and the power of cultural exchange. Listen to this thought-provoking episode of the Deeply [Rooted] Show and explore how art transforms communities. 

In der heutigen Podcast-Folge habe ich einen sehr interessanten Gast, der euch von seinem bewegtes Leben erzählen wird. Dut kommt aus dem Südsudan, hat seit dem Alter 10 Jahren seine Mutter nicht regelmäßig gesehen, musste für seine Schulausbildung Schuhe putzen und hat viel Leid erfahren, dabei möchte er sich nur ein besseres Leben erarbeiten und aufbauen. Ich habe ihn bei einem seiner Jobs als Animateur in Ägypten kennen gelernt und wir haben regelmäßig Kontakt gehalten. Ich habe ihm geholfen, werde ihm weiterhin helfen und eure Hilfe wäre mir ein großes Anliegen.

Les Têtes d'affiches de Denise Epoté de TV5 Monde, comme chaque dimanche sur RFI, avec Nicolas Brousse. Au palmarès de cette semaine, deux innovateurs originaires de la République centrafricaine. Notre première tête d'affiche s'appelle Gabino Guerengomba, il est ingénieur en architecture, réseau et en propriété intellectuelle, formé aux États-Unis. Sa start-up « IST » a conçu des panneaux solaires afin de fournir une énergie fiable et un accès à internet. Notre seconde tête d'affiche s'appelle Teddy Kossoko, diplômé de l'Institut universitaire de Blagnac et de l'université de Toulouse, il possède un DUT en informatique et un master en méthodes informatique appliquées à la gestion des entreprises. Sa start-up « Masseka Game Studio » conçoit des jeux vidéo pour promouvoir l'histoire et la culture africaine.

Welcome back everyone to another episode of the Back 9 Mully Podcast! It is just a 3-man group today with Aut, Dut and J Weeksy! We talk about dealing with homeowner problems that seem to never go away... Then we go into story time about a scam call claiming that Dut has been arrested and needs bail to be paid. Detective Aut was on the case!! Then we wrap things up with TGL, PGA tour and Rick Shiels on YouTube golf.Now, go hit some good shots, go hit some bad shots, but always remember to have fun and to always use your Back 9 Mully!

Pour cet épisode 140, j'appelle Simon Coulombier, artisan cadreur installé à Caen.Très jeune Simon s'intéresse à la mécanique du vélo. Il n'hésite pas à démonter son VTT dans le garage de la maison de ses parents en compagnie de sa bande de copains. Après son DUT et avec son diplôme d'ingénieur en poche, il va chercher un emploi dans le monde du vélo. Ses études dans la mécanique ne l'avaient pas passionné sans doute, car son attirance pour le vélo était déjà plus forte que celle de toute autre piste professionnelle. Il réussit enfin à mettre un pied dans l'univers dont il rêve depuis l'enfance. Il est embauché chez Moustache Bikes et s'installe dans les Vosges. Il deviendra concepteur de vélo dans cette entreprise française, qui en 2018, est alors en plein développement.À cette même époque, Simon va découvrir le monde du vélo artisanal qu'il ne connaissait pas du tout. Pour aller plus loin dans la découverte, il s'inscrit à un stage de cadreur chez La Fraise à Roubaix, profitant d'une semaine de vacances. Ce stage va lui permettre d'avancer sur l'usage qu'il pourra faire de ses compétences en matière de conception et son goût pour le travail manuel. Cette découverte va contribuer à lui donner envie de quitter l'ambiance bureau d'études, assis derrière un ordinateur, pour créer lui même un produit qu'il aura conçu et fabriqué entièrement.La dernière étape sera d'apprendre comment créer sa propre entreprise artisanale et de construire des vélos pour ses premiers clients.Je vous invite à écouter le parcours de Simon qui est désormais artisan cadreur à Caen.Internet : https://www.cycles-soca.fr/Instagram : https://www.instagram.com/cycles_soca/Facebook : https://www.facebook.com/cycles.socaHébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

What is going on everybody! We are finally back with another episode! We have missed you and hopefully you have missed us! We dive right into the last golf tourney that Austin and Dut had the pleasure of playing! We then talk about the tough losses of Alabama football. We also give our two cents on how to fix this NIL and Transfer portal in college football. Then we just go on a random tangent of everything under the sun! Now, go hit some good shots, go hit some bad shots, but always remember to have fun and to always use your Back 9 Mully!

Aujourd'hui, nous vous proposons une nouvelle interview du pOD : une rencontre avec Eric Perrin, Responsable communication du Festival Hellfest Open Air. Retrouvez ci-dessous les principaux éléments abordés durant cet épisode de notre podcast dédié au social media, ainsi que différents liens et ressources utiles pour découvrir notre invité et son métier.  Qui est Eric Perrin ?  Pour ce nouvel échange, nous vous proposons de rencontrer Eric Perrin. C'est lui qui se cache derrière, notamment, la stratégie social media du Festival de musiques extrêmes : le Hellfest. Nous sommes allés à sa rencontre pour parler de lui, de son parcours, de son quotidien et de sa relation avec les réseaux sociaux et la musique.  Sa passion pour le métal remonte à l'adolescence. Il se destinait à une carrière dans l'informatique, comme beaucoup d'adolescents fans de jeux vidéo. C'est pourquoi après le Bac, il part en DUT services et réseaux de communication, avec une spécialité en développement web et graphisme. Lors de son premier stage, il mixe ses études et sa passion pour la musique, en participant à l'organisation d'un festival itinérant. Il poursuit ensuite en licence informations et communication et découvre le monde des associations étudiantes. C'est à ce moment-là qu'il commence à apprendre à organiser des concerts : faire une affiche, la programmation, trouver des prestataires techniques, une salle, etc. Puis, lors de son master en communication, il effectue deux stages en community management et c'est son stage de fin d'études qui lui ouvre les portes du Hellfest, en tant qu'assistant chargé de communication et de production. Après plusieurs expériences professionnelles dans le milieu de l'événementiel musical, il est de retour au Hellfest depuis 2020 en tant que Responsable communication. Et croyez-moi, les anecdotes d'Eric sur son métier et son quotidien au Hellfest, sont toutes plus intéressantes les unes que les autres. Les intervenants sur cet épisode de podcast sont : Gwen, chef de projet social media chez Ouest Digital. En plus d'être la Voix du pOD elle est pilote la stratégie social media & social ads de nombreux clients de l'agence Bryan, co-fondateur de l'agence et directeur de clientèle.  Eric, Responsable Communication du Hellfest Open Air Festival  Au programme de cet épisode Vous êtes Community Manager ou Social Media Manager, et vous avez envie de découvrir les parcours professionnels de vos confrères et consœurs ?  Dans cet épisode, voici ce que nous partageons avec vous :  Le parcours d'Eric et comment il en est arrivé à exercer ce métier Son quotidien en tant que Responsable Communication d'un festival qui attire 60 000 personnes par jour Ses missions & son organisation, notamment en matière de réseaux sociaux Ses relations avec ses équipes, prestataires et partenaires  Ce qu'il aime le plus dans son métier Ressources utiles en complément de cet épisode  Le site du Hellfest Le compte Facebook du Hellfest (animé par Eric) Le compte Instagram du Hellfest (animé par Eric) Le compte TikTok du Hellfest (animé par Eric) Le compte Twitch du Hellfest (animé par Eric) Le compte Discord du Hellfest (animé par Eric) La chaîne YouTube du Hellfest (animé par Eric) Vous souhaitez intervenir, vous aussi, intervenir à notre micro ?  Vous êtes communiquant.e ou marketeux.se et le social media management fait partie de votre quotidien professionnel ? Vous aimeriez partager et échanger votre parcours avec vos homologues pour enrichir votre expérience ? Alors, vous êtes le ou la bienvenu.e ! Pour cela, rien de plus simple contactez Gwen sur son profil Linkedin ou par email : gwen[at]ouest.digital 

8ème épisode : Fils de commerçants et passionné d'informatique, Boris a suivi ses premières amours pour le code jusqu'à obtenir un DUT en Informatique. Une première expérience professionnelle dans un cabinet d'expertise comptable l'a incité à plonger dans les livres de comptabilité...

Kültürümüzde "evin ruhunu," sembolize eden Dut ağacını, özellikle de iki türünü konuşuyoruz: Biri, dört bin yıldan fazla süredir ipek endüstrisini besleyen beyaz dut Morus alba ve diğeri lezzetli meyvesiyle karadut Morus nigra.

Auch dieses Jahr war ich auf der FPGA Conference und möchte in dieser Folge berichten. Inhalt der Folge: * Rückblick auf die FPGA Conference 2024 * Besuchte Sessions * Dienstag * Fast data transmission with Artix UltraScale+ via various interfaces * 100GbE from FPGA to Disk * Open-Source FPGA Tools and Frameworks * All FPGAs are equal, but some FPGAs are more equal * Why Should Our Team be Using VHDL+OSVVM for verification? * FPGA Based 400GBit/s Data Recorder - Insight into different pitfalls and design choices * Mittwoch * Verifying a simple DUT (FPGA or module) from scratch with basic verification – for beginners * Verifying a complex DUT in a simple way from scratch * What challenges do we encounter while working at the edge of technology * RTL on a Higher Level: Introducing the Hierarchical FSMD * Constraining Multiple Clock Domains * Donnerstag * MicroBlaze V – the AMD/Xilinx way to do RISC-V * Using OSVVM's AXI4 Verification Component * Perfecting PetaLinux – a hands on tutorial Part 1+2 * Meine Session am Dienstag * Video Stream Verarbeitung im Zynq 7000 * Ingenieure führen Camp * Sommerpause Trage Dich auch gerne in meinen Newsletter ein. Du findest eine Möglichkeit auf der Webseite zu dieser Folge. Der Beitrag IF218 – FPGA Conference 2024 erschien zuerst auf Ingenieurbüro David C. Kirchner.

Welcome back everyone to another great week of the Back 9 Mully Podcast! We start things off all golf with Aut and Dut. Then we rotate things in with the wives. This was such a fun one to do! Then we wrap things up with the listener questions. Thanks again for all the support and make sure to like, share and sub! Now, go hit some good shots, go hit some bad shots, but always remember to have fun and to always use your Back 9 Mully!

Previously Patrick was Operations Director at Innov8; Purchasing and RD Director at Groupe ADF; Operations Director at Uniross; Purchasing Director at Alcatel Mobile Phones and Mechanical Manager at SAGEM.  He has a Masters Degree in Mechanical Engineering from Arts et Metiers Paris Tech – Ecole National Superieure d'Arts et Metiers and an MBA from ESSEC Business School and a DUT, Mechanical from the Universite de Provance

In this episode Sean B and Dut discuss BOTH NCAA Final Fours. Can Purdue Beat UConn? How crazy is the Caitlin Clark effect? Also congrats to Rick Carlisle on 939 wins!

Bugün 2 Nisan 2024 salı #doğatakvimi

In this episode Sean B and Reggie miss Dut! We also talk about the NCAA Tournament, new NFL rules and do some Caitlyn Clark fanboy stuff!

Sean B and Dut sit and discuss a not unusually crazy first round of the tournament.

This week's EYE ON NPI will galvanize your next design, with robust galvanic isolation specifically for I2C devices: we're highlighting the Analog Devices ADuM1252/3 Bidirectional I²C Isolators (https://www.digikey.com/en/product-highlight/a/analog-devices/adum1252-bidirectional-i2c-isolator). They are available in two flavors: as the unidirectional ADuM1253 (https://www.digikey.com/short/0w8fq3w5) and bi-directional ADuM1252 (https://www.digikey.com/short/r4j3tcrf). These little SOIC chips provide trustworthy isolation up to a shocking ±10 kV surge, with pending safety and regulatory approvals, so you can feel confident that your design is created as safe as possible. Digital isolation (https://www.analog.com/en/product-category/isolation.html) is essential when dealing with medical, industrial or robotic designs. For industrial/robotic applications, the motors are very noisy and you want to make sure that there is no direct path for that electrical noise to your delicate sensors or microcontrollers. With medical cases, engineers are often tasked with measuring very fine sensors, with uV signals, and providing repeatable data that is used for life-or-death decisions, while also making sure that the 'DUT' is never exposed to dangerous voltages all in an environment with tons of other equipment, some of which may be misbehaving...that's a lot of pressure! The ADuM1252/3 is specifically designed for isolation of I2C signals: you can't just use 'any' isolator because I2C is a bi-directional data protocol that uses pull-ups on open-drain data and clock lines to communicate from controller and peripheral. The ADuM1252 (https://www.digikey.com/short/r4j3tcrf) has bi-directionality on both SDA and SCL, useful for 'multi-controller' modes or when clock stretching is used. The ADuM1253 (https://www.digikey.com/short/0w8fq3w5) has unidirectional SCL for most common I2C devices, and is a little less expensive. The ADI iCoupler technology uses 'galvanic' isolation, that's not the same as optoisolation! According to ADI, you'll get much better data-rate performance and isolation with galvanic compared to optoisolation. Also, lower power since you don't have to turn on/off an LED. Plus you can also use iCoupler for power transfer, which optoisolation cannot do. (https://www.analog.com/media/en/technical-documentation/frequently-asked-questions/icoupler_faq.pdf) The way iCoupler works is by creating a tiny transformer (https://en.wikipedia.org/wiki/Transformer) with two sets of metal coils, separated by an isolating polyamide layer. For data transfer, little coils are used and for power transfer, bigger coils can handle a couple mA! Of course, if we're using a transformer, you know that DC signals cannot be passed through, only AC; and data has a DC component plus isn't a sine wave. That means that there's also a data-to-AC codec on board that will turn I2C signals to AC, then back to I2C. All this is managed transparently so you don't have to worry about it, just treat it as a single I2C bus. There's also a couple nice extras that are helpful if you're trying to make I2C more fault-tolerant. Pre-charge circuitry and 'stuck' detection allow hot-swapping, either purposeful or accidental. The two isolated sides are not connected together until the Side2 half is in a neutral-bus condition. Since each side is separate, you can also use the ADuM1252/3 (https://www.digikey.com/short/1vbn4hcb) for level shifting: either half can be between 1.7 and 5.5V power and logic. With the fast iCoupler codec, you can get up to 2 MHz clock rate for fast I2C data transfer. If you need iCouplers for other protocols like USB or SPI - Analog devices has those available as well, each version is tuned for the usage so you get the best performance. If you need high performance galvanic isolation for your next I2C design, the Analog Devices ADuM1252/3 Bidirectional I²C Isolators (https://www.digikey.com/en/product-highlight/a/analog-devices/adum1252-bidirectional-i2c-isolator) will do an excellent job at creating a code-transparent galvanic barrier for up to 2 MHz bidirectional I2C communication. And best of all, both the unidirectional ADuM1253 (https://www.digikey.com/short/0w8fq3w5) and bidirectional ADuM1252 (https://www.digikey.com/short/r4j3tcrf) are stock at DigiKey right now for immediate shipment. Order today and you'll be gallivanting your way to iCoupler bliss by tomorrow afternoon. See the ADI video https://www.youtube.com/watch?v=4cH-ym9QJlQ

A bientôt 26 ans, Louise Cervera s'offre des premières : elle a en effet été la première athlète française sélectionnée en voile pour les Jeux olympiques de Paris 2024, en ILCA 6. Elle disputera par conséquent ses premiers JO, elle qui avait eu un avant-goût de ce que représentait cette compétition en étant partenaire d'entraînement de Marie Bolou lors des Jeux de Tokyo. « J'ai adoré cette expérience, je ne me suis jamais sentie dans l'ombre de Marie, elle m'a associée à tout, tout le temps. »Pour la première fois également, Louise Cervera est montée sur un podium européen, en l'occurrence la médaille de bronze des championnats d'Europe disputés à Athènes, quelques semaines après avoir mis le sésame olympique dans sa poche. Elle le dit, « ce n'est qu'une étape », et la spécialiste d'ILCA 6 (ex Laser Radial) n'a pas vraiment eu le temps de rester sur son petit nuage, concentrée sur l'objectif à venir, fin juillet sur le plan d'eau de Marseille.Licenciée au YC de Mandelieu, Louise connaît la Méditerranée par cœur, l'aime au plus profond d'elle-même, tout comme la voile et la compétition, au point de confier : « Plusieurs jours sans naviguer, c'est une torture. » Parallèlement, elle a tracé sa route en faisant un DUT de génie mécanique et productique, avant d'étudier à l'INSA de Lyon, l'objectif qu'elle s'était fixé. Elle mène de front deux projets exigeants et ça tombe bien, la lasériste n'aime pas quand c'est facile…Navigantes est animé par Hélène Cougoule et produit par Tip & Shaft.Diffusé le 6 mars 2024Post production :  Grégoire LevillainGénérique : All the summer girls

Join Kolby and Dut on this episode where they talk super bowl predictions, sports, and bourbon!

Join Kolby and Dut as they talk all things current sports and bourbon!

Dans cet épisode, je reçois Mohamed Boclet. Mohammed grandit à Saint Ouen, seul garçon parmi 6 soeurs ! Ses parents sont issus de l'immigration et n'ont pas fait d'études. Pour autant, ils inculquent très tôt à Mohamed le goût du travail et le sens de l'effort. À l'école, Mohamed rencontre de nombreuses difficultés mais ne lâchera jamais. Malgré sa dyslexie et sa dysorthographie, il travaille dur et repousse ses propres limites. Ses efforts finissent par payer: Mohamed passe son bac, obtient son DUT en étant major de promotion et fini par entrer dans une école d'ingénieur et intègre une entreprise dans le secteur de l'énergie. Ayant des difficultés en prise de parole, Mohamed décide de prendre des cours de théâtre, repoussant définitivement ses croyances limitantes qui lui laissaient croire que ce n'était pas pour lui. Il suit quelques années plus tard des cours de lecture rapide.  Mohamed se passionne pour cette nouvelle discipline, au point qu'il monte une association de lecture rapide et se présente aux championnats du monde une puis deux fois et fini par lire 1 livre par jour pour s'entraîner et parvient à devenir vice champion du monde de lecture rapide mais aussi de mind mapping, une autre discipline qu'il enseigne aujourd'hui. Mohamed a fait plusieurs plateaux TV, deux TEDx, des dizaines de conférences, lui qui était paralysé par l'exercice de prise de parole. Il nous partage ses astuces et ce qui l'a fait progresser. Nous avons aussi parlé de sa formidable aventure avec son livre "Connaissance Illimitée" aux éditions Robert Lafont paru en février dernier et qui rencontre un immense succès. Mohamed nous parle également du développement de son entreprise Nous avons bien sur également parlé d'ambition et de son incroyable projet prévu pour 2024 ! Je ne vous en dit pas plus et vous laisse découvrir le parcours hors normes de mon invité exceptionnel: Mohamed Boclet.    NOTES DE L'ÉPISODE: Le podcast vous plaît ? Prenez 30 secondes pour le noter 5 étoiles sur Apple podcast ou Itunes, et commentez si vous le souhaitez, c'est très précieux pour moi ! 

On today's podcast Dr. Gillett and James O'Hara NP, take a deep dive into Finasteride and Dutasteride.Intro (00:00):DHT Receptors (01:58): The discussion centers around the number of DHT receptors in the body.Net Androgens (02:22): Exploring the concept of net androgens in the body.Fin & Dut and Depression (04:36): Investigating whether Finasteride and Dutasteride cause depression.Erectile Dysfunction (09:30): Discussing the potential relationship between these drugs and erectile dysfunction.Decreased Libido (11:53): Exploring the impact on libido due to Finasteride and Dutasteride.Impaired Spermatogenesis (12:51): Discussing the potential adverse effects on sperm production.Effect on the Liver (15:03): Exploring the impact of these drugs on liver function.Adverse Ocular Effects (16:32): Discussing potential negative effects on the eyes.New Type 3 5-alpha Reductase Deficiency (17:48): Discussing a new type of deficiency related to 5-alpha reductase.Renal Effects (19:25): Exploring potential effects on the kidneys.Diabetes (19:31): Discussing the relationship between these drugs and diabetes.Choosing a Specialist (20:34): Discussing whom to consult regarding these medications.Type 1 vs. Type 2 (26:23): Differentiating between Type 1 and Type 2 conditions.Second Attia Pod (27:37): Referring to a previous podcast episode by Peter Attia.Prostate Cancer (31:26): Discussing the relation between these drugs and prostate cancer.Hair Transplant (35:05): Exploring the option of hair transplant.Risks of Inflated Figures (36:29): Discussing potential risks related to inflated figures in research or statistics.Post-Finasteride Syndrome (PFS) (43:24): Discussing the potential syndrome associated with Finasteride.Fin (MK-906) (55:47): Discussing Finasteride and its identification as MK-906.Dut (Gi 1198745) (57:52): Discussing Dutasteride and its identification as Gi 1198745.Anti-aging (01:01:11): Exploring the potential anti-aging aspects related to these drugs.Studies/References ► https://pubmed.ncbi.nlm.nih.gov/37697052/ ► https://pubmed.ncbi.nlm.nih.gov/34925443/► https://fcdgc.rarediseasesnetwork.org/diseases-studied/srd5a3-cdg► https://pubmed.ncbi.nlm.nih.gov/26390988/► https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7308241/For High-quality labs:► https://gilletthealth.com/order-lab-panels/For information on the Gillett Health clinic, lab panels, and health coaching:► https://GillettHealth.comFollow Gillett Health for more content from James and Kyle► https://instagram.com/gilletthealth► https://www.tiktok.com/@gilletthealth► https://twitter.com/gilletthealth► https://www.facebook.com/gilletthealthFollow Kyle Gillett, MD► https://instagram.com/kylegillettmdFollow James O'Hara, NP► https://Instagram.com/jamesoharanpFor 10% off Gorilla Mind products including SIGMA: Use code “GH10”► https://gorillamind.com/For discounts on high-quality supplements►https://www.thorne.com/u/GillettHealth#podcast #finasteride #hairloss #hormones #pfs #dutasterideAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

Join Kolby and Dut as they open with their toasts, give out some scumbag awards and then talk The Masters.

Join Kolby and Dut as they taste and rate Rabbit Hole Cavehill

Join Kolby and Dut as they toast some amazing accomplishments, hand out some worthy scumbag awards, and talk current events in the world of sports.

Join Kolby and Dut as they rate the Rabbit Hole Heigold

Join Kolby and Dut as they give their opening toasts, handout their scumbags of the week awards and talk the week in sports.

Join Kolby and Dut as they do a blind taste test of the Southern Star Paragon Series

Join Kolby and Dut as they taste and rate a 12 year old Weller.

Episode 7. We Still Had HOPE! Rich and J Weeksy are back this week from their cruise vacation to join us in Fort Morgan for a variety packed episode. We have finally made it to Master's Week. We dive a little bit into the traditions that the Masters offers. We also talk about playing golf on the beach, the Pink Pony, how we deal with awkward encounters, favorite golf beverages, Rich beat Dut in a golf match, and we also talk about our favorite vacations over the years. Now, go hit some good shots, go hit some bad shots, but always rememeber to have fun and to always use your Back 9 Mully!

Join Kolby and Dut as they give their opening toasts, hand out their scumbags of the week and discuss the NCAA Tournament, World Baseball Classic, and a little football.

Join Kolby and Dut as they taste and rate Southern Star Paragon

Join Kolby and Dut as they taste and rate Southern Star Paragon Single Barrel.

Join Kolby and Dut as they give their opening toasts, name their scumbags of the week, and talk College Basketball

Join Kolby and Dut as they open with a toast, name their Scumbags of the week, and discuss the current events in sports. This week the guys talk about how the media sucks.

Join Kolby and Dut as they toast a local poker player, give out their scumbags of the week and then play a round of Who Ya Got?

Join Kolby and Dut as they taste and rate the Southern Distilling Company's Souther Star Paragon Bottled in Bond Bourbon

Dustin Arp is a BMX rider and filmer from Denver, CO. He's made 2 full length videos (Good Day Bad Day & Dut's Comp)... and he is a huge part of the scene out there in the mile high city. Spot master, x-up grind guru, and really fun dude to be around. Dustin also had a section in Scott Marceau's epic full length video "AANGLES"... and in the middle of this episode we watch that section together. Kanode Knows is brought to you by DIGBMX.

Join Kolby and Dut as they toast some top performances, hand out scumbag awards and talk all things sports.

Join Kolby and Dut as they taste and rate a Peerless Small Batch Bourbon

Join Kolby and Dut as they toast TB12, give their Scumbags of the Week, and then discuss the week in sports.

Join Kolby and Dut as they discuss, taste and rate the Colonel Taylor Small Batch Bourbon

Join Kolby and Dut as they toast some NFL coaches, the passing of a hockey legend, and a golfer. Then they have some fun with their scumbags of the week. They finish the podcast talking NFL Conference Championships.

Join Kolby and Dut as they discuss, taste, and rate Duke Kentucky Straight Bourbon.

About JeremyJeremy is the Director of DevRel & Community at CircleCI, formerly at Solace, Auth0, and XDA. He is active in the DevRel Community, and is a co-creator of DevOpsPartyGames.com. A lover of all things coffee, community, open source, and tech, he is also house-broken, and (generally) plays well with others.Links Referenced: CircleCI: https://circleci.com/ DevOps Party Games: https://devopspartygames.com/ Twitter: Iamjerdog LinkedIn: https://www.linkedin.com/in/jeremymeiss/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored by our friends at Logicworks. Getting to the cloud is challenging enough for many places, especially maintaining security, resiliency, cost control, agility, etc, etc, etc. Things break, configurations drift, technology advances, and organizations, frankly, need to evolve. How can you get to the cloud faster and ensure you have the right team in place to maintain success over time? Day 2 matters. Work with a partner who gets it - Logicworks combines the cloud expertise and platform automation to customize solutions to meet your unique requirements. Get started by chatting with a cloud specialist today at snark.cloud/logicworks. That's snark.cloud/logicworksCorey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I generally try to have people that I know in the ecosystem on this show from time to time, but somehow today's guest has never made it onto the show. And honestly, I have no excuse other than that, I guess I just like being contrary about it. Jeremy Meiss is the Director of DevRel and Community at CircleCI. Jeremy, thank you for finally getting on the show.Jeremy: Hey, you know what? I woke up months and months ago hoping I would be able to join and never have, so I appreciate you finally, you know, getting that celestial kick in the ass.Corey: I love the fact that this is what you lie awake at night worrying about. As all people should. So, let's get into it. You have been at CircleCI in their DevRel org—heading their DevRel org—for approximately 20 years, but in real-time and non-tech company timeframes, three years. But it feels like 20. How's that been? It's been an interesting three years, I'll say that much with the plague o'er the land.Jeremy: Yes, absolutely. No, it was definitely a time to join. I joined two weeks before the world went to shit, or shittier than it already was. And yeah, it's been a ride. Definitely see how everything's changed, but it's also been one that I couldn't be happier where I'm at and seeing the company grow.Corey: I've got to level with you. For the longest time, I kept encountering CircleCI in the same timeframes and context, as I did Travis CI. They both have CI in the name and I sort of got stuck on that. And telling one of the companies apart from the other was super tricky at the time. Now, it's way easier because Travis CI got acquired and then promptly imploded.Security issues that they tried to hide left and right, everyone I knew there long since vanished, and at this point, it is borderline negligence from my point of view to wind up using them in production. So oh, yeah, CircleCI, that's the one that's not trash. I don't know that you necessarily want to put that on a billboard somewhere, but that's my mental shortcut for it.Jeremy: You know, I'm not going to disagree with that. I think, you know, it had its place, I think there's probably only one or two companies nowadays actually propping it up as a business, and I think even they are actively trying to get out of it. So yeah, not going to argue there.Corey: I have been on record previously as talking about CI/CD—Continuous Integration slash Continuous Deployment—or for those who have not gone tumbling down that rabbit hole, the idea that when you push a commit to a particular branch on Git—or those who have not gotten to that point, push the button, suddenly code winds up deploying to different environments, occasionally production, sometimes staging, sometimes development, sometimes by accident—and there are a bunch of options in that space. AWS has a bunch of services under their CodeStar suite: CodeBuild, CodeDeploy, CodePipeline, and that's basically there as a marketing exercise by CI/CD companies that are effective because after having attempted to set those things up with the native offerings, you go scrambling to something else, anything else. GitHub Actions has also been heavily in that space because it's low friction to integrate, it's already there in GitHub, and that's awesome in some ways, terrible in others. But CircleCI has persistently been something that I see in a lot of different environments, both the open-source world, as well as among my clients, where they are using you folks to go from developer laptops to production safely and sanely.Jeremy: Absolutely, yeah. And I think that's one thing for us is, there's a niche of—you know, you can start if you're into AWS or you're into Google, or you're in—any of those big ecosystems, you can certainly use what they have, but those are always, like, add-on things, they're always like an afterthought of, “Oh, we're going to go add this,” or, “We're going to go add that.” And so, I think you adequately described it of, you know, once you start hitting scale, you're eventually going to start to want to use something, and I think that's where we generally fit in that space of, you know, you can start, but now you're going to eventually end up here and use best-in-class. I spent years Auth0 in the identity space, and it was the same kind of boat is that, you know, sure you can start with hopefully not rolling your own, but eventually you're going to end up wanting to use something best-in-class that does everything that you want it to do and does it right.Corey: The thing that just completely blows my mind is how much for all these companies, no matter who they are and how I talk to them, everyone talks about their CI/CD flow with almost a sense of embarrassment. And back in the days when I was running production environments, we use Jenkins as sort of a go-to answer for this. And that was always a giant screaming exemption to the infrastructure-as-code approach because you could configure it via the dashboard and the web interface and it would write that out as XML files. So, you wound up with bespoke thing lots of folks could interact with in different ways, and oh, by the way, it has access into development, staging, and production. Surely, there will be no disasters that happened as a result of this.And that felt terrible. And now we've gotten into a place where most folks are not doing that anymore, at least with the folks that I talk to, but I'm still amazed by how few best practices around a lot of this stuff has really emerged. Every time I see a CI/CD pipeline, it feels like it is a reimplementation locally of solving a global problem. You're the director of DevRel and have been for a few years now. Why haven't you fixed this yet?Jeremy: Primarily because I'm still stuck on the fact you mentioned, pushing a button and getting to XML. That just kind of stuck me there and sent me back that I can't come up with a solution at this point.Corey: Yeah, it's the way that you solve the gap—the schism as it were—between JSON and YAML. “Cool, we're going to use XML.” And everyone's like, “Oh, God, not that.” It's like, “Cool, now you're going to settle your differences or I'm going to implement other things, too.”Jeremy: That's right, yeah. I mean, then we're going to go use some bespoke company's own way of doing IAC. No, I think there's an element here where—I mean, it goes back to still using best-in-class. I think Hudson, which eventually became Jenkins, after you know, Cisco—was it Cisco? No, it was Sun—after Sun, you know, got their hands all over it, it was the thing. It's kind of, well, we're just going to spin this up and do it ourselves.But as the industry changes, we do more and more things on the cloud and we do it primarily because we're relocating the things that we don't want to have to manage ourselves with all of the overhead and all of the other stuff. We're going to go spit it over to the cloud for that. And so, I think there's been this shift in the industry that they still do, like you said, look at their pipelines with a little bit of embarrassment [laugh], I think, yeah. I chuckle when I think about that, but there is a piece where more and more people are recognizing that there is a better way and that you can—you don't have to look at your pipelines as this thing you hate and you can start to look at what better options there are than something you have to host yourself.Corey: What I'm wondering about now, though, because you've been fairly active in the space for a long time, which is a polite way of saying you have opinions—and you should hear the capital O and ‘Opinions' when I say it that way—let's fight about DevRel. What does DevRel mean to you? Or as I refer to it, ‘devrelopers?'Jeremy: Uh, devrelopers. Yes. You know, not to take from the standard DevOps answer, but I think it depends.Corey: That's the standard lawyer answer to anything up to and including, is it legal for me to murder someone? And it's also the senior consultant answer, to anything, too, because it turns out the world is baked and nuanced and doesn't lend itself to being resolved in 280 characters or less. That's what threads are for.Jeremy: Right [laugh]. Trademark. That is ultimately the answer, I think, with DevRel. For me, it is depending on what your company is trying to do. You ultimately want to start with building relationships with your developers because they're the ones using your product, and if you can get them excited about what they're doing with your product—or get excited about your product with what they're doing—then you have something to stand on.But you also have to have a product fit. You have to actually know what the hell your product is doing and is it going to integrate with whatever your developers want. And so, DevRel kind of stands in that gap that says, “Okay, here's what the community wants,” and advocates for the community, and then you have—it's going to advocate for the company back to the community. And hopefully, at the end of the day, they all shake hands. But also I've been around enough to recognize that there comes that point where you either a have to say, “Hey, our product for that thing is probably not the best thing for what you're trying to do. Here, you should maybe start at this other point.”And also understanding to take that even, to the next step to finish up the answer, like, my biggest piece now is all the fights that we have constantly around DevRel in the space of what is it and what is it not, DevRel is marketing. DevRel is sales. DevRel is product. And each of those, if you're not doing those things as a member of the company, you're not doing your job. Everybody in the company is the product. Everybody in the company is sales. Everybody in the company is marketing.Corey: Not everyone in the company realizes this, but I agree—Jeremy: Yes.Corey: Wholeheartedly.Jeremy: Yes. And so, that's where it's like yes, DevRel is marketing. Yes, it is sales. Because if you're not out there, spreading whatever the news is about your product and you're not actually, you know, showing people how to use it and making things easier for people, you're not going to have a job. And too often, these companies that—or too often I think a lot of DevRel teams find themselves in places where they're the first that get dropped when the company goes through things because sometimes it is just the fact that the company has not figured out what they really want, but also, sometimes it's the team hasn't really figured out how to position themselves inside the business.Corey: One of the biggest, I'll call it challenges that I see in the DevRel space comes down to defining what it is, first and foremost. I think that it is collectively a mistake for an awful lot of practitioners of developer relations, to wind up saying first and foremost that we're not marketing. Well, what is it that you believe that marketing is? In fact, I'll take it a step beyond that. I think that marketing is inherently the only place in most companies where we know that doing these things leads to good results, but it's very difficult to attribute or define that value, so how do we make sure that we're not first up on the chopping block?That has been marketing's entire existence. It's, you know that doing a whole bunch of things in marketing will go well for you, but as the old chestnut says, half your marketing budget is wasted and you'll go broke figuring out which half it is.Jeremy: Yeah. And whenever you have to make cuts, generally, they always, you know, always come to the marketing teams because hey, they're the ones spending, you know, millions of dollars a quarter on ads, or whatever it is. And so yeah, marketing has, in many ways figured this out. They're also the team that spends the most money in a company. So, I don't really know where to go with that isn't completely off the rails, but it is the reality. Like, that's where things happen, and they are the most in touch with what the direction of the company is going to ultimately be received as, and how it's going to be spoken about. And DevRel has great opportunities there.Corey: I find that when people are particularly militant about not liking sales or marketing or any other business function out there, one of the ways to get through them is to ask, “Great. In your own words, describe to me what you believe that department does. What is that?” And people will talk about marketing in a bunch of tropes—or sales in a bunch of tropes—where it is the worst examples of that.It's, “Terrific, great. Do you want me to wind up describing what you do as an engineer—in many cases—in the most toxic stereotype of Uber and 2015-style engineer I can come up with?” I think, in most cases if we're having a conversation and I haven't ended it by now, you would be horrified by that descriptor. Yeah. Not every salesperson is the skeezy used car salesman trying to trick you into something awful. Actual selling comes down to how do we wind up taking your pain away. One of my lines is, “I'm a consultant. You have problems and money. I will take both.”Jeremy: That's right [laugh]. Yeah, that's right.Corey: If you don't have a painful problem, I have nothing to sell you and all I'm doing is wasting my breath trying.Jeremy: Yeah, exactly. And that's where—I'll say it two ways—the difference between good marketing teams are, is understanding that pain point of the people that they're trying to sell to. And it's also a difference between, like, good and bad, even, DevRel teams is understanding what are the challenges that your users are having you're trying to express to, you're trying to fix? Figure that out because if you can't figure that out, then you or your marketing team are probably soon to be on the block and they're going to bring someone else in.Corey: I'm going to fight you a little bit, I suspect, in that a line I've heard is that, “Oh, DevRel is part of product because we are the voice of the community back into the development cycle of what product is building.” And the reason that I question that is I think that it glosses over an awful lot of what makes product competent as a department and not just a function done by other people. It's, “Oh, you're part of the product. Well, great. How much formal training have you had as part of your job on conducting user research and interviews with users and the rest?”And the answer invariably rounds to zero and, okay, in other words, you're just giving feedback in a drive-by fashion that not structured in any way and your product people are polite enough not to call you out on it. And that's when the fighting and slapping begins.Jeremy: Yeah. I don't think we're going to disagree too much there. I think one of the challenges, though, is for the very reason you just mentioned, that the product teams tend to hear your product sucks. And we've heard all the people telling us that, like, people in the community say that, they hear that so much and they've been so conditioned to it that it just rolls off their back, like, “Okay, whatever.” So, for DevRel teams, even if you're in product, which we can come back to that, regardless of where you're at, like, bringing any type of feedback you bring should have a person, a name associated with it with, like, Corey at Duckbill Group hates this product.Corey: Uh-oh [laugh]. Whenever my name is tied to feedback, it never goes well for me, but that will teach me eventually, ideally, to keep my mouth shut.Jeremy: Yeah. Well, how's that working for you?Corey: I'll let you know if it ever happens.Jeremy: Good. But once you start making the feedback like an actual person, it changes the conversation. Because now it's like, oh, it's not this nebulous, like, thing I can not listen to. It's now oh, it's actually a person at a specific company. So, that's one of the challenges in working with product that you have to overcome.When I think about DevRel in product, while I don't think that's a great spot for it, I think DevRel is an extension of product. That's part of where that, like, the big developer experience craze comes from, and why it is a valuable place for DevRel to be able to have input into is because you tend to be the closest to the people actually using the product. So, you have a lot of opportunities and a big surface area to have some impact.Corey: This episode is sponsored in part by our friends at Strata. Are you struggling to keep up with the demands of managing and securing identity in your distributed enterprise IT environment? You're not alone, but you shouldn't let that hold you back. With Strata's Identity Orchestration Platform, you can secure all your apps on any cloud with any IDP, so your IT teams will never have to refactor for identity again. Imagine modernizing app identity in minutes instead of months, deploying passwordless on any tricky old app, and achieving business resilience with always-on identity, all from one lightweight and flexible platform.Want to see it in action? Share your identity challenge with them on a discovery call and they'll hook you up with a complimentary pair of AirPods Pro. Don't miss out, visit Strata.io/ScreamingCloud. That's Strata dot io slash ScreamingCloud.Corey: I think that that is a deceptively nuanced statement. One of the things I learned from an earlier episode I had with Dr. Christina Maslach, is contributors to occupational burnout, so much of it really distills down—using [unintelligible 00:16:35] crappy layman's terms—to a lack of, I guess what I'm going to call relevance or a lack—a feeling like you are not significant to what the company is actually doing in any meaningful way. And I will confess to having had a number of those challenges in my career when I was working in production environments because, yeah, I kept the servers up and the applications up, but if you really think about it, one of the benefits of working in the system space—or the production engineers base, or DevOps, or platform engineering, or don't even start with me these days—is that what you do conveys almost seamlessly from company to company. Like, the same reason that I can do what I do now, I don't care what your company does, necessarily, I just know that the AWS bill is a bounded problem space and I can reason about it almost regardless of what you do.And if I'm keeping the site up, okay, it doesn't matter if we're streaming movies or selling widgets or doing anything, just so long as I don't find that it contradicts my own values. And that's great, but it also is isolating because you feel like you're not really relevant to the direction of what the company actually does. It's, “Okay, so what does this company do?” “We make rubber bands,” and well, I'm not really a rubber band connoisseur, but I could make sure that the website stays up. But it just feels like there's a disconnect element happening.Jeremy: That is real. It is very real. And one of the ways that I tried to kind of combat that, and I help my team kind of really try and keep this in mind, is we try to meet as much as possible with the people that are actually doing the direction, whether it be product marketing, or whether it's in product managers, or it's even, you know, in engineering is have some regular conversations with what we do as a company. How are we going to fit with that in what we do and what we say and all of our objectives, and making sure that everything we do ties to something that helps other teams and that fits within the business and where it's going so that we grow our understanding of what the company is trying to do so that we don't kind of feel like a ship that's without a sail and just floating wherever things go.Corey: On some level, I am curious as to what you're seeing as we navigate this—I don't know if it's a recession,' I don't know if it's a correction; I'm not sure what to call it—but my gut tells me that a lot of things that were aimed at, let's call it developer quality of life, they were something of a necessity in the unprecedented bull market that we've seen for the last decade at some point because most companies cannot afford to compete with the giant tech company compensation packages, so you have to instead talk about quality of life and what work-life balance looks like, and here's why all of the tools and processes here won't drive you to madness. And now it feels like, “Oh, we don't actually have to invest in a lot of those things, just because oh yeah, like, the benefits here are you're still going to be employed next week. So, how about that?” And I don't think that's a particularly healthy way to interact with people—it's certainly not how I do—but it does seem that worrying about keeping developers absolutely thrilled with every aspect of their jobs has taken something of a backseat during the downturn.Jeremy: I don't know. I feel like developer satisfaction is still an important piece, even though, you know, we have a changing market. And as you described, if you're not happy with the tool you're using, you're not going to be as productive than using the tool or using—you know, whether it's an actual developer productivity tool, or it's even just the fact that you might need two monitors, you're not going to be as productive if you're not enjoying what you're doing. So, there is a piece of it, I think, the companies are recognizing that there are some tools that do ultimately benefit and there's some things that they can say, we're not going to invest in that area right now. We're good with where we're at.Corey: On some level, being able to say, “No, we're not going to invest in that right now,” is the right decision. It is challenging, in some cases, to wind up talking to some team members in some orgs, who do not have the context that is required to understand why that decision is being made. Because without context, it looks like, “Mmm, no. I'm just canceling Christmas for you personally this year. Sorry, doesn't it suck to be you? [singing] Dut, dut.” And that is very rarely how executives make decisions, except apparently if they're Elon Musk.Jeremy: Right. Well, the [Muskrat 00:21:23] can, you know, sink any company—Corey: [laugh].Jeremy: — and get away with it. And that's one thing I've really been happy with where I'm at now, is you have a leadership team that says, “Hey, here's where things are, and here's what it looks like. And here's how we're all contributing to where we're going, and here's the decisions we're going to make, and here's how—” they're very open with what's going on. And it's not a surprise to anybody that the economic time means that we maybe can't go to 65 events next year. Like, that's just reality.But at the end of the day, we still have to go and do a job and help grow the company. So, how can we do that more efficiently? Which means that we—it leaves it better to try and figure that out than to be so nebulous, with like, “Yep, nope. You can't go do that.” That's where true leadership comes to is, like, laying it out there, and just, you know, getting people alongside with you.Corey: How do you see DevRel evolving? Because I think we had a giant evolution over the past few years. Because suddenly, the old vision of DevRel—at least in some quarters, which I admit I fell a little too deeply into—was, I'm going to go to all the conferences and give all of the talks, even though most of them are not related to the core of what I do. And maybe that's a viable strategy; maybe it's not. I think it depends on what your business does.And I don't disagree with the assertion that going and doing something in public can have excellent downstream effects, even if the connection is not obvious. But suddenly, we weren't able to do that, and people were forced to almost reinvent how a lot of that works. Now, that the world is, for better or worse, starting to open up again, how do you see it evolving? Are we going right back to a different DevOps days in a different city every week?Jeremy: I think it's a lot more strategic now. I think generally, there is less mountains of money that you can pull from to go and do whatever the hell you want. You have to be more strategic. I said that a few times. Like, there's looking at it and making sure, like, yeah, it would be great to go and, you know, get in front of 50,000 people this quarter or this year, whatever you want to do, but is that really going to move the bottom line for us? Is that really going to help the business, or is that just helping your Delta miles?What is really the best bang for the buck? So, I think DevRel as it evolves, in the next few years, has to come to a good recognition moment of we need to be a little bit more prescriptive in how we do things within our company and not so willy-nilly return to you know, what we generally used to get away with. That means you're going to see a lot more people have to be held to account within their companies of, is what you're doing actually match up to our business goal here? How does that fit? And having to explain more of that, and that's, I think, for some people will be easy. Some people are going to have to stretch that muscle, and others are going to be in a real tough pickle.Corey: One last topic I want to get into with you is devopspartygames.com, an online more or less DevOps, quote-unquote, “Personality” assortment of folks who wind up playing online games. I was invited once and promptly never invited back ever again. So first, was it something I said—obviously—and two what is that and how—is that still going in this post-pandemic-ish era?Jeremy: I like how you answered your own question first; that way I don't have to answer it. The second one, the way it came about was just, you know, Matty and I had started missing that interaction that we would tend to have in person. And so, one of the ways we started realizing is we play these, you know, Jackbox games, and why can't we just do this with DevOps tech prompts? So, that's kind of how it kicked off. We started playing around doing it for fun and then I was like, “You know, we should—we could do this as a big, big deal for foreseeable future.”Where's that now is, we actually have not done one online for—what is it? So probably, like, eight, nine months, primarily because it's harder and harder to do so as everybody [laugh]—we're now doing a little bit more travel, and it's hard to do those—as you know, doing podcasts, it takes a lot of work. It's not an easy kind of thing. And so, we've kind of put that on pause. But we actually did our first in-person DevOps Party Games at DevOpsDays Chicago recently, and that was a big hit, I think, and opportunity to kind of take what we're doing virtually, and the fun and excitement that we generally would have—relatively half-drunk—to actually doing it actually in-person at an event. And in the different—like, just as giving talks in person was a different level of interaction with the crowd, the same thing is doing it in person. So, it was just kind of a fun thing and an opportunity maybe to continue to do it in person.Corey: I think we all got a hell of a lot better very quickly at speaking to cameras instead of audiences and the rest. It also forced us to be more focused because the camera gives you nothing in a way that the audience absolutely does.Jeremy: They say make love to the camera, but it doesn't work anyways.Corey: I really want to thank you for spending as much time as you have talking to me. If people want to learn more about who you are and what you're up to, where should they go?Jeremy: Well, for the foreseeable future, or at least what we can guess, you can find me on the Twitters at @Iamjerdog. You can find me there or you can find me at, you know, LinkedIn, at jeremymeiss, LinkedIn. And you know, probably come into your local DevOpsDays or other conference as well.Corey: Of course. And we will, of course, put links to that in the show notes.Jeremy: Excellent.Corey: Thank you so much for being so generous with your time. It is always appreciated. And I do love talking with you.Jeremy: And I appreciate it, Corey. It was great beyond, finally. I won't hold it against you anymore.Corey: Jeremy Meiss, Director of DevRel at CircleCI. 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, irritated comment talking about how CI/CD is nonsense and the correct way to deploy to production is via the tried-and-true method of copying and pasting.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.

Join Kolby and Dut as the taste and rate Elvis Tiger Man Straight Tennessee Whiskey

Join Kolby and Dut as they toast Anton Walkes and Chris Ford, give out their scumbags of the week and talk NFL playoffs.

Join Kolby and Dut as they taste and rate the Michter's Small Batch Straight Kentucky Bourbon