Podcasts about Software

ALSO! Is Amazon responsible for tragedies being live-streamed on Twitch? And is McDonald's self-removal from Russia admirable or suspicious?

Thank you so much for listening to today's episode all about Forte! Below you'll find all of the information you need to qualify for a free tech upgrade this month. What is the Forte Tech Challenge? Teachers who teach at least 3 - 30 minute lessons using the https://carlyjowalton.lt.acemlna.com/Prod/link-tracker?redirectUrl=aHR0cHMlM0ElMkYlMkZmb3J0ZWxlc3NvbnMuY29tJTJG&sig=ES9yP8tQcz6PR4mBmk5dLwQSfr6Y8rVWipeoUxAjpBH8&iat=1651597065&a=%7C%7C1001108908%7C%7C&account=carlyjowalton%2Eactivehosted%2Ecom&email=bpW7%2BGJJKaHenOFQs1fpHOdMbvrMGnE6fkRIdvDq3LM%3D&s=577ff676bc4fb45ec5d15bbdd9a2e6bc&i=392A498A3A2440 (Forte calling software) will qualify for a free tech upgrade. After June 1st you can submit a form and Forte will send you one piece of new equipment. This is NOT a giveaway. Every single teacher who teaches on Forte following the requirements will qualify for and be sent one of the following (depending on your needs). 1. https://carlyjowalton.lt.acemlna.com/Prod/link-tracker?redirectUrl=aHR0cHMlM0ElMkYlMkZ3d3cuYmx1ZW1pYy5jb20lMkZlbi11cyUyRnByb2R1Y3RzJTJGeWV0aSUyRg==&sig=3TWSmEzxWBg8ZcLjJuvexa37AGJeHMtMCSby4EU8vy89&iat=1651597065&a=%7C%7C1001108908%7C%7C&account=carlyjowalton%2Eactivehosted%2Ecom&email=bpW7%2BGJJKaHenOFQs1fpHOdMbvrMGnE6fkRIdvDq3LM%3D&s=577ff676bc4fb45ec5d15bbdd9a2e6bc&i=392A498A3A2441 (Blue Yeti USB Microphone) 2. https://carlyjowalton.lt.acemlna.com/Prod/link-tracker?redirectUrl=aHR0cHMlM0ElMkYlMkZ3d3cuYW1hem9uLmNvbSUyRkxvZ2l0ZWNoLUNhbGxpbmctTm9pc2UtQ2FuY2VsaW5nLUNvcnJlY3Rpb24tTWljcm9zb2Z0JTJGZHAlMkZCMDFONVVPWUM0&sig=GF9xpm1VPKMLQZ8oGQu2bXrKD68PF4bQncc9nrGbVJhh&iat=1651597065&a=%7C%7C1001108908%7C%7C&account=carlyjowalton%2Eactivehosted%2Ecom&email=bpW7%2BGJJKaHenOFQs1fpHOdMbvrMGnE6fkRIdvDq3LM%3D&s=577ff676bc4fb45ec5d15bbdd9a2e6bc&i=392A498A3A2442 (Logitech Brio Webcam) 3. https://carlyjowalton.lt.acemlna.com/Prod/link-tracker?redirectUrl=aHR0cHMlM0ElMkYlMkZ3d3cuYW1hem9uLmNvbSUyRlNlbm5oZWlzZXItUHJvZmVzc2lvbmFsLU92ZXItRWFyLU1vbml0b3JpbmctSGVhZHBob25lcyUyRmRwJTJGQjAwSVQwSUhPWSUyRnJlZiUzRHNyXzFfMyUzRmNyaWQlM0QzMFAzTDBFQzE3WlZHJTI2a2V5d29yZHMlM0RzZW5uaGVpc2VyJTI1MkJvdmVyLWVhciUyNTJCaGVhZHBob25lcyUyNnFpZCUzRDE2NTE0NTQwMjMlMjZzJTNEZWxlY3Ryb25pY3MlMjZzcHJlZml4JTNEc2VubmhlaXNlciUyNTJCb3Zlci1lYXIlMjUyQmhlYWRwaG9uZXMlMjUyQ2VsZWN0cm9uaWNzJTI1MkM3MyUyNnNyJTNEMS0zJTI2dGglM0Qx&sig=C6GDdih1ZzYsN87s7C8C7bwPV1bdAHbntXXUF8581G8V&iat=1651597065&a=%7C%7C1001108908%7C%7C&account=carlyjowalton%2Eactivehosted%2Ecom&email=bpW7%2BGJJKaHenOFQs1fpHOdMbvrMGnE6fkRIdvDq3LM%3D&s=577ff676bc4fb45ec5d15bbdd9a2e6bc&i=392A498A3A2443 (Sennheiser Professional Over-Ear Headphones) How to qualify To qualify for the promotion, visithttps://carlyjowalton.lt.acemlna.com/Prod/link-tracker?redirectUrl=aHR0cHMlM0ElMkYlMkZzdHJlYWtsaW5rcy5jb20lMkZCQl9OVnVxMnRsSTlzMnVLWHd2VG8xd2YlMkZodHRwJTI1M0ElMjUyRiUyNTJGd3d3LmZvcnRlbGVzc29ucy5jb20lMjUyRnByb21v&sig=DemvvexznFYPgV1bqkVprwXzdHA4TgzxaZT8ABJMKnhV&iat=1651597065&a=%7C%7C1001108908%7C%7C&account=carlyjowalton%2Eactivehosted%2Ecom&email=bpW7%2BGJJKaHenOFQs1fpHOdMbvrMGnE6fkRIdvDq3LM%3D&s=577ff676bc4fb45ec5d15bbdd9a2e6bc&i=392A498A3A2444 ( www.fortelessons.com/promo) and use the promo code CARLY. After June 1, Forte will reach out to those teachers who qualified for the free equipment. Getting started To get started head over tohttps://carlyjowalton.lt.acemlna.com/Prod/link-tracker?redirectUrl=aHR0cHMlM0ElMkYlMkZmb3J0ZWxlc3NvbnMuY29tJTJG&sig=ES9yP8tQcz6PR4mBmk5dLwQSfr6Y8rVWipeoUxAjpBH8&iat=1651597065&a=%7C%7C1001108908%7C%7C&account=carlyjowalton%2Eactivehosted%2Ecom&email=bpW7%2BGJJKaHenOFQs1fpHOdMbvrMGnE6fkRIdvDq3LM%3D&s=577ff676bc4fb45ec5d15bbdd9a2e6bc&i=392A498A3A2440 ( Forte )and create your free account. Try out Forte with students during the Month of May for least 3 lessons to...

What's the single best thing happening in technology right now? According to entrepreneur and venture capitalist Marc Andreessen, it's the ability to live in rural Wisconsin but still earn a Silicon Valley salary. Andreessen also explains to EconTalk host Russ Roberts why software is still eating the world, why he's an optimist, and why he's still bullish on Bitcoin and the blockchain.

Diese Episode startet mit einem kleinen Follow-Up zu einem Kommentar zur letzten Episode, die sich unter anderem um den Passwortmanager 1Password drehte. Danach geht es weiter um die Google I/O 2022 und die letzten Apple News. Tom erzählt dann vom troii Retreat in Kroatien und seinen Erfahrungen und Versuchen mit der Meta Quest 2. In der Dev Section geht es dieses Mal um "circular Dependencies" zwischen Spring Beans mit Spring Boot und im Konsumabschnitt werden tolle Werkzeuge und Software von André und Tom besprochen.

In our previous episode, we talked to Dr. Seth Benzell about How the Pandemic Changed Global Labor Markets and in this episode, we talk about the work he's done to find a solution to the age-old issue of rising automation. The automation scare is not new.  Since the luddites in the 19th century, we've heard the laborers complain about automation. In fact, it is the new standard in todays world. We all hear about the benefits of automation but we are still trying to understand and remediate the negative externalities.If you've listened to Things Have Changed before, you know Dr. Seth Benzell spends his time studying the digital economy, the platforms that have succeeded in it, and how it's affected our economy as a whole. In this episode, he helps us understand how he's gotten to the two solutions that he mentions in his paper on "Simulating Endogenous Global Automation". Seth walks us through two of his considerations for policy that could possibly change the direction away from increased wage inequality:Mandating automation for regions that would otherwise not automateUniversal Basic Income Check out our previous episodes with Dr. Seth Benzell on the links below:How Tech Created a Winner-Take-All Economy – with Seth BenzellHow the Pandemic Has Changed Global Labor Markets with Dr. Seth BenzellHere is a link to Dr. Seth Benzells work:Dr. Seth Benzell WebsiteEfficiency of U.S. Public Space UtilizationSupport the show

Über diesen Link hast Du die Möglichkeit, Dich für eine Zusammenarbeit mit FOOTBALL LEVERAGE zu bewerben: https://footballleverage.com/mindgame Dies hier ist eine sehr spannende Folge mit einem sehr interessanten Gast: Mirco Papaleo ist Scout bei einem Super League Verein (1. Liga in der Schweiz) und Mitgründer von Footballytics, einer Software zur Scouting-Unterstützung und Spielanalyse für Vereine. In diesem Interview sprechen wir über seine Aufgabe als Scout, welche Tipps er Dir unbedingt mitgeben möchte und einige weitere spannende Themen, von denen Du sehr profitieren kannst. Hier findest du Mirco und Footballytics: twitter.com/mircopapaleo & www.footballytics.ch/ Auf meinem Instagram Account kannst Du Deine Fragen und / oder Themenvorschläge mit mir teilen: https://www.instagram.com/mindgame.fussball Über diesen Link hast Du die Möglichkeit Dich für eine Coaching Zusammenarbeit mit uns zu bewerben: https://footballleverage.com/mindgame

Ever get an urge to sit down with a game a second, third, twentieth time? Why? What makes us want to re-play a video game? What games do we typically re-play? Is there something about the games themselves that gravitate us back? https://linktr.ee/80bitpodsmash Music: Halcyonic Falcon X - Of Rainbows and Unicorns http://creativecommons.org/licenses/by-nc-sa/3.0/us/

Jerome Friedman, CPO and Co-founder of SpotOn, speaks to Ryan about the multiple start-ups he has built, what inspired him to create SpotOn and the unique solutions it offers to their customers. KEY TAKEAWAYS SpotOn has created multiple platforms and solutions that help restaurants, retail and a whole host of other small businesses at point os sale. Since the birth of SpotOn, Jerome has helped build it from nothing to a valuation of 3 billion dollars and employer of 2000 employees in just four years. SpotOn's primary go-to-market strategy is direct sales, with a 500+ sales rep team who directly build strong relationships with their customers to offer and create solutions specifically for them. SpotOn are constantly creating technology and products to help solve the pain points and difficulties that businesses face. Everything SpotOn do is to help businesses save revenue, decrease costs and give great services to their customers. Jerome's father was his main inspiration to becoming an entrepreneur, even though he warned him against the stress and difficulties you face in the entrepreneurial lifestyle. But, Jerome just knew that it's what he wanted to do and if he could be half the entrepreneur his Dad was he will have done well in life! At 21 he created a bagel business across colleges on the west coast which became successful, he then had the concept of creating on-demand credit cards and so found the tech people he needed to build it with him. At 40 after managing with some difficult financial situations in this business, Jerome decided to start again and this is when and where SpotOn was born. You must find people in business to work with that compliment your weaknesses. Find those who are different to you and that have different strengths to help you build success. Spot On has one of the biggest percentage most women-leaders in a tech company. Two of the most recent additions to spot on solution is pacing technology for restaurant orders and stock tracking on multiple platforms for small retail businesses. During the pandemic SpotOn tried to do everything they could to help their clients. They asked their teams to work as hard as they could to help them, they released and built new systems before they were ready and even gave away free solutions. They cared and therefore helped in any and every way they could.   BEST MOMENTS “We're not always right, we make mistakes all the time. We have a saying, fail fast and pivot” “If we're to have empathy with our clients, we need to have empathy with each other” “We thought in order to make something really powerful we wanted to build it from the ground up” “If you can add value and save people money at the same time it's the biggest win in the world” Do You Want The Closing Secrets That Helped Close Over $125 Million in New Business for Free?"  Grab them HERE: https://www.whalesellingsystem.com/closingsecrets   Ryan Staley Founder and CEO Whale Boss 312-848-7443 ryan@whalesellingsystem.com www.ryanstaley.io    EPISODE RESOURCES https://www.spoton.com ABOUT THE SHOW How do you grow like a VC backed company without taking on investors? Do you want to create a lifestyle business, a performance business or an empire? How do you scale to an exit without losing your freedom? Join the host Ryan Staley every Monday and Wednesday for conversations with the brightest and best Founders, CEO's and Entrepreneurs to crack the code on repeatable revenue growth, leadership, lifestyle freedom and mindset. This show has featured Startup and Billion Dollar Founders, Best Selling Authors, and the World's Top Sales and Marketing Experts like Terry Jones (Founder of Travelocity and Chairman of Kayak), Andrew Gazdecki (Founder of Micro Acquire), Harpaul Sambhi (Founder of Magical with a previous exit to Linkedin) and many more. This is where Scaling and Sales are made simple in 25 minutes or less. Support the show: https://www.linkedin.com/in/ryan-staley/ See omnystudio.com/listener for privacy information.

von Jürgen Vagt 12.05.22 Heute begrüßte ich Luise Müller-Hofstede von Circular bei den Zukunftsmobiltisten und Luise Müller-Hofstede verfügt schon über mehrere Jahre Erfahrungen in der Blockchain-Technologie. Seit ein paar Jahren wird die Blockchain-Technologie in einer Software bei Circulor verpackt und immer Kunden unter den Autohersteller greifen zu. Wir haben Anfang des Gespräches des über die Anwendungen der Blockchain-Technologie in der zukünftigen Mobilität gesprochen. Die Blockchain-Technologie gilt als kostengünstige, transparente und betrugssichere Lösung, um Transaktionen durchzuführen. Allein die Elektromobilität wird sehr viele mehr Abrechnungen und Transaktionen notwendig machen und hier könnte die Blockchain-Technologie eingesetzt werden. Batterien und die Lebensdauer Für die Batterien im Elektroauto und die damit verbundenen Nachhaltigkeitsprobleme entwickelt Cicular unter Luise Müller-Hofstede eine Lösung. Die Batterie im Elektroauto bringt einen CO2-Rucksack mit und die Batterie ist der wertvollste Teil im Elektroauto und nun stellt sich die Frage, wie man die Batterie am besten nutzt. Luise Müller-Hofstede hob hervor, dass beim Markthochlauf der Elektromobilität eine Gefahr besteht. Wenn immer mehr Elektroautos verkauft werden, dann könnten viele Batterien verschrottet werden und eine solche Entwicklung würde den Klimawandel beschleunigen. Elektromobilität leistet nur einen Beitrag zum Klimaschutz, wenn die Batterie möglichst lange genutzt werden kann und in einen erneuerbaren Kreislauf überführt wird. Hierfür bräuchte man aber ein allgemein akzeptiertes, betrugssicheres Dokument, welches die Leistungsdaten der Batterie erfasst und allen beteiligten Akteuren über die Lebensdauer und Qualität informiert. Deswegen hat der Bund in Form des Wirtschaftsministeriums den Batteriepass entwickelt und dieses Dokument basiert auf der Blockchain-Technologie. Luise Müller-Hofstede meint, dass jetzt erstmal die Grundlagen gelegt sind und in den nächsten Jahren wird das System mit dem Feedback der beteiligten Akteure verfeinert. Der Batteriepass hat viele Funktionen und man kann seine Funktionen mit dem TÜV-Zertifikat vergleichen und laut Luise Müller-Hofstede ist der Batteriepass der zentrale Baustein für das Batterie – Recycling, weil nur der Wert der einzelnen Batterie klar ist und einen definierten Wert hat, somit kann die Batterie im Recycling wieder nutzbar gemacht werden.

TCW Podcast Episode 162 - Spinnaker Software   Often we laugh at educational games and software.  We tend to view the products as jokes and something that cannot fully succeed.  In our look at Spinnaker Software, we learn that there is more to it.  The company was short-lived but was founded by people with a deep passion for technology and gaming. They released games, and software that helped to show that there is more one can do with a computer than just drills.  If one of them went on to become a major World Of Warcraft raid leader it can't all be bad right?   Facemaker: https://www.youtube.com/watch?v=seh6DyUPV8w Story Machine: https://www.youtube.com/watch?v=YpbrcpfVwPY Snooper Troops: https://www.youtube.com/watch?v=MJOFAPPfZ2I Alphabet Zoo: https://www.youtube.com/watch?v=X1m4Lt-7cY8 Adventure Creator: https://www.youtube.com/watch?v=nb_7-rlocKo Rendezvous with Rama: https://www.youtube.com/watch?v=4VMbPzf_pq8 Fahrenheit 451: https://www.youtube.com/watch?v=vnET12whCYs Dragonworld: https://www.youtube.com/watch?v=ens1xbetX88 Amazon: https://www.youtube.com/watch?v=MTojZBzyFrI Shadowkeep: https://www.youtube.com/watch?v=igXOcweWz_M Below the Roots: https://www.youtube.com/watch?v=pI87UAC3JzQ WindowWorks: https://winworldpc.com/product/pfs-windowworks/2x   New episodes on the 1st and 15th of every month!   TCW Email: feedback@theycreateworlds.com  Twitter: @tcwpodcast Patreon: https://www.patreon.com/theycreateworlds Alex's Video Game History Blog: http://videogamehistorian.wordpress.com Alex's book is available for preorder and should be released through CRC Press in December 2019: http://bit.ly/TCWBOOK1     Intro Music: Josh Woodward - Airplane Mode -  Music - "Airplane Mode" by Josh Woodward. Free download:http://joshwoodward.com/song/AirplaneMode  Outro Music: RolemMusic - Bacterial Love - http://freemusicarchive.org/music/Rolemusic/Pop_Singles_Compilation_2014/01_rolemusic_-_bacterial_love    Copyright: Attribution: http://creativecommons.org/licenses/by/4.0/

AI-driven urban safety drones

Der aktuelle Raspberry Pi 4 ist derzeit nur zu überzogenen Preisen zu bekommen, wenn überhaupt. Raspi-Bastler müssen daher mit den älteren lieferbaren Varianten des Bastelcomputers vorlieb nehmen oder damit, was Bastelschublade und eBay hergeben. Oder sie werfen einen Blick auf den viel günstigeren und und stromsparenden Raspi Pi Pico, einem Microcontroller mit herausfordernden Einschränkungen. Wir sprechen über die in c't 11/2022 vorgestellten Projekte: Eines verlängert ganz ohne Hardware-Basteln ein USB-Kabel per LAN/WLAN. Das ermöglicht beispielsweise, alte Drucker an einen entfernt stehenden PC anzuschließen oder USB-Sensoren (etwa für Zigbee) an günstigen Positionen zu befestigen statt in PC-Nähe. Der Hardwareaufbau war trivial, aber die Software erforderte einige Hartnäckigkeit. Anders herum das zweite Projekt, ein kleiner Roboter: Er war vor allem mechanisch aufwendig zusammenzubauen. Beide Projekte funktionieren auch mit älteren Raspis -- aber mit welchen? Wir geben einen Überblick über die wichtigsten Unterschiede ihrer Schnittstellenausstattung und Leistungsfähigkeit. Das dritte Projekt nähert sich dem Raspberry Pi Pico an, der weniger ein abgespeckter Raspi ist, sondern ein Microcontroller, bei dem man viel Raspi-Wissen einbringen kann. Wir vergleichen an einem digitalen Zollstock -- ein Ultraschall-Entfernungsmesser und eine Siebensegmentanzeige -- die Unterschiede der Implementierung am Raspi und am Pico. Zudem diskutieren wir die Vorteile des Pico gegenüber anderen Microcontrollern -- und generell die Gründe, warum die c't-Redaktion größtenteils Projekte lieber mit dem Raspi umsetzt als mit anderen Bastelcomputern. ***SPONSOR-HINWEIS*** Das IT-Team der Finanz Informatik gestaltet das Banking der Zukunft – als Digitalisierungspartner der Sparkassen-Finanzgruppe. IT-Profis finden hier spannende Aufgaben und attraktive Benefits. Jetzt bewerben! karriere.f-i.de/jobs ***SPONSOR-HINWEIS ENDE***

Der aktuelle Raspberry Pi 4 ist derzeit nur zu überzogenen Preisen zu bekommen, wenn überhaupt. Raspi-Bastler müssen daher mit den älteren lieferbaren Varianten des Bastelcomputers vorlieb nehmen oder damit, was Bastelschublade und eBay hergeben. Oder sie werfen einen Blick auf den viel günstigeren und und stromsparenden Raspi Pi Pico, einem Microcontroller mit herausfordernden Einschränkungen. Wir sprechen über die in c't 11/2022 vorgestellten Projekte: Eines verlängert ganz ohne Hardware-Basteln ein USB-Kabel per LAN/WLAN. Das ermöglicht beispielsweise, alte Drucker an einen entfernt stehenden PC anzuschließen oder USB-Sensoren (etwa für Zigbee) an günstigen Positionen zu befestigen statt in PC-Nähe. Der Hardwareaufbau war trivial, aber die Software erforderte einige Hartnäckigkeit. Anders herum das zweite Projekt, ein kleiner Roboter: Er war vor allem mechanisch aufwendig zusammenzubauen. Beide Projekte funktionieren auch mit älteren Raspis -- aber mit welchen? Wir geben einen Überblick über die wichtigsten Unterschiede ihrer Schnittstellenausstattung und Leistungsfähigkeit. Das dritte Projekt nähert sich dem Raspberry Pi Pico an, der weniger ein abgespeckter Raspi ist, sondern ein Microcontroller, bei dem man viel Raspi-Wissen einbringen kann. Wir vergleichen an einem digitalen Zollstock -- ein Ultraschall-Entfernungsmesser und eine Siebensegmentanzeige -- die Unterschiede der Implementierung am Raspi und am Pico. Zudem diskutieren wir die Vorteile des Pico gegenüber anderen Microcontrollern -- und generell die Gründe, warum die c't-Redaktion größtenteils Projekte lieber mit dem Raspi umsetzt als mit anderen Bastelcomputern. ***SPONSOR-HINWEIS*** Das IT-Team der Finanz Informatik gestaltet das Banking der Zukunft – als Digitalisierungspartner der Sparkassen-Finanzgruppe. IT-Profis finden hier spannende Aufgaben und attraktive Benefits. Jetzt bewerben! karriere.f-i.de/jobs ***SPONSOR-HINWEIS ENDE***

Der aktuelle Raspberry Pi 4 ist derzeit nur zu überzogenen Preisen zu bekommen, wenn überhaupt. Raspi-Bastler müssen daher mit den älteren lieferbaren Varianten des Bastelcomputers vorlieb nehmen oder damit, was Bastelschublade und eBay hergeben. Oder sie werfen einen Blick auf den viel günstigeren und und stromsparenden Raspi Pi Pico, einem Microcontroller mit herausfordernden Einschränkungen. Wir sprechen über die in c't 11/2022 vorgestellten Projekte: Eines verlängert ganz ohne Hardware-Basteln ein USB-Kabel per LAN/WLAN. Das ermöglicht beispielsweise, alte Drucker an einen entfernt stehenden PC anzuschließen oder USB-Sensoren (etwa für Zigbee) an günstigen Positionen zu befestigen statt in PC-Nähe. Der Hardwareaufbau war trivial, aber die Software erforderte einige Hartnäckigkeit. Anders herum das zweite Projekt, ein kleiner Roboter: Er war vor allem mechanisch aufwendig zusammenzubauen. Beide Projekte funktionieren auch mit älteren Raspis -- aber mit welchen? Wir geben einen Überblick über die wichtigsten Unterschiede ihrer Schnittstellenausstattung und Leistungsfähigkeit. Das dritte Projekt nähert sich dem Raspberry Pi Pico an, der weniger ein abgespeckter Raspi ist, sondern ein Microcontroller, bei dem man viel Raspi-Wissen einbringen kann. Wir vergleichen an einem digitalen Zollstock -- ein Ultraschall-Entfernungsmesser und eine Siebensegmentanzeige -- die Unterschiede der Implementierung am Raspi und am Pico. Zudem diskutieren wir die Vorteile des Pico gegenüber anderen Microcontrollern -- und generell die Gründe, warum die c't-Redaktion größtenteils Projekte lieber mit dem Raspi umsetzt als mit anderen Bastelcomputern. ***SPONSOR-HINWEIS*** Das IT-Team der Finanz Informatik gestaltet das Banking der Zukunft – als Digitalisierungspartner der Sparkassen-Finanzgruppe. IT-Profis finden hier spannende Aufgaben und attraktive Benefits. Jetzt bewerben! karriere.f-i.de/jobs ***SPONSOR-HINWEIS ENDE***

This week's construction tech news with James Benham (@JamesMBenham), and Jeff Sample (@IronmanofIT) Featuring: - Interview with Courtney Honda from BidVita - Construction Tech News of the Week Follow @TheConTechCrew on social media for more updates and to join the conversation! Listen to the show at http://thecontechcrew.com Powered by JBKnowledge Learn more at http://thecontechcrew.com or follow @JBKnowledge & @TheConTechCrew on Twitter.

In this episode, Jamon, Robin, and Mazen go through some of the differences in React Native 0.68. We also find out that somehow Robin managed to get "banned" from Twitter Communities. This episode brought to you by Infinite Red! Infinite Red is a premier React Native design and development agency located in the USA. With five years of React Native experience and deep roots in the React Native community (hosts of Chain React and the React Native Newsletter), Infinite Red is the best choice for your next React Native app.Helpful Links:Announcing React Native 0.68Jamon's article on using the correct JDK for M1 MacsConnect With Us!React Native Radio - @ReactNativeRdioJamon - @jamonholmgrenMazen - @mazenchamiRobin -  @robin_heinze

This week we're joined by Mike Riley and we're talking about his book Portable Python Projects (Running your home on a Raspberry Pi). We breakdown the details of the latest Raspberry Pi hardware, various automation ideas from the book, why Mike prefers Python for scripting on a Raspberry Pi, and of course why the Raspberry Pi makes sense for home labs concerned about data security. Use the code PYPROJECTS to get a 35% discount on the book. That code is valid for approximately 60 days after the episode's publish date.

Bei Saturn bekommt ihr im Rahmen der Gutscheinheft-Aktion noch bis zum 17. Mai zu ausgewählten Produkten Coupons, Rabatte oder Gratis-Artikel. Als Geschenke winken Soundbars, Software und vieles mehr. Wir haben uns die Angebote genauer angesehen und verraten, welche Deals sich wirklich lohnen.

Kuhfladen, Kontinentaldrift und Kraftfahrtbundesamt. Damit Mercedes die S-Klasse und den EQS automatisiert auf die deutschen Autobahnen schicken kann, sind jede Menge Sensoren, Computer, Software und vor allem Genehmigungen gefragt. Wie das alles zusammenhängt, haben wir in der aktuellen Folge des Moove Podcast mit Matthias Kaiser von Mercedes besprochen, der uns den weltweit ersten serienreifen Level 3-Assistenten Drive Pilot genau erklärt hat. Matthias verrät, welche Probleme Kameras beim automatisierten Fahren haben, was Sheldon Cooper und die US-Serie Big Bang Theorie mit den Talenten des Radars zu tun haben und wieso die Mikrofone der Freisprecheinrichtung während der Fahrt mit dem Drive Pilot immer in die Umgebung lauschen. Außerdem erklärt Matthias warum es beim Level 3 Fahren zunächst bei 60 km/h bleibt, warum 10 Sekunden beim automatisierten Fahren ziemlich lange sind und warum Zeitunglesen trotz aller technischer Raffinesse des Systems aktuell noch nicht möglich ist. Was Matthias Kaiser sonst noch erzählt hat und wieso er nicht glaubt, dass die Zeit des Selbstfahrens so schnell endet und warum die Corona-Zeit und die damit verbundenen leeren Straßen für ihn und seine Kollegen besonders hart waren, erfahrt ihr, in der aktuellen Folge.

Você sabe como funciona a gestão dentro das internações hospitalares? Além disso, você entende como é construir uma empresa sendo cofounder, COO e, também, sendo uma mulher? Hoje, vamos descobrir, juntos, como fazer do mundo um lugar melhor. No episódio #222 do “EmpreendaCast”, Gustavo Passi recebe Erika Monteiro, co-founder da Carefy, a plataforma de gestão de pacientes internados. A empresa tem tecnologia para desenvolver um sistema de gerenciamento para leitos, auxiliar operadoras e hospitais a estruturarem esforços de forma rápida e eficiente. Siga o nosso Instagram: @empreendacast Participe do nosso grupo no Telegram: https://t.me/empreendacast Produção: Voz e Conteúdo – www.vozeconteudo.com.br - @vozeconteudo --- Send in a voice message: https://anchor.fm/empreendacast/message Support this podcast: https://anchor.fm/empreendacast/support

Honor möchte den Platz von Huawei einnehmen und hat das in China auch schon geschafft. Jetzt kommt mit dem Honor Magic 4 Pro wieder ein Top-Smartphone zum Preis von 1.099 Euro in Deutschland auf den Markt. Technisch und optisch gesehen ein echter Leckerbissen. Bei der Software hakt es jedoch deutlich, wie erste Tests von Übersee verraten – besonders bei der Update-Garantie.

Ian and Corey met at Microsoft, where they built Microsoft Office Business Scorecard Manager 2005 (which boasted its own CD-ROM).They went on to found Mattermost in 2016 to give developers one platform for collaborating across tools and teams.Ian, who previously founded the game company SpinPunch, calls Mattermost “yet another of those video game companies turned B2B software companies,” like Slack and Discord. Says Ian: “Games are all the risk of a movie plus all the complexity of a B2B SaaS product.”Today's Lifeboat badge goes to user Diogo for their answer to How can I call functions from one .cpp file in another .cpp file?.Connect with Ian on LinkedIn.Connect with Corey on LinkedIn.

Welcome to Episode 121 Main Topic How do I get a hold of expensive software, for the purposes of learning? Check with your school, a LOT of vendors have super-cheap solutions for education.  Your school may be able to provide you a learning license/sub for software you are interested in Less than Legal alternatives Red hat enterprise linux Red Hat Developer Sub https://developers.redhat.com/articles/getting-red-hat-developer-subscription-what-rhel-users-need-know#  Centos literally feeds RHEL, Centos stream is an extremely similar platform. Fedora feeds Centos, Ubuntu Ubuntu Server is free, but you can buy support from Canonical Windows Server Try it on azure's free tier Windows server will run for some time without activation Talk to a partner about a trial https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/ https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/  https://www.microsoft.com/en-us/windows-server/trial  Red Hat Openshift https://developers.redhat.com/openshift/hosting-openshift Trial, ask your account rep OKD is the upstream for Openshift OpenShift Online has a free tier First, are you a student?  What if i Just CANNOT find a demo? Operating Systems VM/Container platforms   Vmware vsphere https://www.vmware.com/try-vmware.html https://customerconnect.vmware.com/en/web/vmware/evalcenter?p=free-esxi7 . Vmware has a surprising number of public trials/demos, and even labs, here: Or just stand-alone esxi?  Industry Software Included with most RHEL subs, but not the dev sub.   Trials are available.  The Katello project is the open source upstream Oracle DB Their site seems to steer you toward an account rep, or their cloud. I believe that oracle will operate without a license, but I do not know that they have an official trial Red Hat Satellite Oracle SaaS and Cloud Aws AWS Free Tier https://www.microsoft.com/en-us/windows-server/trial  Also, amazon linux is pretty similar to RHEL…  Google compute https://cloud.google.com/compute/  You get a $300 credit to get hooked. Azure https://azure.microsoft.com/en-in/free/  Effectively a 30 day trial, you get $200 to use for 30 days Digital ocean https://try.digitalocean.com/freetrialoffer/  Currently a 60 day/$100 trial Linode $100 trial credit Rotating list of promotions: https://www.linode.com/promotions/ Github Free for all, as far as I know Enterprise: (includes a free trial link) https://github.com/enterprise     Watch us live on the 2nd and 4th Thursday of every month! Subscribe and hit the bell! https://www.youtube.com/IronSysadminPodcast  OR https://twitch.tv/IronSysadminPodcast   Discord Community: https://discord.gg/wmxvQ4c2H6  Find us on Twitter, and Facebook! https://www.facebook.com/ironsysadmin https://www.twitter.com/ironsysadmin Subscribe wherever you find podcasts! And don't forget about our patreon! https://patreon.com/ironsysadmin   Intro and Outro music credit: Tri Tachyon, Digital MK 2http://freemusicarchive.org/music/Tri-Tachyon/ 

My blog:https://nicolalindgren.comTwitter: @NicolaLindgrenHow Can I Test This?https://leanpub.com/howcanitestthisStarting Your Software Testing Career:https://leanpub.com/startinginsoftwaretesting (paperback can be bought on Amazon)Testing With Charles Proxy Blog series :https://nicolalindgren.com/2022/01/17/testing-with-charles-proxy-part-1/

Episodio donde Pari le regala a Wisto algo inolvidable. Continúan con una plática sobre los diferentes Jasons y sus películas, el desestrés de Wisto le da estrés con su avance de Bloodborne, lo bueno y lo malo sobre los desarrolladores From Software, están regalando el EA Fifa 2022 como venganza, se hace oficial The Batman 2, tiene muchísimo potencial con tantos villanos nuevos porque el Guasón ya chole, y termina con una reseña complementaria de Wisto sobre la nueva película de Scream con spoilers. Escúchanos: Spotify / Apple Podcast / ivoox / YouTube Apóyanos: patreon.com/holamsupernova Síguenos: Twitter/ Instagram: holamsupernova

Another entry in the maintenance series! Throughout the series we've discussed building versus buying, building actually maintainable software, maintaining ourselves, open source maintenance, legacy code, and most recently Go project structure. In this 7th installment of the series, we continue narrowing our focus by talking about what to do when projects get big and messy.

I've tried many grammar checkers online, but most programs don't measure up to the choice few. You may have heard of and use grammar checking programs like Grammarly, WhiteSmoke, Ginger, Hemingway, and Textly, but what about ProWritingAid? Where does it stand among its competitors? And why do I heavily endorse ProWritingAid? Find out my full thoughts and why I believe ProWritingAid is the best grammar checking software today!   Level-Up Your Self-Publishing Business TODAY: ProWritingAid - https://DaleLinks.com/ProWritingAid The Amazon Self Publisher – https://DaleLinks.com/SelfPubBook Subscribe to Self-Publishing with Dale on YouTube at https://DaleLinks.com/YT and https://DaleLinks.com/YouTubePodcast. Join other like-minded and motivated self-publishers in the Self-Publishing Books Group. Learn, grow, and network with authors, freelancers, and industry experts at https://DaleLinks.com/SPB. Remember to answer the 3 questions to gain entry. Get access to my go-to resource, Publisher Rocket. Confidently research profitable keywords & categories. Easily select effective keywords for Amazon Advertising campaigns. For more details, visit https://dalelinks.com/PR.   FULL DISCLOSURE: Most outbound links financially compensate the podcast through affiliate programs or sponsorship deals. We only recommend products and services we've used and confidently stand behind. Using the links do not adversely affect your purchase price and greatly helps support the channel. Thank you for your understanding. 

The Morning Crew discusses car software problems. 

Laura Crabtree (@llcrabbie), founder and CEO of Epsilon3, joins Lucas Bagno and Ian Cinnamon on this episode to discuss:- What she accomplished during her time at SpaceX and her journey to starting Epsilon3. - Whether the biggest contribution of SpaceX to the industry will be all the amazing people leaving to start their own space companies.- How to get into the space industry if you don't already have a background in it.- Why a company like Epsilon3 hasn't been built before.- The importance of being vulnerable as a founder.Thanks for listening — if you like what you hear, please review us on your favorite podcast platform. Check us out on the web at www.villageglobal.vc or get in touch with us on Twitter @villageglobal.Want to get updates from us? Subscribe to get a peek inside the Village. We'll send you reading recommendations, exclusive event invites, and commentary on the latest happenings in Silicon Valley. www.villageglobal.vc/signup

Dede Perkins, Co-Founder and CEO of ProCanna, joined the cannabis industry in 2013 as a member of the application team that won one of the first competitive vertically integrated applications in Massachusetts. After that, she helped win cannabis licenses in New York, Maryland, Pennsylvania, Ohio, California, Arkansas, North Dakota, and Nevada. A regulatory specialist, Dede is passionate about combining compliance with operational excellence; safe, standardized products; empowered employees; strong company culture and brands. Instagram: https://www.instagram.com/rmcc_cannaconsulting/ LinkedIn: https://www.linkedin.com/company/rocky-mountain-cannabis-consulting Subscribe to Podcast: https://open.spotify.com/show/4TaI1xJHpRgvTXT92Jfv4W?si=HTTsEiO3Tq6FdhBlWju9Uw Subscribe to YouTube: https://www.youtube.com/channel/UCBysW0XMCO5lUvgy1xk2RYw Free 40-minute compliance operations masterclass: https://academy.rmcc.io/audit-workshop

Show Notes can be found on the episode page on TuxDigital - https://tuxdigital.com/podcasts/sudo-show/sudo-51

Watch the live stream: Watch on YouTube About the show Sponsored: RedHat: Compiler Podcast Special guest: Tonya Sims Michael #1: Pathy: a Path interface for local and cloud bucket storage via Spencer Pathy is a python package (with type annotations) for working with Cloud Bucket storage providers using a pathlib interface. It provides an easy-to-use API bundled with a CLI app for basic file operations between local files and remote buckets. It enables a smooth developer experience by letting developers work against the local file system during development and only switch over to live APIs for deployment. Also has optional local file caching. From Spenser The really cool function is "Pathy.fluid" which can take any type of local, GCS, or S3 path string and then just give you back a Path object that you can interact with agnostic of what platform it was. So this has worked amazingly for me in local testing since i can just change the file path from the "s3://bucket/path" that i use in prod to a local "test_dir/path" and it works automatically. Brian #2: Robyn “Robyn is a fast, high-performance Python web framework with a Rust runtime.” Hello, Robyn! - intro article docs, repo Neat things doesn't need WSGI or ASGI async very Flask-like Early, so still needs some TLC docs, etc. getting started and demo apps would be good. Tonya #3: Python package 'nba_api' is a package to access data for NBA.com This package is maintained by Swar Patel API Client package for NBA.com, more accessible endpoints, and better documentation The NBA.com API's are not well documented and change frequently (player traded, injured, retired, points per game, stats, etc) The nba_api package has tons of features: The nba_api starts with static data on players and teams (Full name, team name, etc). Each player and Team has an id. Can get game data from the playergamelog API endpoint The package also has many different API endpoints that it can hit by passing in features from the static data to the API endpoints as parameters Michael #4: Termshot From Jay Miller Creates screenshots based on terminal command output Just run termshot YOUR_CMD or termshot --show-cmd -- python program.py Even termshot /bin/zsh for full interactive “recording” Example I made: Brian #5: When Python can't thread: a deep-dive into the GIL's impact Itamar Turner-Trauring Building a mental model of the GIL using profiler graphs of simple two thread applications. The graphs really help a lot to see when the CPU is active or waiting on each thread. Tonya #6: Sportsipy: A free sports API written for python Free python API that pulls the stats from www.sports-reference.com sports-reference.com - great website for getting sports stats for professional sports(NBA, NFL, NHL, MLB, college sports) Looks like an HTML website for the 90s - great for scraping (email site owners) You can get API queries for every sport (North American sports) like the list of teams for that sport, the date and time of a game, the total number of wins for a team during the season, and many more team-related metrics. You can also get stats from players and box scores - so you can build cool stuff around how a team performed during a game or during a season. Extras Michael: Python 3.11.0 beta 1 is out Test with GitHub Actions against Python 3.11 Joke: Finding my family

How much time do you spend solving negative engineering problems? And can a framework solve them for you? Think of negative engineering as things you do to avoid bad outcomes in software. At the lowest level, this can be writing good error handling with try / except. But it's broader than that: logging, observability (like Sentry tools), retries, failover (as in what you might get from Kubernetes), and so on. We have a great chat with Chris White about Prefect, a tool for data engineers and data scientists meaning to solve many of these problems automatically. But it's a conversation applicable to a broader software development community as well. Links from the show Chris White: @markov_gainz Prefect: prefect.io Fermat's Enigma Book (mentioned by Michael): amazon.com Prefect Docs (2.0): orion-docs.prefect.io Prefect source code: github.com A Brief History of Dataflow Automation: prefect.io/blog Watch this episode on YouTube: youtube.com Episode transcripts: talkpython.fm --- Stay in touch with us --- Subscribe to us on YouTube: youtube.com Follow Talk Python on Twitter: @talkpython Follow Michael on Twitter: @mkennedy Sponsors Microsoft Talk Python Training AssemblyAI

OpenBSD 7.1 is out, Building Your Own FreeBSD-based NAS with ZFS Part 2, Let's try V on OpenBSD, Waiting for Randot, Compiling an OpenBSD kernel 50% faster, A Salute for 10+ years of service, and more NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines OpenBSD 7.1 is out (https://www.openbsd.org/71.html) Building Your Own FreeBSD-based NAS with ZFS Part 2 (https://klarasystems.com/articles/part-2-tuning-your-freebsd-configuration-for-your-nas/) News Roundup Let's try V on OpenBSD (https://briancallahan.net/blog/20220426.html) Waiting for Randot (or: nia and maya were right and I was wrong) (http://mail-index.netbsd.org/tech-security/2021/01/11/msg001100.html) Compiling an openbsd kernel 50% faster (https://flak.tedunangst.com/post/compiling-an-openbsd-kernel-50-faster) A Salute for 10+ years of service (http://aboutbsd.net/?page_id=26661) https://archive.ph/JL5hf (if the site is down) Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Glenn - Toms Home Lab (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/454/feedback/Glenn%20-%20Toms%20Home%20Lab.md) Iamchunky_pie - unix tool writing (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/454/feedback/I_am_chunky_pie%20-%20unix%20tool%20writing.md) Mike - Making Routers (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/454/feedback/Mike%20-%20Making%20Routers.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

How do I set an appropriate price for my software? What criteria should I consider when setting up a price? What is the right price for paid software? These are the questions we are going to answer in today's episode of Dev Questions.Website: https://iamtimcorey.com/Patreon: https://www.patreon.com/IAmTimCoreyAsk Your Question: https://suggestions.iamtimcorey.com/Sign Up to Get More Great Developer Content in Your Inbox: https://signup.iamtimcorey.com/

All three major averages closed lower and Jim Cramer is helping investors through the continuously volatile market. Then, Unity Software CEO John Riccitiello talks to Cramer fresh off earnings to discuss what brought the company to lower their full year guidance. Next, GlobalFoundries CEO Dr. Tom Caulfield joins Cramer as the first in-studio guest in more than two years to discuss 1Q '22 results and more. Plus, Roblox CEO Dave Baszucki shares insight on the company's key financial and operating results from the most recent quarter.

Ken Wimberly is the founder of the Legacy of Love app, a parent-to-child journaling app designed to capture the moments that matter. Ken speaks about the challenges of building and growing an app as a non-technical founder, his entrepreneurial endeavors as the owner of a pizza place, in commercial real estate, and opening a chain of laundromats.Connect with Ken:Email: ken@legacyoflove.appFacebook: https://www.facebook.com/lordwimberly Mentioned in today's episode:Legacy of Love: https://legacyjournal.app/LaundryLuv: https://www.laundryluv.com/ Want more from Ardan Labs? You can learn Go, Kubernetes, Docker & more through our video training, live events, or through our blog!Online Courses: https://ardanlabs.com/education/ Live Events: https://www.ardanlabs.com/live-training-events/ Blog: https://www.ardanlabs.com/blog Github: https://github.com/ardanlabs 

• Intro • Nintendo had it's Financial Reports Briefing, showing Switch Sales • Nintendo expects Switch sales to DROP this year, despite great SOFTWARE launches • Nintendo updated it's current list of best selling Switch games • IGN reports on growing discontent at Nintendo  • Xbox streaming only system reportedly coming soon • Fortnite back on iOS (thanks to Xbox cloud gaming) • Xbox games were UNPLAYABLE for FOUR DAYS due to DRM outage • 2022 world video game hall of fame inductees  • AEW game title and footage revealed • The Queen's 24k gold Wii going on sale • Last gen Gotham knights canceled  • TWEET OF THE WEEK • Q&A Streamed: May 10th, 2022 on http://twitch.tv/wulffden

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews: Hot Topics: Digital Transformation in Ghana, How AI is Being Used to Fight Forest Fires, How and Why Digital Transformation Needs a Make Over, Kraft Heinz and Microsoft Relationship (Eric and Kyler) Digital Strategy and Software Selection (Tony Ford, Third Stage Consulting) Creating a Culture of Change When Deploying Sales Technology (Josh Noble, ShipOffers) We also cover a number of other relevant topics related to digital and business transformation throughout the show. This weekly podcast series premiers live on YouTube every Wednesday at 8am NYC time / 1pm London / 9pm Hong Kong. You can also subscribe to the podcast on Apple, Google, Spotify, Pandora, or your favorite podcast platform. WATCH MORE EPISODES HERE: https://youtube.com/playlist?list=PLyI-oIQSgI2DGXQKvUz-farHwls_B3G3i —————————————————————— DOWNLOAD MORE RESOURCES BELOW: —————————————————————— 2021 DIGITAL TRANSFORMATION REPORT: http://resource.thirdstage-consulting.com/2021-digital-transformation-report   TOP 10 ERP SYSTEMS RANKING: https://www.thirdstage-consulting.com/the-top-10-erp-systems-for-2020/   TOP 10 ERP SYSTEMS FOR SMALL BUSINESSES: https://www.thirdstage-consulting.com/top-erp-systems-for-small-businesses/   TOP 10 CRM SYSTEMS: https://www.thirdstage-consulting.com/top-10-crm-systems-for-digital-transformations   GUIDE TO ORGANIZATIONAL CHANGE MANAGEMENT: http://resource.thirdstage-consulting.com/the-definitive-guide-to-erp-hcm-organizational-change-management   20 LESSONS FROM 1,000 ERP IMPLEMENTATIONS: https://resource.thirdstage-consulting.com/lessons-from-1000-erp-implementations-ebook   ———————————————————— CONNECT WITH ME: ———————————————————— LINKEDIN: https://www.linkedin.com/in/erickimberling/ INSTAGRAM: https://www.instagram.com/erickimberling/ TIKTOK: https://www.tiktok.com/@erickimberling0 TWITTER: https://twitter.com/erickimberling CLUBHOUSE: https://www.joinclubhouse.com/@erickimberling THIRD STAGE LINKEDIN PAGE: https://www.linkedin.com/company/third-stage-consulting-group/ CONTACT ME TO BRAINSTORM IDEAS FOR YOUR DIGITAL TRANSFORMATION: eric.kimberling@thirdstage-consulting.com   ———————————————————— MUSIC IN THIS EPISODE: ———————————————————— Get I'm Ready by The Eiffels here https://t.lickd.co/geq6gnjo3Y8 License ID: klJ8vZQv83Z     Get You Worry Me by Nathaniel Rateliff & The Night Sweats here https://t.lickd.co/XzBW917yD6r License ID: 1kdvJDkmP2G   Get International Space Station by British Sea Power here https://t.lickd.co/5rM5pxr8zjn License ID: O50xpBppWGK   Get Epic by Faith No More here https://t.lickd.co/zG5VzByg51a License ID: vOoDmdKN9Bm   Get Can I Play With Madness (1998 - Remaster) by Iron Maiden here https://t.lickd.co/rPYy0OeVxlk License ID: 5vBq7GExqoV   Get Relax by Frankie Goes To Hollywood here https://t.lickd.co/86xKJAXy5n0 License ID: LZd7OoK67l0   Get Bad To The Bone by George Thorogood & The Destroyers here https://t.lickd.co/Ooy7kBDQy97 License ID: xRNEVyaYzMB   Get Back on the Chain Gang by Pretenders here https://lickd.lnk.to/H2t9DXID!Eric%20Kimberling%20-%20Digital%20Transformation License ID: a5Pk5v8gD71 Get this and other songs for your next YouTube video at https://lickd.co      

Drew Ryun is the founder and CEO of Campaign Sidekick, a voter contact app used by campaigns across the country to reach voters via phone, at doors, and text messages. Drew has a long history of working in campaigns both as an operative and as an entrepreneur. The Business of Politics Show, hosted by Eric Wilson, is a production of Startup Caucus, an investment fund and incubator for Republican campaign technology.Visit StartupCaucus.com to learn more.

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.