Podcasts about Argentina

Download this set😎👉🏻: www.techno-livesets.com This week on Drumcode Radio Live we have a Flug mix from Buenos Aires, Argentina, to celebrate his release ‘Altered Existence I' on DCLTD Planetary Assault Systems – Rip the Cut (Dubfire Remix) [Mote Evolver] Deano (ZA) – The Oldowan (Mark Broom Remix) [Hardgroove] Truncate – The Drill [Truncate] Siasia, Peter Fern – Kronos (Original […] Subscribe to listen to Techno music, Tech House music, Deep House, Acid Techno, and Minimal Techno for FREE.

Investigadores chilenos y franceses estudian la extraordinaria resistencia de las plantas que crecen en la zona más árida del mundo: el desierto de Atacama del norte de Chile. Una tierra inhóspita pero que resguarda misterios biológicos que podrían ser útiles para mejorar la resistencia de los cultivos agrícolas a la sequía. En el marco de la COP15 sobre la Desertificación, que tiene lugar este año Abiyán, Costa de Marfil, la comunidad internacional busca hacer frente al creciente empobrecimiento de los suelos debido al cambio climático. En paralelo, científicos chilenos, asociados con expertos del centro de investigación de agronomía francés INRAE, ponen la lupa en el desierto de Atacama. Pese a ser una de las regiones más inhóspita del mundo por su aridez, su radiación extrema y sus oscilaciones de temperaturas, el desierto de Atacama resguarda una flora que crece entre 2.500 y 4.600 metros. Rodrigo Gutiérrez, doctor en biología e investigador en la Universidad Católica de Chile, comparte con RFI los procesos de un prometedor estudio de la resistencia de las plantas a condiciones extremas. Los científicos esperan poder adaptar las técnicas de resistencia de las plantas desérticas a la agricultura. RFI: ¿Por qué estudiar las plantas del desierto? Rodrigo Gutiérrez: “En el escenario de cambio climático actual, debido al calentamiento global, las predicciones que se han hecho por los paneles internacionales indican que va a haber un aumento de la desertificación a nivel mundial. En particular las zonas de los subtrópicos van a ser las más afectadas. Y países como Argentina, Chile vivirán con más fuerza estos procesos de desertificación. Si uno piensa en entender cómo la vida puede soportar estas condiciones de aridez cada más frecuente, ir a un lugar donde los organismos han experimentado condiciones de aridez extrema por millones de años nos pareció que era una buena idea. Para usar como laboratorio natural el desierto más antiguo del planeta. Existe una diversidad vegetal que se ha estudiado muy poco. Se sabe de sus descripciones botánicas, pero más allá de eso, la gran mayoría de ellas no se han estudiado. Hay una mina de oro desde el punto de vista genético y biológico que está esperando que lo caractericemos. RFI: ¿De qué especies se trata? Rodrigo Gutiérrez: En esta década con un poquito más de estudios, hemos identificado cerca de 78 especies. De esas, hay 32 que son las más importantes desde el punto de vista ecológico por su abundancia y su distribución. La gran mayoría son angiosperma, plantas que florecen, y dependiendo a qué altura uno este, se cambia el paisaje. En la parte alta domina el pasto, la zona intermedia hay arbustos y la parte más baja, a medida que uno se acerca hacia el desierto absoluto donde no hay vida, está dominado por plantas anuales y suculentas. Entre los 2.400 y los 4.600 metros es donde se concentra la vida vegetal. RFI: ¿Cuál es el método empleado? Rodrigo Gutiérrez: Nos hemos enfocado en tratar de entender los mecanismos que les permiten a estas especies sobrevivir del punto de vista molecular y evolutivo. Lo que hemos caracterizado es qué genes tienen estas especies. Tratando de entender cómo los genes han evolucionado en estas especies confiriendo capacidad adaptativa. Entonces nuestro foco es, a partir de lo que pasa a nivel molecular, tratar de entender los procesos biológicos que contribuyen a la sobrevida de estas especies en las condiciones desérticas. También los suelos son muy pobres y la radiación solar es realmente muy alta. RFI: ¿Y cómo se adaptan concretamente estas plantas? Rodrigo Gutiérrez: La primera etapa fue la caracterización de la biodiversidad. En ambientes extremos no es tan simple. Tomó varios años entender realmente qué especies hay. Hicimos una reconstrucción de los últimos 30.000 años de la flor en Atacama utilizando los registros fósiles. La segunda parte tenía que ver con entender a nivel molecular cuáles eran los mecanismos involucrados. Y tenemos identificados procesos que tienen que ver con cambios en las secuencias de las proteínas que hacen trabajos de manera más eficientes que les permite a las plantas sobrevivir. Y la tercera etapa, en la que estamos ahora, es seleccionar algunos de estos procesos moleculares para tratar de entenderlos con más detalles y ver si es posible tomar lo que hemos aprendido y llevarlo a plantas de interés agronómico y ver si podemos mejorarlas de alguna manera. Hay otra parte del trabajo que estamos haciendo, que tiene que con rescatar algunas de estas especies por su valor propio. Muchas de estas especies eran utilizadas por los pueblos originarios, por ejemplo, como alimentos, y estas tradiciones están un poco olvidadas. Y creemos que hay mucho potencial en algunas de estas especies como la quínoa, el maqui o el calafate que son especies que eran propias de esta zona, consumidas por los pueblos originarios pero que se ha perdido un poco la historia.

Patagonia ambassador, writer, and fly fisherman Dylan Tomine chats with Trey Elling about HEADWATERS: THE ADVENTURES, OBSESSION, AND EVOLUTION OF A FLY FISHERMAN. Topics include: What he loves so much about fly-fishing (1:49) The allure of steelhead trout (6:24) Why he's a catch-and-release fly fisherman (7:32) Drinking his yerba mate tea out of a dried goat scrotum in Argentina (8:39) The importance of the Skykomish River (11:42) Reasons for the steelhead population plummeting in the Skykomish (12:53) Whether the federal government is helping conserve steelhead populations (16:12) Viable solutions to help steelhead populations rebound (17:17) The prefect fly-fishing conditions (21:04)

Lo esencial que debes saber: Analizan el presente y futuro del audio en ‘Estación Podcast'. Apple Podcasts permitirá a los creadores subir, gestionar y distribuir un pódcast de subscripción a través de proveedores externos que han seleccionado. La publicidad en pódcast sigue creciendo. La comedia y las noticias, las categorías más populares entre los anunciantes de pódcast. Los grupos de radio Univision y Cumulus detallan planes de pódcast en IAB Upfront. La nueva revisión del libro de Félix Riaño ‘Todo Sobre Pódcast' ya está disponible. Acast anuncia nuevas funciones para podcasters y anunciantes. Quill Podcasting, realiza sondeo de opinión y lanza nuevo servicio de alojamiento de pódcast. Pódcast nuevo: “Alimentando con Innovación, el campo habla”. Pódcast recomendado La otra corona. Una producción sonora sobre el lado B (los secretos) de la realeza británica. Carola Gil, conductora y columnista de TV en Argentina y Gabriel Oliveri, periodista y disertante, exponen curiosidades, ceremonias, historia y personalidades inolvidables de la corona británica. Un pódcast de Film & Arts.

This week, we look at a man who was once the most famous human being, on the planet Earth. He was a hero of his country, and many others, as well. Given godlike status by fans, all over the world, his soccer prowess was unmatched, but so was his ego, and passion for partying. Cocaine, ladies of the night, and plenty of mafioso friends led him down a path of excess that got him in trouble with police, on multiple continents, and destroyed his health. His legend is enormous, his list of mistakes is just as impressive!!Come from nowhere to be the greatest soccer player that exists, be rich & famous beyond dreams, as a teenager, and throw it all away, with no concern for health, or legacy with Diego Maradona!! Check us out, every Tuesday! We will continue to bring you the biggest idiots in sports history!! Hosted by James Pietragallo & Jimmie Whisman Donate at... patreon.com/crimeinsports or with paypal.com using our email: crimeinsports@gmail.com Get all the CIS & STM merch at crimeinsports.threadless.com Go to shutupandgivememurder.com for all things CIS & STM!! Contact us on... twitter.com/crimeinsports crimeinsports@gmail.com facebook.com/Crimeinsports instagram.com/smalltownmurderSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Learning a language is much more than learning vocabulary. This includes understanding and anticipating interactions within a cultural context. John and Jared discuss exactly what this means and what you should know to maximize your gains. Interview is with Elisa Ferrero, a native of Italy who learned English to learn Chinese and today is a Chinese teacher to Spanish speakers in Argentina. Links from the episode:AllSet Learning 1-on-1 Live LessonsYou Can Learn Chinese in Taiwan (even now!)HSK Level | vocab level assessmentElisa Ferrero website | ElisaLaoshi.com (Spanish)See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In which we try out two wines from Argentina, learn about the region, and shenanigans ensue. ----- Leave us a message! anchor.fm/itswine Twitter: @itswinepodcast Facebook: ItsWinePodcast

The Astronomy, Technology, and Space Science News Podcast.SpaceTime Series 25 Episode 55*First image of the Milky Way's central black holeAstronomers have unveiled the first ever direct image of Sagittarius A* the supermassive black hole at the centre of our Milky Way galaxy.*History and dark matter in the Milky Way GalaxyA new study exploring the formation history of the Milky Way is also revealing new details about the dark matter halo enveloping the galaxy.*May 19 launch date for StarlinerNASA and Boeing have announced May 19 as the potential launch date for the long delayed Starliner spacecraft.*The Science ReportWarnings that climate change will increase human exposure to new virus and disease species.New study looks at the ideal amount of sleep you should have.A new species of theropod dinosaur discovered in Argentina.Skeptic's guide to Pentagon investigation into Unexplained Aerial Phenomena.Listen to SpaceTime on your favorite podcast app with our universal listen link: https://spacetimewithstuartgary.com/listen For more SpaceTime and show links: https://linktr.ee/biteszHQ If you love this podcast, please get someone else to listen to. Thank you…To become a SpaceTime supporter and unlock commercial free editions of the show, gain early access and bonus content, please visit https://bitesz.supercast.com/ . Premium version now available via Spotify and Apple Podcasts.For more podcasts visit our HQ at https://bitesz.com #podcast #astronomy #space #science #astrophysics #cosmology #spacetime

Fernando Castiñeiras dejó aparcado su trabajo de profesor de español en Alemania para viajar por América Latina. Un viaje de 6 meses que le llevó por Argentina, Uruguay, Chile, Bolivia, Perú, Ecuador y, finalmente, Colombia. Un viaje que se le quedó corto, especialmente cuando comprobó que lo que más le gustaba era el contacto con la gente. En este podcast, hablamos de personas increíbles que conoció, pero también de paisajes, decepciones viajeras, problemas y soledades. Y también, de su libro El plan es no tener plan, autopublicado por él 3 años después de volver. Más información y fotos en: https://bit.ly/fercasti Si sueñas con hacer un gran viaje como este te recomendamos: > Nuestro libro "Cómo preparar un gran viaje" (2ª ed.): https://www.laeditorialviajera.es/tienda/como-preparar-un-gran-viaje-2/ > Nuestro NUEVO libro "El libro de los grandes viajes": https://www.laeditorialviajera.es/tienda/el-libro-de-los-grandes-viajes/ Si quieres conocer historias en primera persona de otros viajeros, este evento te gustará: > Jornadas de los grandes viajes: https://www.jornadasgrandesviajes.es ¿Te gusta este podcast? ¿Quieres agradecernos el trabajo que hacemos? APOYA ESTE PROGRAMA: conviértete en mecenas en iVoox o Patreon. Más info en: > https://www.ungranviaje.org/podcast-de-viajes/apoya-podcast-un-gran-viaje/

The likely end of Roe v. Wade marks a bitter setback for the pro-choice movement. But the success of abortion legalization campaigns in Ireland and Argentina may be models for a way forward.  What are the ingredients for effective public messaging? What can American activists learn from the examples of international movements? Guest: Anat Shenker-Osorio, communications researcher and campaign advisor, host of the podcast “Words To Win By.” If you enjoy this show, please consider signing up for Slate Plus. Slate Plus members get benefits like zero ads on any Slate podcast, bonus episodes of shows like Slow Burn and Dear Prudence—and you'll be supporting the work we do here on What Next. Sign up now at slate.com/whatnextplus to help support our work. Learn more about your ad choices. Visit megaphone.fm/adchoices

The likely end of Roe v. Wade marks a bitter setback for the pro-choice movement. But the success of abortion legalization campaigns in Ireland and Argentina may be models for a way forward.  What are the ingredients for effective public messaging? What can American activists learn from the examples of international movements? Guest: Anat Shenker-Osorio, communications researcher and campaign advisor, host of the podcast “Words To Win By.” If you enjoy this show, please consider signing up for Slate Plus. Slate Plus members get benefits like zero ads on any Slate podcast, bonus episodes of shows like Slow Burn and Dear Prudence—and you'll be supporting the work we do here on What Next. Sign up now at slate.com/whatnextplus to help support our work. Learn more about your ad choices. Visit megaphone.fm/adchoices

The likely end of Roe v. Wade marks a bitter setback for the pro-choice movement. But the success of abortion legalization campaigns in Ireland and Argentina may be models for a way forward.  What are the ingredients for effective public messaging? What can American activists learn from the examples of international movements? Guest: Anat Shenker-Osorio, communications researcher and campaign advisor, host of the podcast “Words To Win By.” If you enjoy this show, please consider signing up for Slate Plus. Slate Plus members get benefits like zero ads on any Slate podcast, bonus episodes of shows like Slow Burn and Dear Prudence—and you'll be supporting the work we do here on What Next. Sign up now at slate.com/whatnextplus to help support our work. Learn more about your ad choices. Visit megaphone.fm/adchoices

CLICK HERE TO DONATE OR SUPPORT TO PODCAST!!!! - https://thinkinginenglish.blog/donate-and-support/ 40 years ago Britain and Argentina fought a bitter war over a few small and remote islands in the Atlantic ocean. The Falkland islands remain a controversial issue today. Where are the Falklands? Why did Argentina and Britain go to war over them? And who should control the islands? Let's discuss these questions on today's episode of Thinking in English! TRANSCRIPT - https://thinkinginenglish.blog/2022/05/16/why-are-the-falkland-islands-so-controversial/ You may also like... 151. What is Roe v. Wade? (English Vocabulary Lesson) 150. How to Stop Procrastinating!! (English Vocabulary Lesson) Does Your English Accent Matter? w/ Dan Sensei (English Conversation Lesson) 149. Should Cannabis be Legal? (English Vocabulary Lesson) INSTAGRAM - thinkinginenglishpodcast (https://www.instagram.com/thinkinginenglishpodcast/) Blog - thinkinginenglish.blog Vocabulary List Remote (adj) - far away in distance He lives in a remote mountain village Sparsely (adv) - with only a small number or amount of people or things His room is sparsely furnished To renounce (v) - to say formally or publicly that you no longer own, support, believe in, or have a connection with something Gandhi renounced the use of violence Sovereignty (n) - the power of a country to control its own government Talks are ongoing over the sovereignty of the disputed island To occupy (v) - to move into and take control and/or possession of a place Troops quickly occupied the city To surrender (v) - to stop fighting and admit defeat They would rather die than surrender To inherit (v) - if you inherit a situation, problem, department, etc., you become responsible for dealing with it or managing it When I took on the job of manager, I inherited a lot of financial problems Undisputed (adj) - if something is undisputed, everyone agrees about it He is the undisputed heavyweight champion of the world Self-determination (n) - the ability or power to make decisions for yourself, especially the power of a nation to decide how it will be governed The UN considers self-determination to be a human right --- Send in a voice message: https://anchor.fm/thinking-english/message

Las noticias del día con César Vidal y María Jesús Alfaya. Ayúdanos a seguir en emisión, participa en el Crowdfunding de La Voz de César Vidal: https://www.cesarvidal.com/dona En el informativo de hoy hemos tratado los siguientes temas: - Estudiantes independentistas se encandenan ante la Delegación del Gobierno en Cataluña contra el 25% del castellano dictado por el TSJC. - El Cardenal Arzobispo de Barcelona defiende las esteladas en las iglesias porque afirma que "La casa de Dios debe ser inclusiva". - Perú aprueba una ley que protege el derecho de los padres en la educación de sus hijos. - Rechazo ante la aprobación del primer trigo transgénico del mundo en Argentina. - Turquía se opone a la adhesión de Suecia y Finlandia a la OTAN. - CEO de Goya Foods “Estamos al borde de la escasez de alimentos”.

The New American Nightmare with Doug Casey What lies ahead for the global financial markets and freedom in the US? Best-selling author, world-renowned speculator, and brilliant libertarian philosopher Doug Casey returns to the Outer Limits of Inner Truth. Casey offers his perspectives on the philosophies of Martin Armstrong, Jeff Berwick, and Larken Rose to name a few. Casey also discusses the new nightmare that we are apparently all in the midst of walking into (and what people who love free speech can do about it).. Doug Casey has garnered a well-earned reputation for his erudite (and often controversial) insights into politics, economics, and investment markets. Doug is widely respected as one of the preeminent authorities on “rational speculation,” especially in the high-potential natural resource sector. Doug wrote the book on profiting from periods of economic turmoil: his book Crisis Investing spent weeks as #1 on the New York Times bestseller list and became the best-selling financial book of 1980 with 438,640 copies sold; surpassing big-caliber names, like Free to Choose by Milton Friedman, The Real War by Richard Nixon, and Cosmos by Carl Sagan. He has been a featured guest on hundreds of radio and TV shows, including David Letterman, Merv Griffin, Charlie Rose, Phil Donahue, Regis Philbin, Maury Povich, NBC News, and CNN; has been the topic of numerous features in periodicals such as Time, Forbes, People, and the Washington Post; and is a regular keynote speaker at FreedomFest, the world's largest gathering of free minds. Doug has lived in 10 countries and visited over 175. He currently spends most of his time in Argentina and Uruguay, and traveling to various dysfunctional hellholes. Today you're most likely to find him at La Estancia de Cafayate, an oasis tucked away in the high red mountains outside Salta, Argentina. Cafayate most resembles the isolating beauty of Bryce Canyon, Utah combined with the lush vineyards of Napa Valley. Residents enjoy economic and social freedoms not found in the US and some of the best wine and golf on the planet. Website Link:  ================================================= The New American Nightmare Doug Casey on Food Riots and “Inflation Lockdowns” The “Great Reset” and the Future of Money… Here's What You Need To Know

El cuentista Pep Bruno nos narra La hija de la bruja caníbal, un cuento de los Tobas, cultura precolombina del norte de Argentina (y sur de Bolivia y Paraguay). Escuchar audio

Hoy saboreamos la cocina patria con Miguel Ángel Almodóvar. El autor del libro Esto no estaba en mi libro de historia de la cocina española repasa nuestra gastronomía desde sus orígenes hasta la actualidad. Después, Sergio Martín repasa la actualidad informativa en su sección ‘Si yo tuviera un programa…’. El cuentista Pep Bruno nos narra La hija de la bruja caníbal, un cuento de los Tobas, cultura precolombina del norte de Argentina (y sur de Bolivia y Paraguay). El astrofísico Javier Armentia nos habla de cómo afectan los ruidos a los océanos. Carmen Fernández nos comenta vuestras peticiones y quejas en ‘El rincón del Ciudadano’. Y, por último, nuestro cocinero Sergio Fernández, nos enseña recetas de aprovechamiento con las sobras que nos han quedado de la semana. Escuchar audio

Por primera vez en la historia, en la Argentina se va a hacer un censo sobre las personas que viven en situación de calle. Este operativo especial se va a hacer en centros urbanos de todo el país en la noche del 16 de mayo, dos días antes de la fecha del censo nacional sobre toda la población. Hasta ahora en el país no tuvimos datos oficiales a nivel nacional sobre cuántas personas viven en situación de calle, qué necesitan, y qué factores las llevaron a esta situación, entre otras cuestiones. La consecuencia de esto es que no es posible diseñar políticas públicas inteligentes, ni para prevenir que más personas estén en esta situación, ni para ayudar a quienes ya la viven. ¿Qué dicen los expertos sobre el operativo del censo y la metodología de la encuesta? ¿Son acertados? ¿Cómo debe cambiar la mirada del Estado y del conjunto de la sociedad sobre estas personas?

1 - B.P.T. feat.DM Binxter - Moody (PAUL (AR)) /  2 - Husa & Zeyada - On My Own (Hernan Cattaneo & Marcelo Vasami Remix) /  3 - Integral Bread - Ready To Born (simos tagias remix) /  4 - Hayden James Cassian Elderbrook - On Your Own (Fort Romeau Remix) /  5 - Abity - Lotus /  6 - Goraieb e Luciano Scheffer - Endless Symphony - Noiyse Project Remix /  7 - Belms _ VeeQue - Western Clouds (Abel Meyer Mix) /  8 - VegaZ-SL - Endometriosis (NOIYSE-PROJECT-Remix) /  9 - Fulltone - Kairo /  10 - Yotam Avni - Here We Are Again /  Download episode on MP3 (Right click, save link as...)   Help me support NGO Alegría Intensiva, Hospital Clown, in Argentina. Donate now by clicking here!!! Donar desde Argentina haciendo click aquí!!!  

►ATTACK On Bitcoin Fails, Norway Mining Ban Defeated. We dive into how the IMF is coercing Argentina's exchanges. Huge win for Proof of work Mining in Norway. ► Fail: KRNC, LightSpark the mounting social attacks on bitcoin are never ending. We explore the latest in shitcoin affinity scams attempting to fool you out of bitcoin ownership. ✔ Special Guest: @natbrunell ► https://talkingbitcoin.com/ ✔ Software Releases: Sparrow Wallet 1.6.4-Beta1 ► https://github.com/sparrowwallet/sparrow/releases/tag/1.6.4-beta1 1.6.4-beta1 ✔ Check out our Sponsors, support Bitcoin ONLY Businesses: ✔ Crypto Cloaks: ► http://www.cryptocloaks.com?afmc=2h&utm_campaign=2h&utm_source=leaddyno&utm_medium=affiliate ► USE PROMO CODE 'SIMPLYBITCOIN' FOR 5% OFF THE CRYPTOCLOAKS.COM STORE! ✔ Citadel21: ► https://www.citadel21.com ✔ Swan: ► https://www.swanbitcoin.com ✔ CypherSafe: ► https://cyphersafe.io ✔ Represent Clothing: ► https://www.representltd.com ► USE PROMO CODE SIMPLY-BITCOIN FOR 10% OFF ANYTHING IN THE REPRESENT CLOTHING STORE! ✔ NODL : ► https://www.nodl.eu ✔ Join our Telegram, Give us Memes to Review! ► https://t.me/TheSimplyBitcoinChannel ✔ Follow Us! ► https://twitter.com/SimplyBitcoinTV ► https://twitter.com/BITVOLT7 ► https://twitter.com/Coinicarus ✔ Special Thanks to these Awesome Bitcoiners: ► https://bitcoin.clarkmoody.com/dashboard/ ► https://t.me/nobullshitbitcoin ► https://twitter.com/DocumentingBTC ✔ Descriptions & Thumbnails by, Meg: ► https://twitter.com/btcmeg ► We are a proud supporter of Bitcoin only businesses. ⚡️ simplybitcoin@getalby.com DISCLAIMER: All views in this episode are our own and DO NOT reflect the views of any of our guests or sponsors. Timecodes: 0:00 - Intro 0:35 - BTC Stats 9:44 - Daily Fail 24:53 - Meme Review 28:10 - BTC News 43:50 - Software Release #Bitcoin #BitcoinDailyNews #BitcoinDailyRecap

El cuentista Pep Bruno nos narra El diluvio de fuego, un cuento de los Tobas, cultura precolombina del norte de Argentina (y sur de Bolivia y Paraguay). Escuchar audio

Hoy viajamos a Hollywood con el peluquero de las estrellas, Alexis Continente. El catalán nominado a los Oscar 2022 por La Casa Gucci, nos muestra cómo es su trabajo tanto dentro como fuera de los rodajes. Después, Sergio Martín repasa la actualidad informativa en su sección ‘Si yo tuviera un programa…’. El cuentista Pep Bruno nos narra El diluvio de fuego, un cuento de los Tobas, cultura precolombina del norte de Argentina (y sur de Bolivia y Paraguay). La sexóloga Arola Poch nos habla de voces sexis y sobre la censura en internet. Carmen Fernández nos hace viajar en el tiempo con la exposición En Madrid. Una historia de la moda, 1940-1970. Y, por último, nuestro cocinero Sergio Fernández, nos prepara el bocadillo para el fútbol. Escuchar audio

Audio del Streaming en vivo que Álvaro Martín hizo el viernes 13 de mayo de 2022 analizando los Playoffs de la temporada 2021-22 de la NBA e informando sobre las noticias de la jornada. Invitado especial: Coach Julio Lamas, ex DT de la selección Argentina y de la de Japón, entre muchos otros equipos que tuvo a su cargo en 30 años de carrera. Análisis de los juegos del día anterior: MIA 99 - 90 PHI (Heat Gana la serie 4-2) PHX 86 - 113 DAL (Mavericks lleva la serie al séptimo juego) Previas de los partidos del día: BOS (2) en MIL (3) MEM (2) en GSW (3) ¡Síguenos y suscríbete! - Ritmo NBA Canal de YouTube: bit.ly/2ECwwGh Twitter: bit.ly/3gq4cV7 Instagram: bit.ly/31ugLdH Facebook: bit.ly/3aUoRPX

 @Luck Ra habla de #TeMentiríaRemix junto a @Rusher King en esta entrevista de #tumusicahoy

 @Trueno Oficial presenta #BienOMal , habla de su familia, su vida, sus proyectos, y mucho más, en esta #entrevista de #tumusicahoy

Nueva Música presenta lo último de Abraham Mateo & Ana Mena, Álex Ubago, Mon Laferte, Ruggero y más artistas.

The Copa de la Liga knockout stage has begun, and after Tuesday's two matches brought the expected home wins for Racing and Boca Juniors, who'll meet in the first semifinal on Saturday, Wednesday saw two shock results, as Argentinos Juniors outplayed Estudiantes before putting them out on spot kicks and Tigre took advantage of a howling defensive error to beat River Plate, in spite of a Puskás Award contender from Enzo Fernández. Sam, English Dan, Santi and Andrés are on hand to talk you through it all.

Yamana Gold Inc. is a Canada-based precious metals producer. The Company has gold and silver production, development stage properties, exploration properties, and land positions throughout the Americas, including Canada, Brazil, Chile and Argentina. The Company's principal producing mining properties are comprised of the Canadian Malartic mine in Canada, the Jacobina mine in Brazil, the El Penon and Minera Florida mines in Chile and the Cerro Moro mine in Argentina. The Company's projects include the MARA project in Argentina and the Wasamac project in Canada. The Canadian Malartic mine, in which the Company holds a 50% interest, is located in the Abitibi region of Quebec near the town of Val-d'Or. Minera Florida is an underground gold mine located in central Chile, approximately 75 kilometers southwest of Santiago. The Cerro Moro is a gold-silver operation located in the Santa Cruz province of Argentina approximately 70 km south of the port city of Puerto Deseado.

Esta semana dedicamos el Sofá Sonoro a recordar Musas, los dos discos que la cantante mexicana Natalia Lafourcade editó en 2017 y 2018 y que suponen un hermoso viaje al folclore latinoamericano. Para este proyecto Natalia se rodeó de Los Macorinos, la banda de Chavela Vargas y grabó dos decenas de canciones que recorren la historia de México, Perú, Chile o Argentina. Para recordar el proyecto nos acompañan Jimena Marcos, Lucía Taboada y la propia Natalia. 

Hoy César Vidal entrevistara a Hugo Agustín Mancini, Suboficial Subalterno de la Fuerza Aérea Argentina, Artillero Antiaéreo jefe y nos contará de primera mano la verdad sobre la guerra de las Malvinas. Ayúdanos a seguir en emisión, participa en el Crowdfunding de La Voz de César Vidal: https://www.cesarvidal.com/dona

Seguna parte de la saga de la banda de sonido de nuestras vidas. La fiebre disco continúa. Kissmanía en Argentina con "Fui hecho para amarte". The Police en Buenos Aires. Las películas de la época. El amor a través de los ojos de un niño. Los traumas. Crecer en dictadura. Rebelarse contra lo establecido. Más canciones que forjan nuestra identidad. Contar historias a partir de la música que nos acompañó durante aquella etapa de formación. Con Gustavo Olmedo. Un podcast original de Radio en Casa.

Impaactante caso ocurrido en Argentina

P. Juan (Argentina)-La Virgen nos pide, en su advocación de Fátima, que recemos y que ofrezcamos sacrificios para que del Cielo nos llegue la ayuda que tanto necesita nuestro mundo, para que vuelva a Dios.

Following last week's Supreme Court draft opinion leak that may mark the end of abortion rights in the U.S., Latino Rebels Radio host Julio Ricardo Varela speaks with journalist Juanita Ramos Ardila to discuss why some countries in Latin America are going in the other direction and how feminist groups in Colombia, Mexico and Argentina are leading the charge.

The Quarantine Tapes es un podcast diario de Onassis LA y dublab. El programa es presentado por Paul Holdengräber. Artistas, escritoras y escritores, activistas, líderes, trabajadores y trabajadoras, pensadoras y pensadores charlan con Paul acerca de cómo pasan el tiempo en este momento histórico sin precedentes. Es una crónica de paradigmas cambiantes en la era del distanciamiento social, que destaca las afinidades universales en esta experiencia humana mundial.La edición Argentina presentada por el periodista Sergio Cohen convoca a invitados con enfoque en América Latina y comunidades de habla hispana alrededor del mundo. The Quarantine Tapes se emite los días de semana a las 9.30 PT en DUBLAB.com; a partir de las 12 pm PT está disponible en todas las plataformas de podcasts. The Quarantine Tapes Argentina transmite todos los Jueves a las 9.30 PST en DUBLAB.comNo pudo escuchar la transmisión en vivo? Escúchela como podcast en quarantinetapes.com~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~En este nuevo episodio de “Las cintas de la cuarentena” Argentina, la anfitriona invitada Karina Lorré, recibe a Nancy Jaramillo y juntas emprenden un viaje en el que se alternan la historia de vida de la invitada con las sensaciones que experimentó durante la primera etapa de la pandemia y los efectos de la cuarentena estricta.De la mano de la anfitriona, Jaramillo se interna en los aspectos poco conocidos de la casi inhumana tarea que lleva adelante el personal que trabaja en los buques pesqueros del cual forma parte; da cuenta de los obstáculos y los prejuicios que debió enfrentar a lo largo de su extensa trayectoria para convertirse en la primera y única mujer que alcanzó en Argentina el grado de Capitán de Pesca y reflexiona, entre otros temas, sobre las enseñanzas que, probablemente, dejé esta situación extrema y atípica en la humanidad.La cálida conversación que mantienen las protagonistas de este registro concluye con el deseo de llegar a buen puerto, luego de la ajetreada travesía que aún sacude al mundo.Nancy Viviana Jaramillo nació el 10 de julio de 1976 en Trelew, Chubut. Fue madre a los 17 años. Trabajó como empleada doméstica y desempeñó múltiples tareas informarles para alimentar a su hijo. En 1996 emprendió su primer embarque en el buque “Antonio Álvarez”. Se desempeñó como ayudante de cocina a bordo, cocinera, operaria de planta y marinera de cubierta. Realizó tareas de carga, lavado, pre-procesamiento y estiba. Trabajó en las bodegas y en el sector de clasificado. En el 2003 obtuvo el título de Patrón de Pesca Costera. Durante el 2005 la Asociación de Capitanes y Patrones de Pesca reconoció su trayectoria como trabajadora del sector.  Fue en el 2006 cuando cumplió funciones como 2° Oficial de Pesca y en el 2007 cuando obtuvo el título de Piloto de Pesca. Un año más tarde, ejerció como 1° Oficial de Pesca. En el transcurso del 2012, se convirtió en Piloto de Pesca de 1°. Al año siguiente, debutó como capitana del buque “Miss Tide”. En el 2016 llegó a ser  capitana efectiva del buque “Erin Bruce”. Culminó su formación en el 2017, al obtener el diploma de Capitán de Pesca, siendo la primera mujer en alcanzar tal graduación. La Escuela Nacional de Pesca colocó en su museo una placa resaltando los logros de Jaramillo. Su personalidad y su empeño le permitieron formarse y enfrentar los límites socialmente impuestos a su condición femenina, llegando a conducir naves de gran tamaño y teniendo la facultad necesaria para manejar numerosas tripulaciones.  Karina Lorré nació en 1981, en Bahía Blanca, aunque pasó su infancia y creció en Cabildo, un pequeño pueblo bonaerense. Es Locutora Nacional, egresada de ISER en 2002. En ese mismo año empezó su carrera profesional en LU3 Radio del Sur, y en distintas radios FM de Bahía Blanca, como locutora y en paralelo, como presentadora de diversos eventos, y trabajos para estudios de grabación. Desde 2003, vive en Puerto Madryn. Allí trabaja como locutora en LU17 Radio Golfo Nuevo, una de las radio AM de la provincia de Chubut, y conduce programa musical en Paraíso FM. En veinte años de trayectoria, también trabajó como periodista de El Diario de Madryn, condujo programas radiales diarios, magazines, en diferentes proyectos independientes y distintas emisoras, en paralelo con su ocupación en LU17. Con amplia experiencia en entrevistas a personajes de todos los ámbitos, desde la cultura a la política provincial y nacional.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Este podcast puede ser subscripto en apple podcast, simplecast, spotify o cualquier otro medio como escuche sus podcasts.  Para ver otros podcasts producidos por dublab visite: dublab.com/podcasts.

Why are Finland's leaders calling for the country to apply to join Nato “without delay”? Plus, we discuss France's new left-wing coalition, find out why the sale of Maradona's 1986 World Cup shirt is going down badly in Argentina and give you Fernando Augusto Pacheco's special pop countdown from Turin.

El sábado pasado 7 de mayo se conmemoró el día Internacional de la Jardinería al desnudo por ello hoy nos acompañan dos invitados. Miguel Suarez de Argentina y Rubén Pérez de España para hablar de cómo se relacionan con los espacios naturales y las necesidades o deseos que tienen sobre los jardines para disfrutarlos "al desnudo". Si deseas conocer un poco más sobre el nudismo y naturismo te dejo los enlaces. Argentina: APANNA (Asociación para el Nudismo Naturista Argentino): www.apanna.org.ar Complejo Yatan Rumi: https://www.facebook.com/yatan.rumi.3 Podcast de Rubén Naturalmentepod lo encuentras en iVoox, Spotify y todas las plantaformas. Web: https://naturalmentepod.wordpress.com en donde encontrarás los enlaces a Youtube y el resto de los canales de contacto. Muchas gracias!

Mayor hopefuls come in all shapes and sizes and from all walks of life. Whakatane hopeful Dr Luca has been invited by the United Nations Atomic Energy Agency to travel to Argentina for two months on an 'expert mission'.

Jaime Vázquez: Promotor cultural Muestra de Cine Sur Americano en Ponce y Mayagüez • parte del Festival de Cine de San Juan • La historia de los festivales de cine en Ponce • Se lleva a cabo en el Centro Cultural Carmen Solá de Pereira • Donativo sugerido de $5:00 • Aportaciones del gobierno español mediante a compañías estadounidenses que auspicia la cultura hispana • Contenidos del festival en Ponce o Chile y Argentina o Todas las películas giran en torno al tema de “la familia” o Títulos:  Yo Niña – Argentina  El Despertar de Camila – Chile  Amor Urgente – Argentina  Siete Semanas – Argentina Además del Festival, qué hay en las salas comerciales en el sur

================================================== ==SUSCRIBETEhttps://www.youtube.com/channel/UCNpffyr-7_zP1x1lS89ByaQ?sub_confirmation=1================================================== == DEVOCIÓN MATUTINA PARA MUJERES 2022“SIN MIEDOS NI CADENAS”Narrado por: Sirley DelgadilloDesde: Bucaramanga, ColombiaUna cortesía de DR'Ministries y Canaan Seventh-Day Adventist Church  12 DE MAYO RED DE SEGURIDAD"En esa clase de amor no hay temor, porque el amor perfecto expulsa todo temor. Si tenemos miedo es por temor al castigo, y esto muestra que no hemos experimentado plenamente el perfecto amor de Dios" (1 Juan 4:18, NTV) .Tomé clases de manejo dos veces en mi vida: primero, en Argentina, y después al mudarme a Inglaterra (porque aquí se conduce "al revés”, por la mano izquierda). Una de mis instructoras de manejo era, por lo general, bastante paciente conmigo. Sin embargo, de vez en cuando se enojaba y hacía comentarios irónicos cuando yo no sabía cómo hacer algo, o cuando una maniobra no me salía bien. “¿De verdad no sabes cómo comprobar el nivel de aceite del motor?”, me preguntaba con tono horrorizado.Sin embargo, todos nuestros errores están cubiertos por la gracia de Cristo. El escritor cristiano Graham Cooke, en su artículo “All Your Mistakes Are Covered”, lo describe con estas palabras: “Dios sabe que cuando hace algo por primera vez, vas a cometer errores. Lo asombroso acerca de Dios es que él no los describe como 'errores'; él los llama 'aprendizaje, porque sabe que nunca antes lo esforzó habíaado". Dios no es un maestro severo e imposible de complacer. Cuando nos atrevemos a avanzar ya intentar algo diferente, cuando navegamos por aguas inexploradas, él aplaude y nos anima. Lo que nos da el coraje para avanzar es justamente su gracia, y saber que somos amadas más allá del éxito o del fracaso de nuestros planes.Dios es el Maestro más amable, compasivo y humilde que hayamos conocido. Él no nos presiona con expectativas irreales. No se mofa cuando nos equivocamos. No se impacienta cuando nos demoramos. ¡Al contrario! Él nos alienta, diciendo: "Hija, yo ya te amo y mi gracia cubre todo lo que te falta. Yo veo no solo quién eres ahora, sino quién serás. Te veo resplandeciendo con mi presencia. Te veo valiente y victoriosa. No temas , yo sé quién eres realmente”.Señor, tu perfecto amor desaloja el temor de mi corazón. Porque hay una red de gracia que me protege, hoy puedo arriesgarme, intentar cosas nuevas y cambiar.

About AmyAmy Tobey has worked in tech for more than 20 years at companies of every size, working with everything from kernel code to user interfaces. These days she spends her time building an innovative Site Reliability Engineering program at Equinix, where she is a principal engineer. When she's not working, she can be found with her nose in a book, watching anime with her son, making noise with electronics, or doing yoga poses in the sun.Links Referenced: Equinix Metal: https://metal.equinix.com Personal Twitter: https://twitter.com/MissAmyTobey Personal Blog: https://tobert.github.io/ 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 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. Every once in a while I catch up with someone that it feels like I've known for ages, and I realize somehow I have never been able to line up getting them on this show as a guest. Today is just one of those days. And my guest is Amy Tobey who has been someone I've been talking to for ages, even in the before-times, if you can remember such a thing. Today, she's a Senior Principal Engineer at Equinix. Amy, thank you for finally giving in to my endless wheedling.Amy: Thanks for having me. You mentioned the before-times. Like, I remember it was, like, right before the pandemic we had beers in San Francisco wasn't it? There was Ian there—Corey: Yeah, I—Amy: —and a couple other people. It was a really great time. And then—Corey: I vaguely remember beer. Yeah. And then—Amy: And then the world ended.Corey: Oh, my God. Yes. It's still March of 2020, right?Amy: As far as I know. Like, I haven't checked in a couple years.Corey: So, you do an awful lot. And it's always a difficult question to ask someone, so can you encapsulate your entire existence in a paragraph? It's—Amy: [sigh].Corey: —awful, so I'd like to give a bit more structure to it. Let's start with the introduction: You are a Senior Principal Engineer. We know it's high level because of all the adjectives that get put in there, and none of those adjectives are ‘associate' or ‘beginner' or ‘junior,' or all the other diminutives that companies like to play games with to justify paying people less. And you're at Equinix, which is a company that is a bit unlike most of the, shall we say, traditional cloud providers. What do you do over there and both as a company, as a person?Amy: So, as a company Equinix, what most people know about is that we have a whole bunch of data centers all over the world. I think we have the most of any company. And what we do is we lease out space in that data center, and then we have a number of other products that people don't know as well, which one is Equinix Metal, which is what I specifically work on, where we rent you bare-metal servers. None of that fancy stuff that you get any other clouds on top of it, there's things you can get that are… partner things that you can add-on, like, you know, storage and other things like that, but we just deliver you bare-metal servers with really great networking. So, what I work on is the reliability of that whole system. All of the things that go into provisioning the servers, making them come up, making sure that they get delivered to the server, make sure the API works right, all of that stuff.Corey: So, you're on the Equinix cloud side of the world more so than you are on the building data centers by the sweat of your brow, as they say?Amy: Correct. Yeah, yeah. Software side.Corey: Excellent. I spent some time in data centers in the early part of my career before cloud ate that. That was sort of cotemporaneous with the discovery that I'm the hardware destruction bunny, and I should go to great pains to keep my aura from anything expensive and important, like, you know, the SAN. So—Amy: Right, yeah.Corey: Companies moving out of data centers, and me getting out was a great thing.Amy: But the thing about SANs though, is, like, it might not be you. They're just kind of cursed from the start, right? They just always were kind of fussy and easy to break.Corey: Oh, yeah. I used to think—and I kid you not—that I had a limited upside to my career in tech because I sometimes got sloppy and I was fairly slow at crimping ethernet cables.Amy: [laugh].Corey: That is very similar to growing up in third grade when it became apparent that I was going to have problems in my career because my handwriting was sloppy. Yeah, it turns out the future doesn't look like we predicted it would.Amy: Oh, gosh. Are we going to talk about, like, neurological development now or… [laugh] okay, that's a thing I struggle with, too right, is I started typing as soon as they would let—in fact, before they would let me. I remember in high school, I had teachers who would grade me down for typing a paper out. They want me to handwrite it and I would go, “Cool. Go ahead and take a grade off because if I handwrite it, you're going to take two grades off my handwriting, so I'm cool with this deal.”Corey: Yeah, it was pretty easy early on. I don't know when the actual shift was, but it became more and more apparent that more and more things are moving towards a world where you could type. And I was almost five when I started working on that stuff, and that really wound up changing a lot of aspects of how I started seeing things. One thing I think you're probably fairly well known for is incidents. I want to be clear when I say that you are not the root cause as—“So, why are things broken?” “It's Amy again. What's she gotten into this time?” Great.Amy: [laugh]. But it does happen, but not all the time.Corey: Exa—it's a learning experience.Amy: Right.Corey: You've also been deeply involved with SREcon and a number of—a lot of aspects of what I will term—and please don't yell at me for this—SRE culture—Amy: Yeah.Corey: Which is sometimes a challenging thing to wind up describing or putting a definition around. The one that I've always been somewhat partial to is, “SRE is DevOps, except you worked at Google for a while.” I don't know how necessarily accurate that is, but it does rile people up.Amy: Yeah, it does. Dave Stanke actually did a really great talk at SREcon San Francisco just a couple weeks ago, about the DORA report. And the new DORA report, they split SRE out into its own function and kind of is pushing against that old model, which actually comes from Liz Fong-Jones—I think it's from her, or older—about, like, class SRE implements DevOps, which is kind of this idea that, like, SREs make DevOps happen. Things have evolved, right, since then. Things have evolved since Google released those books, and we're all just figured out what works and what doesn't a little bit.And so, it's not that we're implementing DevOps so much. In fact, it's that ops stuff that kind of holds us back from the really high impact work that SREs, I think, should be doing, that aren't just, like, fixing the problems, the symptoms down at the bottom layer, right? Like what we did as sysadmins 20 years ago. You know, we'd go and a lot of people are SREs that came out of the sysadmin world and still think in that mode, where it's like, “Well, I set up the systems, and when things break, I go and I fix them.” And, “Why did the developers keep writing crappy code? Why do I have to always getting up in the middle of the night because this thing crashed?”And it turns out that the work we need to do to make things more reliable, there's a ceiling to how far away the platform can take us, right? Like, we can have the best platform in the world with redundancy, and, you know, nine-way replicated data storage and all this crazy stuff, and still if we put crappy software on top, it's going to be unreliable. So, how do we make less crappy software? And for most of my career, people would be, like, “Well, you should test it.” And so, we started doing that, and we still have crappy software, so what's going on here? We still have incidents.So, we write more tests, and we still have incidents. We had a QA group, we still have incidents. We send the developers to training, and we still have incidents. So like, what is the thing we need to do to make things more reliable? And it turns out, most of it is culture work.Corey: My perspective on this stems from being a grumpy old sysadmin. And at some point, I started calling myself a systems engineer or DevOps or production engineer, or SRE. It was all from my point of view, the same job, but you know, if you call yourself a sysadmin, you're just asking for a 40% pay cut off the top.Amy: [laugh].Corey: But I still tended to view the world through that lens. I tended to be very good at Linux systems internals, for example, understanding system calls and the rest, but increasingly, as the DevOps wave or SRE wave, or Google-isation of the internet wound up being more and more of a thing, I found myself increasingly in job interviews, where, “Great, now, can you go wind up implementing a sorting algorithm on the whiteboard?” “What on earth? No.” Like, my lingua franca is shitty Bash, and no one tends to write that without a bunch of tab completions and quick checking with manpages—die.net or whatnot—on the fly as you go down that path.And it was awful, and I felt… like my skill set was increasingly eroding. And it wasn't honestly until I started this place where I really got into writing a fair bit of code to do different things because it felt like an orthogonal skill set, but the fullness of time, it seems like it's not. And it's a reskilling. And it made me wonder, does this mean that the areas of technology that I focused on early in my career, was that all a waste? And the answer is not really. Sometimes, sure, in that I don't spend nearly as much time worrying about inodes—for example—as I once did. But every once in a while, I'll run into something and I looked like a wizard from the future, but instead, I'm a wizard from the past.Amy: Yeah, I find that a lot in my work, now. Sometimes things I did 20 years ago, come back, and it's like, oh, yeah, I remember I did all that threading work in 2002 in Perl, and I learned everything the very, very, very hard way. And then, you know, this January, did some threading work to fix some stability issues, and all of it came flooding back, right? Just that the experiences really, more than the code or the learning or the text and stuff; more just the, like, this feels like threads [BLEEP]-ery. Is a diagnostic thing that sometimes we have to say.And then people are like, “Can you prove it?” And I'm like, “Not really,” because it's literally thread [BLEEP]-ery. Like, the definition of it is that there's weird stuff happening that we can't figure out why it's happening. There's something acting in the system that isn't synchronized, that isn't connected to other things, that's happening out of order from what we expect, and if we had a clear signal, we would just fix it, but we don't. We just have, like, weird stuff happening over here and then over there and over there and over there.And, like, that tells me there's just something happening at that layer and then have to go and dig into that right, and like, just basically charge through. My colleagues are like, “Well, maybe you should look at this, and go look at the database,” the things that they're used to looking at and that their experiences inform, whereas then I bring that ancient toiling through the threading mines experiences back and go, “Oh, yeah. So, let's go find where this is happening, where people are doing dangerous things with threads, and see if we can spot something.” But that came from that experience.Corey: And there's so much that just repeats itself. And history rhymes. The challenge is that, do you have 20 years of experience, or do you have one year of experience repeated 20 times? And as the tide rises, doing the same task by hand, it really is just a matter of time before your full-time job winds up being something a piece of software does. An easy example is, “Oh, what's your job?” “I manually place containers onto specific hosts.” “Well, I've got news for you, and you're not going to like it at all.”Amy: Yeah, yeah. I think that we share a little bit. I'm allergic to repeated work. I don't know if allergic is the right word, but you know, if I sit and I do something once, fine. Like, I'll just crank it out, you know, it's this form, or it's a datafile I got to write and I'll—fine I'll type it in and do the manual labor.The second time, the difficulty goes up by ten, right? Like, just mentally, just to do it, be like, I've already done this once. Doing it again is anathema to everything that I am. And then sometimes I'll get through it, but after that, like, writing a program is so much easier because it's like exponential, almost, growth in difficulty. You know, the third time I have to do the same thing that's like just typing the same stuff—like, look over here, read this thing and type it over here—I'm out; I can't do it. You know, I got to find a way to automate. And I don't know, maybe normal people aren't driven to live this way, but it's kept me from getting stuck in those spots, too.Corey: It was weird because I spent a lot of time as a consultant going from place to place and it led to some weird changes. For example, “Oh, thank God, I don't have to think about that whole messaging queue thing.” Sure enough, next engagement, it's message queue time. Fantastic. I found that repeating myself drove me nuts, but you also have to be very sensitive not to wind up, you know, stealing IP from the people that you're working with.Amy: Right.Corey: But what I loved about the sysadmin side of the world is that the vast majority of stuff that I've taken with me, lives in my shell config. And what I mean by that is I'm not—there's nothing in there is proprietary, but when you have a weird problem with trying to figure out the best way to figure out which Ruby process is stealing all the CPU, great, turns out that you can chain seven or eight different shell commands together through a bunch of pipes. I don't want to remember that forever. So, that's the sort of thing I would wind up committing as I learned it. I don't remember what company I picked that up at, but it was one of those things that was super helpful.I have a sarcastic—it's a one-liner, except no sane editor setting is going to show it in any less than three—of a whole bunch of Perl, piped into du, piped into the rest, that tells you one of the largest consumers of files in a given part of the system. And it rates them with stars and it winds up doing some neat stuff. I would never sit down and reinvent something like that today, but the fact that it's there means that I can do all kinds of neat tricks when I need to. It's making sure that as you move through your career, on some level, you're picking up skills that are repeatable and applicable beyond one company.Amy: Skills and tooling—Corey: Yeah.Amy: —right? Like, you just described the tool. Another SREcon talk was John Allspaw and Dr. Richard Cook talking about above the line; below the line. And they started with these metaphors about tools, right, showing all the different kinds of hammers.And if you're a blacksmith, a lot of times you craft specialized hammers for very specific jobs. And that's one of the properties of a tool that they were trying to get people to think about, right, is that tools get crafted to the job. And what you just described as a bespoke tool that you had created on the fly, that kind of floated under the radar of intellectual property. [laugh].So, let's not tell the security or IP people right? Like, because there's probably billions and billions of dollars of technically, like, made-up IP value—I'm doing air quotes with my fingers—you know, that's just basically people's shell profiles. And my God, the Emacs automation that people have done. If you've ever really seen somebody who's amazing at Emacs and is 10, 20, 30, maybe 40 years of experience encoded in their emacs settings, it's a wonder to behold. Like, I look at it and I go, “Man, I wish I could do that.”It's like listening to a really great guitar player and be like, “Wow, I wish I could play like them.” You see them just flying through stuff. But all that IP in there is both that person's collection of wisdom and experience and working with that code, but also encodes that stuff like you described, right? It's just all these little systems tricks and little fiddly commands and things we don't want to remember and so we encode them into our toolset.Corey: Oh, yeah. Anything I wound up taking, I always would share it with people internally, too. I'd mention, “Yeah, I'm keeping this in my shell files.” Because I disclosed it, which solves a lot of the problem. And also, none of it was even close to proprietary or anything like that. I'm sorry, but the way that you wind up figuring out how much of a disk is being eaten up and where in a more pleasing way, is not a competitive advantage. It just isn't.Amy: It isn't to you or me, but, you know, back in the beginning of our careers, people thought it was worth money and should be proprietary. You know, like, oh, that disk-checking script as a competitive advantage for our company because there are only a few of us doing this work. Like, it was actually being able to, like, manage your—[laugh] actually manage your servers was a competitive advantage. Now, it's kind of commodity.Corey: Let's also be clear that the world has moved on. I wound up buying a DaisyDisk a while back for Mac, which I love. It is a fantastic, pretty effective, “Where's all the stuff on your disk going?” And it does a scan and you can drive and collect things and delete them when trying to clean things out. I was using it the other day, so it's top of mind at the moment.But it's way more polished than that crappy Perl three-liner. And I see both sides, truly I do. The trick also, for those wondering [unintelligible 00:15:45], like, “Where is the line?” It's super easy. Disclose it, what you're doing, in those scenarios in the event someone is no because they believe that finding the right man page section for something is somehow proprietary.Great. When you go home that evening in a completely separate environment, build it yourself from scratch to solve the problem, reimplement it and save that. And you're done. There are lots of ways to do this. Don't steal from your employer, but your employer employs you; they don't own you and the way that you think about these problems.Every person I've met who has had a career that's longer than 20 minutes has a giant doc somewhere on some system of all of the scripts that they wound up putting together, all of the one-liners, the notes on, “Next time you see this, this is the thing to check.”Amy: Yeah, the cheat sheet or the notebook with all the little commands, or again the Emacs config, sometimes for some people, or shell profiles. Yeah.Corey: Here's the awk one-liner that I put that automatically spits out from an Apache log file what—the httpd log file that just tells me what are the most frequent talkers, and what are the—Amy: You should probably let go of that one. You know, like, I think that one's lifetime is kind of past, Corey. Maybe you—Corey: I just have to get it working with Nginx, and we're good to go.Amy: Oh, yeah, there you go. [laugh].Corey: Or S3 access logs. Perish the thought. But yeah, like, what are the five most high-volume talkers, and what are those relative to each other? Huh, that one thing seems super crappy and it's coming from Russia. But that's—hmm, one starts to wonder; maybe it's time to dig back in.So, one of the things that I have found is that a lot of the people talking about SRE seem to have descended from an ivory tower somewhere. And they're talking about how some of the best-in-class companies out there, renowned for their technical cultures—at least externally—are doing these things. But there's a lot more folks who are not there. And honestly, I consider myself one of those people who is not there. I was a competent engineer, but never a terrific one.And looking at the way this was described, I often came away thinking, “Okay, it was the purpose of this conference talk just to reinforce how smart people are, and how I'm not,” and/or, “There are the 18 cultural changes you need to make to your company, and then you can do something kind of like we were just talking about on stage.” It feels like there's a combination of problems here. One is making this stuff more accessible to folks who are not themselves in those environments, and two, how to drive cultural change as an individual contributor if that's even possible. And I'm going to go out on a limb and guess you have thoughts on both aspects of that, and probably some more hit me, please.Amy: So, the ivory tower, right. Let's just be straight up, like, the ivory tower is Google. I mean, that's where it started. And we get it from the other large companies that, you know, want to do conference talks about what this stuff means and what it does. What I've kind of come around to in the last couple of years is that those talks don't really reach the vast majority of engineers, they don't really apply to a large swath of the enterprise especially, which is, like, where a lot of the—the bulk of our industry sits, right? We spend a lot of time talking about the darlings out here on the West Coast in high tech culture and startups and so on.But, like, we were talking about before we started the show, right, like, the interior of even just America, is filled with all these, like, insurance and banks and all of these companies that are cranking out tons of code and servers and stuff, and they're trying to figure out the same problems. But they're structured in companies where their tech arm is still, in most cases, considered a cost center, often is bundled under finance, for—that's a whole show of itself about that historical blunder. And so, the tech culture is tend to be very, very different from what we experience in—what do we call it anymore? Like, I don't even want to say West Coast anymore because we've gone remote, but, like, high tech culture we'll say. And so, like, thinking about how to make SRE and all this stuff more accessible comes down to, like, thinking about who those engineers are that are sitting at the computers, writing all the code that runs our banks, all the code that makes sure that—I'm trying to think of examples that are more enterprise-y right?Or shoot buying clothes online. You go to Macy's for example. They have a whole bunch of servers that run their online store and stuff. They have internal IT-ish people who keep all this stuff running and write that code and probably integrating open-source stuff much like we all do. But when you go to try to put in a reliability program that's based on the current SRE models, like SLOs; you put in SLOs and you start doing, like, this incident management program that's, like, you know, you have a form you fill out after every incident, and then you [unintelligible 00:20:25] retros.And it turns out that those things are very high-level skills, skills and capabilities in an organization. And so, when you have this kind of IT mindset or the enterprise mindset, bringing the culture together to make those things work often doesn't happen. Because, you know, they'll go with the prescriptive model and say, like, okay, we're going to implement SLOs, we're going to start measuring SLIs on all of the services, and we're going to hold you accountable for meeting those targets. If you just do that, right, you're just doing more gatekeeping and policing of your tech environment. My bet is, reliability almost never improves in those cases.And that's been my experience, too, and why I get charged up about this is, if you just go slam in these practices, people end up miserable, the practices then become tarnished because people experienced the worst version of them. And then—Corey: And with the remote explosion as well, it turns out that changing jobs basically means their company sends you a different Mac, and the next Monday, you wind up signing into a different Slack team.Amy: Yeah, so the culture really matters, right? You can't cover it over with foosball tables and great lunch. You actually have to deliver tools that developers want to use and you have to deliver a software engineering culture that brings out the best in developers instead of demanding the best from developers. I think that's a fundamental business shift that's kind of happening. If I'm putting on my wizard hat and looking into the future and dreaming about what might change in the world, right, is that there's kind of a change in how we do leadership and how we do business that's shifting more towards that model where we look at what people are capable of and we trust in our people, and we get more out of them, the knowledge work model.If we want more knowledge work, we need people to be happy and to feel engaged in their community. And suddenly we start to see these kind of generational, bigger-pie kind of things start to happen. But how do we get there? It's not SLOs. It maybe it's a little bit starting with incidents. That's where I've had the most success, and you asked me about that. So, getting practical, incident management is probably—Corey: Right. Well, as I see it, the problem with SLOs across the board is it feels like it's a very insular community so far, and communicating it to engineers seems to be the focus of where the community has been, but from my understanding of it, you absolutely need buy-in at significantly high executive levels, to at the very least by you air cover while you're doing these things and making these changes, but also to help drive that cultural shift. None of this is something I have the slightest clue how to do, let's be very clear. If I knew how to change a company's culture, I'd have a different job.Amy: Yeah. [laugh]. The biggest omission in the Google SRE books was [Ers 00:22:58]. There was a guy at Google named Ers who owns availability for Google, and when anything is, like, in dispute and bubbles up the management team, it goes to Ers, and he says, “Thou shalt…” right? Makes the call. And that's why it works, right?Like, it's not just that one person, but that system of management where the whole leadership team—there's a large, very well-funded team with a lot of power in the organization that can drive availability, and they can say, this is how you're going to do metrics for your service, and this is the system that you're in. And it's kind of, yeah, sure it works for them because they have all the organizational support in place. What I was saying to my team just the other day—because we're in the middle of our SLO rollout—is that really, I think an SLO program isn't [clear throat] about the engineers at all until late in the game. At the beginning of the game, it's really about getting the leadership team on board to say, “Hey, we want to put in SLIs and SLOs to start to understand the functioning of our software system.” But if they don't have that curiosity in the first place, that desire to understand how well their teams are doing, how healthy their teams are, don't do it. It's not going to work. It's just going to make everyone miserable.Corey: It feels like it's one of those difficult to sell problems as well, in that it requires some tooling changes, absolutely. It requires cultural change and buy-in and whatnot, but in order for that to happen, there has to be a painful problem that a company recognizes and is willing to pay to make go away. The problem with stuff like this is that once you pay, there's a lot of extra work that goes on top of it as well, that does not have a perception—rightly or wrongly—of contributing to feature velocity, of hitting the next milestone. It's, “Really? So, we're going to be spending how much money to make engineers happier? They should get paid an awful lot and they're still complaining and never seem happy. Why do I care if they're happy other than the pure mercenary perspective of otherwise they'll quit?” I'm not saying that it's not worth pursuing; it's not a worthy goal. I am saying that it becomes a very difficult thing to wind up selling as a product.Amy: Well, as a product for sure, right? Because—[sigh] gosh, I have friends in the space who work on these tools. And I want to be careful.Corey: Of course. Nothing but love for all of those people, let's be very clear.Amy: But a lot of them, you know, they're pulling metrics from existing monitoring systems, they are doing some interesting math on them, but what you get at the end is a nice service catalog and dashboard, which are things we've been trying to land as products in this industry for as long as I can remember, and—Corey: “We've got it this time, though. This time we'll crack the nut.” Yeah. Get off the island, Gilligan.Amy: And then the other, like, risky thing, right, is the other part that makes me uncomfortable about SLOs, and why I will often tell folks that I talk to out in the industry that are asking me about this, like, one-on-one, “Should I do it here?” And it's like, you can bring the tool in, and if you have a management team that's just looking to have metrics to drive productivity, instead of you know, trying to drive better knowledge work, what you get is just a fancier version of more Taylorism, right, which is basically scientific management, this idea that we can, like, drive workers to maximum efficiency by measuring random things about them and driving those numbers. It turns out, that doesn't really work very well, even in industrial scale, it just happened to work because, you know, we have a bloody enough society that we pushed people into it. But the reality is, if you implement SLOs badly, you get more really bad Taylorism that's bad for you developers. And my suspicion is that you will get worse availability out of it than you would if you just didn't do it at all.Corey: This episode is sponsored by our friends at Revelo. Revelo is the Spanish word of the day, and its spelled R-E-V-E-L-O. It means “I reveal.” Now, have you tried to hire an engineer lately? I assure you it is significantly harder than it sounds. One of the things that Revelo has recognized is something I've been talking about for a while, specifically that while talent is evenly distributed, opportunity is absolutely not. They're exposing a new talent pool to, basically, those of us without a presence in Latin America via their platform. It's the largest tech talent marketplace in Latin America with over a million engineers in their network, which includes—but isn't limited to—talent in Mexico, Costa Rica, Brazil, and Argentina. Now, not only do they wind up spreading all of their talent on English ability, as well as you know, their engineering skills, but they go significantly beyond that. Some of the folks on their platform are hands down the most talented engineers that I've ever spoken to. Let's also not forget that Latin America has high time zone overlap with what we have here in the United States, so you can hire full-time remote engineers who share most of the workday as your team. It's an end-to-end talent service, so you can find and hire engineers in Central and South America without having to worry about, frankly, the colossal pain of cross-border payroll and benefits and compliance because Revelo handles all of it. If you're hiring engineers, check out revelo.io/screaming to get 20% off your first three months. That's R-E-V-E-L-O dot I-O slash screaming.Corey: That is part of the problem is, in some cases, to drive some of these improvements, you have to go backwards to move forwards. And it's one of those, “Great, so we spent all this effort and money in the rest of now things are worse?” No, not necessarily, but suddenly are aware of things that were slipping through the cracks previously.Amy: Yeah. Yeah.Corey: Like, the most realistic thing about first The Phoenix Project and then The Unicorn Project, both by Gene Kim, has been the fact that companies have these problems and actively cared enough to change it. In my experience, that feels a little on the rare side.Amy: Yeah, and I think that's actually the key, right? It's for the culture change, and for, like, if you really looking to be, like, do I want to work at this company? Am I investing my myself in here? Is look at the leadership team and be, like, do these people actually give a crap? Are they looking just to punt another number down the road?That's the real question, right? Like, the technology and stuff, at the point where I'm at in my career, I just don't care that much anymore. [laugh]. Just… fine, use Kubernetes, use Postgres, [unintelligible 00:27:30], I don't care. I just don't. Like, Oracle, I might have to ask, you know, go to finance and be like, “Hey, can we spend 20 million for a database?” But like, nobody really asks for that anymore, so. [laugh].Corey: As one does. I will say that I mostly agree with you, but a technology that I found myself getting excited about, given the time of the recording on this is… fun, I spent a bit of time yesterday—from when we're recording this—teaching myself just enough Go to wind up being together a binary that I needed to do something actively ridiculous for my camera here. And I found myself coming away deeply impressed by a lot of things about it, how prescriptive it was for one, how self-contained for another. And after spending far too many years of my life writing shitty Perl, and shitty Bash, and worse Python, et cetera, et cetera, the prescriptiveness was great. The fact that it wound up giving me something I could just run, I could cross-compile for anything I need to run it on, and it just worked. It's been a while since I found a technology that got me this interested in exploring further.Amy: Go is great for that. You mentioned one of my two favorite features of Go. One is usually when a program compiles—at least the way I code in Go—it usually works. I've been working with Go since about 0.9, like, just a little bit before it was released as 1.0, and that's what I've noticed over the years of working with it is that most of the time, if you have a pretty good data structure design and you get the code to compile, usually it's going to work, unless you're doing weird stuff.The other thing I really love about Go and that maybe you'll discover over time is the malleability of it. And the reason why I think about that more than probably most folks is that I work on other people's code most of the time. And maybe this is something that you probably run into with your business, too, right, where you're working on other people's infrastructure. And the way that we encode business rules and things in the languages, in our programming language or our config syntax and stuff has a huge impact on folks like us and how quickly we can come into a situation, assess, figure out what's going on, figure out where things are laid out, and start making changes with confidence.Corey: Forget other people for a minute they're looking at what I built out three or four years ago here, myself, like, I look at past me, it's like, “What was that rat bastard thinking? This is awful.” And it's—forget other people's code; hell is your own code, on some level, too, once it's slipped out of the mental stack and you have to re-explore it and, “Oh, well thank God I defensively wound up not including any comments whatsoever explaining what the living hell this thing was.” It's terrible. But you're right, the other people's shell scripts are finicky and odd.I started poking around for help when I got stuck on something, by looking at GitHub, and a few bit of searching here and there. Even these large, complex, well-used projects started making sense to me in a way that I very rarely find. It's, “What the hell is that thing?” is my most common refrain when I'm looking at other people's code, and Go for whatever reason avoids that, I think because it is so prescriptive about formatting, about how things should be done, about the vision that it has. Maybe I'm romanticizing it and I'll hate it and a week from now, and I want to go back and remove this recording, but.Amy: The size of the language helps a lot.Corey: Yeah.Amy: But probably my favorite. It's more of a convention, which actually funny the way I'm going to talk about this because the two languages I work on the most right now are Ruby and Go. And I don't feel like two languages could really be more different.Syntax-wise, they share some things, but really, like, the mental models are so very, very different. Ruby is all the way in on object-oriented programming, and, like, the actual real kind of object-oriented with messaging and stuff, and, like, the whole language kind of springs from that. And it kind of requires you to understand all of these concepts very deeply to be effective in large programs. So, what I find is, when I approach Ruby codebase, I have to load all this crap into my head and remember, “Okay, so yeah, there's this convention, when you do this kind of thing in Ruby”—or especially Ruby on Rails is even worse because they go deep into convention over configuration. But what that's code for is, this code is accessible to people who have a lot of free cognitive capacity to load all this convention into their heads and keep it in their heads so that the code looks pretty, right?And so, that's the trade-off as you said, okay, my developers have to be these people with all these spare brain cycles to understand, like, why I would put the code here in this place versus this place? And all these, like, things that are in the code, like, very compact, dense concepts. And then you go to something like Go, which is, like, “Nah, we're not going to do Lambdas. Nah”—[laugh]—“We're not doing all this fancy stuff.” So, everything is there on the page.This drives some people crazy, right, is that there's all this boilerplate, boilerplate, boilerplate. But the reality is, I can read most Go files from top to the bottom and understand what the hell it's doing, whereas I can go sometimes look at, like, a Ruby thing, or sometimes Python and e—Perl is just [unintelligible 00:32:19] all the time, right, it's there's so much indirection. And it just be, like, “What the [BLEEP] is going on? This is so dense. I'm going to have to sit down and write it out in longhand so I can understand what the developer was even doing here.” And—Corey: Well, that's why I got the Mac Studio; for when I'm not doing A/V stuff with it, that means that I'll have one core that I can use for, you know, front-end processing and the rest, and the other 19 cores can be put to work failing to build Nokogiri in Ruby yet again.Amy: [laugh].Corey: I remember the travails of working with Ruby, and the problem—I have similar problems with Python, specifically in that—I don't know if I'm special like this—it feels like it's a SRE DevOps style of working, but I am grabbing random crap off a GitHub constantly and running it, like, small scripts other people have built. And let's be clear, I run them on my test AWS account that has nothing important because I'm not a fool that I read most of it before I run it, but I also—it wants a different version of Python every single time. It wants a whole bunch of other things, too. And okay, so I use ASDF as my version manager for these things, which for whatever reason, does not work for the way that I think about this ergonomically. Okay, great.And I wind up with detritus scattered throughout my system. It's, “Hey, can you make this reproducible on my machine?” “Almost certainly not, but thank you for asking.” It's like ‘Step 17: Master the Wolf' level of instructions.Amy: And I think Docker generally… papers over the worst of it, right, is when we built all this stuff in the aughts, you know, [CPAN 00:33:45]—Corey: Dev containers and VS Code are very nice.Amy: Yeah, yeah. You know, like, we had CPAN back in the day, I was doing chroots, I think in, like, '04 or '05, you know, to solve this problem, right, which is basically I just—screw it; I will compile an entire distro into a directory with a Perl and all of its dependencies so that I can isolate it from the other things I want to run on this machine and not screw up and not have these interactions. And I think that's kind of what you're talking about is, like, the old model, when we deployed servers, there was one of us sitting there and then we'd log into the server and be like, I'm going to install the Perl. You know, I'll compile it into, like, [/app/perl 558 00:34:21] whatever, and then I'll CPAN all this stuff in, and I'll give it over to the developer, tell them to set their shebang to that and everything just works. And now we're in a mode where it's like, okay, you got to set up a thousand of those. “Okay, well, I'll make a tarball.” [laugh]. But it's still like we had to just—Corey: DevOps, but [unintelligible 00:34:37] dev closer to ops. You're interrelating all the time. Yeah, then Docker comes along, and add dev is, like, “Well, here's the container. Good luck, asshole.” And it feels like it's been cast into your yard to worry about.Amy: Yeah, well, I mean, that's just kind of business, or just—Corey: Yeah. Yeah.Amy: I'm not sure if it's business or capitalism or something like that, but just the idea that, you know, if I can hand off the shitty work to some other poor schlub, why wouldn't I? I mean, that's most folks, right? Like, just be like, “Well”—Corey: Which is fair.Amy: —“I got it working. Like, my part is done, I did what I was supposed to do.” And now there's a lot of folks out there, that's how they work, right? “I hit done. I'm done. I shipped it. Sure. It's an old [unintelligible 00:35:16] Ubuntu. Sure, there's a bunch of shell scripts that rip through things. Sure”—you know, like, I've worked on repos where there's hundreds of things that need to be addressed.Corey: And passing to someone else is fine. I'm thrilled to do it. Where I run into problems with it is where people assume that well, my part was the hard part and anything you schlubs do is easy. I don't—Amy: Well, that's the underclass. Yeah. That's—Corey: Forget engineering for a second; I throw things to the people over in the finance group here at The Duckbill Group because those people are wizards at solving for this thing. And it's—Amy: Well, that's how we want to do things.Corey: Yeah, specialization works.Amy: But we have this—it's probably more cultural. I don't want to pick, like, capitalism to beat on because this is really, like, human cultural thing, and it's not even really particularly Western. Is the idea that, like, “If I have an underclass, why would I give a shit what their experience is?” And this is why I say, like, ops teams, like, get out of here because most ops teams, the extant ops teams are still called ops, and a lot of them have been renamed SRE—but they still do the same job—are an underclass. And I don't mean that those people are below us. People are treated as an underclass, and they shouldn't be. Absolutely not.Corey: Yes.Amy: Because the idea is that, like, well, I'm a fancy person who writes code at my ivory tower, and then it all flows down, and those people, just faceless people, do the deployment stuff that's beneath me. That attitude is the most toxic thing, I think, in tech orgs to address. Like, if you're trying to be like, “Well, our liability is bad, we have security problems, people won't fix their code.” And go look around and you will find people that are treated as an underclass that are given codes thrown over the wall at them and then they just have to toil through and make it work. I've worked on that a number of times in my career.And I think just like saying, underclass, right, or caste system, is what I found is the most effective way to get people actually thinking about what the hell is going on here. Because most people are just, like, “Well, that's just the way things are. It's just how we've always done it. The developers write to code, then give it to the sysadmins. The sysadmins deploy the code. Isn't that how it always works?”Corey: You'd really like to hope, wouldn't you?Amy: [laugh]. Not me. [laugh].Corey: Again, the way I see it is, in theory—in theory—sysadmins, ops, or that should not exist. People should theoretically be able to write code as developers that just works, the end. And write it correct the first time and never have to change it again. Yeah. There's a reason that I always like to call staging environments in places I work ‘theory' because it works in theory, but not in production, and that is fundamentally the—like, that entire job role is the difference between theory and practice.Amy: Yeah, yeah. Well, I think that's the problem with it. We're already so disconnected from the physical world, right? Like, you and I right now are talking over multiple strands of glass and digital transcodings and things right now, right? Like, we are detached from the physical reality.You mentioned earlier working in data centers, right? The thing I miss about it is, like, the physicality of it. Like, actually, like, I held a server in my arms and put it in the rack and slid it into the rails. I plugged into power myself; I pushed the power button myself. There's a server there. I physically touched it.Developers who don't work in production, we talked about empathy and stuff, but really, I think the big problem is when they work out in their idea space and just writing code, they write the unit tests, if we're very lucky, they'll write a functional test, and then they hand that wad off to some poor ops group. They're detached from the reality of operations. It's not even about accountability; it's about experience. The ability to see all of the weird crap we deal with, right? You know, like, “Well, we pushed the code to that server, but there were three bit flips, so we had to do it again. And then the other server, the disk failed. And on the other server…” You know? [laugh].It's just, there's all this weird crap that happens, these systems are so complex that they're always doing something weird. And if you're a developer that just spends all day in your IDE, you don't get to see that. And I can't really be mad at those folks, as individuals, for not understanding our world. I figure out how to help them, and the best thing we've come up with so far is, like, well, we start giving this—some responsibility in a production environment so that they can learn that. People do that, again, is another one that can be done wrong, where it turns into kind of a forced empathy.I actually really hate that mode, where it's like, “We're forcing all the developers online whether they like it or not. On-call whether they like it or not because they have to learn this.” And it's like, you know, maybe slow your roll a little buddy because the stuff is actually hard to learn. Again, minimizing how hard ops work is. “Oh, we'll just put the developers on it. They'll figure it out, right? They're software engineers. They're probably smarter than you sysadmins.” Is the unstated thing when we do that, right? When we throw them in the pit and be like, “Yeah, they'll get it.” [laugh].Corey: And that was my problem [unintelligible 00:39:49] the interview stuff. It was in the write code on a whiteboard. It's, “Look, I understood how the system fundamentally worked under the hood.” Being able to power my way through to get to an outcome even in language I don't know, was sort of part and parcel of the job. But this idea of doing it in artificially constrained environment, in a language I'm not super familiar with, off the top of my head, it took me years to get to a point of being able to do it with a Bash script because who ever starts with an empty editor and starts getting to work in a lot of these scenarios? Especially in an ops role where we're not building something from scratch.Amy: That's the interesting thing, right? In the majority of tech work today—maybe 20 years ago, we did it more because we were literally building the internet we have today. But today, most of the engineers out there working—most of us working stiffs—are working on stuff that already exists. We're making small incremental changes, which is great that's what we're doing. And we're dealing with old code.Corey: We're gluing APIs together, and that's fine. Ugh. I really want to thank you for taking so much time to talk to me about how you see all these things. If people want to learn more about what you're up to, where's the best place to find you?Amy: I'm on Twitter every once in a while as @MissAmyTobey, M-I-S-S-A-M-Y-T-O-B-E-Y. I have a blog I don't write on enough. And there's a couple things on the Equinix Metal blog that I've written, so if you're looking for that. Otherwise, mainly Twitter.Corey: And those links will of course be in the [show notes 00:41:08]. Thank you so much for your time. I appreciate it.Amy: I had fun. Thank you.Corey: As did I. Amy Tobey, Senior Principal Engineer at Equinix. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, or on the YouTubes, smash the like and subscribe buttons, as the kids say. Whereas if you've hated this episode, same thing, five-star review all the platforms, smash the buttons, but also include an angry comment telling me that you're about to wind up subpoenaing a copy of my shell script because you're convinced that your intellectual property and secrets are buried within.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.