Podcasts about developer relations engineer

  • 44PODCASTS
  • 62EPISODES
  • 46mAVG DURATION
  • 1MONTHLY NEW EPISODE
  • Apr 28, 2025LATEST

POPULARITY

20172018201920202021202220232024


Best podcasts about developer relations engineer

Latest podcast episodes about developer relations engineer

OpenObservability Talks
CNCF Ambassadors Share the Best of KubeCon EU 2025 - OpenObservability Talks S5E11

OpenObservability Talks

Play Episode Listen Later Apr 28, 2025 62:54


KubeCon Europe 2025 in London has wrapped up, and we're bringing you all the highlights, trends, and behind-the-scenes insights straight from the show floor!In this special recap episode, I'm joined by two CNCF Ambassadors and community powerhouses: Kasper Borg Nissen, the Co-Chair of this KubeCon as well as of the KubeCon 2024 editions, and a Developer Relations Engineer at Dash0; and William Rizzo, Consulting Architect at Mirantis and Linkerd Ambassador.Together, we unpack the major themes from the event—from platform engineering and internal developer platforms, to open source observability, and where Kubernetes is headed next. We also chat about the vibe of the community, emerging projects to watch, and important trends in European tech sphere.Whether you missed the conference or want to catch up on important updates you might have missed, this episode gives you a curated take straight from the experts who know the cloud-native space inside out.The episode was live-streamed on 22 April 2025 and the video is available at https://www.youtube.com/watch?v=JyxJOmOEBvQYou can read the recap post: https://medium.com/p/740258a5fa46OpenObservability Talks episodes are released monthly, on the last Thursday of each month and are available for listening on your favorite podcast app and on YouTube.We live-stream the episodes on Twitch and YouTube Live - tune in to see us live, and chime in with your comments and questions on the live chat.⁠⁠https://www.youtube.com/@openobservabilitytalks⁠  https://www.twitch.tv/openobservability⁠Show Notes:00:00 - intro03:28 - KubeCon impressions09:59 - Backstage turns 518:56 - CNCF turns 10 and CNCF annual survey27:22 - Sovereign cloud in Europe and the NeoNephos initiative33:55 - CI/CD use in production increases36:52 - OpenInfra joins the Linux Foundation40:16 - Cloud native local communities, DEI and the BIPOC initiative 51:11 - Observability query standardization SIG updates59:36 - outroResources:CNCF 2024 Annual Survey https://www.cncf.io/reports/cncf-annual-survey-2024/NeoNephos initiative for sovereign EU cloud: https://www.linkedin.com/feed/update/urn:li:share:7313115943075766273/ OpenInfra Foundation and OpenStack join The Linux Foundation: https://www.linkedin.com/feed/update/urn:li:share:7307839934072066048/ Backstage turns 5: https://www.linkedin.com/feed/update/urn:li:activity:7318163557206966272/ Kubernetes 1.33 release: https://www.linkedin.com/feed/update/urn:li:activity:7321054742174924800/Socials:Twitter:⁠ https://twitter.com/OpenObserv⁠YouTube: ⁠https://www.youtube.com/@openobservabilitytalks⁠Dotan Horovits============Twitter: @horovitsLinkedIn: www.linkedin.com/in/horovitsMastodon: @horovits@fosstodonBlueSky: @horovits.bsky.socialKasper Borg Nissen===============Twitter: https://www.twitter.com/phennexLinkedIn: https://www.linkedin.com/in/kaspernissen/BlueSky: https://bsky.app/profile/kaspernissen.xyz⁠William Rizzo===========Twitter: https://twitter.com/WilliamRizzo19LinkedIn: https://www.linkedin.com/in/william-rizzo/BlueSky: https://bsky.app/profile/williamrizzo.bsky.social

VisualMakers
#125 - a Developer's View on the No-Code Industry - with Alex from Plasmic

VisualMakers

Play Episode Listen Later Mar 20, 2025 66:38


In this episode I had the pleasure to speak with Alex Noel, Developer Relations Engineer at Plasmic - a visual development Plattform.Alex' background as a full-stack Developer made me wonder: why and how did he start to work for a visual development tool?We talked about AI and its place in the No-Code space, as well as the usefulness of the term “no-code” itself. Alex also shared his opinion about the importance of open source projects and his top 10 criteria for a good no-code tool.Relevant links:Plasmic's website: https://www.plasmic.app/Alex' LinkedIn: https://www.linkedin.com/in/alexnoelee/Pasmic is hiring! - https://www.plasmic.app/careers**////////// Gefällt dir unser VisualMakers Content? Werde selbst zum VisualMaker mit einem unserer vielen kostenlosen Kurse. Starte jetzt durch und werde No-Code Profi https://www.visualmakers.de/academy****////////// Folge uns auf:LinkedIn: https://bit.ly/3SfL6oOYoutube: https://bit.ly/3OF5jBjInstagram: https://bit.ly/3cMYH6NSlack: https://bit.ly/vm-slack****////////// Jetzt Newsletter abonnieren und keine No-Code News mehr verpassen! https://bit.ly/3cMYNeF**

Web3 with Sam Kamani
214: AI-Powered Meme Coins: Raghu on Kava's Hard.fun Revolution

Web3 with Sam Kamani

Play Episode Listen Later Jan 22, 2025 30:37


In this episode of Web3 with Sam Kamani, I chat with Raghu, Developer Relations Engineer at Kava.io and the driving force behind Hard.fun, an AI-powered meme coin launchpad. We discuss: Meme Coin Ecosystem: How Hard.fun simplifies token creation and why community-driven meme coins thrive. AI in Web3: Kava's plans for decentralized AI agents and models. Challenges and Growth: Educating meme coin creators, bridging liquidity gaps, and timing the market. Developer Support: Grants, incubations, and opportunities for builders on the Kava blockchain. Whether you're curious about launching a meme coin, leveraging AI in Web3, or exploring Kava's ecosystem, this episode has it all. Key Timestamps [00:00:00] Introduction: Sam introduces Raghu and the conversation's focus on Kava, Hard.fun, and the future of meme coins and decentralized AI. [00:01:00] Raghu's Journey into Web3: From finance and tech to blockchain development. Transitioning into Developer Relations at Kava.io. [00:04:00] What is Hard.fun? An AI-powered meme coin launchpad governed by Kava's HARD token. Simplifying meme coin creation and governance. [00:07:00] Differentiators of Hard.fun: Combining AI and blockchain for seamless user experiences. Decentralized governance and liquidity support for meme coins. [00:12:00] Kava's Decentralized AI Initiative: Developing decentralized AI models and agents. Plans for launching AI-powered solutions by 2025. [00:16:00] Challenges for Meme Coin Creators: Educating founders about bonding curves, liquidity, and market dynamics. The importance of community and narrative in meme coin success. [00:22:00] Developer Opportunities on Kava: Kava Rise: Grants for developers based on TVL. Incubation programs for dApps and meme coins. [00:27:00] Future Plans for Hard.fun: Expanding cross-chain compatibility via Stargate. Attracting users from other blockchain communities. [00:29:00] Closing Thoughts: The importance of timing the market and embracing multi-chain ecosystems. Raghu's advice: “Web3 is all about building—don't stop innovating.” Connect https://hard.fun/ https://www.kava.io/ https://x.com/hard_protocol https://x.com/KAVA_CHAIN https://www.linkedin.com/in/0xraghu/ Disclaimer Nothing mentioned in this podcast is investment advice and please do your own research. Finally, it would mean a lot if you can leave a review of this podcast on Apple Podcasts or Spotify and share this podcast with a friend.Be a guest on the podcast or contact us - https://www.web3pod.xyz/

Fireside with Voxgig
Episode 228, Zameer Fouzan, Lead Developer Relations Engineer at New Relic

Fireside with Voxgig

Play Episode Listen Later Dec 6, 2024 28:02


Today we're talking observability, open source, developer education and the politics of conference speaking. And we're doing it all with our amazing guest, Zameer Fouzan from New Relic. If you don't already know, New Relic helps engineers effectively deploy and run software with Full Stack Observability. Where other companies may do observability, but don't have a single language to communicate it, New Relic makes use of a single specification that caters to all languages and frameworks with the same APIs and languages. Part of Zameer's job is of course, speaking at various conferences and he chats to us about how he's evolved as a speaker since first starting out, and gives us his best advice for both new and experienced speakers. Reach out to Zameer here: https://www.linkedin.com/in/zmrfzn/ Check out New Relic's past and upcoming events: https://newrelic.com/events Find out more and listen to previous podcasts here: https://www.voxgig.com/podcast Subscribe to our newsletter for weekly updates and information about upcoming meetups: https://voxgig.substack.com/ Join the Dublin DevRel Meetup group here: www.devrelmeetup.com

Fireside with Voxgig
Episode 211, Tejas Kumar, Developer Relations Engineer and Host of the ConTejas Code Podcast

Fireside with Voxgig

Play Episode Listen Later Sep 19, 2024 36:30


We're delighted to welcome Tejas Kumar back to the Fireside podcast! Tejas is a particularly relevant guest for us, as he takes us behind the scenes of his own wonderful podcast - ConTejas Code. We had Tejas on the podcast last year, and we were excited to hear about all the new developments for him in the last year. Tejas believes that when it comes to AI, it's increasingly obvious that some developments are inevitable, and the sooner we lean into that fact, and start to work with the technology, rather than against it, we can unlock a lot of time and energy that is currently tied up in simple, yet time-consuming tasks. He takes us into his process as a podcaster. The way Tejas describes it sounds like a breeze, he sits down, talks to a guest, then uploads everything. There's more to be done, of course, but day to day the outlines, scheduling and transcripts are all taken care of by AI. This is a perfect example of what AI can do for us when we embrace it. Add to that - it's podcasting! The stakes are relatively low when compared to other potential AI integrations in, let's say, the medical field for example. If your AI misspells a word, no one gets sued - or at least we don't think anyone's tried that yet. These adaptations Tejas has made have allowed him to focus on the very part of his job as a host that makes it interesting, and fun - hosting! We get into the nature of podcasting, and how efficient it can be as a place to create content. If you have a thirty minute podcast, then you have three or four clips that you can take from that. If your podcast has video, those clips can now become shorts, or reels, and you've opened up a whole new element to it that fits within your existing structure. Tejas has a deep admiration for his guests, and this is clear in the way he discusses them - there's a reason that ConTejas Code episodes are two hours long each, he has a burning curiosity about people, and a desire to connect that is clear even when he's on the other side of the table. For any would-be podcasters out there, this episode - and Tejas in general - might be a good place to start when looking for inspiration both practically, and ideologically. Reach out to Tejas here: https://www.linkedin.com/in/tejasq/ Check out Tejas' website: https://tej.as/ Listen to the ConTejas Code podcast: https://shows.acast.com/contejas-code Find out more and listen to previous podcasts here: https://www.voxgig.com/podcast Subscribe to our newsletter for weekly updates and information about upcoming meetups: https://voxgig.substack.com/ Join the Dublin DevRel Meetup group here: http://www.devrelmeetup.com

The Geospatial Index
Wherobots

The Geospatial Index

Play Episode Listen Later Jul 12, 2024 74:45


Will Lyon, Developer Relations Engineer at Wherobots, talks about nothing less than producing a digital mind and memory for humanity. It was a very exciting conversation, finally we are into the visionary potential of our industry. Will was an endlessly patient and kind guest. For example, he did some jargon busting at the start to help those of us unfamiliar with planet scale anlytics to understand key concepts for storage and processing at scale. Thank you Will for taking the time to show us all how to deliver on a computing system that will assist our species to live the role of planetary steward. THE GEOSPATIAL INDEX The Geospatial Index is a comprehensive listing of all publicly traded geospatial businesses worldwide. Why? The industry is growing at ~10% annually. This varies significantly, however, by sub index. For only $58,000 to start, this growth rate is $5,000,000 over a working life. This channel, Bluesky account, newsletter, watchlist and podcast express the view that you are serious about geospatial if you take the view of an investor, venture capitalist or entrepreneur. You are expected to do your own research. This is not a replacement for that. This is not investment advice. Consider it entertainment. NOT THE OPINION OF MY EMPLOYER NOT YOUR FIDUCIARY NOT INVESTMENT ADVICE Bluesky: https://bsky.app/profile/geospatialindex.bsky.social LinkedIn: https://uk.linkedin.com/in/geospatialindex Watchlist: ⁠https://www.tradingview.com/watchlists/123254792/ Newsletter: https://www.geospatial.money/ Podcast: https://open.spotify.com/show/5gpQUsaWxEBpYCnypEdHFC

Open at Intel
How to Make Your First Open Source Contributions

Open at Intel

Play Episode Listen Later Jun 12, 2024 27:48


We spoke with Edoardo Dusi from Sparkfabrik about Edoardo's career path from a backend software engineer specializing in Drupal to his current role in Developer Relations (DevRel). He shared his experiences and the importance of community involvement when working with open source software. He highlighted the supportive nature of open source communities and provided advice for newcomers. We also covered the work of the Open Source Security Foundation (OpenSSF) and the significance of security in open source projects. 00:00 Welcome and Introduction 01:03 Sparkfabrik and Drupal 02:01 Exploring KubeCon 02:56 Getting Involved in Open Source 06:10 Challenges in Modern Open Source 08:37 Joining OpenSSF 11:21 Importance of Security in Open Source 13:01 European Perspectives on Security 14:14 The Role of Big Tech in Open Source 14:36 Community Contributions and Impact 16:34 Navigating the Contribution Process 21:24 Advice for New Open Source Contributors 25:47 The Human Side of Software Development Guest: Edoardo Dusi is a Developer Relations Engineer at SparkFabrik, a company that helps organisations build digital products with open source technologies. He has a strong software developer and team leader background, working on various projects and platforms. He is passionate about creating and sharing content that educates and inspires other developers, such as tech talks, videos, podcasts, conferences, and more. He enjoys connecting with the developer community and promoting the benefits of open source software.

Dev Sem Fronteiras
Developer Relations Engineer em IA no Google em Londres, Inglaterra - Dev Sem Fronteiras #141

Dev Sem Fronteiras

Play Episode Listen Later May 22, 2024 47:01


O mogicruzense Gus fez graduação e mestrado na USP, na época em que se trabalhava com disquetes e Visual Studio. Após passar anos desenvolvendo ferramentas para o mercado financeiro e se interessar por desenvolvimento Android, Gus teve a chance de fazer uma entrevista para o Google em Nova York. Quando não conquistou a vaga, decidiu estudar para aproveitar a próxima oportunidade de se mudar para fora do Brasil. E ela veio, mas em Londres. Neste episódio, Gus conta sua trajetória até se tornar Developer Relations de IA do Google, seu envolvimento com o projeto Gemma, e como foi sua adaptação na vida pessoal e profissional na terra do outro Rei Charles. Fabrício Carraro, o seu viajante poliglota Gus Martins, Developer Relations Engineer em IA no Google Links: Google Gemma Keras Jax Threads do Gus Discord do Gemma Conheça a Escola de Inteligência Artificial da Alura, mergulhe com profundidade no universo da IA aplicada a diferentes áreas de atuação e domine as principais ferramentas que estão moldando o agora, como ChatGPT e Midjourney. TechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões. #7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/ Ouvintes do podcast Dev Sem Fronteiras têm 10% de desconto em todos os planos da Alura Língua. Basta ir a https://www.aluralingua.com.br/promocao/devsemfronteiras/e começar a aprender inglês e espanhol hoje mesmo!  Produção e conteúdo: Alura Língua Cursos online de Idiomas – https://www.aluralingua.com.br/ Alura Cursos online de Tecnologia – https://www.alura.com.br/ Edição e sonorização: Rede Gigahertz de Podcasts

GRTiQ Podcast
Zubin Pratap - Software Engineer & Developer Relations Engineer at Chainlink Labs

GRTiQ Podcast

Play Episode Listen Later Apr 5, 2024 47:51


Today I am speaking with Zubin Pratap, Software Engineer and Developer Relations Engineer at Chainlink Labs. Chainlink is renowned for pioneering how blockchains connect with the real world! Ever since launching the podcast, I have sought to have someone from the Chainlink community on, and I am very happy it was Zubin!During our discussion, Zubin shares his remarkable journey, transitioning from a career in law to entrepreneurship, then making his way into tech, including a stint at Google, before joining Chainlink Labs. Along the way, Zubin offers valuable insights into his career and career management, developments at Chainlink, and his vision for the future of web3.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 

Modern Web
Modern Web Podcast S11E19- It's Impossible for this Code to Fail - with Loren Sands-Ramshaw

Modern Web

Play Episode Listen Later Jan 24, 2024 41:01


Loren Sands-Ramshaw, Developer Relations Engineer at Temporal joins Rob Ocel to talk about reliable application development. They introduce the topic of durable execution and talk about reliability in systems, unraveling common issues developers face and showcase the benefits that durable execution can bring to software development. They also talk about the challenges of traditional programming and the complexities of event-driven architecture. Sponsored by This Dot Labs Watch this episode on YouTube! Read more on our blog!  

Over The Edge
Generative AI at the Edge with Daniel Situnayake, Head of ML and Jenny Plunkett, Senior Developer Relations Engineer at Edge Impulse

Over The Edge

Play Episode Listen Later Nov 15, 2023 54:29


How is AI being used at the edge, and what possibilities does this create for businesses? In this episode, host Bill Pfeifer sits down with the co-authors of the book AI at the Edge, Jenny Plunkett, Senior Developer Relations Engineer and Daniel Situnayake, Head of ML at Edge Impulse. They discuss how to determine which problems can actually be addressed through AI at the edge, how to think about effective AI, and unexpected use cases in generative AI and synthetic data generation. Plus, they cover how AI can support data distillation efforts and how to build teams that can successfully navigate this landscape. ---------Key Quotes:“We're going to be using generative AI to help us build a synthetic data set to train other AI models to deploy to edge devices.” - Jenny“One of the things that's really cool about synthetic data and using generative AI for that, is it potentially reduces the cost of training a model because instead of having to spend huge amounts of money labeling all this data, if you create the data yourself, you can have it implicitly be labeled.” - Dan --------Show Timestamps:(01:49) How did they get started in tech? (03:14) What brought them to AI?(08:12) What brought them together to write their book?(13:26) Determining which problems can be addressed with AI at the edge(15:51) What possibilities does AI at the edge create for businesses? (20:41) Synthetic data and generative AI (24:15) Using AI for data distillation (31:00) Building a skilled and interdisciplinary team (39:30) AI's transition from a career path to a tool (43:06) Effective AI (46:46) Edge / wildlife conservation case study (49:37) What are they excited about moving forward? --------Sponsor:Over the Edge is brought to you by Dell Technologies to unlock the potential of your infrastructure with edge solutions. From hardware and software to data and operations, across your entire multi-cloud environment, we're here to help you simplify your edge so you can generate more value. Learn more by visiting dell.com/edge for more information or click on the link in the show notes.--------Credits:Over the Edge is hosted by Bill Pfeifer, and was created by Matt Trifiro and Ian Faison. Executive producers are Matt Trifiro, Ian Faison, Jon Libbey and Kyle Rusca. The show producer is Erin Stenhouse. The audio engineer is Brian Thomas. Additional production support from Elisabeth Plutko and Eric Platenyk.--------Links:Follow Bill on LinkedInConnect with Jenny Plunkett on LinkedInConnect with Daniel Situnayake on LinkedIn and TwitterDaniel's substack

Wegovox- Wildcat podcast
WeGo Places-Justin Malandrucculo- Class of 2011-Developer Relations Engineer at Google

Wegovox- Wildcat podcast

Play Episode Listen Later Oct 16, 2023 40:51


Justin Malandrucculo Linkedin Education: The University of Illinois- Atmospheric Sciences  

GRTiQ Podcast
Kevin Jones - Developer Relations Engineer at Edge & Node

GRTiQ Podcast

Play Episode Listen Later Sep 1, 2023 57:58


Today I am speaking with Kevin Jones, Developer Relations Engineer at Edge & Node, a core development team actively contributing to The Graph. Although Kevin is a fresh addition to the Edge & Node team, his presence has already been felt significantly through his engagement in hackathons and leadership of key initiatives.In this engaging conversation, Kevin unveils his captivating career journey. He takes us from his early studies in graphic design through a stint in retail, working in sales at Best Buy – a chapter that included an adventure living in Hawaii. We then explore his trajectory to becoming a well-regarded thought leader within the Ethereum ecosystem, a journey that included some time at the industry-leading NGINX.Kevin also shares the pivotal moments when he encountered The Graph and made the transition to full-time work in web3. He provides insights into his role at Edge & Node and dives into some of the transformative initiatives he is driving. Throughout, Kevin offers valuable insights into open source projects, Scaffold-ETH, BuildersDAO – a new DAO within The Graph ecosystem – and the sources of his drive and determination. 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 

CryptoNews Podcast
#259: Ed Marquez, Developer Relations Engineer for Hedera, on Blockchain Scalability and AI Language Models Within Web3

CryptoNews Podcast

Play Episode Listen Later Aug 24, 2023 35:06


Ed Marquez is a Developer Relations Engineer for Hedera at Swirlds Labs. He is passionate about helping developers get on board with Web 3 and the Hedera network. In addition to distributed ledger technology (DLT), Ed has worked on Model-Based Design and development of control algorithms for embedded systems. Ed holds a MS and BS in Mechanical Engineering from Virginia Tech, and is currently pursuing a MS in Business Management at Harvard.In this conversation, we discuss:- Swirlds Labs' role within the Hedera ecosystem- Developer Relations- Hedera's recent integration of ChatGPT's plugin- Blockchain scalability- HBAR Foundation- Blockchain economy bolstered by AI- AI language models within Web3- The future of Blockchain x AI- FedNow instant paymentsHederaWebsite: hedera.comTwitter: @hederaDiscord: hedera.com/discordEd MarquezTwitter: @ed__marquezLinkedIn: Ed Marquez   ---------------------------------------------------------------------------------  This episode is brought to you by PrimeXBT.  PrimeXBT offers a robust trading system for both beginners and professional traders that demand highly reliable market data and performance. Traders of all experience levels can easily design and customize layouts and widgets to best fit their trading style. PrimeXBT is always offering innovative products and professional trading conditions to all customers.  PrimeXBT is running an exclusive promotion for listeners of the podcast. After making your first deposit, 50% of that first deposit will be credited to your account as a bonus that can be used as additional collateral to open positions.  Code: CRYPTONEWS50  This promotion is available for a month after activation. Click the link below:  PrimeXBT x CRYPTONEWS50 

Cloud Security Podcast by Google
EP133 The Shared Problem of Alerting: More SRE Lessons for Security

Cloud Security Podcast by Google

Play Episode Listen Later Aug 7, 2023 35:58


Guest:  Steve McGhee, Reliability Advocate at Google Cloud  Aron Eidelman, Developer Relations Engineer at Google Cloud Topics: What is the shared problem for SRE and security when it comes to alerting? Why is there reluctance to reduce noise? How do SREs, security practitioners, and other stakeholders define “incident” and “risk”? How does involving an “adversary” change the way people think about an incident, even if the impact is identical? Which SRE alerting lessons do NOT apply at all for security? Resources: Video (LinkedIn, YouTube) “Deploy Security Capabilities at Scale: SRE Explains How” (ep85) Steve talk about probability and SLO math at SLOconf   Why Focus on Symptoms, Not Causes? Learning from incidents (LFI) science How to measure anything in cyber security risk book Security chaos engineering book The SRS Book Ch 1 The SRE book Ch 4   

PodRocket - A web development podcast from LogRocket
ICYMI: Svelte and modern frontends with Scott Spence

PodRocket - A web development podcast from LogRocket

Play Episode Listen Later Aug 5, 2023 24:14


In this repeat episode picked by host Paul Mikulskis, Scott Spence, the Svelte Society London Meetup Organizer and a Developer Relations Engineer at Storyblok, joins us to talk about building with SvelteKit, advice for teams who want to get started with Svelte, and more! Links https://twitter.com/spences10 https://scottspence.com https://mas.to/@spences10 https://github.com/spences10 https://svelte.dev/blog/svelte-3-rethinking-reactivity https://twitter.com/dummdidumm_ https://www.youtube.com/scottspenceplease https://www.twitch.tv/spences10 https://www.youtube.com/watch?v=g-Xr6ygI0VE https://scottspence.com/posts/gradient-animations-in-tailwindcss https://scottspence.com/posts/instagram-image-filters https://www.youtube.com/watch?v=2ijSarsHfN0&t=940s 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: Scott Spence.

Women Who Code Radio
Talks Tech #45: Demystifying Web Accessibility

Women Who Code Radio

Play Episode Listen Later Jul 27, 2023 23:45


Josefine Schaefer, Developer Relations Engineer at Storyblok, shares her talk, “Demystifying Web Accessibility.” She discusses how a page visually presents to its viewer and also to a page reader. She talks about tools and tricks to check accessibility.

The State of Developer Education
Web3: A New Way to Store Information with Josh Crites, Developer Relations Engineer at Aztec

The State of Developer Education

Play Episode Listen Later Jul 6, 2023 47:47


How does Web3 facilitate new ways of storing information? Why are hackathons such unique environments? Do failed programming projects open up new opportunities? In this episode of the State of Developer Education podcast, we're joined by Josh Crites, Developer Relations Engineer at Aztec to exploxe and answer these questions.

Espacio Cripto
118: Todo sobre Fuel y la el futuro de escalabilidad sandusky.eth

Espacio Cripto

Play Episode Listen Later Jun 8, 2023 54:03


En este episodio hablamos sobre Fuel que es la primera capa de ejecución modular y no un rollup, sobre su funcionamiento, aplicación, beneficios y escalabilidad de Fuel. Estuvo con nosotros Sandusky quien es Developer Relations Engineer dentro de Fuel. Detalle de contenido: Introducción Presentación Sandusky ¿Qué es Fuel? Diferencias y similitudes de los rollups versus las capas de ejecución modular ¿Qué es una blockchain monolítica? ¿Cómo se están cubriendo los tradeoff? ¿Por qué es mejor una capa de ejecución modular? Para un desarrollador, ¿cuáles son los beneficios y retos para desplegar en Fuel? ¿Cuál es el futuro de Fuel? ¿Cómo utilizar Fuel? ¿Qué le dirías a Satoshi? Learn more about your ad choices. Visit megaphone.fm/adchoices

Espacio Cripto
118: Todo sobre Fuel y la el futuro de escalabilidad sandusky.eth

Espacio Cripto

Play Episode Listen Later Jun 8, 2023 56:03


En este episodio hablamos sobre Fuel que es la primera capa de ejecución modular y no un rollup, sobre su funcionamiento, aplicación, beneficios y escalabilidad de Fuel. Estuvo con nosotros Sandusky quien es Developer Relations Engineer dentro de Fuel. Detalle de contenido: Introducción Presentación Sandusky ¿Qué es Fuel? Diferencias y similitudes de los rollups versus las capas de ejecución modular ¿Qué es una blockchain monolítica? ¿Cómo se están cubriendo los tradeoff? ¿Por qué es mejor una capa de ejecución modular? Para un desarrollador, ¿cuáles son los beneficios y retos para desplegar en Fuel? ¿Cuál es el futuro de Fuel? ¿Cómo utilizar Fuel? ¿Qué le dirías a Satoshi? Learn more about your ad choices. Visit megaphone.fm/adchoices

Modern Web
S10E08 Modern Web Podcast- Understanding Svelte and Ramping Up from React ft. Scott Spence

Modern Web

Play Episode Listen Later Mar 1, 2023 77:01


On this episode of The Modern Web, we catch up with Scott Spence, Developer Relations Engineer at Storyblok, and SvelteSociety London meetup organizer. We dive into the ins and outs of Svelte, ramping up from React, what's it like to a second career developer, and the importance of paying it forward to developers who are new to the community.   Guest Scott Spence, Developer Relations Engineer at Storyblok   Host Jesse Tomchak, Software Architect at This Dot Labs   Sponsored by This Dot Labs

PodRocket - A web development podcast from LogRocket
Svelte and modern frontends with Scott Spence

PodRocket - A web development podcast from LogRocket

Play Episode Listen Later Jan 26, 2023 23:40


Scott Spence is the Svelte Society London Meetup organizer and a Developer Relations Engineer at Storyblok. Scott joins us to talk about building with SvelteKit, advice for teams who want to get started with Svelte, and more! Links https://twitter.com/spences10 https://scottspence.com https://mas.to/@spences10 https://github.com/spences10 https://svelte.dev/blog/svelte-3-rethinking-reactivity https://twitter.com/dummdidumm_ https://www.youtube.com/scottspenceplease https://www.twitch.tv/spences10 https://www.youtube.com/watch?v=g-Xr6ygI0VE https://scottspence.com/posts/gradient-animations-in-tailwindcss https://scottspence.com/posts/instagram-image-filters https://www.youtube.com/watch?v=2ijSarsHfN0&t=940s 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: Scott Spence.

Google Cloud Platform Podcast
2022 Year End Wrap Up

Google Cloud Platform Podcast

Play Episode Listen Later Dec 21, 2022 39:20


Happy Holidays from all of us at Google! This week, hosts Carter Morgan, Stephanie Wong, and Max Saltonstall are sharing their favorite moments from the year! From great partnerships with national companies, new releases in some of your favorite Google software tools, and a trillion digits of pi, we're breaking down some 2022 highlights and introducing special guest Podcast Producer Kevin McCormack to help with a fun podcast trivia game! Carter Morgan Carter Morgan is Developer Advocate for Google Cloud, where he creates and hosts content on Google's Youtube channel, co-hosts several Google Cloud podcasts, and designs courses like the Udacity course “Scalable Microservices with Kubernetes” he co-created with Kelsey Hightower. Carter Morgan is an international standup comedian, who's approach of creating unique moments with the audience in front of him has seen him perform all over the world, including in Paris, London, the Melbourne International Comedy Festival with Joe White. And in 2019, and the 2019 Edinburgh Fringe Festival. Previously, he was a programmer for the USAF and Microsoft. Stephanie Wong Stephanie Wong is a Developer Advocate focusing on online content across all Google Cloud products. She's a host of the GCP Podcast and the Where the Internet Lives podcast, along with many GCP Youtube video series. She is the winner of a 2021 Webby Award for her content about data centers. Previously she was a Customer Engineer at Google and at Oracle. Outside of her tech life she is a former pageant queen and hip hop dancer and has an unhealthy obsession with dogs. Max Saltonstall Max Saltonstall is a Developer Relations Engineer at Google Cloud. He is a father, teacher, storyteller, speaker, educator, nefarious villain, game designer, juggler, and is only part zombie. Cool things of the week Boost medical discoveries with AlphaFold on Vertex AI blog 6 common mistakes to avoid in RESTful web API Design blog Marketing Analytics With Google Cloud blog Our Favorite Episodes of 2022 Stephanie's Favorites GCP Podcast Episode 290: Resiliency at Shopify with Camilo Lopez and Tai Dickerson podcast GCP Podcast Episode 315: Cloud Functions (2nd gen) with Jaisen Mathai and Sara Ford podcast GCP Podcast Episode 307: FinOps with Joe Daly podcast Carter's Favorites GCP Podcast Episode 308: New Pi World Record with Emma Haruka Iwao and Sara Ford podcast GCP Podcast Episode 327: ML/AI Data Science for Data Analytics with Jed Dougherty and Dan Darnell podcast GCP Podcast Episode 289: Cloud Security Megatrends with Phil Venables podcast Max's Favorites GCP Podcast Episode 316: Google Cloud for Higher Education with Laurie White and Aaron Yeats podcast GCP Podcast Episode 317: Launching Products at Google Cloud with Anita Kibunguchy-Grant and Gabe Weiss podcast GCP Podcast Episode 325: Digital Sovereignty with Archana Ramamoorthy and Julien Blanchez podcast Stephanie's Honorable Mentions GCP Podcast Episode 323: Next 2022 with Forrest Brazeal and Stephanie Wong podcast GCP Podcast Episode 298: Celebrating Women's History Month with Vidya Nagarajan Raman podcast Carter's Honorable Mentions GCP Podcast Episode 312: Managed Service for Prometheus with Lee Yanco and Ashish Kumar podcast GCP Podcast Episode 290: Resiliency at Shopify with Camilo Lopez and Tai Dickerson podcast Max's Honorable Mentions GCP Podcast Episode 326: Assured Workloads with Key Access Justifications with Bryce Buffaloe and Seth Denney | Google Cloud Platform Podcast podcast Hosts Stephanie Wong, Carter Morgan and Max Saltonstall

WP Tavern
#47 – Adam Silverstein on the State of Images in WordPress

WP Tavern

Play Episode Listen Later Oct 19, 2022 39:45


On the podcast today we have Adam Silverstein. Adam is a WordPress core comitter where he works to fix bugs and improve modern web capabilities. As a Developer Relations Engineer in the content ecosystem team at Google, he works to invigorate the open web by empowering and educating developers. At the recent WordCamp US, he gave a presentation entitled ‘Images on the Web - past present and future'. In it, he outlined his thoughts on where the web is going in terms of support for different image formats. This then forms the basis of the podcast. How do browsers actually display images to your website visitors, and what formats are most appropriate where? We also talk about the new image formats, which are seeing more widespread adoption; WebP, AVIF and JPEG XL. We learn about the roll out of browser support, how they have smaller file sizes and when we can safely to use them.

Jukebox
#47 – Adam Silverstein on the State of Images in WordPress

Jukebox

Play Episode Listen Later Oct 19, 2022 39:45


On the podcast today we have Adam Silverstein. Adam is a WordPress core comitter where he works to fix bugs and improve modern web capabilities. As a Developer Relations Engineer in the content ecosystem team at Google, he works to invigorate the open web by empowering and educating developers. At the recent WordCamp US, he gave a presentation entitled ‘Images on the Web - past present and future'. In it, he outlined his thoughts on where the web is going in terms of support for different image formats. This then forms the basis of the podcast. How do browsers actually display images to your website visitors, and what formats are most appropriate where? We also talk about the new image formats, which are seeing more widespread adoption; WebP, AVIF and JPEG XL. We learn about the roll out of browser support, how they have smaller file sizes and when we can safely to use them.

Headless WP Podcast
Alexa Spalato and Gatsby WP Themes

Headless WP Podcast

Play Episode Listen Later Sep 8, 2022 52:30


In this episode, Fran and Jeff talk with Alexa Spalato, the co-founder of Gatsby WP Themes, a company focused on building out Gatsby themes made to work with headless WordPress. We learn how Alexa got involved in tech, discuss some of the details of the headless theme market, and get some updates about her future as a Developer Relations Engineer in the headless CMS space.Alexa drops a ton of knowledge about how themes (of all kinds) can lower the barriers for other people, and why she decided to bet on Gatsby as a base for her own theme ventures. We hope you enjoy the episode!    Alexa's WebsiteGatsby WP Themes

Game Dev With a Shot of Jameson
Ted Dinola Returns! - Developer Relations Engineer at Meta

Game Dev With a Shot of Jameson

Play Episode Listen Later Aug 9, 2022 103:22


Today I'm joined by Ted DiNola - Developer Relations Engineer at Meta! He's returning to continue our discussion about Game Dev, Production, and ADHD. We discuss how Meta's work environment lets him feel like he can truly be himself, some thoughts about the Metaverse, and how ADHD impacts finishing games but is a Conference super power! Credits include: Blade & Sorcery: Nomad Zenith YouTube VR Walking Dead: Saints & Sinners Vox Machinae Virtual Virtual Reality 2 Population: One Vacation Simulator Pistol Whip Garden of the Sea Pixel Ripped: 1995 Eleven Table Tennis Electronauts Be sure to join us LIVE every Wednesday night from 7-9pm EST using the link below! JOIN US LIVE▹ https://www.twitch.tv/jamesondurall JOIN THE DEV TEAM DISCORD▹ https://discord.gg/Xp6WsYVszS JAMESON'S PODCAST▹https://anchor.fm/jamesondurall/ JAMESON'S YOUTUBE▹ https://www.youtube.com/jamesondurall JAMESON'S TWITTER▹ https://twitter.com/jamesondurall JAMESON'S INSTAGRAM▹ https://www.instagram.com/jamesondurall/ #GameDev #youtubevr #youtube #meta #Zenith #WalkingDead --- Support this podcast: https://anchor.fm/jamesondurall/support

API Intersection
DevRel Deep Dive: Measuring impact & where your devs should be feat. Rizel Scarlett, Developer Advocate at GitHub

API Intersection

Play Episode Listen Later Aug 4, 2022 22:35


Developer relations (DevRel) is an increasingly rising industry, growing as a reflection of software's ubiquity in the business world — and the growing power of the developer to influence what products and platforms their employers use.But, what makes a good Developer Advocate and strong DevRel program? This week on the API Intersection podcast, we chatted with Rizel Scarlett, Developer Relations Engineer at Github, to get her opinion on how to measure a DevRel program's success and different platforms Developer Advocates can utilize to reach the developer community.Do you have a question you'd like answered, or a topic you want to see in a future episode? Let us know here: stoplight.io/question/

WP Tavern
#34 – Felix Arntz on WordPress and Performance

WP Tavern

Play Episode Listen Later Jul 13, 2022 27:34


On the podcast today we have Felix Arntz. Felix is a Developer Relations Engineer at Google and a WordPress core committer. He is the lead engineer for the Site Kit plugin for WordPress and has been a regular contributor to WordPress for several years. He's also been involved in the newly created WordPress performance team which is trying to work out how WordPress can stay ahead of the performance curve. He's on the podcast today to talk about how the WordPress community need to be focussing more on performance. Not only do search engines place more emphasis upon speed, but the rise of other CMSs might also reflect their ability to optimise their platforms, given that they don't have the plugin and theme architecture which WordPress does. It's an interesting conversation about an area which is going to matter more and more in the months and years to come.

POW! Samsung Developer Program
Foldables: Google, Microsoft & Samsung

POW! Samsung Developer Program

Play Episode Listen Later Jul 13, 2022 51:24


8/11/22Season 3, Episode 7: FoldablesGuy Merin, MicrosoftAde Oshineye, GoogleSoren Lambaek, Samsung On today's show we have 3 guests on the podcast from leading companies in the foldable space.·  Guy Merin, Senior Director of Engineering, Surface Duo Developer Experience, Microsoft· Ade Oshineye, Senior Staff Developer Advocate, Google· Soren Lambaek, Developer Relations Engineer, SamsungNot only do we chat about foldable trends and developer resources, but how companies are working together to help developers create for this new and innovative technologySamsung Developer ProgramVisit the Samsung Developer website at developer.samsung.com to learn more about developer opportunities and building a relationship with Samsung. Be sure to sign up for the Samsung Developer Newsletter to learn about the latest from the Samsung Developer Program. More Interviews! Like and subscribe to the Samsung Developers Podcast where ever you listen to your favorite shows. samsungdev.buzzsprout.com GuestsGuy Merin, MicrosoftAde Oshineye, GoogleSoren Lambaek, SamsungHelpful Links:· Large Screen/Foldable Guidance· Large Screen App Quality· Jetpack WindowManager · Jetpack SlidingPaneLayout· Jetpack WindowManager Foldable/Dual-screens· Surface Duo Layout Libraries· Surface Duo Android Emulator · Figma - Surface Duo Design Kit· Surface Duo Blog · Surface Duo Youtube· Surface Duo Twitch · Surface Duo Twitter· Adopting Native Language· Discover Quality Apps on Large Screens· Foldables: Design/Development Perspectives· Learn About Foldables· Case Studies· 5 steps to Large Screen Designing· Understanding Layout· Code Lab· Testing· Window Size Classes· Jetnews: Different Screen Sizes· Migrate to Responsive Layouts· Compose/Activity Embedding· Unfolding Gaming Potential· Samsung Remote Test LabSamsung Developers· Website· Blog· News· Forum· Facebook· Instagram· Twitter· YouTube· LinkedInHostTony Morelan, Senior Developer Evangelist, Samsung

Jukebox
#34 – Felix Arntz on WordPress and Performance

Jukebox

Play Episode Listen Later Jul 13, 2022 27:34


On the podcast today we have Felix Arntz. Felix is a Developer Relations Engineer at Google and a WordPress core committer. He is the lead engineer for the Site Kit plugin for WordPress and has been a regular contributor to WordPress for several years. He's also been involved in the newly created WordPress performance team which is trying to work out how WordPress can stay ahead of the performance curve. Despite the fact that WordPress' share of the CMS market is very strong, third-party CMS's like Wix and Shopify have been growing their customer base in recent years. As single platforms, they can be very focused upon performance and don't have to worry about the possible performance issues which the plugin and theme architecture of WordPress brings. Is this something that we need to be concerned about? Are website clients beginning to ask more probing questions about performance, and is WordPress keeping up with the marketing and messaging? He also talks today about why it's important for the whole WordPress community to be thinking about performance when building any website. It's no secret that Google and other search engines are very interested in making the web faster, and future rankings could well be boosted by having a performant site. So we talk through some of the ways that this can be achieved. We also talk about Felix's career, the fact that there's an emerging industry of people who are able to work exclusively on website performance, and earn their living from this expertise. This could be in the writing of code, the optimisation of assets as well as the configuration of hosting options. Felix recommends some things which might be of use for people wishing to find out more. It's an interesting conversation about an area which is going to matter more and more in the months and years to come. Useful links. Site Kit Plugin WordPress Performance Team kick off The Performance Lab plugin has been released Enhancing performance in an open-source CMS ecosystem

BragTalks
Episode 11: Getting Your First Job in Tech: Jennifer Reif

BragTalks

Play Episode Listen Later Jun 30, 2022 27:37


In this episode of BragTalks, Jennifer Reif shares how she got her first job in tech and successfully presented at several technology conferences. This episode is hosted by Heather VanCura, who met Jennifer through speaking and attending several of the same conferences as Jennifer. Season 2 is all about transitions and pivots, and this podcast is full of them! This isn't just a one way conversation either. Share your story and experience with us by subscribing and filling out the contact form on BragTalks.com. Follow us on Twitter and LinkedIn as well. You can listen on Apple, Google or Spotify podcast platforms. Bio: Jennifer Reif is a Developer Relations Engineer at Neo4j, speaker, and blogger with an MS in CMIS. An avid developer and problem-solver, she has worked with many businesses and projects to organize and make sense of widespread data assets and leverage them for maximum business value. She has expertise in a variety of commercial and open source tools, and she enjoys learning new technologies, sometimes on a daily basis! Her passion is finding ways to organize chaos and deliver software more effectively. Jennifer writes frequently on her website jmhreif.com, tweets occasionally at @JMHReif, and always publishes code to her Github.

CTO Mastermind: Il Podcast per i CTO
Coltivare la motivazione del team | 💻🍔 CTO Lunch #063

CTO Mastermind: Il Podcast per i CTO

Play Episode Listen Later Jun 23, 2022 55:04


Cosa muove gli sviluppatori? Quali sono le strategie più efficaci per supportare la motivazione dei dev? E poi ancora, quanto è importante allineare i valori aziendali a quelli personali dei membri del team per mantenere alta la motivazione? Ne ho parlato con i membri della Community del CTO Mastermind durante questo CTO Lunch. Ospite anche Roberto Butti, Developer Relations Engineer di Storyblok. Buon ascolto! 🖖 HOST: Alex Pagnoni: imprenditore di servizio e di prodotto, https://www.axelerant.it/ (Fractional CTO), esperto di cloud, sviluppo software e marketing technologies. Sono speaker, content creator, conduttore del CTO Show e del CTO Podcast, fondatore della https://www.ctomastermind.it/community/ (community CTO Mastermind) (+510 CTO italiani). 🗣 GUEST: Spinto dalla passione per lo sviluppo del codice, Roberto Butti ha operato prima come consulente IT per poi passare a ruoli di CTO e Technical Director per Agenzie Digital. Oggi Roberto è Developer Relations Engineer di Storyblok e, nel tempo libero, si dedica al training di nuovi sviluppatori in ambito opensource. 🤝 PARTNER: Quanto è difficile scalare il team di sviluppo? Se sei un CTO o un Leader Tecnologico sai benissimo quali sono le complessita di attirare e trattenere talenti. Per questo Alex Pagnoni ha creato il metodo Team Scaling di sviluppo collaborativo, in cui condivide le skill di una parte del proprio team tech, per aiutarti a scalare anche nei momenti più difficili. Per saperne di più, vai su http://www.teamscaling.it/ (www.teamscaling.it). Ringraziamo della partecipazione: Roberto Butti (Developer Relations Engineer di Storyblok), Roberto Luberti (AWS Cloud Architect di Overdata Sagl). ⭐️⭐️⭐️⭐️⭐️ Il Podcast ti è piaciuto? Aiutaci a farlo a conoscere a altri CTO e leader tecnologici. Aggiungilo ai tuoi preferiti e lascia una recensione su Apple Podcast o su Podchaser!

DonTheDeveloper Podcast
How To Become A Developer Relations Engineer In 2022

DonTheDeveloper Podcast

Play Episode Listen Later Jun 20, 2022 35:08 Transcription Available


I invited on a developer relations engineer to share his story about how he got into the field and landed his position. We dove into both the ups and downs of the position, as well as laid out a path on how you can become on. Even if you're an empathetic aspiring developer that simply wants to break into tech and isn't necessarily dead set on a software engineering position, then this episode is for you.Tarric Sookdeo (guest):Linkedin - https://www.linkedin.com/in/tarric-sookdeo-a86b841a1Blog - https://tarricsookdeo.medium.com ---------------------------------------------------

CTO Mastermind: Il Podcast per i CTO
Team motivation: i valori portanti | CTO Show 064 con Roberto Butti (Storyblok)

CTO Mastermind: Il Podcast per i CTO

Play Episode Listen Later Jun 15, 2022 60:45


Lavorare è una sfida quotidiana. Quali sono i fattori che motivano le persone ad affrontarla ogni giorno nel migliore dei modi? Ne ho parlato in questo CTO Show con Roberto Butti, Developer Relations Engineer di Storyblok. Buon ascolto!  🗣 GUEST: Spinto dalla passione per lo sviluppo del codice, Roberto Butti ha operato prima come consulente IT per poi passare a ruoli di CTO e Technical Director per Agenzie Digital. Oggi Roberto è Developer Relations Engineer di Storyblok e, nel tempo libero, si dedica al training di nuovi sviluppatori in ambito opensource. 🖖 HOST: Alex Pagnoni: CTO Mentor, Fractional CTO, imprenditore di servizio e di prodotto (Innoteam), esperto di cloud, sviluppo software e marketing technologies. Sono speaker, content creator, conduttore del CTO Show e del CTO Podcast, fondatore della community CTO Mastermind (+510 CTO, Leader Tech e aspiranti tali). 🤝 PARTNER: Quanto è difficile scalare il team di sviluppo? Se sei un CTO o un Leader Tecnologico sai benissimo quali sono le complessita di attirare e trattenere talenti. Per questo Alex Pagnoni ha creato il metodo Team Scaling di sviluppo collaborativo, in cui condivide le skill di una parte del proprio team tech, per aiutarti a scalare anche nei momenti più difficili. Per saperne di più, vai su http://www.teamscaling.it/ (www.teamscaling.it). ⭐️⭐️⭐️⭐️⭐️ Il Podcast ti è piaciuto? Aiutaci a farlo a conoscere a altri CTO e leader tecnologici. Aggiungilo ai tuoi preferiti e lascia una recensione su Apple Podcast o su Podchaser!

Game Dev With a Shot of Jameson
Ted DiNola - Developer Relations Engineer @ Meta

Game Dev With a Shot of Jameson

Play Episode Listen Later Jun 8, 2022 112:44


Today I'm joined by Ted DiNola – Developer Relations Engineer at Meta We discuss when he got a Handshake job offer over drinks, Advice for getting your first job in the industry, and A LOT about ADHD and Game Development. His credits include: Blade & Sorcery: Nomad Zenith YouTube VR Walking Dead: Saints & Sinners Vox Machinae Virtual Virtual Reality 2 Population: One Vacation Simulator Pistol Whip Garden of the Sea Pixel Ripped: 1995 Eleven Table Tennis Electronauts Be sure to join us LIVE every Wednesday night from 7-9pm EST using the link below! JOIN US LIVE▹ https://www.twitch.tv/jamesondurall JOIN THE DEV TEAM DISCORD▹ https://discord.gg/43ZJySsTzY JAMESON'S PODCAST▹https://anchor.fm/jamesondurall/ JAMESON'S YOUTUBE▹ https://www.youtube.com/jamesondurall JAMESON'S TWITTER▹ https://twitter.com/jamesondurall JAMESON'S INSTAGRAM▹ https://www.instagram.com/jamesondurall/ #GameDev #Meta #YouTube #WalkingDead #Oculus --- Support this podcast: https://anchor.fm/jamesondurall/support

Darede Cast
É hora de Paz na nuvem com PAAS

Darede Cast

Play Episode Listen Later May 11, 2022 46:18


A Cloud Computing mudou o paradigma no desenvolvimento de software. Entretanto, existem variados pontos críticos a serem considerados, como backups, atualização de bancos de dados e frameworks, CI / CD, entre outros elementos que tornam uma estrutura complexa e consequentemente podendo oferecer algum risco para a arquitetura. Mas existem serviços capazes de diminuir o risco de operações em cloud, como o modelo PaaS (Plataform as a Service) e a Live Darede de hoje, recebe Otávio Santana, Developer Relations Engineer na Platform.sh para abordar os benefícios desse modelo. Confira!

AppForce1: news and info for iOS app developers
Rudrank Riyam, developer relations engineer at Codemagic

AppForce1: news and info for iOS app developers

Play Episode Listen Later Mar 30, 2022 35:24 Transcription Available


Meet Rudrank. He's a developer relations engineer. He is an Apple WWDC Scholarship Winner in 2019 and had an internship with Apple in 2020. You could say he has done a lot of things in a short time.Learn more about Rudrank on his website: https://rudrank.blog/You can also follow him on Twitter: @rudrankriyamPlease rate me on Apple Podcasts.Send me feedback on SpeakPipeOr contact me through twitterNewsletter, sign up!My book: Being a Lead Software DeveloperRunwayPut your mobile releases on autopilot and keep the whole team in sync throughout. Lead Software Developer Learn best practices for being a great lead software developer.Support the show (https://pod.fan/appforce1)

AWS Developers Podcast
Episode 033 - What Every Developer Should Know about Web3 with Nader Dabit - Part 2

AWS Developers Podcast

Play Episode Listen Later Mar 25, 2022 29:09


In this episode, Dave chats with Nader Dabit, Developer Relations Engineer at Edge & Node. In his career, Nader has worn the hats of a web developer, mobile developer, AWS cloud developer, and now Web3 developer. Nader is the author behind many of the popular, free, developer guides for the Web3 space including: The Complete Guide to Full Stack Web3 Development, The Complete Guide to Full Stack Ethereum Development, and The Complete Guide to Full Stack Solana Development. In part two of this two-part conversation, Nader explains the developer lessons he has learned moving from Web2 vs Web3, some of the misconceptions about Web3, and what Web3 can bring to people around the world. Note: This episode is an attempt to cover the developer benefits of Web3. It does not represent financial advice, or any specific Amazon endorsement of Bitcoin and Crypto Currencies. Nader on Twitter: https://twitter.com/dabit3 Dave on Twitter: https://twitter.com/thedavedev Nader's LinkedIn: https://www.linkedin.com/in/naderdabit/ Nader's YouTube Channel: https://www.youtube.com/naderdabit Nader on Dev.to: https://dev.to/dabit3 Nader's Git: https://github.com/dabit3 Developer DAO on Twitter: https://twitter.com/developer_dao The Complete Guide to Full Stack Web3 Development: https://dev.to/dabit3/the-complete-guide-to-full-stack-web3-development-4g74 The Complete Guide to Full Stack Solana Development with React, Anchor, Rust, and Phantom: https://dev.to/edge-and-node/the-complete-guide-to-full-stack-solana-development-with-react-anchor-rust-and-phantom-3291 The Complete Guide to Full Stack Ethereum Development: https://dev.to/dabit3/the-complete-guide-to-full-stack-ethereum-development-3j13 Building GraphQL APIs on Ethereum: https://dev.to/edge-and-node/building-graphql-apis-on-ethereum-4poa Subscribe: Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

AWS Developers Podcast
Episode 032 - What Every Developer Should Know about Web3 with Nader Dabit

AWS Developers Podcast

Play Episode Listen Later Mar 18, 2022 23:32


In this episode, Dave chats with Nader Dabit, Developer Relations Engineer at Edge & Node. In his career, Nader has worn the hats of a web developer, mobile developer, AWS cloud developer, and now Web3 developer. Nader is the author behind many of the popular, free, developer guides for the Web3 space including: The Complete Guide to Full Stack Web3 Development, The Complete Guide to Full Stack Ethereum Development, and The Complete Guide to Full Stack Solana Development. In part one of this two-part conversation, Nader shares getting started with a full-time career as a developer coming from almost no technical background. He then covers the vision of what Web3 is, and regardless of your exposure to blockchain, how Web3 will ultimately benefit everyone. Note: This episode is an attempt to cover the developer benefits of Web3. It does not represent financial advice, or any specific Amazon endorsement of Bitcoin and Crypto Currencies. Nader on Twitter: https://twitter.com/dabit3 Dave on Twitter: https://twitter.com/thedavedev Nader's LinkedIn: https://www.linkedin.com/in/naderdabit/ Nader's YouTube Channel: https://www.youtube.com/naderdabit Nader on Dev.to: https://dev.to/dabit3 Nader's Git: https://github.com/dabit3 Developer DAO on Twitter: https://twitter.com/developer_dao The Complete Guide to Full Stack Web3 Development: https://dev.to/dabit3/the-complete-guide-to-full-stack-web3-development-4g74 The Complete Guide to Full Stack Solana Development: https://dev.to/edge-and-node/the-complete-guide-to-full-stack-solana-development-with-react-anchor-rust-and-phantom-3291 The Complete Guide to Full Stack Ethereum Development: https://dev.to/dabit3/the-complete-guide-to-full-stack-ethereum-development-3j13 Building GraphQL APIs on Ethereum: https://dev.to/edge-and-node/building-graphql-apis-on-ethereum-4poa Graph Day Keynote by Yaniv Tal: https://www.youtube.com/watch?v=fZcbWkrTMtg ------------------ Subscribe: Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

Sustain
Episode 111: Amanda Casari on ACROSS and Measuring Contributions in OSS

Sustain

Play Episode Listen Later Mar 4, 2022 43:02


Guest Amanda Casari Panelists Richard Littauer | Ben Nickolls | Eric Berry Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. We are very excited for today's podcast. Our guest is Amanda Casari, who is a Developer Relations Engineer and Open Source Researcher at Google Open Source Programs Office (OSPO). Today, we learn about some open source work Amanda is doing with her research team at the University of Vermont Complex Systems Center, she tells us about a project called ACROSS, and a paper that was written by her team that was actively looking at contributions that are measured for code centric repositories. Amanda goes in depth about what open source is to her, she shares advice if you're looking to collaborate more effectively with people in open source, she talks more about how we can support projects financially to other parts of the world and mentions some great groups she worked with. Go ahead and download this episode to learn more! [00:02:00] Amanda fills us in on the open source work that she started working on with the University of Vermont Complex Systems Center. [00:06:43] Amanda explains the “assumptions we have that aren't verified,” as well as a paper that came from their research team and what they examined. [00:09:52] We learn more about how people interface with closed decisions behind doors and open source. [00:13:30] Ben asks Amanda to tell us what kind of behaviors and differences she sees between communities that emerge and continue to exists off of platforms like GitHub and GitLab. [00:15:50] Amanda tells us about a project their team is working on called ACROSS, and a paper that won a FOSS award last year that was about actively looking at contributions that are measured for code centric repositories. [0019:18] Eric wonders what type of responsibility Amanda sees that would come from GitHub and if that's going to affect us long term. [00:23:01] Amanda explains working as a Control Systems Engineer, and she explains how she sees open source as blocked diagrams and feedback loops. [00:27:53] We hear some great advice from Amanda if you are someone who wants to make the world of open source a more complex and beautiful place with what you have to offer. [00:32:08] We hear some thoughts from Amanda for people working in open source who don't have a huge amount of privilege to have the ability to share their energy and find it harder to think laterally. [00:35:27] Ben wonders what we can do to support projects financially and what we can do to support the next generation from the different parts of the world who haven't had the opportunity to benefit yet. Amanda shares her thoughts and mentions some really great groups she worked with such as Open Source Community Africa, PyCon Africa, and Python Ghana. [00:39:24] Find out where you can follow Amanda online. Quotes [00:09:01] “A lot of open source decision making is really behind proprietary or closed doors.” [00:19:59] “When it feels like there is only one option for any kind of tool, infrastructure, or access, that's when I always start getting concerned.” [00:24:58] “Open source is a ___ system.” [00:29:59] “Open source is not one thing, it's many interactive parts that fit together in different ways.” Spotlight [00:40:10] Eric's spotlight is an article Amanda submitted on “Open source ecosystems need equitable credit across contributions.” [00:40:39] Ben's spotlight is a shout out to Jess Sachs and the maintainers of Faker.js. [00:41:22] Richard's spotlight is Red Hen Baking in Vermont. [00:41:47] Amanda's spotlights are two books: Data Feminism _and _The Data-Sitters Club that she found on The Executable Books Project. Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) Amanda Casari Twitter (https://twitter.com/amcasari?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Amanda Casari LinkedIn (https://www.linkedin.com/in/amcasari/) Open Source Stories (https://www.opensourcestories.org/) The penumbra of open source: projects outside of centralized platforms are longer maintained, more academic and more collaborative (https://arxiv.org/abs/2106.15611) Getting the Giella source code for your language (https://giellalt.uit.no/infra/GettingStarted.html) Julia Ferraioli Blog (https://www.juliaferraioli.com/blog/) What contributions count? Analysis of attribution in open source (article) (https://scholar.google.com/citations?view_op=view_citation&hl=en&user=VRBk-q8AAAAJ&citation_for_view=VRBk-q8AAAAJ:qjMakFHDy7sC) ACROSS Taxonomy-GitHub (https://github.com/google/across) RubyConf 2021- Black Swan Events in Open Source-That time we broke the Internet (https://docs.google.com/presentation/d/1g9UDReu80wo14H8beoAJ6n69ZorBYhLjKxOU1ngegeY/edit#slid) All Contributors bot-GitHub App (https://github.com/all-contributors/app) All Contributors (https://allcontributors.org/) Open Source Community Africa (https://oscafrica.org/) PyCon Africa (https://pycon-africa-stage.us.aldryn.io/) Python Ghana (https://www.pythonghana.org/) Open source ecosystems need equitable credit across contributions (article) (https://bagrow.com/pdf/casari2021.pdf) Faker (https://github.com/faker-js/faker) Red Hen Baking Co. (https://www.redhenbaking.com/) Data Feminism (https://data-feminism.mitpress.mit.edu/) The Executable Books Project (https://executablebooks.org/en/latest/) The Data-Sitters Club (https://datasittersclub.github.io/site/index.html) Credits Produced by Richard Littauer (https://www.burntfen.com/) Associate Producer Justin Dorfman (https://www.justindorfman.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Transcript by Layten Pryce (https://www.fiverr.com/misstranscript) Transcript Richard [00:11]: Hello, and welcome to Sustain, the podcast where we're talking about sustaining open-source for the long haul. Who are we? Where do we come from? Where are we going? What are we going to talk about today? Very excited for today's podcast. We have an amazing guest. One of the few guests from the state I am in, which is really fun for me. I just feel like saying that first before anything else, because I don't know why, but before we introduce her, I want to make sure we also talk about the other people you're going to be hearing on today's podcast. So I am Richard [name]. Hello everyone. And then we also have Benjamin Nichols, sometimes known as Ben, how are you? Ben [00:48]: I'm good. I'm a bit enjoying the sun. Thank you. Richard [00:51]: Cool. Okay, great, Eric, how are you doing? Eric [00:54]: No sun, but I'm really happy to be here. I'm very well caffeinated. Richard [00:58]: That is very good. I'm going with apple ciders today. I don't know why, I think it's because I already have caffeine. Great. So that's the little tiny stuff at the beginning to set the mood for the show. And now the actual content. Our guest today is the amazing Amanda Casari. Amanda Casari is a lot of things. She doesn't like titles very much, which is cool. So I'm just going to say what she wrote down in the prep doc, DevRel engineer, plus open source researcher at Google open-source programs office, which we're going to shorten to the Google OSPO for the rest of this conversation, because that's just too much of a word. She also lives in Vermont and has a long and storied career. Amanda, how are you doing? Amanda [01:39]: Hi, I'm doing great. It's so good to be here today. And I'm also absolutely thrilled Richard, that you also live in Vermont. Richard [01:47]: I know we have this small thing in Vermont where we really like talking about being in Vermont. I think it's because we're in a little man's complex because it's a very small state and so it's just nice to be like, oh, someone else, Amanda, actually that might be a good intro. So you've been active in open source communities for over a decade. You've organized local community groups. You've filed issues. You've cleaned the documentation, you've tested fixes or fixed tests. You've done all the things. You move chairs around, but like you're really a systems level person. [02:14] You're all about thinking about what open-source is and how can we make sure that the entirety of open-source regenerates builds better, is more sustainable, is more resilient, is more better for the people inside of it. Part of that work has been working directly with UVM, which is confusingly, the University of Vermont and it's based in Burlington. And it now has, I believe some sort of OSPO. Can you talk about what that is and how that happened? Amanda [02:40]: Yeah, so as brief as I can make it, because otherwise I will spend the next 45 minutes talking about this. I switched into the Google OSPO office because I started and worked on a partnership and a research group with the University of Vermont complex system center. So we started to look within Google and understand how can we really begin to picture, strategize, think about, learn from open-source, like you said, from a systems and ecosystems and networks perspective, which is in line with my background. [03:16] So in the way, way before, I'm a actually a control systems engineer. So problems that are dull, dangerous or dirty fit right with that robotics line of thinking and examining infrastructures and legacy infrastructures and how things interconnect and where they need support and where they don't, is absolutely aligned with what I used to work on. And then I did go to the University of Vermont and I was a fellow at the complex system center. When I was studying power systems and I actually looked at electrical engineering and applied mathematics. [03:48] And so a lot of that is fundamental for the reason why, like my brain is really shaped to examine and look at things, as to what scales and what doesn't, but not from some of the software perspective of how do you scale things, but where do you actually, and can you find rules that may or may not apply at different scales and may not work? So we may try to apply things that work at a smaller group, at a larger scale and they break down and that's when they actually don't scale. So working with the University of Vermont, we started in early 2020, which was a really interesting time to get a new research line started, especially when one of your core researchers is an infectious disease modeler. But I would say the benefit from starting at that time is that we really got lucky in a few places. [04:37] So one of the places that we got lucky in early 2020, is we took everything that we were thinking about for the next two years of life. And we said, this is probably going to change. And we fundamentally moved some of the money and the grant money around to start instead examining who needs support now, what can we do now? So if we're not going to be able to travel, we're not going to be able to hold community workshops. We're not going to be able to invite open-source people together to talk to us, what should we be doing instead? [05:08] One of the things that we did is we hired another researcher. So we took some of the travel money and some of the budget for commuting. We moved that into a position at the time and that, one, was wonderful because that person is brilliant. But second, it really worked out well because I don't remember if everyone remember early 2020 academic institutions were shutting budget and roles and department shut down. And it was really a crisis mode, but we were sheltered from a lot of that because of the structure we set up. [05:33] But there's been a lot of great research coming out of that group and that team. One of the fundamental things we've been just trying to figure out is where's the information you would need to understand and what's happening at open-source at a large scale level? And we found there are a lot of assumptions that are made that we can't verify. So we find that we are looking for information always in a way that respects individuals and respects people in open-source as humans. And doesn't observe them in a way that is without their consent, but it's very hard to find the information you need that doesn't just result from conveniently available information on the internet. [06:12] But for the OSPO perspective at the University of Vermont, UVM is a recent recipient of a Sloan tech grant that is going to be establishing an open-source programs office and also has a research component to understand and look at open-source communities as they emerge, especially as they emerge in local communities who have a directive to really support local effects rather than maybe like a global effect or a corporate good Richard [06:36]: So much in there. Most interesting was there were assumptions that we have that aren't verified. What assumptions are you talking about regarding open-source and what have you looked at? Amanda [06:47]: So I rant a lot amongst researchers and groups of people, Richard, as you know, and I don't have time to verify all of my ranting or all of my hypothesis. But one of the research lines that I am most excited about learning and exploring more. There's a paper that came out from our team and I will add it to the show notes late,r is called the penumbra of open-source. And so the research team and I was not on this paper, but the research team examined whether or not the sample that we used from GitHub is actually representative of the larger open-source ecosystem. [07:24] And so they went about looking for individual hosted, but public and open Git servers to be able to start to look at whether or not, if you choose not to be on a platform like GitHub or GitLab or any other hosted platform repository, does your open-source project organization, metadata, community, organization, decision making, does that look like what's hosted on GitHub? And they found that it wasn't. So GitHub itself, they called the convenient sample. It's something that's used because it's easy for researchers to get to, which I would also challenge the convenience and ease of getting specifically that data access, because most of that data is accessed by researchers, by aggregated collections like the GitHub archive, or there's a few other aggregation projects, but they're all open-source or research projects. [08:15] They are funded by groups like Google or groups like Microsoft. But if you actually wanted to do aggregated research of what is happening in open-source and trends in time. That's something that is a huge data engineering project. And the best that we can do right now is samples off of those aggregated platforms. But it's not clear in a way that it used to be. So if you look at a lot of the studies that are coming out, they may look at something like the Linux kernel, or they may look at something like projects from the Apache software foundation, because all of the tools that those developers use are in a much more aggregated and less distributed format and also less proprietary systems. [08:57] So that data is actually accessible and is more transparent. Otherwise, a lot of open-source decision making is really behind proprietary or closed doors. And that might be the decision of the community. They may not also realize that like the effects of those decisions. Richard [09:12]: I don't know of a lot of projects that are outside of GitHub. I used to know of one, I just checked and Gela Techno Finn minority language documentation has now moved to GitHub, which seems to happen a lot, I assume. And so it's always shocking to me to hear that people have projects elsewhere and they think about it elsewhere. One of the things I want to focus on though, besides that, which always blows my mind, is you talked about open source decision making happening behind doors. And it seems to me to be at ends with what we think of as open-source naively when we begin learning about open=source, we think, oh, open-source, everything's out in the open. [09:50] It's great. freedom of speech, freedom of everywhere. I want to know more about how people interface with closed decisions behind doors and open-source, and whether everyone knows that, and we're just not talking about it openly, or whether that's something that actually causes fractures in communities when they realize that the power is elsewhere. I'm just curious about your opinion on this. Amanda [10:13]: So to be perfectly frank and clear, decisions about open-source have always been behind closed doors. So there is an illusion of access, but not everybody has always been invited to those meetings. So talking with folks who have been involved in open-source even much longer than I have, we've talked about these different kinds of cyclic patterns and community and transparency and in governance, different kinds of governance models. So it used to be that folks would show up a few days before a conference, ahead of time or stay afterwards for a few conferences. [10:49] And if you were invited to those meetings, you were part of that decision making group. But I would like to point out that the first person that became a core dev programmer contributor for the Cython kernel is actually Mariatta Wijaya. And she just joined that a few years ago. So she was the first person who identified as a female who was even invited for this programming language that's been around for 20 years. And I will say, I feel like that community's done a wonderful job in understanding their limitations and where they have and have not been transparent and open. [11:21] And Guido van Rossum has the creator of the language has also been one of the staunch supporters, allies, and movers of change for that. But it took a long time for that to happen. So the idea that there are these close off areas where decision are making is nothing new. However, there was always this idea that at least conversations and decisions and communication happen as something as open as a mailing list, and everybody had access to something like the mailing list. Maybe it was cell hosted or maybe it was hosted on a centralized platform, but at least you could see it. That's not the same case anymore. [11:54] We have a ton of developer platforms now that people choose to have conversations on. Sometimes those communications get centralized with things like repositories. And that is for trying to make communication and understanding more atomic, which is totally understandable. And every community gets to make these decisions for themselves. And if you are trying to piece together all of this information, it's a huge data archeology problem. This is something that Julia Farole and I talk about a lot, is if you just want to understand what's happening in a community, who is making decisions, who has access, who is even doing any of the work, like if we just want to understand what work is even visible or valued in a community that's very challenging to see right now. And that's another one of our core research areas that we're working on, is just making labor visible across open-source. Ben [12:47]: So I just wanted to kind of pick up and extend Richards question to a degree. And just, if you can talk a little bit about the difference that you see in communities that are based on more kind of some might say modern traditional platforms, like GitLab, maybe [13:06 inaudible] to a certain degree, but versus those projects that exist kind of, I would say off-platform and behind kind of mailing list and so on, because I think a lot of people would say that some communication methods like mailing list, mailman and so on could be argued to be less accessible than say, like GitHubs, that's now got a lot more kind of discussion based features and so on. So I was just wondering like what kinds of behaviors you see and what kind of difference do you see between communities that emerge and continue to kind of exist off of platforms, like GitHub and GitLab? Amanda [13:43]: So I will say, I feel like the differences between centralized platform centric communities and non platform centric communities. I feel like that actually is still an open research question because of the fact that again, like the data collection for it is pretty hard to do, so you have to start like adding layers at a time. So you can look at things at just like maybe how the repositories are structured, but that may or may not be indicative of how decisions are made, which may or may not be indicative of communication layers. [14:12] But when we start thinking about this in terms of how do you model that? These are all actually separate modeling techniques that you use for each of these different kinds of layers. And I think that is something our team is actively interested in and working on. I have a lot of theories that are not founded on that right now. I would love to start looking at what kinds and if any, are there heard cultural norms, values, but I would really love to start understanding and seeing when a decision is made to choose one technology over the other for dev tool stacks for a community, because there's a lot of porting that's happened in the last few years. [14:51] How has that worked out? So not even like the initial choice to choose that dev tool or that infrastructure stack may have been made five years ago for different reasons that they would be made now. Has that worked out to meet the community's goals? Has it changed who has access and who has voice? Has it changed who's work is visible or is that something that's still an unsolved problem for the community? And are there ways that we need to think about focusing on that so that they get more visibility and transparency regardless of their decision? Ben [15:21]: I kind of feel like those latter points about whose contributions are recognized and valued and so on is a little bit of a, hidden nugget of another point, because I would say that my opinion, which is also not based on fact, but my experience to date has been communities that are based around platforms like GitHub are maybe a little bit more code centric and communities that aren't are possibly a little bit more interpersonal. And I think that there's a whole load of issues that we could potentially unpack there. Do you see any of that already? Is that something that you are already kind of thinking about or working on? Amanda [15:56]: Yes. So our team has been working on, we call it the across project and I always forget what the acronym stands for, but it basically comes to like better attribution and credit in open source. So we have done research on that. The paper actually won the Fass award at Minimg Software Repositories conference last year. And it was actively looking at contributions that are measured for code centric repositories, as you said, because this is what we're really trying to show, is that when you're only looking at code and acknowledging that a lot of people are trying to shove a lot of things into repos these days that maybe they weren't intentionally designed for, for, but again, going along with that idea of atomic information, about a project or about a community or about an ecosystem. [16:38] So looking at a repository centric view, we evaluated the difference between how GitHub contributors shows actions and gives attribution how the events API does it. There's a tool that one of my colleagues, Katie McLaughlin wrote called octohatrack, which looks at a code repo on GitHub and produces a list of contributors for anybody who's ever interacted with that repository, which is different than what the GitHub API shows. And then we also compared that against repositories that were using the all contributors bot. So the all contributors bot for those listening who are not familiar with this, the bot it is a way that you can manually add in or add in through different actions. So it's, auto plus manual. [17:19] Ways that you can start to give people credit and attribution for things that may not be reflected by a change in the repo. So we started to look at the difference between for communities and projects, what kind of things were getting added manually versus what automatic contributions would show. And we were able to see that folks that were using manual additions were giving credit from more of the kind of work that would never show up in an API. And so part of this is really starting to think about what kind of mixed methods tooling, changes to tooling we should be thinking about as a community to really start to give that visibility into all of the work that happens like this podcast itself, unless it's in a repo is not going to be showing up as a part of the open-source community if you're doing archeology around open-source contributions. [18:12] But I would argue that discourse and thought and community should be something that would be recognized. And so we held some workshops. I mean, we're going to have some more results coming out from that. But one of the things that we did find, which we can talk about is that getting everybody in open-source to agree on what a project is, an organization is, or an event is a very hard problem. So standardized definitions is not something that carries across as a global ecosystem level. And so when we talked earlier about examining different projects, I think drawing boundaries and open-source is a very challenging problem. So you have to be very distinct when you talk about where the boundaries around people are or around technology is as opposed to being able to say open source is like this big, broad thing. Ben [19:01]: I was wondering the role of GitHub. And I'm curious your thoughts on how much control we actually have as an open-source community to make really effective changes when the tool that basically we all kind of go to for open source is a private company with their own interests. I was wondering what type of responsibility you see that would come from GitHub and is that going to affect us long term and how so? Amanda [19:26] : I mean, obviously I work for a for-profit company. I don't work for a nonprofit, I don't work for, I'm not an independent consultant or contractor. So for me, I do look at the question of what is the goal of a community to moving to a centralized platform at any time. And I think that when done intentionally and if always done with a feeling of independence and autonomy, that's the right decision for that team to be able to move and choose which dev tools and platforms work best for them. When it feels like there are only one option for any kind of tool or infrastructure or access, that's when I always will start getting concern. [20:10] So for me, when we think about centralized platforms, I think the trade offs for that is considering whether or not this is serving the community, or is this serving the platform and the product? And always taking the perspective and understanding that whenever you choose to be on a product, even if it's a free tier, it's not that are giving nothing in response for getting everything. So in the before, like before I used to, I had this job, I think one of the jokes I used to have with my friends is, if you would like me to tear down your terms and conditions from a data perspective, I'm happy to do that for you to talk about what kind of things the data teams may be working with based on what you sign off as a user. [20:51] It's something I've been highly aware of my entire career, but I don't know if everybody else views it that way. So I also know that when I talk with folks about doing productivity studies of open-source, it makes people feel a little bit nervous. Nobody wants to observed in a way that they are not opting into. So when I try to think about the work that we're doing and where we encourage and think about transparency, not just as a cultural communal trait, but as a source of representation and census. [21:21] So when we hear or think or talk about the larger effects that open-source has in the world, who gets to be represented in that, how is their work represented in that? Your decisions around transparency and proprietary information, how is that influencing or changing the way that larger view has? How does it change the conversation? How does that change the global business and how investments are made? And I think that we can want to pretend that all of those analogies and realities don't exist, but the fact is that they do, and individual efforts can add up to collective and cumulative effects. [22:04] But that's when we really have to start talking as to who does it serve and why. And so I think for me, when I think about centralized platforms and whether or not that gives access, or it removes access, as long as communities are understanding that and understanding who it leaves out and who it includes, that's really the decision that I look for when I'm trying to see why and how people are choosing to be on different kinds of managed services. Richard [22:33]: I'm really enjoying this conversation and I'm really enjoying listening to you, but it's been difficult for me to formulate a question effectively, partially because a lot of the words you are using are not things that I have here on autopilot. A lot of our guests, no offense to them, they're wonderful guests, but I can just be like, cool, where is your business model coming from? How's that going? How are you making things better? And with you, the concepts that you're throwing out during the conversation are ones that I don't regularly wrestle with, using this verbiage which I find very effective. One of the things that I know we've talked about before is open-source as different types of systems, open-source X kind of a system. You mentioned earlier that you worked as a control. I, don't even remember the term because I don't really know what it is, like a control engineer or something I'm guessing that's more like low level. Amanda [23:22]: Okay. I will give you a little bit of a break Richard in that, control systems engineer comes up on exactly zero drop menus. Anytime I've ever had to input. So I don't even know how many programs have that, but it is what's on my bachelor's degree and it's not something that is, and to be quite fair, it's weapons and control systems engineering. Because I went to the United States Naval academy. So that definitely not on there, but my focus while I was there was robotic systems and environmental engineering, which at the time was why are microgrids not yet feasible and how much does solar cost? So totally fine. If that doesn't didn't originally. Richard [24:05]: That's excellent. Thank you for explaining, what did that mean again? Amanda [24:10]: Well, okay. So the TLDR control systems is how do you take what could be inoperable systems and actually make them work together, in a way where you can abstract enough of the way the physics that you can understand where they interconnect. And for me basically it's how do I now see the world as block diagrams and feedback loops? Richard [24:29]: So how do you see open-source as block diagram and feedback loops? What is open-source then to you? Amanda [24:34]: Okay. So I have a full list of these kinds of things and I will say like I have open documents in writing that I have not yet pushed out. And Julie and I do did touch on this in our Ruby comp talk. So we gave a talk last year called black swans of open-source. And that's a research line we're still working on because we're so fascinated by this issue. But the way that we talk about it is open-source. Like you said, open-source is a blank system. And then it's all these different layers and lenses and views that we are looking at this system as. [25:07] And so talking about, I think we talked about before that open-source is a complex system, which is why Vermont complex systems work so well, then I can go through complexity theory or drop some links into the show notes for folks who need to be able to work on that. But we also view the lens that open-source is a sociotechnical system that you cannot divorce the human and social elements and constructs from the technical decisions and effects that it has. Open-source is distributed. It's cooperative. It's an economic system that we don't talk about enough what that means and the effects that it has again on people in it and how it evolves over time. [25:40] And most recently I've also been trying to parse out in my brain that if we view open-source as a legacy system. The concept of open-source as a legacy system, what does that mean for me and a Jing, like an aging global system construct while still keeping it running and then evolving it moving forward. Where are the magnetic tape mainframes of open-source that we just stick these clients and these things on top of? And then build fatter clients on top of, and then we look at it and we're like, well, everything's fine, right? [26:20] But then we start to have things like critical vulnerabilities that are deep down in these older infrastructures and it strikes us by surprise. So I think this is where the black swans area moves into is because Julie and I really try to parse apart and understand what are the analogies and assumptions that we use to describe open-source and are those valid, do they exist? Are they just constructs in our minds that we've used as either recruiting tales or onboarding tales or based on life experience, but don't really exist outside of our own time-frame. [26:56] So this is, I think for me trying to like really take a step back and understand not to is based off of my experience, people ,I know what I can see online, and this was the Genesis for our open-source stories project too. So for those who don't know, Julie and I run a Story Corp project where we are gathering stories from folks in open-source and making them visible in public. And the purpose of that isn't even to talk about people's journeys in open source, it's just to talk about them as humans so that we really start bringing that cultural perspective together, especially before some folks just decide they no longer want to be involved. [27:31] So these are all the different ways that like, let's say background, current work, everything kind of blends together. How are we actually thinking about this and how does the world that we all love and are apart of work and how can we describe it better so that we could better support it? Richard [27:46]: I couldn't hard agree more with everything that you're saying around different ways of viewing open-source. One of the main question I have personally, and I'm going to try to phrase it in a way that's not just about Richard, is what advice would you give to someone who has these thoughts about open-source? You seem to be very and looking at a complex system and finagling other people to pay you to work on that complex system and then be able to actually effectively get your ideas about that system out there into the world. [28:14] I'm curious for those who are doing other open-source projects, for those who want to try a different economic system in their project, who want to talk about open-source is an ethics system, who want to collaborate more effectively with other people about whether open-source is even the term they want to use anymore, et cetera, et cetera. How would you suggest that they make the world of open-source a more complex and beautiful place with what they offer? What should they do? Amanda [28:41]: First of all, call me maybe, because I love co conspirator and people to talk to and work with. And I would say we talked earlier about how I'm not a fan of titles. Part of that is because so much of my career has been really non-linear, job titles, experiences, roles. And this even goes into, when I talk about thinking of representing labor and open source, I really try to avoid nouns and focus on verbs because it's less about what a person is called and more about the work that they do based on what's needed at the time or required. And so I think one of my verbs I would turn into a noun Richard is professional nerd sniper, and that's hard. [29:16] I don't want sniper in there. So it needs to be like snippet, maybe professional nerd snippet, because going back to the XKCD comic, I am very good in conversations at picking up on what brings people energy and then trying to examine in my like mind map of files, where is there a gap that I see in the world or in my projects or interests or someone else's interests and how can I help this energetic person fit with the thing that gives them energy? [29:48] So for other people, I would say that first of all, if you do have the idea that open source is a complex system, keeping in mind that then open source is not one thing. It's many interacting components and parts that interact together in multiple ways, which also tells us that there are local rules you can look at so that there's no one way to go about being in open-source, doing open-source, contributing to open-source, leading in open-source. So giving yourself, first of all, the permission to examine what is it that brings you energy and where can you put that, versus trying to follow someone else's path or pattern to what it is that they think being a leader in open-source looks like. I mean, I started being a data scientist in 2009. Nobody knew what being a data scientist would look like in 2021, 12 years ago. [30:46] So for people who are trying to examine what to do with their time, energy, talent, is really looking at, I try to view things as we're working in an emergent system. There's no map for what's happening next, especially now. There's so much chaos in what's happening in so many different things that we're working on that if you're trying to move things forward in a linear, like exponential scale, you will probably fail right now. But if instead you're viewing and looking at your work, your contributions, what you want to have as really kind of interacting and nudging things in a way where greater things can emerge from it, I feel like you'll get more satisfaction. [31:28] So I feel like a lot of that disconnect that folks have who view things either as a system or from a complexity point, is that they feel like they keep being shoved into these other expectations and these other expectations of time or scale or the way things work. And I would say if you draw back to the things that you really think to be true and examine that and find other people who value that you'll be much more satisfied. Richard [31:53]: I know you're a huge fan of DEI work in open source. A lot of what you said strikes me as very easy to accomplish if you're privileged, not saying that was intentional about what you said, I'm just saying that's how it struck me. And one of the things I'm curious about is, how would you ask people who are less privileged in open-source to be able to have the ability to do that and to share that energy and to open those doors. What would you suggest for people working open-source who don't have a huge amount of privilege and may find it harder to laterally? Amanda [32:23]: So, first of all, I do want to say, I think working in open-source isn't always going to be recognized as a centralized platform contribution profile. So when we're trying to say who and how do we actually recognize that work, please do not use that as the measurement for your own contributions, which is why I talk a lot about how some of my main contributions in open-source have been making pies for people because it makes me happy and it makes them happy. And that just makes general community good. [32:48] One of the questions I have is when we are looking at understanding what is best and what's next and needed in open-source, I am concerned that we have an increasingly weird bias. And so weird in that case would be categorized as Western educated, industrialized, rich and democratic. I mean, it's something I'm aware of. I talk to people about, and like incognizant of when we are trying to understand the future, are we increasing that or are we decreasing that? [33:15] And for me that means a lot more connection, outreach and learning from people who don't grow up or contribute or form communities that look like that. And I'll say, I have a ton of work to do there. And I'm very excited to meet more folks who create community, contribute to technology, who don't fit that profile and learning more about what engages them, what keeps them there and what challenges they face, because we know what challenges some folks face. We know that some folks work at technology companies and are extremely talented and rich, but none of their work ever shows up in a public place. And then when they get home, they have other things that they have to do and they will never have anything it's in a public place, but it doesn't make them any less of a contributor in the world. [34:02] Or maybe even a contributor towards asking questions and clarifications and making documentation improved in a way that their name will never show up. But I do think the centralized idea of finding and connecting with community is universal and ensuring that everyone has access to information and communication networks is a human right. And so making sure that people all have access to global communication regardless of where they live and the devices that allow them those communication is something we should all be concerned with and that we should make sure that we are in a way that increases equity and not in a way that actually separates us even more. Ben [34:39]: I love this conversation. There have been so many touch points for me that I'm just massively interested in. And to be honest, a little bit obsessed by, and I think there is a moment, an intersection here between kind of a philosophical kind of view of open-source. You kind of get to decide whether it is about the peopl or it's about the code, which for me is kind of like the discussions that you sometimes hear about market economics, is demand and supply actually decided by the demand side or by the supply side, because the supply side creates the demand side? [35:14] I was wondering with that in mind, and talking about the privilege that people have at the moment to be able to use their free time to contribute to open-source software versus those that necessarily don't, what are your thoughts on kind of emerging ways of being able to support projects financially and things that we can do to support that, to bring the next generation from the developing world, from the global [35:38 inaudible], from however you want to kind of refer to the parts of the world where people just haven't really had the opportunity to benefit yet. Amanda [35:45]: So I think one of the best things we can think about doing is technology companies can start building more offices in places that are not the United States and Europe and certain countries in Asia. So encouraging, not just offshore or remote job. And I know that the idea of offices right now still feels like perhaps either a scary thing. But the reason I bring that up is because very concretely that also changes tax structures and incentives and benefits for companies. [36:11] So there's a big difference between being able to hire someone as a contract, which is fine. That's sometimes the job structure that some people want, but that's a very different benefit structure for other people than sometimes being a full-time employee. So when I think about equity, one of the first things I started thinking about is where are you investing in offices? Where are you investing in incorporating your company? Where are you invested in hiring people from? And the very clear economics of link communities in those countries and countries that are not places that other companies do business is sometimes it can be very challenging as you well know, to get money transferred across borders. [36:47] And in a way where it respects regulatory requirements and actually understands all of those tax incentives. So sometimes one of the hard problems in open-source is getting resources to the groups. If you have resources and someone else needs them moving the thing you have to the thing in need can be very challenging because we only have so many systems that are set up to be able to do that. And being able to do that at scale is an entirely different problem. So when I start thinking about growing places, first of all, I do think about also asking the people who are already there and who are already creating those groups and those challenges. [37:25] So I really have learned a lot and I absolutely love working with the folks from open-source community Africa, and also from Python, Africa and Python, Ghana or some really interesting groups. Python, Ghana is interesting for me because is a countrywide Python community. It's both distributed and centralized in the same way that seems to be working well for folks that they work with. And it incorporates a lot of other kind of groups. Open-source community Africa, I had a chance to go to their open-source festival right before the shutdown in 2020. [37:56] And they had, I think they were expecting like a few hundred people. And by the final day it was over a thousand. I mean, it was tons of students and people brought together and it was absolutely wonderful. When I think also too, about another thing I'm working on now, I would love to improve documentation transparency and reporting around sponsorships for open-source of just making it more clear, what organizations need in a way that is discoverable accessible and able to be found by groups. [38:30] I would love the people who have resources to give, to cast wider nets and have better places to be able to connect with those they depend on and in return, I would love transparency reporting for those sponsorships and the impacts of those sponsorships to be accessible in ways that when we see organizations or foundations or very small projects, be recipients of sponsors, giving them the support and the tools they need to be able to show what impact that had also for holding each other more accountable. There's a lot of money moving around in these ecosystems. And the questions that I constantly have is, are those the right places they should be moving? Richard [39:15]: I think that's probably a really good place to wrap up because it was just so succinct and perfect. So thank you so much, Amanda, for people who want to get in touch with you on the internet to learn more how they can collaborate and get these things done with your help, if you're available, where can they find you online? Amanda [39:30]: Twitter is the best place to contact me, which I know is a closed platform, but it's the easiest way for me to go through all of the direct contact. If you're curious about the open-source stories project, we are on GitHub, but we also have a website with links to be able to contact there as well. Richard [39:49]LThank you so much. And Twitter will also be in the show notes for those of you who want to reach her on Twitter. Amanda this has been excellent, but don't go yet. This is the part of the show where we talk about people, projects or things, which we think we should shed light on and or that need more love, that's right. It's spotlight, Eric Barry, what is your spotlight today? Eric [40:11]: First I got to say, I'm just overwhelmed on how amazing the show has been. So thank you, Amanda. Absolutely incredible podcast episode. I'm a big fan boy. So what I'd like to spotlight is actually an article you had submitted on open-source ecosystems, which need equitable credit across all of the contributions and stuff. I read through that, it was just really fascinating. I recommend anybody to read it. The link will be in the show notes. Richard [40:35]: Thank you so much. Excellent. Ben Nichols. Ben [40:38]: This is incredibly timely. So excuse me if it doesn't age too well, but I just wanted to give a big shout out to Jess Sax and the maintainers of [inaudible] JS that have picked up the project and are kind of providing a huge value to the community that depend on that project. We've been working with them over the course of the last week and the way that they have acted to try to kind of set things up in the best interests of all of the users, all of the kind of contributors, the previous maintainers and everything. Like it's just, it's been great to work with them. So I just wanted to kind of call out Jess specifically, but all of the new maintainers of [inaudible] JS. Richard [41:18]: Awesome. Thank you. In a left turn, I'm going to just give a shout out to Red Hen baking. If you're in Vermont and you want to go to a really nice bakery, there's a place in Middlesex, which is really nice. It's called Red Hen. If you don't have a local baker, I'd suggest looking around because if you're in the United States, there's probably a bakery near you somewhere that makes really good bread. This is mine. So Red Hen baking is excellent. Really like their mad river loaf, highly suggest. Amanda, what is your spotlight today? Amanda [41:47]: Yeah. So for those who don't know, I'm also a complete library and book nerd. And so I get really excited about the open-access projects and books. And so my recommendation, I couldn't narrow it down. So I'm going to say my recommendations today. I love the data feminism book that came out in 2020. It is available via open-access. I recently found a project called the data sitters club, which attracted to me because I found it on the executable book project, which is a whole community around Jupiter book, open-access and computational publishing. [42:16] The data sitters club is this group of people who are helping to explain computational text analysis and open data using open-access, open data and actual exploring fair use. And it is completely fair use of the babysitters club that I grew up with. And I absolutely adore the way that they've adopted that. They have a lovely debt of public health posters for the pandemic that they created in 2020 that still bring me joy to read. Richard [42:46]: Love it. Awesome, Amanda, thank you. Once again, it was great having you on, look forward to talking to you further in the future and best of luck with everything. Thanks. Amanda [42:55]: Thank you. This is great. Special Guest: Amanda Casari.

Chain Reaction
Web3 is an Opportunity for All Developers: Nader Dabit, Developer Relations Engineer at Edge & Node

Chain Reaction

Play Episode Listen Later Mar 1, 2022 57:24


Next in our Web3 series, we have Nader Dabit, a Developer Relations Engineer at The Graph and Edge & Node. Having spent 10 years in the traditional tech world, Nader brings the developers' perspective of building in Web3 versus Web2. We discuss the “Web3-ification” of Web2 apps, identity management solutions, and much more!  Show Notes:  (00:00:00) – Introduction and Nader's background. (00:05:56) – Will Web2 embrace Web3? (00:10:44) – Development in Web2 vs. Web3.  (00:17:30) – Most significant user experiences in Web3.  (00:21:43) – The development process in Web3.  (00:35:56) – The Graph. (00:38:02) – Dealing with Identity / Misconceptions about Web3.  (00:42:51) – Maximalism in crypto.  (00:46:38) – The future of wallets / Web3-ification and new paradigms.  (00:54:07) – Closing. Resources:  Nader's Twitter Edge & Node Twitter Edge & Node Website The Complete Guide to Full Stack Ethereum Development Delphi Podcast Summaries More

Hey Change - Finding Happiness in New Realities
E92. Ecopsychology and The Power Of Emergent Systems

Hey Change - Finding Happiness in New Realities

Play Episode Listen Later Mar 1, 2022 47:42


How do we restore our spiritual relationship with nature and find ourselves as embedded participants within the web of life? More importantly -- what does that look like in practice?In this fascinating conversation with Aaron, we talk Ecopsychology, how a culture of emergence within companies can help shift society in a positive direction, as well as how a community-driven approach might lead us into a climate optimistic world.Aaron Gabriel Neyer is a Developer Relations Engineer at Google with a big passion for both living and technological systems. He's currently furthering his education with a Master's in Eco-Psychology at Naropa University.Connect with Aaron: https://www.linkedin.com/in/wildsunlove/CONNECT + FOLLOW:Podcast Instagram: @heychange_podcastHosts: @annetheresegennari + @robinxshawPodcast website: www.theclimateoptimist.com/hey-change-podcast See acast.com/privacy for privacy and opt-out information.

Council Of The Wise Developers
S2E3 COMMUNITY | Toby Bee's NFC project | Tarric Sookdeo @ Dwolla

Council Of The Wise Developers

Play Episode Listen Later Feb 28, 2022 19:52


It's another VOICES OF THE COMMUNITY Episode!First, get an EXCLUSIVE look at Toby Bee's new project: NFC's!Then, head of the council Enoch Wise interviews Tarric Sookdeo, Developer Relations Engineer at ACH-payments-company Dwolla!

Modern Web
S09E05 Modern Web Podcast - The State of Angular with Mark Thompson

Modern Web

Play Episode Listen Later Feb 11, 2022 53:18


In this episode, Rob Ocel discusses the present state and future goals of the Angular ecosystem with Mark Thompson, Developer Relations Engineer at Google, and Angular Core Team member. They talk about Angular's most recent accomplishments, like the advancements afforded by Angular v12, and how the Angular team responds to RFCs and other forms of community feedback. Mark also explains how the community should interpret roadmaps, and the spectrum of stages at which an in-development project might be, and how developers and non-developers can contribute to the ecosystem. Rob and Mark also talk about the relationship between third-party solutions and the Angular team's attitude toward potentially rolling these solutions into the core framework.   Guest: Mark Thompson (@marktechson) - Developer Relations Engineer, Google    Host: Rob Ocel (@robocell) - Architect, This Dot Labs   This episode is sponsored by HARMAN & This Dot Labs.

CHAOSScast
Episode 50: Recognizing all Kinds of Labor in Open Source Ecosystems with Amanda, Katie, and John

CHAOSScast

Play Episode Listen Later Jan 14, 2022 45:54


Hello and welcome to CHAOSScast Community podcast, where we share use cases and experiences with measuring open source community health. Elevating conversations about metrics, analytics, and software from the Community Health Analytics Open Source Software, or short CHAOSS Project, to wherever you like to listen. Today, we have three amazing guests with us, Amanda Casari, Katie McLaughlin, and John Meluso. Amanda is a Developer Relations Engineer and researcher at Google at the Open Source Programs Office, Katie is a Developer Relations Engineer at Google, and John is the OCEAN Postdoctoral Fellow at the University of Vermont. They are with us to talk about Project OCEAN (Open-Source Complex Ecosystems And Networks), how it came to be, where it is now, and what they hope to accomplish going forward. We also learn more about what they see as an open source ecosystem, and they go in depth about contributions and taxonomy. Download this episode now to find out much more, and don't forget to subscribe for free to this podcast on your favorite podcast app and share this podcast with your friends and colleagues! [00:03:44] John, Amanda, and Katie tell us their backgrounds and how they got involved in open source. [00:07:23] We learn more about OCEAN, how it came to be, and where it's at now. [00:11:25] Amanda and John explain a bit more about ecosystems. [00:15:52] Georg wonders what they have realized early on or over time that they want to make sure everyone who looks at open source takes away from their work. [00:19:59] Amanda brings up a question to the panelists concerning the idea of atomic information around software projects and balancing how much do they keep with a repo versus how do you allow for information to be distributed in many places that many people work, but it doesn't get lost and you don't lose somebody's attribution for the work they do. [00:28:58] Georg brings up the Types of Contributions metrics link CHAOSS uses that helps show how people can contribute to open source, and Katie shares her thoughts on it. [00:32:13] Sophie talks about “Which contributions count? Analysis of attribution in open source” report and what this research explores. John explains how they balance things by varying the kinds of methodologies they use. [00:38:49] Find out where you can follow Amanda, Katie, and John online. Value Adds (Picks) of the week: [00:39:45] Georg's pick is LifeTime wellness and fitness center. [00:40:31] Matt's pick is places to visit in Colorado: Rocky Mtn. National Park, Great Sand Dunes, and Gunnison National Park. [00:41:08] Sophia's pick is emergent property. [00:41:57] Amanda's pick is trading Vermont Golden Dome books with her oldest child. [00:43:10] Katie's pick is the book, CPython Internals by Anthony Shaw. [00:44:03] John's pick is the book, Data Feminism by Catherine D'Ignazio and Lauren F. Klein. Request from our Guests: Open Source Folks: Take (and share!) this anonymous survey about receiving credit for tasks in open source! Conducted by researchers at the University of Vermont in partnership with Google Open Source. [https://qualtrics.uvm.edu/jfe/form/SV_1zUs19oVcZJ0SPA](https://qualtrics.uvm.edu/jfe/form/SV_1zUs19oVcZJ0SPA) Panelists: Georg Link Sophia Vargas Matt Germonprez Guests: Amanda Casari Katie McLaughlin John Meluso Sponsor: SustainOSS (https://sustainoss.org/) Links: CHAOSS (https://chaoss.community/) CHAOSS Project Twitter (https://twitter.com/chaossproj?lang=en) CHAOSScast Podcast (https://podcast.chaoss.community/) podcast@chaoss.community (mailto:podcast@chaoss.community) Project OCEAN (https://vermontcomplexsystems.org/partner/OCEAN/) Amanda Casari Twitter (https://twitter.com/amcasari?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Open Source Stories-Amanda Casari Website (https://www.opensourcestories.org/) Amanda Casari Linkedin (https://www.linkedin.com/in/amcasari/) Katie McLaughlin Twitter (https://twitter.com/glasnt) Katie McLaughlin Website (https://glasnt.com/) John Meluso Twitter (https://twitter.com/johnmeluso) John Meluso Linkedin (https://www.linkedin.com/in/jmeluso/) John Meluso, PhD Website (https://www.johnmeluso.com/) John Meluso Email (mailto:john.meluso@uvm.edu) ACROSS Taxonomy-GitHub (https://github.com/google/across) CHAOSS Types of Contributions metrics (https://chaoss.community/metric-types-of-contributions/) Which contributions count? Analysis of attribution in open source-Jean-Gabriel Young, Amanda Casari, Katie McLaughlin, Milo Z. Trujillo, Laurent Hébert-Dufresne, James P. Bagrow (https://arxiv.org/abs/2103.11007) Open source ecosystems need equitable credit across contributions-Amanda Casari, Katie McLaughlin, Milo Z. Trujillo, Jean-Gabriel young, James P. Bagrow, & Laurent Hébert-Dufresne (https://www.nature.com/articles/s43588-020-00011-w) Nadia Eghbal Website (https://nadiaeghbal.com/) Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure by Nadia Eghbal (https://www.fordfoundation.org/work/learning/research-reports/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure/) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) A Place to Hang Your Hat- Leslie Hawthorn's Hat Rack blog post (https://hawthornlandings.org/2015/02/13/a-place-to-hang-your-hat/) Octohatrack-GitHub (https://github.com/LABHR/octohatrack) A tool for tracking non-code GitHub contributions-Katie McLaughlin (https://opensource.com/life/15/10/octohat-github-non-code-contribution-tracker) Recognize All Contributors (https://allcontributors.org/) CHAOSScast Podcast- Episode 39: Leaderboards and Metrics at Drupal.org with Matthew Tift and Tim Lehnen (https://podcast.chaoss.community/39) LifeTime (https://www.lifetime.life/) Rocky Mountain National Park (https://www.nps.gov/romo/index.htm) Great Sand Dunes (https://www.nps.gov/grsa/index.htm) Black Canyon Of The Gunnison (https://www.nps.gov/blca/index.htm) What Are Emergent Properties? (https://sciencing.com/emergent-properties-8232868.html) Vermont Golden Dome Books (https://libraries.vermont.gov/services/children_and_teens/book_awards/vtgdba) CPython Internals by Andrew Shaw (https://realpython.com/products/cpython-internals-book/) Data Feminism by Catherine D'Ignazio (https://www.amazon.com/Feminism-Strong-Ideas-Catherine-DIgnazio/dp/0262044005/) Special Guests: Amanda Casari, John Meluso, and Katie McLaughlin.

The 6 Figure Developer Podcast
Episode 225 – SRE is a Journey with Dave Stanke

The 6 Figure Developer Podcast

Play Episode Listen Later Dec 20, 2021 42:18


  Dave Stanke joins us to talk all about Site Reliability Engineering. Dave is a Developer Relations Engineer with Google Cloud Platform specializing in DevOps, Site Reliability Engineering (SRE), and other flavors of technical relationship therapy. He loves chatting with practitioners: listening to stories, telling stories, sharing a healthy cry. Prior to Google, he was the CTO of OvationTix/TheaterMania, a SaaS startup in the performing arts industry, where he specialized in feeding memory to Java servers. He chose on purpose to live in New Jersey, where he enjoys baking, indie rock, and fatherhood.   Links https://stanke.dev/ https://twitter.com/davidstanke https://cloud.google.com/developers/advocates/dave-stanke   Resources https://sre.google/ https://bit.ly/reliability-discuss https://bit.ly/dora-sodr Thinking, Fast and Slow Site Reliability Engineering The Site Reliability Workbook Want to supercharge your DevOps practice? Research says try SRE Eliminating Toil Identifying and tracking toil using SRE principles How maintenance windows affect your error budget—SRE tips "Tempting Time" by Animals As Leaders used with permissions - All Rights Reserved × Subscribe now! Never miss a post, subscribe to The 6 Figure Developer Podcast! Are you interested in being a guest on The 6 Figure Developer Podcast? Click here to check availability!  

República Web
Headless CMS con Facundo Giuliani de Storyblok

República Web

Play Episode Listen Later Dec 15, 2021 70:32


Los headless CMS o desacoplados son una tendencia imparable en el desarrollo web. La combinación de la potencia de los frameworks de front-end y servicios en la nube para gestionar el flujo de trabajo de un CMS, están consiguiendo lo que se ha llamado "romper el monolito". La arquitectura Jamstack y el renacimiento de los generadores estáticos han propiciado que muchos desarrolladores se inclinen a crear sus soluciones con los CMS desacoplados. Estos headless CMS también ponen la experiencia de los usuarios en el centro de sus productos y además permiten adaptar mejor el contenido a los diferentes escenarios donde puede mostrarse. Para este episodio invitamos a Facundo Giuliani es actualmente Developer Relations Engineer en Storyblok, una empresa austriaca que proporciona headless CMS basada en componentes con un potente editor visual. Facundo es ingeniero y un full stack developer con una interesante carrera en importantes compañías. Aprovechando la experiencia de Facundo en el área de Headless CMS y la arquitectura del Jamstack, hablamos sobre estas tecnologías y cómo están cambiando el panorama del desarrollo web. Entre las cuestiones tratadas: Qué es un Headless CMS y qué explica el auge de esta tecnología.Recomendaciones a un desarrollador acostumbrado a tecnologías de monolito para pasar a soluciones Headless CMS.¿Cómo podemos diferenciar entre las diferentes propuestas que ofrecen los Headless CMS?¿Qué ofrece Storyblok y qué ventajas nos ofrece?¿Cuál es la situación actual del headless CMS en la parte de e-commerce y qué tecnologías y servicios destacarías en este ámbito?Full stack serverless y si los front-end developers cada vez son más full stack.¿Cuál es el futuro de los headless CMS y qué podemos esperar los próximos años?

República Web
Headless CMS con Facundo Giuliani de Storyblok #RW193

República Web

Play Episode Listen Later Dec 15, 2021 70:32


Los headless CMS o desacoplados son una tendencia imparable en el desarrollo web. La combinación de la potencia de los frameworks de front-end y servicios en la nube para gestionar el flujo de trabajo de un CMS, están consiguiendo lo que se ha llamado «romper el monolito». La arquitectura Jamstack y el renacimiento de los generadores estáticos han propiciado que muchos desarrolladores se inclinen a crear sus soluciones con los CMS desacoplados. Estos headless CMS también ponen la experiencia de los usuarios en el centro de sus productos y además permiten adaptar mejor el contenido a los diferentes escenarios donde puede mostrarse. Para este episodio invitamos a Facundo Giuliani es actualmente Developer Relations Engineer en Storyblok, una empresa austriaca que proporciona headless CMS basada en componentes con un potente editor visual. Facundo es ingeniero y un full stack developer con una interesante carrera en importantes compañías. Aprovechando la experiencia de Facundo en el área de Headless CMS y la arquitectura del Jamstack, hablamos sobre estas tecnologías y cómo están cambiando el panorama del desarrollo web. Entre las cuestiones tratadas: - Qué es un Headless CMS y qué explica el auge de esta tecnología. - Recomendaciones a un desarrollador acostumbrado a tecnologías de monolito para pasar a soluciones Headless CMS. - ¿Cómo podemos diferenciar entre las diferentes propuestas que ofrecen los Headless CMS? - ¿Qué ofrece Storyblok y qué ventajas nos ofrece? - ¿Cuál es la situación actual del headless CMS en la parte de e-commerce y qué tecnologías y servicios destacarías en este ámbito? - Full stack serverless y si los front-end developers cada vez son más full stack. - ¿Cuál es el futuro de los headless CMS y qué podemos esperar los próximos años? Más información del episodio https://republicaweb.es/podcast/headless-cms-con-facundo-giuliani-de-storyblok/

Tech Lead Journal
#68 - 2021 Accelerate State of DevOps Report - Nathen Harvey

Tech Lead Journal

Play Episode Listen Later Dec 13, 2021 47:55


“Many organizations think in order to be safe, they have to be slow. But the data shows us that the best performers are getting both. And in fact, as speed increases, so too does stability." Nathen Harvey is the co-author of 2021 Accelerate State of DevOps Report and a Developer Advocate at Google. In this episode, we discussed in-depth the latest release of the State of DevOps Report. Nathen started by describing what the report is all about, how it got started, and explained the five key metrics suggested by the report to measure the software delivery and operational performance. Nathen then explained how the report categorizes different performers based on their performance against the key metrics and how the elite performers outperform the others in terms of speed, stability, and reliability. Next, we dived into several new key findings that came out of the 2021 report that relate to documentation, secure software supply chain, and burnout. Towards the end, Nathen gave great tips on how we can use the findings from the reports to get started and improve our software delivery and operational performance, that ultimately will improve our organizational performance. Listen out for: Career Journey - [00:05:28] State of DevOps Report - [00:09:32] The Five Key Metrics - [00:13:55] Speed, Safety, and Reliability - [00:19:58] Performers Categories - [00:23:26] 2021 New Key Findings - [00:28:01] New Finding: Documentation - [00:30:44] New Finding: Secure Software Supply Chain - [00:34:58] New Finding: Burnout - [00:37:22] How to Start Improving - [00:39:36] 3 Tech Lead Wisdom - [00:43:55] _____ Nathen Harvey's Bio Nathen Harvey, Developer Relations Engineer at Google, has built a career on helping teams realize their potential while aligning technology to business outcomes. Nathen has had the privilege of working with some of the best teams and open source communities, helping them apply the principles and practices of DevOps and SRE. He is part of the Google Cloud DORA research team and a co-author of the 2021 Accelerate State of DevOps Report. Nathen was an editor for 97 Things Every Cloud Engineer Should Know, published by O'Reilly in 2020. Follow Nathen: Twitter – @nathenharvey LinkedIn – https://linkedin.com/in/nathen Github – https://github.com/nathenharvey Our Sponsor Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags by visiting https://techleadjournal.dev/shop. Like this episode? Subscribe on your favorite podcast app and submit your feedback. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/68.

Google Workspace Recap
E044: Google DevRel team members Charles Maxson and Steve Bazyl talk about the Workspace Developer Ecosystem, Delayed launch of Labels and Approvals and more

Google Workspace Recap

Play Episode Listen Later Nov 2, 2021 90:05


We welcome two amazing members from the DevRel (Developer Releations) team this episode. Charles Maxson is a Developer Advocate at Google where focuses on inspiring developers of all types to build solutions that leverage Google Workspace as a platform. Steve Bazyl is a Developer Relations Engineer and Advocate at Google and has worked with various Google Workspace APIs and partners for over a decade. Google Workspace Developer Links Everything can be found via https://developers.google.com/workspace How developers can utilize advances in Google Workspace Workspace Developer Preview Program Workspace Developer on Google Cloud Community Developer Newsletter Card Builder for Add-ons & Chatbots Deliver asynchronous notifications in Google Chat using webhooks (Charles Maxson, Justin Wexler) Silent Releases Drive Labels / Approvals GA Release Delayed > “We found some last minute issues that stopped us from making these two features generally available (GA). The teams are hard at work on solving these and they should become GA in the coming weeks.” Updating Gmail "Compose" button for Chat in Gmail users on the web New navigation menus in Google Sites Published Releases Enhanced menus in Google Sheets improves findability of key features Manage and share private iOS apps through Google Endpoint Management VirusTotal integration with the security investigation tool provides deeper insight into Gmail events Improved and updated security menu in the Admin Console

Screaming in the Cloud
The Mayor of Wholesome Twitter with Mark Thompson

Screaming in the Cloud

Play Episode Listen Later Oct 28, 2021 41:18


About MarkMark loves to teach and code.He is an award winning university instructor and engineer. He comes with a passion for creating meaningful learning experiences. With over a decade of developing solutions across the tech stack, speaking at conferences and mentoring developers he is excited to continue to make an impact in tech. Lately, Mark has been spending time as a Developer Relations Engineer on the Angular Team.Links:Twitter: https://twitter.com/marktechson TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Vultr. Spelled V-U-L-T-R because they're all about helping save money, including on things like, you know, vowels. So, what they do is they are a cloud provider that provides surprisingly high performance cloud compute at a price that—while sure they claim its better than AWS pricing—and when they say that they mean it is less money. Sure, I don't dispute that but what I find interesting is that it's predictable. They tell you in advance on a monthly basis what it's going to going to cost. They have a bunch of advanced networking features. They have nineteen global locations and scale things elastically. Not to be confused with openly, because apparently elastic and open can mean the same thing sometimes. They have had over a million users. Deployments take less that sixty seconds across twelve pre-selected operating systems. Or, if you're one of those nutters like me, you can bring your own ISO and install basically any operating system you want. Starting with pricing as low as $2.50 a month for Vultr cloud compute they have plans for developers and businesses of all sizes, except maybe Amazon, who stubbornly insists on having something to scale all on their own. Try Vultr today for free by visiting: vultr.com/screaming, and you'll receive a $100 in credit. Thats v-u-l-t-r.com slash screaming.Corey: This episode is sponsored in part by something new. Cloud Academy is a training platform built on two primary goals. Having the highest quality content in tech and cloud skills, and building a good community the is rich and full of IT and engineering professionals. You wouldn't think those things go together, but sometimes they do. Its both useful for individuals and large enterprises, but here's what makes it new. I don't use that term lightly. Cloud Academy invites you to showcase just how good your AWS skills are. For the next four weeks you'll have a chance to prove yourself. Compete in four unique lab challenges, where they'll be awarding more than $2000 in cash and prizes. I'm not kidding, first place is a thousand bucks. Pre-register for the first challenge now, one that I picked out myself on Amazon SNS image resizing, by visiting cloudacademy.com/corey. C-O-R-E-Y. That's cloudacademy.com/corey. We're gonna have some fun with this one!Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Anyone who has the misfortune to follow me on Twitter is fairly well aware that I am many things: I'm loud, obnoxious, but snarky is most commonly the term applied to me. I've often wondered, what does the exact opposite of someone who is unrelentingly negative about things in cloud look like? I'm here to answer that question is lightness and happiness and friendliness on Twitter, personified. His Twitter name is @marktechson. My guest today is Mark Thompson, developer relations engineer at Google. Mark, thank you for joining me.Mark: Oh, I'm so happy to be here. I really appreciate you inviting me. Thanks.Corey: Oh, by all means. I'm glad we're doing these recordings remotely because I strongly suspect, just based upon the joy and the happiness and the uplifting aspects of what it is that you espouse online that if we ever shook hands, we'd explode as we mutually annihilate each other like matter and antimatter combining.Mark: Feels right. [laugh].Corey: So, let's start with the day job; seems like the easy direction to go in. You're a developer relations engineer. Now, I've heard of developer advocates, I've heard of the DevRel term, a lot of them get very upset when I refer to them as ‘devrelopers', but that's the game that we play with language. What is the developer relations engineer?Mark: So, I describe my job this way: I like to help external communities with our products. I work on the Angular team, so I like to help our external communities but then I also like to work with our internal team to help improve our product. So, I see it as helping as a platform, as a developer relations engineer. But the engineer part is, I think, is important here because, at Google, we still do coding and we still write things; I'm going to contribute to the Angular platform itself versus just only giving talks or only writing blog posts to creating content, they still want us to do things like solve problems with the platform as well.Corey: So, this is where my complete and abject lack of understanding of the JavaScript ecosystem enters the conversation. Let's be clear here, first let me check my assumptions. Angular is a JavaScript framework, correct?Mark: Technically a TypeScript framework, but you could say JavaScript.Corey: Cool. Okay, again, this is not me setting you up for a joke or anything like that. I try to keep my snark to Twitter, not podcast because that tends to turn an awful lot into me berating people, which I try to reserve for those who really have earned it; they generally have the word chief somewhere in their job title. So, I'm familiar with sort of an evolution of the startups that I worked at where Backbone was all the rage, followed by, “Oh, you should never use Backbone. You should be using Angular instead.”And then I sort of—like, that was the big argument the last time I worked in an environment like that. And then I see things like View and React and several other things. At some point, it seems like, pick a random name out of the air; if it's not going to be a framework, it's going to be a Pokemon. What is the distinguishing characteristic or characteristics of Angular?Mark: I like to describe Angular to people is that the value-add is going to be some really incredible developer ergonomics. And when I say that I'm thinking about the tooling. So, we put a lot of work into making sure that the tooling is really strong for developers, where you can jump in, you can get started and be productive. Then I think about scale, and how your application runs at scale, and how it works at scale for your teams. So, scale becomes a big part of the story that I tell, as well, for Angular.Corey: You spend an awful lot of time telling stories about Angular. I'm assuming most of them are true because people don't usually knowingly last very long in this industry when they just get up on stage and tell lies, other than, “This is how we do it in our company,” which is the aspirational conference-ware that we all wish we ran. You're also, according to your bio, which of course, is always in the [show notes 00:04:16], you're an award-winning university instructor. Now, award-winning—great. For someone who struggled mightily in academia, I don't know much about that world. What is it that you teach? How does being a university instructor work? I imagine it's not like most other jobs where you wind up showing up, solving algorithms on a whiteboard, and they say, “Great, can you start tomorrow?”Mark: Sure. So, when I was teaching at university, what I was teaching was mostly coding bootcamps. So, some universities have coding bootcamps that they run themselves. And so I was a part of some instructional teams that work in the university. And that's how I won the Teaching Excellence Award. So, the award that I won actually was the Distinguished Teaching Excellence Award, based on my performance at work when I was teaching at university.Corey: I want to be clear here, it's almost enough to make someone question whether you really were involved there because the first university, according to your background that you worked on was Northwestern, but then it was through the Harvard Extension School, and I was under the impression that doing anything involving Harvard was the exact opposite of an NDA, where you're contractually bound to mention that, “Oh, I was involved with Harvard in the following way,” at least three times at any given conversation. Can you tell I spent a lot of time dealing with Harvard grads?Mark: [laugh]. Yeah, Harvard is weird like that, where people who've worked there or gone there, it comes up as a first thing. But I'll tell the story about it if someone asks me, but I just like to talk about univer—that's why I say ‘university,' right? I don't say, “Oh, I won an award at Northwestern.” I just say, “University award-winning instructor.”The reason I say even the ‘award-winning', that part is important for credibility, specifically. It's like, hey, if I said I'm going to teach you something, I want you to know that you're in really good hands, and that I'm really going to do my best to help you. That's why I mention that a lot.Corey: I'll take that even one step further, and please don't take this as in any way me casting aspersions on some of your colleagues, but very often working at Google has felt an awful lot like that in some respects. I've never seen you do it. You've never had to establish your bona fides in a conversation that I've seen by saying, “Well, at Google this is how we do it.” Because that's a logical fallacy of appeal to authority in many respects. Yeah, I'm sure you do a lot of things at Google at a multinational trillion-dollar company that if I'm founding a four-person startup called Twitter for Pets might not necessarily be the same constraints that I'm faced with.I'm keenly appreciative folks who recognize that distinction and don't try and turn it into something else. We see it with founders, too, “Oh, we're a small scrappy startup and our founders used to work at Google.” And it's, “Hmm, I'm wondering if the corporate culture at a small startup might be slightly different these days.” I get it. It does resonate and it carries weight. I just wonder if that's one of those unexamined things that maybe it's time to dive into a bit more.Mark: Hmm. So, what's funny about that is—so people will ask me, what do I do? And it really depends on context. And I'll usually say, “Oh, I work for a company on the West Coast,” or, “For a tech company on the West Coast.” I'll just say that first.Because what I really want to do is turn the conversation back to the person I'm talking to, so here's where that unrelenting positivity kind of comes in because I'm looking at ways, how can I help boost you up? So first, I want to hear more about you. So, I'll kind of like—I won't shrink myself, but I'll just be kind of vague about things so I could hear more about you so we're not focused on me. In this case, I guess we are because I'm the guest, but in a normal conversation, that's what I would try to do.Corey: So, we've talked about JavaScript a little bit. We've talked about university a smidgen. Now, let me complete the trifecta of things that I know absolutely nothing about, specifically positivity on Twitter. You have been described to me as the mayor of wholesome Twitter. What is that about?Mark: All right, so let me be really upfront about this. This is not about toxic positivity. We got to get that out in the open first, before I say anything else because I think that people can hear that and start to immediately think, “Oh, this guy is just, you know, toxic positivity where no matter what's happening, he's going to be happy.” That is not the same thing. That is not the same thing at all.So, here's what I think is really interesting. Online, and as you know, as a person on Twitter, there's so many people out there doing damage and saying hurtful things. And I'm not talking about responding to someone who's being hurtful by being hurtful. I mean the people who are constantly harassing women online, or our non-binary friends, people who are constantly calling into question somebody's credibility because of, oh, they went to a coding bootcamp or they came from self-taught. All these types of ways to be really just harmful on Twitter.I wanted to start adding some other perspective of the positivity side of just being focused on value-add in our interactions. Can I craft this narrative, this world, where when we meet, we're both better off because of it, right? You feel good, I feel good, and we had a really good time. If we meet and you're having a bad time, at least you know that I care about you. I didn't fix you. I didn't, like, remove the issue, but you know that somebody cares about you. So, that's what I think wholesome positivity comes into play is because I want to be that force online. Because we already have plenty of the other side.Corey: It's easy for folks who are casual observers of my Twitter nonsense to figure, “Oh, he's snarky and he's being clever and witty and making fun of big companies”—which I do–And they tend to shorthand that sometimes to, “Oh, great. He's going to start dunking on people, too.” And I try mightily to avoid that it's punch up, never down.Mark: Mm-hm.Corey: I understand there's a school of thought that you should never be punching at all, which I get. I'm broken in many ways that apparently are entertaining, so we're going to roll with that. But the thing that incenses me the most—on Twitter in my case—is when I'll have something that I'll put out there that's ideally funny or engaging and people like it and it spreads beyond my circle, and then you just have the worst people on the internet see that and figure, “Oh, that's snarky and incisive. Ah, I'm like that too. This is my people.”I assure you, I am not your people when that is your approach to life. Get out of here. And curating the people who follow and engage with you on Twitter can be a full-time job. But oh man, if I wind up retweeting someone, and that act brings someone who's basically a jackwagon into the conversation, it's no. No-no-no.I'm not on Twitter to actively make things worse unless you're in charge of cloud pricing, in which case yes, I am very much there to make your day worse. But it's, “Be the change you want to see in the world,” and lifting people up is always more interesting to me than tearing people down.Mark: A thousand percent. So, here's what I want to say about that is, I think, punching up is fine. I don't like to moderate other people's behavior either, though. So, if you'd like punching up, I think it'd be funny. I laugh at jokes that people make.Now, is it what I'll do? Probably not because I haven't figured out a good way for me to do it that still goes along my core values. But I will call out stuff. Like if there's a big company that's doing something that's pretty messed up, I feel comfortable calling things out. Or when drama happens and people are attacking someone, I have no problem with just be like, “Listen, this person is a stand-up person.”Putting myself kind of like… just kind of on the front line with that other person. Hey, look, this person is being attacked right now. That person is stand-up, so if you got a problem them, you got a problem with me. That's not the same thing as being negative, though. That's not the same thing as punching down or harming people.And I think that's where—like I say, people kind of get that part confused when they think that being kind to people is a sign of weakness, which is—it takes more strength for me to be kind to people who may or may not deserve it, by societal standards. That I'll try to understand you, even though you've been a jerk right now.Corey: Twitter excels at fomenting outrage, and it does it by distancing us from being able to easily remember there's a person on the other side of these things. It is ways you're going to yell at someone, even my business partner in a text message. Whenever we start having conversations that get a little heated—which it happens; business partnership is like a marriage—it's oh, I should pick up the phone and call him rather than sending things that stick around forever, that don't reflect the context of the time, and five years later when I see it, I feel ashamed." I'm not here to advocate for other people doing things on Twitter the way that I do because what I do is clever, but the failure mode of clever in my case is being a complete jerk, and I've made that mistake a lot when I was learning to do it when my audience was much smaller, and I hurt people. And whenever I discovered that that is what happened, I went out of my way, and still do, to apologize profusely.I've gotten relatively good at having to do less of those apologies on an ongoing basis, but very often people see what I'm doing and try to imitate what they're seeing; it just comes off as mean. And that's not acceptable. That's not something that I want to see more of in the world. So, those are my failure modes. I have to imagine the only real failure mode that you would encounter with positivity is inadvertently lifting someone up who turns out to be a trash goblin.Mark: [laugh]. That and I think coming off as insincere. Because if someone is always positive or a majority of the time, positive, if I say something to you, and you don't know me that actually mean it, sincerity is incredibly hard to get over text. So, if I congratulate you on your job, you might be like, “Oh, he's just saying that for attention for himself because now he's being the nice guy again.” But sincerity is really, really hard to convey, so that's one of the failure modes is like I said, being sincere.And then lifting up people who don't deserve to be lifted up, yeah, that's happened before where I've engaged with people or shared some of their stuff in an effort to boost them, and find out, like you said, legit trash goblin, like, their home address is under a bridge because they're a troll. Like, real bad stuff. And then you have back off of that endorsement that you didn't know. And people will DM you, like, “Hey, I see that you follow this person. That person is a really bad person. Look at what they're saying right now.” I'm like, “Well, damn, I didn't know it was bad like that.”Corey: I've had that on the podcast, too, where I'll have a conversation with someone and then a year or so later, they'll wind up doing something horrifying, or something comes to light and the rest, and occasionally people will ask, “So, why did you have that person on this show?” It's yeah, it turns out that when we're having a conversation, that somehow didn't come up because as I'm getting background on people and understanding who they are and what they're about in the intake questionnaire, there is not a separate field for, “Are you terrible to women?” Maybe there should be, but that's something that it's—you don't see it. And that makes it easy to think that it's not there until you start listening more than you speak, and start hearing other people's stories about it. This is the challenge.As much as I aspire at times to be more positive and lift folks up, this is the challenge of social media as it stands now. I had a tweet the other day about a service that AWS had released with the comment that this is fantastic and the team that built it should be proud. And yeah, that got a bit of engagement. People liked it. I'm sure it was passed around internally, “Yay, the jerk liked something.” Fine.A month ago, they launched a different service, and my comment was just distilled down to, “This is molten garbage.” And that went around the tech internet three times. When you're positive, it's one of those, “Oh, great. Yeah, that's awesome.” Whereas when I savage things, it's, “Hey, he's doing it again. Come and look at the bodies.” Effectively the rubbernecking thing. “There's been a terrible accident, let's go gawk at it.”Mark: Right.Corey: And I don't quite know what to do with that because it leads to the mistaken and lopsided impression that I only ever hate things and I don't think that a lot of stuff is done well. And that's very much not the case. It doesn't restrict itself to AWS either. I'm increasingly impressed by a lot of what I'm seeing out of Google Cloud. You want to talk about objectivity, I feel the same way about Oracle Cloud.Dunking on Oracle was a sport for me for a long time, but a lot of what they're doing on a technical and on a customer-approach basis in the cloud group is notable. I like it. I've been saying that for a couple of years. And I'm gratified the response from the audience seems to at least be that no one's calling me a shill. They're saying, “Oh, if you say it, it's got to be true.” It's, “Yes. Finally, I have a reputation for authenticity.” Which is great, but that's the reason I do a lot of the stuff that I do.Mark: That is a tough place to be in. So, Twitter itself is an anomaly in terms of what's going to get engagement and what isn't. Sometimes I'll tweet something that at least I think is super clever, and I'm like, “Oh, yeah. This is meaningful, sincere, clever, positive. This is about to go bananas.” And then it'll go nowhere.And then I'll tweet that I was feeling a depression coming on and that'll get a lot of engagement. Now, I'm not saying that's a bad thing. It's just, it's never what I think. I thought that the depression tweet was not going to go anywhere. I thought that one was going to be like, kind of fade into the ether, and then that is the one that gets all the engagement.And then the one about something great that I want to share, or lifting somebody else up, or celebrating somebody that doesn't go anywhere. So, it's just really hard to predict what people are going to really engage with and what's going to ring true for them.Corey: Oh, I never have any idea of how jokes are going to land on Twitter. And in the before times, I had the same type of challenge with jokes in conference talks, where there's a joke that I'll put in there that I think is going to go super well, and the audience just sits there and stares. That's okay. My jokes are for me, but after the third time trying it with different audiences and no one laughs, okay, I should keep it to myself, then. Other times just a random throwaway comment, and I find it quoted in the newspaper almost. And it's, “Oh, okay.”Mark: [laugh].Corey: You can never tell what's going to hit and what isn't.Mark: Can we talk about that though? Like—Corey: Oh, sure.Mark: Conference talking?Corey: Oh, my God, no.Mark: Conference speaking, and just how, like—I remember one time I was keynoting—well I was emceeing and I had the opening monologue. And so [crosstalk 00:17:45]—Corey: We call that a keynote. It's fine. It is—I absolutely upgrade it because people know what you're talking about when you say, “I keynoted the thing.” Do it. Own it.Mark: Yeah.Corey: It's yours.Corey: So, I was emcee and then I did the keynote. And so during the keynote rehearsals—and this is for all the academia, right, so all these different university deans, et cetera. So, in the practice, I'm telling this joke, and it is landing, everybody's laughing, blah, blah, blah. And then I get in there, and it was crickets. And in that moment, you want to panic because you're like, “Holy crap, what do I do because I was expecting to be able to ride the wave of the laughter into my next segment,” and now it's dead silent. And then just that ability to have to be quick on your feet and not let it slow you down is just really hard.Corey: This episode is sponsored by our friends at Oracle HeatWave is a new high-performance accelerator for the Oracle MySQL Database Service. Although I insist on calling it “my squirrel.” While MySQL has long been the worlds most popular open source database, shifting from transacting to analytics required way too much overhead and, ya know, work. With HeatWave you can run your OLTP and OLAP, don't ask me to ever say those acronyms again, workloads directly from your MySQL database and eliminate the time consuming data movement and integration work, while also performing 1100X faster than Amazon Aurora, and 2.5X faster than Amazon Redshift, at a third of the cost. My thanks again to Oracle Cloud for sponsoring this ridiculous nonsense.Corey: It's a challenge. It turns out that there are a number of skills that are aligned but are not the same when it comes to conference talks, and I think that is something that is not super well understood. There's the idea of, “I can get on stage in front of a bunch of people with a few loose talking points, and just riff,” that sort of an improv approach. There's the idea of, “Oh, I can get on stage with prepared slides and have presenter notes and have a whole direction and theme of what I'm doing,” that's something else entirely. But now we're doing video and the energy is completely different.I've presented live on video, I've done pre-recorded video, but in either case, you're effectively talking to the camera and there is no crowd feedback. So, especially if you'd lean on jokes like I tend to, you can't do a cheesy laugh track as an insert, other than maybe once as its own joke. You have to make sure that you can resonate and engage with folks, but there are no subtle cues from the audience like half the front row getting up and walking out. You have to figure out what it is that resonates, what it is that doesn't, why people should care. And of course, distinguishing and differentiating between this video that you're watching now and the last five Zoom meetings that you've been on that look an awful lot the same; why should you care about this talk?Mark: The hardest thing to do. I think speaking remotely became such a big challenge. So, over time it became a little easier because I found some of the value in it, but it was still much harder because of all the things that you said. What became easier was that I didn't have to go to a place. That was easier.So, I could take three different conference talks in a day for three different organizations. So, that was easier. But what was harder, just like you said, not being able to have that energy of the crowd to know when you're on point because you look for that person in the audience who's nodding in agreement, or the person who's shaking their head furiously, like, “Oh, this is all wrong.” So, you might need to clarify or slow down or—you lose all your cues, and that's just really, really hard. And I really don't like doing video pre-recorded talks because those take more energy for me than they do the even live virtual because I have to edit it and I have to make sure that take was right because I can't say, “Oh, excuse me. Well, I meant to say this.”And I guess I could leave that in there, but I'm too much of a—I love public speaking, so I put so much pressure on myself to be the best version of myself at every opportunity when I'm doing public speaking. And I think that's what makes it hard.Corey: Oh, yeah. Then you add podcasts into the mix, like this one, and it changes the entire approach. If I stumble over my words in the middle of a sentence that I've done a couple of times already, on this very show, I will stop and repeat myself because it's easier to just cut that out in post, and it sounds much more natural. They'll take out ums, ahs, stutters, and the rest. Live, you have to respond to that very differently, but pre-recorded video has something of the same problem because, okay, the audio you can cut super easily.With video, you have to sort of a smear, and it's obvious when people know what they're looking at. And, “Wait, what was that? That was odd. They blew a take.” You can cheat, which is what I tend to do, and oh, I wind up doing a bunch of slides in some of my talks because every slide transition is an excuse to cut because suddenly for a split second I'm not on the camera and we can do all kinds of fun things.But it's all these little things, and part of the problem, too, with the pandemic was, we suddenly had to learn how to be A/V folks when previously we had the good fortune slash good sense to work with people who are specialist experts in this space. Now it's, “Well, I guess I am the best boy grip today,” whate—I'm learning what that means [laugh] as we—Mark: That's right.Corey: —continue onward. Ugh. I never signed up for this, but it's the thing that happens to you instead of what you plan on. I think that's called life.Mark: Feels right. Feels right, yeah. It's just one of those things. And I'm looking forward to the time after this, when we do get back to in-person talks, and we do get to do some things. So, I have a lot of hot takes around speaking. So, I came up in Toastmasters. Are you familiar with Toastmasters at all?Corey: I very much am.Mark: Oh, yeah. Okay, so I came up in Toastmasters, and for people at home who don't know, it's kind of like a meetup where you go and you actually practice public speaking, based on these props, et cetera. For me, I learned to do things like not say ‘um' and ‘ah' on stage because there's someone in the room counting every time you do it, and then when you get that review at the end when they give you your feedback, they'll call that out. Or when you say ‘like you know,' or too many ‘and so', all these little—I think the word is disfluencies that you use that people say make you sound more natural, those are things that were coached out with me for public speaking. I just don't do those things anymore, and I feel like there are ways for you not to do it.And I tweeted that before, that you shouldn't say ‘um' and ‘ah' and have someone tell me, “Oh, no, they're a natural part of language.” And then, “It's not natural and it could freak people out.” And I was like, “Okay. I mean, you have your opinion about that.” Like, that's fine, but it's just a hot take that I had about speaking.I think that you should do lots of things when you speak. The rate that you walk back and forth, or should you be static? How much should be on your slides? People put a lot of stuff on slides, I'm like, “I don't want to read your slides. I'd rather listen to you use your slides.” I mean, I can go on and on. We should have another podcast called, “Hey, Mark talks about public speaking,” because that is one of my jams. That and supporting people who come from different paths. Those two things, I can go on for hours about.Corey: And they're aligned in a lot of respects. I agree with you on the public speaking. Focusing on the things that make you a better speaker are not that hard in most cases, but it's being aware of what you're doing. I thought I was a pretty good speaker when I had a coach for a little while, and she would stand there, “Give just the first minute of your talk.” And she's there and writing down notes; I get a minute in and it's like, “Okay, I can't wait to see what she doesn't like once I get started.” She's like, “Nope. I have plenty. That will cover us for the next six weeks.” Like, “O…kay? I guess she doesn't know what she's doing.”Spoiler she did, in fact, know what she was doing and was very good at it and my talks are better for it as a result. But it comes down to practicing. I didn't have a thing like Toastmasters when I was learning to speak to other folks. I just did it by getting it wrong a lot of times. I would speak to small groups repeatedly, and I'd get better at it in time.And I would put time-bound on it because people would sit there and listen to me talk and then the elevator would arrive at our floor and they could escape and okay, they don't listen to me publicly speaking anymore, but you find time to practice in front of other folks. I am kidding, to be clear. Don't harass strangers with public speaking talks. That was in fact a joke. I know there's at least one person in the audience who's going to hear that and take notes and think, “Ah, I'm going to do that because he said it's a good idea.” This is the challenge with being a quote-unquote, “Role model” sometimes. My role model approach is to give people guidance by providing a horrible warning of what not to do.Mark: [laugh].Corey: You've gone the other direction and that's kind of awesome. So, one of the recurring themes of this show has been, where does the next generation come from? Where do we find the next generation of engineer, of person working in cloud in various ways? Because the paths that a lot of us walked who've been in this space for a decade or more have been closed. And standing here, it sounds an awful lot like, “Oh, go in and apply for jobs with a firm handshake and a printed copy of your resume and ask to see the manager and you'll have a job before dark.”Yeah, what worked for us doesn't work for people entering the workforce today, and there have to be different paths. Bootcamps are often the subject of, I think, a deserved level of scrutiny because quality differs wildly, and from the outside if you don't know the space, a well-respected bootcamp that knows exactly what it's doing and has established long-term relationships with a number of admirable hiring entities in the space and grifter who threw together a website look identical. It's a hard problem to solve. How do you view teaching the next generation and getting them into this space, assuming that that isn't something that is morally reprehensible? And some days, I wonder if exposing this industry to folks who are new to it isn't a problem.Mark: No, good question. So, I think in general—so I am pro bootcamp. I am pro self-taught. I was not always. And that's because of personal insecurity. Let's dive into that a little bit.So, I've been writing code since I was probably around 14 because I was lucky enough to go to a high school to had a computer science program on the south side of Chicago, one school. And then when I say I was lucky, I was really lucky because the school that I went to wasn't a high resource school; I didn't go to a private school. I went to a public school that just happened that one of the professors from IIT, also worked on staff a few days a week at my school, and we could take programming classes with this guy. Total luck. And so I get into computer science that way, take AP Computer Science in high school—which is, like, the pre-college level—then I go into undergrad, then I go into grad school for computer science.So, like, as traditional of a path that you can get. So, in my mind, it was all about my sweat equity that I had put in that disqualified everybody else. So, Corey, if you come from a bootcamp, you haven't spent the time that I spent learning to code; you haven't sweat, you haven't had to bleed, you haven't tried to write a two's complement algorithm on top of your other five classes for that semester. You haven't done it, definitely you don't deserve to be here. So, that was so much of my attitude, until—until—I got the opportunity to have my mind completely blown when I got asked to teach.Because when I got to asked to teach, I thought, “Yeah, I'm going to have my way of going in there and I'm going to show them how to do it right. This is my chance to correct these coding bootcampers and show them how it goes.” And then I find these people who were born for this life. So, some of us are natural talents, some of us are people who can just acquire the talent later. And both are totally valid.But I met this one student. She was a math teacher for years in Chicago Public Schools. She's like, “I want a career change.” Comes to the program that I taught at Northwestern, does so freaking well that she ends up getting a job at Airbnb. Now, if you have to make her go back four years at university, is that window still open for her? Maybe not.Then I meet this other woman, she was a paralegal for ten years. Ten years as a paralegal was the best engineer in the program when I taught, she was the best developer we had. Before the bootcamp was over, she had already gotten the job offer. She was meant for this. You see what I'm saying?So, that's why I'm so excited because it's like, I have all these stories of people who are meant for this. I taught, and I met people that changed the way I even saw the rest of the world. I had some non-binary trans students; I didn't even know what pronouns were. I had no idea that people didn't go by he/him, she/her. And then I had to learn about they and them and still teach you code without misgendering you at the same time, right because you're in a classroom and you're rapid-fire, all right, you—you know, how about this person? How about that person? And so you have to like, it's hard to take—Corey: Yeah, I can understand async, await, and JavaScript, but somehow understanding that not everyone has the pronouns that you are accustomed to using for people who look certain ways is a bridge too far for you to wrap your head around. Right. We can always improve, we can always change. It's just—at least when I screw up async, await, I don't make people feel less than. I just make—Mark: Totally.Corey: —users feel that, “Wow, this guy has no idea how to code.” You're right, I don't.Mark: Yeah, so as I'm on my soapbox, I'll just say this. I think coding bootcamps and self-taught programs where you can go online, I think this is where the door is the widest open for people to enter the industry because there is no requirement of a degree behind this. I just think that has just really opened the door for a lot of people to do things that is life-changing. So, when you meet somebody who's only making—because we're all engineers and we do all this stuff, we make a lot of money. And we're all comfortable. When you meet somebody where they go from 40,000 to 80,000, that is not the same story for—as it is for us.Corey: Exactly. And there's an entire school of thought out there that, “Oh, you should do this for the love because it is who you are, it is who you were meant to be.” And for some people, that's right, and I celebrate and cherish those folks. And there are other folks for whom, “I got into tech because of the money.” And you know what?I celebrate and cherish those folks because that is not inherently wrong. It says nothing negative about you whatsoever to want to improve your quality of life and wanting to support your family in varying ways. I have zero shade to throw at either one of those people. And when it comes to which of those two people do I want to hire, I have no preference in either direction because both are valid and both have directions that they can think in that the other one may not necessarily see for a variety of reasons. It's fine.Mark: I wanted to be an engineering manager. You know why? Not because I loved leadership; because I wanted more money.Corey: Yes.Mark: So, I've been in the industry for quite a long time. I'm a little bit on the older side of the story, right? I'm a little bit older. You know, for me, before we got ‘staff' and ‘principal' and all this kind of stuff, it was senior software engineer and then you topped out in terms of your earning potential. But if you wanted more, you became a manager, director, et cetera.So, that's why I wanted to be a manager for a while; I wanted more money, so why is my choice to be a manager more valuable than those people who want to make more money by coming into engineering or software development? I don't think it is.Corey: So, we've talked about positivity, we've talked about dealing with unpleasant people, we've talked about technology, and then, of course, we've talked about getting up on soapboxes. Let's tie all of that together for one last topic. What is your position on open-source in cloud?Mark: I think open-source software allows us to do a lot of incredible things. And I know that's a very light, fluffy, politically correct answer, but it is true, right? So, we get to take advantage of the brains of so many different people, all the ideas and contributions of so many different people so that we can do incredible things. And I think cloud really makes the world more accessible in general because—so when I used to do websites, I had to have a physical server that I would have to, like, try to talk to my ISP to be able to host things. And so, there was a lot of barriers to entry to do things that way.Now, with cloud and open-source, I could literally pick up a tool and deploy some software to the cloud. And the tool could you open-source so I can actually see what's happening and I could pick up other tools to help build out my vision for whatever I'm creating. So, I think open-source just gives a lot of opportunity.Corey: Oh, my stars, yes. It's even far more so than when I entered the field, and even back then there were challenges. One of the most democratizing aspects of cloud is that you can work with the same technologies that giant companies are using. When I entered the workforce, it's, “Wow, you're really good with Apache, but it seems like you don't really know a whole lot about the world of enterprise storage. What's going on with that?”And the honest answer was, “Well, it turns out that on my laptop, I can compile Apache super easily, but I'm finding it hard, given that I'm new to the workforce, to afford a $300,000 SAN in my garage, so maybe we can wind up figuring out that there are other ways to do it.” That doesn't happen today. Now, you can spin something up in the cloud, use it for a little bit. You're done, turn it off, and then never again have to worry about it except over in AWS land where you get charged 22 cents a month in perpetuity for some godforsaken reason you can't be bothered to track down and certainly no one can understand because, you know, cloud billing.Mark: [laugh].Corey: But if that's the tax versus the SAN tax, I'll take it.Mark: So, what I think is really interesting what cloud does, I like the word democratization because I think about going back to—just as a lateral reference to the bootcamp thing—I couldn't get my parents to see my software when I was in college when I made stuff because it was on my laptop. But when I was teaching these bootcamp students, they all deployed to Heroku. So, in their first couple of months, the cloud was allowing them to do something super cool that was not possible in the early days when I was coming up, learning how to code. And so they could deploy to Heroku, they could use GitHub Pages, you know like, open-source still coming into play. They can use all these tools and it's available to them, and I still think to me that is mind-blowing that I would have to bring my physical laptop or desktop home and say, “Mom, look at this terminal window that's doing this algorithm that I just did,” versus what these new people can do with the cloud. It's like, “Oh, yeah, I want to build a website. I want to publish it today. Publish right now.” Like, during our conversation, we both could have probably spent up a Hello World in the cloud with very little.Corey: Well, you could have. I could have done it in some horrifying way by using my favorite database: DNS. But that's a separate problem.Mark: [laugh]. Yeah, but I go to Firebase deploy and create a quick app real quick; Firebase deploy. Boom, I'm in the cloud. And I just think that the power behind that is just outstanding.Corey: If I had to pick a single cloud provider for someone new to the field to work with, it would be Google Cloud, and it's not particularly close. Just because the developer experience for someone who has not spent ten years marinating in cloud is worlds apart from what you're going to see in almost every other provider. I take it back, it is close. Neck-and-neck in different ways is also DigitalOcean, just because it explains things; their documentation is amazing and it lets people get started. My challenge with DigitalOcean is that it's not thought of, commonly, as a tier-one cloud provider in a lot of different directions, so the utility of learning how that platform works for someone who's planning to be in the industry for a while might potentially not get them as far.But again, there's no wrong answer. Whatever interests you, whenever you have to work on, do it. The obvious question of, “What technology should I learn,” it's, “Well, the ones that the companies you know are working with,” [laugh] so you can, ideally, turn it into something that throws off money, rather than doing it in your spare time for the love of it and not reaping any rewards from it.Mark: Yeah. If people ask me what should they use it to build something? And I think about what they want to do. And I also will say, “What will get you to ship the fastest? How can you ship?”Because that's what's really important for most people because people don't finish things. You know, as an engineer, how many side projects you probably have in the closet that never saw the light of day because you never shipped. I always say to people, “Well, what's going to get you to ship?” If it's View, use View and pair that with DigitalOcean, if that's going to get you to ship, right? Or use Angular plus Google Cloud Platform if that's going to get you to ship.Use what's going to get you to ship because—if it's just your project you're trying to run on. Now, if it's a company asking me, that's a consulting question which is a different answer. We do a much more in-detail analysis.Corey: I want to thank you so much for taking the time to speak with me about, honestly, a very wide-ranging group of topics. If people want to learn more about who you are, how you think, what you're up to, where can they find you?Mark: You can always find me spreading the love, being positive, hanging out. Look, if you want to feel better about yourself, come find me on Twitter at @marktechson—M-A-R-K-T-E-C-H-S-O-N. I'm out there waiting for you, so just come on and have a good time.Corey: And we will, of course, throw links to that in the [show notes 00:36:45]. Thank you so much for your time today.Mark: Oh, it's been a pleasure. Thanks for having me.Corey: Mark Thompson, developer relations engineer at Google. 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, deranged comment that you spent several weeks rehearsing in the elevator.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Access Control
When should a startup call the FBI

Access Control

Play Episode Listen Later Sep 28, 2021 30:04


For this 11th episode of Access Control Podcast, a podcast providing practical security advice for startups, Developer Relations Engineer at Teleport Ben Arent chats with Elvis Chan. Elvis is Assistant Special Agent in charge assigned to the San Francisco FBI Field office. Chan manages a squad responsible for investigating national security cyber matters and has over 14 years of experience in the bureau.

Access Control
Securing Kubernetes

Access Control

Play Episode Listen Later Aug 26, 2021 57:35


In this eighth episode of Access Control, a podcast providing practical security advice for startups, Developer Relations Engineer at Teleport Ben Arent chats with Andrew Martin, CEO of Control Plane. Control Plane is a London-based Kubernetes consultancy. Helping architect, install, audit, and secure Kubernetes clusters using Cloud Native technologies. Andrew was previously a DevOps Lead at the UK Home office and has helped lead teams implementing high-volume critical national infrastructure projects for the UK government. We'll deep-dive into securing Kubernetes and strategies for partnering with the public sector. Andrew is co-author of O'Reilly's Hacking Kubernetes, a great book in progress (and due November 21) to better understand the Kubernetes defaults, Kubernetes threat models and how you can protect against those attacks.

Google Cloud Platform Podcast
Working with Kubernetes and KRM with Megan O'Keefe

Google Cloud Platform Podcast

Play Episode Listen Later Aug 25, 2021 35:58


This week on the podcast, we welcome guest Megan O'Keefe to talk about KRM and Kubernetes with your hosts Mark Mirchandani and Anthony Bushong. To start the show, Megan gives us a quick rundown of Kubernetes, an open-source tool to orchestrate containers and manage other GCP resources. She explains the difference between declarative and imperative to help us better understand the basics of Kubernetes. We tackle the challenges people face when beginning their Kubernetes journey and how it works with other open-source projects, like Anthos. This year, Megan and her team have been working to help developers understand the Kubernetes Resource Model, a concept that helps define how companies can organize and run clusters, enforce policies, and more for improved standardization across multiple teams. Megan explains GitOps, a deployment model for Kubernetes focusing on Git, and takes us through examples of implementation. We learn about Config Sync and how it helps with optimizing and automating GitOps. Megan goes over some other valuable tools, including Open Policy Agent and Gatekeeper, which help developers specify not just which resources are allowed, but also what kinds of things are allowed within each resource. We wrap up the show with a discussion on streamlining the development process with strategic use of Kubernetes and the help of open-source tools like Skaffold. Megan also talks about controllers like Config Connector that help with deploying to a GCP project and the things she finds most exciting about this space. Megan O'Keefe Megan O'Keefe is a Developer Relations Engineer at Google Cloud, helping developers build platforms with Kubernetes and Anthos. Cool things of the week Listen up! Google Cloud Reader reaches 50 episodes blog Private Pools Overview docs Interview Kubernetes site GKE site KRM site KRM Tutorial Demos site Build a platform with KRM: Part 1 - What's in a platform? blog Build a platform with KRM: Part 2 - How the Kubernetes resource model works blog Build a platform with KRM: Part 3 - Simplifying Kubernetes app development blog Build a platform with KRM: Part 4 - Administering a multi-cluster environment blog Build a platform with KRM: Part 5 - Manage hosted resources from Kubernetes blog I do declare! Infrastructure automation with Configuration as Data blog Multi-cluster Use Cases docs CNCF Kubernetes Overview site Anthos site Anthos Technical Overview docs Anthos Config Management site Config Sync Overview docs Guide To GitOps site Policy Controller Overview docs Kustomize site Cloud Code site Config Connector Overview docs Crossplane site Skaffold site Open Policy Agent site Backstage site What’s something cool you’re working on? Anthony shared info about GKE on the podcast last week and he’s been working on his video series on GKE cost optimization. The solutions guide and white paper are great resources for this topic.

Percona's HOSS Talks FOSS:  The Open Source Database Podcast
The Hoss Talks Foss _ Ep 30 with Derek Downey, Developer Relations Engineer - Google

Percona's HOSS Talks FOSS: The Open Source Database Podcast

Play Episode Listen Later Jul 15, 2021 33:11


Matt Yonkovit, The HOSS, talks with Google Dev Rel Engineer Derek Downey who recently joined the Google cloud team to talk about his career in the database space, learning Google Spanner, Ansible, database automation, Kubernetes, and more. Derek recently gave a talk at Percona Live entitled "Practical DB Automation Ansible", and has been active in the open source community for over 10 years.

GRTiQ Podcast
Nader Dabit - Developer Relations Engineer at Edge & Node

GRTiQ Podcast

Play Episode Listen Later Jul 9, 2021 60:01


* This episode was recorded before the announcements made by The Graph on July 8, 2021. In this episode, we spoke to Nader Dabit, Developer Relations Engineer at Edge & Node. Nader is an incredibly accomplished and well-respected voice in the developer world – with an impressive professional pedigree. Prior to joining Edge & Node, Nader was a Senior Developer Advocate at Amazon Web Services. He's also worked as a trainer and consultant to Fortune 500 companies, including the likes of Microsoft, Visa, Warner Brothers, and American Express.Nader is very active in the developer community, and has a large following on social media, with nearly 65,000 Twitter followers and tens of thousands of views on his YouTube channel.Our conversation was very broad, ranging from how he got his start as a developer, his departure from Web 2 to join Edge & Node, the publication of his recent book, and his vision for Web 3 and where The Graph fits into it all.Show NotesThe GRTiQ Podcast takes listeners inside The Graph (GRT) by interviewing members of The Graph's community and ecosystem.  Please help support this project and build the community by subscribing and leaving a review.Twitter: GRT_iQwww.GRTiQ.co

Serverless Chats
Episode #106: Building Apps on the Decentralized Web with Nader Dabit

Serverless Chats

Play Episode Listen Later Jun 21, 2021 59:04


About Nader DabitNader Dabit is a web and mobile developer, author, and Developer Relations Engineer building the decentralized future at Edge and Node. Previously, he worked as a Developer Advocate at AWS Mobile working with projects like AWS AppSync and AWS Amplify. He is also the author and editor of React Native in Action and OpenGraphQL.Nader Dabit Twitter: @dabit3Edge and Node Twitter: @edgeandnodeGraph protocol Twitter: @graphprotocolEdge and Node: edgeandnode.com Everest: everest.link YouTube: YouTube.com/naderdabitWhat is Web3? The Decentralized Internet of the Future ExplainedWatch this episode on YouTube: https://youtu.be/pSv_cCQyCPQ This episode is sponsored by CBT Nuggets and Fauna. TranscriptJeremy: Hi everyone. I'm Jeremy Daly and this is Serverless Chats. Today I am joined again by Nader Dabit. Hey Nader, thanks for joining me.Nader: Hey Jeremy. Thanks for having me.Jeremy: You are now a developer relations engineer at Edge & Node. I would love it if you could tell the listeners a little bit about yourself. I think a lot of people probably know you already, but a little bit about your background and then what Edge & Node is.Nader: Yeah, totally. My name is Nader Dabit like you mentioned, and I've been a developer for about, I guess, nine or ten years now. A lot of people might know me from my work with AWS, where I worked with the Amplify team with the front end web and mobile team, doing a lot of full stack stuff there as well as serverless. I've been working as a developer relations person, developer advocate, actually, leading the front end web and mobile team at AWS for a little over three years I was there. I was a manager for the last year and I became really, really interested in serverless while I was there. It led to me writing a book, which is Full Stack Serverless. It also just led me down the rabbit hole of managed services and philosophy and all this stuff.It's been really, really cool to learn about everything in the space. Edge & Node is my next step, I would say, in doing work and what I consider maybe a serverless area, but it's an area that a lot of people might not associate with the traditional, I would say definition of serverless or the types of companies they often associate with serverless. But Edge & Node is a company that was spun off from a team that created a decentralized API protocol, which is called the Graph protocol. And the Graph protocol started being built in 2017. It was officially launched in a decentralized way at the end of 2020. Now we are currently finalizing that migration from a hosted service to a decentralized service actually this month.A lot of really exciting things going on. We'll talk a lot about that and what all that means. But Edge & Node itself, we do support the Graph protocol, that's part of what we do, but we also build out decentralized applications ourselves. We have a couple of applications that we're building as engineers. We're also doing a lot of work within the Web3 ecosystem, which is known as the decentralized web ecosystem by investing in different people and companies and supporting different things and spreading awareness around some of the things that are going on here because it does have a lot to do with maybe the work that people are doing in the Web2 space, which would be the traditional webspace, the space that I was in before.Jeremy: Right, right. Here I am. I follow you on Twitter. Love the videos that you do on your YouTube channel. You're like a shining example of what a really good developer relations dev advocate is. You just produce so much content, things like that, and you're doing all this stuff on serverless and I'm loving it. And then all of a sudden, I see you post this thing saying, hey, I'm leaving AWS Amplify. And you mentioned something about blockchain and I'm like, okay, wait a minute. What is this that Nader is now doing? Explain to me this, or maybe explain to me and hopefully the audience as well. What is the blockchain have to do with this decentralized applications or decentralized, I guess Web3?Nader: Web3 as defined by definition, what you might see if you do some research, would be what a lot of people are talking about as the next evolution of the web as we know it. In a lot of these articles and stuff that people are trying to formalize ideas and stuff, the original web was the read-only web where we were not creators, the only creators were maybe the developers themselves. Early on, I might've gone and read a website and been able to only interact with the website by reading information. The current version that we're currently experiencing might be considered as Web2 where everyone's a creator. All of the interfaces, all of the applications that we interact with are built specifically for input. I can actually create a comment, I can upload a video, I can share stuff, and I can write to the web. And I can read.And then the next evolution, a lot of people are categorizing, yes, is Web3. It's like taking a lot of the great things that we have today and maybe improving upon those. A lot of people and everyone kind of, this is just a really, a very old discussion around some of the trade-offs that we currently make in today's web around our data, around advertising, around the way a lot of business models are created for monetization. Essentially, they all come down to the manipulation of user data and different tricks and ways to steal people's data and use that essentially to create targeted advertising. Not only does this lead to a lot of times a negative experience. I just saw a tweet yesterday that resonated a lot with me that said, "YouTube is no longer a video platform, it's now an ad platform with videos in between." And that's the way I feel about YouTube. My kids ...Jeremy: Totally.Nader: ... I have kids that use YouTube and it's interesting to watch them because they know exactly what to do when the ads come up and exactly how to time it because they're used to, ads are just part of their experience. That's just what they're used to. And it's not just YouTube, it's every site that's out there, that's a social site, Instagram, LinkedIn. I think that that's not the original vision that people had, right, for the web. I don't think this was part of it. There have been a lot of people proposing solutions, but the core fundamental problem is how these applications are engineered, but also how the applications are paid for. How do these companies pay for developers to build. It's a really complex problem that, the simplest solution is just sell ads or maybe create something like a developer platform where you're charging a weekly or monthly or yearly or something like that.I would say a lot of the ideas around Web3 are aiming to solve this exact problem. In order to do that you have to rethink how we build applications. You have to rethink how we store data. You have to rethink about how we think about identity as well, because again, how do you build an application that deals with user data without making it public in some way? Right? How do we deal with that? A lot of those problems are the things that people are thinking about and building ways to address those in this decentralized Web3 world. It became really fascinating to me when I started looking into it because I'm very passionate about what I'm doing. I really enjoy being a developer and going out and helping other people, but I always felt there was something missing because I'm sitting here and I love AWS still.In fact, I would 100% go back and work there or any of these big companies, right? Because you can't really look at a company as, in my opinion, a black or white, good or bad thing, there's companies are doing good things and bad things at the same time. For instance, at AWS, I would meet a developer, teach them something at a workshop, a year later they would contact me and be like, hey, I got my first job or I created a business, or I landed my first client. So you're actually helping improve people's lives, at the same time you're reading these articles about Amazon in the news with some of the negative stuff going on. The way that I look at it is, I can't sit there and say any company is good or bad, but I felt a lot of the applications that people were building were also, at the end goal when you hear some of these VC discussions or people raising money, a lot of the end goal for some of the people I was working with were just selling advertising.And I'm like, is this really what we're here to do? It doesn't feel fulfilling anymore when you start seeing that over and over and over. I think the really thing that fascinated me was that people are actually building applications that are monetized in a different way. And then I started diving into the infrastructure that enabled this and realized that there was a lot of similarities between serverless and how developers would deploy and build applications in this way. And it was the entry point to my rabbit hole.Jeremy: I talked to you about this and I've been reading some of the stuff that you've been putting out and trying to educate myself on some of this. It seems very much so that show Silicon Valley on HBO, right? This decentralized web and things like that, but there's kind of, and totally correct me if I'm wrong here, but I feel there's two sides of this. You've got one side that is the blockchain, that I think some people are familiar with in the, I guess in the context of cryptocurrency, right? This is a very popular use of the blockchain because you have that redundancy and you have the agreement amongst multiple places, it's decentralized. And so you have that security there around that. But there's other uses for the blockchain as well.Especially things like banking and real estate and some of those other use cases that I'd like to talk about. And then there's another side of it that is this decentralized piece. Is the decentralized piece of it like building apps? How is that related to the blockchain or are those two separate things?Nader: Yeah, absolutely. I'm a big fan of Silicon Valley. Working in tech, it's almost like every single episode resonates with you if you've been in here long enough because you've been in one of those situations. The blockchain is part of the discussion. Crypto is part of the discussion, and those things never really interested me, to be honest. I was a speculator in crypto from 2015 until now. It's been fun, but I never really looked at crypto in any other way other than that. Blockchain had a really negative, I would say, association in my mind for a long time, I just never really saw any good things that people were doing with it. I just didn't do any research, maybe didn't understand what was going on.When I started diving into it originally what really got me interested is the Graph protocol, which is one of the things that we work on at Edge & Node. I started actually understanding, why does this thing exist? Why is it there? That led me to understanding why it was there and the fact that 90% of dApps, decentralized apps in the Ethereum ecosystem are using it. And billions of queries, companies with billions of dollars in transactions are all using this stuff. I'm like, okay, this whole world exists, but why does it exist? I guess to give you an example, I guess we can talk about the Graph protocol. And there are a lot of other web, I would say Web3 or decentralized infrastructure protocols that are out there that are similar, but they all are doing similar things in the sense of how they're actually built and how they allow participation and stuff like that.When you think of something like AWS, you think of, AWS has all of these different services. I want to build an app, I need storage. I need some type of authentication layer, maybe with Cognito, and then maybe I need someplace to execute some business logic. So maybe I'll spin up some serverless functions or create an EC2 instance, whatever. You have all these building blocks. Essentially what a lot of these decentralized protocols like the Graph are doing, are building out the same types of web infrastructure, but doing so in a decentralized way. Why does that even matter? Why is that important? Well, for instance, when you live, let's say for example in another country, I don't know, in South America and outside the United States, or even in the United States in the future, you never know. Let's say that you have some application and you've said something rude about maybe the president or something like that.Let's say that for whatever reason, somebody hacks the server that you're dealing with or whatever, at the end of the day, there is a single point of failure, right? You have your data that's controlled by the cloud provider or the government can come in and they can have control over that. The idea around some of, pretty much all of the decentralized protocols is that they are built and distributed in a way that there is no single point of failure, but there's also no single point of control. That's important when you're living in areas that have to even worry about stuff like that. So maybe we don't have to worry about that as much here, but in other countries, they might.Building something like a server is not a big deal, right? With AWS, but how would you build a server and make it available for anyone in the world to basically deploy and do so in a decentralized way? I think that's the problem that a lot of these protocols are trying to solve. For the Graph in particular, if you want to build an application using data that's stored on a blockchain. There's a lot of applications out there that are basically using the blockchain for mainly, right now it's for financial, transactional reasons because a lot of the transactions actually cost a lot of money. For instance, Uniswap is one of these applications. If you want to basically query data from a blockchain, it's not as easy as querying data from a traditional server or database.For us we are used to using something like DynamoDB, or some type of SQL database, that's very optimized for queries. But on the blockchain, you're basically having these blocks that add up every time. You create a transaction, you save it. And then someone comes behind them and they save another transaction. Over time you build up this data that's aggregated over time. But let's say you want to hit that database with the, quote-unquote, database with a query and you want to retrieve data over time, or you want to have some type of filtering mechanism. You can't do that. You can't just query blockchains the way you can from a regular database. Similar to how a database basically indexes data and stores it and makes it efficient for retrieval, the Graph protocol basically does that, but for blockchain data.Anyone that wants to build an application, one of these decentralized apps on top of blockchain data has a couple of options. They can either build their own indexing server and deploy it to somewhere like AWS. That takes away the whole idea of decentralization because then you have a single point of failure again. You can query data directly from the blockchain, from your client application, which takes a very long time. Both of those are not, I would say the most optimal way to build. But also if you're building your own indexing server, every time you want to come up with a new idea also, you have to think about the resources and time that go into it. Basically, I want to come up with a new idea and test it out, I have to basically build a server index, all this data, create APIs around it. It's time-intensive.What the Graph protocol allows you to do is, as a developer you can basically define a subgraph using YAML, similar to something like cloud formation or a very condensed version of that maybe more Serverless Framework where you're defining, I want to query data from this data source, and I want to save these entities and you deploy that to the network. And that subgraph will basically then go and look into that blockchain. And will look for all the transactions that have happened, and it will go ahead and save those and make those available for public retrieval. And also, again, one of the things that you might think of is, all of this data is public. All of the data that's on the blockchain is public.Jeremy: Right. Right. All right. Let me see if I could repeat what you said and you tell me if I'm right about this. Because this was one of those things where blockchain ... you're right. To me, it had a negative connotation. Why would you use the blockchain, unless you were building your own cryptocurrency? Right. That just seemed like that's what it was for. Then when AWS comes out with QLDB or they announced that or whatever it was. I'm like, okay, so this is interesting, but why would you use it, again, unless you're building your own cryptocurrency or something because that's the only thing I could think of you would use the blockchain for.But as you said, with these blockchains now, you have highly sensitive transactions that can be public, but a real estate transaction, for example, is something really interesting, where like, we still live in a world where if Bank of America or one of these other giant banks, JPMorgan Chase or something like that gets hacked, they could wipe out financial data. Right? And I know that's backed up in multiple regions and so forth, but this is the thing where if you're doing some transaction, that you want to make sure that transaction lives forever and isn't manipulated, then the blockchain is a good place to do that. But like you said, it's expensive to write there. But it's even harder to read off the blockchain because it's that ledger, right? It's just information coming in and coming in.So event storming or if you were doing event sourcing or something that, it's that idea. The idea with these indexers are these basically separate apps that run, and again, I'm assuming that these protocols, their software, and things that you don't have to build this yourself, essentially you can just deploy these things. Right? But this will read off of the blockchain and do that aggregation for you and then make that. Basically, it caches the blockchain. Right? And makes that available to you. And that you could deploy that to multiple indexers if you wanted to. Right? And then you would have access to that data across multiple providers.Nader: Right. No single point of failure. That's exactly right. You basically deploy a very concise configuration file that defines how you want your data stored and made available. And then it goes, and it just starts at the very beginning and it queries all those blocks or reads all those blocks, saves the data in a database, and then it keeps up with additional new updates. If someone writes a new transaction after that, it also saves that and makes it available for efficient retrieval. This is just for blockchain data. This is the data layer for, but it's not just a blockchain data in the future. You can also query from IPFS, which is a file storage layer, somewhat S3. You can query from other chains other than Ethereum, which is kind of like the main chamber.In the future really what we're hoping to have is a complete API on top of all public data. Anybody that wants to have some data set available can basically deploy a subgraph and index it and then anyone can then essentially query for it. It's like when you think of public data, we're not really used to thinking of data in this way. And also I think a good thing to talk about in a moment is the types of apps that you can build because you wouldn't want to store private messages on a blockchain or something like that. Right? The types of apps that people are building right now at least are not 100% in line with everything. You can't do everything I would say right now in Web3 that you can do in Web2.There are only certain types of applications, but those applications that are successful seem to be wildly successful and have a lot of people interested in them and using them. That's the general idea, is like you have this way to basically deploy APIs and the technology that we use to query is GraphQL. That was one of the reasons that I became interested as well. Right now the main data sources are blockchains like Ethereum, but in the future, we would like to make that available to other data sources as well.Jeremy: Right. You mentioned earlier too because there are apps obviously being built on this that you said are successful. And the problem though, I think right now, because I remember I speculated a little bit with Bitcoin and I bought a whole bunch of Ripple, so I'm still hanging on to it. Ripple XPR whatever, let's go. Anyways, but it was expensive to make a transaction. Right? Reading off of the blockchain itself, I think just connecting generally doesn't cost money, but if you're, and I know there's some costs with indexers and that's how that works. But in terms of the real cost, it's writing to the blockchain. I remember moving some Bitcoin at one point, I think cost me $30 to make one transaction, to move something like that.I can see if you're writing a $300,000 real estate transaction, or maybe some really large wire transfer or something that you want to record, something that makes sense where you could charge a fee of $30 or $40 in order to do that. I can't see you doing that for ... certainly not for web streaming or click tracking or something like that. That wouldn't make sense. But even for smaller things there might be writing more to it, $30 or whatever that would be ... seems quite expensive. What's the hope around that?Nader: That was one of the biggest challenges and that was one of the reasons that when I first, I would say maybe even considered this as a technology back in the day, that I would be considering as something that would possibly be usable for the types of applications I'm used to seeing. It just was like a no-brainer, like, no. I think right now, and that's one of the things that attracted me right now to some of the things that are happening, is a lot of those solutions are finally coming to fruition for fixing those sorts of things. There's two things that are happening right now that solve that problem. One of them is, they are merging in a couple of updates to the base layer, layer one, which would be considered something like Ethereum or Bitcoin. But Ethereum is the main one that a lot of the financial stuff that I see is happening.Basically, there are two different updates that are happening, I think the main one that will make this fee transactional price go down a little bit is sharding. Sharding is basically going to increase the number of, I believe nodes that are basically able to process the transactions by some number. Basically, that will reduce the cost somewhat, but I don't think it's ever going to get it down to a usable level. Instead what the solutions seem to be right now and one of the solutions that seems to actually be working, people are using it in production really recently, this really just started happening in the last couple of months, is these layer 2 solutions. There are a couple of different layer 2 solutions that are basically layers that run on top of the layer one, which would be something like Ethereum.And they treat Ethereum as the settlement layer. It's almost like when you interact with the bank and you're running your debit card. You're probably not talking to the bank directly and they are doing that. Instead, you have something like Visa who has this layer 2 on top of the banks that are managing thousands of transactions per second. And then they take all of those transactions and they settle those in an underlying layer. There's a couple different layer 2s that seem to be really working well right now in the Ethereum ecosystem. One of those is Arbitrum and then the other is I think Matic, but I think they have a different name now. Both of those seem to be working and they bring the cost of a transaction down to a fraction of a penny.You have, instead of paying $20 or $30 for a transaction, you're now paying almost nothing. But now that's still not cheap enough to probably treat a blockchain as a traditional database, a high throughput database, but it does open the door for a lot of other types of applications. The applications that you see building on layer one where the transactions really are $5 to $20 or $30 or typically higher value transactions. Things like governance, things like financial transactions, you've heard of NFTs. And that might make sense because if someone's going to spend a thousand bucks or 500 bucks, whatever ...Jeremy: NFTs don't make sense to me.Nader: They're not my thing either, the way they're being, I would say, talked about today especially, but I think in the future, the idea behind NFTs is interesting, but yeah, I'm in the same boat as you. But still to those people, if you're paying a thousand dollars for something then that 5 or 10 or 20 bucks might make sense, but it's not going to make sense if I just want to go to an e-commerce store and pay $5 for something. Right? I think that these layer 2s are starting to unlock those potential opportunities where people can start building these true financial applications that allow these transactions to happen at the same cost or actually a lot cheaper maybe than what you're paying for a credit card transaction, or even what those vendors, right? If you're running a store, you're paying percentages to those companies.The idea around decentralization comes back to this discussion of getting rid of the middleman, and a lot of times that means getting rid of the inefficiencies. If you can offload this business logic to some type of computer, then you've basically abstracted away a lot of inefficiencies. How many billions of dollars are spent every year by banks flying their people around the world and private jets and these skyscrapers and stuff. Now, where does that money come from? It comes from the consumer and them basically taking fees. They're taking money here and there. Right? That's the idea behind technology in general. They're like whenever something new and groundbreaking comes in, it's often unforeseen, but then you look back five years later and you're like, this is a no-brainer. Right?For instance Blockbuster and Netflix, there's a million of them. I don't have to go into that. I feel this is what that is for maybe the financial institutions and how we think about finance, especially in a global world. I think this was maybe even accelerated by COVID and stuff. If you want to build an application today, imagine limiting yourself to developers in your city. Unless you're maybe in San Francisco or New York, where that might still work. If I'm here in Mississippi and I want to build an application, I'm not going to just look for developers in a 30-mile radius. That is just insane. And I don't use that word mildly, it's just wild to think about that. You wouldn't do that.Instead, you want to look in your nation, but really you might want to look around the world because you now have things like Slack and Discord and all these asynchronous ways of doing work. And you might be able to find the best developer in the world for 25% or 50% of what you would typically find locally and an easy way to pay them might just be to just send them some crypto. Right? You don't have to go find out all their banking information and do all the wiring and all this other stuff. You just open your wallet, you send them the money and that's it. It's a done deal. But that's just one thing to think about. To me when I think about building apps in Web2 versus Web3, I don't think you're going to see the Facebook or Instagram use case anytime in the next year or two. I think the killer app for right now, it's going to be financial and e-commerce stuff.But I do think in maybe five years you will see someone crack that application for, something like a social media app where we're basically building something that we use today, but maybe in a better way. And that will be done using some off-chain storage solution. You're not going to be writing all these transactions again to a blockchain. You're going to have maybe a protocol like Graph that allows you to have a distributed database that is managed by one of these networks that you can write to. I think the ideas that we're talking about now are the things that really excite me anyway.Jeremy: Let's go back to GraphQL for a second, though. If you were going to build an app on top of this, and again, that's super exciting getting those transaction fees down, because I do feel every time you try to move money between banks or it's the $3 fee, if you go to a foreign ATM and you take money out of an ATM, they charge you. Everybody wants to take a cut somewhere along, and there's probably reasons for it, but also corporate jets cost money. So that makes sense as well. But in terms of the GraphQL protocol here, so if I wanted to build an application on top of it, and maybe my application doesn't write to the blockchain, it just reads from it, with one of these indexers, because maybe I'm summing up some financial transactions or something, or I've got an app we can look things up or whatever, I'm building something.I'm querying using the GraphQL, this makes sense. I have to use one of these indexers that's aggregating that data for me. But what if I did want to write to the blockchain, can I use GraphQL to do a mutation and actually write something to the blockchain? Or do I have to write to it directly?Nader: Yeah, that's actually a really, really good question. And that's one of the things that we are currently working on with the Graph. Right now if you want to write a transaction, you typically are going to be using one of these JSON RPC wallets and using some type of client library that interacts with the wallet and signs the transaction with the private key. And then that sends the transaction to the blockchain directly. And you're talking to the blockchain and you're just using something like the Graph to query. But I think what would be ideal and what we think would be ideal, is if someone could use a single technology, a single language, and a single abstraction to do everything, not only with reading and writing but also with subscriptions for real-time updates.That's where we think the whole idea for this will ultimately be, and that's what we're working on now. Right now you can only query. And if you want to write a transaction, you basically are still going to be using something like ethers.js or Web3 or one of these other libraries that allows you to sign a transaction using your wallet. But in the future and in fact, we're already building this right now as having an end-to-end GraphQL library that allows you to write transactions as well as read. That way someone just learns a single API and it's a lot easier. It would also make it easier for developers that are coming from a traditional web background to come in because there's a little bit of learning curve for understanding how to create one of these signed providers and write the transaction. It's not that much code, but it is a new way of thinking about things.Jeremy: Well I think both of us coming from the serverless space, we know that new way of thinking about things certainly can throw a wrench in the system when a new developer is trying to pick that stuff up.Nader: Yeah.Jeremy: All right. So that's the blockchain side of things with the data piece of it. I think people could wrap their head around that. I think it makes a lot of sense. But I'm still, the decentralized, the other things that you talked about. You mentioned an S3, something that's sort of an S3 type protocol that you can use. And what are some of the other ones? I think I've written some of them down here. Acash was one, Filecoin, Livepeer. These are all different protocols or services that are hosted by the indexers, or is this a different thing than the indexers? How does that work? And then how would you use that to save data, maybe save some blob, a blob storage or something like that?Nader: Let's talk about the tokenomics idea around how crypto fits into this and how it actually powers a protocol like this. And then we'll talk about some of those other protocols. How do people actually build all this stuff and do it for, are they getting paid for it? Is it free? How does that work and how does this network actually stay up? Because everything costs money, developers' time costs money, and so on and so forth. For something like the Graph, basically during the building phase of this protocol, basically, there was white papers and there was blog posts, and there was people in Discords talking about the ideas that were here. They basically had this idea to build this protocol. And this is a very typical life cycle, I would say.You have someone that comes up with an idea, they document some of it, they start building it. And the people that start building it are going to be basically part of essentially the founding team you could think of, in the sense of they're going to be having equity. Because at the end of the day, to actually launch one of these decentralized protocols, the way that crypto comes into it, there's typically some type of a token offering. The tokens need to be for a network like this, some type of utility token to keep the network running in the future. You're not just going to create some crypto and that's it like, right? I think that's the whole idea that I thought was going on when in reality, these tokens are typically used for powering the protocol.But let's say early on you have let's say 20 developers and they all build 5% of the system, whatever percentage that you want to talk about, whatever. Let's say you have these people helping out and then you actually build the thing and you want to go ahead and launch it and you have something that's working. A lot of times what people will do is they'll basically have a token offering, where they'll basically say, okay, let's go ahead and we're going to mint X number of tokens, and we're going to put these on the market and we're going to also pay these people that helped build this system, X number of tokens, and that's going to be their payment. And then they can go and sell those or keep those or trade those or whatever they would like to do.And then you have the tokens that are then put on the public market essentially. Once you've launched the protocol, you have to have tokens to basically continue to power the protocol and fund it. There are different people that interact with the protocol in different ways. You have the indexers themselves, which are basically software engineers that are deploying whatever infrastructure to something like AWS or GCP. These people are still using these cloud providers or they're maybe doing it at their house, whatever. All you basically need is a server and you want to basically run this indexer node, which is software that is open source, and you run this node. Basically, you can go ahead and say, okay, I want to start being an indexer and I want to be one of the different nodes on the network.To do that you basically buy some GRT, Graph Token, and in our case you stake it, meaning you are putting this money up to basically affirm that you are an indexer on the protocol and you are going to be accepting subgraph developers to deploy their subgraphs to your indexer. You stake that money and then when people use the API, they're basically paying money just like they might pay money to somewhere like API gateway or AppSync. Instead, they're paying money for their subgraph and that money is paid in GRT and it's distributed to the people in the ecosystem. Like me as a developer, I'm deploying the subgraph, and then if I have a million people using it, then I make some money. That's one way to use tokens in the system.Another way is basically to, as an outside person looking in, I can say, this indexer is really, really good. They know what they're doing. They're a very strong engineer. I'm going to basically put some money into their indexer and I'm basically backing them as an indexer. And then I will also share the money that comes in from the query fees. And then there are also people that are subgraph developers, which is the stuff that I've been working with mainly, where I can basically come up with a new API. I can be like, it'd be cool if I took data from this blockchain and this file system and merged it together, and I made this really cool API that people can use to build their apps with. I can deploy that. And basically, people can signal to this subgraph using tokens. And when people do that, they can say that they believe that this is a good subgraph to use.And then when people use that, I can also make money in that way. Basically, people are using tokens to be part of the system itself, but also to use that. If I'm a front end application like Uniswap and I want to basically use the Graph, I can basically say, okay, I'm going to put a thousand dollars in GRT tokens and I'm going to be using this API endpoint, which is a subgraph. And then all of the money that I have put up as someone that's using this, is going to be taken as the people start using it. Let's say I have a million queries and each query is one, 1000th of a cent, then after those million queries are up, I've spent $100 or something like that. Kind of similar to how you might pay AWS, you're now paying, you know, subgraph developers and indexers.Jeremy: Right. Okay. That makes sense. So then that's the payment method of that. So then these other protocols that get built on top of it, the Acash and Filecoin and Livepeer. So those ...Nader: They're all operating in a very similar fashion.Jeremy: Okay. All right. And so it's ...Nader: They have some type of node software that's run and people can basically run this node on some server somewhere and make it available as part of the network. And then they can use the tokens to participate. There's Filecoin for file storage. There's also IPFS, which is actually more of, it's a completely free service, but it's also not something that's as reliable as something like S3 or Filecoin. And then you have, like you mentioned, I believe Acash, which is a way to execute arbitrary code, business logic, and stuff like that. You have Ceramic Network, which is something that you can use for authentication. You have Livepeer which is something you use for live streaming. So you have all these ideas, these decentralized services fitting in these different niches.Jeremy: Right, right. Okay. So then now you've got a bunch of people. Now you mentioned this idea of, you could say, this is a good indexer. What about bad indexers? Right?Nader: That's a really good question.Jeremy: Yeah. You're relying on people to take data off of a public blockchain, and then you're relying on them to process it correctly and give you back good data. I'm assuming they could manipulate that data if they wanted to. I don't know why, but let's say they did. Is there a way to guarantee that you're getting the correct data?Nader: Yeah. That's a whole part of how the system works. There's this whole idea and this whole, really, really deep rabbit hole of crypto-economics and how these protocols are structured to incentivize and also disincentivize. In our protocol, basically, you have this idea of slashing and this is also a fairly known and used thing in the ecosystem and in the space. It's this idea of slashing. Basically, you incentivize people to go out and find people that are serving incorrect data. And if that person finds someone that's serving incorrect data, then the person that's serving the incorrect data is, quote-unquote, slashed. And that basically means that they're not only not going to receive the money from the queries that they were serving, but they also might lose the money that they put up to be a part of the network.I mentioned you have to actually put up money to deploy an indexer to the network, that money could also be at risk. You're very, very, very much so financially disincentivized to do that. And there's actually, again, incentives in the network for people to go and find those people. It's all-around incentives, game theory, and things like that.Jeremy: Which makes a ton of sense. That's good to know. You mentioned, you threw out the number, five years from now, somebody might build the killer app or whatever, they'll figure out some of these things. Where are we with this though? Because this sounds really early, right? There's still things that need to be figured out. Again, it's public data on the blockchain. How do you see this evolving? When do you think Web3 will be more accessible to the masses?Nader: Today people are actually building really, really interesting applications that are fitting the current technology stack, what are the things that you can build? People are already building those. But when you think about the current state of the web, where you have something like Twitter, or Facebook or Instagram, where I would say, especially maybe something like Facebook, that's extremely, extremely complex with a lot of UI interaction, a lot of private data, messages and stuff. I think to build something like that, yeah, it's going to be a couple of years. And then you might not even see certain types of applications being built. I don't think there is going to be this thing where there is no longer these types of applications. There are only these new types. I think it's more of a new type of application that people are going to be building, and it's not going to be a winner takes all just like in all tech in my opinion.I wouldn't say all but in many areas of tech where you're thinking of something as a zero-sum game where I don't think this is. But I do think that the most interesting stuff is around how Web3 essentially enables native payments and how people are going to use these native payments in interesting ways that maybe we haven't thought of yet. One of the ways that you're starting to see people doing, and a lot of venture capitalists are now investing in a lot of these companies, if you look at a lot of the companies coming out of YC and a lot of the new companies that these traditional venture capitalists are investing in, are a lot of TOMS crypto companies.When you think about the financial incentives, the things that we talked about early on, let's say you want to have the next version of YouTube and you don't want to have ads. How would that even work? Right? You still need to enable payments. But there's a couple of things that could happen there. Well, first of all, if you're building an application in the way that I've talked about, where you basically have these native payments or these native tokens that can be part of the whole process now, instead of waiting 10 years to do an IPO for an application that has been around for those 10 years and then paying back all his investors and all of those people that had been basically pulling money out their pockets to take part in.What if someone that has a really interesting idea and maybe they have a really good track record, they come out with a new application and they're basically saying, okay, if you want to own a piece of this, we're going to basically create a token and you can have ownership in it. You might see people doing these ICO's, initial coin offerings, or whatever, where basically they're offering portions of the company to anyone that wants to own it and then incentivizing people to basically use those, to govern how the application is built in the future. Let's say I own 1% of this company and a proposal is put up to do something new. I can basically say, I can use that portion of my ownership to vote on things. And then people that are speculating can say, this company is doing interesting things. I'm going to buy into it, therefore driving the price up or down.Kind of like the same way that you see the traditional stock market there, but without all of the regulation and friction that comes with that. I think that's interesting and you're already seeing companies doing that. You're not seeing the majority of companies doing that or anything like that, but you are starting to see those types of things happening. And that brings around the discussion of regulations. Is ... can you even do something like that in the United States? Well, maybe, maybe not. Does that mean people are going to start building these companies elsewhere? That's an interesting discussion as well. Right now if you want to build an application this way, you need to have some type of utility that these tokens are there for. You can't just do them purely on speculation, at least right now. But I think it's going to be interesting for sure, to watch.Jeremy: Right. And I think too that, I'm just thinking if you're a bank, right? And you maybe have a bunch of private transactions that you want to keep private. Because again, I don't even know how, I don't know how we get to private transactions on the blockchain. I could see you wanting to have some transactions that were public blockchain and some that were private and maybe a hybrid approach would make sense for some companies.Nader: I think the idea that we haven't really talked about at all is identity and how identity works compared to how we're used to identity. The way that we're used to identity working is, we basically go to a new website and we're like, this looks awesome. Let me try it out. And they're like, oh wait, we need your name, your email address, your phone number, and possibly your credit card and all this other stuff. We do that over and over and over, and over time we've now given our personal information to 500 people. And then you start getting these emails, your data has been breached, every week you get one of these emails, if you're someone like me, I don't know. Maybe I'm just signing up for too much stuff. Maybe not every week, but maybe every month or two. But you're giving out your personal data.But we're used to identity as being tied to our own physical name and address and things like that. But what if identity was something that was more abstract? And I think that that's the way that you typically see identity managed in Web3. When you're dealing with authentication mechanisms, one of the most interesting things that I think that is part of this whole discussion is this idea of a single sign-on mechanism, that you own your identity and you can transfer it across all the applications and no one else is in control of it. When you use something like an Ethereum wallet, like MetaMask, for example, it's an extension you can just download and put crypto in and basically make payments on the web with. When you create a wallet, you're given a wallet address. And the wallet address is basically created using public key cryptography, where basically you start with this private key, your public key is derived from the private key, and then your address is dropped from the public key.And when you send a transaction, you basically sign the transaction with your private key and you send your public key along with the transaction, and the person that receives that can decode the transaction with the public key to verify that that's who signed the transaction. Using this public key cryptography that only you can basically sign with your own address and your own password, it's all stored on the blockchain or in some decentralized manner. Actually in this case stored on the blockchain or it depends on how you use it really, I guess. But anyway, the whole idea here is that you completely own your identity. If you never decide to associate that identity with your name and your phone number, then who knows who's sending these transactions and who knows what's going on, because why would you need to associate your own name and phone number with all of these types of things, in these situations where you're making payments and stuff like that. Right?What is the idea of a user profile anyway, and why do you actually need it? Well, you might need it on certain applications. You might need it or want it on social network, or maybe not, or you might come up with a pseudonym, because maybe you don't want to associate yourself with whatever. You might want to in other cases, but that's completely up to you and you can have multiple wallet addresses. You might have a public wallet address that you associate your name with that you are using on social media. You might have a private wallet address that you're never associating with your name, that you're using for financial transactions. It's completely up to you, but no one can change that information. One of the applications that I recently built was called Decentralized Identity. I built it and release it a few days ago.And it's an implementation of this and it's using some of these Web3 technologies. One of them is IDX. One of them is Ceramic, which is a decentralized protocol similar to the Graph but for identity. And then it's using something called DIDs, which are decentralized identifiers, which are a way to have a completely unique ID based off of your address. And then you own the control over that. You can basically go in and make updates to that profile. And then any application across the web that you choose to use can then access that information. You're only dealing with it stored in one place. You have full control over it, at any time you can go in and delete that. You can go in and change it. No one has control over it except for you.The idea of identity is a mind-bending thing in this space because I think we're so used to just handing everybody our real names and our real phone numbers and all of our personal information and just having our fingers crossed, that we're just not used to anything else.Jeremy: It's all super interesting. You mentioned earlier about, would it be legal in the United States? I'm thinking of all these recent ransomware attacks and I think they were able to trace back some Bitcoin transaction, they were actually able to trace it back to the individual group that accepted the payment. It opens up a whole can of worms. I love this idea of being anonymous and not being tracked, but then it's also like, what could bad actors do with anonymous financial transactions and things like that? So ...Nader: There kind of has been anonymous transactional layer for a long time. Cash brought in, you can't really do a lot of illegal stuff these days without cash. So should we get rid of cash? I think with any technology ...Jeremy: No, but I mean, there's a limit though, right? You can't withdraw more than $10,000 worth of cash without the FBI being flagged and you can't deposit more, you know what I mean?Nader: You can't take a million dollars worth of Bitcoin that you've gotten from ransomware and turn it into cash either.Jeremy: That's also true. Right.Nader: Because it's all tracked on the blockchain, that's probably how they caught those people. Right? They somehow had their personal information tied to a transaction, because if you follow these transactions long enough, you're going to find some origination point. I agree though. There's definitely trade-offs with everything. I don't think I'm ever the type to argue that. There's good things and there's bad things. I think you have to look at the whole picture and decide for yourself, what you think. I'm the type that's like, let's lay out all of the ideas and let the market decide.Jeremy: Right. Yeah. I totally agree with that. All this stuff is fascinating, there is way too much more for me to learn at this point. I think my brain is filled at this point. Anything else about Edge & Node? Any cool things you're working on there or anything you want people to know?Nader: We're working on a couple of different projects. I can't really talk about some of them because they're not released yet, but we are working on a new version of something called Everest, and Everest is already out. If you want to check it out, it's at everest.link. It's basically a repository of a bunch of different applications that have already been built in the Web3 ecosystem. It also ties in a lot of the stuff that we talked about, like identity and stuff like that. You can basically sign in with your Ethereum wallet. You can basically interact with different applications and stuff, but you can also just see the types of stuff people are building. It's categorized into games, financial apps. If you've listened to this and you're like, this sounds cool, but are people actually building stuff? This is a place to see hundreds of apps that people have are already built and that are out there and successful.Jeremy: Awesome. All right. Well, listen, Nader, this was awesome. Thank you so much for sharing this with me. I know I learned a ton. I hope the listeners learned a ton. If people want to learn more about this or just follow you and keep up with what you're doing, what's the best way to do that?Nader: I would say check out Twitter, we're on Twitter @dabit3 for me, @edgeandnode for Edge & Node, and of course @graphprotocol for Graph protocol.Jeremy: Okay. And then edgeandnode.com. Your YouTube channel is just youtube.com/naderdabit, N-A-D-E-R D-A-B-I-T. And then you had an article on Web3 and I'll put it in the show notes.Nader: Yeah. Put it in the show notes. For freeCodeCamp, it's called what is Web3. And it's really a condensed version of a lot of the stuff we talked about. Maybe go into a little bit more depth around native payments and how people might build companies in the way that we've talked about here.Jeremy: Awesome. All right. Well, I will get all that stuff into the show notes. Thanks again, Nader.Nader: Thanks for having me. It was good to talk.

API The Docs Podcast
Feedback is the key! - Interview with Alex Hoffer, Developer Relations Engineer at Plaid

API The Docs Podcast

Play Episode Listen Later Jun 3, 2021 35:23


Alex Hoffer is a DevRel engineer at Plaid. Previously, she was managing the QA team at Dropbox for 6 years. At Plaid, she's been working on documentation and an overhaul of the Plaid developer docs. Developer experience is extremely important at Plaid and the docs are a big part of that. Tune in to hear more about how to create an excellent developer experience: How does a cross-functional team work together with other departments in order to improve the developer functionality? How developer experience is about product, documentation and engineering collaborating together? What is her role in the API Review Committee, which helps ensure APIs are standardized and maintain their API style guide? Docs revamp - how have they approached it, why have they done it, where is it going next? How does the entire doc editing and authorship process work at Plaid? And last but not least, how have they incorporated user feedback into the docs process! The host is Laura Vass (Editor of Developer Portals Newsletter, Co-Founder of Pronovix). Sources: https://plaid.com/blog/new-plaid-docs/ plaid.com/careers

Access Control
Offensive Security and the JavaScript Ecosystem

Access Control

Play Episode Listen Later May 27, 2021 37:54


In this fourth episode of Access Control, a podcast providing practical security advice for startups, Developer Relations Engineer at Teleport Ben Arent chats with [Adam Baldwin](https://www.linkedin.com/in/evilpacket/), aka [evilpacket](https://twitter.com/adam_baldwin), Offensive Security at Auth0. Adam was previously the VP of security at npm and founder of ^Lift Security, an application and penetration testing company focused on the JavaScript Ecosystem. Adam is a two-time DEFCON Black Badge holder.

Google Workspace Recap
Googler Max Saltonstall joins to discuss BeyondCorp, Google Docs moves to Canvas based rendering, Defined Meet code expiry timeline, Device Policy EoS for iOS 11 and more!

Google Workspace Recap

Play Episode Listen Later May 18, 2021 52:09


We recorded this week's episode a bit early this week but luckily for us, Google didn't have any last-minute updates so we got it all. We also had a Googler as our guest, Max Saltonstall is a Developer Relations Engineer at Google, and if you want to find out what he really does you have to listen to the episode! Published Releases New options to control chat history in unthreaded Google Chat rooms Google Docs will now use canvas based rendering: this may impact some Chrome extensions Google Device Policy app ending support for iOS 11 soon Additional tools for managing the transition from classic to new Google Sites Check when your Google Meet meeting codes expire to ensure smooth future meeting experiences Beyond Corp Topics Deliver zero trust on unmanaged devices with new BeyondCorp Enterprise protected profiles Chrome Insider: Managing BeyondCorp Enterprise's threat and data protection capabilities in Chrome Making access to SaaS applications more secure with BeyondCorp Enterprise BeyondCorp: A New Approach to Enterprise Security - Rory Ward and Betsy Beyer https://cloud.google.com/beyondcorp-enterprise/pricing Getting started with BeyondCorp Enterprise (GCP) Workspace Recap is the only show dedicated to and discussing all of the changes happening in Google Workspace on a weekly basis, as well as how all these changes affect our users and our businesses. Google Workspace is innovating at a breakneck pace, making it difficult to keep up and keep track. Join us each week as we discuss What’s New in Google Workspace, Upcoming Google Workspace releases, and answer your questions. Hit the subscribe button, engage with us on Twitter at @WorkspaceRecap and on our website at workspacerecap.com

PodRocket - A web development podcast from LogRocket
Firebase, development, and design in 2021 with David East

PodRocket - A web development podcast from LogRocket

Play Episode Listen Later Apr 27, 2021 28:04


In this episode, Ben and Kate talk to David East, Developer Relations Engineer at Firebase. They talk about the three tiers of the Firebase product -- Build, Release & Monitor, and Engage. They also get into design vs. development and what that means for web developers in 2021. Links https://firebase.google.com/ (https://firebase.google.com/) https://twitter.com/Firebase (https://twitter.com/Firebase) https://twitter.com/_davideast (https://twitter.com/_davideast) https://davidea.st/ (https://davidea.st/) https://www.sketch.com/ (https://www.sketch.com/) https://www.framer.com/motion/ (https://www.framer.com/motion/) https://tailwindcss.com/ (https://tailwindcss.com/) https://www.figma.com/ (https://www.figma.com/) https://podrocket.logrocket.com/different-flavors-of-frontend (https://podrocket.logrocket.com/different-flavors-of-frontend) https://css-tricks.com/the-great-divide (https://css-tricks.com/the-great-divide/) Contact us https://podrocket.logrocket.com/contact-us (https://podrocket.logrocket.com/contact-us) @LogRocket (https://twitter.com/LogRocket) brian@logrocket.com 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: David East.