Podcasts about principal software engineer

In this special in-person episode, Sanne Grinovero shares the story of Java's evolution from his unique perspective as a long-time open-source contributor. He shares his 16-year career journey at Red Hat, highlighting his amazing work on key projects like Hibernate, Infinispan, and especially the creation of Quarkus. His career trajectory, from a student who initially disliked Java's complexity to a leading figure in its modernization, shows the transformative power of open source.A key part of the conversation focuses on how technical challenges spark innovation. Sanne explains how the task of making the popular Hibernate framework compatible with GraalVM's limitations led directly to the birth of Quarkus. This journey tells the bigger story of how Java adapted for cloud-native development, ensuring it continues to be a top choice for developers seeking high performance and a great developer experience.  Timestamps:(00:00:00) Trailer & Intro(00:02:16) Career Turning Points(00:04:52) Winning an Innovation Award(00:06:35) Java Heroes(00:08:04) Working as a Consultant(00:09:56) Taking a Massive Pay Cut to Work on Open Source(00:10:59) Contributing to Big Open Source as a Youngster(00:12:53) State of Hibernate Project(00:15:15) Spring Boot(00:16:54) Making Hibernate Work on GraalVM(00:21:05) GraalVM Limitations for Running Hibernate(00:26:09) Java for Cloud Native Application(00:28:04) Quarkus vs Spring Boot(00:33:21) JRebel & Quarkus(00:34:35) Java vs New Programming Languages(00:39:22) The ORM Dilemma(00:42:38) Some Hibernate Design Pattern Tips(00:46:40) Getting Paid Working on Open Source(00:48:41) Hibernate License Change(00:51:05) Intellectual Property & Meaningful Contributions(00:52:52) AI Usage & Copyright in Open Source(00:55:21) Biggest Challenge Working in a Big Open Source(00:56:08) Politics in Open Source(00:58:32) Security Risks in Open Source(01:02:25) Donating Hibernate to Commonhaus Foundation(01:04:49) The Future of Red Hat(01:06:39) 3 Tech Lead Wisdom_____Sanne Grinovero's BioSanne Grinovero has been a member of the Hibernate team for 10 years; today he leads this project in his role of Sr. Principal Software Engineer at Red Hat, while also working on Quarkus as a founding R&D engineer.Deeply interested in solving performance and concurrency challenges around data access, scalability, and exploring integration with new storage technologies, distributed systems and search engines.Working on Hibernate features led him to contribute to related open source technologies; most notably to Apache Lucene and Elasticsearch, Infinispan and JGroups, ANTLR, WildFly, various JDBC drivers, the OpenJDK and more recently getting interested in GraalVM.After being challenged to reduce memory consumption and improve bootstrap times of Hibernate, Sanne worked as part of a small R&D team at Red Hat on some ideas which have evolved into what is known today as Quarkus.Follow Sanne:LinkedIn – linkedin.com/in/sannegrinoveroTwitter – twitter.com/SanneGrinoveroGitHub – github.com/sanneLike this episode?Show notes & transcript: techleadjournal.dev/episodes/220.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Chatting with Principal Software Engineer at Treasure Data Justin Heyes-Jones from British Columbia, Canada- Justin Heyes-Jones is a seasoned software developer with broad experience spanning the Fintech, Leisure, and Entertainment industries. His career ranges from building AAA video games at studios like Sony and Activision to engineering scalable systems at Fintech startups and global enterprises. Known for his ability to translate complex technical challenges into clear, actionable insights, he excels at aligning technical solutions with real-world business needs.With an academic background in Artificial Intelligence, Justin began his career developing high-performance systems in C and C++, including physical simulations and animation engines. Today, his focus is on highly scalable, cloud-based distributed systems. His technical interests include functional programming, microservices, and event sourcing. He is a regular speaker at local meetups and industry conferences and shares his insights through a widely read technical blog.for more info visit- https://smartcherrysthoughts.com

In this episode, we're bringing you a curated selection of conversations from the KubeCon EU 2025 showfloor. We'll be diving into the rise of platform engineering, exploring some cutting-edge technologies, getting updates on core Kubernetes components, and hearing some truly unique user stories, like using Kubernetes on a dairy farm! Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod - bluesky: @kubernetespodcast.com   News of the week CNCF Blog - Announcing the Automated Governance Maturity Model Kubernetes Blog CNCF Blog - Understanding Kubernetes Gateway API: A Modern Approach to Traffic Management Open Observability Summit Links from the interview NAIS at NAV, with Hans Kristian Flaatten and Audun Fauchald Strand Audun Fauchald Strand Hans Kristian Flaatten NAV (Norwegian Labor and Welfare Administration) Kubernetes Podcast 216: NAIS, with Johnny Horvi and Frode Sundby NAIS KubeCon EU 2025 Keynote: Adventures of Building a Platform as a Service for the Government - Hans Kristian Flaatten, Lead Platform Engineer, NAV & Audun Fauchald Strand, Principal Software Engineer, NAV GKE release notes   Platform Engineering, with Max Körbächer and Andreas (Andi) Grabner Max Körbächer Andreas (Andi) Grabner Book: “Platform Engineering for Architects: Crafting modern platforms as a product” by Max Körbächer, Andreas Grabner, and Hilliary Lipsig Cloud Native Summit Munich   Kubernetes at LinkedIn, with Ahmet Alp Balkan and Ronak Nathani Ahmet Alp Balkan Ronak Nathani Kubernetes Podcast 249: Kubernetes at LinkedIn, with Ahmet Alp Balkan and Ronak Nathani Ahmet's Blog Introducing Multi-Cluster Orchestrator: Scale your Kubernetes workloads across regions   LLMs on Kubernetes, with Mofi and Abdel KubeCon EU 2025 talk: Yes You Can Run LLMs on Kubernetes - Abdel Sghiouar & Mofi Rahman, Google Cloud About the Gateway API Gateway API Inference Extension Deploy GKE Inference Gateway   SIG etcd with Ivan Valdes Ivan Valdes etcd.io SIG etcd on GitHub   Open Source Kubernetes, with Jago Macleod Jago Macleod Google Open Source: Kubernetes Schedmd Slurm Ray Run:ai from Nvidia Medium blog: “Deploy Slurm on GKE” by Abdel Sghiouar AI-Hypercomputer, xpk XPK (Accelerated Processing Kit, pronounced x-p-k) is a command line interface that simplifies cluster creation and workload execution on Google Kubernetes Engine (GKE). XPK generates preconfigured, training-optimized clusters and allows easy workload scheduling without any Kubernetes expertise. Cursor AI Editor   Dairy Farm Automation & Banking with Kubernetes, with Clément Nussbaumer Clément Nussbaumer Talos Linux Cluster-api Cluster API is a Kubernetes subproject focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters. KubeCon EU 2025 Talk: “Day-2'000 - Migration From Kubeadm+Ansible To ClusterAPI+Talos: A Swiss Bank's Journey” - Clément Nussbaumer, PostFinance Kubeadm Kubeadm is a tool built to provide kubeadm init and kubeadm join as best-practice "fast paths" for creating Kubernetes clusters.   Being a First-Time KubeCon Attendee, with Nick Taylor Kubernetes The Hard Way K3s - “The certified Kubernetes distribution built for IoT & Edge computing” Kubernetes Ingress Controllers Kubernetes Up and Running Kubernetes Docs KubeCon EU 2025 Sponsored Keynote: The Science of Winning: Oracle Red Bull Racing's Formula with Open Source, Kubernetes and AI - Sudha Raghavan, SVP of OCI Developer Platform, Oracle

Hey everyone, Alex here

Dustin is a Principal Software Engineer at Microsoft. He works on enhancing .NET tooling and contributing to the design of the next version of C# as part of the language design team. Prior to his current role, he spent several years working as a program manager on Project Roslyn. He also contributed in a strong way to the Razor UI framework. He recently presented a session at .NET Conf 2024 on What's new in C# 13.   Topics of Discussion: [4:04] Fun fact: Dustin has a jazz guitar performance degree! [3:39] The unique appeal of C#. [5:06] Evolution of C# and its features. [10:48] Impact of Async and Await on C#. [13:17] The compatibility of C# 13 with older .NET versions, specifically .NET 8. [15:04] How developers can leverage the latest C# features while still targeting older .NET frameworks, and the challenges associated with runtime support for new language capabilities. [17:04] Hacking the C# compiler. [17:28] The evolution of records from their initial introduction to the added features. [18:46] Records vs. Classes in C#. [22:51] AI's influence on developer productivity. [25:46] The future of AI developer tools. [33:26] The need for better support for testing with large language models and other AI-driven dependencies.   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at programming@palermo.net. Clear Measure, Inc. (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo  The Five Pillars: Leadership For Effective Custom Software, by Jeffrey Palermo  Jeffrey Palermo's Twitter — Follow to stay informed about future events! Dustin Campbell on LinkedIn .NET Conf 2024: What's New in C#13   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

On this episode, I talk with JP Camara, Principal Software Engineer at Wealthbox about nicknames, how having quality A/V equipment impacts how people perceive you, concurrency in programming, quantum computing, Galileo and the multiverse, blank slate-ism and whether people deserve credit or blame for their inborn traits and decisions, free will or determinism, whether or not we live in a simulation, and Jeremy Bearimy.The Fabric of Reality by David DeutschThe Beginning of Infinity by David DeutschThe Blank Slate by Stephen PinkerThe Language Instinct by Stephen PinkerJP Camara on LinkedInJP Camara on TwitterJP Camara.com

Gil Tayar is a Principal Software Engineer at Microsoft, developer advocate, and conference speaker. Gil's contributions to the Node.js ecosystem include adding support for ECMAScript Modules in Node.js to Mocha and TestDouble. He joins the show to talk about his history in software engineering, monorepos vs polyrepos, the state of JavaScript, and more. Josh Goldberg The post Node.js and the Javascript Ecosystem with Gil Tayar appeared first on Software Engineering Daily.

Gil Tayar is a Principal Software Engineer at Microsoft, developer advocate, and conference speaker. Gil’s contributions to the Node.js ecosystem include adding support for ECMAScript Modules in Node.js to Mocha and TestDouble. He joins the show to talk about his history in software engineering, monorepos vs polyrepos, the state of JavaScript, and more. Josh Goldberg The post Node.js and the Javascript Ecosystem with Gil Tayar appeared first on Software Engineering Daily.

In this episode of the Modern Web Podcast, recorded live at All Things Open in Raleigh, NC, hosts Rob Ocel and Danny Thompson sit down with Dr. Sally Wahba, Principal Software Engineer at Splunk. Dr. Wahba shares her experience tackling on-call burnout, offering insights into reducing fatigue through better observability, automation, and thoughtful team practices. The conversation also touches on mentorship and growth in the tech industry, including practical advice for junior engineers navigating the transition from academics to professional roles and tips for companies to better support new talent. Chapters 00:00:13 - Introduction to Marketing This Dot 00:01:00 - Asking for Help Effectively 00:02:21 - Reducing On-Call Fatigue 00:04:42 - Observability Best Practices 00:07:07 - Balancing Alerts and On-Call Efficiency 00:09:30 - The Role of On-Call in Modern Engineering 00:11:29 - Insights from the Grace Hopper Celebration 00:13:56 - Mentorship and Team Dynamics 00:16:14 - Rapid Changes in Technology and Adaptation 00:18:39 - Automation, Observability, and Debugging Challenges 00:21:04 - Addressing the Talent Gap and Junior Engineer Growth 00:24:00 - Closing Thoughts and Where to Learn More Follow Dr. Sally Wahba on Social Media Twitter: https://x.com/sallyky Linkedin: https://linkedin.com/in/sallywahba/ Sponsored by This Dot: thisdot.co

The hallway track at All Things Open 2024 — features Carl George, Principal Software Engineer at Red Hat for a discussion on the state of open source enterprise linux and RHEL (Red Hat Enterprise Linux), Max Howell, creator of Homebrew and tea.xyz which offers rewards and recognition to open source maintainers, and Chad Whitacre, Head of Open Source at Sentry about the launch of Open Source Pledge and their plans to helps businesses and orgs to do the right thing and support open source.

The hallway track at All Things Open 2024 — features Carl George, Principal Software Engineer at Red Hat for a discussion on the state of open source enterprise linux and RHEL (Red Hat Enterprise Linux), Max Howell, creator of Homebrew and tea.xyz which offers rewards and recognition to open source maintainers, and Chad Whitacre, Head of Open Source at Sentry about the launch of Open Source Pledge and their plans to helps businesses and orgs to do the right thing and support open source.

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRead the full transcription of the interview here:https://gotopia.tech/episodes/322Ashley Davis - Author of "Bootstrapping Microservices" & Principal Software Engineer at AutodeskDamian Maclennan - Technologist, Software Architect, Trainer, Developer & Consultant CTO at Stack MechanicsRESOURCESAshleyhttps://x.com/codecapershttps://www.linkedin.com/in/ashleydavis75https://www.codecapers.com.auDamianhttps://damianm.comhttps://mastodon.social/@damianmhttps://bsky.app/profile/damianm.comhttps://www.linkedin.com/in/damianmaclennanhttps://instagram.com/damianmaclennanhttps://twitter.com/DamianMLinkshttps://bootstrapping-microservices.comhttps://rapidfullstackdevelopment.comDESCRIPTIONDamian Maclennan, a software architecture and trainer, engages with Ashley Davis, author of “Bootstrapping Microservices", discussing the evolution and practical applications of microservices.With over 25 years of experience as a developer, Ashley shares insights into his career and what inspired him to write the book's second edition, emphasizing the importance of context in choosing the right architecture—be it microservices or monolithic systems—through examples like AI model processing and data security.They explore how industry trends, feedback, and advancements in tools have shaped the book, making complex concepts more accessible. Ashley and Damian highlight microservices' flexibility in system design, allowing for the gradual evolution and replacement of components, which helps manage technical debt and adapt to newer technologies.They emphasize that microservices facilitate smaller, focused teams that can independently manage and scale components, enhancing overall agility. However, they also caution against potential pitfalls, such as unnecessary complexity and improper implementation, which can undermine the advantages of microservices.RECOMMENDED BOOKSAshley Davis • Bootstrapping Microservices • https://amzn.to/3X8ccTcSarah Wells • Enabling Microservice Success • https://amzn.to/4aa8xrvSam Newman • Monolith to Microservices • https://amzn.to/2Nml96ESam Newman • Building Microservices • https://amzn.to/3dMPbOsSimon Brown • Software Architecture for Developers Vol. 2 • https://leanpub.com/visualising-software-architectureTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Welcome to another engaging episode of the Maintainable Software Podcast! In this episode, Robby sits down with Moriel Schottlender, Principal Software Engineer at the Wikimedia Foundation, to explore the complex journey of modernizing MediaWiki, the software behind Wikipedia. Moriel shares her insights on what it takes to keep an enormous monolithic codebase maintainable while supporting an ever-growing and diverse set of global users. She highlights the importance of modularization, ownership, and the delicate balance between flexibility and stability in open-source software.Key Takeaways[00:00:51] Characteristics of Well-Maintained Software: Moriel discusses the three crucial characteristics of well-maintained software: ownership, modularization, and documentation.[00:01:09] Ownership and Rules for Contribution: Ownership goes beyond just fixing bugs—it involves understanding the architectural purpose and maintaining consistency even as teams change.[00:03:35] Product Vision's Role in Maintainability: Why a clear product vision is essential for maintaining software, even in the face of organic growth.[00:07:14] Balancing Experimentation and Long-Term Planning: Moriel shares insights into how Wikimedia balances rapid experimentation with careful, long-term architectural planning.[00:07:32] The Evolution of MediaWiki: MediaWiki's growth from a small project to the backbone of Wikipedia, now supporting over 900 wikis, and the challenges that come with scaling.[00:14:18] Modernizing a 23-Year-Old Monolith: Robby and Moriel dive into the challenges of modernizing MediaWiki's architecture, including the difficulties of updating a monolithic structure.[00:17:15]Wikitext vs. Markdown: Moriel explains why MediaWiki uses its own Wikitext language instead of Markdown and the unique challenges it presents.[00:22:25] Architectural Flexibility for the Future: The importance of having a flexible architecture that can adapt to the evolving needs of users and technologies.[00:26:04] Technical Debt and Modularization: How Wikimedia approaches technical debt in MediaWiki and prioritizes architectural interventions to improve modularity and maintainability.[00:39:00] Community Contributions to MediaWiki: Strategies for increasing developer contributions and how Wikimedia empowers volunteers while maintaining software quality.[00:41:59] Advice for Aspiring Open Source Contributors: Moriel shares encouraging words for anyone looking to contribute to open-source projects, emphasizing that everyone can make a meaningful impact.[00:35:44] The Role of Documentation: Moriel discusses Wikimedia's efforts to improve documentation and ensure it's useful for both developers and end-users, leveraging the strengths of wiki-based contributions.[00:30:29] Celebrating Small Wins: Moriel talks about how Wikimedia celebrates small victories to keep team morale high in the face of big challenges.Resources MentionedMoriel's WebsiteMoriel on MastodonMediaWiki DocumentationBook Recommendation:Year Zero by Rob ReidConnect with MorielMoriel on LinkedInInstagramTwitterGitHubMastodonThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

The White House recently announced plans to boost Internet routing security in the US through better RPKI coverage. So how does RPKI help secure BGP? How easy is it to boost coverage on a national level? And what's the future potential of the infrastructure? Our guest Tim Bruijnzeels shares his views.Tim is Principal Software Engineer for RPKI at the RIPE NCC and has worked in standards development and software implementation around RPKI for well over a decade. He talked to us about where RPKI is at today, how governments can and have aided its adoption, and how work being done on ASPA and BGPsec promise a more secure future for the Internet.Show notes:02:40 - The Dublin IETF meeting back in 2008.03:17 - Tim has contributed to a number of RFCs over the years.03:40 - NLnet Labs develops free, liberally licensed, open-source software for DNS and BGP routing.03:50 - Krill is a free, open source RPKI Certificate Authority developed by NLnet Labs that lets you run delegated RPKI under one or multiple RIRs.07:24 - You can read more on how the Internet routes around damage on RIPE Labs.10:47 - Get more information on how to manage ROAs through the RPKI Dashboard.11:36 - Check out the RIPE NCC's Routing Information Service (RIS).12:17 - Alex Band's article on the launch of the RIPE NCC Resource Certification Service back in 2011.13:51 - There are a number of RPKI validators to choose from, including Routinator from NLnet Labs.17:32 - Here's a nice explainer article on ASPA.22:07 - Plans to support ASPA and BGPsec router certificates in RIPE NCC Quarterly Planning.24:42 - Press Release: White House Office of the National Cyber Director Releases Roadmap to Enhance Internet Routing Security.26:47 - More on Dutch government measures for ensuring RPKI coverage. Hosted on Acast. See acast.com/privacy for more information.

Ryan Riley is a Principal Software Engineer at Wise Rock in Houston, TX. He enjoys learning and collaborating on simple, creative solutions to problems, and implementing those solutions with others through teamwork, training, and mentoring. He has worked as a Solution Architect and Team Lead for local and remote teams, focusing on front-end UX and back-end, distributed applications and APIs to delight customers across many industries.   Topics of Discussion: [:36] Intro to Ryan and his experience in software engineering leadership. [4:10] Ryan's early career journey and transition from the .com bubble to software development. [6:17] How Ryan stepped into leadership roles through initiative and team collaboration. [8:40] Balancing hands-on coding with team leadership in a long-term software engineering career. [12:10] The importance of experience and technical knowledge for effective leadership in development teams. [14:27] Empowering team members to lead projects and grow their skill sets. [18:15] Key non-negotiables for young developers, including pull requests, testing, and small commits. [21:28] Architectural patterns Ryan favors, like JSON APIs and balancing between monoliths and microservices. [28:55] Key strategies for supporting software in production and ensuring stability. [34:41] Challenges of cloud costs and performance and the importance of managing resources efficiently.   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at programming@palermo.net. Clear Measure, Inc. (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's Twitter — Follow to stay informed about future events! Panes of Glass Wizards of Smart James Riley   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

The software world is vast and ever changing. Cutting through the noise of language fads and building a system that meets your organization's goals, is maintainable, scalable, performant and clean is no easy feat. It is the Principal Engineers that stand at the helm and steer the ship in the right direction. Today we dive into the world of one Principal Engineer steering the ship for an iconic brand and how he views his role, what it means to be a principal engineer, his thoughts on AI in software, the importance and meaning of InnerSource software development, and more. Our guest, Jeff Bailey, is one of those superheroes guiding a famous brand to success. He started his software journey as a teenager and his first computer was a White Box 286, that he traded his Sega Master System and some games to acquire. He now has over 25 years of professional software development experience. He has worked for companies like Internet In A Mall, Earthlink, Evoque and Axian doing consultant work, and has a wide range of experience in languages like Perl to Cold Fusion to Python to Java to Javascript. He is currently a Principal Software Engineer at Nike and the co-leader of the Tech Modernization Team. He believes you must be a force multiplier to enable maximum efficiency for your team and prioritizing the right tool for the job. When our guest is not designing architecture or driving excellence at Nike he is gaming on Nintendo Switch, Steam and Xbox or creating a moody vibe playing his guitar. Enjoy the conversation!! Connect with Jeff: LinkedIn Website/Blog Sponsor: Clairity: Do you know how your engineers feel about your company? About their work? Connect your Github and install Clairitiy's real-time survey iteration tool now with code "buildwithpeople" and get 20% off your first year to discover real insights about your engineers experience. Show notes and helpful resources: Alfred Productivity App - A MacOS productivity app for automating workflows and tasks NuShell - A tool that allows running commands against JSON, CSVs, and other file types using a consistent query language. Jeff's Tools Jeff's blog post on Learning, Earning and Growing InnerSource Commons - A global community focused on promoting InnerSource practices and building InnerSource programs Principal engineer role - Jeff describes his role as a "force multiplier," amplifying the effectiveness of his team by solving complex problems, exploring new technologies, and always thinking a step ahead. A principal engineer isn't just a tech expert but a leader who can look beyond code to the broader organizational needs Building software for and with people - For Jeff, the ultimate goal of any technology is to serve people. Whether it's through enhancing productivity or solving everyday problems, software should make life simpler and less complicated for its users. His focus is always on understanding the real needs behind the code. Building something cool or solving interesting problems? Want to be on this show? Send me an email at jointhepodcast@unfilteredbuild.com Podcast produced by Unfiltered Build - dream.design.develop.

Fisayo Oluwadiya is the Founder of OKAO and the creator of Resactly, an intelligent app that foodies can use to share their taste profiles and receive unique dining experiences.Dive into topics such as her journey on becoming a Principal Software Engineer, the social following she built around dining out in New York City, deploying her first restaurant experience AI model, proactive methods to find impactful mentors and much more. Hosted by Perry Tiu.Guest links available at: https://perrytiu.com/podcast/fisayo-oluwadiya—Interested being on the show? contact@perrytiu.comSponsorship enquiries: sponsor@perrytiu.comFollow Podcast Ruined by a Software Engineer and leave a review• Apple Podcasts: https://apple.co/3RASg8x• Spotify: https://spoti.fi/3RBAXEw• Youtube: https://youtube.com/@perrytiuMore Podcast Ruined by a Software Engineer• Website: https://perrytiu.com/podcast• Merch: https://perrytiu.com/shop• RSS Feed: https://perrytiu.com/podcast/rss.xmlFollow Perry Tiu• Twitter: https://twitter.com/perry_tiu• LinkedIn: https://linkedin.com/in/perrytiu• Instagram: https://instagram.com/doctorpoor

Benno van der Berg, Principal Software Engineer at Fiberplane, sits down with Luca Palmieri. They discuss Fiberplane's 3-years long journey with Rust, building an interactive observability notebook. They touch on Benno's experience switching from .NET to Rust and share insights on using Rust for a commercial product, including the reasons behind Fiberplane's Rust adoption. They then dive into the challenges of maintaining Fiberplane's codebase and conclude with a few tips for developers looking for Rust jobs. Contributing to Rustacean Station Rustacean Station is a community project; get in touch with us if you'd like to suggest an idea for an episode or offer your services as a host or audio editor! Twitter: @rustaceanfm Discord: Rustacean Station Github: @rustacean-station Email: hello@rustacean-station.org Timestamps & referenced resources [@00:00] - Introduction Video recording of the interview [@00:33] - Start of the interview [@01:17] - Benno's journey as a Software Engineer [@04:29] - Fiberplane's products [@07:05] - Building an observability product in Rust [@09:25] - Uses for Rust at Fiberplane [@13:30] - WASM and front end [@22:04] - Fiberplane's 3-year experience with Rust [@32:43] - Benno's advice for developers seeking Rust jobs [@35:28] - Conclusion Credits Intro Theme: Aerocity Audio Editing: Mainmatter Hosting Infrastructure: Jon Gjengset Show Notes: Mainmatter Hosts: Luca Palmieri

Join us for this special live edition of the Shared Security Podcast, recorded in scorching Las Vegas at Black Hat 2024. Host Tom Eston is joined by Shourya Pratap Singh, Principal Software Engineer at SquareX. They discuss highlights from Black Hat 2024, emerging themes in cybersecurity such as AI-based threats, compliance, and cloud security. The […] The post Exploring Cybersecurity Trends at Black Hat 2024 with Shourya Pratap Singh from SquareX appeared first on Shared Security Podcast.

In this episode, I welcome Jason Gilman, a Principal Software Engineer at Element 84, to explore the exciting world of natural language geocoding. Key Topics Discussed: Introduction to Natural Language Geocoding: Jason explains the concept of natural language geocoding and its significance in converting textual descriptions of locations into precise geographical data. This involves using large language models to interpret a user's natural language input, such as "the coast of Florida south of Miami," and transform it into an accurate polygon that represents that specific area on a map. This process automates and simplifies how users interact with geospatial data, making it more accessible and user-friendly. The Evolution of AI and ML in Geospatial Work: Over the last six months, Jason has shifted focus to AI and machine learning, leveraging large language models to enhance geospatial data processing. Challenges and Solutions: Jason discusses the challenges of interpreting natural language descriptions and the solutions they've implemented, such as using JSON schemas and OpenStreetMap data. Applications and Use Cases: From finding specific datasets to processing geographical queries, the applications of natural language geocoding are vast. Jason shares some real-world examples and potential future uses. Future of Geospatial AIML: Jason touches on the broader implications of geospatial AI and ML, including the potential for natural language geoprocessing and its impact on scientific research and everyday applications. Interesting Insights: The use of large language models can simplify complex geospatial queries, making advanced geospatial analysis accessible to non-experts. Integration of AI and machine learning with traditional geospatial tools opens new avenues for research and application, from environmental monitoring to urban planning. Quotes: "Natural language geocoding is about turning a user's textual description of a place on Earth into a precise polygon." "The combination of vision models and large language models allows us to automate complex tasks that previously required manual effort." Additional Resources: Element 84 Website State of the Map US Conference Talk on YouTube Blog Posts on Natural Language Geocoding Connect with Jason: Visit Element 84's website for more information and contact details. Google "Element 84 Natural Language Geocoding" for additional resources and talks.

In this episode of MongoDB Global 2024, we chat with Ramesh Sunkara, Principal Software Engineer at Hewlett Packard Enterprise (HPE). Discover how HP Greenlake leverages MongoDB to enhance customer experiences through their wellness platform, offering automated support, proactive maintenance, and predictive analytics. Ramesh shares insights into the platform's architecture, the benefits of using MongoDB, and the collaboration with MongoDB's professional services.

Send us a Text Message.Jack Herrington is the mastermind behind the YouTube channel Blue Collar Coder where he does deep dives on React, JavaScript and front end concepts. He shares his impressive 40-year journey in coding that began at age 13 and has remained close to the front end and excelled in software with only a high school diploma! From working at Nike and Walmart Labs to becoming a prominent tech content creator, Jack opens up about balancing his YouTube channel, a high-level tech role, and personal life.Jack offers invaluable career tips, opens up about dealing with dyslexia, and advice for junior developers looking to thrive in the tech industry.Check out his YouTube channel if you're learning JS, React or NextJS, it's a no brainer: https://www.youtube.com/@jherrShameless Plugs

Wi-Fi 7 has arrived, elevating 6GHz Wi-Fi to unprecedented heights. In this podcast, we dive head-first into the Wi-Fi 7 standard, examining its impact on enterprise networks. We cover a range of topics including Wi-Fi 7 features and capabilities, device and infrastructure readiness, adoption, and what comes next for the standard. -What is wifi 7 (what is its relationship to 802.11be) -What are some new use cases? In homes, but also in enterprise? -Why is wifi 7 important/different from previous gens? Does it work with previous gens? -What problems are being addressed? -How are new standards developed, what is Cisco's input/role with IEEE 802.11, WFA -Interoperability partnerships – advanced etc -What should customers consider re: adopting wifi 7? Any caveats? Check out our latest Mobility Field Day session on Wi-Fi 7 here https://www.youtube.com/watch?v=90A8sYNxvEg Cisco Guests: Jerome Henry, Lead Researcher, Office of the Wireless, CTO, Cisco Binita Gupta, Wireless Systems Architect, Cisco Brian Hart, Principal Software Engineer. Cisco Cisco Champion Hosts Mike Bolitho (https://www.linkedin.com/in/mikebolitho/), Wireless Engineer, CommonSpirit Health Samuel Clements (https://www.linkedin.com/in/saclements/), Technical Solutions Architect, WWT Gert-Jan de Boer (https://www.linkedin.com/in/gjdeboer/), Networking Archeologist, aaZoo Network Solutions Moderator Danielle, Customer Voices and Cisco Champion Program

Mitch is a Principal Software Engineer on the .NET Cloud team working on .NET Aspire and ASP.NET Core. Previously Mitch has worked on Azure services, the Azure SDK, and Azure DevOps.   Topics of Discussion: [2:46] Mitch's career journey in the Microsoft ecosystem. [5:46] What makes it .NET Aspire vs. .NET8? [6:16] .NET Aspire focuses on seamless integration between app components. [8:18] Making sure the core of Aspire is cloud-agnostic. [10:48] Developer control plane. [11:40] How Aspire simplifies cross processes. [14:36] Using Aspire to manage dependencies in microservices applications. [18:18] Automating deployments with Azure DevOps and easy mode for .NET Aspire. [30:27] Securing container deployments. [34:39] Using Azure DevOps for cloud deployment and configuration management. [37:33] What are the best resources for people to dig in? [40:03] Azure subscriptions inside Microsoft. [43:43] They are only just getting started with Aspire, and with .NET 9 coming out in November.   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at programming@palermo.net. Clear Measure, Inc. (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's Twitter — Follow to stay informed about future events! GitHub Mitch Denny .NET Aspire (aspire) github.com/dotnet/aspire/tree/main/playground github.com/dotnet/aspire github.com/dotnet/eShop   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

In this episode, we talk to three active leaders who have been around since the very beginning of Kubernetes. We explore how Kubernetes has changed since its inception, with a particular focus on current efforts in Open source Kubernetes to support AI/ML style workloads.   Maciej Szulik is currently taking a seat in the Kubernetes Steering Committee. He's also leading Special Interests Groups responsible for kubectl, workload and batch controllers. Maciej has been contributing to Kubernetes since the early days, jumping from one area to another where help was needed. He authored the first version of audit and helped shape its current one, as well as touched multiple other places in apimachinery. He was also responsible for designing and implementing Job and CronJob controllers. In kubectl he was responsible for the plugin mechanism and several major refactors to simplify the code. Since May 2024 he joined the ranks of Production Readiness Review (PRR) approvers helping ensure high production standards for the future of Kubernetes releases.    Clayton Coleman is a long-time Kubernetes contributor, having helped launch Kubernetes as open source, being on the bootstrap steering committee, and working across a number of SIGs to make Kubernetes a reliable and powerful foundation for workloads.  At Red Hat he led OpenShift's pivot onto Kubernetes and its growth across on-premise, edge, and into cloud.  At Google he is now focused on enabling the next generation of key workloads, especially AI/ML in Kubernetes and on GKE.   Dawn Chen has been a Principal Software Engineer at Google cloud since May 2007. Dawn has worked on an open source project called Kubernetes before the project was founded. She has been one of tech leads in both Kubernetes and GKE, and founded SIG Node from scratch. She also led Anthos platform team for the last 4 years, and mainly focuses on the core infrastructure. Prior to Kubernetes, she was the one of the tech leads for Google internal container infrastructure -- Borg for about 7 years. Outside of work, she is a wife, a mother of a 16-year old boy and a good friend. She enjoys reading, cooking, hiking and traveling.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod News of the week Kubernetes 1.31 Code Freeze is on July 9th Links from the interview Kubernetes Working Group Batch Kubernetes Working Group Serving Blog: Introducing Indexed Jobs (2021) Docs: Kubernetes Jobs KEP: Elastic Indexed Jobs Docs: Kubernetes CronJobs KubeCon EU 2021: The Long, Winding and Bumpy Road to CronJob's GA - Maciej Szulik, Red Hat & Alay Patel, Red Hat KubeCon EU 2018: Writing Kube Controllers for Everyone - Maciej Szulik, Red Hat (Beginner Skill Level) Kubernetes Working Group Device Management Kubernetes Enhancement Proposal process README DockerCon 2014: The announcement of Kubernetes at DockerCon Blog: AI & Kubernetes (by Kaslin) Kueue - “Kueue is a cloud-native job queueing system for batch, HPC, AI/ML, and similar applications in a Kubernetes cluster.” Whitepaper: Large-scale cluster management at {Google} with {Borg} Email: “Containers: Introduction” - An email introducing the concept of Linux containers to the Linux community Links from the post-interview chat Blog - “Scaling Kubernetes to 7,500 nodes” - OpenAI Ray on Kubernetes  

Guest: Seth Vargo, Principal Software Engineer responsible for Google's use of the public cloud, Google Topics: Google uses the public cloud, no way, right? Which one? Oh, yeah, I guess this is obvious: GCP, right? Where are we like other clients of GCP?  Where are we not like other cloud users? Do we have any unique cloud security technology that we use that others may benefit from? How does our cloud usage inform our cloud security products? So is our cloud use profile similar to cloud natives or traditional companies? What are some of the most interesting cloud security practices and controls that we use that are usable by others? How do we make them work at scale?  Resources: EP12 Threat Models and Cloud Security (previous episode with Seth) EP66 Is This Binary Legit? How Google Uses Binary Authorization and Code Provenance EP75 How We Scale Detection and Response at Google: Automation, Metrics, Toil EP158 Ghostbusters for the Cloud: Who You Gonna Call for Cloud Forensics IAM Deny Seth Vargo blog “Attention Is All You Need” paper (yes, that one)

Innovation Unveiled: SquareX's Vision at RSA Conference 2024During RSA Conference 2024, SquareX emerged as a source of fresh innovation, revolutionizing the cybersecurity landscape with their cutting-edge solutions. Hosted by Sean Martin, this episode of "On Location" takes you on a journey through the insights and revelations brought to light by key figures at SquareX.Introducing SquareX: Meet the VisionariesThe episode turn on the microphones at the Square X booth, where Sean Martin introduces the audience to Dakshitaa Babu and Shourya Pratap Singh, pivotal figures driving innovation at SquareX. Dakshitaa, the product evangelist, and Shourya, the principal software engineer, shed light on their roles and the impact of SquareX's work on the industry.The Passion Behind the InnovationDakshitaa shares her perspective on the privilege of contributing to a company that drives meaningful change in the industry, emphasizing SquareX's commitment to innovation. Shourya echoes this sentiment, highlighting the satisfaction of solving complex problems and witnessing their solutions making a tangible impact on customers.Pushing the Boundaries: A Glimpse Into SquareX's TechnologySean Martin delves into the intricacies of SquareX's technology, discussing AI-generated images and reverse engineering techniques employed to uncover hidden threats within images. Shourya elaborates on the challenges posed by malicious files and the innovative approaches adopted by SquareX to enhance cybersecurity.Addressing Customer Concerns: SquareX's Value PropositionSean Martin probes Dakshitaa and Shourya on the key concerns voiced by prospects and customers at the conference. They shed light on how SquareX addresses the gap in endpoint security solutions, providing customers with insightful data and a comprehensive understanding of cyber threats.Empowering Organizations: The SquareX DifferenceThe episode concludes with Sean Martin underscoring the significance of visibility at the web browser level and commending SquareX for empowering organizations to proactively tackle cybersecurity challenges. Dakshitaa extends her gratitude to visitors at the booth, emphasizing the value of SquareX's solutions for a secure digital environment.Learn more about SquareX: https://itspm.ag/sqrx-l91Note: This story contains promotional content. Learn more.Guests: Dakshitaa Babu, Security Researcher, SquareXOn LinkedIn | https://www.linkedin.com/in/dakshitaababu/Shourya Pratap Singh, Principal Software Engineer, SquareXOn LinkedIn | https://www.linkedin.com/in/shouryaps/ResourcesLearn more and catch more stories from SquareX: https://www.itspmagazine.com/directory/squarexView all of our RSA Conference Coverage: https://www.itspmagazine.com/rsa-conference-usa-2024-rsac-san-francisco-usa-cybersecurity-event-infosec-conference-coverageLearn more about 7 Minutes on ITSPmagazine Short Brand Story Podcasts: https://www.itspmagazine.com/purchase-programsNewsletter Archive: https://www.linkedin.com/newsletters/tune-into-the-latest-podcasts-7109347022809309184/Business Newsletter Signup: https://www.itspmagazine.com/itspmagazine-business-updates-sign-upAre you interested in telling your story?https://www.itspmagazine.com/telling-your-story

Innovation Unveiled: SquareX's Vision at RSA Conference 2024During RSA Conference 2024, SquareX emerged as a source of fresh innovation, revolutionizing the cybersecurity landscape with their cutting-edge solutions. Hosted by Sean Martin, this episode of "On Location" takes you on a journey through the insights and revelations brought to light by key figures at SquareX.Introducing SquareX: Meet the VisionariesThe episode turn on the microphones at the Square X booth, where Sean Martin introduces the audience to Dakshitaa Babu and Shourya Pratap Singh, pivotal figures driving innovation at SquareX. Dakshitaa, the product evangelist, and Shourya, the principal software engineer, shed light on their roles and the impact of SquareX's work on the industry.The Passion Behind the InnovationDakshitaa shares her perspective on the privilege of contributing to a company that drives meaningful change in the industry, emphasizing SquareX's commitment to innovation. Shourya echoes this sentiment, highlighting the satisfaction of solving complex problems and witnessing their solutions making a tangible impact on customers.Pushing the Boundaries: A Glimpse Into SquareX's TechnologySean Martin delves into the intricacies of SquareX's technology, discussing AI-generated images and reverse engineering techniques employed to uncover hidden threats within images. Shourya elaborates on the challenges posed by malicious files and the innovative approaches adopted by SquareX to enhance cybersecurity.Addressing Customer Concerns: SquareX's Value PropositionSean Martin probes Dakshitaa and Shourya on the key concerns voiced by prospects and customers at the conference. They shed light on how SquareX addresses the gap in endpoint security solutions, providing customers with insightful data and a comprehensive understanding of cyber threats.Empowering Organizations: The SquareX DifferenceThe episode concludes with Sean Martin underscoring the significance of visibility at the web browser level and commending SquareX for empowering organizations to proactively tackle cybersecurity challenges. Dakshitaa extends her gratitude to visitors at the booth, emphasizing the value of SquareX's solutions for a secure digital environment.Learn more about SquareX: https://itspm.ag/sqrx-l91Note: This story contains promotional content. Learn more.Guests: Dakshitaa Babu, Security Researcher, SquareXOn LinkedIn | https://www.linkedin.com/in/dakshitaababu/Shourya Pratap Singh, Principal Software Engineer, SquareXOn LinkedIn | https://www.linkedin.com/in/shouryaps/ResourcesLearn more and catch more stories from SquareX: https://www.itspmagazine.com/directory/squarexView all of our RSA Conference Coverage: https://www.itspmagazine.com/rsa-conference-usa-2024-rsac-san-francisco-usa-cybersecurity-event-infosec-conference-coverageLearn more about 7 Minutes on ITSPmagazine Short Brand Story Podcasts: https://www.itspmagazine.com/purchase-programsNewsletter Archive: https://www.linkedin.com/newsletters/tune-into-the-latest-podcasts-7109347022809309184/Business Newsletter Signup: https://www.itspmagazine.com/itspmagazine-business-updates-sign-upAre you interested in telling your story?https://www.itspmagazine.com/telling-your-story

Microsoft Copilot is a chatbot developed by Microsoft that launched in 2023 and is based on a large language model. Justin Harris is a Principal Software Engineer at Microsoft and has an extensive background in classical machine learning and neural networks, including large language models. He joins the show to talk about Microsoft Copilot, natural The post Microsoft Copilot with Justin Harris appeared first on Software Engineering Daily.

Microsoft Copilot is a chatbot developed by Microsoft that launched in 2023 and is based on a large language model. Justin Harris is a Principal Software Engineer at Microsoft and has an extensive background in classical machine learning and neural networks, including large language models. He joins the show to talk about Microsoft Copilot, natural The post Microsoft Copilot with Justin Harris appeared first on Software Engineering Daily.

We're celebrating May the 4th be with you. Yes, it's Star Wars Day and we've been given incredible behind the scenes access at none other than Star Wars: Galaxy's Edge at Walt Disney World Resort in Florida. Courtesy of Jose Corpuz, Principal Software Engineer with Global Engineering Technology and Analysis with Walt Disney Parks and Resorts, we've been given an exclusive behind-the-scenes tour of the tech that makes this one of the most immersive theme park experiences of its kind anywhere in the world. This is one you don't want to miss!This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week we look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations and what we can learn from it.About this week's guest: https://www.linkedin.com/in/jose-corpuz-a23533/More about Star Wars: Galaxy's Edge: https://www.hpe.com/psnow/doc/a00083951enw

We're celebrating May the 4th be with you. Yes, it's Star Wars Day and we've been given incredible behind the scenes access at none other than Star Wars: Galaxy's Edge at Walt Disney World Resort in Florida. Courtesy of Jose Corpuz, Principal Software Engineer with Global Engineering Technology and Analysis with Walt Disney Parks and Resorts, we've been given an exclusive behind-the-scenes tour of the tech that makes this one of the most immersive theme park experiences of its kind anywhere in the world. This is one you don't want to miss!This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week we look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations and what we can learn from it.About this week's guest: https://www.linkedin.com/in/jose-corpuz-a23533/More about Star Wars: Galaxy's Edge: https://www.hpe.com/psnow/doc/a00083951enw

We're celebrating May the 4th be with you. Yes, it's Star Wars Day and we've been given incredible behind the scenes access at none other than Star Wars: Galaxy's Edge at Walt Disney World Resort in Florida. Courtesy of Jose Corpuz, Principal Software Engineer with Global Engineering Technology and Analysis with Walt Disney Parks and Resorts, we've been given an exclusive behind-the-scenes tour of the tech that makes this one of the most immersive theme park experiences of its kind anywhere in the world. This is one you don't want to miss!This is Technology Now, a weekly show from Hewlett Packard Enterprise. Every week we look at a story that's been making headlines, take a look at the technology behind it, and explain why it matters to organizations and what we can learn from it.About this week's guest: https://www.linkedin.com/in/jose-corpuz-a23533/More about Star Wars: Galaxy's Edge: https://www.hpe.com/psnow/doc/a00083951enw

Alongside his peers studying Systems Network Engineering, Jelte Fennema-Nio unearthed a security vulnerability within the framework of Postgres. Since then, Jelte joined the world of cybersecurity and network engineering. He is currently Principal Software Engineer at Microsoft working on Citus/ Postgres/ PgBouncer. In this episode we explore:Forking and the impact of commercial entities on the core project The challenges of connection poolingThe suitability of Citus for scalabilityThe intricacies of configuring PgBouncerPaying attention to community needs and modernizing contribution methodsLinks mentioned:Jelte on XJelte on LinkedIn

In this episode of CyberWire-X, N2K CyberWire's Podcast host Dave Bittner is joined by Brian Davis, Principal Software Engineer, and Thomas Gardner, Senior Detection Engineer, both from Red Canary. They engage in a cloud architect vs. detection engineer discussion. Through the conversation, they illustrate how one person benefits the other's work and how they work together. Red Canary is our CyberWire-X episode sponsor.

Pratik Thantharate is a Principal Software Engineer with over ten years of experience in Agile Software Development, Cybersecurity, and DevOps. ================ All Episodes can be found at www.thecryptopodcast.org   Podcast Coaching + All Social Media + Donations link https://bio.link/podcaster   Our Facebook Group can be found at https://www.facebook.com/thecryptopodcast   =======   Thanks to my Sponsors : If you or know some body you know is struggling with anxiety and want to know how to be 100% anxiety free, in 6 weeks, without therapy or drugs, fully guaranteed    https://www.danielpackard.com/ --------------------------   Speaking Podcast Social Media / Coaching My Other Podcasts ⁠https://bio.link/podcaster⁠   ======================== Bio of Pratik Thantharate : Pratik Thantharate is a Principal Software Engineer with over ten years of experience in Agile Software Development, Cybersecurity, and DevOps. With dual M.S. degrees in Computer Science and Management Information Systems from US universities, he currently works at Paycor. His focus areas include Agile development, DevOps, security from code to cloud, monitoring, observability, and data privacy. Pratik applies his knowledge in CI/CD pipelines, infrastructure as code, containerization, and microservices to innovate in DevOps platforms and security frameworks. He has authored 6 research papers, peer-reviewed over 100, and served on the Technical Program Committee for over 30 international conferences, aiming to advance software delivery through his research. What we Discussed:   - How he got involved in Blockchain Technology (2:30 mins)   - What is Agile Development & Dev Ops (3:30 mins)   - Ai & Machine Learning (6 mins)   - ZeroTrustBlock ( 7 mins)   - How to stop errors in Hospitals ( 10 mins)   - How do we ensure that the Ai gives proper date (14 mins)   - A better Healthcare using Ai (16 mins)   - Cyber Security and how to protect yourself (20 mins)   - Ensure side effects are reported (22 mins)   - Transparency with Employees (26 mins)   - Protecting your Personal Data in Healthcare (28 mins)   - How to ensure that people can use this technology (30 mins)   - What Paycor does ( 31 mins)   - Why he is Positive for the Future of Ai (35 min)   and more     How to Contact Pratik Thantharate :   https://scholar.google.com/citations?hl=en&user=VEjDpX8AAAAJ   https://www.linkedin.com/in/pratikt1988/  

Pratik Thantharate is a Principal Software Engineer with over ten years of experience in Agile Software Development, Cybersecurity, and DevOps. ================ All Episodes can be found at www.thecryptopodcast.org   Podcast Coaching + All Social Media + Donations link https://bio.link/podcaster   Our Facebook Group can be found at https://www.facebook.com/thecryptopodcast   =======   Thanks to my Sponsors : If you or know some body you know is struggling with anxiety and want to know how to be 100% anxiety free, in 6 weeks, without therapy or drugs, fully guaranteed    https://www.danielpackard.com/ -------------------------- Speaking Podcast Social Media / Coaching My Other Podcasts ⁠https://bio.link/podcaster⁠   ======================== Bio of Pratik Thantharate : Pratik Thantharate is a Principal Software Engineer with over ten years of experience in Agile Software Development, Cybersecurity, and DevOps. With dual M.S. degrees in Computer Science and Management Information Systems from US universities, he currently works at Paycor. His focus areas include Agile development, DevOps, security from code to cloud, monitoring, observability, and data privacy. Pratik applies his knowledge in CI/CD pipelines, infrastructure as code, containerization, and microservices to innovate in DevOps platforms and security frameworks. He has authored 6 research papers, peer-reviewed over 100, and served on the Technical Program Committee for over 30 international conferences, aiming to advance software delivery through his research. What we Discussed:   - How he got involved in Blockchain Technology (2:30 mins) - What is Agile Development & Dev Ops (3:30 mins) - Ai & Machine Learning (6 mins) - ZeroTrustBlock ( 7 mins) - How to stop errors in Hospitals ( 10 mins) - How do we ensure that the Ai gives proper date (14 mins) - A better Healthcare using Ai (16 mins) - Cyber Security and how to protect yourself (20 mins) - Ensure side effects are reported (22 mins) - Transparency with Employees (26 mins) - Protecting your Personal Data in Healthcare (28 mins) - How to ensure that people can use this technology (30 mins) - What Paycor does ( 31 mins) - Why he is Positive for the Future of Ai (35 min)   and more     How to Contact Pratik Thantharate :   https://scholar.google.com/citations?hl=en&user=VEjDpX8AAAAJ https://www.linkedin.com/in/pratikt1988/ --- Send in a voice message: https://podcasters.spotify.com/pod/show/roy-coughlan8/message

Are you looking for ways to make your work stand out in a crowded industry, like sports? Or maybe looking for a topic with pretty clean data to create a portfolio project? In today's episode, we're chatting with Shri Khalpada, a D.C. area creative coder and Principal Software Engineer at Cleaning the Glass, which is an NBA analytics website founded by Ben Faulk that's available to the public and also has more robust tools for NBA teams. Shri shares how he increased his chances of landing a coveted sports analytics job, and a few lessons he's learned working with sports data that can be applied to any dataviz job. Let's go! Show notes: https://dataviztoday.com/shownotes/93 Grab my book Chart Spark, which has NINE prompts to help you be more innovative in your data communication: https://www.chartsparkbook.com If you think the book deserves a review, I'd be so grateful if you shared your favorite part in an Amazon or Goodreads review

On this week's episode of Screaming in the Cloud, Corey is joined by Kristi Perreault. Given Kristi's title of AWS Serverless Hero, Corey and Kristi discuss the origins and current state of the serverless world, the similarities between AI and serverless as the tech world moves into this next era, and why she emphasizes that serverless is not always the right solution for every issue. Kristi also opens up about her role as Principal Software Engineer at Liberty Mutual, and what she enjoys most about jet setting around the globe giving speeches.Highlights:(00:00) - Introducing Christy Perrealt(00:39) - The Unconventional Path to Becoming an AWS Serverless Hero(05:05) - Exploring the Boundaries of Cloud Education(10:53) - The Challenges of Keeping Up with Rapid Tech Changes(11:51) - Redefining Serverless: Beyond the Hype(13:12) - The Evolution of Serverless and Its Impact(21:55) - Staying Grounded Amidst Technological Zealotry(27:18) - Python Development in the Cloud(29:31) - Upcoming Talks and Where to Connect with KristiAbout KristiKristi Perreault is an AWS Serverless Hero and a Principal Software Engineer at Liberty Mutual Insurance, where her focus is serverless-first cloud enablement. She has over 5 years of industry experience, holds an M.S. in Electrical & Computer Engineering, and is very passionate about promoting women in technology. She is an established speaker, appearing in over 35 conferences, podcasts, panels, and more. Kristi founded the Serverless Denver meetup, and currently co-organizes the Portsmouth, NH AWS User Group and CDK Day. Outside of work and the serverless tech space, Kristi can be found reading a good book in her tiny home, enjoying a good poke bowl, or jet setting all over the world.Links:Linkedin: https://www.linkedin.com/in/kristi-perreault/Twitter: @kperreault95AWS Portsmouth User Group: https://www.meetup.com/aws-portsmouth-user-group/AWS Usergroup Belfast: https://www.meetup.com/aws-usergroup-belfast/

We spoke with Vigith Maurice, a principal engineer at Intuit and the co-creator of Numaproj, during the booth crawl at KubeCon. Vigith introduces Numaproj, a streaming platform designed for real-time analytics, machine learning inference, and ease of use across various developer disciplines. Recently released as version 1.0, Numaproj aims to make streaming accessible to all, requiring no new learning for those familiar with Kubernetes. With a few external contributors and usage within Intuit, the project seeks to expand its adoption and get community feedback.  00:00 Introduction 00:26 Overview of Numaproj 00:52 The Challenges and Solutions in Streaming 02:45 Community Contributions and Future Needs 03:38 Real-world Applications 06:27 Unexpected Uses 07:40 Closing Remarks and Future Expectations Guest: Vigith Maurice is a co-creator of Numaproj, and Principal Software Engineer for the Intuit Observability and Analytics team in Mountain View, California. One of Vigith's current day-to-day focus areas is on the various challenges in building scalable data and AIOps solutions for both batch and high throughput systems. He is pivotal in building the streaming platform to ease data engineering. Previously, he has been a key driver for Intuit's journey to Big Data-first. He also led various engineering initiatives at Yahoo!

Today I am speaking with Pablo Carranza Velez, Principal Software Engineer at Edge & Node. Pablo previously joined the podcast in February 2023 for a panel discussion on The Graph's transition to Arbitrum One during Episode 105.In this episode, we take a more in-depth look into Pablo's personal journey, tracing his educational pursuits and early fascination with the space industry. Pablo shares insights into his evolution as a developer, from learning to program to his eventual foray into startups. Our conversation then navigates towards Pablo's transition into the dynamic landscape of web3 and his role at Edge & Node.We also talk about two significant initiatives Pablo has been working on. First, we discuss the highly successful L2 migration, which Pablo played a pivotal role in orchestrating. Second, we discuss Graph Horizon, an ambitious proposal from Edge & Node that Pablo has been instrumental in shaping. Recently, he authored a comprehensive Forum post detailing the proposal, providing The Graph community with a lot of important context.Show Notes and TranscriptsThe GRTiQ Podcast takes listeners inside web3 and The Graph (GRT) by interviewing members of the ecosystem.  Please help support this project and build the community by subscribing and leaving a review.Twitter: GRT_iQwww.GRTiQ.com 

Laura Nolan, Principal Software Engineer at Stanza, joins Corey on Screaming in the Cloud to offer insights on how to use SRE to avoid disastrous and lengthy production delays. Laura gives a rich history of her work with SREcon, why her approach to SRE is about first identifying the biggest fire instead of toiling with day-to-day issues, and why the lack of transparency in systems today actually hurts new engineers entering the space. Plus, Laura explains to Corey why she dedicates time to work against companies like Google who are building systems to help the government (inefficiently) select targets during wars and conflicts.About LauraLaura Nolan is a software engineer and SRE. She has contributed to several books on SRE, such as the Site Reliability Engineering book, Seeking SRE, and 97 Things Every SRE Should Know. Laura is a Principal Engineer at Stanza, where she is building software to help humans understand and control their production systems. Laura also serves as a member of the USENIX Association board of directors. In her copious spare time after that, she volunteers for the Campaign to Stop Killer Robots, and is half-way through the MSc in Human Factors and Systems Safety at Lund University. She lives in rural Ireland in a small village full of medieval ruins.Links Referenced: Company Website: https://www.stanza.systems/ Twitter: https://twitter.com/lauralifts LinkedIn: https://www.linkedin.com/in/laura-nolan-bb7429/ 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. My guest today is someone that I have been low-key annoying to come onto this show for years, and finally, I have managed to wear her down. Lauren Nolan is a Principal Software Engineer over at Stanza. At least that's what you're up to today, last I've heard. Is that right?Laura: That is correct. I'm working at Stanza, and I don't want to go on and on about my startup, but I'm working with Niall Murphy and Joseph Bironas and Matthew Girard and a bunch of other people who more recently joined us. We are trying to build a load management SaaS service. So, we're interested in service observability out of the box, knowing if your critical user journeys are good or bad out of the box, being able to prioritize your incoming requests by what's most critical in terms of visibility to your customers. So, an emerging space. Not in the Gartner Group Magic Circle yet, but I'm sure at some point [laugh].Corey: It is surreal to me to hear you talk about your day job because for, it feels like, the better part of a decade now, “Laura, Laura… oh, you mean USENIX Laura?” Because you are on the USENIX board of directors, and in my mind, that is what is always short-handed to what you do. It's, “Oh, right. I guess that isn't your actual full-time job.” It's weird. It's almost like seeing your teacher outside of the elementary school. You just figure that they fold themselves up in the closet there when you're not paying attention. I don't know what you do when SREcon is not in process. I assume you just sit there and wait for the next one, right?Laura: Well, no. We've run four of them in the last year, so there hasn't been very much waiting. I'm afraid. Everything got a little bit smooshed up together during the pandemic, so we've had a lot of events coming quite close together. But no, I do have a full-time day job. But the work I do with USENIX is just as a volunteer. So, I'm on the board of directors, as you say, and I'm on the steering committee for all of the global SREcon events, and typically is often served by the program committee as well. And I'm sort of there, annoying the chairs to, “Hey, do your thing on time,” very much like an elementary school teacher, as you say.Corey: I've been a big fan of USENIX for a while. One of the best interview processes I ever saw was closely aligned with evaluating candidates along with USENIX SAGE levels to figure out what level of seniority are they in different areas. And it was always viewed through the lens of in what types of consulting engagements will the candidate shine within, not the idea of, “Oh, are you good or are you crap? And spoiler, if I'm asking the question, I'm of course defaulting myself to goading you to crap.” Like the terrible bespoke artisanal job interview process that so many companies do. I love how this company had built this out, and I asked them about it, and, “Oh, yeah, it comes—that dates back to the USENIX SAGE things.” That was one of my first encounters with what USENIX actually did. And the more I learned, the more I liked. How long have you been involved with the group?Laura: A relatively short period of time. I think I first got involved with USENIX in around 2015, going to [Lisa 00:03:29] and then going on to SREcon. And it was all by accident, of course. I fell onto the SREcon program committee somehow because I was around. And then because I was still around and doing stuff, I got eventually—you know, got co-opted into chairing and onto the steering committee and so forth.And you know, it's like everything volunteer. I mean, people who stick around and do stuff tend to be kept around. But USENIX is quite important to me. We have an open access policy, which is something that I would like to see a whole lot more of, you know, we put everything right out there for free as soon as it is ready. And we are constantly plagued by people saying, “Hey, where's my SREcon video? The conference was like two weeks ago.” And we're like, “No, no, we're still processing the videos. We'll be there; they'll be there.”We've had people, like, literally offer to pay extra money to get the videos sooner, but [laugh] we're, like, we are open access. We are not keeping the videos away from you. We just aren't ready yet. So, I love the open access policy and I think what I like about it more than anything else is the fact that it's… we are staunchly non-vendor. We're non-technology specific and non-vendor.So, it's not, like, say, AWS re:Invent for example or any of the big cloud vendor conferences. You know, we are picking vendor-neutral content by quality. And as well, as anyone who's ever sponsored SREcon or any of the other events will also tell you that that does not get you a talk in the conference program. So, the content selection is completely independent, and in fact, we have a complete Chinese wall between the sponsorship organization and the content organization. So, I mean, I really like how we've done that.I think, as well, it's for a long time been one of the family of conferences that our organizations have conferences that has had the best diversity. Not perfect, but certainly better than it was, although very, very unfortunately, I see conference diversity everywhere going down after the pandemic, which is—particularly gender diversity—which is a real shame.Corey: I've been a fan of the SREcon conferences for a while before someone—presumably you; I'm not sure—screwed up before the pandemic and apparently thought they were talking about someone else, and I was invited to give a keynote at SREcon in EMEA that I co-presented with John Looney. Which was fun because he and I met in person for the first time three hours beforehand, beat together our talk, then showed up an hour beforehand, found there will be no confidence monitor, went away for the next 45 minutes and basically loaded it all into short term cash and gave a talk that we could not repeat if we had to for a million dollars, just because it was so… you're throwing the ball to your partner on stage and really hoping they're going to be able to catch it. And it worked out. It was an anger subtext translator skit for a bit, which was fun. All the things that your manager says but actually means, you know, the fun sort of approach. It was zany, ideally had some useful takeaways to it.But I loved the conference. That was one of the only SREcons that I found myself not surprised to discover was coming to town the next week because for whatever reason, there's presumably a mailing list that I'm not on somewhere where I get blindsided by, “Oh, yeah, hey, didn't you know SREcon is coming up?” There's probably a notice somewhere that I really should be paying attention to, but on the plus side, I get to be delightfully surprised every time.Laura: Indeed. And hopefully, you'll be delightfully surprised in March 2024. I believe it's the 18th to the 20th, when SREcon will be coming to town in San Francisco, where you live.Corey: So historically, in addition to, you know, the work with USENIX, which is, again, not your primary occupation most days, you spent over five years at Google, which of course means that you have strong opinions on SRE. I know that that is a bit dated, where the gag was always, it's only called SRE if it comes from the Mountain View region of California, otherwise it's just sparkling DevOps. But for the initial take of a lot of the SRE stuff was, “Here's how to work at Google.” It has progressed significantly beyond that to the point where companies who have SRE groups are no longer perceived incorrectly as, “Oh, we just want to be like Google,” or, “We hired a bunch of former Google people.”But you clearly have opinions to this. You've contributed to multiple books on SRE, you have spoken on it at length. You have enabled others to speak on it at length, which in many ways, is by far the better contribution. You can only go so far scaling yourself, but scaling other people, that has a much better multiplier on it, which feels almost like something an SRE might observe.Laura: It is indeed something an SRE might observe. And also, you know, good catch because I really felt you were implying there that you didn't like my book contributions. Oh, the shock.Corey: No. And to be clear, I meant [unintelligible 00:08:13], strictly to speaking.Laura: [laugh].Corey: Books are also a great one-to-many multiplier because it turns out, you can only shove so many people into a conference hall, but books have this ability to just carry your words beyond the room that you're in a way that video just doesn't seem to.Laura: Ah, but open access video that was published on YouTube, like, six weeks ahead [laugh]. That scales.Corey: I wish. People say they want to write a book and I think they're all lying. I think they want to have written the book. That's my philosophy on it. I do not understand people who've written a book. Like, “So, what are you going to do now?” “I'm going to write another book.” “Okay.” I'm going to smile, not take my eyes off you for a second and back away slowly because I do not understand your philosophy on that. But you've worked on multiple books with people.Laura: I actually enjoy writing. I enjoy the process of it because I always learn something when I write. In fact, I learn a lot of things when I write, and I enjoy that crafting. I will say I do not enjoy having written things because for me, any achievement once I have achieved it is completely dead. I will never think of it again, and I will think only of my excessively lengthy-to do list, so I clearly have problems here. But nevertheless. It's exactly the same with programming projects, by the way. But back to SRE we were talking about SRE. SRE is 20 now. SRE can almost drink alcohol in the US, and that is crazy.Corey: So, 2003 was the founding of it, then.Laura: Yes.Corey: Yay, I can do simple arithmetic in my head, still. I wondered how far my math skills had atrophied.Laura: Yes. Good job. Yes, apparently invented in roughly 2003. So, the—I mean, from what I understand Google's publishing of the, “20 years of SRE at Google,” they have, in the absence of an actual definite start date, they've simply picked. Ben Treynor's start date at Google as the start date of SRE.But nevertheless, [unintelligible 00:09:58] about 20 years old. So, is it all grown up? I mean, I think it's become heavily commodified. My feeling about SRE is that it's always been this—I mean, you said it earlier, like, it's about, you know, how do I scale things? How do I optimize my systems? How do I intervene in systems to solve problems to make them better, to see where we're going to be in pain and six months, and work to prevent that?That's kind of SRE work to me is, figure out where the problems are, figure out good ways to intervene and to improve. But there's a lot of SRE as bureaucracy around at the moment where people are like, “Well, we're an SRE team, so you know, you will have your SLO Golden Signals, and you will have your Production Readiness Checklists, which will be the things that we say, no matter how different your system is from what we designed this checklist for, and that's it. We're doing SRE now. It's great.” So, I think we miss a lot there.My personal way of doing SRE is very much more about thinking, not so much about the day-to-day SLO [excursion-type 00:10:56] things because—not that they're not important; they are important, but they will always be there. I always tend to spend more time thinking about how do we avoid the risk of, you know, a giant production fire that will take you down for days, or God forbid, more than days, you know? The sort of, big Roblox fire or the time that Meta nearly took down the internet in late-2021, that kind of thing. So, I think that modern SRE misses quite a lot of that. It's a little bit like… so when BP, when they had the Deepwater Horizon disaster on that very same day, they received an award for minimizing occupational safety risks in their environment. So, you know, [unintelligible 00:11:41] things like people tripping and—Corey: Must have been fun the next day. “Yeah, we're going to need that back.”Laura: [laugh] people tripping and falling, and you know, hitting themselves with a hammer, they got an award because it was so safe, they had very little of that. And then this thing goes boom.Corey: And now they've tried to pivot into an optimization award for efficiency, like, we just decided to flash fry half the sea life in the Gulf at once.Laura: Yes. Extremely efficient. So, you know, I worry that we're doing SRE a little bit like BP. We're doing it back before Deepwater Horizon.Corey: I should disclose that I started my technical career as a grumpy old Unix sysadmin—because it's not like you ever see one of those who's happy or young; didn't matter that I was 23 years old, I was grumpy and old—and I have viewed the evolution since then have going from calling myself a sysadmin to a DevOps engineer to an SRE to a platform engineer to whatever we're calling it this week, I still view it as fundamentally the same job, in the sense that the responsibility has not changed, and that is keep the site or environment up. But the tools, the processes and the techniques we apply to it have evolved. Is that accurate? Does it sound like I'm spouting nonsense? You're far closer to the SRE world than I ever was, but I'm curious to get your take on that perspective. And please feel free to tell me I'm wrong.Laura: No, no. I think you're completely right. And I think one of the ways that I think is shifted, and it's really interesting, but when you and I were, when we were young, we could see everything that was happening. We were deploying on some sort of Linux box or other sort of Unix box somewhere, most likely, and if we wanted, we could go and see the entire source code of everything that our software was running on. And kids these days, they're coming up, and they are deploying their stuff on RDS and ECS and, you know, how many layers of abstraction are sitting between them and—Corey: “I run Kubernetes. That means I don't know where it runs, and neither does anyone else.” It's great.Laura: Yeah. So, there's no transparency anymore in what's happening. So, it's very easy, you get to a point where sometimes you hit a problem, and you just can't figure it out because you do not have a way to get into that system and see what's happening. You know, even at work, we ran into a problem with Amazon-hosted Prometheus. We were like, “This will be great. We'll just do that.” And we could not get some particular type of remote write operation to work. We just could not. Okay, so we'll have to do something else.So, one of the many, many things I do when I'm not, you know, trying to run the SREcon conference or do actual work or definitely not write a book, I'm studying at Lund University at the moment. I'm doing this master's degree in human factors and system safety. And one of the things I've realized since doing that program is, in tech, we missed this whole 1980s and 1990s discipline of cognitive systems theory, cognitive systems engineering. This is what people were doing. They were like, how can people in the control room in nuclear plants and in the cockpit in the airplane, how can they get along with their systems and build a good mental model of the automation and understand what's going on?We missed all that. We came of age when safety science was asking questions like how can we stop organizational failures like Challenger and Columbia, where people are just not making the correct decisions? And that was a whole different sort of focus. So, we've missed all of this 1980s and 1990s cognitive system stuff. And there's this really interesting idea there where you can build two types of systems: you can build a prosthesis which does all your interaction with a system for you, and you can see nothing, feel nothing, do nothing, it's just this black box, or you can have an amplifier, which lets you do more stuff than you could do just by yourself, but lets you still get into the details.And we build mostly prostheses. We do not build amplifiers. We're hiding all the details; we're building these very, very opaque abstractions. And I think it's to the detriment of—I mean, it makes our life harder in a bunch of ways, but I think it also makes life really hard for systems engineers coming up because they just can't get into the systems as easily anymore unless they're running them themselves.Corey: I have to confess that I have a certain aversion to aspects of SRE, and I'm feeling echoes of it around a lot of the human factor stuff that's coming out of that Lund program. And I think I know what it is, and it's not a problem with either of those things, but rather a problem with me. I have never been a good academic. I have an eighth grade education because school is not really for me. And what I loved about being a systems administrator for years was the fact that it was like solving puzzles every day.I got to do interesting things, I got to chase down problems, and firefight all the time. And what SRE is represented is a step away from that to being more methodical, to taking on keeping the site up as a discipline rather than an occupation or a task that you're working on. And I think that a lot of the human factors stuff plays directly into it. It feels like the field is becoming a lot more academic, which is a luxury we never had, when holy crap, the site is down, we're going to go out of business if it isn't back up immediately: panic mode.Laura: I got to confess here, I have three master's degrees. Three. I have problems, like I said before. I got what you mean. You don't like when people are speaking in generalizations and sort of being all theoretical rather than looking at the actual messy details that we need to deal with to get things done, right? I know. I know what you mean, I feel it too.And I've talked about the human factors stuff and theoretical stuff a fair bit at conferences, and what I always try to do is I always try and illustrate with the details. Because I think it's very easy to get away from the actual problems and, you know, spend too much time in the models and in the theory. And I like to do both. I will confess, I like to do both. And that means that the luxury I miss out on is mostly sleep. But here we are.Corey: I am curious as far as what you've seen as far as the human factors adoption in this space because every company for a while claimed to be focused on blameless postmortems. But then there would be issues that quickly turned into a blame Steve postmortem instead. And it really feels, at least from a certain point of view, that there was a time where it seemed to be gaining traction, but that may have been a zero interest rate phenomenon, as weird as that sounds. Do you think that the idea of human factors being tied to keeping systems running in a computer sense has demonstrated staying power or are you seeing a recession? It could be I'm just looking at headlines too much.Laura: It's a good question. There's still a lot of people interested in it. There was a conference in Denver last February that was decently well attended for, you know, a first initial conference that was focusing on this issue, and this very vibrant Slack community, the LFI and the Learning from Incidents in Software community. I will say, everything is a little bit stretched at the moment in industry, as you know, with all the layoffs, and a lot of people are just… there's definitely a feeling that people want to hunker down and do the basics to make sure that they're not seen as doing useless stuff and on the line for layoffs.But the question is, is this stuff actually useful or not? I mean, I contend that it is. I contend that we can learn from failures, we can learn from what we're doing day-to-day, and we can do things better. Sometimes you don't need a lot of learning because what's the biggest problem is obvious, right [laugh]? You know, in that case, yeah, your focus should just be on solving your big obvious problem, for sure.Corey: If there was a hierarchy of needs here, on some level, okay, step one, is the building—Laura: Yes.Corey: Currently on fire? Maybe solve that before thinking about the longer-term context of what this does to corporate culture.Laura: Yes, absolutely. And I've gone into teams before where people are like, “Oh, well, you're an SRE, so obviously, you wish to immediately introduce SLOs.” And I can look around and go, “Nope. Not the biggest problem right now. Actually, I can see a bunch of things are on fire. We should fix those specific things.”I actually personally think that if you want to go in and start improving reliability in a system, the best thing to do is to start a weekly production meeting if the team doesn't have that, actually create a dedicated space and time for everyone to be able to get together, discuss what's been happening, discuss concerns and risks, and get all that stuff out in the open. I think that's very useful, and you don't need to spend however long it takes to formally sit down and start creating a bunch of SLOs. Because if you're not dealing with a perfectly spherical web service where you can just use the Golden Signals and if you start getting into any sorts of thinking about data integrity, or backups, or any sorts of asynchronous processing, these sorts of things, they need SLOs that are a lot more interesting than your standard error rate and latency. Error rate and latency gets you so far, but it's really just very cookie-cutter stuff. But people know what's wrong with their systems, by and large. They may not know everything that's wrong with their systems, but they'll know the big things, for sure. Give them space to talk about it.Corey: Speaking of bigger things and turning into the idea of these things escaping beyond pure tech, you have been doing some rather interesting work in an area that I don't see a whole lot of people that I talked to communicating about. Specifically, you're volunteering for the campaign to stop killer robots, which ten years ago would have made you sound ridiculous, and now it makes you sound like someone who is very rationally and reasonably calling an alarm on something that is on our doorstep. What are you doing over there?Laura: Well, I mean, let's be real, it sounds ridiculous because it is ridiculous. I mean, who would let a computer fly around to the sky and choose what to shoot at? But it turns out that there are, in fact, a bunch of people who are building systems like that. So yeah, I've been volunteering with the campaign for about the last five years, since roughly around the time that I left Google, in fact, because I got interested in that around about the time that Google was doing the Project Maven work, which was when Google said, “Hey, wouldn't it be super cool if we took all of this DoD video footage of drone video footage, and, you know, did a whole bunch of machine-learning analysis on it and figured out where people are going all the time? Maybe we could click on this house and see, like, a whole timeline of people's comings and goings and which other people they are sort of in a social network with.”So, I kind of said, “Ahh… maybe I don't want to be involved in that.” And I left Google. And I found out that there was this campaign. And this campaign was largely lawyers and disarmament experts, people of that nature—philosophers—but also a few technologists. And for me, having run computer systems for a large number of years at this point, the idea that you would want to rely on a big distributed system running over some janky network with a bunch of 18-year-old kids running it to actually make good decisions about who should be targeted in a conflict seems outrageous.And I think almost every [laugh] software operations person, or in fact, software engineer that I've spoken to, tends to feel the same way. And yet there is this big practical debate about this in international relations circles. But luckily, there has just been a resolution in the UN just in the last day or two as we record this, the first committee has, by a very large majority, voted to try and do something about this. So hopefully, we'll get some international law. The specific interventions that most of us in this field think would be good would be to limit the amount of force that autonomous weapon, or in fact, an entire set of autonomous weapons in a region would be able to wield because there's a concern that should there be some bug or problem or a sort of weird factor that triggers these systems to—Corey: It's an inevitability that there will be. Like, that is not up for debate. Of course, it's going to break in 2020, the template slide deck that AWS sent out for re:Invent speakers had a bunch of clip art, and one of them was a line art drawing of a ham with a bone in it. So, I wound up taking that image, slapping it on a t-shirt, captioning it “AWS Hambone,” and selling that as a fundraiser for 826 National.Laura: [laugh].Corey: Now, what happened next is that for a while, anyone who tweeted the phrase “AWS Hambone” would find themselves banned from Twitter for the next 12 hours due to some weird algorithmic thing where it thought that was doxxing or harassment or something. And people on the other side of the issue that you're talking about are straight face-idly suggesting that we give that algorithm [unintelligible 00:24:32] tool a gun.Laura: Or many guns. Many guns.Corey: I'm sorry, what?Laura: Absolutely.Corey: Yes, or missiles or, heck, let's build a whole bunch of them and turn them loose with no supervision, just like we do with junior developers.Laura: Exactly. Yes, so many people think this is a great idea, or at least they purport to think this is a great idea, which is not always the same thing. I mean, there's lots of different vested interests here. Some people who are proponents of this will say, well, actually, we think that this will make targeting more accurate, less civilians will actually will die as a result of this. And the question there that you have to ask is—there's a really good book called Drone by Chamayou, Grégoire Chamayou, and he says that there's actually three meanings to accuracy.So, are you hitting what you're aiming at is one of it—one thing. And that's a solved problem in military circles for quite some time. You got, you know, laser targeting, very accurate. Then the other question is, how big is the blast radius? So, that's just a matter of, you know, how big an explosion are you going to get? That's not something that autonomy can help with.The only thing that autonomy could even conceivably help with in terms of accuracy is better target selection. So, instead of selecting targets that are not valid targets, selecting more valid targets. But I don't think there's any good reason to think that computers can solve that problem. I mean, in fact, if you read stuff that military experts write on this, and I've got, you know, lots of academic handbooks on military targeting processes, they will tell you, it's very hard and there's a lot of gray areas, a lot of judgment. And that's exactly what computers are pretty bad at. Although mind you, I'm amused by your Hambone story and I want to ask if AWS Hambone is a database?Corey: Anything is a database, if you hold it wrong.Laura: [laugh].Corey: It's fun. I went through a period of time where, just for fun, I would ask people to name an AWS service and I would talk about how you could use it incorrectly as a database. And then someone mentioned, “What about AWS Neptune,” which is their graph database, which absolutely no one understands, and the answer there is, “I give up. It's impossible to use that thing as a database.” But everything else can be. Like, you know, the tagging system. Great, that has keys and values; it's a database now. Welcome aboard. And I didn't say it was a great database, but it is a free one, and it scales to a point. Have fun with it.Laura: All I'll say is this: you can put labels on anything.Corey: Exactly.Laura: We missed you at the most recent SREcon EMEA. There was a talk about Google's internal Chubby system and how people started using it as a database. And I did summon you in Slack, but you didn't show up.Corey: No. Sadly, I've gotten a bit out of the SRE space. And also, frankly, I've gotten out of the community space for a little while, when it comes to conferences. And I have a focused effort at the start of 2024 to start changing that. I am submitting CFPs left and right.My biggest fear is that a conference will accept one of these because a couple of them are aspirational. “Here's how I built the thing with generative AI,” which spoiler, I have done no such thing yet, but by God, I will by the time I get there. I have something similar around Kubernetes, which I've never used in anger, but soon will if someone accepts the right conference talk. This is how I learned Git: I shot my mouth off in a CFP, and I had four months to learn the thing. It was effective, but I wouldn't say it was the best approach.Laura: [laugh]. You shouldn't feel bad about lying about having built things in Kubernetes, and with LLMs because everyone has, right?Corey: Exactly. It'll be true enough by the time I get there. Why not? I'm not submitting for a conference next week. We're good. Yeah, Future Corey is going to hate me.Laura: Have it build you a database system.Corey: I like that. I really want to thank you for taking the time to speak with me today. If people want to learn more, where's the best place for them to find you these days?Laura: Ohh, I'm sort of homeless on social media since the whole Twitter implosion, but you can still find me there. I'm @lauralifts on Twitter and I have the same tag on BlueSky, but haven't started to use it yet. Yeah, socials are hard at the moment. I'm on LinkedIn. Please feel free to follow me there if you wish to message me as well.Corey: And we will, of course, put links to that in the [show notes 00:28:31]. Thank you so much for taking the time to speak with me. I appreciate it.Laura: Thank you for having me.Corey: Laura Nolan, Principal Software Engineer at Stanza. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry, insulting comment that soon—due to me screwing up a database system—will be transmogrified into a CFP submission for an upcoming SREcon.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.

Neha Narkhede is a co-founder at Confluent, a data streaming software that raised at a $9.1b valuation in 2021. Neha later co-founded Oscilar, a no-code platform that helps companies detect and manage fraud. Before building these two companies, Neha was a Principal Software Engineer at LinkedIn where she co-created Apache Kafka. Neha is ranked #50 on Forbes' list of “America's Richest Self-Made Women 2023” with an estimated net worth of $520m. — In today's episode we discuss: The origins of Confluent, Kafka, and Oscilar How to become a successful second-time founder Advice for monetizing open source product Neha's unique GTM strategies How Confluent ran two businesses within one company Neha's path to founder market fit — Referenced: Apache Kafka: https://kafka.apache.org/ Confluent: https://www.confluent.io/ Confluent Cloud: https://www.confluent.io/confluent-cloud/ Jay Kreps, co-founder at Confluent: https://www.linkedin.com/in/jaykreps/ Jun Rao, co-founder at Confluent: https://www.linkedin.com/in/junrao/ MongoDB: https://www.mongodb.com/ Oscilar: https://oscilar.com/ — Where to find Neha: LinkedIn: https://www.linkedin.com/in/nehanarkhede/ Twitter/X: https://twitter.com/nehanarkhede Website: https://www.nehanarkhede.com/ — Where to find Brett: LinkedIn: https://www.linkedin.com/in/brett-berson-9986094/ Twitter/X: https://twitter.com/brettberson — Where to find First Round Capital: Website: https://firstround.com/ First Round Review: https://review.firstround.com/ Twitter: https://twitter.com/firstround Youtube: https://www.youtube.com/@FirstRoundCapital This podcast on all platforms: https://review.firstround.com/podcast — Timestamps: (00:00) Introduction (02:14)The origin story of Kafka (05:24) Co-creating Kafka at LinkedIn (07:31) Why open sourcing Kafka was a masterstroke (11:04) The unique nature of Confluent's Zero to One phase (16:35) Building for a specific customer early on (18:42) Inside Confluent's successful launch (20:12) Establishing Confluent as an enterprise company (22:00) The role of developer evangelism in Confluent's success (23:49) Using developer evangelism in category creation (26:41) Navigating early co-founder dynamics (30:06) Leveraging complementary founder skills (31:56) Advice for future founders (32:45) Building Confluent with monetization in mind (34:38) Monetizing open source products (36:05) GTM for subscription Saas versus consumption SaaS (39:48) The importance of founder-led GTM sales (40:58) Neha's order of operations for GTM sales (42:33) When to build out outbound sales (44:34) Adding SaaS to a software business (48:54) Choosing what to license and what to open source (52:38) How Confluent's co-founders decided on SaaS offering (56:04) Neha's journey as a second-time founder (58:54) Building Oscilar differently to Confluent (63:21) Going from speculation to product realization (69:06) Solving problems people are willing to pay for (71:13) Neha's “proactive research sprint” tactic (72:54) How Neha has applied this tactic

Neste episódio Emilio Aiolfi, Hugo Marques e Willian Martins, junto com o convidado Waldemar Neto, conversam sobre as responsabilidades do papel de Principal Software Engineer, incluindo liderança técnica, tomada de decisões de arquitetura e mentorias. Uma conversa bacana sobre como essas responsabilidades se aplicam ao trabalho do dia a dia de quem está nesse papel.

Hoje o papo é sobre cargos! Nesta conversa, vamos falar sobre as tendências, os desafios e as responsabilidades que vêm com o avanço da carreira no cargo de engenharia. Vem ver quem acompanha a gente neste papo!

Jack Herrington is a Principal Software Engineer. Misko Hevery is the Chief Technology Officer at Builder.io. They join the show to talk about "Qwik v1.0". Misko takes the lead as he shares its exciting new features. He explains what is the Panda CSS and how it works. Moreover, he dives into some of the "Qwiklabs projects", its benefits, and many more!SponsorsChuck's Resume Template Developer Book Club Become a Top 1% Dev with a Top End Devs MembershipLinksqwikQwiklabsPanda CSSSocialsLinkedIn: Jack HerringtonLinkedIn: Misko HeveryPicksAJ - The Legend of Zelda™Jack - Monkeytype Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacy

Derrick Stolee is a Principal Software Engineer at GitHub working on Git. We talk about Git 2.41, Scalar (a built-in repository manager for large repos), and more. Links https://twitter.com/stolee https://mastodon.online/@stolee https://git-scm.com https://github.blog/author/dstolee https://github.blog/2023-06-01-highlights-from-git-2-41 https://github.blog/2022-10-13-the-story-of-scalar Tell us what you think of PodRocket We want to hear from you! We want to know what you love and hate about the podcast. What do you want to hear more about? Who do you want to see on the show? Our producers want to know, and if you talk with us, we'll send you a $25 gift card! If you're interested, schedule a call with us (https://podrocket.logrocket.com/contact-us) or you can email producer Kate Trahan at kate@logrocket.com (mailto:kate@logrocket.com) Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Derrick Stolee.

In this episode, Titus Winters, Principal Software Engineer at Google, joins us to discuss why computing education should really focus on the craft of programming rather than the mathematical side, especially in an increasingly automated world; and just how much the programming industry has evolved and grown over time!

Today, Saron talks with Alice Goldfuss, Principal Software Engineer and Systems Programmer specializing in building resilient distributed systems at scale. Alice delivered industry-impacting talks on container platforms, infrastructure operations, and organizational best practices, as well as written on the SRE field, kernel crashes, and personal security. We hear about her coding journey and learn all about her take on various programs and the tech world as a whole. Show Links Compiler (sponsor) Porkbun (sponsor) How to Get Into SRE Rust CSS Notepad++ Inline CSS HTML4