Podcasts about Apache

Share on
Share on Facebook
Share on Twitter
Share on Reddit
Share on LinkedIn
Copy link to clipboard

Several groups of indigenous peoples of the United States

  • 1,401PODCASTS
  • 2,536EPISODES
  • 53mAVG DURATION
  • 1DAILY NEW EPISODE
  • Jul 1, 2022LATEST
Apache

POPULARITY

20122013201420152016201720182019202020212022


Best podcasts about Apache

Show all podcasts related to apache

Latest podcast episodes about Apache

En Perspectiva
Entrevista Alejandro Stipanicic - Exploración de petróleo y gas en aguas de Uruguay

En Perspectiva

Play Episode Listen Later Jul 1, 2022 50:51


Uruguay retomará la búsqueda de petróleo y gas en su plataforma marítima, una tarea que se llevó a cabo por última vez en 2016, sin resultado positivo. La semana pasada Ancap adjudicó a las multinacionales Shell y Apache Corporation tres de los seis bloques disponibles en la plataforma continental uruguaya para la búsqueda de estos hidrocarburos. Dos bloques fueron asignados a Shell, que se comprometió a efectuar un programa exploratorio, además de invertir en un modelado 3D. En tanto, Apache dio un paso adicional y se comprometió en su bloque a la perforación de un pozo en un período inicial de cuatro años. Estas dos resoluciones, que ahora deben ser avaladas por el Poder Ejecutivo, se suman al contrato firmado el 25 de mayo entre Ancap y la compañía Challenger Energy para la exploración de un cuarto bloque. En ese contrato la empresa se compromete a la evaluación y modelado geológico y de recursos prospectivos del área, así como el licenciamiento y reprocesamiento de información sísmica 2D existente. Las autoridades de Ancap destacaron el interés de empresas “de primer nivel” para volver a colocar a Uruguay en el mapa petrolero mundial. Sin embargo, desde la academia y organizaciones ambientalistas se señala que el anuncio implica un “retroceso” en materia ambiental, cuando el mundo y también este gobierno están apostando por el desarrollo de energías verdes. Ayer conocimos el punto de vista crítico de Omar de Feo, Dr. en Ciencias del Mar.  Hoy conversamos En Perspectiva con el presidente de Ancap, ingeniero Alejandro Stipanicic.

En Perspectiva
Entrevista Omar Defeo - Ancap adjudicó tres bloques para la búsqueda de petróleo y gas en el mar

En Perspectiva

Play Episode Listen Later Jun 30, 2022 43:59


Uruguay volvió la semana pasada al mapa petrolero mundial. Ancap anunció el jueves 23 la adjudicación de tres bloques en la plataforma marítima uruguaya para la exploración de petróleo y gas. Dos bloques fueron adjudicados a la compañía Shell y el restante a Apache Corporation. En el caso de Shell, el compromiso es efectuar un programa exploratorio en los dos bloques, además de invertir en modelado 3D. Apache dio un paso adicional y se comprometió a la perforación de un pozo exploratorio en un período inicial de cuatro años. Ahora Ancap debe elevar al Poder Ejecutivo la resolución y luego proceder con la firma de los contratos para que las dos firmas puedan empezar las actividades. Pese a que el gobierno celebró “el retorno de empresas de primer nivel mundial al mar uruguayo a explorar petróleo y gas” desde la academia y organizaciones ambientalistas se señala que el anuncio implica un “retroceso” en materia ambiental, cuando el mundo y el gobierno están apostando por el desarrollo de energías verdes. Hoy y mañana vamos a profundizar en esta discusión. Mañana el diálogo será con el presidente de Ancap, Alejandro Stipanicic. Hoy conversamos En Perspectiva con Omar Defeo, ecólogo, integrante del Laboratorio de Ciencias del Mar de la Facultad de Ciencias de la Universidad de la República.

Global Club Vibes
01 REC - 2022 - 06 - 29 Global Club Vibes 29 Juni Week 26 2022

Global Club Vibes

Play Episode Listen Later Jun 29, 2022 59:46


# - Titel van muziekstuk - Artiest - Album - Genre - Duur 1. Running Up That Hill (KREAM Remix) (Clean Extended) - Kate Bush - Unknown Album - Future House - 04:57 2. Dial M for Moguai - Beatbox - Unknown Album - Dance - 03:51 3. None answer By DJWimpossible - Dj Wimpossible - Unknown Album - Dance/Techno - 05:14 4. Confused - D-diN - The Switch - House - 04:33 5. Lotus - Mumbai Science - Solid Sounds 2011 Volume 2 Cd 2 - Dance - 05:32 6. We No Speak Americano [Tech House Party Starter Edit] - Collini x Yolanda Be Cool - The Chemist Music - Dance/Mashup - 03:04 7. SWEET FERRARI (PARKAH & DURZO x N4C VIP EDIT) - JAMES HYPE x EURYTHMICS - Unknown Album - Dance/Mashup - 03:41 8. One Way Ticket vs. Abcdefu (Maze Mashup) - Nari vs. Gayle - Unknown Album - Dance/Mashup - 05:11 9. These gypsy sounds [jmd 2022 discofied bootleg] - Chicago, Crystal Waters, NeverDull, Bucketheads & DeLa Soul - JMD - theese gypsy sounds - Dance/Mashup/House - 05:40 10. Apache vs Pepas (YO-TKHS Mashup) - Dirty Ducks vs Farruko - 2022 MASHUP PACK Vol.3 - Dance/Mashup - 04:48 11. Hello (Febration Remix) [EXTENDED] - Martin Solveig - Unknown Album - Dance - 03:40 12. Green Green Grass (Sam Feldt Remix) (Clean Extended) - George Ezra - Unknown Album - Dance Pop - 03:25 13. Uptown funk (Ayur Tsyrenov DFM remix) - Mark Ronson feat. Bruno Mars - Unknown Album - Dance - 03:50 14. Can't Get You Out Of My Head (Nathan Woods Edit) - Kylie Minogue - Unknown Album - Dance - 05:04 15. Work It (Sir Gio VIP Edit) - Missy Elliott X Harry Romero - Unknown Album - Dance - 03:07

The Vox Markets Podcast
764: Eytan Uliel of Challenger Energy explains how licencing bids by oil majors in Uruguay validates their strategy

The Vox Markets Podcast

Play Episode Listen Later Jun 27, 2022 13:14


Eytan Uliel, CEO of Challenger Energy #CEG explains how the entry into Uruguay of Shell & APA Corporation and the commitment by both to undertake meaningful work programs during an initial exploration period, validates both the Company's decision to enter Uruguay in 2020 and underscores the solid technical foundation and excellent value proposition represented by their OFF-1 block. Highlights ·   On 23 June 2022 ANCAP, the Uruguayan state-owned petroleum company, advised publicly that three offshore blocks in Uruguay have been licenced following bids received in the most recent ANCAP 2022 Open Bidding Round. ·   Two blocks have been awarded to Shell - the shallow offshore block immediately adjacent to Challenger's OFF-1 block (AREA OFF-2), and one deep-water block (AREA OFF-7). ANCAP has reported that the work Shell committed to undertake in relation to these blocks in the initial 4-year exploration period includes the acquisition of new 3D seismic. ·   One deep-water block (AREA OFF-6) has been awarded to APA Corporation (formerly Apache). ANCAP has reported that the work APA Corporation committed to undertake in relation to this block in the initial 4-year exploration period includes the drilling of an exploration well. ·   The award of these three blocks is in addition to the OFF-1 block previously awarded to Challenger. Of the three new blocks awarded, the OFF-2 block, which is directly adjacent to Challenger's OFF-1 block, was the only block which received competing bids, with both Shell and APA Corporation having submitted proposals. ·   The aggregate value of work committed across blocks OFF-2, OFF-6 and OFF-7 by Shell and APA Corporation in the next 4 years, in respect of both technical and exploration activities including well drilling by APA Corporation, is stated by ANCAP to be approximately US$200 million. To read the full RNS click HERE

Dal fondo del Sand Creek
Apache vuol dire nemico - Geronimo

Dal fondo del Sand Creek

Play Episode Listen Later Jun 25, 2022 59:02


Chi non conosce Geronimo, il simbolo stesso della caparbia e irriducibile resistenza apache.

Blue Island Radio Podcast
BIRP 152 - STEEV CUSTER

Blue Island Radio Podcast

Play Episode Listen Later Jun 25, 2022 76:41


On today's episode of the podcast Brandon and AP Lindsay are joined by special guest Steev Custer who, as a member of such bands as Fractured Adolescents, My Big Beautiful, Boneyard Brawlers, The Bomb, and Death & Memphis, has been an active member of the Chicagoland music scene for more than 30 years. Together they discuss Steev's hometown Joliet, IL., band life, and the one through line through each of these bands, his friend and bandmate Paul Garcia. We also discuss his Fine Tunes School of Music, the impending Death & Memphis EP and his uncanny ability for landing himself in Facebook “Jail”. Mini-Intro song by Niko Riley. Main Theme song: Apache by Jorgan Ingmann Instagram: @birp60406 Facebook: @blueislandradio Twitter: @birp60406 If you'd like to support the show visit Patreon.com/blueislandradio LINKS: https://www.facebook.com/DeathandMemphis https://deathandmemphis.bandcamp.com/  

The WP Minute
What would GoDaddy's WordPress look like?

The WP Minute

Play Episode Listen Later Jun 24, 2022 9:11


Whoever thought that Apache web server would be de-throned in it's prime? Hello NGINX. We see you Cloudflare. Red Hat and Fedora linux showed up, but then the world went faster together with Ubuntu. Intel dominated the chip space forever. Still does, technically, but AMD and Apple are going after their lunch including the paper bag it's packed in. Sprinkle in the open source coding languages, tooling, and protocols over the last 30 years and everyone shouts open operability — until they get control — and then it's “our way is better than your way, see ya later.” Why I want WordPress to win Probably for all of the reasons you do too. I love the software, it affords me a career, a specific lifestyle, and it puts food on the table. I think WordPress is the best piece of software around to help drive a technical workforce. First, because of its flexibility. Second, because it's open source. But not open source like Swift — which is locked into Apple. WordPress can run and do a lot more than other “closed” open source projects. The open source software could be powerful for local community programs that train, spread awareness, and deploy solutions around WordPress which leave real impacts on society. An approachable solution to publish and consume local government topics which are crucial to a town's population. Non-profit and news that sorely need a low-cost solution to democratize publishing. Understanding how programming, the internet, and technology works for a young (or old!) demographic. I want WordPress to win because of that, not because it makes a prettier website than Wix. The desire for open source should not be the desire for control If you love open source, you have to love the fact that you're not in control. It's going to be dealing with the ups and downs, letting humans settle the issues at hand. You hate a feature? Too bad, wait for someone to change it. Your favorite part of code just got shipped? Now stand and defend its existence in each future version. Not in control? Fork it. Me? No. You? Doubt it. But GoDaddy could. It wouldn't be easy. None of this is easy. Who said it would be? Open source is giving up direct control, knowing that you have to deal with the wait: volunteering, funding, resources, project direction, etc. It means dealing with the flaws of humans or herding cats, as some call it. Otherwise you put someone in control, let them decide all the things, and you get something that isn't open source. It's called Apple, where they build a great commercial product but only release a sliver of it through open source. It's the brittle timeline of WordPress we're living in now. On one hand, we need a leader like Matt, on the other he's a benevolent dictator that doesn't want to leave. On one hand, he needs the community to rally around the cause, volunteer at all the things, and generally drive innovation for good. On the other hand, he can walk into any board room with his 43% of the pie, and raise enough money to do it all himself — WordCamps and all. But he'd still have his kryptonite: Time. In defense of Matt Mullenweg I don't envy his position, plus I think he does way too much. .org release lead, CEO of Automattic and the dozen+ products it has, Tumblr guy, investor, I think philanthropist, and then he has to live a life. My gut tells me that none of this is moving fast enough for him. WordPress competing with other platforms, WooCommerce being more real, and exercising this desire to weave open source (through WordPress) into the fabric of web technologies.

Ubuntu Security Podcast
Episode 165

Ubuntu Security Podcast

Play Episode Listen Later Jun 24, 2022 34:11


This week Camila dives into the details on some of the most prolific buzzwords flying around the cybersecurity community, plus we cover security updates for BlueZ, the Linux kernel, Intel Microcode, QEMU, Apache and more.

Pursuit of the Paranormal
June 2022 UAP Round Table with UFO Thinker & PotP - Latest UFO News and Videos

Pursuit of the Paranormal

Play Episode Listen Later Jun 23, 2022 85:07


June 2022 UAP Round Table with UFO Thinker & PotP - Latest UFO News and Videos This month we are joined by special guest Dave Smethurst as we discuss the very latest UAP news from around the world, taking a casual look at: Lue Elizondo's Inspector General complaint; NASA launching a UAP study; UFO seen during the platinum jubilee celebrations; Apache helicopter recording three UAP; UFO video from Niagara Falls; Jeremy Corbell's triangle UFO video being a drone, or not a drone ———————————————————-——— Follow Frank @ UFO Thinker Podcast Support the show from just £1 at www.buymeacoffee.com/paranormalpod Share your story or contact us to say Hi! at podcast@pursuitoftheparanormal.co.uk Check out our brand new Merch Store at https://linktr.ee/pursuitoftheparanormal --- Send in a voice message: https://anchor.fm/pursuitoftheparanormal/message

MDR KULTUR Hörspiele und Lesungen
Podcast-Empfehlung: "Winnetou ist kein Apache"

MDR KULTUR Hörspiele und Lesungen

Play Episode Listen Later Jun 23, 2022 3:37


MDR KULTUR-Redakteur Ben Hänchen liebt Karl May. Seit seiner Kindheit steht er auf Deutschlands kleinster Karl-May-Bühne. Aber ist das noch zeitgemäß? Im Podcast "Winnetou ist kein Apache" geht er dieser Frage nach.

MDR KULTUR Unter Büchern mit Katrin Schumacher

Wir sprechen mit Autor Ben Hänchen über seinen Podcast "Winnetou ist kein Apache". Wir tauchen tief in die Romantik mit E.T.A. Hoffmann, der vor 200 Jahren starb. Und blättern im Essay "Das Loch" von Wolfgang Hagen.

MDR KULTUR Features und Essays
Podcast-Empfehlung: "Winnetou ist kein Apache"

MDR KULTUR Features und Essays

Play Episode Listen Later Jun 21, 2022 3:37


Sind Karl-May-Festspiele noch zeitgemäß? Im Podcast "Winnetou ist kein Apache" geht MDR-KULTUR-Redakteur Ben Hänchen dieser Frage nach und trifft Menschen mit ganz unterschiedlichen Ansichten. Jetzt in der ARD AUDIOTHEK.

My Dark Path
Vegas Field Trip, Part 2: The Spooks Are On the House

My Dark Path

Play Episode Listen Later Jun 21, 2022 48:07


Episode Summary: My Dark Path podcast explores the fringes of history, science, and the paranormal. This episode is a continuation of the “Vegas Field Trip” where stories of eerie  happenings are explored as a backdrop following different tragic and fatal events  in the past.In this conversation, Thurkettle, Townsend, and Hodur explored hotel hallways,  walking the floors of casinos ranging from some of the oldest to the biggest and  most glamorous. Shared in this episode are more clips recorded by the team  in the very places they were discussing in the pedestrian hallways around  Bally's, on the main floor of the Luxor, or in a restaurant in Binion's. Episode HighlightsAbout today's conversation; More experiences of Thurkettle,  Townsend, and Hodur in the dark tales of Las Vegas. The ghosts of Benny Binion's hotel. La Palazza Mansion; The Death House Ghosts from the sins of corporations; the MGM fire disaster. The Curse of the LuxorA few Celebrity ghosts.Zac Bagans' Haunted MuseumNotes:Three storytellers, Thurkettle, Townsend, and Hodur, rendezvoused in Sin City for  a special My Dark Path field trip, recording clips of discussions had in key places  surrounded by stories of supernatural happenings. The first clip was recorded in  The El Cortez where the supposedly haunted room, 3300, sits in the historic wing  our team was exploring. One of the biggest major criminal entities who made a  fortune in driving the evolution of Las Vegas was Benny Binion; his hotel tells all  about its ghosts. Despite being a convicted murderer and an experienced gambling hall boss even before his initial arrival to Vegas, there is a statue of Benny in Vegas today. His story started in Texas where he was born in 1904, but couldn't go to  school due to chronic poor health. Hence, Benny got his education by  accompanying his father, a horse trader, on trips throughout the wild, wild west  where many fellow horse traders also gambled. As a teenager, Benny got more involved in the gambling business till he moved to  El Paso where he began bootlegging and even committed murders, but walked  scot-free based on his influence. When his destructive nature attracted attention  beyond his influence, he moved to Las Vegas where he set up the Binion's  Horseshoe Casino, leveraging higher stakes than other casinos to attract high  rollers, as well as many other perks that transformed gambling in Vegas to what it  would evolve to become today. In the end, the law caught up with Benny as he was  arrested for tax evasion and lost his Nevada gaming license but "The hotel  Apache", the only section of Binion's with its name restored, is the only  hotel that will openly tell you it is haunted. At the front desk, there's a  pamphlet describing its history of haunted encounters with a card to report yours;  this list is on the Dark Path Website. Interestingly, most cases were reported in  the same rooms or areas of the hotel, with no explanation from the hotel as to why. Another place in the suburbs known for supernatural events is the La  Palazza Mansion also known as The Death Mansion, The Devil's Mansion, and  The Hell House. Located in a residential neighborhood, miles from the Las Vegas  strip, it was once owned by Tony “The Ant” Spilotro, who was an enforcer for one  of the deadliest gangs in Vegas. Rumored to be the place where many of Tony's  heinous acts were carried out, the house is also known for legends surrounding it  like having dead bodies in the backyard and a drain in a room for spilled blood to  flow out. La Palazza does not offer ghost tours but there are stories of previous  owners like Chris Martinez, who led the Ghost Ad

Cage Fighting: Answering the Big Questions in Film

Cage starring in a Bird-based, Armed-forces-themed movie?! Most actor's don't even have one of those credits to their name, Cage has two. The question is; Is Fire Birds (AKA Wings of the Apache) as godawful as Birdy was? Pop in your earphones and find out. Socials: @CageFightingPod Emails: CageFightingPod@gmail.com --- Send in a voice message: https://anchor.fm/cage-fighting/message

airhacks.fm podcast with adam bien
Becoming an Apache Maven Committer

airhacks.fm podcast with adam bien

Play Episode Listen Later Jun 19, 2022 54:36


An airhacks.fm conversation with Karl Heinz Marbaise (@khmarbaise) about: PET 2001 was the first computer, enjoying programming at school, writing Basic and assembly code on Commodore CBM 4000, writing software for Commodore 1 PCB, finally getting a Commodore 64, programming extruder mesh machines, writing floating point libraries on Intel 8080, the connection between computers and math, starting with Turbo Pascal, C and C++ and Turbo C, studying part time, working full time, tracking cars with GPS in Delphi, implementing a new language in lex, yacc and bison, banks were using the OS/2 Warp operating system, working with Visual Basic, starting with Java 1.4 in 2004, working with PHP and MySQL, SOAP with PHP, developing an internal sourceforge, write simple code and enjoy JVM performance, starting with Ant then migrate to Maven 2, Apache Jelly the executable XML, Convention over Configuration with Maven, Apache Continuum, AnthillPro and CruiseControl, becoming a Maven committer, Apache Axis 2, using Hudson for CI/CD, contributing to open source at Deutsche Boerse, working with Robert Scholte, airhacks.fm episode with Robert: "#28 More Conventions with Maven.next", working as DevOps engineer, Karl Heinz Marbaise on twitter: @khmarbaise

Casus Belli Podcast
CBP #269 Nayaf 2007 - Batalla de Zarqa - Guerra de Irak

Casus Belli Podcast

Play Episode Listen Later Jun 18, 2022 232:33


El 27 y 28 de enero del 2007, un enfrentamiento en una ciudad aledaña a Nayaf, las fuerzas iraquíes se enfrentaron a los Soldados del Cielo, una secta mesiánica de inspiración chiita que ya había causado problemas anteriormente. Pero esta vez el levantamiento superó las expectativas, y se sumaron al combate unidades norteamericanas, incluyendo Rangers y otras unidades de fuerzas especiales. Fue necesario el apoyo aéreo ofrecido por F-16, helicópteros Apache, y CAS A-10 Warthogs para poder ganar una batalla muy complicada. Te lo cuenta el G-4 al completo: 🏍 Julio Caronte, ⚓️ Esaú Rodríguez,🦕 Antonio Gómez y 👩‍🚀 Dani CarAn. Casus Belli Podcast pertenece a la 🏭 Factoría Casus Belli. Casus Belli Podcast forma parte de 📀 Ivoox Originals. 👉https://podcastcasusbelli.com 👉En Facebook, nuestra página es @casusbellipodcast https://www.facebook.com/CasusBelliPodcast 👉En Instagram estamos como @casusbellipodcast https://www.instagram.com/casusbellipodcast 👉En Twitter estamos como @casusbellipod y @podcastvictoria 👉Telegram, nuestro canal es @casusbellipodcast https://t.me/casusbellipodcast 👨‍💻Nuestro chat del canal es https://t.me/aviones10 ⚛️ Los logotipos aparecidos en la 🏭 Factoría Casus Belli están diseñados por Publicidad Fabián publicidadfabian@yahoo.es 🎵 La música incluida en el programa es toda bajo licencia CC. https://creativecommons.org/licenses/by-nd/3.0/, o licencias privadas de Epidemic Music, Jamendo Music o SGAE de Ivoox. 📧¿Queréis contarnos algo? También puedes escribirnos a casus.belli.pod@gmail.com Escucha el episodio completo en la app de iVoox, o descubre todo el catálogo de iVoox Originals

OSOM First Hour
2022-06-18 EM-Imaging Team It Only Takes One White Crow

OSOM First Hour

Play Episode Listen Later Jun 17, 2022 64:25


Guest Page Fast links to Items:  Richard – Ron – Robert – Jonathan – Keith – Ruggero Fast links to Bios:   Ron – Keith – Ruggero – Jonathan – Robert Support The Other Side of Midnight! “It Only Takes One White Crow ….” “It only takes one white crow ….” Living in the “Land of Enchantment,” surrounded by Native Americans, I was struck long ago by the stark wisdom underlying one old Apache saying– “It only takes one white crow … to PROVE all crows aren't black!” For many years now, I have pursued that “one white crow” — that ONE ancient Martian artifact or ruin that could ultimately prove the fundamental truth I have been insisting for so long: That we are all living in nothing less than an ancient– “Designer Solar System!” Then, a few weeks ago, NASA found “a door” … on Mars! Impossibly — while NASA's official reaction (and [...]

Carole Baskins Diary
2017-10-26 Carole Baskin's Diary

Carole Baskins Diary

Play Episode Listen Later Jun 16, 2022 2:01


Apache Bobcat is Euthanized Note to volunteers:  This morning Apache Bobcat's Keepers reported that in addition to not eating this morning, he had vomited and was "acting weird."  We took him into the West Boensch Recovery Hospital to keep him comfortable and called Dr. Wynn.  She couldn't break free from her clinic until later on tonight.  We noticed on the webcam that he was acting disoriented and went to check on him.  It was obvious that he was near death so we asked if we could bring Apache to Dr. Wynn's office to put him to sleep.  She got him in right away, but he was so ready to go that he died after being sedated.  He had a good run here for the past 22 years and it was all because of the work you have done to keep him groomed, fed and hydrated.   Apache and I had a pact. Whenever I gave tours, I'd wait to talk about the cruelty of the fur industry until I got to Apache's cage. I'd say, "It takes 20 bobcats to make a fur coat because they only use that little bit of white, spotted, belly fur..." at which point I'd make a sweeping motion toward Apache who would almost always, right on cue, stand up on his back feet, with his forepaws kneading at the wire to hold himself up, so everyone could see the belly fur. You might think it operant conditioning, but he was the one who started the little game, and I finally caught on that he was helping make the point. In later years I had to quit because he was too old for that pose and I didn't want him to hurt himself.   https://bigcatrescue.org/apache/    Hi, I'm Carole Baskin and I've been writing my story since I was able to write, but when the media goes to share it, they only choose the parts that fit their idea of what will generate views.  These are my views and opinions. If I'm going to share my story, it should be the whole story.  The titles are the dates things happened. If you have any interest in who I really am please start at the beginning of this playlist: http://savethecats.org/   I know there will be people who take things out of context and try to use them to validate their own misconception, but you have access to the whole story.  My hope is that others will recognize themselves in my words and have the strength to do what is right for themselves and our shared planet.     You can help feed the cats at no cost to you using Amazon Smile! Visit BigCatRescue.org/Amazon-smile   You can see photos, videos and more, updated daily at BigCatRescue.org   Check out our main channel at YouTube.com/BigCatRescue   Music (if any) from Epidemic Sound (http://www.epidemicsound.com) This video is for entertainment purposes only and is my opinion.  Closing graphic with permission from https://youtu.be/F_AtgWMfwrk  

Minnesota Vikings - Wobcast
MVP - Special Teams Assistant Ben Kotwica On His NFL Experience & The Joy Of Coaching | Episode 151

Minnesota Vikings - Wobcast

Play Episode Listen Later Jun 14, 2022 41:00


Special Teams Assistant Coach Ben Kotwica joins Tatum Everett, Gabe Henderson and Producer Jay Nelson this week on the podcast. "Coach K" (sorry Gabe) has used his experiences growing up in Chicago, attending West Point, flying Apache helicopters and more to help navigate his way through his NFL career. He shares what gives him his motivation at this stage professionally and what he looks forward to most with this 2022 Vikings squad. Tatum, Gabe and Jay also discuss the latest Colin Cowherd hot take, plus preview some of the other great content we have coming up in the next few weeks. The players may be enjoying some R & R, but there is still plenty to talk about on Episode 151 of the Minnesota Vikings Podcast.

Minnesota Vikings - Wobcast
MVP - Special Teams Assistant Ben Kotwica On His NFL Experience & The Joy Of Coaching | Episode 151

Minnesota Vikings - Wobcast

Play Episode Listen Later Jun 14, 2022 41:03


Special Teams Assistant Coach Ben Kotwica joins Tatum Everett, Gabe Henderson and Producer Jay Nelson this week on the podcast. "Coach K" (sorry Gabe) has used his experiences growing up in Chicago, attending West Point, flying Apache helicopters and more to help navigate his way through his NFL career. He shares what gives him his motivation at this stage professionally and what he looks forward to most with this 2022 Vikings squad. Tatum, Gabe and Jay also discuss the latest Colin Cowherd hot take, plus preview some of the other great content we have coming up in the next few weeks. The players may be enjoying some R & R, but there is still plenty to talk about on Episode 151 of the Minnesota Vikings Podcast.

Blue Island Radio Podcast
BIRP 151 - CHICAGO STYLE with Nick and King Onion

Blue Island Radio Podcast

Play Episode Listen Later Jun 9, 2022 92:38


On today's episode of the podcast Brandon is joined by friends and fellow Blue Islanders Nick Stankus and Scottie "King Onion" Armstrong to discuss Chicago and some of the things that make it unique. Hint: It's just 90 minutes of people talking about pizza. Oh yeah, and they also take some phone calls. Mini-Intro song by Niko Riley Main Theme song: Apache by Jorgan Ingmann Instagram: @birp60406 Facebook: @blueislandradio Twitter: @birp60406 If you'd like to support the show visit Patreon.com/blueislandradio  

Prostor X
Ukrajinci by měli Rusáky nakopat a vyhnat, říká válečný veterán Lumír Neměc, který zatýkal Kajínka - podcast

Prostor X

Play Episode Listen Later Jun 9, 2022


Přesvědčení, že budoucnost se mění okamžikem, nezastával bezpečnostní poradce Lumír Němec vždy. Vrátil se s ním z války.  „Bavil jsem se s britským vojákem, mladým klukem, a ten říkal, že je to jeho poslední mise u pěchoty, že se vrací za tři týdny domů a chce jít dělat pilota Apache (bitevní vrtulník pozn. red.). A druhý den se útočilo na Rahim Kalay, což bylo městečko v provincii, kde jsme byli. On to schytal od snipera,“ popisuje bývalý velitel operační skupiny SOG v Afghánistánu a účastník misí v Kosovu i Bagdádu zážitek, který ho přiměl přehodnotit přístup k životu i smrti, jež vnímá jako jeho nedílnou součást. Ať už měl ale na sobě policejní, nebo vojenskou uniformu, nikdy si ji nepřipouštěl.

@BEERISAC: CPS/ICS Security Podcast Playlist
41: Writing a Book to Leverage Your Expertise and Improve Your Career with Pascal Ackerman

@BEERISAC: CPS/ICS Security Podcast Playlist

Play Episode Listen Later Jun 7, 2022 49:35


Podcast: Control System Cyber Security Association International: (CS)²AIEpisode: 41: Writing a Book to Leverage Your Expertise and Improve Your Career with Pascal AckermanPub date: 2022-06-07Derek Harp is happy to welcome Pascal Ackerman as his guest for today's podcast!Pascal is a security professional, focused on industrial control systems and he's currently the Managing Director of Threat Services at ThreatGEN. He has a Master's of Science degree in Electrical Engineering (MSEE/CE). He has had 18 years of experience in industrial Ethernet design and support, information and network security, risk assessments, pen-testing, forensics, and threat hunting, WAN/LAN/Internet and Wireless Technologies, Windows Environments, Unix, Linux, IIS, and Apache.He specialized in the architecture, engineering, and securing of plant-wide Ethernet networks using Purdue-model design strategies, IDS/IPS sensors, network monitoring, Security Information, and Event Management (SIEM) solutions, next-gen firewalls, MS domain services, WSUS servers, MS SQL server clusters, etc.Pascal was born and raised in the Netherlands. Right after leaving high school, he was put behind a POC by a company that sent him out across the world installing prototype machinery for filling machines. He is an engineer, programmer, gamer, hacker, traveler, tinkerer, pen-tester, and father. In this episode of the (CS)²AI Podcast, he shares his superhero backstory and discusses his certifications, his education, and his career path. He also offers advice for those who would like to get into the field of cybersecurity and people thinking about writing a book.If you are considering a career in cybersecurity or if you are an engineer and want to specialize in cyber security, you will gain a lot from this podcast! Stay tuned for more!Show highlights:After leaving college, Pascal stayed with the company where he did his internship. The company got him to set up a software simulation to test their POC programs and later put him on their commissioning team. (6:51)Pascal talks about what he did while working as a controls engineer. (8:08)How Pascal got invited to move to the US to continue with his work. (9:50)Pascal explains how many doors opened for him after presenting his first report in 2005. (12:27)Pascal talks about how security measures first intersected with his work in 2008-2009. (14:07)Pascal pinpoints the moment when he decided to change his career path. (16:00)Pascal offers advice for traditional engineers who want to improve what they do and join the cyber security workforce. (17:35)A Network Plus certification will help controls engineers understand the fundamentals of networking. (18:19) Pascal explains why he got hired as a commercial engineer in Network and Security at Rockwell. (21:16)Pascal talks about his book, Industrial Cybersecurity. (23:39)The book Hacking Exposed by Clint Bodungen inspired Pascal to write his first book. (27:50)How Threat GEN became a company based around a game Pascal developed. (29:10)Pascal offers advice on where people in IT who want to know more about safety, reliability, resiliency, and POCs can start. (32:36)The most successful companies have a combined IT and OT team with knowledgeable people on both sides. (36:43)Why do you need to figure out what you like the most and focus on that technology? (37:58)Architecture will be the next big step for monitoring everything. (45:06)Pascal discusses the process of writing his books and offers advice for those who would like to write a book. (45:49)Links:(CS)²AIPascal Ackerman on LinkedInIndustrial Cybersecurity by Pascal AckermanBooks mentioned:Hacking Exposed by Clint BodungenThe podcast and artwork embedded on this page are from Derek Harp, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

La Fantasmagórica - podcast futbol
135. El adiós de "El Apache" Tévez

La Fantasmagórica - podcast futbol

Play Episode Listen Later Jun 6, 2022 19:40


Carlos Tévez le dijo adiós a las canchas. Un niño que creció sin sus padres biológicos, que sufrió quemaduras de tercer grado y que se convirtió en ídolo del futbol argentino. Ignacio “El Fantasma” Suárez te cuenta la historia de " El Apache" en “La Fantasmagórica”, un podcast exclusivo de futvox. ¡Síguenos en redes sociales! Twitter: @FutvoxOficial Instagram: @futvoxoficial TikTok: @futvoxoficial Facebook: @futvoxoficial Learn more about your ad choices. Visit megaphone.fm/adchoices

Play Fútbol
Tévez: adiós al último jugador de barrio

Play Fútbol

Play Episode Listen Later Jun 6, 2022 70:20


Analizamos con Pakillo Mariscal la trayectoria del Apache, que ha anunciado que se retira. Además, repasamos lo mejor que nos deja el fútbol de selecciones y sus nombres propios: Frenkie De Jong, Tchouameni, Bale... Cerramos el episodio charlando con José Miguel Villarroya, historiador y periodista que acaba de publicar un libro sobre el fútbol alemán en la segunda parte del Siglo XX.

AZ: The History of Arizona podcast
Episode 100: A great joke

AZ: The History of Arizona podcast

Play Episode Listen Later Jun 6, 2022 30:15


In our 100th episode, things are a little tense at San Carlos. A new leader among the Chiricahua is pushing the limits, the Apache want to move some place better, the military commander and Indian Agent are at each other's throats, and two over-eager custom officials almost blow Geronimo finally turning himself into Crook.

Primary Sources
Lauren Redniss on the Art of Dance

Primary Sources

Play Episode Listen Later Jun 6, 2022 29:05


Lauren Redniss is the recipient of a MacArthur genius grant and the author of four remarkable works of visual nonfiction. These genre-defying books combine oral history, visual art, reportage, and archival research to create volumes that look a bit like graphic novels but read like nothing else you’ve ever experienced. Among them is Radioactive, a biography of the scientists Marie and Pierre Curie; Thunder and Lightning, a sprawling exploration of the weather; and Oak Flat, a work of original reportage about an Apache family trying to protect sacred land from a mining company in modern-day Arizona. Her newest project, a children’s book called Time Capsule, has just been released. When invited to talk about one of her deepest influences, Lauren might have discussed an oral historian she admires, such as Studs Terkel, or a painter to whom she has been compared, such as Paul Klee. Instead, she proposed talking about an entire artistic medium, which she considers to be her greatest source of inspiration: that of dance. In today’s episode, you’ll hear Lauren discuss the ways in which the multimedia nature of a dance performance has inspired her to create books that readers can experience as events unto themselves. She also talks about how the elements of discipline, pacing, and improvisation—which are all crucial to dance—inform her approach to her own work. And she tells us about how the New York City Ballet became the location of one of the most memorable—and politically transgressive—projects of her career. Primary Sources is a co-production of Public Books and Type Media Center. Our show’s executive producer is Caitlin Zaloom, the founding editor of Public Books. Our producer is DJ Cashmere. Our engineer is Jess Engebretson. Special thanks to Kelley Deane McKinney, the publisher and managing editor of Public Books and Taya Grobow, executive director of Type Media Center. Our theme music is “Kitty in the Window,” composed by Podington Bear (Attribution-NonCommercial 3.0 International License). View full episode notes and a transcript here.

Growing Native
Butterfly, Grasshopper, Beetle

Growing Native

Play Episode Listen Later Jun 5, 2022 5:08


Every time I pull a reference book or field guide off the shelf to read about a recently seen insect I seem to run across a quote by the famous entomologist E. O. Wilson. I like this comment I ran across recently on insects, calling them “the little things that run the world.” It's easy to see why someone would want to become an entomologist. You could specialize in any one of a number of orders in the Class Insecta; Hymenoptera, Coleoptera, Orthoptera, Lipidoptera…how many orders of insects are there? It depends who you talk to, but there are around thirty orders. Whoa, you could spend several lifetimes studying insects and never be done! This Growing Native episode only mentions three species from three different orders. I've got some learning to do! The photos are mine. The common buckeye butterfly is on an Apache plume shrub. The oak leaf grasshopper on the ground is among old oblong white oak leaves and the large leaves in the top right of the photo are sycamore. The fiery searcher ground beetle in my hand is with some of the old grass that came with the capture. It's a beautiful beetle!

NIGHT-LIGHT RADIO
Travis Walton UFO w/ Jennifer Stein, Travis Walton, & Host Dr. Bob Hieronimus

NIGHT-LIGHT RADIO

Play Episode Listen Later Jun 5, 2022 86:00


Jennifer W. Stein is a self-taught filmmaker who harnesses the power of the moving visual image to educate, inspire and empower. Jennifer uses film to help achieve her goals: to further her causes–global peace, gun control legislation, environmental awareness, and appreciation of ancient archaeology. The result: a powerful combination of community leadership and purposeful film making.  Jennifer collaborates with other filmmakers and learns from them. Her film, “TRAVIS: The True Story of Travis Walton” was recently released on DVD. In hour two we are joined by Travis Walton himself to describe his UFO Incident of 1975. While working as an American forestry worker in the Apache-sitgreaves National forests, near Snowflake, AZ . While riding in a truck with six of his coworkers, they encountered a saucer-shaped object hovering over the ground approximately 110 feet away, making a high-pitched buzz. Walton claims that after he left the truck and approached the object, a beam of light suddenly appeared from the craft and knocked him unconscious. The other six men were frightened and drove away. Walton awoke in a hospital-like room, being observed by three short, bald creatures. He claimed that he fought with them until a human wearing a helmet led Walton to another room, where he blacked out as three other humans put a clear plastic mask over his face. Walton remembers nothing else until he found himself walking along a highway five days later, with the flying saucer departing above him.  The case received enormous media coverage and has been called the best documented case of alien abduction on record. Despite terrific opposition from the skeptics, all the participants have passed lie-detector tests.      

Texas History Lessons
Daily Dose of Texas History - May 31, 1783 The Death of Fernando Veramendi

Texas History Lessons

Play Episode Listen Later May 31, 2022 14:28


On May 31, 1783, a band of Mescalero Apaches killed a man named Fernando Veramendi near the presidio of San Juan Bautista in Coahuila. Veramendi and the Veramendi family played an important part in the early history of Texas and of San Antonio. A San Antonio businessman and alderman, Veramendi was only about forty years old on May 31, 1783 when he was away from home on a business trip to Mexico City when he found himself at the mercy of the Apache raiders. Fernando had been born in Pamplona, Spain in either 1743 or 1744 and left Spain to practice his merchant trade in New Spain in search of success and wealth. He was in La Bahia, Texas by 1770 and his business occasionally required him to visit San Antonio, where he met and married married Doña María Josefa Granados on April 17, 1776. Her family were one of the famous Canary Islander settler families that had been brought to Texas 1731 to boost settlement of Texas.  After his marriage, his business thrived in San Antonio-he ran a store, loaned out money, and purchased large tracts of land. As his success grew, he gained the wealth to build a wonderful house on Soledad Street. This home became known as the Veramendi Palace.  His success made him a leader in community affairs. Veramendi was an alderman of the ayuntamiento in 1779 and in the year he died, 1783, he was elected senior alderman. His son, Juan Martin de Veramendi, was 4 and a half when his father died. He carried on in his father's successes and was elected vice governor of Coahuila y Texas in 1830 and was governor from 1832 to 1833. Fernando's granddaughter and Juan Martin's daughter, Ursala Maria married the notorious Texas legend Jim Bowie of Alamo fame in 1831, but sadly Juan Martin de Veramendi, wife Josefa, and Ursala Bowie died of cholera in 1833. As an added note, Ben Milam died in 1835 just outside or just inside the Veramendi house and he was first buried on the house's grounds before being reinterred elsewhere. The Texas History Lessons Theme song, Walking Through History, was written and recorded by Derrick McClendon. Listen to his new album, Interstate Daydreamer! Available everywhere you find good music. Thank you Derrick! Twitter: @dmclendonmusic The song at the end of the episode is by Texas History Lessons new spotlight artist, Colton Mathis. The song Fight, and a new one, Always Mad, are available everywhere you listen to music... If you are enjoying Texas History Lessons, consider buying me a cup of coffee by clicking here! Help make Texas History Lessons by supporting it on Patreon. And a special thanks to everyone that already does. Website: texashistorylessons.com email: texashistorylessons@gmail.com Twitter: @TexasHistoryL Learn more about your ad choices. Visit megaphone.fm/adchoices

AZ: The History of Arizona podcast
Episode 99: Chasing Charley

AZ: The History of Arizona podcast

Play Episode Listen Later May 30, 2022 29:40


In the fall of 1883, Crook and other Americans had two questions on their minds: What the heck was up with the Apache still in Mexico and where the heck was Charley McComas?

The Unforgiving60
S4E9–Cleared Hot! Shannon Huffman Polson on flying Apache Gunships, bagging big peaks and being a badass

The Unforgiving60

Play Episode Listen Later May 30, 2022 59:15


Shannon Polson was one of Americas first female gunship pilots. We talk flying and that incredible aircraft but also climbing, losing loved ones and grit and resilience. After a childhood in Alaska, Shannon studied English literature and art history at Duke University then commissioned into the Army to fly Apache helicopters, serving on three continents and leading two flight platoons and a line company. In the midst of school and flying came skydiving, scuba diving, big-mountain climbing and long-course triathlons. She climbed Tim's dream mountain- Denali. Now she devotes her work to speaking, research and writing, as well as online and bespoke facilitated leadership journeys for leaders at The Grit Institute.   Shannon has an MBA from the Tuck School at Dartmouth, and an MFA in creative writing.     05:00       Shannon's background…. And swimming in Alaska! 07:20       What is ROTC in the US… and how does that allow you to fly Army helicopters? 09:00       Learning to fly helicopters…. Rub your tummy and pat your head! 11:10       What are the roles and responsibilities in an Apache gunship…. Tandem seated! 12:10       How do two pilots in the same aircraft collaborate and cooperative? 14:50       Ben talks about receiving air support in Afghanistan 17:20       Shannon's advice for women wanting to fly in the military 20:00       Shannon climbs Denali….. the story J 25:00       Tragically Shannon loses both of her parents …. the story L 28:00       Interlude- Information on The Resilience Retreat off Cairns 29:15       What is resilience to Shannon? 33:15       Ego and self efficacy…. And grit and resilience 37:50       Talking transferrable knowledge from the military into corporates 40:30       Advice on determining purpose in work- Paths to Purpose at Tuck School 43:20       How can we separate role and identity? 50:45       Shannon's Power Song!       External Links   The Grit Factor book by Shannon is here Shannon's LinkedIn More about Shannon from her Instagram   More About Us   www.unforgiving60.com   Email us at debrief@unforgiving60.com   Instagram, Twitter, Facebook & Linked In: @Unforgiving60     Music The Externals – available on Spotify Ben Frichot - available on Spotify    

Correct Weight
Desleigh Forster - Apache Chase

Correct Weight

Play Episode Listen Later May 28, 2022 6:37


Desleigh Forster joined Warren Huntly to reflect on the win of Apache Chase in the Group 1 Kingsford Smith Cup.

Blue Island Radio Podcast
BIRP 150 - Pasha Gerard / Seize The Night

Blue Island Radio Podcast

Play Episode Listen Later May 27, 2022 67:39


On today's episode Brandon is joined in the studio by AP Lindsay, and together they talk to Brandon's longtime friend Pasha "Ashe" Gerard, a filmmaker whose first movie Seize the Night has recently entered the world and is now streaming on Amazon Prime, Tubi and other fine streaming services.  Together they talk about Pasha's coming to America from the Philippines, basketball, movie night, and Seize the Night.    Mini-Intro song by Niko Riley Main Theme song: Apache by Jorgan Ingmann Instagram: @birp60406 Facebook: @blueislandradio Twitter: @birp60406 If you'd like to support the show visit Patreon.com/blueislandradio

Leveraging Thought Leadership with Peter Winick
Being Strategic with Your Book and Business Model | Jan Rutherford & Shannon Huffman Polson | 396

Leveraging Thought Leadership with Peter Winick

Play Episode Listen Later May 26, 2022 30:59


This was originally a LinkedIn Live recorded on October 6th, 2021 In our first Leveraging Thought Leadership Live session, we invited two amazing guests to speak with us about challenges and the grit it takes to overcome them.    Jan Rutherford is a former Green Beret, and the founder of Self-Reliant Leadership. He's also the author of The Littlest Green Beret: On Self-Reliant Leadership.   Shanon Huffman-Polson is one of the first female Apache helicopter pilots, and also the founder of The Grit Institute and author of The Grit Factor: Courage, Resilience, and Leadership in the Most Male Dominated Organization in the World. Together, these two brilliant leaders, vets, and authors, discuss with us the importance of laying down a strategic plan early in your thought leadership journey. We discuss how they found ways to convey their leadership experience in methods that help others learn from it, and developing avatars to help reach the audience who needs you the most. The conversation covers the need to iterate in order to stay on top of your game, and how to listen to the market in order to keep your business growing with today's needs. Jan and Shannon share why they chose to become authors, and their reasons for wanting to write a book about their personal experience. Both created books that focused on making their personal stories a delivery mechanism for inspiration, insight, and ideas that others can use to improve their lives. If you missed this episode when it was live, this is the perfect opportunity to get caught up.   Three Key Takeaways: * Understand your thought leadership's deeper purpose, identify the people you want it to serve, and reach out to them early in your career. * The market will tell you what it values — which might be different than what you want! Be open and willing to listen, and change course toward success. * It can be easy to create thought leadership based on our experiences, but it shouldn't be about you. Make sure you are giving your audience something they can use.

Orden de traslado
Prohibido prohibir (Caetano Veloso, por Apache O'Raspi)

Orden de traslado

Play Episode Listen Later May 25, 2022 5:13


Traducción: Apache O´Raspi / Alejandro Albarrán Guitarra, armónica y voz: Apache O´Raspi Arreglos: Apache O´Raspi y Alejandro Albarrán Poema “El día del fin del mundo” de Jorge Tellier leído por: Alejandro Albarrán. Mezcla y máster: Apache O´Raspi

Open||Source||Data
Apache Pinot and Real-Time Analytics with Neha Pawar

Open||Source||Data

Play Episode Listen Later May 25, 2022 40:57


This episode features an interview with Neha Pawar, a Founding Engineer at StarTree. StarTree is a software development company that focuses on democratizing data for all users by providing real-time, user-facing analytics.Prior to her time at StarTree, Neha was a Senior Software Engineer on LinkedIn's Data Analytics team where she spent five years working on Apache Pinot. Neha has provided countless contributions to Pinot over the years, focusing on real-time streaming integrations, ingestion, and storage. In this episode, Sam sits down with Neha to discuss Apache Pinot's impact on the data community and how LinkedIn popularized real-time analytics.-------------------"Many people do think that a batch is good enough, real-time infra is expensive anyway. And what difference is it going to make if the data shown in this application is a day ago or an hour ago, and it's not real-time to the nearest second? And while that is true, in some cases, but in many other cases, not having real-time data can be super expensive and can affect the business badly and also make them irrelevant. You need the real-time data and then you also need to be able to analyze that data at the speed of your thought. For example, if you are having fraudulent activity somewhere, you can't wait for, ‘Hey, my model is going to learn about this.' And then the next time, be able to tell me that that was a fraudulent activity. You need to be able to analyze all that data right now. So, it's not just a nice-to-have, it's a must-have.” – Neha Pawar-------------------Episode Timestamps:(01:58): What open source data means to Neha(06:04): Neha's learnings from the LinkedIn Data Analytics Team(07:07): What peaked Neha's interest in real-time data analytics(08:30): Neha's first experiences working on Apache Pinot(11:40): How the work of real-time data spread from LinkedIn to other companies(17:30): How the Apache community has grown(24:04): Neha's focus at StarTree(30:41): Neha's motivation for tiered storage at StarTree (37:07): Neha's advice for open source data folks-------------------Links:LinkedIn - Connect with NehaLinkedIn - Connect with StarTreeTwitter - Follow NehaTwitter - Follow StarTreeVisit StarTree

História pros brother
Eu vou fazer você odiar o México

História pros brother

Play Episode Listen Later May 23, 2022 33:31


Boa parte do território que hoje é dos EUA antes pertencia ao México. Por isso povos nativos que muitas pessoas acham que só tiveram conflito com os estadunidenses também tiveram suas tretas com os mexicanos. Um exemplo disso são os Apaches e o governo Mexicano em 1835. Nesse ano, o governador do Estado de Songara emitiu um decreto oferecendo uma recompensa para pessoas que chegassem na sede do governo com o escalpo (couro cabeludo) de um Apache. Com o tempo o governo chegou a pagar aproximadamente 100 pesos para cada escalpo de um Apache maior de 14 anos de idade. Essa prática se tornou famosa e outros Estados começaram a oferecer o mesmo tipo de recompensa para quem chegasse com um escalpo indígena. O Estado de Chihuahua também ofereceu recompensa, 100 pesos por guerreiro, 50 pesos por mulher, e 25 pesos por criança. Era genocídio. Esse tipo de prática fez com que existisse uma espécie de “turismo da matança” para o México. Eslavos, anglo-saxões e até escravizados fugitivos dos EUA iam para o México tentar fazer dinheiro. Um presidente importante do México foi Porfírio Diaz, que governou o país entre 1884 e 1911. Durante esse governo ele reprimiu um povo em específico, os Yaqui. O massacre e a escravidão contra a tribo Yaqui reduziram a população de 30.000 para 7.000, com cerca de 20.000 Yaqui sendo mortos apenas na cidade de Sonora. Além disso, outro problema do país era que existiam latifundiários, a maioria estrangeiros, que dominavam quase toda a terra do país e a sua população ficava com bem pouco, ou quase nada. Só que como Porfírio Diaz estava no poder há tanto tempo, quase como que um ditador, depois de determinado tempo algumas lideranças populares se levantaram para questionar a forma que a política estava sendo administrada no país. Surgiram duas lideranças importantes nesse processo: Emiliano Zapata e Pancho Villa. Zapata acabou sendo o principal nome e foi decisivo no início da Revolução Mexicana, em 1910. A principal proposta de Zapata para o país era uma grande REFORMA AGRÁRIA, para que a população também pudesse ter acesso a terras e produzir. Só que terra é dinheiro e os caras do poder vão perseguir Zapata e Pancho Villa a todo custo. Eles lideravam grupos diferentes, mas que tinham o mesmo objetivo. Em 1914 os revolucionários já tinham conseguido derrubar o ditador Porfírio Díaz, e para você ver como Zapata estava interessado apenas na reforma agrária, ele recusou um cargo no novo governo que estava começando. Muita gente no lugar dele ia aproveitar essa oportunidade para ficar no poder e usufruir de privilégios. Por uma série de motivos a sucessão de poderes no México foi bastante complicada. Os políticos não estavam cumprindo sua parte no acordo que era fazer uma reforma agrária e os revolucionários Zapata e Villa continuaram a pressionar por mudanças. A parte revoltante é que mesmo tirando o ditador e mudando a governança, Emiliano Zapata e Pancho Villa continuaram a ser perseguidos. Zapatta foi morto violentamente em uma emboscada em 1919 e Pancho Villa morreu em 1923 também assassinado. A morte desses dois líderes revolucionários colocou um fim à Revolução Mexicana e fez com que as expectativas de mudança fossem perdidas. Até hoje existem grupos no México que tentam algum tipo de reforma agrária para que tenham mais chances de mudar de vida, mas nada. No México a burguesia tomou o poder e eliminou suas principais dores de cabeça: Zapata e Villa.

Go West, Young Podcast
First & Wildest: The Gila Wilderness at 100

Go West, Young Podcast

Play Episode Listen Later May 18, 2022 57:50


The Gila Wilderness was the first wilderness area designated in the country, and it's coming up on its 100 year anniversary in 2024. Hear from USFWS biologist Leanna Torres and Apache backcountry guide Joe Saenz about what makes the Gila special, as well as the threats it's facing today, from military flyovers to attempts to dam the Gila River. The post First & Wildest: The Gila Wilderness at 100 appeared first on Center for Western Priorities.

Break Things On Purpose
Dan Isla: Astronomical Reliability

Break Things On Purpose

Play Episode Listen Later May 17, 2022 34:59


It's time to shoot for the stars with Dan Isla, VP of Product at itopia, to talk about everything from astronomical importance of reliability to time zones on Mars. Dan's trajectory has been a propulsion of jobs bordering on the science fiction, with a history at NASA, modernizing cloud computing for them, and loads more. Dan discusses the finite room for risk and failure in space travel with an anecdote from his work on Curiosity. Dan talks about his major take aways from working at Google, his “baby” Selkies, his work at itopia, and the crazy math involved with accounting for time on Mars!In this episode, we cover: Introduction (00:00) Dan's work at JPL (01:58) Razor thin margins for risk (05:40) Transition to Google (09:08)  Selkies and itopia (13:20) Building a reliability community (16:20) What itopia is doing (20:20) Learning, building a “toolbox,” and teams (22:30) Clockdrift (27:36) Links Referenced: itopia: https://itopia.com/ Selkies: https://github.com/danisla/selkies selkies.io: https://selkies.io Twitter: https://twitter.com/danisla LinkedIn: https://www.linkedin.com/in/danisla/ TranscriptDan: I mean, at JPL we had an issue adding a leap second to our system planning software, and that was a fully coordinated, many months of planning, for one second. [laugh]. Because when you're traveling at 15,000 miles per hour, one second off in your guidance algorithms means you missed the planet, right? [laugh]. So, we were very careful. Yeah, our navigation parameters had, like, 15 decimal places, it was crazy.Julie: Welcome to Break Things on Purpose, a podcast about reliability, building things with purpose, and embracing learning. In this episode, we talked to Dan Isla, VP of Product at itopia about the importance of reliability, astronomical units, and time zones on Mars.Jason: Welcome to the show, Dan.Dan: Thanks for having me, Jason and Julie.Jason: Awesome. Also, yeah, Julie is here. [laugh].Julie: Yeah. Hi, Dan.Jason: Julie's having internet latency issues. I swear we are not running a Gremlin latency attack on her. Although she might be running one on herself. Have you checked in in the Gremlin control panel?Julie: You know, let me go ahead and do that while you two talk. [laugh]. But no, hi and I hope it's not too problematic here. But I'm really excited to have Dan with us here today because Dan is a Boise native, which is where I'm from as well. So Dan, thanks for being here and chatting with us today about all the things.Dan: You're very welcome. It's great to be here to chat on the podcast.Jason: So, Dan has mentioned working at a few places and I think they're all fascinating and interesting. But probably the most fascinating—being a science and technology nerd—Dan, you worked at JPL.Dan: I did. I was at the NASA Jet Propulsion Lab in Pasadena, California, right, after graduating from Boise State, from 2009 to around 2017. So, it was a quite the adventure, got work on some, literally, out-of-this-world projects. And it was like drinking from a firehose, being kind of fresh out to some degree. I was an intern before that so I had some experience, but working on a Mars rover mission was kind of my primary task. And the Mars rover Curiosity was what I worked on as a systems engineer and flight software test engineer, doing launch operations, and surface operations, pretty much the whole, like, lifecycle of the spacecraft I got to experience. And had some long days and some problems we had to solve, and it was a lot of fun. I learned a lot at JPL, a lot about how government, like, agencies are run, a lot about how spacecraft are built, and then towards the end a lot about how you can modernize systems with cloud computing. That led to my exit [laugh] from there.Jason: I'm curious if you could dive into that, the modernization, right? Because I think that's fascinating. When I went to college, I initially thought I was going to be an aerospace engineer. And so, because of that, they were like, “By the way, you should learn Fortran because everything's written in Fortran and nothing gets updated.” Which I was a little bit dubious about, so correct folks that are potentially looking into jobs in engineering with NASA. Is it all Fortran, or… what [laugh] what do things look like?Dan: That's an interesting observation. Believe it or not, Fortran is still used. Fortran 77 and Fortran—what is it, 95. But it's mostly in the science community. So, a lot of data processing algorithms and things for actually computing science, written by PhDs and postdocs is still in use today, mostly because those were algorithms that, like, people built their entire dissertation around, and to change them added so much risk to the integrity of the science, even just changing the language where you go to language with different levels of precision or computing repeatability, introduced risk to the integrity of the science. So, we just, like, reused the [laugh] same algorithms for decades. It was pretty amazing yeah.Jason: So, you mentioned modernizing; then how do you modernize with systems like that? You just take that codebase, stuff it in a VM or a container and pretend it's okay?Dan: Yeah, so a lot of it is done very carefully. It goes kind of beyond the language down to even some of the hardware that you run on, you know? Hardware computing has different endianness, which means the order of bits in your data structures, as well as different levels of precision, whether it's a RISC system or an AMD64 system. And so, just putting the software in a container and making it run wasn't enough. You had to actually compute it, compare it against the study that was done and the papers that were written on it to make sure you got the same result. So, it was pretty—we had to be very careful when we were containerizing some of these applications in the software.Julie: You know, Dan, one thing that I remember from one of the very first talks I heard of yours back in, I think, 2015 was you actually talked about how we say within DevOps, embrace failure and embrace risk, but when you're talking about space travel, that becomes something that has a completely different connotation. And I'm kind of curious, like, how do you work around that?Dan: Yeah, so failing fast is not really an option when you only have one thing [laugh] that you have built or can build. And so yeah, there's definitely a lot of adverseness to failing. And what happens is it becomes a focus on testing, stress testing—we call it robustness testing—and being able to observe failures and automate repairs. So, one of the tests programs I was involved with at JPL was, during the descent part of the rover's approach to Mars, there was a power descent phase where the rover actually had a rocket-propelled jetpack and it would descend to the surface autonomously and deliver the rover to the surface. And during that phase it's moving so fast that we couldn't actually remote control it, so it had to do everything by itself.And there were two flight computers that are online, pretty much redundant, everything hardware-wise, and so it's kind of up to the software to recover itself. And so, that's called entry descent and landing, and one of my jobs towards the end of the development phase was to ensure that we tested all of the possible breakage points. So, we would do kind of evil Gremlin-like things. We actually—the people in the testbed, we actually call Gremlins. And [laugh] we would—we—they inject faults during the simulation.So, we had copies of the hardware running on a desk, the software was running, and then we'd have Gremlins go and say like, “Hey, flight computer one just went out. You know, what's going to happen?” And you watch the software, kind of, take over and either do the right thing or simulate a crash landing. And we find bugs in the software this way, we'd find, like, hangs in the control loops for recovery, and we had to fix those before we made it to Mars, just in case that ever happened. So, that was like how we, like, really stressed test the hardware, we did the same thing with situational awareness and operations, we had to simulate things that would happen, like, during launch or during the transit from Earth to Mars, and then see how the team itself reacted to those. You know, do our playbooks work? Can we run these in enough time and recover the spacecraft? So, it was a lot of fun. That's I guess that's about as close to, like, actually breaking something I can claim to. [laugh].Julie: Well, I have to say, you've done a good job because according to Wikipedia—which we all know is a very reliable source—as of May 9th, 2022, Curiosity has been active on Mars for 3468 sols or 3563 days, and is still active. Which is really amazing because I don't—was it ever intended to actually be operational that long?Dan: Not really. [laugh]. The hardware was built to last for a very long time, but you know, as with most missions that are funded, they only have a certain amount of number of years that they can be operated, to fund the team, to fund the development and all that. And so, the prime mission was only, like, two years. And so, it just keeps getting extended. As long as the spacecraft is healthy, and, like, doing science and showing results, we usually extend the missions until they just fall apart or die, or be intentionally decommissioned, kind of like the Cassini project. But yeah.Julie: Well, you've heard it here first, folks. In order to keep funding, you just need to be, quote, “Doing science.” [laugh]. But Dan, after JPL, that's when you went over to Google, right?Dan: Yeah, yeah. So, it was kind of that transition from learning how to modernize with cloud. I'd been doing a lot with data, a lot with Amazon's government cloud, which is the only cloud we could use at JPL, and falling in love with these APIs and ways to work with data that were not possible before, and saw this as a great way to, you know, move the needle forward in terms of modernization. Cloud is a safe place to prototype a safe place to get things done quick. And I always wanted to work for a big tech company as well, so that was always another thing I was itching to scratch.And so Google, I interviewed there and finally made it in. It was not easy. I definitely failed my first interview. [laugh]. But then try it again a few years later, and I came in as a cloud solution architect to help customers adopt cloud more quickly, get through roadblocks.My manager used to say the solution architects were the Navy Seals of cloud, they would drop in, drop a bunch of knowledge bombs, and then, like, get out, [laugh] and go to the next customer. It was a lot of fun. I got to build some cool technology and I learned a lot about what it's like working in a big public company.Julie: Well, one of my favorite resources is the Google SRE book, which, as much as I talk about it, I'm just going to admit it here now, to everybody that I have not read the entire thing.Dan: It's okay.Julie: Okay, thank you.Dan: Most people probably haven't.Julie: I also haven't read all of Lord of the Rings either. But that said, you know, when you talk about the learnings, how much of that did you find that you practiced day-to-day at Google?Dan: In cloud—I've mostly worked in cloud sales, so we were kind of post-sales, the experts from the technology side, kind of a bridge to engineering and sales. So, I didn't get to, like, interact with the SREs directly, but we have been definitely encouraged, I had to learn the principles so that we could share them with our customers. And so, like, everyone wanted to do things like Google did, you know? Oh, these SREs are there, and they're to the rescue, and they have amazing skills. And they did, and they were very special at Google to operate Google's what I would call alien technology.And so, you know, from a principles point of view, it was actually kind of reminded me a lot of what I learned at JPL, you know, from redundant systems and automating everything, having the correct level of monitoring. The tools that I encountered at Google, were incredible. The level of detail you could get very quickly, everything was kind of at your fingertips. So, I saw the SREs being very productive. When there was an outage, things were communicated really well and everyone just kind of knew what they were doing.And that was really inspiring, for one, just to see, like, how everything came together. That's kind of what the best part of working at Google was kind of seeing how the sausage was made, you know? I was like, “Oh, this is kind of interesting.” [laugh]. And still had some of its big company problems; it wasn't all roses. But yeah, it was definitely a very interesting adventure.Jason: So, you went from Google, and did you go directly to the company that you helped start, right now?Dan: I did. I did. I made the jump directly. So, while I was at Google, you know, not only seeing how SRE worked, but seeing how software was built in general and by our customers, and by Google, really inspired me to build a new solution around remote productivity. And I've always been a big fan of containers since the birth of Docker and Kubernetes.And I built the solution that let you run, kind of, per-user workloads on Kubernetes and containers. And this proved to be interesting because you could, you know, stand up your own little data processing system and scale it out to your team, as well as, like, build remote code editors, or remote desktop experiences from containers. And I was very excited about this solution. The customers were really starting to adopt it. And as a solution architect, once the stuff we built, we always open-source it.So, I put it on GitHub as a project called Selkies. And so, Selkies is the Kubernetes components and there's also the high performance streaming to a web browser with WebRTC on GitHub. And a small company, itopia, I met at a Google conference, they saw my talk and they loved the technology. They were looking for something like that, to help some of their product line, and they brought me in as VP of Product.So, they said, “We wanted to productize this.” And I'm like, “Well, you're not doing that without me.” [laugh]. Right? So, through the pandemic and work from home and everything, I was like, you know, now is probably a good time to go try something new.This is going to be—and I get to keep working on my baby, which is Selkies. So yeah, I've been itopia since beginning of 2021, building a remote desktop, really just remote developer environments and other remote productivity tools for itopia.Julie: Well and, Dan, that's pretty exciting because you actually talked a little bit about that at DevOpsDays Boise, which if that video is posted by the time of publication of this podcast, we'll put a link to that in the show notes. But you're also giving a talk about this at SCaLE 19x in July, right?Dan: Yeah, that's right. Yeah, so SCaLE is the Southern California Linux Expo, and it's a conference I really enjoy going to get to see people from Southern California and other out of town, a lot of JPLers usually go as well and present. And so, it's a good time to reconnect with folks. But yeah, so SCaLE, you know, they usually want to talk more about Linux and some of the technologies and open-source. And so yeah, really looking forward to sharing more about selfies and kind of how it came to be, how containers can be used for more than just web servers and microservices, but also, you know, maybe, like, streaming video games that have your container with the GPU attached. The DevOpsDays Boise had a little demo of that, so hopefully, that video gets attached. But yeah, I'm looking forward to that talk at the end of July.Jason: Now, I'm really disappointed that I missed your talk at DevOpsDays Boise. So Julie, since that's your domain, please get those videos online quickly.Julie: I am working on it. But Dan, one of the things that you know you talk about is that you are the primary maintainer on this and that you're looking to grow and improve with input from the community. So, tell us, how can the community get involved with this?Dan: Yeah, so Selkies is on GitHub. You can also get to it from selkies.io. And basically, we're looking for people to try it out, run it, to find problems, you know, battle test it. [laugh]. We've been running it in production at itopia, it's powering the products they're building now.So, we are the primary maintainers. I only have a few others, but, you know, we're just trying to build more of an open-source community and level up the, you know, the number of contributors and folks that are using it and making it better. I think it's an interesting technology that has a lot of potential.Jason: I think as we talk about reliability, one of the things that we haven't covered, and maybe it's time for us to actually dive into that with you is reliability around open-source. And particularly, I think one of the problems that always happens with open-source projects like this is, you're the sole maintainer, right? And how do you actually build a reliable community and start to grow this out? Like, what happens if Dan suddenly just decides to rage quit tech and ups and leaves and lives on his own little private island somewhere? What happens to Selkies?Do you have any advice for people who've really done this, right? They have a pet project, they put it on GitHub, it starts to gain some traction, but ultimately, it's still sort of their project. Do you have any advice for how people can take that project and actually build a reliable, growing, thriving community around it?Dan: Honestly, I'm still trying to figure that out [laugh] myself. It's not easy. Having the right people on your team helps a lot. Like, having a developer advocate, developer relations to showcase what it's capable of in order to create interest around the project, I think is a big component of that. The license that you choose is also pretty important to that.You know, there's some software licenses that kind of force the open-sourcing of any derivative of what you build, and so that can kind of keep it open, as well, as you know, move it forward a little bit. So, I think that's a component. And then, you know, just, especially with conferences being not a thing in the last couple of years, it's been really hard to get the word out and generate buzz about some of these newer open-source technologies. One of the things I kind of like really hope comes out of a two-year heads-down time for developers is that we're going to see some, like, crazy, amazing tech on the other side. So, I'm really looking forward to the conferences later this year as they're opening up more to see what people have been building. Yeah, very interested in that.Jason: I think the conversation around open-source licenses is one that's particularly interesting, just because there's a lot involved there. And there's been some controversy over the past couple of years as very popular open-source projects have decided to change licenses, thinking of things like Elastic and MongoDB and some other things.Dan: Yeah. Totally.Jason: You chose, for Selkies, it looks like it's Apache v2.Dan: Yep. That was mostly from a Google legal point of view. When I was open-sourcing it, everything had to be—you know, had to have the right license, and Apache was the one that we published things under. You know, open-source projects change their license frequently. You saw that, like what you said, with Elastic and Mongo.And that's a delicate thing, you know, because you got to make sure you preserve the community. You can definitely alienate a lot of your community if you do it wrong. So, you got to be careful, but you also, you know, as companies build this tech and they're proud of it and they want to turn it into a product, you want to—it's a very delicate process, trying to productize open-source. It can be really helpful because it can give confidence to your customers, meaning that, like, “Hey, you're building this thing; if it goes away, it's okay. There's this open-source piece of it.”So, is instills a little bit of confidence there, but it also gets a little tricky, you know? Like, what features are we adding the add value that people will still pay for versus what they can get for free? Because free is great, but you know, it's a community, and I think there are things that private companies can add. My philosophy is basically around packaging, right? If you can package up an open-source product to make it more easier to consume, easier to deploy, easier to observe and manage, then you know, that's a lot of value that the rest of the free community may not necessarily need.If they're just kind of kicking the tires, or if they have very experienced Kubernetes team on-site, they can run this thing by themselves, go for it, you know? But for those, the majority that may not have that, you know, companies can come in and repackage things to make it easier to run open-source. I think there's a lot of value there.Jason: So, speaking of companies repackaging things, you mentioned that itopia had really sort of acquired you in order to really build on top of Selkies. What are the folks at itopia doing and how are they leveraging the software?Dan: That's a good question. So, itopia's mission is to radically improve work-from-anywhere. And we do that by building software to orchestrate and automate access to remote computing. And that orchestration and automation is a key component to this, like, SaaS-like model for cloud computing.And so, Selkies is a core piece of that technology. It's designed for orchestrating per-user workloads, like, remote environments that you would need to stand up. And so, you know, we're adding on things that make it more consumable for an enterprise, things like VPN peering and single-sign-on, a lot of these things that enterprises need from day one in order to check all the boxes with their security teams. And at the heart of that is really just increasing the amount of the productivity you have through onboarding.Basically, you know, setting up a developer environment can take days or weeks to get all the dependencies set up. And the point of itopia—Spaces is the product I'm working on—is to reduce that amount of time as much as possible. And, you know, this can increase risk. If you have a product that needs to get shipped and you're trying to grow or scale your company and team and they can't do that, you can slip deadlines and introduce problems, and having a environment that's not consistent, introduces reliability problems, right, because now you have developers that, “Hey, works on my machine.” But you know, they may have—they don't have the same machine, same environment as everyone else, and now when it comes to reproducing bugs or even fixing them, that you can introduce more problems to the software supply chain.Julie: I mean, that sounds like a great problem to solve and I'm glad you're working on it. With your background being varied, starting as an intern to now where you personally are being acquired by organizations. What's something that you've really learned or taken from that? Because one thing that you said was that you failed your first Google interview badly? And—Dan: Yes. [laugh].Julie: I find that interesting because that sounds like you know, you've taken that learning from failure, you've embraced the fact that you failed it. Actually, I just kind of want to go back. Tell us, do you know what you did?Dan: It was definitely a failure. I don't know how spectacular it was, but, like, [laugh] google interviews are hard. I mean—and that's just how it is, and it's been—it's notorious for that. And I didn't have enough of the software, core software experience at the time to pass the interview. These are, like, five interviews for a software engineer.And I made it through, like, four of them. The last one was, like, just really, really, really hard and I could not figure it out. You know, because this is, like, back in the day—and I think they still do this, like, where you're, like, coding on a whiteboard, right? Like, okay, right, this C code on a whiteboard, and it has to work. You know, the dude is, like, right, there compiling it, right? Like, “Okay, [unintelligible 00:23:29], boy.” [laugh].So, not only is a high stress, but it has to be right as well. [laugh]. And so, like, it was just a very difficult experience. And what I learned from that was basically, “Okay, I need to, one, get more experience in this style and this domain of programming, as well, as you know, get more comfortable speaking and being in front of people I don't know.” [laugh].So yeah, there's definitely components there of personal growth as well as technical growth. From a technical point of view, like, my philosophy as being an engineer in general, and software developer, is have a really big toolbox and use the tools that are appropriate for the job. This is, like, one of my core philosophies. Like, people ask, you know, ‘what language do you use?' And I'm like, “Whatever language you needed to solve the problem.”Like, if you're writing software, in a—with libraries that are all written in C, then don't try to do that in, like, Java or something, in some other language that doesn't have those language bindings. Don't reinvent the language bindings. You follow the problem and you follow the tech. What language, what tool will best solve this problem? And I'm always working backwards from the problem and then bringing in the right tools to solve it.And that's something that has paid off in dividends because it's very—problem-solving is fun and it's something I always had a passion for, but when you have a toolbox that is full of interesting gadgets and things you can use, you get excited every time you get to use that tool. Like, just like power tools here, I have a—I don't know, but it's like, “Yeah, I get to use the miter saw for this thing. Awesome. I don't have one? Okay, I'm going to go buy one.” [laugh].Julie: That's actually—that's a really good point, one of the talks that I gave was, “You Can't Buy DevOps.” And it was really all about letting developers be part of the process in choosing the tools that they're going to use. Because sometimes I think organizations put too many constraints around that and force you to use these tools that might not be the best for what you're trying to accomplish. So, I like that you bring up having the ability to be excited about your toolbox, or your miter saw. For me, it would be my dremel. Right? But what tool is going to—Dan: [crosstalk 00:25:39] cool.Julie: Yeah, I mean, they really are—what tool is going to be best for the job that you are trying to accomplish? And I think that that's, that's a big thing. So, when you look to bring people onto your team, what kind of questions do you ask them? What are you looking for?Dan: Well, we're just now starting to really grow the company and try and scale it up. And so we're, you know, we're starting to get into more and more interview stuff, I try to tell myself, I don't want to put someone through the Google experience again. And part of that is just because it wasn't pleasant, but also, like, I don't know if it was really that useful [laugh] at the end of the day. And so, you know, there's a lot about culture fit that is really important. People have to be able to communicate and feel comfortable with your team and the pace that your team is working at. And so, that's really important.But you know, technically, you know, I like to see a lot of, you know—you got to be able to show me that you can solve problems. And that can be from, you know, just work that you've done an open-source, you know, having a good resume of projects you've worked on is really important because then we can just talk about tech and story about how you solve the problem. I don't have to—I don't need you to go to the whiteboard and code me something because you have, like, 30 repos on GitHub or something, right? And so, the questions are much more around problem-solving: you know, how would you solve this problem? What technology choices would you use, and why?Sometimes I'll get the fundamentals, like, do you understand how this database works at its core or not? You know, or why is it… why is that good or bad? And so, looking for people who can really think within the toolbox they have—it doesn't have to be a big one, but do they know how to use the tools that they've acquired so far, and really, just really, really critically think through with your problems? So, to me, that's a better skill to have than just, you know, being able to write code on the whiteboard.Julie: Thanks for that, Dan. And earlier, before we started the official recording here, you were talking a little bit about time drift. Do you want to fill everybody in on what you were talking about because I don't think it was Doctor Strange and the Multiverse of Madness?Dan: No. [laugh]. I think there were some—we were talking about um…clocks?Julie: Clocks skew.Dan: Daylight savings time?Julie: Yeah.Dan: Clock skew, clock drift. There was a time at JPL when we were inserting a leap second to the time. This actually happened all throughout the world, where periodically that the clocks will drift far enough because the orbits and the rotation of the planet are not, like, perfectly aligned to 365 days in a year and 24 hours in a day. And so, every so decades, you have to insert these leap seconds in order to catch up and make time more precise. Well, space travel, when you're planning, you have to—you're planning to the position of the stars and the planets and the orbital bodies, and those measurements are done at such a large scale that you have—your precision goes, like, way out, you know, many, many decimal places in order to properly plan to the bodies up big.And with the Mars Rover, one of these leap seconds happened to come in, like, right, before we launched. And it was like, oh my gosh, this is going to be to—change all of our ephemeris files—the data that you use to track positions—and we had to do it, like, synchronize it all, like, right, when the leap second was going in. And we tested this extensively because if you get it wrong with your spacecraft is traveling, like, 15,000 miles an hour towards Mars, and a one-second pointing error from Earth means, like, you missed the whole planet, you won't even get there. [laugh]. We're not talking about, like, missing the landing site of, like, a few kilometers. No, it's like thousands of kilometers in pointing error.So yeah, things are astronomical [laugh] in units. Actually, that's why they're called AU, astronomical units, when you're measuring the distance from the Sun. So yeah, it was a pretty fun time. A little bit nerve-wracking just because the number of systems that had to be updated and changed at the same time. It's kind of like doing a rolling update on a piece of software that just had to go out all at the same time. Yeah.Jason: I think that's really interesting, particularly because, you know, for most of us, I think, as we build things whether that's locally or in the cloud or wherever our servers are at, we're so used to things like NTP, right, where things just automatically sync and I don't have to really think about it and I don't really have to worry about the accuracy because NTP stays pretty tight. Usually, generally.Dan: Mm-hm.Jason: Yeah. So, I'm imagining, obviously, like, on a spacecraft flying 15,000 miles a second or whatever, no NTP out there.Dan: [laugh]. Yeah, no NTP and no GPS. Like, all the things you take for granted, on Mars are just not there. And Mars even has a different time system altogether. Like the days on Mars are about 40 minutes longer because the planet spins slower.And my first 90 sols—or days on Mars—of the mission, the entire planning team on earth that I was a part of, we lived on Mars time. So, we had to synchronize our Earth's schedule with what the rover was doing so that when the rover was asleep, we were planning the next day's activities. And when it woke up, it was ready to go and do work during the day. [laugh]. So, we did this Mars time thing for 90 days. That was mostly inherited from the Mars Exploration rovers, Spirit and Opportunity because they were only designed to live for, like, 90 days.So, the whole team shifted. And we—and now it's kind of done in spirit of that mission. [laugh]. Our rover, we knew it was going to last a bit longer, but just in case, let's shift everyone to Mars time and see what happened. And it was not good. We had to [laugh] we had to end that after 90 days. People—your brain just gets completely fried after that. But it was bizarre.And there's no time. You have invent your own time system for Mars. Like, there's no, it was called LMST, or Local Mars Standard Time, local mean standard time. But it was all, like, relative to, you know, the equator and where you were on the planet. And so, Mars had his own Mars time that counted at a different rate per second.And so, it was funny, we had these clocks in the Mission Control Room that—there was this giant TV screen that had, like, four different time clocks running. It had, like, Pasadena time, UTC time, Mars time, and, like, whatever time it was at the Space Network. And I was like, “Oh, my gosh.” And so, we were always doing these, like, time conversions in our heads. It was mental. [laugh]. So, can't we just all be on UTC time? [laugh].Jason: So, I'm curious, with that time shift of being on Mars time and 40 minutes longer, that inherently means that by the end of that 90 days, like, suddenly, your 8 a.m. Mars local time is, like, shifted, and is now, like, hours off, right? You're waking—Dan: Yeah.Jason: Up in the middle of the night?Dan: Totally, yeah.Jason: Wow.Dan: Yeah, within, like, two weeks, your schedule will be, like, upside down. It's like, every day, you're coming in 40 minutes later. And yeah, it was… it was brutal. [laugh]. Humans are not supposed to do that.If you're actually living on Mars, you're probably okay, but like, [laugh] trying to synchronize those schedules. I thought you were going from East Coast to West Coast time, working remote was hard. And, like, [laugh] that's really remote.Julie: Dan, that's just astronomical.Dan: [laugh].Julie: I'm so sorry. I had to do it. But with that—[laugh].Jason: [laugh].Dan: [laugh]. [unintelligible 00:33:15].Julie: With that, Dan, I really just want to thank you for your time on Break Things on Purpose with us today. And as promised, if I can find the links to Dan's talks, if they're available before this episode posts, we will put those in the show notes. Otherwise, we'll put the link to the YouTube channel in the show notes to check for updates. And with that, I just want to thank you, Dan, and wish you a wonderful day.Jason: Before we go, Dan, do you have anything that you'd like to plug? Any projects that people should check out, where they can find you on the internet, stuff like that?Dan: Yeah, thank you guys very much for having me. It was a great conversation. Really enjoyed it. Please check out our new product, itopia Spaces, remote developer environments delivered, powered by Selkies. We launched it last fall and we're really trying to ramp that up.And then check out the open-source Selkies project, selkies.io will get you there. And yeah, we're looking for contributors. Beyond that, you can also find me on Twitter, I'm @danisla, or on LinkedIn.Jason: Awesome. Well, thanks again for being a part of the show. It's been fantastic.Dan: You're very welcome. Thanks for having me.Jason: For links to all the information mentioned, visit our website at gremlin.com/podcast. If you liked this episode, subscribe to the Break Things on Purpose podcast on Spotify, Apple Podcasts, or your favorite podcast platform. Our theme song is called, “Battle of Pogs” by Komiku, and it's available on loyaltyfreakmusic.com.

Screaming in the Cloud
Reliability Starts in Cultural Change with Amy Tobey

Screaming in the Cloud

Play Episode Listen Later May 11, 2022 46:37


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.

House of X - An X-Men Podcast
Episode 138 - I am Mutant

House of X - An X-Men Podcast

Play Episode Listen Later May 11, 2022 94:06


We review Giant Size X-Men Thunderbird, Marauders and AXE Judgement Day from Free Comic Book Day

Sta Cagado con Sam Butler
Da Sh*t 96: Was Chief Geronimo, Catholic?

Sta Cagado con Sam Butler

Play Episode Listen Later May 10, 2022 15:23


Geronimo was an Apache leader who belonged to the Bedonkohe band of the Chiricahua Apache tribe. He was not considered a chief among the Apache people, but was known as an infamous leader with a warrior spirit that conducted raids and warfare. Was he also catholic? Follow Us: https://www.instagram.com/stacagadopodcast/ https://www.facebook.com/stacagadopodcast/

New Books in Native American Studies
Paul Conrad, "The Apache Diaspora: Four Centuries of Displacement and Survival" (U Pennsylvania Press, 2021)

New Books in Native American Studies

Play Episode Listen Later May 10, 2022 63:36


In The Apache Diaspora: Four Centuries of Displacement and Survival (U Pennsylvania Press, 2021), Paul Conrad brings to life the stories of displaced Apaches and the kin from whom they were separated. Conrad uses the lens of “diaspora” to analyze four centuries of Ndé/Apache history, from their initial interactions with Europeans in the sixteenth century to the early twentieth century, when several dozen Apaches returned to the Southwest –if not to their ancestral lands, after decades of forced exile. The case for an Apache diaspora is persuasively demonstrated throughout with illustrative examples drawn from a wide array of secondary and primary sources, including original documents from repositories in the U.S., Mexico, and Spain. Conrad charts Apaches' efforts to survive or return home from places as far-flung as Cuba and Pennsylvania, Mexico City and Montreal. While deeply analytical, Conrad enlivens his narrative with meaningful stories, such as the arrival of the first shipment of Apaches to Havana in 1784, and evocative vignettes, for instance, of life on the reservations in the 1870s. Joaquín Rivaya-Martínez es profesor de Historia en Texas State University. Sus intereses académicos incluyen la etnohistoria, los pueblos indígenas de las Grandes Llanuras y el Suroeste de EE.UU., la frontera México-EE.UU. y la América hispánica. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/native-american-studies