Podcasts about aws summit

Quest'anno l'AWS Summit di Milano si terrà il 18 giugno a Fiera Milano Rho. In questo episodio Massimiliano Galli (Head of Marketing AWS Italia) ci racconterà come funziona il Summit, quali sono i contenuti, le attività in programma, le tracce e tutte le cose interessanti che potrete trovare. Ci vediamo al Summit!Link utili:- AWS Summit Milano

Send us a textIn this episode, we dive deep into the world of digital transformation and cloud-native architecture with Madoc Batters, Head of Cloud, Network and IT Security at Warner Hotels. Madoc shares his remarkable journey from washing 100 cars at age 11 to buy his first ZX81 computer to leading enterprise-scale cloud migrations. We explore the challenges of organizational culture change, the bold decision to migrate their most complex system first, and the importance of shifting left with security and FinOps practices. Madoc also shares insights on modern networking solutions like Alkira, the role of AI in transformation, and how his ultra-marathon mindset (including a 105-mile run) applies to pushing through digital transformation challenges. Whether you're starting your cloud journey or looking to accelerate your transformation efforts, this episode is packed with practical wisdom and inspiring leadership insights.Where to Find MadocLinkedIn: https://www.linkedin.com/in/madoc-batters-aws-machinelearning/Sessionize: https://sessionize.com/madoc-batters/Show LinksWarner Hotels: https://www.warnerhotels.co.uk/Alkira: https://www.alkira.com/AWS Bedrock: https://aws.amazon.com/bedrock/HashiCorp: https://www.hashicorp.com/AWS Summit: https://aws.amazon.com/events/summits/FinOpsX: https://www.finops.org/community/finopsx/ZX81 Computer: https://en.wikipedia.org/wiki/ZX81Follow, Like, and Subscribe!Podcast: https://www.thecloudgambit.com/YouTube: https://www.youtube.com/@TheCloudGambitLinkedIn: https://www.linkedin.com/company/thecloudgambitTwitter: https://twitter.com/TheCloudGambitTikTok: https://www.tiktok.com/@thecloudgambit

What does it take to turn a moment of frustration into a global mission to tackle waste? At the AWS Summit in London, I sat down with Tessa Clarke, co-founder and CEO of Olio, to explore how a single idea born on a snowy Swiss street evolved into a powerful tech platform reshaping how communities think about consumption, sharing, and sustainability. Tessa shared her personal journey, from growing up on a farm where food waste was unthinkable to climbing the corporate ladder before walking away to co-found Olio. That decision came after she was told to throw away perfectly good food while moving house, a moment that sparked an idea and a deeper calling. What followed was years of research, a grassroots WhatsApp experiment, and ultimately, the creation of an app that now connects millions of users worldwide. In our conversation, we explored how Olio uses technology to drive real-world change. Tessa explained how AWS has been a foundational partner since day one, helping Olio scale sustainably without compromising its values. She also gave an inside look at how AI is integrated thoughtfully across their operations, from assisting users in listing items faster to detecting potentially unsafe or inappropriate listings before they go live. What stood out is how intentional Tessa and her team have been in making AI serve the mission, not distract from it. Whether it's reducing friction within communities or using automation to offset operational challenges, every tech choice is aligned with their goal: to build a waste-free world. We also discussed how AI is helping them break the traditional link between headcount and impact, paving the way toward profitability while staying people-focused. As Olio aims to reach a billion users by 2030, this episode is a reminder of what happens when purpose and technology meet. Tessa's story offers a compelling blueprint for founders, technologists, and anyone looking to use digital tools to solve human problems. How can a simple act of sharing create ripple effects across the world, and what role will technology play in scaling that vision responsibly?

In dieser Episode sprechen wir mit zwei AWS Heroes über den AWS Summit Hamburg am 5. Juni 2025. Markus Ostertag und Thorsten Höger geben als langjährige Summit-Veteranen einen exklusiven Einblick in das, was Besucher erwartet und teilen ihre persönlichen Highlights und Networking-Tipps. Kernthemen der Episode: - Warum der Summit 2025 in Hamburg stattfindet - Content-Highlights: Über 100 Sessions zu Gen AI, Cloud Transformation und mehr - Die AWS Community Lounge als wichtiger Treffpunkt - Das neue AWS for Software and Technology Loft - Women of the Cloud Stage mit erweitertem Programm - AWS HouseWarming am Vortag mit über 60 Hands-on Workshops - Networking-Möglichkeiten und Festival-Atmosphäre Summit-Tipps für Neulinge: - Vorab die Agenda durchgehen und interessante Sessions markieren - Flexibel bleiben und nicht zu strikt planen - auch spontane Entdeckungen zulassen - Die Community Lounge als erste Anlaufstelle nutzen - hier gibt es praxisnahe Erfahrungsberichte - Aktiv das Gespräch suchen, z.B. beim Mittagessen oder an den Expo-Ständen - AWS Announcements der letzten Wochen als Gesprächseinstieg nutzen - "Walk the Summit" Format für Frauen in Tech nutzen, um gemeinsam die Veranstaltung zu erkunden - Balance zwischen Sessions, Expo und Networking finden - Genug Zeit für spontane Gespräche einplanen Die AWS Community Lounge - Highlights: - Eigene Stage mit Community-kuratiertem Programm "von der Community für die Community" - Praxisnahe Sessions mit ehrlichen Einblicken in Herausforderungen und Lösungen  - Hands-on Erfahrungsberichte von AWS-Anwendern - Offener Networking-Bereich zum Austausch mit erfahrenen Community-Mitgliedern - Tiefgehende technische Diskussionen im "Maschinenraum" - Idealer Startpunkt für Summit-Neulinge zum Kontakte knüpfen - Direkte Gespräche mit Vortragenden und Community-Experten - 7 Slots mit ausgewählten Community-Speakern Besondere Highlights: - Keynote mit Stefan Höchbauer (AWS), Dr. Steffen Merkel (DFL) und Donja Florence-Aimer (Hapag Lloyd) - Kundenvorträge von BMW, Mercedes-Benz, Trade Republic, E.ON u.v.v.v.m. - Interaktive Bereiche wie AI Escape Room und SaaS Builders' Showdown - Riesenrad, DJs und Networking Reception mit Live-Musik Links: - ‼️ AWS Summit Hamburg Registrierung ‼️ - AWS Summit Hamburg Agenda - AWS Housewarming Anmeldung - AWS for Software and Technology Stage Programm - AWS x OMR Reviews SaaS Leaders Breakfast - AWS Community DACH Über die Gäste: - Markus Ostertag ist Chief AWS Technologist bei ADESO und seit 2016 AWS Hero - Thorsten Höger ist selbstständiger Cloud-Berater für regulierte Kunden und seit 2017 AWS Hero Hosts: - Jana Kupfer (AWS) - Michelle Mei-Li Pfister (AWS) AWS Cloud Horizonte ist der offizielle deutschsprachige AWS Podcast.

What happens when access to advanced AI models is no longer the real differentiator, and the true advantage lies in how businesses leverage their own data? At the AWS Summit in London, I sat down with Rahul Pathak, Vice President of Data and AI Go-to-Market at AWS, to unpack this question and explore how organisations are moving beyond experimentation and into large-scale generative AI adoption. Recorded live on the show floor, this conversation explores how AWS is supporting customers at every layer of their AI journey. From custom silicon innovations like Trainium and Inferentia to scalable services like Bedrock, Q Developer, and SageMaker, AWS is giving businesses the infrastructure, tools, and flexibility to innovate with confidence. Rahul shared how leading organisations such as BT Group, SAP, and Lonely Planet are already applying these tools to reduce costs, speed up development cycles, and deliver tailored experiences that would have been unthinkable just a few years ago. A key theme that emerged in our discussion is that data, not just models, is the true foundation of effective AI. Rahul explained why unifying data across silos is critical and how AWS is helping companies create more intelligent applications by connecting what they uniquely know about their business to powerful AI capabilities. We also addressed the operational realities of AI deployment. From moving proof-of-concept projects into production to meeting the growing demand for responsible AI, the challenges are shifting. Organisations are now focused on trust, security, transparency, and measurable value. If you're leading digital transformation and wondering how to scale AI solutions that deliver on business outcomes, this episode provides practical insight from someone at the center of the industry. How will your business stand out in a world where every company has access to AI models, but only a few know how to apply them with purpose?

Amid the buzz of the AWS Summit in London, I sat down with Eiso Kant, the CTO and Co-Founder of Poolside, to explore how his team is reshaping the future of software development through AI. This conversation was recorded right on the show floor inside a surprisingly sleek podcast booth at the ExCel, where Eiso unpacked what sets Poolside apart in a space many claim to be in but few truly build for. Poolside is not just another AI company. It's one of a handful globally that is actually training foundation models from the ground up. While most firms are chasing general-purpose AI, Poolside has chosen a different path. They focus solely on empowering software developers inside high-consequence environments, such as banking, defense, and major global retailers. These are systems where precision and security matter, and where AI can drive measurable gains in productivity and reliability. What struck me during this discussion is how deliberately Poolside has been built for enterprise use from the start. Their model doesn't just live in the cloud. It is designed to live within the customer's own infrastructure, whether that's in their private AWS environment or even on-prem. This focus on data privacy, security, and customizability is helping Poolside win trust where it counts most. And the partnership with AWS takes this a step further, making it easier for enterprises to deploy Poolside's AI within existing cloud frameworks while meeting strict governance requirements. Eiso explained that Poolside doesn't just throw larger models at problems. Instead, they use reinforcement learning from code execution, training on millions of real codebases and test suites. This approach helps the model go beyond autocomplete and simple bug fixes. It's now stepping into longer, more complex tasks, nudging us closer to a future where AI could serve as a true teammate for software engineers. We also tackled one of the most important discussions in AI today: whether this is a cost-cutting tool or a productivity multiplier. Eiso didn't dodge the nuance. While some may use AI to reduce headcount, Poolside's focus is on enabling companies to build more, ship faster, and innovate with greater speed. That shift is not about replacing people. It's about creating leverage for development teams under pressure to deliver more in less time. If you're a CTO, CIO, or engineering leader, this episode is packed with practical insights. Whether it's understanding the ROI of AI-assisted development, the importance of retaining control of your own models, or how to think about enterprise-grade security in the age of LLMs, there's a lot here to digest. So how should we really be thinking about AI in the enterprise? Is it a partner, a tool, or the beginning of an entirely new workforce paradigm? Tune in to find out.

In dieser Episode von Cloud Horizonte sprechen Oliver und Pavel auf dem AWS Summit in Berlin mit Frank Alsmann (VHV Versicherung) und Philipp Richter (Public Cloud Group) über die Cloud-Transformation der VHV. Die VHV migriert Anwendungen von On-Premise in die AWS Cloud – mit Fokus auf Serverless-Technologien wie AWS Lambda. Wir diskutieren die Herausforderungen einer solchen Migration, von Sicherheit und Kostenoptimierung bis hin zur Modernisierung des einer konkreten Anwendung, des Tarifrechners. Es geht nicht nur um Technik: Die Cloud-Reise ist auch eine kulturelle Veränderung. Wie nimmt man Mitarbeitende mit? Welche Rolle spielen Schulungen, Compliance und FinOps? Erfahren Sie, warum Cloud nicht nur Effizienz bringt, sondern auch neue Denkweisen in Unternehmen etabliert. Wir sprechen über Lessons Learned, den langfristigen Wandel in der IT und wie Unternehmen wie die VHV sich für die Zukunft aufstellen.

In der neuesten Episode des AWS Cloud Horizonte Podcasts erleben Sie ein faszinierendes Gespräch zwischen Host Heinrich Nikonow und Siggi Schallenmüller, Head of Digital Innovation EMEA bei Amazon, live vom AWS Summit in Berlin. Tauchen Sie ein in die Geheimnisse, die Amazon zu einem Vorreiter in der Innovationswelt gemacht haben. Erfahren Sie, wie die einzigartige „Day 1 Culture“ von Amazon nicht nur den Innovationsgeist des Unternehmens befeuert, sondern auch als Vorbild für die gesamte Branche dient. Siggi Schallenmüller erläutert, wie das Prinzip „Working Backwards“ den Entwicklungsprozess bei Amazon revolutioniert hat und warum diese Methoden für Unternehmen auf der ganzen Welt von unschätzbarem Wert sind. Highlights dieser Episode:

In der aktuellen Episode des AWS Cloud Horizonte Podcasts begrüßt unser Host Heinrich Nikonow den CTO und Mitbegründer von Sereact, Marc Tuscher, live vom AWS Summit in Berlin. Gemeinsam tauchen sie tief in die Welt der Logistik ein und diskutieren die neuesten Entwicklungen in den Bereichen Digitalisierung und Robotik. Erfahren Sie, wie Sereact, eine Ausgründung des Instituts für Steuerungstechnik der Werkzeugmaschinen und Fertigungseinrichtungen (ISW) der Universität Stuttgart, die Logistikbranche revolutioniert. Sereact entwickelt KI-gestützte Software für intelligente Robotik, die den Pick-and-Pack-Prozess in Warenlagern und Produktionsstätten optimiert.  Marc Tuscher erläutert, wie Sereacts innovative Lösungen in Zusammenarbeit mit AWS umgesetzt werden und wie die Integration der KI-Robotik-Lösung innerhalb eines einzigen Tages zu sofortigen Kosteneinsparungen von bis zu 77 % pro Kommissionierung führt. Ein weiteres Highlight: Die Pick-Software von Sereact ist flexibel und bewältigt mühelos wechselnde Produktsortimente. Hören Sie rein, um zu erfahren, wie Sereact und AWS gemeinsam die Zukunft der Logistik gestalten und welche Herausforderungen und Chancen die Digitalisierung und Robotik in diesem Bereich mit sich bringen.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 29/06 a 12/07.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 29/06 a 12/07.

We are live for episode 29 of the Hot Desk Podcast with Melody Brue and Robert Kramer.   IBM at Wimbledon  https://www.linkedin.com/posts/melodybrue_ibm-serves-new-generative-ai-features-at-activity-7215655729595080704-QxN7?utm_source=share&utm_medium=member_desktop https://www.ibm.com/sports/wimbledon   AWS Summit 2024 NYC AWS Democratizing Data and AI https://aws.amazon.com/blogs/aws/top-announcements-of-the-aws-summit-in-new-york-2024-2/ https://aws.amazon.com/blogs/machine-learning/empowering-everyone-with-genai-to-rapidly-build-customize-and-deploy-apps-securely-highlights-from-the-aws-new-york-summit https://www2.deloitte.com/us/en/pages/about-deloitte/articles/press-releases/deloitte-launches-gen-ai-accelerator-program-with-aws.html#   Avaya CEO Transition  https://www.avaya.com/en/about-avaya/newsroom/pr-us-240710/    Zoho Apptics https://www.zoho.com/blog/apptics/introducing-zoho-apptics-application-analytics-solution.html    What's coming up?  Robert Mel   Disclaimer: This show is for information and entertainment purposes only. While we will discuss publicly traded companies on this show. The contents of this show should not be taken as investment advice.

***Please note this episode contains background noise and distortion from the AWS Summit *** Mark Tate and Luther King are reporting live from day two of the AWS Summit in Washington, DC, sharing the excitement and opportunities of the event, including sessions on cloud security and serverless computing. They highlight the evolution of cloud technology and its impact, emphasizing the importance of adapting to innovations like generative AI. The hosts also discuss the ongoing Olympic track and field events, celebrating athletes like Corey Richardson and Noah Lyles. They shift gears to address mental health awareness and PTSD, stressing the importance of support and resources for veterans. They encourage those struggling to seek help, highlighting the significance of addressing mental health stigma in the military. Luther and Mark also cover health and wellness, discussing the benefits of fitness and nutrition in coping with stress.

***Please note this episode contains some background noise and distortion from the AWS Summit in the background*** In this episode, hosts Luther King and Mark Tate report live from the AWS Summit in Washington, DC. They kick off the podcast by discussing AWS's commitment to providing free AI skills training for millions globally and the excitement surrounding the summit. Both hosts share their experiences from various sessions, highlighting the keynote speech on generative AI and a surprising presentation by a representative from the Central Intelligence Agency on the long-term use of AI in their operations. They emphasize the importance of adapting and learning about new technologies to stay relevant. The hosts delve into Mark Tate's recently published book, "Sprint to the Mountaintop," discussing its core themes and offering listeners a deeper look into its contents, exploring key chapters. The book can be found on Amazon at https://a.co/d/076xyJz3

Willkommen zur neuesten Episode von Cloud Horizonte, dem offiziellen deutschen AWS Podcast! In dieser spannenden Folge tauchen wir tief in die Welt der IT-Talente ein und beleuchten, welche Fähigkeiten und Profile in der Zukunft gefragt sein werden. Unsere Gastgeber sind Heinrich Nikonow von AWS und Basti Meissner, CEO von Nijodex. Themen dieser Folge: - Zukunft der IT-Talente: Welche Fähigkeiten und Qualifikationen werden zukünftig in der IT-Branche besonders gefragt sein? - Team Staffing: Wie stellt man das ideale Team für IT-Projekte zusammen? Welche Rollen und Kompetenzen sind unerlässlich? - Amazon's Hiring-Prozess: Ein exklusiver Einblick in den Einstellungsprozess bei Amazon – von der Bewerbung bis zum Interview. - Mitarbeiterbindung: Strategien und Best Practices, um sicherzustellen, dass die besten Talente langfristig im Team bleiben. Diese Episode wurde live auf dem AWS Summit in Berlin aufgenommen und bietet wertvolle Einblicke sowohl für Führungskräfte als auch für IT-Profis, die sich für effektives Teammanagement und die zukünftigen Anforderungen der Branche interessieren. Hören Sie jetzt rein und erfahren Sie, wie Sie Ihr Team optimal aufstellen und die besten Talente der IT-Branche für sich gewinnen und halten können!

In an interview at the AWS Summit, Pacific Northwest National Laboratory (PNNL) Chief Scientist for AI Court Corley and Director of the Center for Cloud Computing Scott Godwin discussed their efforts to enhance research through AI and cloud computing. They emphasized providing foundational compute capabilities and access to cloud services for Energy Department researchers addressing critical issues like sustainable energy and national security. They also highlighted the rapid evolution of AI tools and the importance of data management across different domains. Both stressed the need for cultural adaptation within the scientific community to embrace new technologies while also ensuring they enable reliable and validated results.

The Air Force Sustainment Center is modernizing supply chain and logistics operations with cloud. Having an efficiently running supply chain and manufacturing operations for supplies and weapons systems is critical to national security. Leaders from the center, John York and Josh Thompson, highlight at AWS Summit some of their priorities around cloud and hybrid cloud. They also detail how developments in the Technology Hosting Environment for NextGen Automation (ATHENA) program is driving cost savings and improving insight into disparate sensors and data hubs for the service.

At AWS Summit in Washington DC, Nutanix Senior Director of US Federal Greg O'Connell discussed how agencies can ensure seamless data migration and app mobility, leverage generative AI and incorporate security. He equated today's rapid growth in modern applications to the impact of the browser, as the “killer app” of the internet era of the 1990s. With projections of 750 million new apps by 2026, he said agencies face challenges to incorporate more cloud and edge computing that would handle increased data processing and to develop more sophisticated security measures. Additionally, he addressed the impact of industry acquisitions on vendor dependency, stressing the importance of flexibility and freedom of choice in IT infrastructure to adapt to changing needs and avoid lock-in with a single provider.

Amazon Web Services (AWS) announced the AWS Public Sector Generative Artificial Intelligence (AI) Impact Initiative. The two-year, $50 million investment is designed to help public sector organisations - and those that directly support their technology needs - to accelerate innovation in support of critical missions using AWS generative AI services and infrastructure, such as Amazon Bedrock, Amazon Q, Amazon SageMaker, AWS HealthScribe, AWS Trainium, and AWS Inferentia. As part of this initiative, AWS is committing up to $50 million in AWS Promotional Credits, training, and technical expertise across generative AI projects. Credit issuance determinations will be based on a variety of factors, including but not limited to the customer's experience developing new technology solutions, the maturity of the project idea, evidence of future solution adoption, and the customer's breadth of generative AI skills. The Impact Initiative is open to new or existing AWS Worldwide Public Sector customers and partners from enterprises worldwide who are building generative AI solutions to help solve society's most pressing challenges. Across the public sector, leaders are seeking to leverage generative AI to become more efficient and agile. However, public sector organisations face several challenges such as optimising resources, adapting to changing needs, improving patient care, personalising the education experience, and strengthening security. To respond to these challenges, AWS is committed to helping public sector organisations unlock the potential of generative AI and other cloud-based technologies to positively impact society. This global initiative is open from June 26, 2024 through June 30, 2026. Benefits and resources will include: Tailored training: Check out the latest trainings to help you achieve your go-to-market goals and business needs. Generative AI Innovation Center expertise: Ideate, identify, and implement generative AI solutions securely with guidance from the Generative AI Innovation Center. Technical support: Learn from AWS technical experts and tutorials to optimize your generative AI build with Well-Architected Framework. Networking and free builder sessions: Access to registration for no-cost AWS Summit events around the world. Global thought leadership opportunities: Showcase your AWS Generative AI Impact Initiative success stories with AWS marketing efforts. The AWS Public Sector Generative AI Impact Initiative builds on our ongoing commitment to the safe, secure, and responsible development of AI technology. For example, AWS is a contributing partner to the National Science Foundation's National Artificial Intelligence Research Resource (NAIRR), which provides U.S.-based researchers and educators access to advanced computing, datasets, models, software, training, and user support for AI research. Additionally, Amazon is a member of the U.S. Artificial Intelligence Safety Institute Consortium, established by the National Institute of Standards and Technology, and is contributing $5 million to enable the development of tools and methodologies that organisations can use to evaluate the safety of their foundation models. AWS is also committed to supporting initiatives like the AI for Changemakers Accelerator program, led by Tech To The Rescue, which includes AWS Chief Technology Officer Werner Vogels' Now Go Build CTO Fellowship program. To learn more about the Impact Initiative, visit https://aws.amazon.com/generative-ai-impact-initiative. See more stories here.

The U.S. Army is prioritizing digital transformation and new software development policies when it historically took the service months, even years, to deploy new technology. At AWS Summit, Army Principal Deputy Assistant Secretary for Acquisition, Logistics and Technology Young Bang highlights the Army's efforts to modernize its acquisition and technology processes to field new tech more quickly. He also discusses the cybersecurity implications of new technology for a priority he said is to reduce the U.S.'s electronic footprint in the battlefield. He also emphasizes how partnerships with industry are key to this plan and the importance of data management and cybersecurity. This includes its data mesh to help it manage data more efficiently across tactical and enterprise environments.

In an interview at the AWS Summit, Department of Health and Human Services Chief Medical Officer Dr. Leith States discussed the significant impact of AI on health care. He also highlighted the critical priorities of ensuring continuity through the upcoming election cycle and managing resources effectively amid unpredictable funding scenarios. Plus, he shared his vision for health equity by design. States stressed the importance of ethical data practices, including patient empowerment, transparency and interoperability, facilitated by generative AI and machine learning. For technology providers, he advised engaging with and understanding the communities they serve to create effective solutions.

The Food and Drug Administration recently released a new acquisition strategy that aims to transform how the agency buys technology to impact multiple mission areas. In an interview with FDA Office of Enterprise Portfolio Management Director Joseph Montgomery at AWS Summit, he highlights the importance of this strategy to create a “one FDA” ecosystem that prioritizes advanced technology and keeping pace with IT innovation. Montgomery also highlights how he's thinking about artificial intelligence, cybersecurity and cloud to impact financial operations (FinOps) and ultimately support FDA's modernization goals.

Join us as we dive into an inspiring conversation from the AWS Summit in Stockholm with Matt Houghton, an AWS Ambassador and Community Builder. Matt shares insights on his team at CDL and their monumental achievement of migrating 600 Oracle databases to RDS Postgres.

En esta entrega, nos sumergimos en el mundo del aprendizaje por refuerzo con José Coronel, Executive Director en JPMorgan Chase y experto en DeepRacer Pro. Descubre los secretos detrás del éxito de los corredores Pro y recibe consejos que te ayuden a potenciar tu función de recompensa en DeepRacer.Tabla de Contenidos00:57 - Comienzan las temporadas de AWS Summit!02:19 - Conociendo a nuestro invitado José Coronel03:12 - Descifrando DeepRacer: ¿Qué es?06:28 - Del Mundo Virtual al Real: Una travesía fascinante11:25 - Habilidades Clave para el Éxito en DeepRacer12:34 - Acelerando con Estilo: El arte del drifting13:57 - ¿Velocidad o Distancia? ¿Qué importa más?14:13 - Consejo: Optimizando la ruta para la máxima eficiencia15:03 - Consejo: Dominando el arte de frenar17:24 - Exploración vs. Explotación23:26 - Navegando los Hiperparámetros: La clave del rendimiento25:07 - La Función de Recompensa: El corazón de DeepRacer36:03 - Manteniendo la Motivación: Secretos para el éxito a largo plazo41:04 - DeepRacer como puerta de entrada a la Observabilidad o SRE41:50 - Consejos para Alcanzar el Estrellato en DeepRacer45:03 - ¿Por dónde empezar? Guía para principiantes47:20 - Trucos y Tips: Mejorando tu juego rápidamente56:45 - Innovando con Creatividad: El toque personal en DeepRacer57:53 - Las Múltiples Motivaciones de DeepRacer58:40 - Aplicaciones Empresariales de DeepRacer: Más allá de las pistasAWS SummitsJunio 5, AWS Summit Madrid  (Link)Julio 18, AWS Summit Bogotá (Link) Agosto 7, AWS Summit México (Link) Agosto 15, AWS Summit Sao Paolo (Link) Redes de Nuestro invitadoLinkedInVideos mencionados en este episodioAWS Deepracer League F1 ProAmAWS Deepracer StrategiesAWS DeepRacer AvanzadoTraining an unbeatable AI in Trackmania (3 Years)ArtículosOptimizando modelos AWS DeepRacer para el mundo realAWS DeepRacer Developer GuideSeries Aprendiendo Deepracer (dev.to) Libro Introducción al aprendizaje por refuerzo, Jordi Torres ✉️ Si quieren escribirnos pueden hacerlo a este correo: podcast-aws-espanol@amazon.comPodes encontrar el podcast en este link: https://aws-espanol.buzzsprout.com/O en tu plataforma de podcast favoritaMás información y tutoriales en el canal de youtube de Charlas Técnicas☆☆ NUESTRAS REDES SOCIALES ☆☆

Julien Lepine, directeur des Architectes Solutions AWS France, était l'invité de François Sorel dans Tech & Co, la quotidienne, ce lundi 25 mars. Il s'est penché sur l'événement AWS Summit, une édition qui sera sous le signe de l'intelligence artificielle, sur BFM Business. Retrouvez l'émission du lundi au jeudi et réécoutez la en podcast.

If you have an interest in exploring Machine Learning (who doesn't?) but have no Data Science experience, you can check this course out. We attended the AWS Summit recently, and learned a bit about ML related AWS Services, and we'll share our knowledge with you. As programmers, a lot of us lack Data Science experience. Given that, how do we leverage our existing skills to build ML systems? Purchase course in one of 2 ways: 1. Go to https://getsnowpal.com, and purchase it on the Web 2. On your phone:     (i) If you are an iPhone user, go to http://ios.snowpal.com, and watch the course on the go.     (ii). If you are an Android user, go to http://android.snowpal.com.

En este episodio conversamos sobre las 7 innovaciones de Inteligencia Artificial Generativa anunciadas en el reciente Summit de AWS en New York en su edición 2023. Les compartimos las ideas principales del keynote de Swami Sivasubramanian, VP de Bases de datos, Analítica y Machine Learning en AWS. Material Adicional: https://www.aboutamazon.com/news/aws/aws-summit-new-york-generative-ai

Welcome episode 221 of The Cloud Pod podcast - where the forecast is always cloudy! This week your hosts, Justin, Jonathan, Ryan, and Matthew look at some of the announcements from AWS Summit, as well as try to predict the future - probably incorrectly - about what's in store at Next 2023. Plus, we talk more about the storm attack, SFTP connectors (and no, that isn't how you get to the Moscone Center for Next) Llama 2, Google Cloud Deploy and more!  Titles we almost went with this week: Now You Too Can Get Ignored by Google Support via Mobile App The Tech Sector Apparently Believes Multi-Cloud is Great… We Hate You All.  The cloud pod now wants all your HIPAA Data The Meta Llama is Spreading Everywhere The Cloud Pod Recursively Deploys Deploy A big thanks to this week's sponsor: Foghorn Consulting, provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

This week, we discuss New Relic going private, Dell buying Moogsoft and digital transformation comes to Border Control. Plus, ideas for a last minute family vacation. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=6M31eD5nVy0) 426 (https://www.youtube.com/watch?v=6M31eD5nVy0) Runner-up Titles The Paris economy is all croissants. The Euphoria of the Buffet All that firing people gave us a soft landing. Is it going to be New Logic, or SumoRelic? You drive a hard bargain, now we're billionaires The tinfoil hat of complexity Just buy more backpacks Here in the United States, we have a lot of banks. Can Americans use it? Bigger numbers are smaller numbers. It's pretty easy to quarantine with Internet. Rundown More Monitoring, More Money Dell Technologies Announces Intent to Acquire Moogsoft (https://www.prnewswire.com/news-releases/dell-technologies-announces-intent-to-acquire-moogsoft-301881557.html) What the New Relic Sale Means for SaaS by @ttunguz (https://www.tomtunguz.com/newr_acquisition/) Exclusive: Francisco Partners, TPG end talks to buy New Relic (https://www.reuters.com/markets/deals/francisco-partners-tpg-end-talks-buy-new-relic-sources-2023-05-26/?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axiosprorata&stream=top) Francisco Partners & TPG to take New Relic private in $6 billion all-cash deal (https://www.cnbc.com/2023/07/31/francisco-partners-tpg-to-take-new-relic-private-in-6-billion-deal.html) Inside the $6.5 billion buyout of New Relic (https://www.axios.com/2023/08/01/inside-the-65-billion-buyout-of-new-relic) Government IT Federal Reserve announces that its new system for instant payments, the FedNow® Service, is now live (https://www.federalreserve.gov/newsevents/pressreleases/other20230720a.htm) CBP Goes Paperless with Global Entry (https://www.cbp.gov/newsroom/local-media-release/cbp-goes-paperless-global-entry) Mexico Phasing Out Use of Paper Visitor Permits (FMM) (https://www.mexperience.com/mexico-begins-to-phase-out-paper-versions-of-the-fmm/#:~:text=Mexico%27s%20paper%20FMM%20forms%20being,Mexico%20no%20longer%20use%20them) New requirements coming in 2024 for Americans traveling to Europe (https://abcnews.go.com/GMA/Travel/new-requirements-coming-2024-americans-traveling-europe/story?id=101546203) Passport Palooza (https://markcathcart.com/2023/07/24/passport-palooza/) Relevant to your Interests Broadcom's $61 billion VMware deal wins conditional EU antitrust OK (https://www.reuters.com/markets/deals/broadcom-wins-conditional-eu-antitrust-approval-buy-vmware-2023-07-12/) Broadcom claims VMware's strategy isn't succeeding (https://www.theregister.com/2023/07/14/broadcom_vmware_cma_response/) Moderation actions (https://docs.joinmastodon.org/admin/moderation/) Shopify's anti-meeting crusade is failing and it's taken to shaming employees instead: 'Most of the modern work environment is broken' (https://fortune.com/2023/07/12/remote-work-zoom-meeting-shopify-cost-calculator-modern-work-broken/) Investors and business owners for 3x more likely to invest after reading a GPT-4 pitch deck (https://twitter.com/mrhinkle/status/1670431487621996547?s=20) 3 tax prep firms shared 'extraordinarily sensitive' data about taxpayers with Meta (https://apnews.com/article/irs-taxpayer-tax-preparation-meta-congress-9315cfca7a0942ab89f765d183fbf822) macOS Sonoma lets Chrome use passwords stored in iCloud (https://www.theverge.com/2023/7/13/23793532/apple-icloud-passwords-chrome-extension-mac-sonoma-beta) Passkeys in iOS 17: Watch a sneak peek at what's coming to 1Password for iOS | 1Password (https://blog.1password.com/apple-passkey-api-wwdc/?utm_medium=email&utm_source=beyond-passwords-newsletter-july&utm_campaign=passwordless&utm_ref=email-beyond-passwords-newsletter-july) Former Amazon Web Services data center leader Chris Vonderhaar joins Google Cloud (https://www.geekwire.com/2023/former-amazon-web-services-data-center-leader-chris-vonderhaar-joins-google-cloud/) AlmaLinux OS - Forever-Free Enterprise-Grade Operating System (https://almalinux.org/blog/future-of-almalinux/) Amazon Shares Jump 2% After Reporting Record Prime Day Sales (https://www.bloomberg.com/news/articles/2023-07-13/amazon-shares-jump-2-after-reporting-record-prime-day-sales) Threads Is About to Make All the Money That Twitter Isn't (https://slate.com/technology/2023/07/meta-threads-advertising-twitter-musk-zuckerberg.html) Mark Zuckerberg (@zuck) on Threads (https://www.threads.net/t/Cu0BgHESnwF/?igshid=MzRlODBiNWFlZA==) Jamin Ball (@jaminball) on Threads (https://www.threads.net/t/Cu3WuVGsWgy/?igshid=MzRlODBiNWFlZA==) Introducing NotebookLM (https://blog.google/technology/ai/notebooklm-google-ai/) Ford CEO explains why legacy car manufacturers cannot compete with Tesla in software (https://www.linkedin.com/feed/update/urn:li:activity:7084904611349757952?utm_source=share&utm_medium=member_desktop> linkedin.comlinkedin.com) Cloudflare as an AI play. An interview with CEO Matthew Prince. (https://redmonk.com/jgovernor/2023/07/17/cloudflare-as-an-ai-play-an-interview-with-ceo-matthew-prince/) This is huge: Llama-v2 is open source, with a license that authorizes commercial use! (http://ttps://twitter.com/ylecun/status/1681336284453781505?s=20) The Rise Of DIY In FinOps (https://www.forrester.com/blogs/the-rise-of-diy-in-finops/) Announcing Akita Has Joined Postman — Akita Software (https://www.akitasoftware.com/blog-posts/announcing-akita-has-joined-postman) Announcing the New Lightweight Postman API Client | Postman Blog (https://blog.postman.com/announcing-new-lightweight-postman-api-client/#:~:text=Starting%20May%2015%2C%202023%2C%20Scratch,calls%20through%20the%20Postman%20UI.) Does ‘Buy American' Policy Make Sense? The Answer Is Key for Your AI Portfolio Too (https://www.wsj.com/articles/does-buy-american-policy-make-sense-the-answer-is-key-for-your-ai-portfolio-too-562825af?st=zwct83dpy1hrssv) AlmaLinux says Red Hat source changes won't kill its RHEL-compatible distro (https://arstechnica.com/information-technology/2023/07/almalinux-says-red-hat-source-changes-wont-kill-its-rhel-compatible-distro/) Twitter becomes X (https://www.platformer.news/p/twitter-becomes-x?utm_source=substack&utm_medium=email) The problem with X? Meta, Microsoft, hundreds more own trademarks to new Twitter name (https://www.reuters.com/technology/problem-with-x-meta-microsoft-hundreds-more-own-trademarks-new-twitter-name-2023-07-25/) Meta Profit Is Up 16% to $7.8 Billion in Recent Quarter (https://www.nytimes.com/2023/07/26/technology/meta-earnings-second-quarter.html?smid=nytcore-ios-share&referringSource=articleShare) Top Announcements of the AWS Summit in New York, 2023 | Amazon Web Services (https://aws.amazon.com/blogs/aws/top-announcements-of-the-aws-summit-in-new-york-2023/?trk=d73defd9-9fc4-45cf-99f9-433b69146fbb&sc_channel=el) AWS Easily Beats Microsoft In $120B IaaS Cloud Market: Gartner (https://www.crn.com/news/cloud/aws-easily-beats-microsoft-in-120b-iaas-cloud-market-gartner) Russia Takes Its Ukraine Information War Into Video Games (https://www.nytimes.com/2023/07/30/technology/russia-propaganda-video-games.html) Breaking: AWS Begins Charging For Public IPv4 Addresses (https://www.lastweekinaws.com/blog/breaking-aws-begins-charging-for-public-ipv4-addresses/) The massive bug at the heart of the npm ecosystem (https://blog.vlt.sh/blog/the-massive-hole-in-the-npm-ecosystem) Tech Moves: Ex-Microsoft president joins Google Cloud as VP; iSpot hires research chief; and more (https://www.geekwire.com/2023/tech-moves-ex-microsoft-president-joins-google-cloud-as-vp-ispot-hires-research-chief-and-more/) A Day in the Life of a Senior Manager at Amazon (https://newsletter.pragmaticengineer.com/p/a-day-in-the-life-of-a-senior-manager) 7 generative AI innovations from AWS Summit New York 2023 (https://www.aboutamazon.com/news/aws/aws-summit-new-york-generative-ai) TikTok is adding text posts (https://www.theverge.com/2023/7/24/23805530/tiktok-text-posts-micro-blogging-twitter-threads) Prime Day 2023 Powered by AWS – All the Numbers (https://aws.amazon.com/blogs/aws/prime-day-2023-powered-by-aws-all-the-numbers/) AWS Launches Infrastructure Region in Israel (https://press.aboutamazon.com/2023/8/aws-launches-infrastructure-region-in-israel) AMD revenue falls 18% as PC market shows continued weakness (https://www.cnbc.com/2023/08/01/amd-earnings-report-q2-2023.html) From Docker to Dagger with Solomon Hykes (Changelog Interviews #550) (https://changelog.com/podcast/550) A New IT Automation Project? Moving Beyond Ansible And Keeping The Spirit (https://laserllama.substack.com/p/a-new-it-automation-project-moving) Google Docs can now automatically add line numbers (https://www.theverge.com/2023/7/24/23805822/google-docs-line-numbers-support) Q2 2023 is the largest quarter ever in the number of startup closures. (https://twitter.com/mahaniok/status/1682375196764717056) VCs Face an Existential Threat: There Are Too Many of Them (https://www.vice.com/en/article/4a3az9/venture-capital-vcs-existential-too-many) VC firm says their companies are good/leading, and you should invest in them too (https://twitter.com/Machiz/status/1680975185808171008) Nonsense FIGHTING (https://open.substack.com/pub/pmarca/p/fighting?r=2d4o&utm_medium=ios&utm_campaign=post) The Best Buy It for Life Backpack (Please Don't Call It Tactical) (Published 2020) (https://www.nytimes.com/wirecutter/reviews/buy-for-life-backpack/) Convicted felon gets DC contract to install car battery tech called impossible by experts (https://www.wusa9.com/article/news/investigations/lawrence-hardge-dc-battery-rejuvenation-contract/65-93a48463-e2fd-43e4-9a1b-9f727036ce0c) Americans spark backlash after claiming that Europeans ‘don't believe in water' (https://www.independent.co.uk/life-style/europe-travel-americans-water-bottles-b2377078.html) The Spongmonkeys, Fast Food's Most Unhinged Mascots, Are Back (https://www.eater.com/23797910/quiznos-spongmonkeys-unhinged-mascots-are-back) Here's why Elon Musk's rebranding of Twitter to 'X' is good, actually (https://techcrunch.com/2023/07/24/heres-why-elon-musks-rebranding-of-twitter-to-x-is-good-actually/) The First Room-Temperature Ambient-Pressure Superconductor (https://arxiv.org/abs/2307.12008) Conferences August 8th Kubernetes Community Day Australia (https://community.cncf.io/events/details/cncf-kcd-australia-presents-kubernetes-community-day-australia-2023/) in Sydney, Matt attending. August 21st to 24th SpringOne (https://springone.io/) & VMware Explore US (https://www.vmware.com/explore/us.html), in Las Vegas. Explore EU CFP is open. Sep 6th to 7th DevOpsDays Des Moines (https://devopsdays.org/events/2023-des-moines/welcome/), Coté speaking. Sep 18th to 19th SHIFT (https://shift.infobip.com/) in Zadar, Coté speaking. October 2-6, 2023, QCon San Francisco (https://qconsf.com/workshop/oct2023/open-source-kubernetes-cloud-cost-monitoring-opencost), Matt's doing a workshop October 6, 2023, KCD Texas 2023 (https://community.cncf.io/events/details/cncf-kcd-texas-presents-kcd-texas-2023/), CFP Closes: August 30, 2023 November 6-9, 2023, KubeCon NA (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/), SDT's a sponsor Jan 29, 2024 to Feb 1, 2024 That Conference Texas CFP Open 6/1 - 8/21 (https://that.us/call-for-counselors/tx/2024/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Full Circle (https://www.rottentomatoes.com/tv/full_circle_2023/s01) Matt: Amtrak Pacific Surfliner (https://www.amtrak.com/pacific-surfliner-train). Coté: A Waiter in Paris: Adventures in the Dark Heart of the City (https://amzn.to/47eBRws). Coté's Newsletter (https://cote.io/newsletter/) Photo Credits Header (https://unsplash.com/photos/ELf8M_YWRTY) Artwork (https://unsplash.com/photos/IOffoLkBmig)

Matt Wood is the VP of product at Amazon Web Services. He joins Big Technology Podcast live at the AWS Summit in New York City for a conversation about Amazon's plan to compete — and thrive — in the AI race. In this conversation, Wood describes Amazon's plan to support all AI models, not just one, and support builders via its computing infrastructure. Tune in for the most extensive comments from Amazon on its AI strategy to date. Stay tuned for the second half were we discuss ethics, company culture, and Jeff Bezos. You can read Alex's Substack story about the conversation here: Inside Amazon's Low Key Plan To Dominate AI --- Enjoying Big Technology Podcast? Please rate us five stars ⭐⭐⭐⭐⭐ in your podcast app of choice. For weekly updates on the show, sign up for the pod newsletter on LinkedIn: https://www.linkedin.com/newsletters/6901970121829801984/ Questions? Feedback? Write to: bigtechnologypodcast@gmail.com

In onze tweede en laatste aflevering vanaf de AWS Summit in Amsterdam, spreken we Luuk Figdor. Hij is Principal Sports Technology Advisor bij Amazon Web Services. Luuk helpt teams, clubs en media met het vertellen van verhalen via data, mensen en technologie. Want naast onze geliefde F1 werkt AWS ook samen met Nascar, de Bundesliga en de grote Amerikaanse bonden als NHL en NFL. Luuk deelt wat achtergrond informatie over de AWS Insights in de Formule 1 met ons en geeft een inkijkje in hoe ook de regie werkt met al die data. Maar bovenal hoe ook anderen sporten steeds meer data-gedreven raken. Voor atleet, team en club. Maar ook voor de fans. Luister nu de nieuwste aflevering van #F1SA, live vanaf de #AWSSummit! Geen uitzending missen? Abonneer je dan via je favoriete podcast app! Reageren? Dat kan het snelst via Twitter naar @F1SpoilerAlert (https://twitter.com/F1SpoilerAlert), @marjolijn (https://twitter.com/marjolijn) of @johanvoets (https://twitter.com/johanvoets) Wil je vorige afleveringen van F1 Spoiler Alert terugluisteren of je abonneren op onze show? Check dan https://www.f1spoileralert.nl Direct abonneren op onze feed? Kan ook natuurlijk: https://www.f1spoileralert.nl/rss Meer podcasts van Numrush luisteren? Bekijk het overzicht op http://numrush.nl/podcasts/ Special Guest: Luuk Figdor.

Querida tecnología, este año, por fin hemos podido volver a esos eventos técnicos que tanto nos gustan, algunos de ellos los habíamos echado en falta durante estos últimos años. Hoy te contaremos nuestras impresiones tras el T3chFest, la CommitConf, el Codemotion y el AWS Summit. Música: ⁠Aliaksei Yuknhevich - Background Ukulele⁠⁠ ⁠⁠Makesound - Ambient Motivational Inspirational⁠⁠

This week, George K and George A delve into the sales shenanigans they endured recently, and report from the frontlines of enterprise AI tech. In this episode:

When 10,000 people show up to talk about cloud computing, what topics do they cover? Today, we sit down with Jeffery Kratz, Vice President, of Worldwide Public Sector Channels & Alliances to find out. With a conference this large, there are hundreds of stories to tell.  To focus on the needs of the federal government, we will look at how improvement with Amazon partners can help federal agencies reach their goals. First, Amazon is targeting partners with Transformation Modules.  This means that a partner can do the face-to-face work of understanding the needs of a specific federal program.  From there, they can take advantage of one of these modules to deepen their understanding of how innovations from Amazon can help federal agencies reduce costs and improve security for that specific initiative. Second, sometimes, great ideas come out of startups. Approaching solving federal concerns from a different perspective, Amazon is launching an AWS GovTech Accelerator for Startups.  They take the modules to the next level. The program includes a one-month virtual and combines it with in-person opportunities for technical and business mentorship for GovTech startups.  It is one thing to have a great solution, quite another to be able to package it in a format that will adhere to stringent federal requirements. It looks like this program will bring innovation faster to the federal government. Third, we learn something new.  According to the well-respected consulting firm Euroconsult, we will see 17,000 new satellites by 2030. Today's ground station technology is based on outdated proprietary hardware and software. Amazon is leading the charge when it comes to making today's ground stations simple and scalable. Jeffery Kratz mentions the success of a company out of Japan called Infostellar with a new array of 26 ground stations serving the satellite and space community. This is especially important for the newly created Space Force as well as existing programs at the Department of Defense. Listen to the interview to catch up with how Amazon is responding to the dynamic needs of federal agencies. Follow John Gilroy on Twitter @RayGilray Follow John Gilroy on LinkedIn  https://www.linkedin.com/in/john-gilroy/ Listen to past episodes of Federal Tech Podcast  www.federaltechpodcast.com  

You will remember that we had previously spoken to Allyson Fryhoff of Amazon Web Services, who explained how AWS provides many tech tools to ...

(Part 1/2) I attended the AWS Summit in DC last week, and here are some of my thoughts. #snowpal #projectmanagement #developer #api Integrate with Snowpal. Subscribe to Snowpal API. Manage personal and professional projects on https://snowpal.com. Download iOS and Android App.

(Part 2/2) I attended the AWS Summit in DC last week, and here are some of my thoughts. #snowpal #projectmanagement #developer #api Integrate with Snowpal. Subscribe to Snowpal API. Manage personal and professional projects on https://snowpal.com. Download iOS and Android App.

Geen raceweekend, toch een verse F1SA! En wát voor een: tijdens de AWS Summit die recent in Amsterdam plaatvond, kregen we de unieke kans om voormalig Ferrari- en Williams-engineer Rob Smedley te interviewen. Smedley werd bekend als engineer van Felipe Massa, maar is sinds 2018 aangesloten bij de Formula 1 Group als data- en technisch consultant. Johan sprak Rob over de rol van data, cloud computing en de samenwerking met AWS binnen de Formule 1. Hoe de laatste technologische innovaties niet alleen teams helpen, maar ook de fans een betere ervaring moeten bieden en zelfs ondersteunen bij het ontwikkelen van de auto. Maar is al die data wel goed voor de beleving van de fans en de toekomst van de sport? Luister nu de nieuwste aflevering van #F1SA, live vanaf de #AWSSummit! Geen uitzending missen? Abonneer je dan via je favoriete podcast app! Reageren? Dat kan het snelst via Twitter naar @F1SpoilerAlert (https://twitter.com/F1SpoilerAlert), @marjolijn (https://twitter.com/marjolijn) of @johanvoets (https://twitter.com/johanvoets) Wil je vorige afleveringen van F1 Spoiler Alert terugluisteren of je abonneren op onze show? Check dan https://www.f1spoileralert.nl Direct abonneren op onze feed? Kan ook natuurlijk: https://www.f1spoileralert.nl/rss Meer podcasts van Numrush luisteren? Bekijk het overzicht op http://numrush.nl/podcasts/ Special Guest: Rob Smedley.

Capt. Erickson took the stage recently at the SWISH Data GIST 23 conference to share more about what his nascent office is doing to elevate data for transformation within the Coast Guard. Listen to what he had to say. Agencies across the federal government are looking to the cloud to elevate their next-gen computing capabilities. In this interview with Scoop News group's Wyatt Kash, Christian Hoff of AWS,highlights how NOAA, Customs and Border Protection and other agencies are using the cloud to advance their high-performance computing, data management and AI efforts — and what to look for at the upcoming AWS Summit in Washington, D.C. The Daily Scoop Podcast is available every Tuesday and Thursday afternoon. If you want to hear more of the latest from Washington, subscribe to The Daily Scoop Podcast on Apple Podcasts, Google Podcasts, Spotify and Stitcher. And if you like what you hear, please let us know in the comments.

Rijksoverheid heeft een overeenkomst bereikt met Amazon Web Services (AWS). Er is een 'framework agreement' getekend met tal van voorwaarden, onder meer qua privacy en beveiliging. Daardoor kunnen ministeries en andere overheids-departementen werken in de cloud met dat bedrijf. Dat is vandaag bekendgemaakt tijdens de AWS Summit in de RAI. Daar zijn zo'n zesduizend klanten, partners en geïnteresseerden in dergelijke toepassingen. En daar spraken we ook over dit nieuws met Merijn Schik, Senior Manager Public Policy Benelux bij Amazon Web Services. Verder in deze Tech Update: De Nederlandse overheid wil niet dat tech-bedrijven moeten gaan meebetalen aan ons telecom-netwerk. Dat blijkt nu weer uit een position paper in handen van Reuters, dat bedoeld is voor een meeting hierover met andere ministers die hierover gaan in de EU. Die komen hierover morgen bijeen in Luxemburg. "In tegenstelling tot de claims, heeft groei van het internetdata-verkeer nooit voor hogere kosten gezorgd bij telecom-bedrijven", klinkt het. See omnystudio.com/listener for privacy information.

AWS's US federal civilian and health director, Christian Hoff, highlights how NOAA, Customs and Border Protection and other agencies are using the cloud to advance their high-performance computing, data management and AI efforts — and what to look for at the upcoming AWS Summit in Washington, D.C. Host: Wyatt Kash, SVP, Content Strategy, Scoop News Group

We've been talking about AWS re:Invent over the last few episodes. But one thing that we haven't talked about is Serverless Espresso. Serverless Espresso is a pop up coffee shop that allows you to order coffee from your phone. In the Expo Hall at the AWS Summit, they have a Barista setup. And you walk up to a QR code with a screen in the background. So you scan the QR code and enter in your email address. And up pops a menu. If you select an americano, espresso or other type of coffee, it kicks off an event driven flow. It uses an event driven service under the hood and pops up in the screen as a number. And then the Barista takes the number makes your coffee and gives it to you. But what's happening in the background is a whole load of orchestration and choreography run events. And as they've been using it as a way to explain serverless event driven architecture. Event driven architecture can be hard for people to conceptually wrap their heads around. So making it real through ordering coffee. And showing how to tie a coffee process and an event driven coffee ordering system makes it real. It demystifies it a little bit and removes some of the thinking that event driven architecture sounds really hard. This makes it more approachable. It stitches together a lot of stuff that we've been advocating for, in a way that makes sense. By using AWS Step Functions, EventBridge, Lambda, API Gateway, S3, DynamoDB and Cognito. It brings to bare a lot of great technology that we are advocating for in a way that's practical and easily consumable. And the Serverless Espresso workshop is very good for walking you through the steps about why you're doing what you're doing. And how do you do that, set up rules and set up everything. It's a great way to get hands on with event driven architectures and serverless in a practical way. There are two myths in this space that AWS are trying to dispel. We first started talking about event driven architecture 13 years ago. We had the idea of doing something but back then it was really difficult, because we didn't have a lot of support. So we had hard problems to solve technically, because the foundations weren't there. That is the first myth of being a hard thing to do. The second myth is that people think of serverless as just writing code and functions. It's actually more like an event driven architecture. It's events firing off activity and not a call stack. So it's a lot easier to build full event of architecture than it would have been years ago. The technical challenge is not as bad as you think it is. What I like about Serverless Espresso is the simple interactions. You order, it goes to the barista who makes the coffee, and he gives it back to you. There's one interaction. Normally when ordering a coffee, you talk to a waiter, the waiter talks to the barista, and the barista talks to someone about milk etc. There can be six or seven people in that flow. It causes confusion. In a company, if a business process is owned by six or seven teams, even across two or three departments, it gets messy. If a single team builds for the customer directly and there's no one else, it's usually pretty clean. Because you can see everything needs to happen. It gets complicated if the business processes is split over several teams and departments. Serverless Espresso Lab is good, because the opinions are out there and you add on your bit, which is your business process flow. It goes back to our book The Value Flywheel Effect. And the first phase of the value flywheel which is clarity of purpose. Who is the customer and what is the business flow that we're trying to build? And let's have a good debate on how we are going to do that. When you get to the technical side, that opinion is already there. And you can focus on getting the orchestration correct. Because you know that a lot of that underlying stuff is pretty much solved apart from making it behave. Look at the Serverless Espresso Lab on workshop.serverlesscoffee.com. Or search for Serverless Espresso. And big kudos to the AWS Serverless Developer Advocate team. They're mostly on serverlessland.com. Thanks for listening. Serverless Craic from The Serverless Edge Check out our book The Value Flywheel Effect Follow us on Twitter @ServerlessEdge  

En este episodio les hablaremos del AWS Summit, uno de los eventos más importantes de AWS, que se llevara a cabo de manera presencial el 21 y 22 de septiembre en Ciudad de México y el 4 de octubre en Bogotá Material Adicional: https://aws.amazon.com/es/events/summits/mexico-city/

About MattMatt is a Sr. Architect in Belfast, an AWS DevTools Hero, Serverless Architect, Author and conference speaker. He is focused on creating the right environment for empowered teams to rapidly deliver business value in a well-architected, sustainable and serverless-first way.You can usually find him sharing reusable, well architected, serverless patterns over at cdkpatterns.com or behind the scenes bringing CDK Day to life.Links Referenced: Previous guest appearance: https://www.lastweekinaws.com/podcast/screaming-in-the-cloud/slinging-cdk-knowledge-with-matt-coulter/ The CDK Book: https://thecdkbook.com/ Twitter: https://twitter.com/NIDeveloper 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: Welcome to Screaming in the Cloud. I'm Corey Quinn. One of the best parts about, well I guess being me, is that I can hold opinions that are… well, I'm going to be polite and call them incendiary, and that's great because I usually like to back them in data. But what happens when things change? What happens when I learn new things?Well, do I hold on to that original opinion with two hands at a death grip or do I admit that I was wrong in my initial opinion about something? Let's find out. My guest today returns from earlier this year. Matt Coulter is a senior architect since he has been promoted at Liberty Mutual. Welcome back, and thanks for joining me.Matt: Yeah, thanks for inviting me back, especially to talk about this topic.Corey: Well, we spoke about it a fair bit at the beginning of the year. And if you're listening to this, and you haven't heard that show, it's not that necessary to go into; mostly it was me spouting uninformed opinions about the CDK—the Cloud Development Kit, for those who are unfamiliar—I think of it more or less as what if you could just structure your cloud resources using a programming language you claim to already know, but in practice, copy and paste from Stack Overflow like the rest of us? Matt, you probably have a better description of what the CDK is in practice.Matt: Yeah, so we like to say it's imperative code written in a declarative way, or declarative code written in an imperative way. Either way, it lets you write code that produces CloudFormation. So, it doesn't really matter what you write in your script; the point is, at the end of the day, you still have the CloudFormation template that comes out of it. So, the whole piece of it is that it's a developer experience, developer speed play, that if you're from a background that you're more used to writing a programming language than a YAML, you might actually enjoy using the CDK over writing straight CloudFormation or SAM.Corey: When I first kicked the tires on the CDK, my first initial obstacle—which I've struggled with in this industry for a bit—is that I'm just good enough of a programmer to get myself in trouble. Whenever I wind up having a problem that StackOverflow doesn't immediately shine a light on, my default solution is to resort to my weapon of choice, which is brute force. That sometimes works out, sometimes doesn't. And as I went through the CDK, a couple of times in service to a project that I'll explain shortly, I made a bunch of missteps with it. The first and most obvious one is that AWS claims publicly that it has support in a bunch of languages: .NET, Python, there's obviously TypeScript, there's Go support for it—I believe that went generally available—and I'm sure I'm missing one or two, I think? Aren't I?Matt: Yeah, it's: TypeScript, JavaScript, Python Java.Net, and Go. I think those are the currently supported languages.Corey: Java. That's the one that I keep forgetting. It's the block printing to the script that is basically Java cursive. The problem I run into, and this is true of most things in my experience, when a company says that we have deployed an SDK for all of the following languages, there is very clearly a first-class citizen language and then the rest that more or less drift along behind with varying degrees of fidelity. In my experience, when I tried it for the first time in Python, it was not a great experience for me.When I learned just enough JavaScript, and by extension TypeScript, to be dangerous, it worked a lot better. Or at least I could blame all the problems I ran into on my complete novice status when it comes to JavaScript and TypeScript at the time. Is that directionally aligned with what you've experienced, given that you work in a large company that uses this, and presumably, once you have more than, I don't know, two developers, you start to take on aspects of a polyglot shop no matter where you are, on some level?Matt: Yeah. So personally, I jump between Java, Python, and TypeScript whenever I'm writing projects. So, when it comes to the CDK, you'd assume I'd be using all three. I typically stick to TypeScript and that's just because personally, I've had the best experience using it. For anybody who doesn't know the way CDK works for all the languages, it's not that they have written a custom, like, SDK for each of these languages; it's a case of it uses a Node process underneath them and the language actually interacts with—it's like the compiled JavaScript version is basically what they all interact with.So, it means there are some limitations on what you can do in that language. I can't remember the full list, but it just means that it is native in all those languages, but there are certain features that you might be like, “Ah,” whereas, in TypeScript, you can just use all of TypeScript. And my first inclination was actually, I was using the Python one and I was having issues with some compiler errors and things that are just caused by that process. And it's something that talking in the cdk.dev Slack community—there is actually a very active—Corey: Which is wonderful, I will point out.Matt: [laugh]. Thank you. There is actually, like, an awesome Python community in there, but if you ask them, they would all ask for improvements to the language. So, personally if someone's new, I always recommend they start with TypeScript and then branch out as they learn the CDK so they can understand is this a me problem, or is this a problem caused by the implementation?Corey: From my perspective, I didn't do anything approaching that level of deep dive. I took a shortcut that I find has served me reasonably well in the course of my career, when I'm trying to do something in Python, and you pull up a tutorial—which I'm a big fan of reading experience reports, and blog posts, and here's how to get started—and they all have the same problem, which is step one, “Run npm install.” And that's “Hmm, you know, I don't recall that being a standard part of the Python tooling.” It's clearly designed and interpreted and contextualized through a lens of JavaScript. Let's remove that translation layer, let's remove any weird issues I'm going to have in that transpilation process, and just talk in the language it written in. Will this solve my problems? Oh, absolutely not, but it will remove a subset of them that I am certain to go blundering into like a small lost child trying to cross an eight-lane freeway.Matt: Yeah. I've heard a lot of people say the same thing. Because the CDK CLI is a Node process, you need it no matter what language you use. So, if they were distributing some kind of universal binary that just integrated with the languages, it would definitely solve a lot of people's issues with trying to combine languages at deploy time.Corey: One of the challenges that I've had as I go through the process of iterating on the project—but I guess I should probably describe it for those who have not been following along with my misadventures; I write blog posts about it from time to time because I need a toy problem to kick around sometimes because my consulting work is all advisory and I don't want to be a talking head-I have a Twitter client called lasttweetinaws.com. It's free; go and use it. It does all kinds of interesting things for authoring Twitter threads.And I wanted to deploy that to a bunch of different AWS regions, as it turns out, 20 or so at the moment. And that led to a lot of interesting projects and having to learn how to think about these things differently because no one sensible deploys an application simultaneously to what amounts to every AWS region, without canary testing, and having a phased rollout in the rest. But I'm reckless, and honestly, as said earlier, a bad programmer. So, that works out. And trying to find ways to make this all work and fit together led iteratively towards me discovering that the CDK was really kind of awesome for a lot of this.That said, there were definitely some fairly gnarly things I learned as I went through it, due in no small part to help I received from generous randos in the cdk.dev Slack team. And it's gotten to a point where it's working, and as an added bonus, I even mostly understand what he's doing, which is just kind of wild to me.Matt: It's one of those interesting things where because it's a programming language, you can use it out of the box the way it's designed to be used where you can just write your simple logic which generates your CloudFormation, or you can do whatever crazy logic you want to do on top of that to make your app work the way you want it to work. And providing you're not in a company like Liberty, where I'm going to do a code review, if no one's stopping you, you can do your crazy experiments. And if you understand that, it's good. But I do think something like the multi-region deploy, I mean, with CDK, if you'd have a construct, it takes in a variable that you can just say what the region is, so you can actually just write a for loop and pass it in, which does make things a lot easier than, I don't know, try to do it with a YAML, which you can pass in parameters, but you're going to get a lot more complicated a lot quicker.Corey: The approach that I took philosophically was I wrote everything in a region-agnostic way. And it would be instantiated and be told what region to run it in as an environment variable that CDK deploy was called. And then I just deploy 20 simultaneous stacks through GitHub Actions, which invoke custom runners that runs inside of a Lambda function. And that's just a relatively basic YAML file, thanks to the magic of GitHub Actions matrix jobs. So, it fires off 20 simultaneous processes and on every commit to the main branch, and then after about two-and-a-half minutes, it has been deployed globally everywhere and I get notified on anything that fails, which is always fun and exciting to learn those things.That has been, overall, just a really useful experiment and an experience because you're right, you could theoretically run this as a single CDK deploy and then wind up having an iterate through a list of regions. The challenge I have there is that unless I start getting into really convoluted asynchronous concurrency stuff, it feels like it'll just take forever. At two-and-a-half minutes a region times 20 regions, that's the better part of an hour on every deploy and no one's got that kind of patience. So, I wound up just parallelizing it a bit further up the stack. That said, I bet they are relatively straightforward ways, given the async is a big part of JavaScript, to do this simultaneously.Matt: One of the pieces of feedback I've seen about CDK is if you have multiple stacks in the same project, it'll deploy them one at a time. And that's just because it tries to understand the dependencies between the stacks and then it works out which one should go first. But a lot of people have said, “Well, I don't want that. If I have 20 stacks, I want all 20 to go at once the way you're saying.” And I have seen that people have been writing plugins to enable concurrent deploys with CDK out of the box. So, it may be something that it's not an out-of-the-box feature, but it might be something that you can pull in a community plug-in to actually make work.Corey: Most of my problems with it at this point are really problems with CloudFormation. CloudFormation does not support well, if at all, secure string parameters from the AWS Systems Manager parameter store, which is my default go-to for secret storage, and Secrets Manager is supported, but that also cost 40 cents a month per secret. And not for nothing, I don't really want to have all five secrets deployed to Secrets Manager in every region this thing is in. I don't really want to pay $20 a month for this basically free application, just to hold some secrets. So, I wound up talking to some folks in the Slack channel and what we came up with was, I have a centralized S3 bucket that has a JSON object that lives in there.It's only accessible from the deployment role, and it grabs that at deploy time and stuffs it into environment variables when it pushes these things out. That's the only stateful part of all of this. And it felt like that is, on some level, a pattern that a lot of people would benefit from if it had better native support. But the counterargument that if you're only deploying to one or two regions, then Secrets Manager is the right answer for a lot of this and it's not that big of a deal.Matt: Yeah. And it's another one of those things, if you're deploying in Liberty, we'll say, “Well, your secret is unencrypted at runtime, so you probably need a KMS key involved in that,” which as you know, the costs of KMS, it depends on if it's a personal solution or if it's something for, like, a Fortune 100 company. And if it's personal solution, I mean, what you're saying sounds great that it's IAM restricted in S3, and then that way only at deploy time can be read; it actually could be a custom construct that someone can build and publish out there to the construct library—or the construct hub, I should say.Corey: To be clear, the reason I'm okay with this, from a security perspective is one, this is in a dedicated AWS account. This is the only thing that lives in that account. And two, the only API credentials we're talking about are the application-specific credentials for this Twitter client when it winds up talking to the Twitter API. Basically, if you get access to these and are able to steal them and deploy somewhere else, you get no access to customer data, you get—or user data because this is not charge for anything—you get no access to things that have been sent out; all you get to do is submit tweets to Twitter and it'll have the string ‘Last Tweet in AWS' as your client, rather than whatever normal client you would use. It's not exactly what we'd call a high-value target because all the sensitive to a user data lives in local storage in their browser. It is fully stateless.Matt: Yeah, so this is what I mean. Like, it's the difference in what you're using your app for. Perfect case of, you can just go into the Twitter app and just withdraw those credentials and do it again if something happens, whereas as I say, if you're building it for Liberty, that it will not pass a lot of our Well-Architected reviews, just for that reason.Corey: If I were going to go and deploy this at a more, I guess, locked down environment, I would be tempted to find alternative approaches such as having it stored encrypted at rest via KMS in S3 is one option. So, is having global DynamoDB tables that wind up grabbing those things, even grabbing it at runtime if necessary. There are ways to make that credential more secure at rest. It's just, I look at this from a real-world perspective of what is the actual attack surface on this, and I have a really hard time just identifying anything that is going to be meaningful with regard to an exploit. If you're listening to this and have a lot of thoughts on that matter, please reach out I'm willing to learn and change my opinion on things.Matt: One thing I will say about the Dynamo approach you mentioned, I'm not sure everybody knows this, but inside the same Dynamo table, you can scope down a row. You can be, like, “This row and this field in this row can only be accessed from this one Lambda function.” So, there's a lot of really awesome security features inside DynamoDB that I don't think most people take advantage of, but they open up a lot of options for simplicity.Corey: Is that tied to the very recent announcement about Lambda getting SourceArn as a condition key? In other words, you can say, “This specific Lambda function,” as opposed to, “A Lambda in this account?” Like that was a relatively recent Advent that I haven't fully explored the nuances of.Matt: Yeah, like, that has opened a lot of doors. I mean, the Dynamo being able to be locked out in your row has been around for a while, but the new Lambda from SourceArn is awesome because, yeah, as you say, you can literally say this thing, as opposed to, you have to start going into tags, or you have to start going into something else to find it.Corey: So, I want to talk about something you just alluded to, which is the Well-Architected Framework. And initially, when it launched, it was a whole framework, and AWS made a lot of noise about it on keynote stages, as they are want to do. And then later, they created a quote-unquote, “Well-Architected Tool,” which let's be very direct, it's the checkbox survey form, at least the last time I looked at it. And they now have the six pillars of the Well-Architected Framework where they talk about things like security, cost, sustainability is the new pillar, I don't know, absorbency, or whatever the remainders are. I can't think of them off the top of my head. How does that map to your experience with the CDK?Matt: Yeah, so out of the box, the CDK from day one was designed to have sensible defaults. And that's why a lot of the things you deploy have opinions. I talked to a couple of the Heroes and they were like, “I wish it had less opinions.” But that's why whenever you deploy something, it's got a bunch of configuration already in there. For me, in the CDK, whenever I use constructs, or stacks, or deploying anything in the CDK, I always build it in a well-architected way.And that's such a loaded sentence whenever you say the word ‘well-architected,' that people go, “What do you mean?” And that's where I go through the six pillars. And in Liberty, we have a process, it used to be called SCORP because it was five pillars, but not SCORPS [laugh] because they added sustainability. But that's where for every stack, we'll go through it and we'll be like, “Okay, let's have the discussion.” And we will use the tool that you mentioned, I mean, the tool, as you say, it's a bunch of tick boxes with a text box, but the idea is we'll get in a room and as we build the starter patterns or these pieces of infrastructure that people are going to reuse, we'll run the well-architected review against the framework before anybody gets to generate it.And then we can say, out of the box, if you generate this thing, these are the pros and cons against the Well-Architected Framework of what you're getting. Because we can't make it a hundred percent bulletproof for your use case because we don't know it, but we can tell you out of the box, what it does. And then that way, you can keep building so they start off with something that is well documented how well architected it is, and then you can start having—it makes it a lot easier to have those conversations as they go forward. Because you just have to talk about the delta as they start adding their own code. Then you can and you go, “Okay, you've added these 20 lines. Let's talk about what they do.” And that's why I always think you can do a strong connection between infrastructure-as-code and well architected.Corey: As I look through the actual six pillars of the Well-Architected Framework: sustainability, cost optimization, performance, efficiency, reliability, security, and operational excellence, as I think through the nature of what this shitpost thread Twitter client is, I am reasonably confident across all of those pillars. I mean, first off, when it comes to the cost optimization pillar, please, don't come to my house and tell me how that works. Yeah, obnoxiously the security pillar is sort of the thing that winds up causing a problem for this because this is an account deployed by Control Tower. And when I was getting this all set up, my monthly cost for this thing was something like a dollar in charges and then another sixteen dollars for the AWS config rule evaluations on all of the deploys, which is… it just feels like a tax on going about your business, but fine, whatever. Cost and sustainability, from my perspective, also tend to be hand-in-glove when it comes to this stuff.When no one is using the client, it is not taking up any compute resources, it has no carbon footprint of which to speak, by my understanding, it's very hard to optimize this down further from a sustainability perspective without barging my way into the middle of an AWS negotiation with one of its power companies.Matt: So, for everyone listening, watch as we do a live well-architected review because—Corey: Oh yeah, I expect—Matt: —this is what they are. [laugh].Corey: You joke; we should do this on Twitter one of these days. I think would be a fantastic conversation. Or Twitch, or whatever the kids are using these days. Yeah.Matt: Yeah.Corey: And again, if so much of it, too, is thinking about the context. Security, you work for one of the world's largest insurance companies. I shitpost for a living. The relative access and consequences of screwing up the security on this are nowhere near equivalent. And I think that's something that often gets lost, per the perfect be the enemy of the good.Matt: Yeah that's why, unfortunately, the Well-Architected Tool is quite loose. So, that's why they have the Well-Architected Framework, which is, there's a white paper that just covers anything which is quite big, and then they wrote specific lenses for, like, serverless or other use cases that are shorter. And then when you do a well-architected review, it's like loose on, sort of like, how are you applying the principles of well-architected. And the conversation that we just had about security, so you would write that down in the box and be, like, “Okay, so I understand if anybody gets this credential, it means they can post this Last Tweet in AWS, and that's okay.”Corey: The client, not the Twitter account, to be clear.Matt: Yeah. So, that's okay. That's what you just mark down in the well-architected review. And then if we go to day one on the future, you can compare it and we can go, “Oh. Okay, so last time, you said this,” and you can go, “Well, actually, I decided to—” or you just keep it as a note.Corey: “We pivoted. We're a bank now.” Yeah.Matt: [laugh]. So, that's where—we do more than tweets now. We decided to do microtransactions through cryptocurrency over Twitter. I don't know but if you—Corey: And that ends this conversation. No no. [laugh].Matt: [laugh]. But yeah, so if something changes, that's what the well-architected reviews for. It's about facilitating the conversation between the architect and the engineer. That's all it is.Corey: This episode is sponsored in part by our friend EnterpriseDB. EnterpriseDB has been powering enterprise applications with PostgreSQL for 15 years. And now EnterpriseDB has you covered wherever you deploy PostgreSQL on-premises, private cloud, and they just announced a fully-managed service on AWS and Azure called BigAnimal, all one word. Don't leave managing your database to your cloud vendor because they're too busy launching another half-dozen managed databases to focus on any one of them that they didn't build themselves. Instead, work with the experts over at EnterpriseDB. They can save you time and money, they can even help you migrate legacy applications—including Oracle—to the cloud. To learn more, try BigAnimal for free. Go to biganimal.com/snark, and tell them Corey sent you.Corey: And the lens is also helpful in that this is a serverless application. So, we're going to view it through that lens, which is great because the original version of the Well-Architected Tool is, “Oh, you built this thing entirely in Lambda? Have you bought some reserved instances for it?” And it's, yeah, why do I feel like I have to explain to AWS how their own systems work? This makes it a lot more streamlined and talks about this, though, it still does struggle with the concept of—in my case—a stateless app. That is still something that I think is not the common path. Imagine that: my code is also non-traditional. Who knew?Matt: Who knew? The one thing that's good about it, if anybody doesn't know, they just updated the serverless lens about, I don't know, a week or two ago. So, they added in a bunch of more use cases. So, if you've read it six months ago, or even three months ago, go back and reread it because they spent a good year updating it.Corey: Thank you for telling me that. That will of course wind up in next week's issue of Last Week in AWS. You can go back and look at the archives and figure out what week record of this then. Good work. One thing that I have learned as well as of yesterday, as it turns out, before we wound up having this recording—obviously because yesterday generally tends to come before today, that is a universal truism—is it I had to do a bit of refactoring.Because what I learned when I was in New York live-tweeting the AWS Summit, is that the Route 53 latency record works based upon where your DNS server is. Yeah, that makes sense. I use Tailscale and wind up using my Pi-hole, which lives back in my house in San Francisco. Yeah, I was always getting us-west-1 from across the country. Cool.For those weird edge cases like me—because this is not the common case—how do I force a local region? Ah, I'll give it its own individual region prepend as a subdomain. Getting that to work with both the global lasttweetinaws.com domain as well as the subdomain on API Gateway through the CDK was not obvious on how to do it.Randall Hunt over at Caylent was awfully generous and came up with a proof-of-concept in about three minutes because he's Randall, and that was extraordinarily helpful. But a challenge I ran into was that the CDK deploy would fail because the way that CloudFormation was rendered in the way it was trying to do stuff, “Oh, that already has that domain affiliated in a different way.” I had to do a CDK destroy then a CDK deploy for each one. Now, not the end of the world, but it got me thinking, everything that I see around the CDK more or less distills down to either greenfield or a day one experience. That's great, but throw it all away and start over is often not what you get to do.And even though Amazon says it's always day one, those of us in, you know, real companies don't get to just treat everything as brand new and throw away everything older than 18 months. What is the day two experience looking like for you? Because you clearly have a legacy business. By legacy, I of course, use it in the condescending engineering term that means it makes actual money, rather than just telling really good stories to venture capitalists for 20 years.Matt: Yeah. We still have mainframes running that make a lot of money. So, I don't mock legacy at all.Corey: “What's that piece of crap do?” “Well, about $4 billion a year in revenue. Perhaps show some respect.” It's a common refrain.Matt: Yeah, exactly. So yeah, anyone listening, don't mock legacy because as Corey says, it is running the business. But for us when it comes to day two, it's something that I'm actually really passionate about this in general because it is really easy. Like I did it with CDK patterns, it's really easy to come out and be like, “Okay, we're going to create a bunch of starter patterns, or quickstarts”—or whatever flavor that you came up with—“And then you're going to deploy this thing, and we're going to have you in production and 30 seconds.” But even day one later that day—not even necessarily day two—it depends on who it was that deployed it and how long they've been using AWS.So, you hear these stories of people who deployed something to experiment, and they either forget to delete, it cost them a lot of money or they tried to change it and it breaks because they didn't understand what was in it. And this is where the community starts to diverge in their opinions on what AWS CDK should be. There's a lot of people who think that at the minute CDK, even if you create an abstraction in a construct, even if I create a construct and put it in the construct library that you get to use, it still unravels and deploys as part of your deploy. So, everything that's associated with it, you don't own and you technically need to understand that at some point because it might, in theory, break. Whereas there's a lot of people who think, “Okay, the CDK needs to go server side and an abstraction needs to stay an abstraction in the cloud. And then that way, if somebody is looking at a 20-line CDK construct or stack, then it stays 20 lines. It never unravels to something crazy underneath.”I mean, that's one pro tip thing. It'd be awesome if that could work. I'm not sure how the support for that would work from a—if you've got something running on the cloud, I'm pretty sure AWS [laugh] aren't going to jump on a call to support some construct that I deployed, so I'm not sure how that will work in the open-source sense. But what we're doing at Liberty is the other way. So, I mean, we famously have things like the software accelerator that lets you pick a pattern or create your pipelines and you're deployed, but now what we're doing is we're building a lot of telemetry and automated information around what you deployed so that way—and it's all based on Well-Architected, common theme. So, that way, what you can do is you can go into [crosstalk 00:26:07]—Corey: It's partially [unintelligible 00:26:07], and partially at a glance, figure out okay, are there some things that can be easily remediated as we basically shift that whole thing left?Matt: Yeah, so if you deploy something, and it should be good the second you deploy it, but then you start making changes. Because you're Corey, you just start adding some stuff and you deploy it. And if it's really bad, it won't deploy. Like, that's the Liberty setup. There's a bunch of rules that all go, “Okay, that's really bad. That'll cause damage to customers.”But there's a large gap between bad and good that people don't really understand the difference that can cost a lot of money or can cause a lot of grief for developers because they go down the wrong path. So, that's why what we're now building is, after you deploy, there's a dashboard that'll just come up and be like, “Hey, we've noticed that your Lambda function has too little memory. It's going to be slow. You're going to have bad cold starts.” Or you know, things like that.The knowledge that I have had the gain through hard fighting over the past couple of years putting it into automation, and that way, combined with the well-architected reviews, you actually get me sitting in a call going, “Okay, let's talk about what you're building,” that hopefully guides people the right way. But I still think there's so much more we can do for day two because even if you deploy the best solution today, six months from now, AWS are releasing ten new services that make it easier to do what you just did. So, someone also needs to build something that shows you the delta to get to the best. And that would involve AWS or somebody thinking cohesively, like, these are how we use our products. And I don't think there's a market for it as a third-party company, unfortunately, but I do think that's where we need to get to, that at day two somebody can give—the way we're trying to do for Liberty—advice, automated that says, “I see what you're doing, but it would be better if you did this instead.”Corey: Yeah, I definitely want to spend more time thinking about these things and analyzing how we wind up addressing them and how we think about them going forward. I learned a lot of these lessons over a decade ago. I was fairly deep into using Puppet, and came to the fair and balanced conclusion that Puppet was a steaming piece of crap. So, the solution was that I was one of the very early developers behind SaltStack, which was going to do everything right. And it was and it was awesome and it was glorious, right up until I saw an environment deployed by someone else who was not as familiar with the tool as I was, at which point I realized hell is other people's use cases.And the way that they contextualize these things, you craft a finely balanced torque wrench, it's a thing of beauty, and people complain about the crappy hammer. “You're holding it wrong. No, don't do it that way.” So, I have an awful lot of sympathy for people building platform-level tooling like this, where it works super well for the use case that they're in, but not necessarily… they're not necessarily aligned in other ways. It's a very hard nut to crack.Matt: Yeah. And like, even as you mentioned earlier, if you take one piece of AWS, for example, API Gateway—and I love the API Gateway team; if you're listening, don't hate on me—but there's, like, 47,000 different ways you can deploy an API Gateway. And the CDK has to cover all of those, it would be a lot easier if there was less ways that you could deploy the thing and then you can start crafting user experiences on a platform. But whenever you start thinking that every AWS component is kind of the same, like think of the amount of ways you're can deploy a Lambda function now, or think of the, like, containers. I'll not even go into [laugh] the different ways to run containers.If you're building a platform, either you support it all and then it sort of gets quite generic-y, or you're going to do, like, what serverless cloud are doing though, like Jeremy Daly is building this unique experience that's like, “Okay, the code is going to build the infrastructure, so just build a website, and we'll do it all behind it.” And I think they're really interesting because they're sort of opposites, in that one doesn't want to support everything, but should theoretically, for their slice of customers, be awesome, and then the other ones, like, “Well, let's see what you're going to do. Let's have a go at it and I should hopefully support it.”Corey: I think that there's so much that can be done on this. But before we wind up calling it an episode, I had one further question that I wanted to explore around the recent results of the community CDK survey that I believe is a quarterly event. And I read the analysis on this, and I talked about it briefly in the newsletter, but it talks about adoption and a few other aspects of it. And one of the big things it looks at is the number of people who are contributing to the CDK in an open-source context. Am I just thinking about this the wrong way when I think that, well, this is a tool that helps me build out cloud infrastructure; me having to contribute code to this thing at all is something of a bug, whereas yeah, I want this thing to work out super well—Docker is open-source, but you'll never see me contributing things to Docker ever, as a pull request, because it does, as it says on the tin; I don't have any problems that I'm aware of that, ooh, it should do this instead. I mean, I have opinions on that, but those aren't pull requests; those are complete, you know, shifts in product strategy, which it turns out is not quite done on GitHub.Matt: So, it's funny I, a while ago, was talking to a lad who was the person who came up with the idea for the CDK. And CDK is pretty much the open-source project for AWS if you look at what they have. And the thought behind it, it's meant to evolve into what people want and need. So yes, there is a product manager in AWS, and there's a team fully dedicated to building it, but the ultimate aspiration was always it should be bigger than AWS and it should be community-driven. Now personally, I'm not sure—like you just said it—what the incentive is, given that right now CDK only works with CloudFormation, which means that you are directly helping with an AWS tool, but it does give me hope for, like, their CDK for Terraform, and their CDK for Kubernetes, and there's other flavors based on the same technology as AWS CDK that potentially could have a thriving open-source community because they work across all the clouds. So, it might make more sense for people to jump in there.Corey: Yeah, I don't necessarily think that there's a strong value proposition as it stands today for the idea of the CDK becoming something that works across other cloud providers. I know it technically has the capability, but if I think that Python isn't quite a first-class experience, I don't even want to imagine what other providers are going to look like from that particular context.Matt: Yeah, and that's from what I understand, I haven't personally jumped into the CDK for Terraform and we didn't talk about it here, but in CDK, you get your different levels of construct. And is, like, a CloudFormation-level construct, so everything that's in there directly maps to a property in CloudFormation, and then L2 is AWS's opinion on safe defaults, and then L3 is when someone like me comes along and turns it into something that you may find useful. So, it's a pattern. As far as I know, CDK for Terraform is still on L1. They haven't got the rich collection—Corey: And L4 is just hiring you as a consultant—Matt: [laugh].Corey: —to come in fix my nonsense for me?Matt: [laugh]. That's it. L4 could be Pulumi recently announced that you can use AWS CDK constructs inside it. But I think it's one of those things where the constructs, if they can move across these different tools the way AWS CDK constructs now work inside Pulumi, and there's a beta version that works inside CDK for Terraform, then it may or may not make sense for people to contribute to this stuff because we're not building at a higher level. It's just the vision is hard for most people to get clear in their head because it needs articulated and told as a clear strategy.And then, you know, as you said, it is an AWS product strategy, so I'm not sure what you get back by contributing to the project, other than, like, Thorsten—I should say, so Thorsten who wrote the book with me, he is the number three contributor, I think, to the CDK. And that's just because he is such a big user of it that if he sees something that annoys him, he just comes in and tries to fix it. So, the benefit is, he gets to use the tool. But he is a super user, so I'm not sure, outside of super users, what the use case is.Corey: I really want to thank you for, I want to say spending as much time talking to me about this stuff as you have, but that doesn't really go far enough. Because so much of how I think about this invariably winds up linking back to things that you have done and have been advocating for in that community for such a long time. If it's not you personally, just, like, your fingerprints are all over this thing. So, it's one of those areas where the entire software developer ecosystem is really built on the shoulders of others who have done a lot of work that came before. Often you don't get any visibility of who those people are, so it's interesting whenever I get to talk to someone whose work I have directly built upon that I get to say thank you. So, thank you for this. I really do appreciate how much more straightforward a lot of this is than my previous approach of clicking in the console and then lying about it to provision infrastructure.Matt: Oh, no worries. Thank you for the thank you. I mean, at the end of the day, all of this stuff is just—it helps me as much as it helps everybody else, and we're all trying to do make everything quicker for ourselves, at the end of the day.Corey: If people want to learn more about what you're up to, where's the best place to find you these days? They can always take a job at Liberty; I hear good things about it.Matt: Yeah, we're always looking for people at Liberty, so come look up our careers. But Twitter is always the best place. So, I'm @NIDeveloper on Twitter. You should find me pretty quickly, or just type Matt Coulter into Google, you'll get me.Corey: I like it. It's always good when it's like, “Oh, I'm the top Google result for my own name.” On some level, that becomes an interesting thing. Some folks into it super well, John Smith has some challenges, but you know, most people are somewhere in the middle of that.Matt: I didn't used to be number one, but there's a guy called the Kangaroo Kid in Australia, who is, like, a stunt driver, who was number one, and [laugh] I always thought it was funny if people googled and got him and thought it was me. So, it's not anymore.Corey: Thank you again for, I guess, all that you do. And of course, taking the time to suffer my slings and arrows as I continue to revise my opinion of the CDK upward.Matt: No worries. Thank you for having me.Corey: Matt Coulter, senior architect at Liberty Mutual. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice and leave an angry comment as well that will not actually work because it has to be transpiled through a JavaScript engine first.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.

Hi all，請不要再上班時間玩遊戲。或是假藉參加研討會偷休假。 FB：https://www.facebook.com/%E5%B7%A5%E7%A8%8B%E5%B8%AB%E8%81%8A%E4%BB%80%E9%BA%BC-109229084578194 Youtube：https://www.youtube.com/channel/UCsRpKtsw50dUZG9Dv7NMvGQ

This episode is about AWS Well Architected and specifically about the Operational Excellence Pillar. Who should be using AWS WAF from startups to enterprises. What are the biggest challenges when performing an AWS WAF Review? If you're interested in learning more check out the AWS WAF Website. Are you looking to attend an AWS Summit or maybe AWS re:invent, more information here! Well-Architected Framework: https://aws.amazon.com/architecture/well-architected/ OE Pillar: https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html Operations Readiness Reviews Whitepaper: https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/operational-readiness-reviews-orrs.html DevOpsDays: https://devopsdays.org/ DevOps Meetups: https://www.meetup.com/find/?keywords=devops&source=EVENTS

This episode is about AWS Well Architected and specifically about the Operational Excellence Pillar. Who should be using AWS WAF from startups to enterprises. What are the biggest challenges when performing an AWS WAF Review? If you're interested in learning more check out the AWS WAF Website. Are you looking to attend an AWS Summit or maybe AWS re:invent, more information here! Well-Architected Framework: https://aws.amazon.com/architecture/well-architected/ OE Pillar: https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html Operations Readiness Reviews Whitepaper: https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/operational-readiness-reviews-orrs.html DevOpsDays: https://devopsdays.org/ DevOps Meetups: https://www.meetup.com/find/?keywords=devops&source=EVENTS

Kurt's administration hasn't being bad but they can do better — Juliet Bawuah, Founder of AWS Summit.

Erik Bradly from ETR joins theCUBE hosts Dave Vellante and John Furrier live from our coverage of AWS Summit New York 2022

With the AWS Summit Roadshow in full swing around the world, this special feature showcases highlights from the London event with five core themes to the fore: Technology, Skills, Culture, Passion and Sustainability. We are joined by: Tanuja Randery, Managing Director EMEA, Amazon Web Services discussing the fantastic AWS re/Start scheme, opening up new opportunities to a diversity of talent in technology, and other initiatives to support underrepresented groups. Rob Smedley, Technical Consultant, Formula 1 on how AWS and F1 work together closely for data driven sports innovation, plus a fantastic initiative from Rob, enabling easier entry into F1 and opening up inclusive opportunities for children of diverse backgrounds.Chris Wigley, CEO, Genomics England exploring the health challenges across the pandemic period, and how this is ultimately increased the rapid progression of clinical trials and innovation in this critical sector, empowered by AI, DataScience and technology partnership.Rob Salguero-Gomez, Associate Professor, University of Oxford on new research to advance sustainability, particularly around climate change, including an incredible project using drones for thermal imaging, helping to assist with environmental monitoring at scale. Malcolm McDermott, Consumer Brand Lead, Aqua Libra discussing embedding sustainability by design for sustainable water, a superb exemplar of scaling technology as a force for good.And we would love your thoughts on the episode too - thanks for listening! Sally, Tanuja, Rob, Chris, Rob, Malcolm and the #TTT TeamPlease join us on Twitter to continue the conversation! @techradiotttToday's guests on LinkedIn:Tanuja Randery: https://www.linkedin.com/in/tanuja-randeryRob Smedley: https://www.linkedin.com/in/rob-smedley/Chris Wigley: https://www.linkedin.com/in/wigleychrisRob-Salguero-Gomez:https://www.linkedin.com/in/rob-salguero-gomez-7572a0191 Malcolm McDermott:https://www.linkedin.com/in/malcolm-mcdermott-4065811a/And our host Prof. Sally Eaves on Twitter @sallyeavesAnd LinkedIn http://www.linkedin.com/in/sally-eaves

About MaishMaish Saidel-Keesing is a Senior Enterprise Developer Advocate @AWS working on containers and has been working in IT for the past 20 years and with a stronger focus on cloud and automation for the past 7.He has extensive experience with AWS Cloud technologies, DevOps and Agile practices and implementations, containers, Kubernetes, virtualization and, and a number of fun things he has done along the wayHe is constantly trying to bridge the gap between Developers and Operators to allow all of us provide a better service for our customers (and not wake up from pages in the middle of the night). He is an avid practitioner of dissolving silos - educating Ops how to code and explaining to Devs what the hell is OperationsLinks Referenced: @maishsk: https://twitter.com/maishsk duckbillgroup.com: https://duckbillgroup.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored by our friends at Fortinet. Fortinet's partnership with AWS is a better-together combination that ensures your workloads on AWS are protected by best-in-class security solutions powered by comprehensive threat intelligence and more than 20 years of cybersecurity experience. Integrations with key AWS services simplify security management, ensure full visibility across environments, and provide broad protection across your workloads and applications. Visit them at AWS re:Inforce to see the latest trends in cybersecurity on July 25-26 at the Boston Convention Center. Just go over to the Fortinet booth and tell them Corey Quinn sent you and watch for the flinch. My thanks again to my friends at Fortinet.Corey: Let's face it, on-call firefighting at 2am is stressful! So there's good news and there's bad news. The bad news is that you probably can't prevent incidents from happening, but the good news is that incident.io makes incidents less stressful and a lot more valuable. incident.io is a Slack-native incident management platform that allows you to automate incident processes, focus on fixing the issues and learn from incident insights to improve site reliability and fix your vulnerabilities. Try incident.io, recover faster and sleep more.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm a cloud economist at The Duckbill Group, and that was a fun thing for me to become because when you're starting to set out to solve a problem, well, what do you call yourself? I find that if you create a job title for yourself, well, no one knows quite how to categorize you and it leads to really interesting outcomes as a result. My guest today did something very similar. Maish Saidel-Keesing is an EntReloper, or Enterprise Developer Advocate, specifically for container services at AWS. Maish, thank you for joining me.Maish: Thank you for having me on the show, Corey. It's great to be here.Corey: So, how did you wind up taking a whole bunch of words such as enterprise, developer, advocate because I feel like the way you really express seniority at big companies, almost as a display of dominance, is to have additional words in your job title, which all those words are very enterprise-y, very business-y, and very serious. And in container services to boot, which is a somewhat interesting culture, just looking at the enterprise adoption of the pattern. And then at AWS, whose entire sense of humor can be distilled down into, “That's not funny.” You have the flexibility to refer to yourself as an EntReloper in public. I love it. Is it just something you started doing? Was there, like, 18 forms of approval you had to go through to do it? How did this happen? I love it.Maish: So, no. I didn't have to go through approval, of course. Same way, you didn't call yourself a cloud economist with anybody else's approval. But I got the idea mostly from you because I love your term of coining everybody who's in developer advocacy or developer relations as a DevReloper. And specifically, the reason that I coined the term of an EntReloper—and actually looked it up on Google to see if anybody had actually used that term before, and no they haven't—it's the fact of I came into the position on the premise of trying to bring the enterprise voice of the customer into developer advocacy.When we speak about developer advocates today, most of them are the people who are the small startups, developers who write the code, and we kind of forget that there is a whole big world outside of, besides small startups, which are these big, massive, behemoth sort of enterprise companies who kind of do things differently because they've been around for many, many years; they have many, many silos inside their organizations. And it's not the most simple thing to open up your laptop, and install whatever software you want on, because some of these people don't even give you admin rights on your laptop, or you're allowed to ssh out to a computer in the cloud because also the same thing: everything is blocked by corporate firewalls where you have to put in a ticket in order to get access to the outside world. I worked in companies like that when I was—before I moved to Amazon. So, I want to bring that perspective to the table on behalf of our customers.Corey: Bias is a very funny thing. I spent the overwhelming majority of my career in small environments like you describe. To me a big company is one that has 200 people there, and it turns out that there's a whole ‘nother sense of scale that goes beyond that. And there's, like, 18 different tiers beyond. But I still bias based upon my own experiences when I talk about how I do things and how I think about things to a certain persona that closely resembles my own experiences where, “Just install this thing as a tool and it'll be great,” ignoring entirely, the very realistic fact that you've got an entire universe out there of people who are not empowered to install things on their own laptop, for example.How is developer advocacy different within enterprises than in the common case of, “We're a startup. We're going to change the world with our amazing SaaS.” Great, maybe you will. Statistically, you won't. But enterprises have different concerns, different challenges, and absolutely a different sense of scale. How is the practice of advocacy different in those environments?Maish: So, I think the fact is, mostly working on standardization from the get-go that these big enterprises want things to work in a standard way where they can control it, they can monitor it, they can log everything, they can secure it mostly, of course, the most important thing. But it's also the fact that as a developer advocate, you don't always talk to developers within the enterprise. You also have to talk to the security team and to the network team and to the business itself or the C-level to understand. And as you also probably have found out as well in your job, you connect the people with inside the business one to another, these different groups, and get them talking to each other to make these decisions together. So, we act as kind of a bridge in between the people with inside their own company where they don't really talk to each other, or don't have the right connections, or the right conduit in order for them to start that conversation and make things better for themselves.Corey: On some level, my line about developer relations, developer advocacy, has generally taken the track of, “What does that mean? Well, it means you work in marketing, but they're scared to tell you that.” Do you view what you do as being within marketing, aligned with marketing, subtly different and I'm completely wrong, et cetera, et cetera? All positions are legitimate, by the way.Maish: So, I think, at the position that I'm currently in, which is a developer advocate but for the service team, is slightly different than a marketing developer advocate. The marketing developer advocate—and we have many of them which are amazing people and doing amazing work within AWS—their job is to teach everybody about the services and the capabilities available within AWS. That is also part of my job, but I would think that is the 40% of my job. I also go on stage, I go on podcasts like this, I present at conferences, I write blog posts. I also do the kind of marketing work as well.But the other 60% of my job as a service developer advocate is to seek out the feedback, or the signals, or the sentiment from our customers, and bring that back into the service teams, into the product management, into the engineering teams. And, as I said, sit as the enterprise customer in the chair in those meetings, to voice their concerns… their opinions, how they would like the products to go, how we can make the products better. So, the 60% is mostly what we call inbound, which is taking feedback from our customers back into the service teams directly in order to have some influence on the roadmap. And 40% is the outbound work, which we do, as I said, conferences, blog posts, and things like this.Corey: I have a perception. And I am thrilled to be corrected on this because it's not backed by data; it's backed by my own biases—and some people tend to conflate the two; I strive not to—that there's a—I think the term that I heard bandied around at one point was ‘the dark matter developers.' These are folks that primarily work in .NET or Java. They work for companies that are not themselves tech companies, but rather tech is a supporting function, usually in a central IT-style organization, that supports what the business actually does, and they generally are not visible to a lot of traditional developer advocacy approaches.They, by and large, don't go to conferences, they don't go on Twitter to yell at people about things, they commit the terrible sin—according to many startup folks—of daring to view the craft of writing software as this artistic thing, and they just view it as a job and a thing to make money for—filthy casuals—as opposed to this higher calling that's changing the world. Which I think is wild take. But there are a tremendous number of people out there who do fit the profile of they show up, they do their jobs working on this stuff, they don't go to conferences, they don't go out into the community, and they just do their job and go home. The end. Is that an accurate perception? Are there large swaths of folks like that in the industry, and if so, do they centralize or congregate more around enterprises than they do around smaller companies?Maish: I think that your perception is correct. Specifically, for my experience, when I worked, for example, my first two years before I was a developer advocate, I was an enterprise solutions architect which I worked with financial institutions, which are banks, which usually have software which are older than me, which are written in languages, which are older than I am. So, there are people which, as they say, they come there to—they do their job. They're not interested in looking at Twitter, or writing blog posts, or participating in any kind of thing which is outgoing. And they just, they're there to write the code. They go home at the end of the day.They also usually don't have pagers that page them in middle of the night because that's what you have operations teams for, not developers because they're completely different entities. So, I do think your perception might be correct, yes. There are people like that when you say, these dark matter people, dark matter developers.Corey: And I don't have any particular problem. I'm not here to cast shade on anything that they're doing, to be very clear.Maish: Not at all.Corey: Everyone makes different choices and that's great. I don't think necessarily everyone should have a job that is all-consuming, that eats them alive. I wish I didn't, some days. [laugh]. The challenge I have for you then is, as an EntReloper, how do you reach folks in positions like that? Or don't you?Maish: I think the way to reach those people is to firstly, expose them to technology, expose them to the capabilities that they can use in AWS in the cloud, specifically with my position in container services, and gain their trust because that's one of the LPs in Amazon itself: customer obsession. And we work consistently in order to—with our customers to gain their trust and help them along their journey, whatever it may be. If it might be the fact, okay, I only want to write software for nine to five and go home and do everything afterwards, which most normal people do without having to worry about work, or they still want to continue working and adopt the full model of you build it, you own it; manage everything in production on their own and go into the new world of modern software, which many enterprises, unfortunately, are not all the way there yet, but hopefully, they will get there sooner than later.Corey: There's a misguided perception in many corners that you have to be able to reach everyone at all times; wherever they are, you have to be able to go there. I don't think that's true. I think that showing up and badgering people who are just trying to get a job done into, “Hey, have you heard the good word of cloud?” It's like, evangelists knocking on your door at seven o'clock in the morning on a weekend and you're trying to sleep in because the kids are somewhere else for the week. Yeah, I might be projecting a little bit on that.I think that is the wrong direction to go. And I find that being able and willing to meet people where they are is key to success on this. I'm also a big believer in the idea that in any kind of developer advocacy role, regardless whether their targets are large, small, or in my case, patently ridiculous because my company is in fact ridiculous in some ways, you have to meet them where they are. There's no choice around that. Do you find that there are very different concerns that you have to wind up addressing with your audience versus a more, “Mainstream,” quote-unquote, developer advocacy role?Maish: For the enterprise audience, they need to, I would say, relate to what we're talking to. For an example, I gave a talk a couple of weeks ago on the AWS Summit here in Tel Aviv, of how to use App Runner. So, instead of explaining to the audiences how you use the console, this is what it does, you can deploy here, this is how the deployments work, blue, green, et cetera, et cetera, I made up an imaginary company and told the story of how the three people in the startup of this company would start working using App Runner in order to make the thing more relatable, something which people can hopefully remember and understand, okay, this is something which I would do as a startup, or this is what my project, which I'm doing or starting to work on, something I can use. So, to answer your question, in two words, tell stories instead of demo products.Corey: It feels like that's a… heavy lift, in many cases, because I guess it's also partially a perception issue on my part, where I'm looking at this across the board, where I see a company that has 5000 developers working there and, like, how do you wind up getting them to adopt cloud, or adopt new practices, or change anything? It feels like it's a Herculean, impossible task. But in practice, I feel like you don't try and do all of that at once. You start with small teams, you start with specific projects, and move on. Is that directionally accurate?Maish: Completely accurate. There's no way to move a huge mothership in one direction at one time. You have to do, as you say, start small, find the projects, which are going to bring value to the company or the business, and start small with those projects and those small teams, and continue that education within the organization and help the people with your teaching or introducing them to the cloud, to help others within inside their own organization. Make them, or enable them, or empower them to become leaders within their own organization. That's what I tried to do, at least.Corey: You and I have a somewhat similar background, which is weird given that we've just spent a fair bit of time talking about how different our upbringings were in tech at scales of companies and whatnot, but we're alike in that we are both fairly crusty, old operations-side folks, sysadmins—Maish: [laugh]. Yep.Corey: —grumpy people.Maish: Grumpy old sysadmins. Yeah, exactly.Corey: Exactly. Because do you ever notice there's never a happy one? Imagine that. And DevOps was always a meeting of the development and operations, meaning everyone's unhappy. And there's a school of thought that—like, I used to think that, “Oh, this is just what we call sysadmins once they want a better title and more money, but it's still the same job.”But then I started meeting a bunch of DevOps types who had come from the exact opposite of our background, where they were software developers and then they wound up having to learn not so much how the code stuff works the way that we did, but rather how systems work, how infrastructure works. Compare and contrast those for me. Who makes, I guess, the more successful DevOps engineer when you look at it through that lens?Maish: So, I might be crucified for this on the social media from a number of people from the other side of the fence, but I have the firm belief that the people who make the best DevOps engineers—and I hate that term—but people who move DevOps initiatives or changes or transformations with organization is actually the operations people because they usually have a broader perspective of what is going on around them besides writing code. Too many times in my career, I've been burned by DNS, by a network cable, by a power outage, by somebody making a misconfiguration in the Puppet module, or whatever it might have been, somebody wrote it to deploy to 15,000 machines, whatever it may be. These are things where developers, at least my perception of what developers have been doing up until now, don't really do that. In a previous organization I used to work for, the fact was, there was a very, very clear delineation about between the operations people, and the developers who wrote the software. We had very hard times getting them into rotations for on-call, we had very hard times educating them about the fact that not every single log line has to be written to the log because it doesn't interest anybody.But from developer perspective, of course, we need that log because we need to know what's happening in the end. But there are 15, different thousand… turtles all the way down, which have implications about the number of log lines which are written into a piece of software. So, I am very much of the belief that the people that make the best DevOps engineers—if we can use that term still today—are actually people which come from an operations background because it's easier to teach them how to write code or become a programmer than the other way round of teaching a developer how to become an operations person. So, the change or the move from one direction from operations to adding the additional toil of writing software is much easier to accomplish than the other way around, from a developer learning how to run infrastructure at scale.Corey: This episode is sponsored in part by our friend EnterpriseDB. EnterpriseDB has been powering enterprise applications with PostgreSQL for 15 years. And now EnterpriseDB has you covered wherever you deploy PostgreSQL on-premises, private cloud, and they just announced a fully-managed service on AWS and Azure called BigAnimal, all one word. Don't leave managing your database to your cloud vendor because they're too busy launching another half-dozen managed databases to focus on any one of them that they didn't build themselves. Instead, work with the experts over at EnterpriseDB. They can save you time and money, they can even help you migrate legacy applications—including Oracle—to the cloud. To learn more, try BigAnimal for free. Go to biganimal.com/snark, and tell them Corey sent you.Corey: I once believed much the same because—and it made sense coming from the background that I was in. Everyone intellectually knows that if you're having trouble with a piece of equipment, have you made sure that it's plugged in? Yes, everyone knows that intellectually. But there's something about having worked on a thing for three hours that wasn't working and only discover it wasn't plugged in, that really sears that lesson into your bones. The most confidence-inspiring thing you can ever hear from someone an operations role is, “Oh, I've seen this problem before. Here's how we fixed it.”It feels like there are no junior DevOps engineers, for lack of a better term. And for a long time, I believed that the upcoming and operational side of the world were in fact, the better DevOps types. And in the fullness of time, I think a lot of that—at least my position on it—was rooted in some level of insecurity because I didn't know how to write code and the thing that I saw happening was my job that I had done historically was eroding. Today, I don't know that it's possible to be in the operation space and not be at least basically conversant with how code works. There's a reason most of these job interviews turn into algorithm hazing.And my articulation of it was rooted, for me at least—at least in a small way—in a sense of defensiveness and wanting to validate the thing that I had done with my career that I defined myself by, I was under threat. And obviously, the thing that I do is the best thing because otherwise it's almost a tacit admission that I made poor career choices at some point. And I don't think that's true, either. But for me, at least psychologically, it was very much centered in that. And honestly, I found that the right answer for me was, in fact, neither of those two things because I have met a couple of people in my life that I would consider to be full-stack engineers.And there's a colloquialism these days, that means oh, you do front-end and back-end. Yeah. The people I'm thinking of did front-end, they did back-end, they did mobile software, they did C-level programming, they wrote their own freaking device drivers at one point. Like, they have done basically everything. And they were the sort of person you could throw any technical issue whatsoever at and get out of their way because it was going to get solved. Those people are, as it turns out, the best. Like, who does a better job developer or operations, folks? Yes. Specifically, both of those things together.Maish: Exactly.Corey: And I think that is a hard thing to talk about. I think that it's a hard—it's certainly a hard thing to find. It turns out that there's a reason that I only know two or three of those folks in the course of my entire career. They're out there, but they're really, really hard to track down.Maish: I completely agree.Corey: A challenge that I hear articulated in some cases—and while we're saying things that are going to get us yelled out on social media, let's go for the fences on this one—a concern that comes up when talking about enterprises moving to cloud is that they have a bunch of existing sysadmin types—while we're on the topic—and well, those people need to learn to work within cloud. And the reality is, in many cases that first, that's a whole new skill set that not everyone is going to be willing or able to pick up. For those who can they have just found that their market rate has effectively doubled. And that seems, on some level, to pose a significant challenge to companies undergoing this, and the larger the company, the more significant the challenge.Because it's my belief that you pay market rate for the talent you have whether you want to or not. And if companies don't increase compensation, these people will leave for things that double their income. And if they raise compensation internally, good for them, but that does have a massive drag on their budget that may not have been accounted for in a lot of the TCO analyses. How do you find that the companies you talk to wind up squaring that circle?Maish: I don't think I have a correct answer for that. I do completely agree—Corey: Oh, I'm not convinced there's a correct answer at all. I'm just trying [laugh] to figure out how to even think about it.Maish: I… have seen this as well in companies which I used to work for and companies that were customers that I have also worked with as part of my tenure in AWS. It's the fact of, when companies are trying to move to the cloud and they start upskilling their people, there's always the concern in the back of their mind of the fact, “Okay, I'm now training this person with new technology. I'm investing time, I'm investing money. And why would I do this if I know that, for example, as soon as I finish this, I'm going to have to just say, I have to pay them more because they can go somewhere else and get the same job with a better pay? So, why would we invest amount of time and resources into upscaling the people?”And these are questions which I have received and conversations which I've had with customers many times over the last two, three years. And the answer, from my perspective always, is the fact is because, number one, you're making the world a better place. Number two, you're making your employees feel more appreciated, giving them better knowledge. And if you're afraid of the fact of teaching somebody to become better is going to have negative effects on your organization then, unfortunately, you deserve to have that person leave and let them find a better job because you're not taking good care of your people. And it's sometimes hard for companies to hear that.Sometimes we get, “You know what? You're completely right.” Sometimes I don't agree with you because I need to compete there, get to the bottom line, and make sure that I stay within my budget or my TCO. But the most important thing is to have the conversation, let people hear different ideas, see how it can benefit them, not only by giving people more options to maybe leave the company, but it can actually make their whole organization a lot better in the long run.Corey: I think that you have to do right by people because reputations last a long time. Even at big companies it becomes a very slow thing to change and almost impossible to do in the short term. So, people tell stories when they feel wronged. That becomes a problem. I do want to pivot a little bit because you're not merely an EntReloper; you are an EntReloper specifically focusing on container services.Maish: Correct.Corey: Increasingly, I am viewing containers as what amounts to effectively a packaging format. That is the framework through which I am increasingly seeing. How are you seeing customers use containers? Is that directionally correct? Is it completely moonbat stuff compared to what you're seeing in the wild, or something else?Maish: I don't think it's a packaging format; I think it's more as an accelerator to enable the customers to develop in a more modern way with using twelve-factor apps with modern technology and not necessarily have their own huge, sticky, big monolith of whatever it might be, written in C# or whatever, or C++ whatever it may be, as they've been using up until now, but they now have the option and the technology and the background in order to split it up into smaller services and develop in the way that most of the modern world—or at least, the what we perceive as the modern world—is developing and creating applications today.Corey: I feel like on some level, containers were a radical change to how companies envisioned software. They definitely provide a path of modernizing things that were very tied to hardware previously. It let some companies even just leapfrog the virtualization migration that they'd been considering doing. But, on some level, I also feel like it runs counter to the ideas of DevOps, where you have development and operations working in partnership, where now it's like, welp, inside the container is a development thing and outside the container, ops problem now. It feels almost, on some level, like, it reinforces a wall. But in a lot of cultures and a lot of companies, that wall is there and there's no getting rid of it anytime soon. So, I confess that I'm conflicted on that.Maish: I think you might be right, and it depends, of course, on the company and the company culture, but what I think that companies need to do is understand that there will never be one hundred percent of people writing software that want to know one hundred percent of how the underlying infrastructure works. And the opposite direction as well: that there will never be people which maintain infrastructure and understand how computers and CPUs and memory buses and NUMA works on motherboards, that they don't need to know how to write the most beautiful enticing and wonderful software for programs, for the world. There's always going to have to be a compromise of who's going to be doing this or who's going to be doing that, and how comfortable they are with taking at least part of the responsibility of the other side into their own realm of what they should be doing. So, there's going to be a compromise on both sides, but there is some kind of divide today of separating, okay, you just write the Helm chart for your Kubernetes Pod spec, or your ECS task, or whatever task definition, whatever you would like. And don't worry about the things in the background because they're just going to magically happen in the end. But they do have to understand exactly what is happening at the background in the end because if something goes wrong, and of course, something will go wrong, eventually, one day somewhere, somehow, they're going to have to know how to take care of it.Corey: I really want to thank you for taking the time to speak with me today about, well, I guess a wide ranging variety of topics, some of which will absolutely inspire people to take to their feet—or at least their Twitter accounts—and tell us, “You know what your problem is?” And I honestly live for that. If you don't evoke that kind of reaction on some level, have you ever really had an opinion in the first place? So, I'm looking forward to that. If people want to learn more about you, your beliefs, call set beliefs misguided, et cetera, et cetera, where's the best place to find you?Maish: So, I'm on Twitter under @maishsk. I assume that will be in the [show notes 00:26:31]. I pontificate some time on technology, on cooking every now and again, on Friday before the end of the weekend, a little bit of politics, but you can find me @maishsk on Twitter. Or maishsk everywhere else social that's possible.Corey: Excellent. We will toss links to that, of course, in the [show notes 00:26:50]. Thank you so much for being so generous with your time. I appreciate it.Maish: Thank you very much, Corey. It was fun.Corey: Maish Saidel-Keesing, EntReloper of container services at AWS. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated it, please leave a five-star review on your podcast platform of choice along with an angry comment that your 5000 enterprise developer colleagues can all pile on.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.

Simon B went to the AWS summit in Milan and comes back with interesting data based stats about Formula 1 and shares his experience of the conference including the Gameday challenge for developers.Meanwhile Simon G has silently opened up his latest side project Ionic Blocks to the world and already made a sale without any official announcement,Links in this episode Ionic Blocks (super) early bird launch

In this episode of AWS Techchat, we started by talking about foundations, where we spoke about an overview of EventBridge and how it is different from CloudWatch Events. Then we talked about some of the features such as Archive and replay, Schema Registry, Global Endpoints and API Destinations And finally we dove into architecture patterns. Here we touched on the need to spend time modeling your logical architecture to get a good foundation for your event-driven architecture and explored event bus topologies and best practices. Speakers Shai Perednik - Global Tech Lead - Blockchain Cheryl Joseph - Solutions Architect, AWS Stephen Liedig - Principal SA - Serverless, AWS Resources *Amazon EventBridge resource policy samples* https://github.com/aws-samples/amazon-eventbridge-resource-policy-samples *AWS re:Invent 2020 session* Building event-driven applications with Amazon EventBridge (https://youtu.be/Wk0FoXTUEjo) *Introducing global endpoints for Amazon EventBridge* https://aws.amazon.com/blogs/compute/introducing-global-endpoints-for-amazon-eventbridge/ *ANZ Summit: Design event-driven integrations using Amazon EventBridge (Day 2)* * AWS Summit regisration (https://aws.amazon.com/events/summits/anz/) * Agenda at a glance (https://pages.awscloud.com/rs/112-TZM-766/images/AWS-Summit-ANZ-2022-Agenda.pdf) Blog Post * Building an event-driven application with Amazon EventBridge (https://aws.amazon.com/blogs/compute/building-an-event-driven-application-with-amazon-eventbridge/)

On The Cloud Pod this week, the team establishes that Justin may be immune to COVID. Plus all the latest from the AWS Summit, Azure Red Button team up on DDOS defense, and engines are revving in the great VMware showdown.  A big thanks to this week's sponsor, Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. This week's highlights

Entre deux conférence AWS Summit, les nouveautés AWS des deux dernières semaines qui ont attiré mon attention tournent autour des bases de données RDS, de Kafka, et encore une nouvelle famille d'instances EC2

Nos hemos ido a Madrid al AWS Summit, el evento anual en el que uno de los líderes mundiales de almacenamiento y computación en la nube presenta sus grandes novedades, las tendencias para los próximos años y nos cuenta por dónde irán los tiros digitales en el futuro.  Y este año ha sido muy especial, ya que España, en general, y Aragón, en particular, han sido protagonistas. Esto es, lo más destacado de un evento que nos ha maravillado a todos. Y sí, estamos en las nubes. Y cada vez más...

Entre deux conférence AWS Summit, les nouveautés AWS des deux dernières semaines qui ont attiré mon attention tournent autour des bases de données RDS, de Kafka, et encore une nouvelle famille d'instances EC2

Holy Sh*t - The performance 23andMe saw on the AWS cloud nearly seems like science-FICTION. Bob & Josh are live from AWS Summit and discuss our customer 23andMe's presentation on leveraging AWS for ultimate flexibility.

Om Shownotes ser konstiga ut (exempelvis om alla länkar saknas. Det ska finnas MASSOR med länkar) så finns de på webben här också: https://www.enlitenpoddomit.se    Avsnitt 364 spelades in den 26 April och eftersom att det finns djur som är allergiska mot människor ( https://www.popsci.com/science/article/2011-07/fyi-why-my-cat-so-sneezy/ ) så handlar dagens avsnitt om: INTRO: - Alla har haft en vecka... David har gjort en massa. Björn har rensat förråd, och fått lära mig MASSOR om iOT. Johan har åkt skidor, och gått med skidor, och gått upp på berg.    - BONUSLÄNK: https://www.ridestore.se/mag/randonee/   (Tack till RAMBUS som postade den i chatten)  FEEDBACK AND BACKLOG: - Vi nämnde en siffra för hur många som kör Windows 11 förra veckan. Nu har vi uppdateringar.    https://www.ghacks.net/2022/03/01/windows-11-usage-share-continued-to-rise-in-february-2022/    https://www.lansweeper.com/  ALLMÄNT NYTT - Musk köper Twitter för 427 miljarder kronor   https://www.theverge.com/2022/4/25/23028323/elon-musk-twitter-offer-buyout-hostile-takeover-ownership    https://www.cnbc.com/2022/04/25/twitter-accepts-elon-musks-buyout-deal.html    https://appleinsider.com/articles/22/04/26/the-elon-musk-twitter-takover-sparks-controversy-and-conspiracy  - Han har även sagt annat kul den senaste tiden   Musk says robot, aimed for 2023, will be worth more than Tesla's car business | TechCrunch   https://techcrunch.com/2022/04/20/musk-says-robot-aimed-for-2023-will-be-worth-more-than-teslas-car-business/   - AWS Summit?   https://www.crn.com/slide-shows/cloud/aws-summit-5-new-aurora-iot-twinmaker-and-glue-offerings  DISKUSSION: - Dealbreaker på telefon? (om vi tycker att vi hinner och den är kul)    https://swedroid.se/vad-ar-en-dealbreaker-for-dig-i-en-smartphone-2022/    - BONUSLÄNK: https://en.wikipedia.org/wiki/AppleTalk  LYSSNARFRÅGA: - Jonas har fått ett klistermärke MICROSOFT - Teams optimerat för de nya Macarna   https://appleinsider.com/articles/22/04/25/microsoft-teams-version-with-apple-silicon-optimization-quietly-released  - Teams finns i Microsoft Store   Ang Teams Store App   https://www.microsoft.com/en-in/microsoft-365/roadmap?filters=&searchterms=94577  - Microsoft går om AWS   https://www.techtarget.com/searchcloudcomputing/feature/Azure-surpasses-AWS-for-some-enterprise-cloud-uses  - Hur många minns vad som hände när allt helt plötsligt hette "Microsoft Defender %insertAnythingHere%"?   https://www.zdnet.com/article/microsoft-rebrands-its-compliance-and-data-governance-products-as-microsoft-purview  APPLE - DSA utkast har läckt   https://www.macrumors.com/2022/04/25/apple-forced-to-allow-third-party-app-stores/    https://appleinsider.com/articles/22/04/22/eu-antitrust-bill-could-force-apple-to-make-sweeping-changes-to-siri-app-store-more  - Och lite lobbying information angående att lägga pengar på saker    https://techcrunch.com/2022/04/22/google-facebook-apple-eu-lobbying-report/    - BONUSLÄNK: https://www.statista.com/statistics/265125/total-net-sales-of-apple-since-2004/  - Vad tycker vi om att Apple använder AirDrop för att skicka annonser till Apple Store kunder?   https://www.macrumors.com/2022/04/25/apple-store-customers-targeted-airdrop-ad/  - WOW… Om de löser detta är det ganska coolt   https://www.macrumors.com/2022/04/25/iphone-14-to-miss-out-on-48mp-camera-and-a16/    https://appleinsider.com/articles/22/04/25/now-apple-watch-may-get-satellite-communications-not-just-iphone  - Apple och jurister. Fast ibland så är det inte riktigt lika coolt..   https://appleinsider.com/articles/22/04/25/apple-hires-labor-busting-lawyers-to-fight-employees-efforts-to-unionize  GOOGLE: - Google rensar bort inspelningsappar från Play Store   https://www.thurrott.com/mobile/266029/google-play-policy-update-targets-third-party-call-recording-apps  - Pixel Watch på gång :-)   https://techcrunch.com/2022/04/25/googles-pixel-watch-may-finally-be-on-its-way/    https://www.engadget.com/the-morning-after-another-gadget-prototype-left-at-a-restaurant-111559891.html    https://www.engadget.com/google-files-a-trademark-application-for-pixel-watch-095342186.html  TIPS: - Twitter-variant   https://mastodon.social/    - BONUSLÄNK: https://www.enlitenpoddomit.se/e/elpoit-340-kom-det-fakta-i-vagen/  - Om James Webb Space Telescope   https://www.youtube.com/watch?v=fpYfx6oQWRk  PRYLLISTA - Björn:  Dammsugare!! https://www.dyson.se/dammsugare/sladdlosa-dammsugare  - David: Hörlurar för kontoret https://www.webhallen.com/se/product/343884-Steelseries-Arctis-7P-White  - Johan: Randone Pjäxor          Laddare https://www.amazon.se/UGREEN-Laddare-Portsladdare-Kompatibel-MacBook/dp/B091TV6LWN  EGNA LÄNKAR - En Liten Podd Om IT på webben,      http://enlitenpoddomit.se/  - En Liten Podd Om IT på Facebook,      https://www.facebook.com/EnLitenPoddOmIt/  - En Liten Podd Om IT på Youtube,      https://www.youtube.com/enlitenpoddomit  - Ge oss gärna en recension    - https://podcasts.apple.com/se/podcast/en-liten-podd-om-it/id946204577?mt=2#see-all/reviews      - https://www.podchaser.com/podcasts/en-liten-podd-om-it-158069  LÄNKAR TILL VART MAN HITTAR PODDEN FÖR ATT LYSSNA: - Apple Podcaster (iTunes), https://itunes.apple.com/se/podcast/en-liten-podd-om-it/id946204577  - Overcast, https://overcast.fm/itunes946204577/en-liten-podd-om-it  - Acast, https://www.acast.com/enlitenpoddomit  - Spotify, https://open.spotify.com/show/2e8wX1O4FbD6M2ocJdXBW7?si=HFFErR8YRlKrELsUD--Ujg%20  - Stitcher, https://www.stitcher.com/podcast/the-nerd-herd/en-liten-podd-om-it  - YouTube, https://www.youtube.com/enlitenpoddomit  LÄNK TILL DISCORD DÄR MAN HITTAR LIVE STREAM + CHATT - http://discord.enlitenpoddomit.se  (Och glöm inte att maila bjorn@enlitenpoddomit.se  om du vill ha klistermärken, skicka med en postadress bara. :) 

Les nouveautés AWS des deux dernières semaines qui ont attiré mon attention tournent autour de bourses pour apprendre la programmation des intelligences artificielles, d'automatisation des workflows de migrations, de jumeaux digitaux, mais que se cache-t-il donc sous ce terme ? Et puis Amplify Studio débarque après avoir été annoncé en novembre dernier. Il y a eu un AWS Summit aussi, je vous dit ou trouver les vidéos.

Les nouveautés AWS des deux dernières semaines qui ont attiré mon attention tournent autour de bourses pour apprendre la programmation des intelligences artificielles, d'automatisation des workflows de migrations, de jumeaux digitaux, mais que se cache-t-il donc sous ce terme ? Et puis Amplify Studio débarque après avoir été annoncé en novembre dernier. Il y a eu un AWS Summit aussi, je vous dit ou trouver les vidéos.

En este episodio hablamos de como un equipo de ingenieros de datos sin conocimientos de AWS tuvierón que aprender a la vez que hacian la migración de sus sistemas a AWS. Cómo lo hicieron? Cuales fuerón las estrategias que les ayudaron? Este es el episodio 4 de la tercera temporada del podcast de Charlas Técnicas de AWS.

En este episodio hablamos de como se recomienda que la organizaciones gestionen sus multiples cuentas de AWS. Para eso introducimos el concepto de Landing Zone y el servicio de AWS Control Tower.Este es el episodio 2 de la tercera temporada del podcast de Charlas Técnicas de AWS

About DanielleDanielle Baskin is a serial entrepreneur and multimedia artist whose work has been featured in The New York Times, The Guardian, NPR, The New Yorker, WSJ, and more. She's also the CEO of Dialup, a globally acclaimed voice-chat app.Links: Dialup: https://dialup.com Twitter: https://twitter.com/djbaskin Cofounder Quest: https://cofounder.quest Personal Website: https://daniellebaskin.com 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: It seems like there is a new security breach every day. Are you confident that an old SSH key, or a shared admin account, isn't going to come back and bite you? If not, check out Teleport. Teleport is the easiest, most secure way to access all of your infrastructure. The open source Teleport Access Plane consolidates everything you need for secure access to your Linux and Windows servers—and I assure you there is no third option there. Kubernetes clusters, databases, and internal applications like AWS Management Console, Yankins, GitLab, Grafana, Jupyter Notebooks, and more. Teleport's unique approach is not only more secure, it also improves developer productivity. To learn more visit: goteleport.com. And not, that is not me telling you to go away, it is: goteleport.com. Corey: You know how Git works right?Announcer: Sorta, kinda, not really. Please ask someone else.Corey: That's all of us. Git is how we build things, and Netlify is one of the best ways I've found to build those things quickly for the web. Netlify's Git-based workflows mean you don't have to play slap-and-tickle with integrating arcane nonsense and web hooks, which are themselves about as well understood as Git. Give them a try and see what folks ranging from my fake Twitter for Pets startup, to global Fortune 2000 companies are raving about. If you end up talking to them—because you don't have to; they get why self-service is important—but if you do, be sure to tell them that I sent you and watch all of the blood drain from their faces instantly. You can find them in the AWS marketplace or at www.netlify.com. N-E-T-L-I-F-Y dot com.Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. It's always fun when I get the opportunity to talk to people whose work inspires me, and makes me reflect more deeply upon how I go about doing things in various ways. Now, for folks who have been following my journey for a while, it's pretty clear that humor plays a big part in this, but that is not something that I usually talk about with respect to whose humor inspires me.Today that's going to change a little bit. My guest is Danielle Baskin, who among so many other things is the CEO of a company called Dialup, but more notably is renowned for pulling a bunch of—I don't know if we'd call them pranks. I don't know if we would call them performance art. I don't know if we would call them shitposting in real life, but they are all amazing. Danielle, thank you so much for joining. How do you describe what it is that you do?Danielle: Thanks for having me. Yeah, I've used a few different terms. I've called it situation design. I've called it serious jokes. I have called what I do business art, but all the things you said, shitposting IRL, that's part of it too.Corey: It's been an absolute pleasure to just watch what you've done since I first became aware of you, which our mutual friend, Chloe Condon first pointed me in your general direction with, “Hey, Corey, you think you're funny? You should watch what Danielle is doing.” That's not how she framed it, but that's what I took from it because I'm incredibly egotistical, which is now basically a brand slash core personality trait. There you have it.And I encountered you for the first time in person—I believe only time to date—at I believe it was Oracle OpenWorld on the expo floor. She had been talking about you a couple of days before, and I saw someone who could only be you because you were dressed as a seer to be at Oracle OpenWorld. The joke should be clear to folks but we'll explain it later for the folks who are—might need to replay that a bit. I staggered up to you with, “Hey, are you Chloe's friend?”Let me give listeners here some advice through counterexample. Don't do that. It makes you look like a sketchy person who has no clue how social graces work. No one has any context and as soon as you said, “No,” I realized, “Oh, I came across as a loon.” I am going to say, “Never mind. My mistake,” and walk away like a sensible person will after bungling an introduction like that. I'm not usually that inartful about these things. I don't know what the hell happened, but it happens often when we meet people that we consider celebrities, and sorry, for some of us that's you.Danielle: [laugh] yeah, also in fairness to you I was probably fully immersed in character being my wizard self, and so I was not there to, you know, be pulled back to reality. For some context, I was at Oracle OpenWorld because I made a thing called same exact name, oracleopenworld.org, but it's a divination conference for oracles, for fortune-tellers, for wizards, for seers, and it happened at the exact same place in time, so there was a whole crew of people dressed up with capes, and robes, and tall pointy hats doing tarot readings and practicing our divination skills.Corey: Now, I could wind up applying about two dozen different adjectives to Oracle, but playful is absolutely not one of them. I would not ever accuse Oracle, or frankly any large company of that scale of having anything even remotely resembling a sense of humor. As someone who does have to factor in the not that remote possibility of getting kicked out of events that I attend, how do you handle that and not find yourself arrested?Danielle: Oh, we were kicked out every single time.Corey: Oh, good good good.Danielle: I've done this for four years. The first year we were kicked out just because we didn't have badges. I made up our own conference lanyard; of course, there's security issues with that. We were pushed out onto the sidewalk, but I wanted to be inside the conference and closer to the building.The next year I did a two-layer conference badge, so I put the real one underneath the fake one so that if security went up to us we had the right to be there. What sort of happened—so, like, the first year we got kicked out was because we were all distributed; maybe there was like 20 of us. Sometimes we were together. Sometimes we were having our own adventures. My friend Brian decided do a séance for the Deloitte team.Corey: Well, that's Deloitte-ful. Tell me more.Danielle: [laugh]. Brian has never done a séance before, but he is a good improv actor and also a spiritual person, so this is, like, perfect for him. As the Deloitte team if they wanted to do a séance they were, like, sure because I think they didn't have anything going—I mean, people are bored at this conference.Corey: Oh, of course, they are.Danielle: Especially if your boss flew you there to stand at your booth and you've been saying the same thing over and over again; you're looking for something interesting. So, he grabs the pillows from a lounge area and little tea light candles and makes a whole circle so that the team can sit down.He's wearing a bright rainbow cape and he stands in the middle and he could have a booming voice if he wants to. So, he just starts riffing and going—he just goes into séance mode, and this was enough to trigger security noticing that something really weird was happening. And when they went—Corey: They come over and say, “What the hell is this?” The answer was “Kubernetes.”Danielle: I had said everyone can blame—if you get in trouble just blame me just say, “I'm doing this with my friend, Danielle,” and have them talk to me. I wanted more people to come and be wizards. I don't want them to worry about it, so I will take all of the issues on me. He said that he should talk to his manager, Danielle, or I don't know.He said something that made it seem we were all part of a company. Which then makes it seem like our whole project was secret guerilla marketing for something. And we didn't pay for booth. We were not selling anything. We were just trolling. Or not troll—I mean, we were having our own divination summit. We were genuinely—Corey: You were virally marketing is the right answer and from my perspective—Danielle: Yeah, no, I wasn't doing viral marketing. They think anything that's unusual and getting people's attention has the ultimate goal of selling something, which it's not a philosophy I live by.Corey: No, it feels like the weird counter-intuitive thing here is the way to get the blessing of everyone from this would've—the only step you missed was charging Deloitte for doing it at their booth because it attracts attention.Danielle: Oh, sure. Oracle should have been paying us a lot of money for entertaining people. Actually, genuinely I had some real heart-to-heart conversations with people who wanted to have a tarot reading about how should they talk to their boss about not listening to them. This is something magical that happens when you are dressed up in costume and you are acting really weird people feel they can say anything because you're acting way more unusual than them, so it sort of takes away people's barriers. So, people are very honest with me about their situation.People had questions about their family. Anyway, I was in the middle of a heart-to-heart tarot reading, and security at Oracle was alerted to find anyone with a cape. Find the wizards and kick them out because they didn't pay to be here. There's some weird marketing thing happen.Corey: “Find and eject the wizards,” is probably the most surreal thing that they have been told that year.Danielle: Oh, yeah. And they didn't know why. The message why I did not transmit to all the security, but they were just told to find us. Two guards with their walkie-talkies in their uniforms went up to me and they had to escort me off the premises. Which means we had to walk through the conference together and I asked them, “Why?” They're like, “We don't know. We were just told to find you.”Corey: Imagine them trying to find you stopping and asking people, “Excuse me, have you seen the wizard?”Danielle: Exactly.Corey: It is hard to be taken seriously when asking questions like that.Danielle: Totally, totally. So yeah, unfortunately, we had to leave and that has consistently happened because I've done it four times. The final year I went, there was a message before the event even started that you're not allowed to wear a cape.Corey: The fact that you can have actual changes made to company policy for large-scale, incredibly expensive events like that is a sign that you've made it.Danielle: It doesn't even point to any particular incident. Yeah, it's cool to have this sort of lore. When I asked in the last year I went, “I asked why can't we wear a cape?” And one of the event organizer security, I don't know what her role was. She said, “There was an incident the previous year.” Which she was talking about me and my friends.Corey: Of course, but that is the best part of it.Danielle: It's just lore than something once happened with these, like, dark spirits that tried to mess up the Oracle conference with their magic.Corey: Times change and events evolve. Years ago I attended an AWS Summit with a large protest sign that said on it AMI has three syllables, and it got a bit of an eyebrow raise from people at the door, but okay, great. Then people started protesting those events for one of the very many reasons people have to protest Amazon, and they keep piling more on that pile all the time which is neither here nor there.I realized, okay, I can't do that anymore because regardless of what the sign says I will get tackled at the door for trying to bring something like that in, and I don't try and actively disrupt keynotes. So okay, it's time to move on and not get myself viewed through certain lenses that are unhelpful, but it's always a question of moving on and try to top what I did previous years. Weren't you also at Dreamforce wearing pajamas?Danielle: I did a few things at Dreamforce. One year I literally set up a tent. They spend millions of dollars on beautiful fake trees and rocks, and also Dreamforce gets taken over every time the event occurs. I did a few things. I thought I should make it seem like this is real nature so I brought camping gear and a tent and just brought a hiking backpack in.Set it up in the middle of the conference floor laying by the waterfall, but there were people in suits networking around me that did not ask me any questions. I just stayed in the tent, but then I decided to list it on Airbnb. So, inside my tent, I was making an Airbnb listing telling people that they could stay at Dreamforce and explore the beautiful nature there, but it took an hour-and-a-half to get kicked out.Corey: The emails that you must have back and forth with places like Airbnb's customer support line and the rest have got to be legendary at this point.Danielle: [laugh] I get interesting cease-and-desists. I wish there was more dialogue. With Airbnb I just got my listing taken down and I couldn't talk to a human, and even when I got kicked out of Dreamforce they wanted me to leave immediately. I totally snuck in; I didn't have a badge or anything. So, I guess they're in the right for that. The second year at Dreamforce I wore a ghillie suit so I hid. So, I stayed a little bit after the conference ended by hiding as a bush.Corey: That is both amazing and probably terrifying for the worker that encountered you while trying to clean up.Danielle: Oh, I mean often employees—like it depends. Some people find my pranks really delightful because it shakes up their day. Security guards also find this amusing. There's some type of organizer that absolutely hates my pranks.Corey: There's something to be said for self-selecting your own audience. One question that I—sure you get; if I get it I know you get it—where it's difficult for people to sometimes draw the line between the fun whimsical things that you do as pranks and the actual things that you do. A great example of this is something you've been doing for, I think, four years now, the decruiter.Danielle: Yeah. The decruiter a service that's the opposite of a recruiter so it is—Corey: At the first re:Invent AWS had a slide that was apparently he made the night before or something and they misspelled security as decurity. From that perspective, what's a decruiter?Danielle: Yes, I love decurity as a way to talk about infiltrating a space, like, “No I'm a decurity officer.” Yeah, decruiter is basically a service where you talk to us to find out if you should quit your job. Instead of finding out if you should work at a place or figuring out what opportunities there are, we discuss the unemployed life—or the inbet—like, being self-employed, between jobs, switching careers, it's a whole spectrum but there's a few recruiters and we're all like very experienced not having an employer or working for a company. And so, we ask people about how would you spend your free time. What's your financial situation? Are you able to afford leaving? It gets pretty personal, but it's highly specific therapy, but we also don't have a high acceptance rate. I've only decruited like 15% people that I've talked to.Corey: Most of them realize that, oh, there's a lot of things I would have to do if I didn't have a job and I'm just going to stay where I am?Danielle: Yeah. Well, I think a lot of people think that as soon as they leave their job a lot of other things in their life will magically transform, or they'll finally be able to do their creative project they've always wanted to do. This is true some percentage of the time, but I always encourage people to do things outside of work and not seek in their whole fulfillment through their job.There's plenty of time where you can explore other ideas and even overlap them to make sure that like when you quit you have things lined up. A lot of people don't know how to answer, “If you suddenly left tomorrow and could just float for three months, what would you do?” If people give me a good answer—and this is similar to an actual job interview I was like, “Why are you excited about working this company?”If people give me a good answer, that's a conversation. A lot of people have no idea, but they're just stuck in a situation where there's things they could do in their outside of work life that would make them feel happier. That's why it's sort of like therapy, but there's a lot of internal company issues that I talk about. A common reason that people want to leave is that they love their role, they love the company's mission, but they do not like their manager, but their manager is really good friends with the CEO and they absolutely can't say anything. This is so common.Corey: They always say people they'll quit jobs they quit managers and there is something to be said for that.Danielle: Yes, it's scary for people to speak up or who do you write a letter to? How do you secretly talk with your team about it? Are you the only one feeling that way? Typically the people that are the most nervous about saying anything are kind of young either in their early 20s and they feel like they can't say anything.I encourage them to come up with a strategy for making change within their corporation but sometimes it's not worth it. If there's tons of other opportunities for them it's not worth them fixing their company.Corey: It's also I think not incumbent upon people to fix their entire corporate culture unless they're at a somewhat higher executive level. That's a fun thing. The derecruiter.com we'll definitely throw a link to that in the [show notes 00:15:49] and I'll start driving people to it when they ask me for advice on these things. Then you decided, okay, that's fun.You're one of those people I feel has a bit of the same alignment that I do which is, why do one thing when I could do a bunch of things? And you decided, ah, you're going to do a startup. What is the best thing that you can do that really can capitalize on emerging cultural trends? That's right. Getting millennial to make phone calls to each other. Tell me about that story.Danielle: Yeah, and it's not just millennials, though I'm millennial. So, a lot of millennials use Dialup. I mean, Dialup started as a project where basically me and a friend set up a robocall between ourselves. So, like a bot would call our phones and if we would pick up we'd both be connected, but neither of us was actually calling each other. So, it was a way to just always be catching up with each other.So, many friends asked me if they could join the robocalls. That was sort of the seat of Dialup is getting serendipitous phone calls throughout the day that connect you to a person that you might know or might want to meet. Because there's overlap of interest or overlap of someone you know. It grew from me and 20 friends to now 31,000 people who are actively using it all over the world and these conversations can be really incredible.Sometimes people stay on the phone for four hours. People have flown out to meet each other. I get notes every day of how a call has impacted someone one. So, that's what I'm up to now, but I'm trying to do more interesting things with voice technology. I just like realized, oh, the voice as a medium it just transports you to other worlds. You have space to imagine.I mean, people listening to this podcast right now they're not seeing us, but they probably are imagining us, what our rooms look like, what we look like. They're imagining the stories that we're telling them without the distraction of video. I want to do more interesting things with intimate audio—not broadcast stuff. Not Clubhouse or Spaces or anything like that, but just more interesting ways to connect people in one-on-ones.Corey: Something I've noticed is that the voice has a power that text does not. It makes it easier to remember that there's a human on the other side of things. It is far easier for me to send off an incendiary tweet at someone than it is for me to call them up and then berate them, not really my style.The more three-dimensional someone becomes in various capacities and the higher bandwidth the communication takes on, I think the easier it is to remember that most people who don't work at Facebook wake up in the morning hoping to do a good job today. Extending empathy to the rest of the world, that's an important thing.Danielle: Yeah, for sure. It's incredible that humans can detect emotional qualities in a voice call. It's hard to describe why, but people can detect pauses and little mutters. You can sort of know when someone's laughing or when someone's listening even though you're missing all of the visual cues.Corey: This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking, databases, observability, management, and security. And—let me be clear here—it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build. With Always Free, you can do things like run small scale applications or do proof-of-concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free, no asterisk. Start now. Visit snark.cloud/oci-free that's snark.cloud/oci-free.Corey: Taking a glance at dialup.com, it appears to be a completely free service. You mentioned that it has 30,000 folks involved. Are you taking the VC model of we're going to get a whole bunch of users first and then figure out how to make money later? Sometimes it works super well. Other times it basically becomes Docker retold.Danielle: I've been thinking about this a lot and I swing back and forth. Right now Dialup is its own thing, connecting strangers. It's free though I do have some paying clients because I do serendipitous one-on-ones within organizations. I've got a secret B2B page, and so that is a little bit of revenue. Right now I'm trying to sort of expand beyond Dialup and make a new thing, in which case I am leaning more towards building a sustainable and profitable company rather than do the raise-VC-money-until-you-die model.Corey: I think it's long past time to disrupt the trope of starving artist. What about well-paid artist? It seems like that would inspire and empower people to create a lot more art when they're not worrying about freezing to death. To that end or presumably to that end you are in the process of looking for a co-founder in what is arguably the most Danielle Baskin possible way. How are you doing it?Danielle: Oh, yeah. I could have done a regular LinkedIn post linking to a Google Doc, but that is not my style, and as a self-employed person I can't reach out to old coworkers and be like, “Oh, you're on my team a few years ago. What are you up to now?” So, I'm sort of under-networked and I thought I should make a game that sort of explains what I'm doing, but have people discover the game in an interesting way. So, I bought a bunch of floppy discs—I have a floppy disc dealer outside of LA.Corey: For those who are not millennials and are in fact younger than that—and of course let's not forget Gen X, the Baby Boom Generation, the Silent Generation which I can only assume is comprised entirely of people who represent big companies from a PR point of view because they never comment on anything. What is a floppy disc for someone who was born in, I don't know, 2005?Danielle: Oh, a floppy disk is how you would run software on your computer.Corey: Yeah, a USB stick with no capacity you can wreck with a magnet.Danielle: Yes, it's like a flat wide USB stick, but it only contains—Corey: 1.44 megabytes on the three-and-a-half-inch version.Danielle: I think some of them then went up to 2.88.Corey: Ohh.Danielle: You can't even fit a picture—a modern picture. You could do a super low-resolution pixel art.Corey: This picture of grandma has a whopping eight pixels in it. Oh, okay, great. I guess.Danielle: Yeah. More complex software would be eight floppy disks that you have to insert disk A, insert disk B.Corey: Anti-piracy warnings in that day of ‘don't copy that floppy.' It was a seminal thing for a long time.Danielle: I have it in my game; it says ‘don't make illegal copies of this game.' My game is not literally on the floppy disc. All floppy discs come with pretty interesting artwork on the label. There's a little space for a sticker, and because I have hundreds of floppy disks, I sort of looked at—I had a ton of design inspiration.So, I made floppy discs in the aesthetic of the other ones that say Cofounder Quest—like it's this game—and it leads you to a website. I scattered these in strategic places around the bay area, and I also mailed some to people outside of the bay area. If you stumble across this in person or on the internet, it leads you to this adventure game that's around seven minutes to play.It really explains what I want to do with Dialup, and explains me, and explains my aesthetic, and the sort of playful experiences that I'm into without telling you. So, you get to really experience it. At the end, it basically leads you to a job description and tells you to reach out to me if you're interested.Corey: I was independent for years and I finally decided to take on a business partner. As it turns out, Mike Julian, who's the CEO of The Duckbill Group and I go back ten years, he's my best friend. I kept correcting him. He introduced me as his friend. I said, “No, Mike, your best friend.” Then I got him on audio at one point saying, “Oh, Corey Quinn? He's my best friend.” I have that on my soundboard and I play it every time he gets uppity. That's the sort of nonsense it's important in a co-founder relationship. It is a marriage in some respects.Danielle: Oh, for sure.Corey: It's a business entity. Each one of you can destroy the other financially in different ways. You have to have shared values. The idea of speed-dating your way through finding some random co-founder as a job application, on some level, has always struck me as a little dissonant. I like the approach you're taking of this is who I am and how I go about things. If this aligns then we should talk, and if you don't like this you're not going to like any of the rest of this.Danielle: For sure. I'm definitely self-selecting with who would actually reach out after playing. I also understand. I'm not going to find a co-founder in a few weeks. I'm just starting conversations with people and then seeing who I should continue talking to or seeing if we could do a mini-project together.Yeah, it's weird. It's a very intense relationship. That's why people do end up becoming co-founders with someone that they already know who's a friend. It's possible I already know my co-founder and they've been in front of me this whole time. I think these sorts of moments happen, but I also think that it's cool to totally expand your network and meet someone who maybe has an overlap in spirit, but is someone that you would've never otherwise met. That there could be this great overlap or convergence there. I wanted to cast a very wide net with who this would reach, but it's still going to be a multi-month-long process or longer.Corey: It's not these one-off projects that are the most interesting part to me. It is the sheer variety and consistency of this. During the pandemic I believe you wound up having the verified checkmark badges for houses and fill out this form if you want one and for folks in San Francisco. Absolutely, of course, I filled that out. I read a fairly bad take news article on it of a bunch of people fell for this prank.No, absolutely not. If people are familiar with your work then they know exactly what they're getting into with something like this and you support the kinds of things you want to see more of in the world. I didn't fall for anything. I wanted to see where it led and that's how I feel on everything you do.Danielle: Yeah, you appreciated the joke.Corey: Yeah.Danielle: Yeah, I think people who are familiar with my work understand that I take jokes very seriously. So, it's not simply—like, usually it's not just a website that's like, huh, this was a trick. It's more of an ongoing theater piece. So, I actually did go through all of the applicants for the Blue Check Homes. Oh, for some context, I made a website where you could apply to have a blue verified badge and a plaster crest put on your house if you are a dignified authentic person that lives in the house.So, I'm interviewing—I narrowed it down to 50 people from all the applicants and I'm going through and interviewing people with a committee. I'm recording all of the interviews because I think this will make an interesting mini-documentary. I'm actually making one in installing one, but I'm documenting all of it.When I started it—for a lot of projects I don't have the ending planned yet. I like the sort of joke to unfold on the internet in real-time, and then figure out what the next thing I should do from there is and continue the project in a sort of curious exploratory mindset as opposed to just saying, “All right, the joke is done.”Corey: What is your process for coming up with this stuff? Because for me the most intimidating thing I ever see in the course of a week is not the inevitable cease and desist I get from every large cloud company for everything I do. Rather an empty page where it's all right time for me to write a humorous blog post, or start drafting the bones of a Twitter thread, or start writing my resignation and if I don't come with an idea by the end of it, I'll submit it. Where does the creative process start from with you?Danielle: Yeah. I rarely have creative brainstorming sessions. I'm a person who thinks of a million bad ideas and then there's one good one. My mind leaps to a ton of ideas. I rarely write down ideas. I don't do any sort of—you might imagine I'm in a room of whiteboards and post-it notes, workshopping things and doing creative brainstorm sessions, but I don't.I think I act upon the things that I feel just extremely excited about and feel like I must do this immediately. It's hard to explain, but with a lot of my ideas, I just feel this surge of energy. I have to do this because no one else will do it and it's funny at this moment. If I don't feel that way I kind of don't do anything and see if the idea keeps reemerging. With a lot of ideas I may be thought of it a year ago and it just kept resurfacing, but I don't really force myself to churn out creative projects if that makes sense. People have told me that my work reminds them of Mischief. It's like as a company that puts out a prank on a Tuesday every two weeks.Corey: Not familiar with them, but there have been a whole bunch of flash mob groups, and other folks who affected just wind up being professional pranksters, which I love the concept.Danielle: Yeah, yeah, for sure. I do churn out a lot of pranks and I even have my own prank calendar. I'm not strict with my own deadlines and I also think timing is important. So, you might think of a good idea, but then it's just the spirit of the zeitgeist doesn't want you to do it that week. I improvise the things that I want to launch. I mostly do things that I just feel are rich in something I could explore.Like, with Cofounder Quest I was always on the fence about it because it feels to me annoying to tell people you're trying to hire someone or to put yourself out there and be pitching your startup. So, I was kind of nervous about that, but I also thought if I leave a floppy disk in the park, and then put a picture on the internet it'll lead to something—there's something that it will lead to.It might lead to finding a co-founder. It might lead to meeting interesting people, but also I've never built an interactive game with audio and so I was interested in learning that, but yeah, I tend to land on ideas that I think are rich in terms of things I could learn. Things that I could turn into more immersive theater and things that keep resurfacing as opposed to keeping myself on a strict schedule of creative ideas if that makes sense.Corey: It makes a lot of sense. It's one of those things that it is not commonly understood for those of us who came up in the nose of the grindstone 40 hours a week, have a work ethic. Even if you're not busy look busy. Sometimes work looks a lot more like getting up and going to a coffee shop and meeting some stranger from the internet than it does sitting down churning out code.Danielle: For sure. I think that it is important to continue being in conversations with people. I think good ideas emerge while you're in the middle of talking, and you realize your own limitations and ideas when you have to explain things to other people. While something you're very clear in your head as soon as there's a person you don't know and they ask you, “What are you working on?” You realize, oh, there's so many gaps. It made perfect sense to me, but there's a lot of gaps. So yeah, I think it's important to stay in dialogue and also have to explain yourself to new people instead of just sort of making ideas in a vacuum.Corey: I want to thank you for being so generous with your time and talking to me about all the various things you have going on. If people want to follow along and learn more about what you're up to, where can they find you?Danielle: I post a lot of my projects on Twitter. So, I'm @djbaskin. If you want to play Cofounder Quest, it's cofounder.quest. That is an actual domain. I also have a website daniellebaskin.com, which has a lot of my projects, many of which we didn't discuss. I also do, similar to Oracle OpenWorld, I like to host popup events that involve lots of people trolling. So, if you want to get involved in anything you see I'm always happy to bring more wizards on board.Corey: We will, of course, put links to that in the [show notes 00:31:10]. Danielle, thank you so much for taking the time to speak with me today.Danielle: Oh yeah, thanks for having me. It was great talking with you.Corey: Danielle Baskin, CEO of Dialup, and oh so very much more. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast please leave a five-star review on your podcast platform of choice, along with a long rambling comment applying to be the co-host of this podcast, viewing it of course as a podcasting call.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.

On The Cloud Pod this week, the results of the AWS Summit prediction draft are in. It was probably worth getting up early for — especially if you're Jonathan. A big thanks to this week's sponsors: Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. JumpCloud, which offers a complete platform for identity, access, and device management — no matter where your users and devices are located.  This week's highlights

On The Cloud Pod this week, everyone's favorite guessing game is back, with the team making their predictions for AWS Summit and re:Inforce — which were not canceled, as they led us to believe last week.                   A big thanks to this week's sponsors: Foghorn Consulting, which provides full-stack cloud solutions with a focus on strategy, planning and execution for enterprises seeking to take advantage of the transformative capabilities of AWS, Google Cloud and Azure. JumpCloud, which offers a complete platform for identity, access, and device management — no matter where your users and devices are located.  This week's highlights

TranscriptCorey: This episode is sponsored in part by LaunchDarkly. Take a look at what it takes to get your code into production. I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visit launchdarkly.com and tell them Corey sent you, and watch for the wince.Jesse: Hello, and welcome to AWS Morning Brief: Fridays From the Field. I'm Jesse DeRose.Amy: I'm Amy Negrette.Tim: I'm Tim Banks.Jesse: This is the podcast within a podcast where we talk about all the ways that we've seen AWS used and abused in the wild, with a healthy dose of complaining about AWS for good measure. Today on the show, we are going to be talking about AWS re:Invent. Now, I know that most of you know what re:Invent is, but I just would love to set the playing field level for everybody really quick. Amy, Tim, what is AWS re:Invent.Tim: AWS re:Invent is AWS's week-long corporate conference. It's not really a user conference; it's certainly not, like, a community conference, but it's a week-long sales pitch in the desert. It's like the worst version of a corporate Burning Man you could ever imagine because they even have a concert.Jesse: It is in Las Vegas. Now, I personally have mixed feelings about going to Las Vegas in general, but this adds so much to the conference in general because it's not just in a single conference venue that's centrally located near the hotels. Is it is across the strip—Amy: It's the entire strip.Jesse: It's the entire strip. So—Amy: They block every hotel and they buy every piece of ad space.Jesse: Yes. There is no escaping AWS re:Invent for the entire week that you're there. And sometimes that's a good thing because you do want to be involved in what's going on, but other times, it is a lot.Tim: So, I'm trying to figure out which LP that ‘buy the entire Las Vegas trip' covers because it's certainly not be frugal.Amy: No. [laugh].Jesse: No, not at all. But we do have new information. We decided to do this episode specifically because new information was just released about re:Invent for this year. Amy, what is that information? What do we know?Amy: They've decided, in having to go virtual last year, due to some kind of horrible global crisis, to return in person to the world's most densely packed tourist spot, Las Vegas, and host this huge event from November 29th to December 3rd—that's right after Thanksgiving—and just, what do they say? Return to normal. Return to normal.Tim: That way everybody can get exposed to COVID before they go home for the holidays.Jesse: [laugh].well, you at least get one holiday in, if you celebrate or recognize Thanksgiving, and then you get to bring everything back after that.Amy: Yeah, people bring enough things back from Vegas. I'm not sure we'd have to find more reasons. [laugh].Tim: [laugh].Jesse: I know that there's that great marketing tactic of, “What happens in Vegas stays in Vegas,” but—Tim: That's not what they say at the clinic.Jesse: Nope. Mm-mm. Now, I will say, I know that almost every conference event was completely virtual last year due to the pandemic, and this year, a lot of conferences are still trying to straddle that line between what's acceptable, can we do maybe smaller events in person, some kind of a hybrid online/in-person thing. I have mixed feelings on this. I appreciate that I can still attend AWS re:Invent from home this year digitally, I can still watch a lot of the main keynote events and a lot of the other information that is being shared, but I don't know, it's always hard because if you do a hybrid event, you're automatically going to miss out on any of that in-person socializing and networking.Tim: Well. So, I think it's interesting. AWS re:Invent suffers from the same issue that pretty much all other conferences suffer from is that there's not really value-add in the talks, at least for attending.Jesse: Yeah.Amy: If you're going to be able to see those talks afterwards if the announcements are going to be publicized afterwards which, that is true in both cases, then what's the point of spending the money, and the time, and the possible exposure to go watch them in person? So, then the other thing is, “Well, we want to go for some of the training seminars,” or some of these other things. Well, those are also offered online, often. Or, like, copies of them online. These are the same kinds of tutorials like that that you can have your TAM or SA run if you're an AWS customer currently; that's what they're doing there.The other thing is, too, those in-person sessions get filled up so quickly that there's no guarantee [unintelligible 00:05:08] anyways. And that's one of the complaints they've had about re:Invent in the past is that you can't get into any of the sessions. And so, you couple all that along with most of the reason going being—if it's not the talks and is not the sessions, it's the hallway track. And then you got to kind of wonder, is the hallway track going to be valuable this year because if it's hybrid, what percent of the people that you would normally talk to you are going to be there and what percentage aren't? And so there's a lot of calculus that's got to go into it this year.Jesse: I've always struggled with any vendor-sponsored event, all the talks feel either like a sales pitch, or they feel like a use case that just doesn't fit for me. And that may just be where I'm at in my professional journey; there's definitely reasons to go if you want to see some of these talks or see some of this information live, or be the first person to talk about it. Or even the people who are going to be the news sources for everybody else who want to be the first person to talk about, “Oh, we attended, and we saw these things and were live-tweeting the entire conference.” If that's your shtick, I fully support that, but I always struggle going to any kind of vendor conference because I just feel like the value that I get from the talks, from training if I go to training, just doesn't feel like enough for me, personally.Amy: So, I've done some of the AWS-led training when Summit was in Chicago, a couple years ago, and I'll be honest, you lose a lot in these large AWS-led trainings because these classes, it's not going to be like the ones that you would sign up for even being hosted either by your company or by your local user group chapter where you will have at max 100 people. You have well over that. You have an entire conference room full of people, and they're asking questions that are across the level of expertise for that topic. I went for one of the certification training seminars and straight-up 15 minutes was spent talking about what a region is. And given that's page one of any training material, that was a waste of $300.Jesse: Yeah.Tim: I think you run into the problem because it is, in fact, I mean, let's be honest, it's a multi-day sales pitch. It's not a user conference, it's not user-generated content. It's cherry-picked by the powers-that-be at AWS, the service groups. Is a big push for account executives to encourage high-level or high-spend accounts to participate in those so they get logo recognition. And so that becomes more of the issue than the actual cool user stories.And that's fine if you're using it literally just a sales conference because it's very compelling sales material, your account executive will go there and try and close deals, or close bigger deals, or sign EDPs or something like that, but from an engineering standpoint, from a technical standpoint, it's remarkably uncompelling.Jesse: Yeah, I think that's one other thing to call out, which is, there is definitely this networking opportunity that we talked about from a hallway track perspective, but there's also a networking and business opportunity to meet with your account manager, or your TAM, or your SA in person and have conversations about whatever things you want to talk about; about future architecture, or about closing an EDP—or I should say, about an EDP because the account manager will try to close that EDP with you—and then basically use that as next steps for what you want to do with AWS. But again, all of those things can be done without flying you to Las Vegas and being amongst all these other people.Tim: I mean, let's not take away, there's a certain synergy that happens when you have face-to-face contact with folks, and a lot of these conversations you have in hallways are super, super organic. And so I think that's indicative of conferences as a whole. One of the things that we learned in the pandemic is that, yeah, you can have talks where people just, like, look at a screen and watch talks, and a lot of conferences have done that. But that's not why people want to go to the conference; they want to go to the conference to talk to people and see people. And if you want to have a conference where people talk to people and see people, and that's the whole point of doing it, then the business model behind that looks dramatically different, and the content behind that looks dramatically different.You just have a bunch of birds-of-feather sessions or a bunch of breakout sessions. You do a keynote at the beginning, you do a keynote at the end, and then you just let people mingle, and maybe you have some led topics, but you don't generate content; you shut up and you let the people innovate.Jesse: I also want to add to that. It is one thing to have a conference that is in one venue where everybody is going to be gathered in the same space, creating conversation, or creating easy opportunities—Amy: Five miles worth of content isn't exciting for you?Jesse: Yeah. So, in Las Vegas because the entire conference is spread across the entire strip, you're going to have opportunities to network across the entire strip basically, and sometimes that means you're going to only spend time networking with the people who are in the same hotel as you at the time of the track that you are waiting for, or the time of the event that you are waiting for. It is unlikely that you are going to run all around the strip just to be able to network with everybody that you run into.Corey: This episode is sponsored in part by our friends at Lumigo. If you've built anything from serverless, you know that if there's one thing that can be said universally about these applications, it's that it turns every outage into a murder mystery. Lumigo helps make sense of all of the various functions that wind up tying together to build applications. It offers one-click distributed tracing so you can effortlessly find and fix issues in your serverless and microservices environment. You've created more problems for yourself; make one of them go away. To learn more visit lumigo.io.Amy: The other issue I have, not just with re:Invent, but this is really any larger conference or conferences that rely on the kind of content where it is a person speaking at you and you don't get to meet these people, is that without any level of Q&A or interactivity—and this is true especially for AWS-led events—is that it is no different than watching someone on video. You can go to these talks, and you can perhaps have conversations with people as they filter out of the room, but there's no way you're going to be able to talk to that person who was delivering that content, unless you can track them down amongst the sea of people in re:Invent or [unintelligible 00:12:16] in Las Vegas.Tim: What typically has to happen is that after someone has given a compelling talk and you really want to talk to them, you have to go and talk to your account manager; your account manager will then set up a meeting that will happen at a later time where you're going to all call in over Chime, and then you will quote-unquote, “Meet” that person virtually. And if that's the case, you could have just stayed home and watched [laugh] the talk online, and then done the same thing.Amy: Conferences need more Chime. That's what [laugh] the problem is.Jesse: [laugh]. I think my eye just started twitching a little bit as soon as you said that, Amy.Amy: I'm glad. So, then why would people go? There's the hallway track, but is that worth the heavy price tag of going to Vegas? A lot of us live in areas where there is either going to be an AWS Summit or there are AWS user groups. What do you get from going to a larger event such as re:Invent and having that level of communication that you can't get from those smaller groups?Tim: I mean, the importance of networking cannot be overstated. It is extremely important, whether it's for laying groundwork for future deals, laying groundwork for future collaborations. I've been at conferences where a hallway track, just folks meeting up in the hallway and having a really organic discussion turned into a product within three months. So, those kinds of things are important. And, unfortunately or unfortunately, they do happen better quite often, when people are in-person and they've had a chance to talk, maybe even a couple of drinks or whatever.So, I mean, people ink deals, they shake hands, they get, you know, a lot of work done when it comes to maintaining and managing relationships, and to some people, that is worth it. But I do think that you have to be very, kind of, eyes-open about going into this. It's like, you're not going to go in there to get a lot of technical insight, you're not going to go in there to talk to a whole bunch of people unless you really have a relationship or establish some kind of rapport with them beforehand. Because just to go up and blindly like, “Hey, I'm going to grab you in the hallway, and this is who I am,” that's not always great, especially nowadays, when people are, kind of, already averse to, you know, talking to strangers, sometimes.Jesse: I've always struggled with talking to strangers in general at conferences because I'm predominantly introverted, so if I don't have an open introduction to someone through a mutual third party or mutual friend, it's just not going to happen. And I've gotten better at that over the years as I go to conferences, but it's going to be especially tough now in cases where folks are not just averse to, I don't want to say strangers, but averse to physical contact and adverse to people just, kind of, approaching them out of the blue. It's tough. I want to be more mindful of that and I want to be better, but it's hard, especially in cases where you're in a crowd of hundreds of people or, you know, thousands of people across the strip, that it just gets overwhelming really quickly for some folks.Amy: I do want to loop this round, if anything, just for a poll for Twitter. Do not close an EDP in Vegas. You're probably not of the right mind [laugh] and have the right people to do that. Wait till you get back to work. Please. That's just me. [laugh].Jesse: I would also like to add—we talk about why people go; I think that there's definitely a solid contingent of folks who attend re:Invent because it is the one time a year that the company sanctions them getting away from their family for a couple of days, getting away from, you know, the day-to-day routine of whatever work is going on for a couple days, and go to Vegas. Now, I know that the company is not going to sponsor them drinking every night, or gambling, or whatnot, but they're likely going to be doing those things anyhow, so it is this company-sanctioned opportunity to just go experience, you know, something different; go take a vacation, basically, for a couple days.Amy: Corporate Burning Man.Tim: Corporate Burning Man, exactly. A vacation in Vegas.Amy: I am not a fan of ever working in Vegas. If I'm on the clock, I cannot be in Vegas, not because I'm prone to excessive behavior when I'm on my own, but more that I cannot be productive in that much noise and that much flaky internet. It drives me absolutely batty, and I'm only going to be, as far as implementations, so productive in a crowd that large.Tim: I will say this, especially in regards to Vegas, there are other places you can go, other places that need the money more. AWS wants to rent a city, rent a city that needed the money. Put that money where it could be to used, where it really makes a difference. I don't know if Vegas is the right place for that, if I'm being honest, especially after all we've learned and dealt with in 2020. And so that's why in 2021, yeah, no for me, continuing to have re:Invent in Vegas is very, very tone-deaf.Jesse: I still think, Amy, you and I just need to—actually sorry, all three of us should attend and basically keep a running Waldorf and Statler commentary through the entire conference. I don't know if we can get that little, you know, opera booth that's kind of up and away from all the action, but if we can get something like that and do some sports commentary—ohh, maybe on the expo hall—Amy: That would be great. That would be great if we don't get banned. [laugh].Tim: I think what would be even more fun is to give a MST3K—Jesse: Ohhh.Tim: —treatment of the keynotes afterwards, you know what I mean?Jesse: Yeah.Amy: Yes.Jesse: I mean, Amy and I had also talked about playing some Dungeons and Dragons while we were there, and I feel like if we can find some, I'm going to say, tech-themed RPG—I realize that is a broad category, and everybody's going to spam me afterwards for this, but—Amy: I got that. Don't worry about it.Jesse: Yeah, I'm on board. I feel like anything that we can do to create a roleplaying game out of this conference, I'm down.Tim: I'm still waiting for you to explain to the audience in general who Waldorf and Statler were?Jesse: Oh, yes, that is fair. Okay. Waldorf and Statler are two characters from the old-school Muppets Show, which is amazing and delightful. It's on Disney+; I highly recommend it. They are basically—Amy: They're two grumpy old muppets, and they have been roasting people since the 70s. That is—that's all it is. [laugh].Tim: All they do is they sit up in the upper booth and they throw shade, and I love it.Amy: Yes. And they just show up in random parts in different movies. They'll be, like, on a park bench, and there'll be a serious moment, and then they'll just start talking crap for no reason. And it's great.Jesse: They're the best. They're absolutely fantastic. I adore them. I hope to be them one day.Amy: One day.Tim: Really, both of them? I don't, I don't know how that's going to work.Jesse: I am hoping to clone myself. One of me is going to have fabulous hair and one of me is going to be balding. Probably the clone is going to be balding; sorry about it, future me. But—Amy: [laugh].Tim: Well, I mean, and have just a magnificent chin, right?Jesse: Yes, yes, that's the trade-off. Losing the hair up top but absolutely fantastic chin.Tim: Here's what I want to see. I want to see the listeners submit things that you think should be on the re:Invent bingo cards.Amy: Ohh, yes.Jesse: Yes.Amy: I would love to see that.Jesse: So, for those of you listening, you've got two options for submitting things that you'd like to be on the re:Invent bingo cards. The ideal option is going to lastweekataws.com/QA. Fill out the form and let us know what you think should be on the bingo card. You can also respond to the social media post that will be posted for this content, and we can take a look at that as well. But that'll be a little bit harder for us to follow because I'm unfortunately not like Corey. I can't absorb all of Twitter in a day; it takes me a longer time to read all that content.Jesse: If you've enjoyed this podcast, please go to lastweekinaws.com/review and give it a five-star review on your podcast platform of choice, whereas if you hated this podcast, please go to lastweekinaws.com/review. Give it a five-star rating on your podcast platform of choice and tell us what you think about AWS re:Invent.Announcer: This has been a HumblePod production. Stay humble.

In questo episodio vi racconto i contenuti che troverete durante le due giornate dell'AWS Summit Online 2021 - inclusi i tantissimi contenuti in italiano. Vi parlo del keynote di apertura e delle sessioni tecniche e culturali che trovate nel Builders Day e nell'Innovation Day - oltre alle tante attività interattive e divertenti come la AWS Deep Racer League, la caccia al tesoro digitale, i workshop pratici, le risorse per la formazione e le certificazioni, e tanto altro. Link: Evento e agenda. Link: AWS DeepRacer League. Link: Registrazione gratuita.

About Amy Arambulo NegretteWith over ten years industry experience, Amy Arambulo Negrette has built web applications for a variety of industries including Yahoo!, Fantasy Sports, and NASA Ames Research Center. One of her projects modernized two legacy systems impacting the entire research center and won her a Certificate of Excellence from the Ames Contractor Council. She has built APIs for enterprise clients for cloud consulting firms and led a team of Cloud Software Engineers. Currently, she works as a Cloud Economist at the Duckbill Group doing bill analyses and leading cost optimization projects. Amy has survived acquisitions, layoffs, and balancing life with two small children.Website: www.amy-codes.comTwitter: @nerdypawsLinkedin: linkedin.com/in/amycodesWatch this episode on YouTube: https://youtu.be/xc2rkR5VCxoThis episode sponsored by CBT Nuggets and Lumigo.TranscriptJeremy: Hi everyone, I'm Jeremy Daly, and this is Serverless Chats. Today, I'm joined by Amy Arambulo Negrette. Hey, Amy thanks for joining me.Amy: Thank you, glad to be here.Jeremy: You are a Cloud Economist at the Duckbill Group, so I'd love it if you could tell the listeners a little bit about yourself and your background and what you do at the Duckbill Group.Amy: Sure thing. I used to be an application developer, I did a bunch of AWS stuff for a while, and now at the Duckbill Group, a cloud economist is someone who goes through cost explorer and your usage report and tries to figure out where you're spending too much money and how the best to help you. It is the best-known use of a small skill I have, which is about being able to dig through someone's receipts and find out what their story is.Jeremy: Sounds like a forensic accountant, maybe forensic cloud economist or something to that effect.Amy: Yep. That's basically what we do.Jeremy: Well, I'm super excited to have you here. First of all, I have to ask this question, I've known Corey for quite some time, and I can imagine that working with him is either amazing or an absolute nightmare. I'm just curious, which one is it?Amy: It is not my job to control Corey, so it's great. He's great to talk to. He really is fully engaged in any conversation you have with him. You've talked to him before, I'm sure you know that. He loves knowing what other people think on things, which I think is a really healthy attitude to have.Jeremy: I totally agree, and hopefully he will subtweet this episode. Anyways, getting into this episode, one of the things that I've noticed that you've done quite a bit, is you create technical content. I've seen a lot of the talks that you've given, and I think that's something that you've done such a great job of not only coming up with content and making content interesting.Sometimes when you put together technical content, it's not super exciting. But you have a very good way of taking that technical content and making it interesting. But then also, following up with it. You have this series of talks where you started talking about managing FaaS, and then you went to the whole frenemies thing with Fargate versus Lambda. Now we're talking about, I think the latest one you did was about Lambda and the container support within Lambda. Maybe we can just go back, or start at a point where, for people who are interested in maybe doing talks, what is the reason for even creating some of these talks in the first place?Amy: I feel a lot of engineers have the same problem, just day-to-day where they will run into a bug, and then they'll go hit the all-knowing software engineer, which is the Google search engine, and have absolutely either nothing come up or have six posts that say, I'm having this problem, but you won't ever get an answer. This is just a fast way of answering those questions before someone has to ask.Jeremy: Right. When you come up with these ... You run into this bug, and you're thinking to yourself, you can't find the answer. So, you do the research, you spend the time digging through, and finding the right way to solve it. When you put these talks together, do you get a sense that it's helping people and then that it's just another way to connect with the community?Amy: Yeah. When I do it, it's really great, because after our talk, I'll see people either in the hallway, or I'll meet someone at a booth, and they'll even say, it's like, I ran into this exact same problem, and I gave up because it was such a strange edge case that it was too hard to fix, and we just moved on to another solution, which is entirely possible.I also get to express to just the general public that I do, in fact, know what I'm talking about, because someone has given me a stage to talk for 30 minutes, and just put up all of my proofs. That's an actually fun and weirdly empowering place to be.Jeremy: Yeah. I actually think that's really interesting. Again, for me, I loved your talks, and some of those things are ... I put those things at the back of my mind, but I know for people who give talks, who maybe get judged for other reasons or whatever, that it certainly is empowering. Is that something where you certainly shouldn't have to do it. There certainly should be that same level of respect. But is that something that you found that doing these talks really just sets the tone, right off the bat?Amy: Yeah, I feel it does. It helps that when someone Googles you, a bunch of YouTube videos on how to solve their problem comes up, that is extremely helpful, especially ... I do a lot of consulting, so if I ever have to go onsite, and someone wants to know what I do, I can pull up an actual YouTube playlist of things that I've done. It's like being in developer relations without having to write all of that content, I get to write a fraction of that content.Jeremy: Right. Unfortunately, that is a fact that we live with right now, which is, it is completely unfair, but I think that, again, the fact that you do that, you put that out there, and that gives you that credibility, which again, you should have from your resume, but at the same time, I think it's an interesting way to circumvent that, given the current world we live in.Amy: It also helps when there are either younger engineers or even other younger professionals who are looking at the tech industry, and the tech industry, especially right now, it does not have the best reputation to be able to see that there are people who are from different backgrounds, either educationally or financially, or what have you, and are able to go out and see someone who has something similar being a subject matter expert in whatever it is that they're talking about.Jeremy: Right. I definitely agree with that. That's that thing, where the more that we can amplify those types of voices and make sure that people can see that diversity, it's incredibly important. Good for you, obviously, for pushing through that, because I know that I've heard a lot of horror stories around that stuff that makes my blood boil.Let's talk to some of these people out here who potentially want to do some of these talks, and want to use this as a way to, again, sell themselves. Because I can tell you one thing, once I started writing blog posts and doing talks and doing those sorts of things, clearly, I have a very different background, but it just gave me a bunch of exposure; job offers and consulting clients and things like that, those just become much easier to get when you can actually go out there and do some of this stuff.If you're interested in doing that, I think one of the hard things for most people is, what even makes a good talk? You've come up with some really great talks. What's that secret sauce? How do you do that?Amy: I think it can also be very intimidating since a lot of the talks that get a lot of promotion are always huge vendor events that they're trying to push their product, they're trying to push a solution. That usually takes up a lot of advertising real estate, essentially, where that's what you see, that's what you see all the threads and everything. When you actually get to these community conferences, or even when I would speak at AWS Summit, it was ... I had a very specific problem that I needed to solve. I ran into a bug, the bug was not in the documentation, because why would it be?Jeremy: Why would you put that in there, right?Amy: Of course. Then Google, three pages down, maybe put me on the path to finding the right answer, and it's the journey of trying to put all of the bug fixes in place to make it work for your specific environment and then being able to share that.Jeremy: Right, yeah. That idea of taking these experiences that you've had, or trying to solve a problem, and then finding the nuances maybe in solving the problem as opposed to the happy path, which it's always great when you're following a blog post and it says, run this command, then run this command, then run this command. Well, what happens on that third command when the thing blows up, and you have no idea what to do? Then you end up Googling for five hours trying to find your way out of that.You take this path of, find those bugs or find that non-happy path and solve it. Then what do you do around there? How do you then take that ... You got to make that interesting somehow.Amy: Yes. A lot of people use gifs and memes. I use pictures of food and screencaps from Dungeons and Dragons. That's usually just different enough that it'll snap someone just out of their phone going, "Why is there a huge elf on my screen trying to attack people screaming elf errors." Well, that's because that's what they thought it would be great to call it. It's not a great error code. It doesn't explain what it is, and it makes you very confused.Jeremy: Right. Part of that is, and again, there's that relatability when you create talks, and you want to connect with the audience in some way. But you also ... This is the other thing that I've always found the hardest when I'm creating talks, is trying to find the right level. Because AWS always does this thing where they're like, it's a 200 level, or it's a 400 level, and so forth. I think that's helpful, but you're going to get people of all different skill levels, and so forth. How do you take a problem like that, and then make it relatable, or understandable, probably? Find that right level?Amy: The way I see it, there's going to be at least one person of these two types in the room that are not going to be your target audience, someone who doesn't know what you're talking about, but sees that a tool that they're considering is going to pose a problem, and they want to know how difficult it is to fix it. Or there's going to be a business person who has no technical background, and they just want to know if what they're evaluating is worth evaluating, if this error is going to be so difficult to narrow down and try to resolve that, yes, why would we go through something that my engineers are going to spend hours to try to fix something that's essentially a configuration issue?When I write any section of a talk, I make sure that it addresses a person who may not have come into that with that exact problem in mind. For the people who have, they'll understand the ... In animation, it's called key images, where there are very specific slots where you understand the topic of what is happening and the context around it. I always produce more verbose notes that go with my presentation. I usually release it either at the end of the day, or later on that week, once everyone has had time to settle, and it provides a tutorial-esque experience where this is what you saw, this is how you would actually do it if you were in front of a screen.Jeremy: Yeah.Amy: There are people who go to technical talks with a laptop on their lap because they're also working while they're trying to do it. But most of the time, they're not going to have the console open while you're walking through the demo. So, how are you going to address that issue? It's just easier that way.Jeremy: I like that idea too, of ... I try to do high-level bullet points, and then talk about the bullet point. Because one thing that I try to do, and I'd love to hear your thoughts on this as well. Here I am picking your brain trying to make my own talks better. But basically, I do a bullet point, and then I talk through it. I actually animate the bullet points coming in.I'm not a huge fan of showing an entire slide with all the bullet points and then letting people read ahead, I bring a bullet point in, talk about the bullet point, bring another bullet point in. Is that something you recommend doing too? Or do you just present all the concepts and then walk people through it?Amy: I think it depends. I tend to have very dense slides, which is not great for reading, especially if you're several rows back. I truly understand that. But the way I see it, because I also talk very fast when I'm on stage that I want there to be enough context around what's happening, so that if I gloss over a concept, then you visually can understand what's happening.That said, if that's because the entire bullet block on my slide is going to be about a very specific thing that's happening. It's not something that you have to view step-by-step. Now, I do have a few where, especially in a more workshop scenario, where you're going, I want you to think about this first and then go on to this next concept. I totally hide stuff. I just discovered for a talk that I was constructing the other day, that there's an animation that drops them down like index cards, and that's now my favorite animation right now.Jeremy: When you're doing that, like because this is the other thing, just for people who have ever ... If you're out there and you've ever written a talker or you've given a talk, the first iteration of it is never going to be the right one. You have to go through and you have to revise. It is sort of weird, and I don't know, maybe you felt this way too, in the pre-pandemic world, when you would give talks in person, most of the time, you'd give it to a relatively small audience, a couple of hundred people or whatever, as opposed to now, when we do talks, post-pandemic, and they're online, it's like, they're immediately available online.It's hard to give the same talk over and over and over and over again, without somebody potentially having seen it. A lot of work goes into a single talk. Not being able to use the same time over and over again, is not great. But, how do you refine it? Is it that you tested it with a live audience, or do you use a family member or a friend, or a colleague? How do you test and refine your talks?Amy: I'm actually an organizer at a meetup group, and specifically built around giving people of marginalized gender identities, and a place to stage and write technical content. It is a very specific audience.Jeremy: I can imagine.Amy: But it addresses that issue I had earlier about visibility, it also does help you ... If you don't have a lot of contacts in this industry, just as an aside, technical speaking is a way to do it, because everyone loves talking to each other after the stress has worn off, and you become the friendliest person after you've done that.But also, there are meetup groups out there, specifically about doing technical feedback, or just general speaking feedback. If you want to do something general, Toastmasters is a great organization to do. If you want to do strictly technical, if you do any cloud-related stuff, the DevOps communities are super friendly, even if it's not specifically about DevOps. I'm not a DevOps person, but I have a lot of DevOps friends. Some of my best friends are DevOps people.And you can get on a meetup or a Zoom call and just burn through your slides for about 10 or 15 minutes and see ... Your friends will be very honest with you, in a small group.Jeremy: Right. One of the things I did notice, too, giving a speech in person or giving your talk in person versus giving a talk via Zoom call, is sometimes when you don't hear any laughs or chuckles from a little joke that you make in there, it can feel very lonely in that space after you're waiting for something in there, but. It's a little bit ...Amy: It's worse when there are people in the room. I assure you, it is so much worse.Jeremy: That is very true. If something falls flat, that's a good point. Just going back to more this idea of creating good talks, and what makes a good talk. Where do you find ... You mentioned, maybe it's a vendor conference or something and you maybe install the vendor stuff, and you find the bugs and so forth. But is there any other places that you get inspiration from? Are there any resources you use to sort build some of these talks?Amy: Again, the communities help. The communities will tell you, really, it's like, I don't understand this thing, can someone hop on a call with me for real quick minute and explain why this concept is so hard? That's a very good place to base your talk off. As far as making them engaging, and interesting, I tend to clone video gaming videos, just because that's what I watch. I know, if it's going to be interesting to me, then it will probably be at least different than the content that's out there.Jeremy: Right. That's a good way to think of things too, is if it's something that you find interesting, chances are, there are lots of other people that will find that interesting. All right, let's go back to just this idea of creating new talks. You had mentioned this idea of, again, finding the bugs and so forth. But one of the things that I think we see quite a bit is always that bleeding edge stuff. People always want to write content about something new that happened.I'm guilty of this, I would think from a serverless standpoint where you're talking about things that are really, really bleeding edge. It's useful and they're interesting. Certainly, if you go to a conference about serverless, then it's really nice to see you have these talks and what might be possible. But sometimes when you're going to more practical type things. Again, even DevOps Days, and some of those other things, I think you've got attendees or talk listeners who are looking for very practical advice.I guess the question is like, how do you take a new piece of content, one of these problems, whatever it is. I guess, how do you keep finding new content is probably the better way to ask that question?Amy: Well, to just roll back just a little bit. My problem with bleeding edge content, I love watching it, but bleeding edge content will almost always be a product demo because it's someone who developed a new solution, and they want to share with everybody, which is just going to walk you through how it's used, which is great, except, and this is just a nature of what the cloud industry is like, all of this stuff, it changes day-to-day.These tools may not be applicable in a few months, or they may become the new standard. There's no way to tell until you're already six months out, and by then, they've already gone through several product revisions. I once did a talk where I was talking about best practices, and AWS released their updated best practices the day before my talk, and I had to update three slides. It threw off my timing, it was great.That's just one of those kind of pitfalls that you have to roll with. As far as getting new content, though, especially if you're dealing ... It depends who your audience is, because my audience tends to be either ICs or technical leads, and by then you're usually in a company ... If you're not developing these bleeding edge solutions, you're just using the tools that's out there already.You had brought up my "Serverless Frenemies," which is still my favorite title of any talk that I've ever made, because when I did the managing containers one, and I love all my Devro friends, but they all got into my mentions about why don't you just use Fargate? If you're at the containerization stage, why don't you just use Fargate, because it's not even close to the same thing, it is closer to Kubernetes than it is to Lambda, and I'm looking for a Lambda-like solution. That's what that whole deal was about, and I was able to stretch that out into I think 30 minutes because Twitter will tell you what's wrong, whether or not it's accurate or not, and whether or not they're actually your friends. They are my friends, but come on.Jeremy: Twitter can definitely be brutal. I think that, and maybe unpack a little bit what you were saying, is you're creating content around existing tools. One way to do it is, you're using existing tools, you're creating content around that, or you can create content around that. Looking at those solutions, you introduce a new solution to something, or you're even using an existing tool, nothing's perfect. You had mentioned that idea of bugs and so forth. But just, I guess new solutions, or just solutions, in general, maybe higher-level abstractions, everything creates some new type of problem that you have to deal with, and that's probably a pretty effective way to generate new content.Amy: It is. If you ever have to write down an RCA, which, for those who have not had the pleasure of doing one is called a root cause analysis, where you took down production, and you had to explain why.Jeremy: Yep.Amy: Or you ever did this, hopefully, in stage, or hopefully, in development where you ran into a situation where ... I had a situation once where Lambda would not delete itself. I call it my Skynet problem where it just hit a stage where it was both trying to save and delete at the same time. It would lock itself and I had to destroy the entire stack and send that command several times just to force that command through.If you ever have a problem like that, that is a thing that you write up instantly, and then you turn it into slide decks, and then you go to SlidesCarnival, you throw a very flashy background on it, and next thing you know, you have a TED talk, or a technical talk.Jeremy: Right. The other thing too, is, I find use cases to be an interesting, just like ... Non-traditional use cases are kind of fun too, how can I use this in a way that it wasn't meant to be used, and do something like that?Amy: I love those. Those are my favorite. I love watching people break away from what the tutorial says you have to do, and I'm going to get a little weird with it, and that to me is totally fascinating. When the whole, I fed these scripts into a computer meme came out, I thought that was super fascinating because that was something a company I had worked for did, they used analytics ... I used to work for Fantasy Sports, to write color commentary for your Fantasy Football team, and they would send it out.If you did really well, you would get a really raving review, and if you did really poorly, you would get roasted by a computer, and then that gets sent to everyone in the league, and it's hilarious. But that is not a thing that you would just assume a computer would do, is just write hot takes on your Fantasy Football team.Jeremy: That's ... Sure, go ahead.Amy: It's so much fun. I love watching people get weird with the tools that are there.Jeremy: There are times where you could do something like that, you could maybe create a content around some strange use case or whatever, and I love that idea of getting weird with that. The other part of it, though, is that, I guess, if you're sitting through a talk, and it's some super interesting problem that you're listening to, and again, I don't know, maybe it's some database replication thing, that you're just really into, whatever. That makes sense. But I think the majority of problems that developers have, are not that interesting, they're just frustrating.Probably the worst thing to do is wanting to sit through a talk that talks about some frustrating issue you have. Is there a way to basically say, "Look, I have a problem that I want to talk about. It's not the most interesting problem, but how can you flip that and take a problem that's not interesting and make it interesting?Amy: The batching containers and the frenemies talk was all based off of a bin library error from within the Lambda AMI. That, on paper is extremely boring, and should be a thing that you can easily look up, it is not. When I went around it trying to make tracking down library errors interesting, just saying it is very slow and can drain the energy out of your voice.But, I put a lot of energy into my work in general, and that's just how I had to approach pulling these talk is like, I like what I do, just, generally. When I try to explain what I do to people, it sounds super boring, and I own that. Now I'm doing it with spreadsheets, which is much, much worse. But when I tell people, it's not about the error itself, it's about everything that happened to make this one particular error happen. The reason why this error happened was because Lambda uses AWS's very specific Linux AMI when they did not used to, and they left stuff out for either security or performance purposes.Whether or not we as a group agree with that, that's a business decision that they made. How does their business decision affect your future business decisions and your future technical ones? Well, that becomes a way more interesting conversation, because it's like, we know this is going to break at this part, do we still want to use SSH? Do we still need it for this reason? You can approach it more from a narrative standpoint of, I wasted way too much time with this, did I need to? It's like, well, you shouldn't have, this should not have happened, but no bug should have happened, right?Jeremy: Right.Amy: You work through your process of finding a solution instead of concentrating on what the solution is because the solution they can look up in your show notes later.Jeremy: Right. No, I love that idea of documenting your process as opposed to just the solution itself. You find the problem, you pull the thread and where does that take you? I think to myself, a lot of times I go down the rabbit hole on trying to find the solution to a problem that I have or a bug fix, whatever. Sometimes, the resolution is underwhelming. Maybe it's not worth sharing. But other times, there's a revelation in there. I think you're right, with a little bit of storytelling, you can usually take that and turn that into a really interesting talk.Amy: One of the things it will also do, if you look at it from a process and from a narrative standpoint, is that when you take this video, and you send it to either a technical lead or a product manager, they'll understand what the problem was because you did not bog it down with code. There's very little live code in mine because I understand that people build things differently, just because every code is as different as every person. I get that and I've come to terms with it. This is the best way to share that information.Jeremy: Absolutely. All right, let's wrap up the idea of building talks. What is your advice to someone who is starting out new? What's the best way for them to get started, or what's just some general advice for people starting to build talks?Amy: The best content new engineers can do, and that's mostly because this is never the standpoint from which tutorials are ever written in, is that, as someone who knows very little of the way a language or a framework should work, write down your process, the entire thing on you getting either a framework onboarded, how you build, and a messaging system, things that people have written a billion times because chances are, one, you got that work from someone else's blog post or their documentation, and you can cite that. And two, when you do it that way, you not only get into the habit of writing, but you get in the habit of editing it in a way that makes it more palatable for people who are not in your specific experience.When you do it this way, people can actually see, from an outsider's perspective, exactly what is hard about the thing that they built, or what people who do not have a different level of experience are going through. If a tutorial is targeted at engineers who know where the memory leaks in PHP are, that's the thing that comes with experience, that is not the thing that can be trained.When a new engineer hits that point, and they found it in a new framework where you fix it, then you start knowing where to fix other problems. That way more senior engineers and more vetted people can learn from your experience, and then they will contact you and they will teach you how to find these issues, so you don't run into them again, and you end up with someone you can just bounce ideas off of. That's how you get pulled into these technical communities. It's a really self-healing process.Jeremy: Yeah. I love that. I think this idea of you approaching something from a slightly different angle, your experience, the way that you do it, the way that you see it, the way that you perceive the word or the next prompt that comes back, or how you read an error message or any of those things, you sharing your experience around that is hugely valuable to the people that are building these things. But also, you may run into problems that other people like you run into, and it's just ... Sometimes, all it takes is just a tiny twisting of the words, rearranging a sentence in a way that now that clicks with somebody where the other time it didn't. I love that.That's why I always encourage people, just even if somebody has written his content 100 times before, whatever slight difference there is in your content, that could have a powerful effect on someone else.Amy: Yeah, it really can.Jeremy: Awesome. All right, let me ask you a couple of questions about Lambda and Functions as a Service because I know that you spent quite a bit of time on this stuff. I guess a question, especially, maybe even from a cloud economist, what's next for Lambda and Functions as a Service? Because I know you've written about the Lambda containers, but what's maybe that next evolution?Amy: What AWS did recently when they released Lambda Containers is basically put it at feature parity with Azure and GCP, which already had that ability, they had either a function service or a function to Json service where you could upload your own container. They finally released the base image, where, granted, if you knew where to look, you could get it before, but they actually released it, and announced it to the general public, so you don't have to know someone in order to be able to use it.What I see a lot of people being able to do with this now is they really want to do local development testing, so they don't have to push anything to their account and rack up those charges, when all that you want to do is make sure that whatever one line update you made, actually worked and you didn't put the space or the cab in the wrong place, which is, I guess, how it works now and it takes down the entire stack, which again, we've all done at least once, so don't worry about it. If you've ever taken down production, don't worry, you're not the only one, I promise you. You can't throw a t-shirt into an empty conference room and not hit a dude who took down production. I'm going to save that for later.Local development testing, live simulation is a really big thing. I've seen asked to do full-on data science just on Lambda containers, so they don't have to use Kubernetes anymore, because speaking of cost stuff, it's easier to track cost-wise than Kubernetes is, because Kubernetes is purely consumption-based, and you have to tie a bunch of stuff together in order to make that tracking work. That would be great.I think from here on, and a lot of the FaaS changes, they're not going to be front ends anymore, it's all going to be optimizations by the providers, you're not going to see much of that anymore. It's not like before, where they would add three more fields and make a blog post about it. I think everything is just going to be tuning just from Lambda's perspective now. That and hooking it to more things, because they love their integrations. What good is Lambda if you can't integrate it yourself?Jeremy: Right, if you can't hook it up to events. It's interesting, though, this move to support containers as a packaging format. You're right, I think this has been available in IBM, it's been available in Google, it's been available in Microsoft, these capabilities have existed for a while to use a container, and again, that's a very overloaded word, I know, but to use that as a packaging format. But moving to that, the parity there with the other cloud providers is one thing, but who's that conversation for? Whose mind does that change about serverless, or FaaS, I guess.Amy: The security team.Jeremy: Security, okay.Amy: Because if you talk to any engineer, if it's a technical problem, they'll find a way to fix it. That's just the way, especially at the individual contributor level, that's how the brain works is like, oh, this is a small thing, I bet I can fix it with a few days, or a weekend. Weekend turns into a month, but that's a completely different problem. I've had clients who did not want to use Lambda because they could not control the containerization system. You would be pushing your code into containers that were owned by Amazon, and the way they saw that, they saw that as liability.While it does have some very strong technical implications, because you're now able to choose the kind of runtime you do, easier than trying to hamstring layers together, because I know layers is supposed to fix this problem, but it's so hard. It's so hard for something that you should be able to download off of Docker and then play with it and then put it back. It's so unnecessarily hard, and it makes me so angry.If you're willing to incur that responsibility, you can tweak your memory and you have more technical control, but also you have more control at a business level too, and that is a conversation that will go way easier as far as adoption.Jeremy: Right. The other thing, in terms of, I guess the complexity of running K8s or running Kubernetes is one of those things where that just seems like a lot of complexity. You mentioned the billing aspect of it and trying to track cost. Not that everyone's trying to narrow down exactly how much this Lambda container ran them, maybe you have more insight into that than I do, but the idea of just the complexity.It seems to me that if you start thinking about cost, that the total cost of ownership of running a container and a Lambda function or running it in Fargate, versus having to install and maintain ... I would say, even if you're using one of the managed services like EKS, or something like that, that the total cost of ownership of going down the serverless route has got to be better.Amy: Yeah, especially if you're one of these apps that are very user generater based. You're tracking mostly events and content, and not even a huge amount of content, you're not streaming video, you're sharing pictures, or sharing ... If you were trying to rebuild Foursquare, you would just be sharing Geo data, which is comparatively an extremely small piece of data.You don't need an entire instance, or an entire container to do that. You can do that on a very small scale, and build that out really quickly. That said, if you go from one of these three-person teams, and then there's interest in your product, for whatever reason, and it explodes, then not just your cost, but if you had to manage the traffic of that, if you had to manage the actual resources of that, and you did not think your usage would stick with your bill, that's not great.Being able to, at least in the first few years of the company, just use Lambda for everything, that's probably just a safer solution, because you're still rapidly iterating, and you're still changing things very quickly, and you're still transmitting very small bits of data. That said, it's like there are also large enterprise companies that are heavy Lambda users, and even their Lambda bill compared to their Kubernetes bill, it is ... If you round it to down there Kubernetes bill, you would get their Lambda bill.Jeremy: Right. Gotcha. I think that's really interesting because I do ... I actually would love to know your thoughts and whether you even see this. I don't know if we have enough data yet to know this, but this idea of using Lambda, especially early on in startups, or even projects within an enterprise, being able to have that flexibility and the low operational overhead and so forth, I think is really great. But do you see that, or is that something that you think will happen is, you'll get to a point where you'll say we've found some sort of stability point with this product, where we now need to move it over to something like Kubernetes, or a container management system because overall, it's going to end up being cheaper in the long run.Amy: What usually happens when you're making that transition from Lambda to either even ECS or Fargate, or eventually Kubernetes is that your business logic has now become so complex, or your infrastructure requirements have become so complex that Lambda can't do it cleanly anymore. You end up maxing out on either memory or CPU utilization, or because you're ... Apparently Lambda has a limit on how many times you can invoke it at the same time, which some people have hit in real life.Those are times when it stops being a cheaper solution, and it stops being a target solution because you can run your own FaaS environment within instances, and then you can have a similar environment to what you're building so you don't have to rebuild everything, but you don't have to incur that on-demand cost anymore. That's one path I've seen someone take, and that's usually the decision is that Lambda, before, when it was limited, can't hold it.Now that you can put your own container, so long as it fits in that requirement, you can pad that runway out a little bit, and you can stretch out how long you have before you do a full conversion to ECS environment. But that is usually how it is because you just try to overload or you have, maybe, 50 Lambdas trying to support one application, which is totally a thing you can do, it may not be the best ... Even with Step, even with everything else. When that becomes too complex, and you end up just going through containers, anyway.Jeremy: Right. I think that's interesting, and I think any company that grows to the point where that they need to start thinking about that next little infrastructure, it's probably a good thing. It's a good point to start having those conversations.All right, I got just one more question for you, because I'm really interested. You mentioned what you do as a cloud economist, reading through people's bills and things like that. Now, I thought Corey just made this thing up. I didn't even know this thing existed until, Corey comes out, and he probably coined the term. But in terms of that ...Amy: That's what he tells people.Jeremy: He does tell people that, right. I think he did. So, I will definitely give him credit there. But in terms of that role, of being a cloud economist and having to look through people's bills, and trying to find them ways to save it, that's pretty insane that we need people like you to do that, isn't it?Amy: Yes, it's a bananas job. I cannot believe this is a job that I'm actually doing. It's also a lot of fun. But if you think about it, that when I was starting out, and everything was LAMP stack, when I started. That was a hot new tech when I started, was the LAMP stack. The solution to all of those problems were we're going to throw more hardware at it. Then the following question was, why are we spending so much on hardware?Their solution to that problem was, we're going to buy real estate to store all of the hardware on. Now that you don't have to do that, you still have the problem of, I'm going to solve this problem by throwing more hardware at it. That's still a mindset that is alive and well, and you still end up with the same problem, except now you don't have the excuse that at least we own the facility that data is in because you don't anymore.Since you don't actually own the cases and the plates and everything, you don't have to worry about disposing of them and having to use stuff that you don't actually use anymore. A lot of my problems are, one of our services has gone out of control, we don't know why. Then I will tell you, who is spending that money. I will talk to that team to make sure that they know that it's happening because sometimes they don't even know what's happening. Something got spun up into their account, and maybe it was a testbed, maybe it was a demo, maybe they hired a vendor to load something into their environment and those costs got out of control.It's not like I'm going out trying to tell you that you did something wrong. It's like, this is where the problem is, let's go find out what happened. Forensic cloud bill person, I'm going to workshop that into a business card, because that sounds way better than the title that Corey uses.Jeremy: Forensic cloud accountant or something like that.Amy: Yes.Jeremy: I think it's also interesting that billing is, and the bills you get from AWS are a leading indicator of things that are potentially going wrong. Interesting, because I don't know if people connect this. Maybe I'm underestimating people here, but the idea that a bill that runs, or that you're seeing EC2 instances cost spiking, or you're seeing a higher load or higher bandwidth or things like that. Those can all be indicators of poorly written code, it can be indicators of the bad compression or missing compression settings, all kinds of things that it can jump out at you. Unless somebody is paying attention to those bills, I don't think most developers and most teams, they're not going to see that.Amy: Yeah. The only time they pay attention when things start spiraling out of control, and ... Okay, this sounds like an intuitive issue, and first thing people will do, will go, "We're going to log everything, and we're going to find out where the problem is."Jeremy: It'll cost you more money.Amy: There is a threshold where cloud watch becomes very expensive.Jeremy: Right, absolutely.Amy: Then they hit that threshold, and now their bill is four times as much.Jeremy: Right.Amy: A lot of the times it's misconfiguration, it's like, very rarely does any product get to the point where they just can't ... It's built so poorly that it can barely hold itself up. That's never been the case. It's always been, this has been turned off, or AWS also offers S3 analytics. You have to turn them on per bucket, that's not a policy that's usually written in anyone's AWS config. When they launch it, they just launch it without any analytics. They don't know if the thing is supposed to be sending things to Glacier, if it's highly used data, there's no way to tell.It's trying to find little holes like that, where it seems like it shouldn't be a problem, but the minute it becomes a problem, it's because you spent $20,000.Jeremy: Right. Yeah. No, you can spend money very, very fast in the cloud. I think that is a lesson learned by many, many people.Amy: The difference between being on metal and throwing hardware at a problem and being on the cloud and throwing hardware at a problem is that you can throw hardware at a problem at scale on the cloud.Jeremy: Exactly. Right. There's no stopping point like we have to go by using servers ...Amy: No one will stop you.Jeremy: No one will stop you. Just maybe the credit card company or whatever. Anyways, Amy, you are doing some amazing work with that, because I actually find that to be very, very fascinating. I think, in terms of what that can do, and the need for it, it's a fascinating field, and super interesting. Good for Corey for really digging into that and calling it out. Then again, for people like you who are willing to take that job, because that seems to me like poring through those numbers can't be the most interesting thing to do. But it must feel good when you do find a way to save somebody some money.Amy: Spreadsheets can be interesting. Again, it's like everything else about my job. If I try to explain why it's interesting, I just make it sound more boring.Jeremy: Awesome. All right. Well, let's leave it there. Amy, thank you again, for joining me, this was awesome. If people want to find out more about you, or maybe they have horribly large AWS cloud bills, and they want to check out the Duckbill Group, how do they do that?Amy: Honestly, if you search for Corey Quinn, you can find the Duckbill Group real fast. If you want to go talk to me because I like doing community engagement, and I like doing talks, and I like roasting people on Twitter just about different stuff, you can hit me up on Twitter @nerdypaws. If you want to be a professional, I'm also on LinkedIn under Amy Codes.Jeremy: All right, and then you also have a website, Amy-codes.com.Amy: Amy-codes.com is the archive of all my talks. It's currently only showing the talks from last year because for some reason, it's somehow became very hard to find a spot for the past year. Who knew?Jeremy: A lot of people doing talks. But anyways, all right, Amy, thank you again. Appreciate it.Amy: Thank you. Had so much fun.

Can you tell us a bit about your role as the Director of SW Modernization for the DoD? What does that entail?On the SW Modernization front, at a high-level, what are some of the primary SW modernziation objectives of the DoD?How does SW modernization tie into National Defense and why is it so critical to get right?There's an increased push to adopt DevSecOps, what are your thoughts on that and why there's such an interest among the DoD/Federal community?Jason Weiss Bio: Jason Weiss has an exceptional background in software engineering, cryptology, and computer security dating back to his service in the US Navy as a cryptologist during the first Gulf War. He is the author of Java Cryptography Extensions, published by Morgan-Kaufman, and co-author or contributor to several other books on distributed computing. He is the sole inventor of the patented Volume Mount Authentication endpoint security algorithm that was eventually integrated into Seagate’s DriveTrust technology, and co-inventor of the Cloud Connected Transponder. In 2000, the NSA recognized Jason as a talented security designer of critical infrastructure protection. He has lectured internationally, including presentations at SD West, Sybase TechWave, Rocky Mountain Java Symposium, AnDevCon, AWS Summit, and various keynotes on NFC and RFID at events like the WIMA European NFC Developers Summit in Monaco. As Director of Software Modernization in the Office of the Secretary of Defense, DoD CIO, he executes critical activities to both maintain and modernization the DoD Information Enterprise, including the department’s push to adopt DevSecOps. Jason holds a BS in computer science and an MA in Intelligence (Information Warfare).

En este episodio te contamos todo lo que tenes que saber de la nueva edicion del AWS Summit 2021 para LATAM Material Adicional: https://register-summit-amer.virtual.awsevents.com/?lang=es

En este es el segundo episodio del Podcast de AWS en Español.En este episodio, te contamos todo los tips que necesitas saber para crear una cuenta de AWS de forma segura y para estar preparado para que tu cuenta pueda crecer.00:00 - Bienvenido al podcast01:15 - Invitación al AWS Summit online (17/6)07:50 - Cómo crear una cuenta en AWS y todo lo que hay en relación a ello29:30 - Todo sobre el soporte de AWS40:25 - Necesitamos múltiples cuentas de AWS?47:15 - Estrategias para asegurar el acceso a la cuenta de AWS56:40 - Formas de acceder a la cuenta de AWS01:04:32 - En el próximo episodioLinks mencionados en este episodio:- Registrate al AWS Summit online: https://aws.amazon.com/events/summits/online/emea/- Información sobre la capa gratuita de AWS: https://aws.amazon.com/es/free/- Calculadora de precios: https://calculator.aws/- Información sobre soporte: https://aws.amazon.com/es/premiumsupport/plans/- Tareas que solo podes hacer con tu root account: https://docs.aws.amazon.com/general/latest/gr/aws_tasks-that-require-root.htmlSi tenés alguna consulta o querés que tratemos algún tema en particular dejanoslo en la cajita de comentarios.Podes encontrar el podcast en este link: https://aws-espanol.buzzsprout.com/O en tu plataforma de podcast favorita. También podes ver este episodio y otros en youtube: https://youtu.be/k69OGQoHIzc

Chris and Tim discuss the adage "Good coders borrow, great coders steal." They also talk about the term refactoring and why you should add that to your development routine. 0:50 Monkey rides a motorcycle 2:26 AWS Summit 4:05 Good coders vs. Great coders 5:50 Copy/Paste from Stack Overflow 7:14 Slippery slope 10:33 Solutions up-voted 12:27 Common libraries and utility solutions 14:32 Don't have to write/maintain/source control 15:52 Security - Beware of what you don't understand 16:51 Credit your original source 18:23 Smart consumer 20:13 No original ideas 23:43 Picasso said it?!? 27:22 Uber-fication 29:51 DON'T STEAL INTELLECTUAL PROPERTY!!! 30:50 Refactoring stories 37:11 Refactor, what is it good for? 40:17 The REAL definition 44:08 Simplicity 45:43 Give something a name 47:23 Why did you delete that? 50:48 Measure your code quality Article in the discussion https://stackoverflow.blog/2020/05/20/good-coders-borrow-great-coders-steal/ Refactoring https://refactoring.com/ Clean Code https://play.google.com/store/books/details?id=_i6bDeoCQzsC&gl=us&hl=en-US ~ Social Media ~ https://twitter.com/forloveofcode https://www.instagram.com/forloveofcode/ https://www.linkedin.com/company/forloveofcode https://www.facebook.com/forloveofcode

theCUBE host Stu Miniman (@stu) is joined by Corey Quinn (@QuinnyPig) and shares his analysis on AWS Summit online 2020To see more of our coverage of this event, please visit: https://www.thecube.net/aws-global-2020

Chris and Tim talk about beard and hair styles, recent AWS Summit 2020 and working remote. The MAIN topic is what is "Agile"...hint, you're probably already doing some of it. 0:35 Nice Hair...Nice Beard 2:00 AWS Summit review 6:56 Why not the cloud? 11:19 Do you want to babysitting servers? 14:52 What's your disaster plan? 17:08 We're not a technology company? 20:29 What are you measuring 28:41 Starting out with Agile 30:26 Who started it?...Open invitation 30:59 Customer satisfaction MVP 32:38 Welcome changing requirements 33:12 Frequent deliveries 33:31 Business people and developers 34:06 Be Motivated 34:44 Measuring progress 35:00 Sustainable pace 35:24 Technical excellence 35:38 Simplicity 35:48 Self-Organizing team 36:04 Meet regularly and adjust 37:22 Agile vs. Waterfall...fight 41:26 Why should a developer be Agile? 47:59 There's no "I" in Team 53:27 Project managers fire drills 59:10 Post-it note priorities 1:02:24 Product owners care 1:06:33 Renaissance 1:08:13 Building a house 1:12:43 Demo it!! Principles behind the Agile Manifesto https://agilemanifesto.org/principles.html Lean manufacturing https://en.wikipedia.org/wiki/Lean_manufacturing Scrum tutorial with actionable tips from experts https://www.knowledgehut.com/tutorials/scrum-tutorial ~ Social Media ~ https://www.youtube.com/channel/UCNkxIgOcBf04Li83x7Lys0A/ https://twitter.com/forloveofcode https://www.instagram.com/forloveofcode/ https://www.linkedin.com/company/forloveofcode https://www.facebook.com/forloveofcode

theCUBE hosts John Furrier (@furrier) and Stu Miniman (@stu) share their analysis in this weeks theCUBE InsightsTo see more of our coverage of this event, please visit: https://www.thecube.net/aws-global-2020

In this episode, Rick Vanover (Twitter @RickVanover) finds time for a chat with Eric Wright (Twitter @discoposse). Eric blogs at Discoposse.com and is an avid community member for many projects. Rick and Eric discuss a few cool projects, including a presentation he gave at the AWS Summit in Toronto around Open-source Infrastructure-as-Code with Terraform and AWS. The content is compelling! Additionally, Eric summarized a recent milestone with Virtual Design Master.

theCUBE hosts Stu Miniman (@stu) and Corey Quinn (@QuinnyPig) share their analysis of the Opening Keynote and discuss the AWS ecosystem at large from the 2019 AWS regional summit in NYCTo see more of our coverage from this event, please visit: https://www.thecube.net/aws-nyc-2019

CUBE hosts Susannah Streeter (@Streeternews) & Dave Vellante (@dvellante)  kickoff AWS Summit London 2019 from ExCeL London, in London, UK.To see more of our coverage of this event, please visit: https://www.thecube.net/aws-summit-london

stdout.fm 25번째 로그에서는 ICT 업계, 마켓컬리, 주니어 채용에 대해서 이야기를 나눴습니다. 참가자: @seapy, @raccoonyy 게스트: @chiyodad, @ecleya 마켓컬리 :: 내일의 장보기, 마켓컬리 정보통신기술 - 위키백과, 우리 모두의 백과사전 뇌를 자극하는 Java 프로그래밍 전사적 자원 관리 - 위키백과, 우리 모두의 백과사전 SAP Software Solutions | Business Applications and Technology Finance for Small-to-Medium Businesses (SMB) | Oracle Cloud 더존ICT그룹 ERP 모든 기능 월4만원 | 웹기반 이카운트 ERP 국제회계기준 - 위키백과, 우리 모두의 백과사전 ABAP - 위키백과, 우리 모두의 백과사전 Oracle Forms 이상한모임 마켓컬리 :: 내일의 장보기, 마켓컬리 창고 관리 시스템 - 위키백과, 우리 모두의 백과사전 후배 개발자에게 - 2019년 Spring Spring Boot eGovFrame Portal 온라인 지원 포탈 Java version history - Wikipedia 마켓컬리, ‘살충제 계란’ 파동 이후 계란 판매량 2배 증가 퀄리티 있게 새벽배송, 마켓컬리 샛별배송 (30s) - YouTube 전지현 효과를 톡톡히 본 네이버 (NAVER)의 1999~2019년도별 CF 광고 모음 - YouTube CUBRID | Enterprise Open Source DBMS garden5 샛별배송 & 택배배송 :: 내일의 장보기, 마켓컬리 로켓프레시 - 쿠팡! NE.O.002 쓱배송 굿모닝 - 이마트몰, 당신과 가장 가까운 이마트 스티로폼 박스, 아이스팩 회수 서비스 안내 :: 내일의 장보기, 마켓컬리 저온 유통(콜드 체인) - 위키백과, 우리 모두의 백과사전 GS25, 1600원 반값 택배 내놨다 - 매일경제 ‘1시간 내 배송기사가 집으로’…SK·GS, 주유소 택배 ‘홈픽’ 내놨다 에코박스v2 시범 운영 안내 :: 내일의 장보기, 마켓컬리 (일본어) 쿡패드 주식회사 - 주방을 갖춘 오피스, 그 진의를 찾아서! Careertasu LINQ 매거진 OnDemandKorea 제주 목초 우유 :: 내일의 장보기, 마켓컬리 검색결과: 이베리코 :: 내일의 장보기, 마켓컬리 검색결과: 이유식 :: 내일의 장보기, 마켓컬리 AWS Summit 서울 행사가 시작됩니다! - 2019년 4월 17일-18일 DEVIEW 2018 컬리 신사사옥 카카오 T | 카카오 주식회사 모두의캠퍼스(모두의캠퍼스) 기업, 채용, 투자, 뉴스 - 로켓펀치 신입개발자가 스타트업에서 AWS로 어떻게든 살아가는 썰 Fizz buzz - Wikipedia DHH on Twitter: “Hello, my name is David. I would fail to write bubble sort on a whiteboard. …” 프로그래머스

פרק מספר 365 (מספר קוסמי!) של רברס עם פלטפורמה - קרבורטור מספר 26: אורי ורן מארחים את נתי שלום (היזם של חברת Cloudify) לשיחה התקופתית על קוד פתוח, עננים, תשתיות ואירועים מהתחום מהזמן האחרון.קצת רקע להיום: ב - 11 למרץ 2019 פורסמה הודעה של AWS על התאגדות משותפת עם מספר חברות (בינהן Expedia ו-Netflix), על מנת לקחת מוצר בשם Elastic Search (חברה שהיזם שלה ישראלי, תזכורת לפרק 362 עם אורי כהן, וגם התגובה של שי בנון המייסד) וליצור עבורו מודל הפצה חדש (Re-distribution), מה שמרעיד את אמות הסיפין בתחום ומעורר לא מעט שאלות.נתי גם אמר את זה קודם . . .הנושא הציף קודם כל את הבלבול שקיים סביב המודל העסקי של חברות קוד פתוח והאופן שבו הן מייצרות רווח - נכון עבור Elastic אבל באותה מידה גם עבור Redis או GitHub וכו’.כל המוצרים של החברות הללו מגיעים מחברות ממומנות ולמטרת רווח ישיר, בשונה למשל מפרויקט כמו Kubernetes, שגוגל מעודדת על מנת לעודד צריכה של Google Cloud (ומשם לייצר רווח “משני”).יש מספר דרכים לרווח ישיר ממוצר קוד פתוח - רישיון שימוש (Subscription license)שירות כ-SaaS (ותשלום לפי צריכה)שירות מנוהל (Managed Service) - דומה ל-SaaS, רק שיש אפשרות גם להריץ בעצמךתשלום על תמיכה ו-Extra Featuresנקודה עדינה, כי יש גבול דק שקל לעבור ולהפסיק להיות “באמת” קוד פתוח. כל ה-API למפתחים חייבים להיות פתוחים, אבל תחומים של Clustering או Security למשל כבר נחשבים כ”איזורי מוניטיזציה” - זה כבר לא POC או פיתוח אלא שימוש משמעותי שמצדיק תשלום.ההבדל המשמעותי לעומת “קוד סגור” הוא היחס שבין הספק ללקוח - צריך לשלם, אבל לא מיד ברגע שנוגעים במוצר אלא רק כשיש ערך ברור.חשוב לשים לב שגם צד הלקוח מעוניין הרבה פעמים בתשלום כלשהו עבור שימוש משמעותי - יוצר מחוייבות לתמיכה (או לפחות תחושה כזו) ואומר שיש מישהו מאחורי המוצר שיכול לתמוך במקרה הצורך.זו מערכת מבוססת אמון (Trust system) - ויש מגוון סוגי רשיונות שמגדירים מה מותר לעשות עם החלק הפתוח (החינמי)הרשיון “המתירני” ביותר נקרא Apache 2.0, שמאפשר כמעט הכל (כולל re-distribution) והרבה ארגונים משתמשים בו, גם מתוך חשש מרישיונות כמו GPL למשל, שאומר שאם מבצעים שינוי בקוד חייבים לשתף גם אותו (מה שעשוי להיות קשה לשליטה ובעייתי באופן כללי לארגונים גדולים).למיטבי לכת (ושמע) - היה פרק שלם גם על זה עם עו”ד(!) דביר גסנר (ב-2012, ועדיין), ועוד אחד על רשיונות קוד פתוח (פרק 211 מ-2014), וגם זהר זקס הרחיב על הנושא בפרק 317 על Zusammen. הרבה שיעורי בית.בשורה התחתונה - חברות פחדו ממצב בו מפתח בודד יעשה שימוש בקוד עם רישיון שמעבר ל-Apache 2.0 (או MIT License שהוא די מקביל) ויחייב את החברה לשיתוף שהיא לא יכולה לעמוד בו.השוני הגדול הוא בעיקר בזכויות ההפצה (Re-distribution) ושימוש כ-SaaS.העיקרון הבסיסי הוא שהפרויקטים הללו דורשים הרבה מאוד השקעה, חדשנות וטכנולגיה, ועומדות מאוריחהם חברות גדולות שבסופו של דבר צריכות מודל עסקי על מנת להתקיים ולהרוויח (ולהנפיק…).לא צריכה להיות סתירה בין זה לבין טובת המשתמש, שעדיין נהנה ממוצר באיכות מאוד גבוהה בחלק הפתוחשונה מפרוייקטים שמבוססים לחלוטין על  תרומות קוד של משתמשים, מה שעובד לרוב רק כשיש חברות שמאגדות את הפרוייקט על מנת להפיק ערך באופן אחר (שוב - דוגמת Kubernetes ו-Google).אז בחזרה לשאלה המקורית -  למה רעדו אמות הסיפין?המרכיב הראשון הוא עניין האמון - ברגע שיש שימוש משמעותי במוצר צריך להתחיל לשלם. מה זה “משמעותי”? בדיוק . . .אם אני עושה שימוש משמעותי בקוד הפתוח, אבל גם מאפשר להשתמש בו בחינם (או לקבל תמיכה בחינם וכו’), נוצרת פגיעה בחברה שפיתחה את הקוד, ולא נהנית מרווח בשלב בו הוא הופך ”לגיטימי”אם נוסף על כך את העובדה שזה קורה בפרויקט שבו לא תרמתי למוצר מלכתחילה, ורק אפשרתי שימוש משמעותי בחינם - נוצר משבר אמון עמוק.אז AWS.משמעות ההודעה של AWS היא שעבור מוצרי קוד פתוח שהם לא באמת תרמו לפיתוחם, הם חותכים את קווי המוניטיזציה - על מנת להנות מהשימוש הרב בהם (להנות מהרווח הנגזר מהשוק שגדל, בלי להשקיע בשלב הראשון של יצירת ופיתוח השוק).נותנים שירות ותמיכה לחלק החינמי של השירות - ובפועל מתחרים בחברה המפתחת על התמיכה במוצר (החינמי) שלה, אותה תמיכה שהרווח הפוטנציאלי ממנה היה הבסיס והתמריץ לפיתוח.הדרך של החברה להגיע למשתמשים הייתה, למשל, לאפשר שירות במודל SaaS על התשתיות של AWS (שמרוויחה כבר בשלב הזה, אבל זה ממודל אחר), ולהרוויח מתמיכה. בשלב הזה נכנסת AWS שוב, ומתחרה בחברה המפתחת על תמיכה במוצר הקוד הפתוח שלה.מעבר ל- Elastic Search היו מקרים דומים גם עם MongoDB ו - Redis, וגם עם InfluxDB - שהגיבו ע”י שינוי מודל הרשיונות שלהן. יש הרבה דוגמאות כאלה עם AWS, שמאוד עקבית במדיניות הזו.התגובה הסטנדרטית של AWS במקרים כאלה היא שהם רוצים לתת שירות טוב יותר למשתמשים - ועבור הלקוחות יש לכאורה שירות יותר טוב במחיר יותר נמוך.האם באמת יש כאן Win-Win? שאלה טובה, נחזור אליה.אז הכל היה כבר קודם - מה קרה עכשיו ששונה?נחזור לכותרת של הפוסט - “Keeping Open Source Open – Open Distro for Elasticsearch”נכתב ע”י Adrian Cockcroft, ארכיטקט Cloud ב-AWS, בעבר גם ב-Netflix, ביקר בארץ באמצע מרץ (Keynote speaker ב- AWS Summit 2019, אפשר גם להשלים בוידאו).מאז היו עוד פרסומים.נתפס כמעיין “הרצחת וגם ירשת?” . . . יש כאן  מתקפה על חברות הקוד הפתוח בטענה שהן לא באמת מספקות קוד פתוח (כי הן מרשות לעצמן לרצות להרוויח), והצגה של AWS ככזו (בזמן שרוב המוצרים שהיא מפתחת בעצמה אינם בקוד פתוח כלשהו).הטענות שעולות בפוסט הן ש-Elastic במשך הזמן הוסיפו סעיפים שהופכים את הקוד ללא באמת פתוח, יחד עם הדוגמא של Java (סיפור ה-End of Life מבחינת אורקל, כש-AWS “ראו את טובת המשתמשים” והחליטו להמשיך ולתמוך).בשורה התחתונה - לא רק לקחו “פרי בשל” של חברה אחרת, אלא גם הטיפו מוסר. אין כאן שום דבר לא חוקי, אבל נראה לא משהו בכלל.הסכנה לטווח הארוך היא פגיעה בשוק הקוד הפתוח לטווח הארוך - משקיעים מתחילים לשאול איך (ואם בכלל) אפשר למנוע מ-AWS לעשות מהלכים כאלה בעתיד?התשובה הפשוטה - להשתמש ברשיונות פחות פתוחיםרואים את זה כבר עם Elastic ועם MongoDB, שמתחילות להגן על עצמן מפני הפרות אמון כאלו, מה שהופך את הדיון לכללי יותר, עבור כלל התעשייה: איך בונים יחסים של Win-Win בין ספקי הקוד הפתוח לספקי תשתיות הענן (Cloud Providers)?האם הכיוון הוא חרם צרכנים? - מי בדיוק יחרים? . . .אם חברות הקוד הפתוח לא ישתמשו ב-AWS, הם יעשו את זה בעצמם. נראה ש-AWS מפסידה בעצמה כי ככל שיותר חברות קוד פתוח ישתמשו בתשתיות של AWS כך היא תרוויח.זו לא באמת שאלה של מי צודק, אלא שאלה של טובת הצרכן לנוכח ניגוד האינטרסים.שווה לשאול מה קורה עם מוצרים שאינם קוד פתוח - תוכנות Microsoft למשל.כאן ב-AWS ידעו למצוא מודלים של Win-Win עבור כל הצדדיםלכאורה ההבדל היחיד הוא שבמקרה של קוד פתוח יש פירצה משפטית (או מערכת מבוססת אמון) שמאפשרת לעקוף את זה, וניצלו אותה.יכול להיות שהדרך היא להסתכל באותה צורה גם על חברות קוד פתוח וגם על חברות “מסורתיות” (ראה מקרה Oracle).ההבדל הוא שבמקרה של קוד פתוח, AWS לכאורה מספקים את השירות בחינם (הם עדיין מרוויחים על התשתיות).כל זאת - בזמן שעל AWS רצים יותר שרתי Windows מכל מערכת אחרת (ע”פ Adrian Cockcroft ב-AWS Summit בתל אביב), וכולם מרוויחים יפה.בזמן שעל Azure רצים עם Linux . . .כל ההבדל הוא הפירצה, והיכולת לנצל אותה.אין משקיע שישקיע בחברה ללא כל סיכוי לרווח כלשהו. המודל אינו התנדבות מלאה (לא מודל בר-קיימא בכל אופן).זה בסדר להשתמש בקוד פתוח ולא לשלם, וזה אכן נכון ל-90% מהמשתמשים. השאלה מה קורה כשמגזימים.אם למשל Outbrain משתמשים ב-Hadoop בלי לשלם (לשימוש פנימי), זה כנראה בסדר - כי הם לא מוכרים את המוצר, ולא מתחרים ביצרן - וזה גם כנראה נלקח בחשבון במודל העסקי של היצרן.זה לא המקרה עם AWS, וזה ההבדל הגדול - זה לא שימוש פנימי אלא תחרות ביצרן: הצעה של חלקים גדולים מאותו שירות לאותו בסיס לקוחות, עם התשתיות האדירות של AWS ובלי הוצאות

stdout.fm 22번째 로그에서는 Write the Docs 후기, 애플 이벤트(애플 TV+, 애플 카드 등), 파이어폭스 계정 멀티 컨테이너에 대해서 이야기를 나눴습니다. 참가자: @seapy, @raccoonyy, @nacyo_t 게스트: @ecleya(후얌얌) Write The Docs 서울의 2019 첫 번째 밋업 | Festa! Write The Docs Seoul (@WTDSeoul) | Twitter To. 지식 공유를 시작하려는 개발자에게 - LINE+ 홍연의 AWS Summit 서울 행사가 시작됩니다! - 2019년 4월 17일-18일 Apple Arcade - Apple Apple TV+ - Apple Highlights from Apple’s keynote event - Apple Khal Drogo - Wikipedia Amazing Stories (TV series) - Wikipedia HBO Now Game of Thrones - Wikipedia The Inventor: Out for Blood in Silicon Valley | Documentaries | HBO Disney+ 소개 List of original programs distributed by Apple - Wikipedia 푹 (POOQ) TVING｜TV를 더 즐겁게 iTunes - Apple Music - Apple (KR) Amazon.com: Prime Music Apple Card - Apple 코스트코 현대카드 출격…적립혜택 2배로 | 한경닷컴 제로페이 국제 - ‘지갑 없는 사회’ 도래…얼굴로 결제한다 - YTN 今日头条 SmartNews The Wall Street Journal & Breaking News, Business, Financial and Economic News, World News and Video Readr | 10,000+ Magazines, One Subscription 無異 on Twitter: “애플 news+ 기존 pdf 잡지 구독 서비스와 차이점 …” 국세청, 구글코리아 세무조사…구글·아마존 과세 ‘신호탄’(종합) - IT조선 なぜAmazonは日本で法人税を払わずに済むのか？ 元国税職員が解説 - まぐまぐニュース！ Tree Style Tab – Get this Extension for

Themen diesmal: Besuch beim AWS Summit 2019 (viel Machine learning), EU-Uploadfilter-Update (so schwer wiegt Artikel 13), Elektrokleinstfahrzeugeverordnung (keine E-Roller ohne Erlaubnis fahren!), der neue Inclusive Internet Report 2019

stdout.fm 15번째 로그에서는Seocho.rb 첫 번째 모임, AWS 람다를 사용한 이미지 변환, 안전한 패스워드 관리, 1Password 등에 대해서 이야기를 나눴습니다. 참가자: @seapy, @raccoonyy, @nacyo_t Patreon: stdout.fm 정기 후원 Seocho.rb 첫 번째 모임: 서버리스 루비 | Festa! 대안언어축제 - anpshare 캐시노트 - 가장 쉬운 매출관리 캐시슬라이드 - 모바일 혜택의 시작 프로그래머스 기계인간 on Twitter: “판교에서 본 프로그래머스 구인 광고. @codingwarrior_… “ 룩핀 AWS Lambda@Edge에서 실시간 이미지 리사이즈 & WebP 형식으로 변환 – 당근마켓 팀블로그 Lambda@Edge - AWS Lambda 왜 굳이 도커(컨테이너)를 써야 하나요? - 컨테이너를 사용해야 하는 이유 | 44bits.io AWS Lambda를 이용한 이미지 썸네일 생성 개발 후기 – 당근마켓 팀블로그 서버 비용을 70%나 줄인 온디맨드 리사이징 이야기 - VCNC Engineering Blog WebP - Wikipedia Home | Google Summer of Code ZZERJAE – Devlog Planet Hackathon 2018 by GDG x 9XD - Goree HackerX Accept HTTP 요청 헤더 | MDN AWS Summit 2019 커뮤니티 트랙 발표 신청 The Worst Passwords of 2018 100-50 | SplashData xkcd: Password Strength 가장 안전한 비밀번호 관리 솔루션 | 1Password NIST’s new password rules – what you need to know – Naked Security Password strength - Wikipedia 가장 안전한 팀용 비밀번호 관리 솔루션 | 1Password Exclusive: Apple to deploy 1Password to all 123,000 employees, acquisition talks underway – BGR (일본어) Apple은 패스워드 관리 애플리케이션 1Password를 전 사원에게 배포했나 | gori.me Hands-on with 1Password and iOS 12’s Password AutoFill feature - 9to5Mac Publisher Sign Up | CJ Affiliate by Conversant (Formerly Commission Junction) LessPass 1Password Watchtower 범죄 악용 ‘알패스’ 결국 서비스 종료…이스트소프트 “보안이슈 때문 아냐” You should change your Twitter password right now | TechCrunch Mac에서 Touch ID 사용하기 - Apple 지원 Mac에서 FileVault를 사용하여 시동 디스크 암호화하기 - Apple 지원

Featured on this episode: Highlights From Inspire & AWS Summit, Layering, IoT Fun & More

CUBE hosts John Furrier (@furrier) and Jeff Frick (@JeffFrick) break down the keynote session at AWS Summit 2018 NYC in New York, NY. To see more of our coverage from this event, please vist: https://www.thecube.net/aws-ny-2018

JOHANNESBURG — Last week, I attended the Amazon Web Services (AWS) Summit in Cape Town. It was the third event of its kind in the city and the attendance has surged from around 600 IT developers several years ago to over 2,000 last week. It's no surprise that demand for the event is on the rise, especially as Amazon's presence in Cape Town has quietly grown, apparently to several thousand staff. Of course, Amazon's growing South African base didn't come about by accident. It started with South African Chris Pinkham who set up an Amazon office in Cape Town in 2004. Pinkham, an internet pioneer in South Africa, was previously VP of Engineering at Amazon and a legendary player behind the company's foray and explosive rise in the cloud market. He would also go on to become VP of Engineering at Twitter for a brief period as well. At the AWS Summit then, I sat down with Geoff Brown, the Sub-Saharan Africa Regional Manager for Amazon Web Services, to chat about the company's presence and future plans in South Africa and the rest of the continent. - Gareth van Zyl

In this episode of Newy Tech People, I chat with Mat Finch from NIB and recent speaker at the AWS Summit in Sydney.

00:00:00 Intro Johan 00:03:32 Wat doet de CTO van Mendix? 00:06:12 Systeemarchitectuur volgt organisatiestructuur 00:07:13 AWS Summit event en cultuur 00:10:20 RAMPS 00:22:22 Product bedenken en lanceren 00:30:00 Microservices 00:45:00 Smart apps en AI 00:48:44 Mendix Assist demo! 00:57:43 Nieuwe releases en mosted loved IDE 01:04:23 Mendix World   01:08:24 Appstore update 01:09:20 Afsluiting Shownotes: AWS summit event Cultuur; volgens Werner is cultuur belangrijk binnen een tech bedrijf om succesvol te zijn Product bedenken en lanceren; Volgorde nav fireside chat met CTO Amazon; working backwards: Blog Werner: https://www.allthingsdistributed.com/2006/11/working_backwards.html Visie Smart apps https://www.mendix.com/smart-apps/ Machine Learning / AI /   Appstore connectors Mendix Assist! https://www.mendix.com/blog/introducing-ai-assisted-development-to-elevate-low-code-platforms-to-the-next-level/ Microservices https://www.mendix.com/blog/can-build-low-code-platform/ Apps voor innovatie, Apps om je te onderscheiden van de rest en Apps voor core systemen. Data makkelijk kunnen gebruiken van andere apps/microservices Meer automatisering in deployment (CICD) Afgelopen releases 7.14 en 7.15 7.14 Highlights, nieuwe layout is heel goed aan te wennen; je brein kan dat gewoon :) 7.15 Blogposts over release: https://www.mendix.com/blog/7-15-release-sharpening-the-saw/ Events Microservices meetup geweest in Rotterdam Mendix On Tour Omnext meetup Amersfoort Tips/ Widgets / Modules https://appstore.home.mendix.com/link/app/106254/Mendix/Grid-Cell-Styler Johan kun je volgen op: Twitter @JohanDenHaan https://twitter.com/johandenhaan LinkedIn: https://www.linkedin.com/in/johandenhaan/ Blog: http://www.theenterprisearchitect.eu/blog/

CUBE hosts John Furrier (@furrier) and Stu Miniman (@stu) kickoff our coverage of AWS Bay area Summit with an in-depth look at the keynote presentation and how AWS stacks up with it's competition in 2018 with Microsoft quickly growing in market share. To see our coverage of AWS Bay area Summit please visit: https://www.thecube.net/aws-sf-2018

The future is here and it's called AWS.   I decided to attend the AWS Summit in San Francisco this week on a whim -- I am not a developer and have no intention of becoming one but as a small biz owner and leadership specialist, I believe it's important that everyone has a basic level of understanding around what this mega company known as Amazon is up to.   Long story short:    Mind. Blown. AWS stands for Amazon Web Services and it is true to its namesake. I had the chance to listen to Werner Vogels, Amazon dot com's CTO and Vice president speak about big things happening with AWS and my mind is still reeling from what I learned. In today's audible, you will hear me share 10 leadership lessons I learned from going to this summit. I recorded those lessons on my iPhone in my hotel room right after getting back from the event. You will hear that I sound a bit fatigued after a full day at the Summit, but also A LOT of excitement about what's happening with this company. If there's one thing I can stress here it's that AWS is laying the groundwork to change the way companies function. Cloud computing is here and we are just at the early stages of what's possible. As a futurist, as a business woman, as a podcaster, as a writer... what AWS is doing thrills me even if I don't understand most of the technical jargon! I hope my takeaways give you something to think about and use as you continue your journey. Enjoy today's Audible, Team PYP! Let me know what you liked. Connect with me on social media and use the hashtag #pyp ! Twitter   LinkedIn Instagram Facebook   PYP Leadership Academy

Show Description: Brian and Tyler discuss some of the use-cases that businesses have for using Kubernetes. They review several public examples of Kubernetes uses, both in web scale and Enterprise environments. Show Notes:GitHub Goes All-In on Kubernetes (via TheNewStack)KubeCon / CloudNativeCon CFP is Due August 21stSegment 1 - Thank you for the great response to the initial show. Response has been very positive and we’ve already had like 8-10 people ask to be guests on the show. The challenge is to figure out what to do on show #2 or #3 since there is so much happening. So we’ve decided that for a while, we’re going to make sure that we cover all the fundamentals of containers and Kubernetes. Segment 2 - News of the WeekGitHub announces details of how they use Kubernetes AWS does not announce a Kubernetes services at AWS Summit in NYC KubeCon CFP is due by August 21stSegment 3 - How are companies using Kubernetes?daemonSets (instance on each node), replicaSets (specific # is always running), jobs (run to completion), statefulSets (stateful apps) vs persistent Volumes (stateful storage) Kubernetes Job Openings Customer sessions at Red Hat Summit OpenShift Commons Gathering (videos) Kubernetes Case-Studies Segment 4 - How to Learn MoreFree Kubernetes Training from CNCF Kubernetes by Example (Michael Hausenblas) How does the Kubernetes scheduler work? (Julia Evans) Kubernetes the Hard Way (Kelsey Hightower) Segment 5 - Question(s) of the Week Q1: What’s the right way to install Kubernetes? There seem like too many options. A1: Kubernetes: A Little Guide to Install Options Feedback?Email: PodCTL at gmail dot comTwitter: @PodCTL Web: http://PodCTL.com

On this weeks episode we are lucky to be joined by Jason Marden, to discuss the world of Amazon Web Services. We start off the show talking about Jason’s recent visit to the AWS Summit in London, and what the talking points were from the conference. From here we delve into the Serverless Architecture, how AWS Lambda is paving the way of FAAS, containers and view-based aggregation services. The Immutable Server is next brought up, highlighting the change in deployment philosophy that can be achieved by using such a concept. Finally, we discuss the value of a good debugger, bringin’ back awesome screen-savers and the craze of Pokemon Go.

A round-up of the latest AWS news, services and feature updates and expert tips for cloud enthusiasts, IT professionals and developers, delivered by AWS subject matter experts.