Podcasts about aws amplify

En este episodio del podcast, Guille y Eli conversan con Catalina, del equipo de startups de AWS en Chile. Catalina comparte su trayectoria en la nube y profundiza en los retos y oportunidades que enfrentan las startups en sus primeras etapas. Hablaremos de escalabilidad, seguridad, optimización de costes y destacaremos herramientas como AWS Amplify. Además, Catalina detalla los programas de apoyo que ofrece AWS, incluyendo créditos, asesoramiento y recursos pensados para acelerar el crecimiento y desarrollo de productos en el ecosistema startup.Tabla de Contenidos00:56 Catalina y lecciones desde el Observatorio astronómico de Chile11:16 Diseñando nuestro MVP o MLP15:13 Deuda técnica y retos al escalar rápido21:37 Preguntas clave para evaluar una arquitectura startup27:10 ¿Vale la pena adoptar nuevas tecnologías en startups?31:51 Qué tener en cuenta al lanzar tu startup40:38 Servicios AWS que aceleran el éxito de startups42:17 Ecosistema global: cómo AWS apoya startups 45:28 Conclusiones y recursos recomendados para founders técnicosRedes Sociales InvitadaLinkedIN: https://www.linkedin.com/in/catalina-sch%C3%A4ufler-herrera-321598158/

Scott and Wes dive into the State of Frontend 2024 Survey, breaking down the latest trends, tools, and frameworks shaping the developer ecosystem. Tune in as they react to hot takes on frameworks, state management, hosting, and what's next for frontend devs! Show Notes 00:00 Welcome to Syntax! 00:53 Brought to you by Sentry.io. 01:15 About the survey. Follow along! State of Frontend Survey 02:10 Frameworks. 06:15 Rendering frameworks. 07:35 State management. 09:14 Other libraries. Just: Dependency-free Utilities. 13:34 Data. Syntax Episode 453. Syntax Episode 833. 16:39 Hosting. AWS Amplify. 19:51 Continuous Integration. 21:30 Micro-frontends. 23:25 Package Managers. pnpm Link Workspace Packages. Corepack. 28:35 JS Runtimes. 29:47 Typescript. 33:13 Browser Technologies. 35:05 What is app property? 38:20 Progressive Web Apps. 40:11 Styling tools. 43:17 Testing. 45:39 Code editors. 49:02 Build tools. 49:17 Linting tools. 50:26 Operating systems. 51:17 The future trends. 54:14 Sick Picks + Shameless Plugs. Sick Picks Scott: Candle Warmer. Wes: Flighty iOS App. Shameless Plugs Scott: Syntax on Bluesky Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

J'ai compté 86 nouveautés ces deux dernières semaines, le rythme accélère, on sent que la conférence re:Invent à Las Vegas approche. Dans cet épisode vous découvrirez des nouveautés concernant le DNS (Amazon Route53), AWS AppSync et les web sockets, l'hébergement de sites web statistiques sur Amazon S3 avec AWS Amplify. On parlera aussi de macOS sur Amazon EC2 et d'un chapelet de nouveautés AWS Lambda. On passe en revue tout cela et plus encore dans le Le podcast

In this episode of the Modern Web Podcast, Rob Ocel, Danny Thompson, and Adam Rackis talk with Michael Liendo, Senior Developer Advocate at AWS, about building practical AI applications and tackling challenges like scalability, multimodal functionality, and cloud infrastructure choices. Michael shares insights on tools like AWS Amplify and DynamoDB, discusses strategies for managing cloud costs, and explores the evolving role of prompt engineering. Michael previews his upcoming talks at AWS re:Invent on AI and scalable B2B SaaS applications. Chapters 00:00 - Introduction and Guest Welcome 01:30 - Talking Weather and Life in the Midwest 03:00 - Exploring Generative AI and Practical Applications 06:45 - Navigating Cloud Costs and Scalability Considerations 08:30 - Maintaining Creativity and Customization with AI 11:00 - Managed Services vs. On-Prem Infrastructure Debate 15:30 - Choosing a Tech Stack for Side Projects and Startups 18:45 - Learning Cloud: Paths for Full-Stack Cloud Development 22:30 - The Role of Cloud Certifications in Today's Market 26:00 - Preview of Michael's Upcoming Talks at AWS re:Invent 32:00 - Where to Find Michael Online Follow Michael Liendo on Social Media Twitter: https://x.com/focusotter Linkedin: https://www.linkedin.com/in/focusotter/ Sponsored by Wix Studio: wix.com/studio

Erik Hanchett, senior developer advocate at AWS Amplify, explores the world of Fullstack TypeScript. He discusses the significance of end-to-end type safety, the tools to achieve it, and delves into the benefits and functionalities of AWS Amplify. Links https://www.programwitherik.com https://x.com/erikch https://www.youtube.com/c/programwitherik https://www.linkedin.com/in/erikhanchett https://trpc.io https://orval.dev https://docs.amplify.aws We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). 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 provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Erik Hanchett.

https://codingcat.dev/podcast/cwcc-1-2-aws-amplify --- Send in a voice message: https://podcasters.spotify.com/pod/show/codingcatdev/message Support this podcast: https://podcasters.spotify.com/pod/show/codingcatdev/support

Welcome to this episode of the DevOps Toolchain podcast! Today, host Joe Colantonio and expert entrepreneur Ken Pomella dive deep into the transformative world of cloud-native technologies and AI. Ken shares his extensive wisdom on navigating the rapid pace of technological advancements, mainly focusing on impactful tools like IoT, cloud-native services, and AI. He praises AWS for its pioneering approach and offers practical advice on leveraging AWS Amplify for newcomers to the DevOps space and Bedrock Studio for those interested in AI solutions. Ken also covers the cost-effectiveness of cloud services, the intricacies of transitioning to cloud-native environments, and the immense potential AI holds in revolutionizing these spaces. Whether you're a seasoned developer or just starting out, this episode is packed with invaluable insights on the future of technology in business. So, tune in as we explore how embracing these advanced technologies can propel your projects forward! Try out SmartBear's Bugsnag for free, today. No credit card required. https://links.testguild.com/bugsnag

Wolltest du schon immer mal eine vollständig cloudbasierte Anwendung bauen, ohne dich vorher tiefgehend mit AWS beschäftigen zu müssen? Dann ist dieser Deep Dive genau richtig für dich!In dieser Folge sprechen wir über AWS Amplify und haben dafür neben Jan und Garrelt auch Constantin Gonzalez Schmitz, Principal Solutions Architect bei Amazon Web Services, im Studio.Wir besprechen die Vor- und Nachteile von AWS Amplify und warum ein gutes Architecture Pattern (wie hexagonale Architektur) trotzdem unerlässlich ist. Wir beleuchten, welche Services out of the box integriert werden können und wie mittels Amazon Bedrock auch Generative-AI-Anwendungsfälle abgedeckt werden können.Außerdem diskutieren wir anfallende Kosten, das kostenlose Nutzungskontingent und die Gründe, warum auch Entwickler:innen ein solides Verständnis vom Geschäftsmodell und Nutzungsverhalten der eigenen Anwendung haben sollten.Picks of the Day: Constantin: Perplexity – Perplexity beschreibt sich selbst als „das Schweizer Taschenmesser der Informationsbeschaffung“. Anders als herkömmliche große Sprachmodelle (LLMs), erzeugt Perplexity nicht nur Antworten aufgrund angelernten Wissens, sondern kann selbstständig Recherchen anstellen und Quellennachweise erbringen. Vielmehr als Konkurrenz zu GPT, LLaMA und den anderen Modellen, will Perplexity eine Alternative zu herkömmlichen Suchmaschinen anbieten. Garrelt: SVG Tutorial – In 25 kleinen Lektionen lernt ihr hier alles, was ihr für den grundlegenden Umgang mit SVGs in der Webentwicklung wissen müsst. Von einfachem Layout, über Gestaltung mit CSS und Interaktion mit JavaScript ist alles dabei. Der perfekte Adventskalender – auch in jeder anderen Jahreszeit! Jan Gregor: Factorio – Factorio ist eine Wirtschaftssimulation, die bereits 2016 in den Early Access startete und zuletzt ein großes Update erhielt. In diesem Spiel müsst ihr Produktionsketten, Beförderung, Forschung und Verteidigung übernehmen und könnt dazu aus einer Unmenge an Werkzeugen und Automatisierungen wählen. Jan hat das Spiel ursprünglich geschenkt bekommen, weil sein damaliger Chef und Gründer bei Shopify ein großer Factorio-Fan war. Alle, die sich für komplexe Systeme und Theory of Constraints interessieren, werden hierbei Spaß haben. Constantin: Compulsory (Martha Wells) – „Compulsory“ ist eine Kurzgeschichte von Martha Wells und Teil ihrer „Murderbot Diaries“-Reihe („Tagebuch eines Killerbots“). Die Kurzgeschichte spielt vor dem ersten Band und ist damit ein gute und kurze Vorschau auf das, was Lesende in den sieben bisher erschienen Bänden erwartet. Im Zentrum steht eine Maschine, die nach der Erlangung ihrer Selbständigkeit lieber Seifenopern im Fernsehen schauen möchte, als ihrer eigentlichen Aufgabe nachzugehen. Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback: podcast@programmier.barFolgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussione

In this episode, Steve delves into a deep and insightful conversation with Erik Hanchett from Amazon AWS. They explore a wide range of topics, from discussing the possibilities and complexities of using multiple software services for back-end development to unraveling the benefits of using services like AWS Amplify for handling multiple tasks and integrated functionalities. The conversation also touches on the development and deployment processes, local testing environment setup, language choices, and the Vue component library with connected components and theming. Erik shares his vast expertise and knowledge in the field, and the engaging dialogue offers valuable insights and recommendations for both experienced and aspiring developers.SponsorsChuck's Resume Template Raygun - Application Monitoring For Web & Mobile AppsBecome a Top 1% Dev with a Top End Devs MembershipSocialsLinkedIn: Erik Hanchett PicksErik - Apple Vision ProSteve - Why You've Never Been In A Plane CrashSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacy

AWS Morning Brief for the week of November 20, 2023 with Corey Quinn. Links: re:Quinnvent Wednesday night drinkup at Atomic Liquors Nature Walk Amazon CloudWatch Logs announces regular expression filter pattern support for Live Tail  Amazon EBS announces Snapshot Lock to protect snapshots from inadvertent or malicious deletions  Amazon MSK Serverless now supports all programming languages Amazon Time Sync Service now supports microsecond-accurate time  AWS CloudTrail Lake announces new pricing option optimized for flexible retention AWS Cost Explorer now provides more historical and granular data AWS announces IPv6 tiered VPCs and subnets AWS Lambda console now features a single pane view of metrics, logs, and traces Announcing Research and Engineering Studio on AWS  Announcing PartyRock, an Amazon Bedrock Playground Amazon Bedrock now provides access to Meta's Llama 2 Chat 13B model  Happy anniversary, Amazon CloudFront: 15 years of evolution and internet advancements New – Multi-account search in AWS Resource Explorer Introducing instance maintenance policy for Amazon EC2 Auto Scaling  The serverless attendee's guide to AWS re:Invent 2023  Amazon EKS and Kubernetes sessions at AWS re:Invent 2023  Optimize AZ traffic costs using Amazon EKS, Karpenter, and Istio Editorial Join us for a week of AWS Amplify launches 

J'ai compté 83 nouveautés ces deux dernières semaines. J'en ai retenu 7 qui j'espère sont pertinentes pour vous, les builders. Dans cet épisode, on parle de l'arrêt de EC2 Classique, de Flink managé pour vos applications data. On parle de nouvelles possibilités des Network Load Balancer et de Cloudwatch Log. Il y a une nouvelle famille d'instances EC2, les R7iz et je termine avec AWS Amplify qui vous permet maintenant de développer des flux d'authentication multi-facteurs avec les TOTP.

J'ai compté 83 nouveautés ces deux dernières semaines. J'en ai retenu 7 qui j'espère sont pertinentes pour vous, les builders. Dans cet épisode, on parle de l'arrêt de EC2 Classique, de Flink managé pour vos applications data. On parle de nouvelles possibilités des Network Load Balancer et de Cloudwatch Log. Il y a une nouvelle famille d'instances EC2, les R7iz et je termine avec AWS Amplify qui vous permet maintenant de développer des flux d'authentication multi-facteurs avec les TOTP.

Simon talks with Alberto Moedano who runs a Spanish and English YouTube channel for React Native. We talk about his journey from Unity to React Native, remote work from the USA and his experience with AWS Amplify compared to Firebase.Learn React Native - https://galaxies.devBeto Twitter: https://twitter.com/betomoedanoBeto YT English: https://www.youtube.com/@codewithbetoBeto YT Spanish: https://www.youtube.com/@codewithbeto1Code with Beto Courses: https://codewithbeto.dev/Links:NestJS: https://nestjs.com/

El domingo en 5 minutos te entrego cómo tirar del hilo de una idea y 12 recursos para developers:https://webreactiva.substack.com/embedFederica quiere feedback:https://webreactiva.dev/feedback-wr-269Queremos crear side projects que hagan algo significativo, que sean visibles y generen ingresos recurrentes o, al menos, que enriquezcan el portafolio. Este sueño developer generalmente gira en torno a resolver problemas cercanos o imitar casos de éxito con algún tipo de modificación.Con SiCode es difícil hacer las cosas (con NoCode también)Se aborda la dificultad de hacer cosas tanto con SiCode como con NoCode. Los desarrolladores buscan principalmente dos cosas: utilizar lo que ya conocen o aprender algo nuevo y revolucionario.Ejemplos en Web Reactiva podcast de programación:Programadores nómadas digitales con Robert Menetray | | Artista de circo orquestando servicios en AWS con Camilo Nevot¿Qué elegir?La elección entre plantillas, boilerplates y BaaS se presenta como un desafío.Las plantillas premium pueden ser arriesgadas, los boilerplates pueden ser difíciles de mantener y los BaaS pueden ser demasiado nuevos y sobrevalorados.Stacks que funcionanEjemplos incluyen Laravel, Django, NextJS, Firebase, AWS Amplify, nhost y Clark.Mientras tanto, solo crecemos en funcionalidadEs fácil olvidar la importancia de atraer usuarios, visitantes o incluso reclutadores. Tu producto puede ser brillante, pero si nadie lo ve, es como brillar en el desierto.Moraleja: mejor que acabarlo es lo que aprendes por el caminoEl episodio cierra con una moraleja poderosa: más allá del objetivo final de completar el producto, el aprendizaje adquirido durante el proceso es invaluable. Los proyectos pueden llevar meses y son un reto complejo, pero el verdadero éxito radica en disfrutar del camino y aprender de él.

Join us in this enlightening episode as our hosts Linda and Dave get an opportunity to dig deep into the fascinating world of gaming and cloud services with David Heidt, Senior Solutions Architect, Games for Amazon Web Services. From his transition to the cloud to his entrance into the gaming industry, David's story is one of passion, innovation, and relentless dedication. As a perimeter defense specialist for games, he tirelessly secures AWS customers' game servers against DDOS attacks, enhancing gamers' experiences worldwide. David also opens up about his innovative creation - the AWS Builder Cards, a unique collectable card game, that cleverly combines AWS Services education with enjoyable in-person gaming. In addition, the trio gives us a glimpse into their personal life and shares candid insights about parenting in a world where video games have become a quintessential part of our children's lives and the delicate balance between entertainment and discipline. Don't miss out on this dynamic and insightful conversation! David on Twitter: https://twitter.com/davidsheidt David on LinkedIn: https://www.linkedin.com/in/davidsimonheidt/ Linda on Twitter: https://twitter.com/lindavivah Linda's Website: https://lindavivah.com/ Linda on TikTok: https://www.tiktok.com/@lindavivah Linda on Instagram: https://www.instagram.com/lindavivah/ Linda's Medium: https://medium.com/@LindaVivah Dave on Twitter: https://twitter.com/thedavedev ** ALERT ** New Developer Hackathon from July 1st through July 31st, 2023! We're excited to announce the AWS Amplify hackathon in partnership with Hashnode. This is a great opportunity to build your dream app and win exciting prizes! The hackathon is open to everyone, and prizes include: $5, $5.5k worth of AWS credits, Hashnode swag, and AWS Amplify swag. *** REGISTER HERE *** https://bit.ly/julydevhack [PORTAL] AWS Builder Cards - https://aws.amazon.com/gametech/buildercards/ [VIDEO] Linda's Tok on AWS Cloud Quest - https://www.tiktok.com/@lindavivah/video/7132911650503445802 [VIDEO] AWS Cloud Quest – An Interactive Roleplaying Game - https://aws.amazon.com/training/digital/aws-cloud-quest/ [YOUTUBE] How to Play AWS Buildercards (2023) - https://www.youtube.com/watch?v=Pn6w8-abgis&ab_channel=AWSforGames Catan - Boardgame and Video Games - https://www.catan.com/ Dominion – Boardgame - https://boardgamegeek.com/boardgame/36218/dominion Clank – Deck Building Adventure Game - https://boardgamegeek.com/boardgame/201808/clank-deck-building-adventure Subscribe: Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Stitcher: https://www.stitcher.com/show/1065378 Pandora: https://www.pandora.com/podcast/aws-developers-podcast/PC:1001065378 TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

In this episode, Dave and Emily have an enlightening chat with Meet Bhagdev, Principal Product Manager for Amazon Keyspaces at AWS. Venture with us into the world of serverless Cassandra-compatible databases as we uncover the power and benefits of Amazon Keyspaces. Meet helps us understand what it's like to steer the product ship at AWS, and the journey he embarked on to reach this exciting role. He dives into a rich developer-focused discussion on how Amazon Keyspaces, with its seamless scalability and high availability, empowers developers to build high-performing applications. Learn about new possibilities created by the de-coupling of compute and storage and get up to speed on the latest multi-region replication updates. If thousands of requests per second, unlimited throughput, and boundless storage sound like your ideal playground, don't miss this episode! Meet on Twitter: https://twitter.com/meet_bhagdev Meet on LinkedIn: https://www.linkedin.com/in/meet-bhagdev/ Meet's Website: https://www.meetbhagdev.com/ Emily on Twitter: https://twitter.com/editingemily Dave on Twitter: https://twitter.com/thedavedev [BLOG] Announcing Amazon Keyspaces Multi-Region Replication - https://aws.amazon.com/blogs/database/announcing-amazon-keyspaces-multi-region-replication/ [CASE STUDY] Venmo's process of migrating to Amazon DocumentDB - https://aws.amazon.com/blogs/database/venmos-process-of-migrating-to-amazon-documentdb-with-mongodb-compatibility/ [PORTAL] Amazon Keyspaces - https://aws.amazon.com/keyspaces/ [PORTAL] Apache Cassandra - Open Source NoSQL Database - https://cassandra.apache.org [YOUTUBE] What is Amazon Keyspaces - https://www.youtube.com/watch?v=PYdLIvBHe2E [YOUTUBE] How Intuit migrated to Amazon Keyspaces - https://youtu.be/AjsKP0Key6U?t=9 ** ALERT ** New Developer Hackathon from July 1st through July 31st, 2023! We're excited to announce the AWS Amplify hackathon in partnership with Hashnode. This is a great opportunity to build your dream app and win exciting prizes! The hackathon is open to everyone, and prizes include: $5, $5.5k worth of AWS credits, Hashnode swag, and AWS Amplify swag. *** REGISTER HERE *** https://bit.ly/julydevhack Subscribe: Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Stitcher: https://www.stitcher.com/show/1065378 Pandora: https://www.pandora.com/podcast/aws-developers-podcast/PC:1001065378 TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

Welcome to the newest episode of The Cloud Pod podcast - where the forecast is always cloudy! Today your hosts Justin, Jonathan, and Matt discuss all things cloud and AI, as well as some really interesting forays into quantum computing, changes to Google domains, Google accusing Microsoft of cloud monopoly shenanigans, and the fact that Azure wants all your industry secrets. Also, Finops and all the logs you could hope for. Are your secrets safe? Better tune in and find out!  Titles we almost went with this week: The Cloud Pod Adds Domains to the Killed by Google list The Cloud Pod Whispers it's Secrets to Azure OpenAI The Cloud Pod Accuses the Cloud of Being a Monopoly The Cloud Pod Does Not Pass Go and Does Not collect $200 A big thanks to this week's sponsor: Foghorn Consulting, provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

Join us in this insightful episode as we welcome back the inimitable Brian Tarbox, an AWS Community Hero and Alexa Champion, whose expertise is steeped in over thirty years of hands-on experience in the tech industry. With an impressive track record that includes ten patents, a slew of papers under his belt, and the co-leadership of the Boston AWS Meetup, Brian's insights are nothing short of invaluable. In this lively and engaging conversation, Emily, Dave, and Brian traverse the burgeoning landscape of technological terminology, exploring how definitions and interpretations have evolved over time. Specifically, they delve into the concept of "Serverless" - a term that, like many in our industry, has undergone significant transformation since its inception. What does Serverless mean in 2023? Brian, with his deep knowledge and candid demeanor, unpacks this in a way that is both easy to grasp and thought-provoking. This episode is not just a feast for your ears, but also a metaphorical banquet, as Brian masterfully utilizes metaphors to bring clarity to these often-complex concepts. It's a lively and humorous ride through the often-puzzling labyrinth of tech jargon, punctuated by heaps of fun and laughter. So, whether you're a seasoned tech veteran or a curious newcomer, tune in to this episode and savor the knowledge-rich discussion between Emily, Dave, and Brian. Be prepared to laugh, learn, and see the tech world through a fresh lens. It's an episode you won't want to miss! Brian on LinkedIn: https://www.linkedin.com/in/briantarbox/ Brian's Website: https://briantarbox.org/ Brian's AWS Community Hero page: https://aws.amazon.com/developer/community/heroes/brian-tarbox/ Brian's Alexa Champion page: https://developer.amazon.com/en-US/alexa/champions/brian-tarbox Emily on Twitter: https://twitter.com/editingemily Dave on Twitter: https://twitter.com/thedavedev [BLOG] Brian's post for AWS Heroes - Time to Rethink Cattle vs. Pets (Serverless Edition) - https://dev.to/aws-heroes/time-to-rethink-cattle-vs-pets-serverless-5c0j [PODCAST] Episode 059 of AWS Developers Podcast – AWS CodeWhisperer with Brian Tarbox - https://open.spotify.com/episode/2IAvSYwNchzEwqqylzun4F ** ALERT ** New Developer Hackathon from July 1st through July 31st, 2023! We're excited to announce the AWS Amplify hackathon in partnership with Hashnode. This is a great opportunity to build your dream app and win exciting prizes! The hackathon is open to everyone, and prizes include: $5, $5.5k worth of AWS credits, Hashnode swag, and AWS Amplify swag. *** REGISTER HERE ***  https://bit.ly/julydevhack Subscribe: Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Stitcher: https://www.stitcher.com/show/1065378 Pandora: https://www.pandora.com/podcast/aws-developers-podcast/PC:1001065378 TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz RSS Feed: https://feeds.soundcloud.com/users/soundcloud:users:994363549/sounds.rss

Check out David's Instaboard app:https://instaboard.page/ytSHOW NOTESAws amplify 1.0https://www.reddit.com/r/FlutterDev/comments/12r158h/aws_amplify_is_announcing_v100_with_general/utm_source=share&utm_medium=ios_app&utm_name=ioscss&utm_content=1&utm_term=1KMPhttps://www.reddit.com/r/FlutterDev/comments/12lmora/kmp_versus_flutter/utm_source=share&utm_medium=ios_app&utm_name=ioscss&utm_content=1&utm_term=1SHOREBIRDhttps://shorebird.dev/CONNECT WITH US

In this episode, Brooke and Dave chat with Abdallah Shaban, Sr. Product Manager, Tech, for Amplify JS and Flutter. AWS Amplify is a complete solution that lets frontend web and mobile developers easily build, ship, and host full-stack applications on AWS, with no cloud expertise needed. Abdallah brings us up to speed on what the team has been building for developers and walks us through the new Amplify Flutter Web and Desktop Support for AWS Amplify Storage, Analytics and API Libraries. Abdallah's Twitter: https://twitter.com/AbdallahSh07 AWS Amplify's Twitter: https://twitter.com/awsamplify Brooke's Twitter: https://twitter.com/brooke_jamieson Brooke on LinkedIn: https://www.linkedin.com/in/brookejamieson/ Brooke's TikTok: https://www.tiktok.com/@brookebytes Brooke's Instagram: https://www.instagram.com/brooke.bytes/ [BLOG] Announcing Flutter Web and Desktop Support for AWS Amplify Storage, Analytics and API Libraries - https://aws.amazon.com/blogs/mobile/announcing-flutter-web-and-desktop-support-for-aws-amplify-storage-analytics-and-api-libraries/ [DISCORD] Amplify Discord Server - https://discord.gg/amplify [DOCS] AWS Amplify Documentation - https://docs.amplify.aws/ [GITHUB] AWS Amplify Github - https://github.com/aws-amplify 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

В новом эпизоде нашего подкаста мы пригласили Егора Мясникова, чтобы обсудить возможности использования Amplify в разработке приложений для iOS, Android, Flutter, Web и React Native. Мы рассмотрели основные компоненты Amplify, включая Studio, CLI, Libraries, UI Components и Web Hosting, и обсудили, как значительно они могут ускорить процесс разработки. Также мы обсудили ситуации, в которых Amplify может быть особенно полезен, и ответили на вопрос, можно ли использовать Amplify для разработки высоконагруженных систем. В конце эпизода мы рассмотрели интеграцию Figma с Amplify и порассуждали о том, могут ли дизайнеры стать кандидатами для становления full-stack developer.

In part two, Dave and Emily continue their conversation with Ali Spittel, head of developer advocacy for AWS Amplify at Amazon. Ali covers the general availability release of Amplify Studio, the history behind the service, and how it can help designer and developers work better together. She also discusses the role of developer advocacy, social media, and the trio shares some of the history behind early developer relations. As part of this conversation, Ali announced the AWS Amplify Hackathon running the entire month of September and giving developers a chance to win both cash prizes and AWS swag! If you missed it, you can listen to part one of this conversation in Episode 050. Ali on Twitter: twitter.com/ASpittel Emily on Twitter: twitter.com/editingemily Dave on Twitter: twitter.com/thedavedev [HACKATHON] AWS Amplify Hackathon - running September 1st-30th, 2022 - Win up to $1000, and AWS Free Credits! https://bit.ly/amplifyhackathon [PODCAST] Ali's Ladybug Podcast: https://www.ladybug.dev [PODCAST] AWS Developers Podcast - Episode 030 - AWS Amplify Hosting with Nikhil Swaminathan: https://soundcloud.com/awsdevelopers/episode-030-aws-amplify-hosting-with-nikhil-swaminathan [PODCAST] AWS Developers Podcast - Episode 026 - AWS AppSync with Brice Pelle: https://soundcloud.com/awsdevelopers/episode-026-aws-appsync-with-brice-pelle PODCAST] AWS Developers Podcast - Episode 020 - AWS Amplify Geo with Harshita Daddala: https://soundcloud.com/awsdevelopers/episode-020-aws-amplify-geo-with-harshita-daddala AWS Amplify on Twitter: https://twitter.com/awsamplify AWS Amplify on Github: https://github.com/aws-amplify AWS Amplify: https://docs.amplify.aws/ Amplify Discord Server: https://discord.gg/amplify 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

In this episode Emily and Dave catch up with Ali Spittel, head of developer advocacy for AWS Amplify at Amazon. Ali covers the general availability release of Amplify Studio, the history behind the service, and how it is helping designer and developers work better together. She also covers how the Amplify team works directly with the community to shape the product, and announces the AWS Amplify Hackathon. This hackathon will be running the entire month of September and giving developers a chance to win both cash prizes and AWS swag! Ali on Twitter: twitter.com/ASpittel Emily on Twitter: twitter.com/editingemily Dave on Twitter: twitter.com/thedavedev [HACKATHON] AWS Amplify Hackathon - running September 1st-30th, 2022 - Win up to $1000, and AWS Free Credits! https://bit.ly/amplifyhackathon [PODCAST] Ali's Ladybug Podcast: https://www.ladybug.dev [PODCAST] AWS Developers Podcast - Episode 030 - AWS Amplify Hosting with Nikhil Swaminathan: https://soundcloud.com/awsdevelopers/episode-030-aws-amplify-hosting-with-nikhil-swaminathan [PODCAST] AWS Developers Podcast - Episode 026 - AWS AppSync with Brice Pelle: https://soundcloud.com/awsdevelopers/episode-026-aws-appsync-with-brice-pelle PODCAST] AWS Developers Podcast - Episode 020 - AWS Amplify Geo with Harshita Daddala: https://soundcloud.com/awsdevelopers/episode-020-aws-amplify-geo-with-harshita-daddala AWS Amplify on Twitter: https://twitter.com/awsamplify AWS Amplify on Github: https://github.com/aws-amplify AWS Amplify: https://docs.amplify.aws/ Amplify Discord Server: https://discord.gg/amplify 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

Listen to AWS.fm: https://aws.fm/episodes/episode-25-shawn-swyx-wangShawn joins Adam to discuss Amplify and its place in the developer ecosystem, whether we should care about Cloudflare, yet, and how to cope with the anxiety that can come with being extremely online. Also, it sounds like Adam is a tech bro and he's NOT happy about it.TranscriptAdam Elmore: Hey, everyone. Welcome to AWS FM, a podcast with guests from around the AWS community. I'm your host, Adam Elmore. And today, I'm joined by Shawn Swyx Wang. Hi, Shawn.Shawn Wang: Hey, Adam. How's it going?Adam Elmore: It's going well. I've been extremely excited. I've said this on a ton of podcasts, that I'm excited to get on with a guest, but this has been a long time because before I took my break, I was going to get on with you. Took a big, long break, and I've finally got you on. You're somebody, and I'm going to say a lot of things, I'm very dramatic, but you're somebody that I really admire in the online space. You have this ability to think about things, and distill them, and put them out there in a way that I admire greatly. I'm so excited to have you on here. It's going to be hard for me to stay on any one topic because I have just a list of questions I want to ask you, basically.Shawn Wang: [inaudible 00:00:52].Adam Elmore: First, could you tell everyone on this show who you are, just the short version of Shawn?Shawn Wang: Yeah. So I'm Shawn, born and raised in Singapore, went to The States for college and then spent my first career in finance where I did investment banking and hedge funds. Loved the coding part because every junior finance person starts to learn to code, and didn't like the stress of the finance part, so I pivoted to tech where I was a software engineer at Two Sigma and then I was in developer relations at Netlify, AWS, Temporal, and I've just joined Airbyte as head of developer experience.Adam Elmore: Oh, I did not know you weren't still at Temporal. So Airbyte, what is Airbyte?Shawn Wang: Airbyte is a data integration company, it basically has the largest community of open-source connectors for connecting to any SaaS API source into your data warehouse. So for anyone doing data engineering, the first task that you have to do is to get data from all the different silos of data in your business. Let's say you have a Salesforce being the source of truth for customers, Stripe being the source of truth for transactions, get all of them into a single data warehouse for you to do operations on. So the goal is to have the largest community of open-source developers for connecting all the data and liberating your data from all the silos that you have in your business.Adam Elmore: And how long ago did you start? How did I miss this?Shawn Wang: A couple weeks ago. I actually have not announced it on Twitter, which is why.Adam Elmore: Oh, there you go.Shawn Wang: I like to slow play it. So when I joined Temporal, I actually waited for six months to really understand Temporal and to practice my pitch before announcing it on Twitter. And that's how I like to do things because, well, partially I want to be fully up to speed before I represent something publicly.Adam Elmore: Yeah. So I want to talk about that. You get very up to speed in a way that I don't see a lot of people on Twitter. I don't see them understand things in the way that you do. So you obviously write, your blog is a huge source of information for me, and I've enjoyed it quite a lot, but it's not just that you write, it's the way you think about things. Does that come from your finance, your analytical background in finance, or were you like that before, your ability to see the whole forest, take in the way things are trending and the way things are moving, put it all together and distill it into these wonderful articles? Where does that come from?Shawn Wang: Oh, so first of all, thanks for the very kind words. I don't hear back from my readers that often, so it's really nice when I get to talk to someone like this. So yeah, I would say a lot of this stuff is actually from my finance days. This is the kind of analysis that you would have to do when you do an investment report or investment research on any stock or any industry. You want to get a perspective of what's going on, what the trends are, who the major players are, and form an opinion on where things are going. And I think taking that finance mindset into the bets I have, in terms of technologies, whether or not it's for using them personally in my personal stack or for joining them as a startup employee, I think is extremely underrated. And it's something I'm trying to model and hopefully teach people someday.Shawn Wang: Although I'm not sure about the teaching part, because if I say like, "Get rich by doing investment analysis stock on early stage startups," I would feel like a hustler. So maybe not that, but I just do like engaging in that. And probably it's an exercise for me to think things through clearly by writing it down. And I also get a lot of feedback from that, so I actually improve and learn a lot by learning in public. And that's the other thing that I am pretty well known for, so this is the application of the general purpose learning in public principle.Adam Elmore: Yeah. No, and I love your learning in public article. I hope more people see how you break down systems and the world around us and distill it. I hope more people do that because I'd love to have more sources of that kind of information. It's really fascinating and that's a lot of what I want to talk about today is your opinions on the future and where certain things are headed. First, I want to talk, you did work at AWS. How long were you at AWS?Shawn Wang: A year. AWS Amplify.Adam Elmore: Yeah. So I'd love to know, I guess what it was like working at AWS, what you took from that, but also more broadly, I want to get into Amplify and where it fits. You sort of live in that intersection. I feel like web, and cloud, and infrastructure, where things are trending, and I want to talk Amplify's place in that, but first, what was your role there like at AWS, at Amplify?Shawn Wang: Yeah, I was a senior dev advocate at Amplify, basically doing demos and talks for Amplify. And the fun thing about working at Amplify is that you are essentially also a developer advocate for all the underlying services. So amplify is essentially a roll up of DynamoDB, API Gateway, AWS AppSync, even file storage like S3. You could do some demos with that. And I did, I made like a DIY Dropbox clone. But it's focus on front-end engineers. And I think that was the first time that AWS had ever made a dedicated arm or products for front-end engineers. And it turned out to be a really good bet because AWS Amplify was one of the fastest growing AWS services, at least during the time that I was there. So I thought it was just really compelling to try it out and obviously everyone has very high regard for AWS. There's a bunch of services that I only experienced on the inside and I only learned about once I got on the inside, and I thought that was really interesting as well.Shawn Wang: A few things I'll point out. I really loved the AWS interview process, actually. I felt like it was very rigorous and I definitely haven't had as rigorous a process anywhere else. And they really got a good look at every single part of me before they made the decision. And fortunately for me, it was a unanimous, good decision, but I felt challenged. I felt like there was a lot of growth that I took away from that process as well. So I highly recommend going through it, even if you don't necessarily take the job.Shawn Wang: And once you're in, I think the other practice I really like was the weekly business reviews. Not everyone gets to be a part of, but I was, and essentially you have a P&L from the central AWS finance team that week to week tells you how well you're doing or not. And the PMs in particular, they'll put up highlights, they bring up topics of discussion, and the general manager would be grilling people on. And I thought that was just a fun way to run a business. It was a little bit stressful, sometimes a little bit dramatic, but hey, it forced you to take on the issues head on instead of ignoring them for three months to a year, which I've also seen happen.Shawn Wang: So I just really appreciated that directness, and everything that you've heard about on the outside about AWS culture applies, like they'll send out the memo and the first 10 minutes of the meeting will be spend in complete silence where you just read the memo.Adam Elmore: Just read the memo. Yeah, that's real. Well, what about the leadership principle? You talked about interviewing there. Did you feel like you started to embody those? Did those really become something you valued or was it sort of like, you're just doing it because that's what Amazon cares about?Shawn Wang: There are a few things here. So I think one, people are drawn to Amazon because of leadership principles, like literally is what the interview is for. So you can't really join without already having them ingrained in you. And then second, yes, it gets brought up a lot when decisions are being made or just behaviors being modeled or discussed, especially in the performance review stuff. So I think that is useful, that is helpful, but at the same time I have problems with some of the LPs myself. "Be right a lot." What the hell is that?Adam Elmore: So what is right?Shawn Wang: Yes, exactly. What is right, what is a lot? So I think that, for example, what is underdiscussed or just not on the table, just because it comes from so much up high and has so much baggage and history with it, is that sometimes you have to try to be wrong, to take more risks. And being right a lot means that you might be more conservative than you otherwise should be. It leads to very incrementalist thinking, which is like, "All right, what is the most obvious next step? What is the low-hanging fruit? What is the short thing?" You just pick that over something that is more risky, but potentially has higher impact.Adam Elmore: Yeah. No, that makes sense. I want to, I want to shift gears a little bit and talk about Amplify. Now that you're outside of AWS, you mentioned it was sort of the first example of AWS trying to go to the front-end developer and bundle up more of a developer experience. How do you feel? And you may have information from being there about traction and things like that. How do you feel about Amplify's return on investment and is Amazon doing a good job, I guess, with Amplify in terms of trying to package up their own experience? Do you see that resonating with developers?Shawn Wang: So I think Amazon is doing a good enough job at addressing the needs of AWS customers. And that's something that is Prime first and foremost, like excels at that. Amplify could be doing a lot better at competing with the other standalone front-end developer focused startups that are out there that don't have the AWS infrastructure, which should help, but actually sometimes hurts it a little bit. So my favorite example of this is, so there's another company Begin, begin.com with Brian LeRoux. It's a four-persons company, and they also do very similar things. They deploy on top of Amazon, they are entirely serverless, they have a smaller set of offerings that they have, but their deploy speeds are in order of magnitude, faster than Amplify. They can deploy faster to AWS than Amplify can.Shawn Wang: And that's because Amplify doesn't do some of the trickery that they do, like having a cold pool ready or anything like that. When people are not married to the AWS stack, just because that's the solution, that's the technology provider or cloud that their company has picked. When you have free choice, then you come with no baggage and just being from AWS doesn't give you any home ground advantage anymore. Therefore, you have to really, really, really compete on developer experience. And that's something that Amplify still needed to work on at the time that I left.Adam Elmore: Yeah. I'm glad you brought up Begin too. I'm curious how it fits into the landscape. I've seen you mention Begin within some of your articles, like the cloud distros article I think about, I want to talk about that, but how is Begin doing? I interact with Brian on Twitter, I generally like him a lot, I like what they're building, but it is sort of a thing you have to buy into. It's like a whole different way of building applications. Do you have any sense for how they fit as a player in all of this?Shawn Wang: They're tiny. I mean, they're not a rocket ship by any means, but they absolutely solve the problem for the serverless full stack minimalist aesthetic that they're going for.Adam Elmore: Those are all things I like, so.Shawn Wang: Right down to the API calls, having an inbuilt authentication solution that when you write the serverless function, you just have the user ID and it's all done for you with cookies in the background. That's just beautiful, that's [inaudible 00:12:58] mess with cognito or anything like that. Because it's very straightforward, that is the way that I would want to build serverless applications. If I didn't have some kind of big enterprise thing requirement, which maybe it's a premature optimization to try to glom that on in the first place, which is what you're required to do with AWS Amplify.Shawn Wang: So I don't think I have enough experience to really judge, are they the right technical choice in all aspects? But I think there's just a certain aesthetic that you try to optimize for. And if you have full stack needs, if you like serverless, if you like one of everything, essentially one story solution, one queuing solution, one database solution, then Begin is the right curation for you. And then Amplify is sort of the more fully loaded solution if you want an easy way to access, let's say API Gateway, even like the... Actually just before I left, they actually launched support for serverless containers with a AWS Fargate, which is also super interesting.Adam Elmore: Oh, I didn't even know Amplify supported that.Shawn Wang: Yeah, exactly. They're just different trade offs in the spectrum, like Begin is way more opinionated than Amplify. Amplify is way more opinionated than the full set of AWS services that are possibly out there. I think they serve front-end developers well in all different respects. Yeah. I think Amplify is definitely hitting its goals and probably exceeding its goals for adoption internally. Begin could do a better job at marketing and something that I should probably try to help them on just because I'm a friend of the company and so, I mean, I just really like the philosophy, but at the same time, there are other competitors out there, like CloudFlare Workers is essentially trying to become a Jamstack or a backend-as-a-service platform, because they have Workers KV and Durable Objects. And that's a very compelling solution for a particular type of audience.Shawn Wang: And it's weird because you have to be much more specific now. Like that's the thing, you have to figure out which part of the population you are in, in order to figure out which provider is best for you. There's no such thing as one provider fits all. It's really about like, "Okay, do you like the minimalist approach? Go with Begin. Do you like the edge-first approach? Maybe go with CloudFlare. Do you like the little bit more full stack, scalable, cloudy service? Maybe go with Amplify." There's a lot there. Like, "Do you like to self-host containers? Maybe go with Fly.io or Render.com. There's just a lot of options out there, but all of them happened to be built on top of AWS, which is why we had the cloud distros thesis.Adam Elmore: Yeah. And I've consumed a lot of your content on that front, like hosted back ends. I do wonder where it's all headed. Maybe the answer is that there's just going to be a lot of options, and because there's a lot of different use cases, I guess maybe narrowing it down. Like if I really don't care about enterprise stuff or big teams, if I just care about building stuff with small teams, startups, that's where I live. Do you have any predictions, I guess, for where ideal product building is headed? Is it hosted back ends to go with your hosted front ends on Vercel or whatever else? Is it learning AWS primitives and just good and good at building stuff? How do you see that forecasting into the future?Shawn Wang: What's the alternative to hosted back ends?Adam Elmore: I guess what I do right now is build... Like I kind of use all the Amplify services, I just don't use Amplify. So I build a lot of bespoke APIs with AppSync, and Dynamo, and whatever.Shawn Wang: So because you have that knowledge, that's the best thing for you, because you already have that knowledge. Like it's not a big deal for you to spin up another service, but for others it would be, because they would be new to that and sometimes a more friendly layer that abstracts it away for them would be helpful. So it's really hard to say which is going to win just because they're all going to win in some way, but some will be more winning than others. That's kind of how I view it.Adam Elmore: Yeah. Yeah.Shawn Wang: Because at the end of the day, like cloud is such a big deal, it's such a multi decade thing. It's going to take the rest of our lives to play out. That means that the vast majority of users of cloud haven't adopted it yet, still. This late into the game, they still haven't adopted it yet.Adam Elmore: It's so hard for me to wrap my brain around. It seems like it's been so long. And when you say the rest of our lives, I don't put it in that kind of perspective. I need to calm down trying to figure out what's going to happen in the next three years. Like it doesn't matter.Shawn Wang: Yeah. Yeah. Lambda is like seven years old. This is so early. The way that this looks 40, 50 years from now is going to be so different. AWS has like a million-something customers, imagine it having 10 million. When you have order of magnitude, when we start to think in terms of orders of magnitude, you start to really sweat the small details a lot less because you're like, "Whatever. Everyone's going to win."Adam Elmore: We all win. Yeah, I guess it's true. I don't know if you've talked about this, I'm sure you've thought about it, and maybe you have written about this, but it's the idea of scarcity versus abundance mentality, I guess. It's weird because all at the same time, I agree with the sentiment that if you're on Twitter or you're very online or whatever, you should have this mentality that we can all lift each other up and we can all succeed. But then on the other hand, you've got the climate and how much can the earth sustain in terms of everything can only grow so much. I just had that thought, that sort of raw stream of consciousness. So I don't know if you've got any refined response to that. Is that sort of totally different concepts that I shouldn't conflate?Shawn Wang: What, the limits to growth thesis?Adam Elmore: Oh, yeah. I guess that's what it's called. See, I knew you'd have a name for it or something. Like the idea that we can all succeed, but at the same time, we all need to do a lot less because the planet can't succeed if we all...Shawn Wang: I mean, this is about the offline-online shift. So we can still do a lot less and cloud can still grow because the mix of what we do in-cloud versus off-cloud is still very much imbalanced. So when you do things like pay attention to an Andy Jassy Keynote, and he'll talk about like, "Oh, cloud penetration is whatever, 20%, 30%." That is how low it is and it still takes a long time for people to adopt for whatever reason, institutional or just generational, or maybe our technology's not there yet. There's still a lot that needs to be developed to serve all kinds of markets that it hasn't penetrated. My favorite stat was that online shopping went from 10% to 20% in COVID.Adam Elmore: I can't believe it's only 20%. That's actually...Shawn Wang: Exactly, right?Adam Elmore: That's bonkers.Shawn Wang: So there's some version of the future where that is 70%, which means that you still have a long, long, long, long, long way to grow for every part of e-commerce and the planet can still win by maybe more efficient sorting or less retail outlets. I don't know. I don't know about that. I think I'm much more shakier ground there, but yeah, often the online transition, I think it is a very positive thing for the planet, especially because a lot of the major clouds are committing to net zero carbon footprints. I'm not sure if AWS has actually done that yet, but definitely Microsoft and Google have done it, which means AWS will eventually do it.Adam Elmore: And I know AWS, they've launched sustainability insights and stuff recently, where you can start to see the emissions impact of the services you're spinning up. I know Google's done that for some time, but AWS is now doing that, I think.Shawn Wang: Right. But we're actually measuring it now versus not measuring it before, so whatever. This is peanuts compared to like, "All right, are we moving to electric vehicles or something?" That is way more of an interesting concern than this stuff. Like invent a better battery and that will drastically accelerate the move to solar, and that will be much more meaningful than choosing paper straws. Sweating over the carbon footprint of your EC2 instance is the developer equivalent of choosing a paper straw. Really, look, I appreciate the effort, the spirit's, the heart's in the right place, but really if you want to make an impact, go work in the big things.Adam Elmore: I'm glad you said that because this is not on my notes, this is not something I planned to talk about, but this is the thing that I feel like to make an impact, I've really struggled, I'm 15 years into my career, I've been like a software engineer mostly early in my career, then I did a startup, and then I've mostly just been doing consulting. I feel like there are more possible things I could do with my time than ever. And it's so hard for me to decide what is worth spending time on.Adam Elmore: And I guess, do you have any thoughts on senior engineers, when you get to a point in your career where you have more flexibility and more opportunities, what is the most impactful thing? I've thought about making courses, I've thought about building products and just continuing with consulting. Is there a way to split your time that you're ever going to feel good about?Shawn Wang: Probably not.Adam Elmore: Okay. It's good to know. I can stop trying to find it.Shawn Wang: Yeah. The menu options is so high. I think just figure out what gives you energy and then try to spend more of your time and day on that than stuff that takes away energy from you, so it was just a very hippie thing for me to say.Adam Elmore: Yeah. No, that seems much simpler than I'm making it.Shawn Wang: There's a concept here that I do like to share about leverage. There's an inherent tension between productivity and leverage. I think we are trained from basically our days in school, that high productivity is the goal, which is you want to have a packed calendar, you want to be doing eight different things at once. You should feel bad if your efficiency went down 10% compared to last week or whatever, and you're not meeting your OKRs or whatever. And the exact opposite to that is leverage where you want to have one thing, you want to do one thing and just have a lot of impacts come out of that.Shawn Wang: And I think there's a movement, at least in VC circles, but also in sort of tech bro circles of waking up to the idea of slack in your life, and having peace and not having so much going on, and just doing high leverage activities that help you extend your reach without you necessarily putting more hours in or being super productive. Like being unproductive is fantastic. It's actually people who cannot figure out leverage who have to try to be productive. If you can figure out leverage, then productivity doesn't matter at all.Adam Elmore: Yeah. No, that's good stuff. I think I intuitively knew that. I just have a really hard time. I feel like I'm much more seeing the tree versus the forest, so I really appreciate talking with people like you that see the broader picture. I think I have a lot of thoughts and then I read an article of yours and it helps me put words to those thoughts that I couldn't really formalize in my head.Shawn Wang: I should really write about this more, but I feel like I haven't got it yet. You see me out there, you see me doing all sorts of random crap. So I haven't internalized it fully. I haven't let go of the sort of productivity mantra. Part of that is me being very risk-averse, part of that is me being doubting myself. Definitely, the stuff that you see from me has extremely high leverage. I think, okay... The other thing is I also have second thoughts or doubts about this whole leverage thing, that's why I have a very divisive tone about VCs and tech bros, because everyone wants to be high leverage, everyone wants to do the 80-20. Nobody wants to ship stuff, they just want to tweet thoughts, and then they think they're done. Right?Adam Elmore: Yeah.Shawn Wang: That's what they think high leverage is. But really the people who get shit done, swipe to find details and take things to the finish line. And guess what? Doing that last 10% is super low leverage. Like, "Oh man, I got to fix this stupid SEO description or the OG image isn't right, let me go fix that." That kind of small little details matter for the quality of the products and for shipping things, but all the high-leverage people feel like they're above that because it's not a good use of time.Adam Elmore: So are they the high-leverage people or you're saying the people that want to be high leverage, is that the VCs and the tech bros?Shawn Wang: Yeah, exactly.Adam Elmore: What is tech bro? I feel like I probably am a tech bro, and I don't want to be a tech bro, but I feel like I'm a white male that has a podcast, so I can't escape it.Shawn Wang: Yeah. Yeah. I'm a tech bro guy. I'm sort of reluctantly in that demographic. Yeah, the tech bro is a bro that's in tech.Adam Elmore: Okay. Yeah. Well.Shawn Wang: That is fully aware. Okay. I do like to have this mis-metric. If you're fully up to speed on the latest news, the gossip, you know all the new launches and new products, you're definitely a tech bro.Adam Elmore: Okay. Okay.Shawn Wang: If nothing surprises you, you're a tech bro. If you know what AUM is, if you know what ARR is, if you know all these acronyms without even blinking, you're a tech bro. Well, the real people who get shit done out there are wonderfully blissfully ignorant. They'll be like, "What is this whole Twitter kerfuffle, what's going on? I don't know. I just completely stayed out of the loop." But you being a tech bro, you would know the blow by blow of like Elon did this, twitter did that, Elon did other thing, twitter did other thing. It doesn't matter, the stuff doesn't matter to some extent and tech bros are so involved in their own filter bubble that they don't see their own forest for the trees, so.Adam Elmore: You said Twitter. I think I've been on Twitter actively for a year or so and I don't know that I'm better for it. I don't know that like... I know that I'm very influenced by that sphere and sort of feeling like, I think that's why it's so surprising to me when I hear about cloud adoption or I hear about online shopping. It just seems like everyone lives in this little community and it's very easy to just not really remember the people that are actually around me in my local community and what life is actually like. Is there a way to balance it? Is there a way to balance being very online, being a member of this Twitter community and still keep a good grasp on the real world?Shawn Wang: I don't think I personally have figured that out a lot, but I think it's basically the developer equivalent of go touch grass, which is go outside.Adam Elmore: Yeah, yeah, yeah.Shawn Wang: Have hobbies, have kids.Adam Elmore: That I was going to say, I've got two boys and they make me be outside a whole lot, so that probably helps, I guess, somewhat.Shawn Wang: Yeah, yeah, yeah.Adam Elmore: I think the biggest thing for me just career and in terms of the always online, the tech broness, I think giving my wife the opportunity to set some boundaries around the time that I am working, I think this stage of my career, I've been able to say I'm going to work less and just seeing her role and what her life looks like and realizing how it shouldn't be this different. Like we shouldn't have such a, I don't know, huge chasm in terms of our daily life. Like I get to go enjoy what I do all day. Yeah, that's helped. We've carved out a lot of time that's like, "This is time for family." I think yeah, but my online, my work life feels very homogenous, I guess. And it could be better.Shawn Wang: For me, it's like, "All right, figure out what is probably going to make your money and focus all your attention on that. Ignore everything else. Try to stick to, okay, what can you reasonably explain to your non-technical relatives? If you can't really justify it to them, then maybe have a second thought about like, 'All right, what am I really doing here?' Am I really making the world a better place by inventing a better form of infrastructure as code? Probably not." Unless you become a billionaire by creating HashiCorp, right?Adam Elmore: Yeah, I guess it happens in that very rare instance. Yeah.Shawn Wang: Right. But it can happen. You just have to be super clear on what you're trying to do here. And just like, yeah, be super intellectually honest about like, "Look, you're you're in this for the money, whatever you work on is probably going to be irrelevant in 10 years anyway. It doesn't matter, but you're at least going to have fun, you're going to build some relationships, you're going to make some people happy, create some jobs, whatever, and then spend the rest of your time with family and friends."Adam Elmore: That was a very succinct way of wrapping up a lot of the things I needed answered. So I don't know if anyone that listens to this podcast cares about any of this. I really appreciate the conversation we just had.Shawn Wang: No, no. I think yeah, this is very real and I really appreciate you bringing it up, because I don't get a lot of chance to talk about this.Adam Elmore: Yeah. No, I live in the Ozarks, so tech literacy here is super low. I think that's where getting into the Twitter community, it was like, "I have friends now that I can talk to about technology and things I care about." But yeah, finding that balance. I think it's really very practical of you, very wise of you to point out that ultimately this stuff doesn't necessarily matter in a decade, that whatever I think I'm working on that's so important is probably more about the people, more about what I'm kind of enjoying the process along the way and that it's making a living and that we're moving a little bit forward whatever parts we touch and what other people we can be involved with. That was very nice for me to hear.Shawn Wang: I will point out one thing. So humanity is kind of moving onto this metaverse. If there's anything that's actually real about the metaverse is that you have your community online that is dissociated from your physical community. You're so into AWS, or cloud, or anything like that, and no one else around you physically is, and it's fine. And this is something that actually the crypto bros, they probably got right. So I think Balaji Srinivasan, who is one of the crypto investors at Andreessen Horowitz, he released this book recently about building a digital nation, which is really compelling, which is like, essentially there's the world of physical nations, like the ones that country that've boundaries, but then there's the digital nations, which are formed online, and you're a member of the digital nation of probably tech Twitter, whatever.Adam Elmore: Yeah, yeah.Shawn Wang: Or AWS Twitter. And I kind of liken it to the difference between friends being the family that you choose versus the family that you have is the one that you're born with.Adam Elmore: Yeah, yeah, yeah, yeah.Shawn Wang: So where you're physically located is just the nation that you're born with or the nation that you have to live in for your family reasons, but the one that you do online, that's the nation that you choose, so you're member of a different nation online. And that nation is global, it's ephemeral, it's virtual, whatever that is. But it's something that you prefer to spend your time in as compared to your physical nation.Adam Elmore: Yeah. So I feel like since getting really active in Twitter and being involved with the AWS community, even outside of Twitter, it is so global. It's helped me see the perspective of America, where I live, so differently. Just getting all those other points of view and just knowing that when I interact with someone, it's not this base assumption that they understand the world through the lens of America like I do. I very much appreciate that. I feel like I'm, if anything, becoming more and more dissociated with the country I physically live in, because I just don't interact much with people outside of these walls. I don't know if it was COVID and being in all the time. I always have been kind of an at-home person.Shawn Wang: So that is dangerous. Right? That is dangerous.Adam Elmore: Yeah. It feels dangerous. Yeah, tell me why.Shawn Wang: Well, because if you don't care about the physical environment that you're in, then it's going to degrade, it's going to diverge away from your preference.Adam Elmore: Yeah.Shawn Wang: I don't know if that's inherently bad to me. Like there's definitely a physical element to humanity that we should keep around. We are not just brains plugged into the matrix. Essentially this leads to the matrix, that we might also just be plugged into something virtual online and spend zero time on a physical environment. Most people would not like to live that way, and that means we should care about what's going on around us. And we should try to have some physical presence that we're actually proud of and enjoy. And I think that there's a tension there that I think is sort of the modern humanistic existentialism, which is like, "How much of my life should I spend online versus how much should I spend in person?" And the fact that you have to choose is just nuts.Adam Elmore: Yeah. And I think my problem, like if I'm just being honest with myself and just thinking through this, I spend about as much time, I think, in the real world, but it's just with my family, at home, it's with my neighbor, I got a neighbor that I go for walks every week with. It's like my very, very hyper local community. But what's going on in the City of Nixa? It's like 10,000 people where I live. What's the local government doing? I don't know. I have no idea. What's the State of Missouri doing? Probably stuff I don't like.Shawn Wang: Exactly. And look, this has a very real impact on us because these people are making the laws that we have to follow. And we don't have a voice because we choose not to have a voice because we choose to not care. But hey, is it really our fault when the Supreme Court or the Congress makes a law that we don't like? Well, yeah. I mean, what did you expect? You didn't spend any time investing in that part of the world. It's like, "When are we going to have a software engineer in Congress?" That's really the big question.Adam Elmore: Yeah. There's not a lot of tech representation, is there? In government in the United States.Shawn Wang: No, because everyone hates politics, they love to dunk on it, they don't want to do a thing about it, but that's kind of the problem. I don't care which side of the bench you're on, like just the politicalness because you feel like you're not a member of the physical nation, you're a member of the digital nation. That is a problem for the physical nation, because at the end of the day, that's basically a reality.Adam Elmore: Yeah. Oh, I think of that, there was that Netflix documentary. I don't even know if it was just on Netflix, but there was that social. Well, I don't even remember what it was called, it was about social media and had all these people from Facebook and other places, or ex-Facebook, talking about just this impact that the very online nature of our generation, what it's doing to our brains and all that. This all sort of ties in my mind. Like I definitely need to do some more things that are yeah, going to impact my life, my kids' lives, sort of being more involved, I guess, outside of... Like I divide my time into I'm at work and I'm on a computer all day or I'm with my family and we're out in the yard playing. It's those two things. And I make no time for anything else, but that's probably not good. Not a good, long-term solution.Adam Elmore: Okay. Now I'm getting way off the rails. AWS FM, people literally listen to this for some good AWS bits. They've turned out long ago. I do have a couple more questions here, getting back to like I'm a developer, I like building full-stack web applications and I happen to like leveraging AWS. I'm going to ask you a few things. When should I care about CloudFlare? They announce all this cool stuff and it really is genuinely cool sounding, but there's so much of a barrier to adoption, like for me to change my day to day and start using a new thing. When should I care about CloudFlare?Shawn Wang: I have the article on this, about how CloudFlare is playing Go while AWS plays chess, so I highly recommend reading that up. Essentially, CloudFlare is a really good CDN. AWS has its own. I would think you can do up comparisons of CloudFront and CloudFlare all day long, but I would say that CloudFlare probably has much more of a security focus than CloudFront has, and that by default wins you the majority of the business and it happens to be very easily adoptable because you just need to configure some DNS, just is carrying a lot of weight there and it comes to DNS.Adam Elmore: If you're asking someone in the Ozarks around me, then what's DNS, first of all?Shawn Wang: So I think it basically starts from the outside in. You want to think about CloudFlare, you think about where your user's traffic is coming in. Maybe you want to protect those with CloudFlare and then you want to come in a little bit. CloudFlare has this S3 wrapper called R2, that basically reduces a lot of your outgoing bandwidth costs. And that seems like basically a Pareto optimal win. Pareto being you're no worse off in any dimension and you're better off in one dimension, which is cost. And that's just a function of CloudFlare.Shawn Wang: Like how many points of presence does AWS have? I think in the hundreds, maybe 100, 150, something like that. CloudFlare has tens of thousands, right?Adam Elmore: Oh, okay.Shawn Wang: It's just a much better edge network than AWS has. And so they just have a fundamentally different business model. And I think once you understand that from a fundamental physics and points of presence perspective, then you're understanding, "Okay, this is what I'm getting that AWS doesn't do." It's not a straight up one-to-one competitor, it's trying to tackle the cloud problem from a different way.Shawn Wang: So you do the cloud traffic protection, then you do the sort of egress charges, which are sort of the main sticking point of AWS. Then you get into the extra stuff that CloudFlare offers for application builders. And I focus on this because I'm an application builder. CloudFlare's other offerings for security that I have no idea, security and networking that I have no idea about, particularly if you need to wire a building or an office, they have a box that's pretty sweet for everything I heard. CloudFlare One is the name of it if you want to Google it.Adam Elmore: Okay. Yeah, I do.Shawn Wang: But for application developers, CloudFlare Workers, that team is the sort of primary team that's working on that. And that is, there's edge function service that would be a big leap to adopt because they don't run Node.js, they run V8 isolates, which are taken out of the Chrome V8 engine.Adam Elmore: Is it similar to like Lambda@Edge? Like the same kind of...?Shawn Wang: No, it is not.Adam Elmore: Oh, is Lambda@Edge node?Shawn Wang: Yes.Adam Elmore: Oh, it is.Shawn Wang: Yes.Adam Elmore: It is. Now, what is it similar to? It's similar to, I guess like Middleware and Next.js, that's that same kind of a limited runtime environment?Shawn Wang: I think so. Yeah, exactly, exactly. I would say it's more limited in Lambda@Edge and it's got different costs and criteria. Basically, there's just more of the open source ecosystem that it will be incompatible with CloudFlare Workers than it would be with Lambda@Edge. And that's the thing that you need to know because you're going to use...Adam Elmore: CloudFront Functions.Shawn Wang: Ah, okay. Yeah, that's the one I keep forgetting.Adam Elmore: I don't know who's using it, but that's what I was thinking of.Shawn Wang: Right. So I used to use this only for smart redirects, like looking at the headers of a request and saying, "If you're coming in with a header indicating you're from a certain region, certain IPS, certain language, then I'm going to route you to a different location than I would normally." Only for route, but now Edge Functions are becoming so capable that you might be able to do rendering on demands instead of just routing. And that actually is unlocking a few new things because on top of that, CloudFlare also has persistence solutions with Workers KV, which is their eventually consistent store, and Workers, and Durable Objects, which is their strongly consistent store. So either one of those combined with the ability to render, means that you can actually just host a site full stack with Front on the Edge. There's no origin server, there's no region, you just have everything everywhere all at once, which is a favorite phrase that I try to sneak in.Adam Elmore: Yeah. That's super compelling.Shawn Wang: So yeah, your latencies go down from like 300 milliseconds to nine, just because you're just pinging near a cell tower or something.Adam Elmore: Yeah, that's incredible. And they've just announced, I don't remember D1 or whatever. I don't know, I can't keep track of their product names, but they have like a distributed SQL offering as well that's coming or...Shawn Wang: SQLite. Yeah.Adam Elmore: Yeah. SQLite at the edge.Shawn Wang: I mean, everything's just built on top, it's just clearly built on top of the original persistence primitive that they have. And so once they got strongly consistent and eventually consistent, those are the two dimensions that you really care about. You can build any sort of solution on that, so the SQLite offering is just built on top of that.Adam Elmore: Yeah. Okay. So I don't know if I'm going to like jump on this stuff yet, but it does sound like there is a world where I could build side projects just on CloudFlare, like stuff runs all at the edge and I don't have to build up, I guess, is the interop, like if I want to still stand up a GraphQL API in AWS, like AppSync or something, is there interoping between the two services? You said their durable storage sits on top of S3, so it's actually, you're using an S3 bucket, you're just wrapping it with a CloudFlare thing?Shawn Wang: It's a proxy.Adam Elmore: Okay. Are people building hybrid CloudFlare, oh, I know they are, hybrid CloudFlare and AWS back ends today? I think I know of a couple at least. Is that a thing you recommend?Shawn Wang: I would say yeah, there are. I'd say this is definitely on the cutting edge. You do it because you feel like [inaudible 00:42:35].Adam Elmore: It's like Twitter, where you do it and you talk about it on Twitter and then everyone thinks...Shawn Wang: It's theoretically possible, it's just like probably not in any size.Adam Elmore: Doesn't make sense yet. Okay. So I'm going to say, I don't need to care about CloudFlare yet, that's what I'm going to say based on this conversation. I mean, I'm going to keep reading the articles, but.Shawn Wang: The only thing I'll point out is don't stop there because this is what they've achieved in the past three, four years, they clearly have a roadmap, they clearly are going to keep going, and just eating the cloud from outside in, which is the name of the article. What else of the functionality can be replicated in an-edge-first way? CloudFlare is probably going to do that. And so there's a whole roadmap that just consists of looking at the AWS console and just going, "That first, that first, that first comes [inaudible 00:43:17]."Adam Elmore: Yep. Yep. Yep.Shawn Wang: And then there's a question of just what kind of application are you building and do you really need the full set of AWS services, or can you just start from the edge first? That's how disruption happens. Disruption happens by taking a section on the market that nobody cared about and making that your entire thing, and then making it so capable over time that people see no use to use the old thing, but it takes a course of what, 10, 20 years to do that because AWS has just spent the past 20 years doing that in the first place.Adam Elmore: I just don't keep those time frames in mind. Like Twitter has warped my sense of when things are coming. And when you say 10, 20 years, it's like, I don't think about anything that's coming 10, 20 years from now. I think I'm thinking what's coming in the next 18 months.Shawn Wang: Right. But that's a problem for us, because that short-term mentality stops us from betting on big trends early. And I think to build anything of significance, you have to do it for 10 years.Adam Elmore: Yeah. I got to get off Twitter, that's what I'm coming to here.Shawn Wang: I think so. I think I'm going to do it in healthy amounts. So I actually, one of my longstanding wishlist projects is to actually build a Twitter client that has a time limit.Adam Elmore: Oh, nice. Yes.Shawn Wang: [inaudible 00:44:25] Client with a time limit. If you're going to have more time, you're going to have to pay to donate to your favorite charity or something.Adam Elmore: Oh, I love it.Shawn Wang: And that's in my wishlist.Adam Elmore: Yeah. I will use it. You've got your first user if you build it.Shawn Wang: I'll just say the only reason I don't do it is because nobody trusts the Twitter API.Adam Elmore: So one more, should I care about it yet or not? Because I see Brian LeRoux talk about this quite a bit. Deno. Should I care about Deno yet?Shawn Wang: I think so. I think it's there. I think it's there. So what is Deno? Dino is sort of the new runtime that the original creator of Node.js is saying, "All right, I'm going to do this over. Node.js has been around for 10 years. I see all the flaws of it, now I'm going to start over from scratch." I was very skeptical of Deno when it first came out, but it's been two years and it's really shown a lot of progress. And I think the governance is right, the funding model was right, and the adoption is growing. What is really compelling to me about Deno, just not from a technical perspective, from a business perspective, which feeds into a technical, the business side. There are companies so Superbase and Netlify, both launched edge functions powered by Deno, which means that their biggest products shipping capability announcement of the year of 2022 was someone else's product. It was a startup that's way younger than them, but they just have the right abstraction and the right cloud service that is already functional that they're launching. So it's weird.Shawn Wang: Deno's go-to-market strategy is just waiting for other people to wake up and go, "I need this. Deno's the only supplier in the market for this. And yeah, let's just bring it on and ship it as our thing." Where it really is Deno's thing, but they're just letting other people white label them. It's that's fantastic. So I mean, from that perspective alone in the past six months, I've really changed to, from like, "Okay, Node and Deno will coexist for the foreseeable future because there's such a huge install base of Node into every incremental app will probably be built in Deno."Adam Elmore: Well, that's... Yeah. No, that's what I needed to hear. I think I there's a lot of excitement. I see it all, but it's all Twitter, so I needed to hear it face to face that it's worth digging into.Adam Elmore: One last question. We do have a couple more minutes here. Do you have thoughts on the whole macro venture capital situation and how that might impact the next 5, 10 years? And I don't know if we're entering into some tightening cycle that we've never seen anything like the last 10 years, 13, whatever years, of government injecting so much capital into the system. And if that starts going away, do you have opinions or thoughts on all these startups that are making our lives better? Like I think of DevX startups where I don't know how financially sound they are yet, they've been living off the VC. Do you have thoughts on all that?Shawn Wang: Not fully formed ones, but I can give you a quick hit.Adam Elmore: Yeah. Yeah.Shawn Wang: So how bad did it get? It got to the point, so the average price of sales ratio of a publicly traded company would be in the range of 10 to 50. That's a very wide range, meaning your market capitalization, the total value of a company is 50 times your sales. In private markets, the price of sales ratios of funding rounds, series A and B, and all that, got up to 1,000 times.Adam Elmore: Oh my God.Shawn Wang: We had 1,500 at one of the startups that I was at and I heard of one startup that was 2,500.Adam Elmore: Wow.Shawn Wang: So that was the peak in November of last year. Those days are gone, people are now asking for 100X, which is very like 10X fall, like very, very big. That's why almost nobody's raising money. So that VC market is right up, I'll say it has different impact on different stages. And this is all to do with like, "Okay, would you invest in Stripe at 95 billion when Shopify used to be 100 billion and now it's worth 20 billion?" You probably want to buy the more quality asset that's already publicly listed than the very stable asset that is at a high valuation.Shawn Wang: So this is the deal making has just gone off. Like I think at the seed stage, people are completely unaffected. I think people are cognizant of the fact that economic cycles repeat or like, this is not going to... This is a recession. We are probably already in a recession right now, we are in a tightening cycle right now, but this is probably not one of those that's just going to drag out super long. And startup take 10 years to build anyway, so why should your early stage investing be affected at all by what the current level of the S&P is? It shouldn't.Adam Elmore: Yeah. No, it's true. I mean, so much of this conversation just echoes your bias towards long term versus short term, and I should have known that coming in. I'm asking all these questions that are very much like, there's a clear answer if you just think outside of the next year.Shawn Wang: Oh, I love training people to do that.Adam Elmore: Yeah. No, it's really nice.Shawn Wang: Take a long-term perspective in the history and then project it out to the future as well, and try to make decisions on that, so.Adam Elmore: Yeah, it's sort of refreshing, especially in this sort of anxiety-ridden digital space. I feel like when you zoom out things feel a lot less pressing or anxiety-laden, I guess. I don't know. Yeah, I appreciate that.Shawn Wang: It's weird because I think that's true, but at the same time, you're only here on this earth for so long. When you zoom out, that actually reduces the available number of decisions that you can possibly make, which means that each decision goes from being a two-way door into a one-way door because you want to make more substantial decisions. Therefore, for example, when I changed jobs, it took me like two months of agonizing to finally land on something, because I could have done any number of things and I think you have to really examine your beliefs as to what the long-term trends are going to be and trade that off versus being happy in the short run.Adam Elmore: Yeah. I'm going to be trying to do that. I think I'm in the middle of the agonizing stage right now, trying to figure out what's next, but I'm going to try and think a little more long term.Shawn Wang: The thing I'll point you to, you're talking about courses and stuff like that in leverage, I'll say definitely check out Eric Jorgenson, who is the book writer for Naval Ravikant. He wrote the Almanac of Naval Ravikant, and he's trying to build up a thesis or a body of knowledge around what leverage is and what leverage means. And then the other thing I'll point you to is Nathan Barry, who's the founder of ConvertKit who talked about the letters of wealth creation and how some things are more high leverage than others, so.Adam Elmore: Thank you so much for that. Again, this podcast may just be for me, but that's okay because I got a lot out of it. Thank you so much for taking the time, Shawn.Shawn Wang: [inaudible 00:50:58].Adam Elmore: I didn't know how much I'd get in on my... I think we covered half the things I thought about talking to you about. You're just a wealth of knowledge, you're sort of a wise sage in this community and it's been so great to pick your brain. Thanks for coming on.Shawn Wang: I think we're the same age.Adam Elmore: Oh, yeah. Well yeah, you've been using your time better, I guess. You've been doing more high-leverage things or something.Shawn Wang: Yeah. Thanks for having me around, but we can talk anytime. I really enjoyed this conversation.Adam Elmore: That sounds good. Thanks, Shawn.

Hi everyone! We had a great time with Muhammed Salih Güler. Salih is a GDE for Flutter & Dart with experience in mobile app development and is currently a Senior Developer Advocate at Amazon Web Services (AWS) - Amplify. In this episode, Salih shared with us how AWS has been using Flutter! Don't miss out! Listen now and share it with your friends!Credits:

If you're a Frontend Developer that has been stuck on side projects due to a lack of backend/auth/database layers knowledge, then this show is for you! In this episode, Michael Liendo demonstrates how AWS Amplify's powerful tooling makes backend functions approachable and enjoyable to Frontend Devs.https://twitter.com/mtliendohttps://blog.focusotter.com/https://www.youtube.com/c/FocusOtterhttps://www.tacobell.com/mexican-pizzahttps://docs.amplify.aws/

Guest Mikaela Caron Youtube - MikaelaCaron Twitter - @mikaela__caron Instagram @mikaelacaron  Youtube Video - https://youtu.be/_-k97s1ZPzERelated Episodes Episode 92 - WWDC 2021 - Platforms State of the Union with Peter Witham Episode 85 - AWS Amplify with Kilo Loco Episode 120 - Xcode Tips with Dominik Hauser Episode 121 - Server-Driven UI with Mohammad Azam Episode 108 - What is Firebase with Peter Friese Episode 97 - Day One App Ideas with Mikaela Caron Episode 90 - AWS and SOTO with Adam Fowler Episode 75 - Year of the Server with Tim Condon - Part 2 Episode 49 - Vapor 4 with Tibor Bödecs Episode 48 - Alternative Backends with Kristaps Grinbergs Episode 8 - Cloud and Backend Services For Apps with Erik Gillespie Related Links Code with Chris - Getting Started with Vapor 4 WWDC 2022 - Use Xcode for server-side development Apps that use iCloud can now be transferred to another developer in the Apple Developer Program. Sponsors360iDev - Denver, CO – August 28-31, 2022 (Hybrid)Grand Hyatt Denver The Leading indie iOS/Mac (and watchOS, and tvOS) Developer conference It's all about Community and Code! Four days of hands-on training, amazing sessions, and the great community. All Swift. Available Online or In-Person Use the promo code EmpowerApps to get 20% off registration.Show Notes Do you need a backend? Why company size matters? SQL vs NoSQL Database Hosting vs MBaaS What if you have an existing dev ops or backend team?  Is CloudKit an even better option with transferrable apps? When does Vapor make sense? How can devs learn more about iOS/Swift backends?  Social MediaEmailleo@brightdigit.comGitHub - @brightdigitTwitter BrightDigit - @brightdigitLeo - @leogdionRedditLeo - /u/leogdionLinkedInBrightDigitLeoInstagram - @brightdigitPatreon - empowerappshowCreditsMusic from https://filmmusic.io"Blippy Trance" by Kevin MacLeod (https://incompetech.com)License: CC BY (http://creativecommons.org/licenses/by/4.0/)★ Support this podcast on Patreon ★

Michael Liendo joins the show to talk about his origin story, starting as a clothing model to attempting to learn iOS development, and shifting to web development before becoming a Developer Advocate. We discuss how we experience failure as a part of learning and how viewing life like a video game can help provide a bit of perspective for persevering through challenges when learning something new. Discussed Links https://aws.amazon.com/amplify/ (AWS Amplify) https://blog.focusotter.com/ (Focus Otter) https://twitter.com/mtliendo (Michael's Twitter: @mtliendo) https://codingcrystals.com/ (Coding Crystals) Previously on WebJoy https://webjoy.fm/episode/season-1-episode-1-play-until-it-pays-jason-lengstorf (S1 E1: Play Until it Pays)

Johnny and Bob discuss Glue the serverless ETL tool from AWS #dataengineering #etl #aws Connect with Johnny Youtube Channel https://www.youtube.com/c/JohnnyChivers The QuestionBank - Completely free Bank of community Questions AWS Certifications developed on AWS Amplify https://www.thequestionbank.io/ Personal Website for Contact, forum and free AWS learning resource https://johnnychivers.co.uk/ Connect with Bob Twitter - @bobhaffner LinkedIn - linkedin.com/in/bobhaffner https://twitter.com/EngSideOfData

Michael joins Adam to discuss the latest with AWS Amplify, his path from modeling to developer advocacy, and the state of full-stack development in 2022.

The Circles- product (incl integrations)- docs- content- community- UGCTALK ABOUT SVELTE SOCIETY STORYDimensions of the Circles- negative engineering? or dev exceptions- onboarding -> production -> prod-dev -> billing -?Other definitions of devx- single command do a lot -> until too magic- does what it says you would do- making some cycles faster -> esbuild 100x faster - bret victor inventing on principleFuture of Devx? integrate forward, or backward- content creation meta - video. shortgame + longgame.- backward -> going into docs, productListen to the DevX pod: https://devxpod.buzzsprout.com/1895030/10012425-the-radiating-circles-in-devx-with-swyx-head-of-developer-experience-temporalPauline: 0:00Hi, Shawn! Thank you so much for joining us for a DevX pod today. We're really excited to have you on board. I just wanted to point out this is one of those things where I tweeted about something and then someone was like, I recommend this person. And then I found you, so this is really exciting and we're going to have this awesome conversation about developer experience. Maybe for those who may not have heard of you before, can you give us a bit of an introduction on your story? What you're all about?Shawn: 0:31Yeah. Thanks for inviting me on. I'm Shawn also known as swyx online. I originally am from Singapore and, moved to the U S for college and pretty much the rest of my career and spent my first career in finance before changing careers to tech. And since I joined tech, I've been fairly known for learning in public, for speaking about reacts and serverless. And now I work as Head of Developer Experience at Temporal.Pauline: 0:55I have a follow-up question actually. What does it mean to be head of developer experience at Temporal?Shawn: 1:02It's a role that we basically, I created for myself because when they were reaching out to hire me, they didn't have something like that. And I don't think it's a common role at a startup as well. The bit of a background, which we can get into like how I got started into developer experience. I previously worked at Netlify where I originally joined as a developer advocate type person, but then when Sarah Drasner came along and started leading us as a VP she restructured the whole thing to make it more of a developer experience engineer. So I'm turning developer relations into something where you actually do a bit more engineering and are responsible for parts of the developer experience rather than talking about it. Then I continued that into AWS, whereas also a driver advocate for AWS Amplify. Well, I think for me, the role that I really thought would make the most sense to borrow was something that spans across docs and developer advocacy as well as community. And then I was also a product manager for our recent tax group STK. When you're in a smaller startup, you kind of have to wear many hats. And so, uh, this developer experience umbrella felt that the most descriptiveMike: 2:14I think you literally just covered the next two questions I wanted to go talk about. I wonder if you have any more details in terms of overall what DevX is to you?Shawn: 2:25Yeah. I've actually written some thoughts about this. I kind of think about it as a radiating circle out from the core product. And so part of this is influenced by me struggling with developer relations at Netlify and at AWS, because often there's a separate team that is responsible for docs. There's a separate team that's responsible for product. It's very hard actually, when you realize. A lot of the things that you do as a developer advocate is very it's downstream of everything else that's above you. And if they're shipped and organized by different teams, then you can get a very disjoint experience. Essentially like your impact as a developer advocate may not be as high because people don't see your stuff as much as they see the docs or the experience about it. So just think about it in terms of like, okay, you start with the core products, make sure that the product design and you get enough feedback. You make sure that API design is really solid. then you radiate out into the docs, which is your sort of first party content on how to use it. I consider docs secondary to products because the best doc's is the docs you don't have to read, right. That is intuitive experience, but still you need docs anyway. And then going out from the docs you need, you go into first party content, which is the role of a developer advocate. And that is anything that's ancillary to docs that explains the why instead of the, what or the how. But you can also dive into the what and the how as well. Like sometimes you just need to pitch the same thing, seven different ways before someone gets it. And then you go from the first party content, which is your blog posts and talks and stuff like that. It's very traditional DevRel fodder into community, which is going from one to many communication to many, to many communication. In other words, having a place where your users talk to other users and help each other out. And then the final tier is enabling third-party content, which is I think about it in terms of users writing blog posts and books, workshops and courses and tutorials about you, even posting jobs with your tool or your technology in the job description on anything like this, where it's very user initiated. I really like encouraging that because that's how you know that you start scaling developer experience beyond the sheer number of people that are working in your company because you have users working for you. But that only happens after you got all the core inner loop stuff right.Mike: 4:48I like the analogy with the radiator being in the middle and starting to do, send the heat out. I wonder, what's your take on in product developer experience, how do you make sure you don't have to ride this doc? Do you know that chapter in the documentation and how do you deal with that? Are you directly involved in the product to make certain changes that you think are more intuitive? Or how does that go?Shawn: 5:13Yeah, I think it depends on the maturity of the company. This role or this job changes very much depending on whether you're a seed stage or series B and maybe you're not a venture funded company, but depending on the maturity of the products, right? If the thing is mostly fully formed, then you have much less impact or possibility of changing things. But for me, I was directly involved in shaping every single part of the API that we shipped for the TypeScript and I wrote almost every single word of the docs. Very extremely involved! Because then after that it can flow from there to my DevRel efforts and community building efforts. So I think it really depends. The second thing it really depends on is how visual you are versus how much of a code base Platform you are. So we are very code based. In other words, we care much more about API design than user experience design or UI design. I think UI design for visual product makes sense. I think Gitpod probably more of a visual products because there's no Gitpod API. I mean, there's a config and there's no Gitpod API that I integrate into my app or anything like that. Netlify where I used to work as well. Yes, there's another Netlify config, but like the rest of the thing is just point and click. So in that sense, yes. The role of UI design, I think is very powerful. The last point I'll mentioned for you as well, is that another principle or API design principle that applies regardless of whether you're doing visual or programmatic SDK work, is that you want to try to enhance the power of a single command. So for us it was Netlify deploy or git commit, and that would create a whole new deploy preview. And that was a big revolution in front end development. There was other analogies in the CLI that we should, that we shift this well that I was involved in. But I always think about that in terms of like, okay, how do you increase the power of a single action and just pack as much as possible in there? I really liked that idea. I don't know if that is described as good developer experience, but to me, I think that really contributes to a wow moment that where you type a single command and something magical happens, because that would have typically taken many steps to accomplish.Mike: 7:27I think this is a great way to describe it. The other thing I like is when it does what you expect it to do, I think that's another huge one. You could have add whatever, but then, it does only half of the stuff or, yeah there's really good examples out there for sure. Nice.Shawn: 7:42There's a part of a developer experience, which I often talk about which is a developer exceptions. In other words, developer experience often we talk about happy paths. Like, oh, if you ask them, do I like this? Look at how amazing it is. Look at how awesome and how fast and how everything, how amazing everything is. But people in developer experience often don't talk about the, what happens when things go wrong and actually sometimes paying attention to giving you a nice remedial path when something goes wrong is actually also a really good experience that developer experience, which people don't talk. So improving observability, making sure that you don't have pricing mistakes or your pricing is predictable, at least. And doing things like having clear versioning and deprecation support policies, these all kind of boring and less headliner things that you want to ship, but it's actually very key for developer experience.Pauline: 8:35That's a really good point. You said having a wow moment and that I think is a really good explanation of what developer experience is. Why is it important to you that we have that wow moment? Why should we even care about developer experience? Why have that wow moment?Shawn: 8:54I think the wow moment is more of a marketing thing in the sense that there's a lot of developer tools out there and you need to stand out somehow and you need to get to that wow moment as quickly as possible because everyone has other things going on. They may click away if you don't get to that wow moment. so I think that's part of it. The other part, which is also like game design, in the sense that, you need to keep having rushes of endorphins to you, to make your job fun, to have the developers stay in flow and developers that stay in flow and more productive. As to why in general, should we even care about developer experience? I actually, yeah. There's a cynical view. And then there's a more genuine view. The one genuine view is that developer experience helps, developers be more productive, which helps ship more products and makes users happy and blah, blah, blah, develop a tooling companies are worth multiple billions of dollars. And if you can help a developer tools company improve the developer experience in whatever form, then that creates a lot of value for developers. That's the feel good, happy view. My secret problem with developer experiences that I don't think it's that important. Like it's, you're not curing cancer. You're not flying to Mars or anything like that. So I think it's intellectually, interesting and financially very rewarding career. But we should also be a bit humble about. Yeah. Like nobody wakes nobody else outside of developers cares about developing experience. We, they just care about, are you making the thing that helps me make the other thing go faster or ship faster, whatever. And that's it. All these other metrics around, like, I don't know, like number of people visiting your blog posts, like no one cares. So I'm very cynical about that sort of thing. OhMike: 10:45no, my analytics,Pauline: 10:49I was just going to say that's... That's probably the most refreshing take actually. Because I feel like a lot of other people have not mentioned it in that sort of way or describe developer experience in that way you are right.Shawn: 11:02Also, I wasn't interviewing there, I was talking with a very senior person at Cloudflare and, I told him this . And he was, I think he was like considering to hire me or whatever. And it wasn't an interview or anything, but I think I closed that door when I told him this, because he was like, what are you talking about? Developer Experience is everything. I'm like, dude, like, come on. Like, like developers are very pampered. Like we have like unlimited leave ,we have like six figure salaries. We're fine. Like, we don't, you don't have to pretend like this is the highest value thing in the world. But, I mean, it's still very valuable. It's just it's one of many possible things that smart people are. Oh, could you read it one more? Nice thing, which is that I think improving the developer experience for beginners is very important. Enables beginners to get started, to make the career, to, to transition their careers which is I'm a career changer myself. And if I did not have the help of people who focus so much on docs and community and, making things accessible to beginners, then I would not be here. I'm not against it. I'm just saying it's not, you know, there are also many other important things.Pauline: 12:09Absolutely. If you're like a doctor or a surgeon, or solving our pandemic . Yeah. No, thank you for that. A lot of our guests have said accessibility especially to begin as is why people should continue caring about developer experience and improving it and stuff like that. That's a good point.Shawn: 12:25Yes.Mike: 12:29No, no, I, I was, uh, I wanted to move on, but that's a good point. And it does make moving on a bit easier then on the previous note we talked about, so I think we talked about the commands that, you know, do a lot for you. What other kind of like excellent developer experience have you experienced or maybe build yourself or with the team that you can share about?Shawn: 12:49I feel like I should write this down because there's a number of nice develop experiences that stick in my head that I haven't really articulated very well. So in other words, single command doing multiple things that's good until the point that it becomes too magic and then that's bad. We've established that already. Another one that I really like is making some cycles faster, right? If you can make things in order of magnitude faster than you have better developer experience. Something that people bring up a lot is the benchmarks of IES built in the JavaScript ecosystem, comparing to Webpack or a parcel or roll-up. On the ESPP build website, they have a very prominent benchmark that shows that they are a hundred times faster than Webpack. And that is. And when anytime you increase things by orders of magnitude, that you unlock different usage of that tool. And so I think it's a very important thing to try to always look for areas in which you can speed up the feedback cycle because then you unlock opportunities for play. I think one of the best talks on developer experience that everybody has talked about is I think Bret Victor's inventing on principle talk, where he shows like, okay, if instead of jumping back and forth between your editor and your final output, why not just combine them and have your app or your writing be directly interactable so that you can shape it and play with it as you go along and discover new things because of the play. So I really am inspired by that. And there's a simple analogy to the shift left ideology that came out of IBM, which is that a lot of times when people discover bugs, they discover it very late in production, or even after they shifted in production. And if you shift things left, if you reduce the feedback loop of finding bugs, whether through tests or types or a QA or whatever, right? There's a whole bunch of techniques that are all developer tooling and development experience related. If you shift those items left from production back into the development time, then you enable the opportunity to increase the feedback loop in and correct your mistakes before they get too far out, or you build too much. So I really liked that feedback loop reduction, and then another developer experience thing, which I really like is this idea that everything is just there for you. In other words, you don't have to go out and assemble a bunch of different tools yourself, having an all in one package that with blessed the tools that are known to work together, I think is really helpful. One example of this is I'm actually going to venture out to the jobs review system and talk about Anaconda and Python. So Python is a fairly wide and huge community. But Anaconda is a specific distribution of hyphen with preselected pack packages that are all guaranteed to work together because dependency resolution was a huge problem for the Python ecosystem and the data scientists that were using Python, where it's spending so much time, like trying to say, like, does this work at the other thing? No, it doesn't. So I will have to both drop back to like an older version of the common thing, blah, blah, blah. Very common in JavaScript as well, by the way. But Anaconda actually managed to carve out a niche in Python and made Python, the de facto language for machine learning because they made that develop experience so much. And I actually genuinely think that they are, single-handedly responsible for making Python itself that much more popular. I think that's another interesting thing, which is like, where's the all-in-one for the 80% of use cases that don't need that much customization. Of course, if you want to customize sure, go ahead. You have the full power, but most people, they don't, they just have very standard needs. Let's just do this, just pave out the common path. And so that's how I went from using React. Which is the most popular Javascript framework, to Svelte, which Mike knows very well. And so has all the tools and tools included batteries included. And if I need to customize or drop out of it, I can. And I think that is also a really good developer experience in there so that the, all the ones who toolkit it, that doesn't constrain you too much.Mike: 16:57So really the question for 2022 is what's the Anaconda of JavaScript?Shawn: 17:01When Vercel talks about building the SDK for the web, that's what they mean.Mike: 17:04Yeah. Good point.Pauline: 17:05You gave me lots of flashbacks of playing around with Python over the past few years. I haven't really been in that ecosystem in a long time. Actually, Mike will be really proud of me, but I started learning and rebuilding one of my big projects. One of my, well, actually my blog, which is my biggest project, in Svelte, moving away from Nextjs. But, it's taking me quite a long time, longer than I thought, because there's so many. I don't know, there's so many different things that I need to learn how to use this Svelte way of doing things. But yeah, it's really interesting. It's a lot of fun. I understand why Mike and yourself love it so much. I think.Mike: 17:43We will talk offline about that Pauline.Pauline: 17:46So let's, let's do that. Yeah. Lots to, lots of talk about, yeah, it's messy. Yeah. Awesome. Thank you for sharing that.Shawn: 17:55One thing I'll share with you about this Svelte thing. I'm friends with Rich. I had come across Svelte, but actually ignored him for a year until I was like on a trip with him at Barcelona. And then he was like, he's still talking about Svelte. And I was like, okay, I have to try this because you can only be friends with someone so long before you have to try their things. And then I tried it and I was like, oh, okay. I'm an idiot for ignoring this for so long. But the other thing. Notice was that Svelte did not have a very strong community backing behind it. So actually started Svelte society as a part of the next stage of developer experience. So if you think about that reading radiating circle thing, had a very strong product already and it needed and it had pretty good docs. It needed the next level, which is community or DevRel, whatever that is. There is no first party DevRel for Svelte, but I guess Rich's the one had a one man show for that. The community part was the thing that I focused on and that's how Svelte society got started.Pauline: 18:45I was going to say, but this is what is this? Maybe the sixth or seventh episodes that we'll be posting on dev X pod and community has taken the lead every single time. It's always the thing that brings everything together. And it's also very validating because I focused on community at Gitpod so every time I hear it, I'm just like, yeah, that was great. Cool. Awesome. I wanted to move on to our next question, which is, where do you see DevX evolving? Will we be focused on tools or people or community?Shawn: 19:20I think, in line with the model that we've been developing, in this episode, either you integrate forward or integrate backwards, in other words, a typical typically develop experience is very tied to developer relations and a lot of first party content creation. So you integrate forward, meaning that talk a little bit more with community, you take on more community management roles or you encourage more, third party content by holding workshops and stuff like that. Or you integrate backwards, which is you get more involved with products. So I think that's an interesting way to think about this in terms of the radiating circles, but the other way to think about it as well is what's the shift within the content creation meta game, which I think about a lot as well. So for me right now is that I think a lot of people should be shifting towards video. I think that, the amount of time that how much time do you spend. You know, a week or a day I spent roughly an hour or two hours. Yeah,Pauline: 20:14exactly. I was going to say a bigger number than that, so, yeah. I'm glad you said your number first.Shawn: 20:19We all spend, we all spent a lot of time and a lot of times we're never going to spend on developer content because we're just on YouTube to veg out to. But I think people who do video very well are getting disproportionate attention. And I think it's a very scalable format. There are challenges with it, which I think Mike has maybe one up in the past before, which is that video is very expensive to produce and it gets outdated very quickly. There will be new tools that arise to fix that. But otherwise, I think the sheer reach of YouTube is just unparalleled. It is the second biggest search engine in the world. The content that lives on there, if you can get it to be evergreen, it can be extremely valuable. I still get comments on videos that I did two years ago, I always think about the half-life of content. The half-life of a tweet is four hours. The half-life of a blog post is maybe like a year or if it's a good blog post, if it's a normal. blog post that everyone is like treating us nothing special then. Yeah. It's probably a day or so. That will be irrelevant in a non-existent, but for videos. It's definitely very long. So I'm very interested in that. And I almost also interested in this idea of having a short game in the long game. It's kind of like tennis. If you only play long games, if you only stay at the back and you only love the ball and then you get killed on the, on the short game. Likewise. So in other words, do you have a short form game where you can pitch your startup in very short and concise detail? And do you have a long game where if people want to engage with you over very in-depth conversation, you also have ability to go deep and you have the content to offer them. I think having, so this is why I focus on having two minute videos and three hour workshops. you want to go extremes? There's a lot of 30 minute talks and podcasts out there. That's fine. But, I think the areas of relative under development are the short game and the long game.Mike: 22:12I had a conversation with a friend recently where she was asking me like, Hey, why don't we put some educational tech content on TikTok? And it was around the time when, TikTok had took over Google products in terms of like number of visits in 2021. And that was yeah, actually, why not? So I signed up for TikTok and I spent like 10 minutes watching videos. And I'm like, this is crap. Like what the heck? There's just too much stuff I don't care about. So I need a way to filter the stuff I care about. But then I started searching for things like web development, full stack development, and then whatnot. And there's a few things, but I think what you're saying in terms of the two minutes versus longer things, you can take that to an even other extreme of I'm going to take a real cheesy example, but array methods. One video, 15 seconds about each method and put it up there, see if it goes viral and people talk about it. But I think this is another platform that it's going to up and coming and currently not used for it, I think might be a really interesting play.Shawn: 23:11To see if it started watching it. I'm keeping eyes on it as well. The problem is that every, everybody knows array methods and you're not really doing anything for your work by explaining a writing methods. You might grow your own personal following, but that's also not a very valuable following. And let's just be real about that, right? If you get a whole bunch of beginners, then you will be incentivized to create more beginner content and you'll be stuck in beginner tutorial. And then I see a lot of people also get stuck to that because the numbers are only thing that matters to them. So I think, as far as philosophy of consecration goes, I definitely aim for some mix of intellectual curiosity and reach. And if you have only reach, then you may sell out yourself and you may burn out. You may not fall in love with the process. And I think that is the saddest thing in the world for someone to be in such a privileged job as a developer experience person, and to have your own personal intellectual curiosity, thrown by the wayside. I do, and they're doing courage to try to pursue some mix of reach plus first intellectual curiosity. I think the person that really does it best is Scott Hanselman. I don't know if you follow him. To talk as well. He does introductory stuff, but it's always authentic to him. He's not selling out. He's genuinely like, Hey, I think this is really important. And whether or not it happens to be advanced or intermediate or beginner, he's always very much that this is something he genuinely thinks in his.Pauline: 24:34The first thing that's on my mind is the fact that I love how in the past two episodes, actually we've been talking about, we've been bringing to light, content creation in developer experience because I don't think a lot of people think about that. Certainly until the previous episode, I didn't really think of developer experience, including content creation or including things like videos or tech talks, because the only thing I was thinking about was the products, like how can we make the product better? So that engineers on board quickly. So yeah, I really liked this conversation and it's really quite eye opening for me. I don't know. Mike, I wanted to say to your point, TikTok does get better after you train the algorithm. I was like, I don't know why anyone is on this app is just full of gen Z. I was just like, I don't understand this. But then after I started watching content that I actually liked it's really good it's really interesting. And now I've been hooked like at least an hour a day. I've been on it.Mike: 25:33But well, on the bright side, I have a lot of different methods to peel a pineapple now. So I learned aPauline: 25:43lot of, and the how to use an air fryer in all these different ways, how to cook all these different recipes. Oh, yeah, it's really cool. I just find it really interesting that content creation is included, but it really validates where my thoughts are in terms of content creation and develop experience as a whole.Shawn: 26:01This job, this industry is still very nascent, so it's not well-defined. So I don't think you should feel weird about it at all. I think for me, I came at it from my background, which is that we called this DevRel function, this content creation function at Netlify, we called it developer experience engineer. And so that's part of what we do. I should also mention that. Yeah, we were responsible for third-party integrations as well. So I guess.Pauline: 26:33Exactly.Shawn: 26:35But no, I think, at the end of the day, people wants to develop the tools. Companies want people to discover them and the best ways to, through content marketing. And that's why they hire people who are smart at that. And getting them down through that top of the funnel is very useful to them. I think probably where that we need to do better is that yes, I can pull a lot of people at the top of funnel, but if the product doesn't align with what they expect, then it's going to be a very leaky bucket. A lot of people going to come in, they're going to kick the tires and then they're going to leave. So how can we get a higher qualified audience or how can we get a product that is more intuitive or that retains people better? My own personal journey has been very much backward integrating into.Mike: 27:21Nice. Yeah, I feel like every episode we recorders, I always go away with it and I'm like, okay, let me think about all that again. And then I started researching and digging deeper and I'm like, there's a lot of interesting stuff. And we're really just getting started and five years from now, if we had another episode and talked about what is DevRel going? We would have a very interesting conversation, probably very different to today. Definitely looking forward to it. Cool. So one thing we tried to do is use kind of at the end of the podcast to wrap up with a fun thing that you recently came across with, or somebody you want to give a shout out to, that really made your day in the last couple of weeks or so? Um, yeah anything top of mind that you want to share?Shawn: 28:01I wasn't prepared for this, but I guess I'll shout out to obsidian. So I think for me, my personal note taking system is very much very important to me in terms of having it as a second brain where I store all the thoughts that I had that are still working progress or data points on some essay that I'm writing, but it's not done yet. And I moved around a lot from simple note to one note to notion. And most recently I made the shift to obsidian and the way I decided on this is that I really wanted to bet on mark down. I think mark down is a format that's going to. Longer than any of us. And that I also wanted it to sync, to GitHub and to have a good mobile application and obsidian match all of those things. Plus it has an optional service to publish your notes so I can share what I am thinking as I think it, for people who really care about, finding out before I publish something on my blog. Obsidian is a really good note taking.Pauline: 29:01I was going to say that is really interesting that you shared that for this week because Mike I'll just go next. But the thing that I wanted to share this week is actually LogSeq which is similar to obsidian. I don't know if you've heard of it. I think it's created by the same people or someone had left obsidian team and then built it. I'm not actually sure of the background. But I have been using it for the past two months now. And it's my favorite note taking app, just because, I think in bullet points. And I sometimes feel overwhelmed when I used to use other note taking apps where I would write like a long block of notes and then I try to organize it, but it just all felt overwhelming. Whereas when I have bullet points at the start of when I'm taking notes, it just like sinking things into my head better. I don't know. No, it just makes sense for my workflow. And then every single day, I don't need to worry about organizing my notes. I can just when I open up the app tomorrow, I will have a fresh, clean slate and I can start I'm taking notes of my day. And again, it's become my second brain because then I can just scroll back down and be like, what did they do yesterday again? And then everything is in one place. So yeah, LogSeq is my shout out of the week actually. And it was just really interesting that you brought up obsidian. Cause I think they go hand in hand. Well, but yeah, over to you, Mike, what's your fun thing about.Mike: 30:30Well, you really put me in a tough spot because I feel like I need to talk about my note taking,Pauline: 30:35I genuinely have this prepared in my notes. I was like, this is what I'm going to talk about, which is why I was really interested in,Mike: 30:42oh, I'll take the Liberty to do two things. One is my note taking app, which is Reflect.App. Exactly the same concept. You get a little graph every day. It gives you a new empty note, you take your note, but same idea. Markdown, I guess, for the win. The other thing I did have in my notes though to share is I don't even know if I should share it because I literally just found out about it two days ago when I read the landing page, but I want to dive deeper into it. It's swim.io with double M. And what they're saying is that they sync your talks with your code. So it's more of like a documentation tool for code, it seems well, the screenshot looks interesting. Let's say that. So I'm going to dive into it, but I figured this, is it something that is literally just top of mind, for today's podcast then? Um, I figuredShawn: 31:30out what share that. Yeah, we actually a hand-rolled we had wrote something like this for our own docs. I don't know if it's a startup. I remember this one because, swim, they raised a pretty big series, a 30 million, and also it's coming out of Israel. So it's just like a really it's the market, this big come on. But, uh, Hey, you know, it's a hard problem and it helps developer experience.Pauline: 31:53We'll link everything that we mentioned from this episode in the show notes, but we have reached the end of the podcast. Oh my gosh time has flown by. Thank you so much, Shawn, for joining us today, I'm excited to share this episode with everyone. So many things to think about, and Mike said earlier, I actually edit these podcasts, so I listen to them, quite a few times over. Every time I listened to them, I'm like, wow, there's so many ideas here that we can take on for Gitpod, for community or whatever it is. I'm really excited to re-listen to this multiple times, take the best bits and then share it with everyone. So yeah. Just want to say thank you again.Shawn: 32:30Well, thanks for having me pleasure. I'm really excited that you guys are doing this because people are dying for more DevX content. Every time I post something about it. You know, how I feel about that mix now? And so every time I posted about it, I always feel like a bit of a mix of like, okay, like, this is interesting, but also I don't want it to define who I am, but I think it, yeah, it's definitely very valuable and people are very interested.Pauline: 32:51Yes, absolutely. Absolutely. I'm sure it's going to be an interesting lesson to a lot of people!

Amplify Studio is a new visual interface that lets front-end and full-stack developers go from Figma design to full-stack React app, both cloud-connected backend and front-end UI components, in hours. In this episode, Simon is joined by Nikhil Swaminathan (Senior Manager, Product Management) to discuss all things AWS Amplify. They dig into the future of web and mobile app development, why the team built the service, and how startups and enterprises are accelerating their development on AWS. Learn more about Amplify - https://aws.amazon.com/amplify/ Learn more about Amplify Studio - https://aws.amazon.com/amplify/studio/ Learn more about Amplify Hosting - https://aws.amazon.com/amplify/hosting/

Web programming is super fun, and it is very handy. Being able to create custom programs to handle pictures, files, and information from other users over the internet is pretty neat. Thanks to projects like AWS Amplify, building web applications is much easier than it used to be! I'll get a tutorial with my little project that I discuss out on my blog at https://sammy.life by March 27th :D. The goal of these talks is to improve my ability to talk enthusiastically! The challenge is based on the book "Grow Rich! With Piece of Mind" by Napoleon Hill, and you are to read or talk enthusiastically for 10 minutes a day. Try it with me! It will be fun comparing this episode to one a month from now! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app Support this podcast: https://anchor.fm/pocket.macro/support

In this episode, Dave chats with Nikhil Swaminathan, Sr. Manager, Product Management at AWS Amplify, to discuss AWS Amplify Hosting. AWS Amplify Hosting is a fully managed CI/CD and hosting service for fast, secure, and reliable static and server-side rendered apps that scale. It supports many modern web frameworks including React, Angular, Vue, Next.js, Gatsby, Hugo, Jekyll, and more. Nikhil covers how AWS Amplify Hosting can help developers, how to get started, and examples of how customers are using it today. Nikhil on Twitter: https://twitter.com/theswaminator Dave on Twitter: https://twitter.com/thedavedev AWS Amplify Hosting: https://go.aws/3sJXouA AWS Amplify on Twitter: https://twitter.com/awsamplify AWS Amplify Documentation: https://docs.amplify.aws Amplify Discord Server: https://discord.gg/amplify 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

In this Episode Mark and Mike chat to Dave 'live from Vegas' at AWS re:Invent 2021. Watch to find out their take on Matt Coulter's speech as part of Werner Vogels keynote, how Serverless and CDK is becoming part of the mainstream as well as the announcement on CDK Patterns Version 2. Sustainability has been the hot ticket item at AWS re:Invent - you saw that prediction from The Serverless Edge first!  AWS have announced their Carbon Calculator.  And sustainability is now another pillar in the Well Architected framework. There was more news on AWS Amplify and great dialogue on the Data Driven Enterprise as well as the Goldman Sachs Financial Cloud for Data.  Some of the new pieces were incremental and the team were spotting how machine learning is being integrated in many of the developer tools. Don't miss out on Serverless Craic's unique insight and perspectives as well as hints on the best talks from AWS re:Invent 2021. Serverless Craic from The Serverless Edge theserverlessedge.com @ServerlessEdge

In this episode, Dave chats with Mohit Srivastava, Sr. Manager, Product Management, Front-End Web and Mobile. The Amplify team had a large announcement during Werner's keynote at re:Invent, with the launch of Amplify Studio. Mohit dives into this new release, the challenges it was created to address, the ability for developers to now extend Amplify Studios behavior, and what else the team has been working on to help accelerate everyday work for developers. Mohit on Twitter: https://twitter.com/mohit Dave on Twitter: https://twitter.com/thedavedev AWS Amplify on Twitter: https://twitter.com/awsamplify AWS Amplify Docs: https://docs.amplify.aws/ AWS Amplify GitHub: https://github.com/aws-amplify AWS Amplify Discord Server: https://discord.gg/amplify AWS re:Invent 2021 Werner Keynote with Amplify Studio announcement: https://bit.ly/3n0Lauz Introducing AWS Amplify Studio with Ali Spittel: https://bit.ly/3HEGeDi 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

In this episode, we discuss AWS Amplify, JetBrains Fleet, Oracle's acquisition of Cerner, review our 2021 predictions, and make new predictions for 2022.

In this extended episode, Luciano and Eoin try to cover a recurring topic around Serverless: is it a good or bad idea for startups? We start by giving a brief description of the different definitions and perspectives on serverless. Then, we try to explore some cases in which we believe serverless might not be the best fit for a startup. We follow on by revisiting some cases where instead we believe serverless can actually be a great fit. We finish by discussing some suggestions on how a startup (or even a more established company) could start approaching serverless in a more cautious and incremental way. In this episode we mentioned the following resources: - Auth0: https://auth0.com/ - Algolia: https://www.algolia.com/ - Firebase: https://firebase.google.com/ - Laravel: https://laravel.com/ - Django: https://www.djangoproject.com/ - Express: https://expressjs.com/ - AWS Amplify: https://aws.amazon.com/amplify/ - Our previous episode on Amplify: https://www.youtube.com/watch?v=W9ZTYIVQWjQ This episode is also available on YouTube: https://www.youtube.com/AWSBites You can listen to AWS Bites wherever you get your podcasts: - Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-bites/id1585489017 - Spotify: https://open.spotify.com/show/3Lh7PzqBFV6yt5WsTAmO5q - Google: https://podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy82YTMzMTJhMC9wb2RjYXN0L3Jzcw== - Breaker: https://www.breaker.audio/aws-bites - RSS: ​​https://anchor.fm/s/6a3312a0/podcast/rss Do you have any AWS questions you would like us to address? Leave a comment here or connect with us on Twitter: - https://twitter.com/eoins - https://twitter.com/loige

In this episode, Emily and Dave chat with Harshita Daddala, Sr. Product Manager - Technical at Amazon Web Services. Harshita covers her career path at Amazon, the benefits of AWS Amplify for developers, and the recent launch of the AWS Amplify Geo library for JavaScript. Amplify Geo enables developers to quickly add location-aware features to their frontend web and mobile applications. It includes a set of abstracted client libraries built on top of Amazon Location Service, pre-integrated map UI components (based on the popular MapLibre open-source library) aa well as an Amplify Command Line Interface (CLI) tool that supports provisioning for all required cloud location services. Harshita on Twitter: https://twitter.com/harshitadaddala Harshita on LinkedIn: https://www.linkedin.com/in/harshita-daddala-682ab138/ ----------- Announcing General Availability of Amplify Geo for AWS Amplify – https://go.aws/2Z2NAQq Add Maps to your App in 3 Steps with AWS Amplify Geo powered by Amazon Location Service - https://go.aws/3FwKiEH ----------- AWS Amplify on Twitter: https://twitter.com/awsamplify AWS Amplify Documentation: https://docs.amplify.aws Amplify Discord Server: https://discord.gg/amplify ----------- Connect with Us on Twitter: Emily on Twitter: https://twitter.com/editingemily Dave on Twitter: https://twitter.com/thedavedev 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

Guest Peter Friese - Blog Twitter - @peterfriese YouTube - @peterfriese GitHub - @peterfriese Youtube Video - https://youtu.be/8m8oppa-LosRelated Episodes Episode 87 - Core Data Fun with Tim Mitra Episode 85 - AWS Amplify with Kilo Loco Episode 75 - Year of the Server with Tim Condon - Part 2 Episode 35 - SwiftUI - The Good, the Bad, and the Benefits Episode 8 - Cloud and Backend Services For Apps with Erik Gillespie Related Links Firebase Summit - November 10th Firebase YouTube Channel Firebase Blog Firebase Medium channel Firebase vs GCP Videos Projects & storage Functions & Firestore the LansingCodes app that never was Authenticate with Firebase Anonymously on Apple Platforms Make It So - Replicating Apple's Reminders app with SwiftUI and Firebase Swift on Cloud Run by Grant Timmerman from GCP SponsorsRevenueCatUsing RevenueCat to power your in-app purchase infrastructure solves: For edge cases you don't even know you have Protects from outages your team hasn't seen yet Saves you time on future maintenance  As well as new features released by the app stores Empowers your marketing teams with clean, reliable IAP data All that to say, RevenueCat handles all the headaches of in-app purchases so you can get back to building your app. Try RevenueCat today at revenuecat.com.LinodeA cloud experience developers love Great for Setting Up a Backend for Your App Variety of VM Configurations and Settings Reasonable Pricing Starting at $5 per month Global Data Centers The Developer Cloud Simplified Try it today with this special link:https://www.linode.com/?r=97e09acbd5d304d87dadef749491d245e71c74e7Check out OrchardNest Today:https://orchardnest.comShow Notes What does Firebase consist of How to use it properly in your iOS app How Firestore's NoSQL DB works How to work with Firestore and SwiftUI What are Firebase's authentication features Setting up security properly How to authenticate with Firebase anonymously? Register for Firebase Summit Social MediaEmailleo@brightdigit.comGitHub - @brightdigitTwitter BrightDigit - @brightdigitLeo - @leogdionRedditLeo - /u/leogdionLinkedInBrightDigitLeoInstagram - @brightdigitPatreon - empowerappshowCreditsMusic from https://filmmusic.io"Blippy Trance" by Kevin MacLeod (https://incompetech.com)License: CC BY (http://creativecommons.org/licenses/by/4.0/)★ Support this podcast on Patreon ★

Alexander Barge ist Solutions Architect im AWS-Startup-Team und unterstützt Gründer:innen dabei, mit ihrem jungen Unternehmen auf AWS durchzustarten. Er selbst war Co-Founder und CTO eines FinTech-Startups, kennt also aus eigener Erfahrung die - nich nur technischen - Herausforderungen, denen sich viele Startups stellen müssen. Links zur Sendung: AWS Startups - Tools und Resourcen für Startups auf AWS (aws.amazon.com/de/startups) AWS Activate (aws.amazon.com/de/activate) AWS Startup Lofts (aws.amazon.com/startups/lofts) AWS Amplify (aws.amazon.com/amplify) Alexander Barge bei LinkedIn (www.linkedin.com/in/alexanderbarge) und Twitter (twitter.com/realalexbarge) Der offizielle deutschsprachige Podcast rund um Amazon Web Services (AWS), für Neugierige, Cloud-Einsteiger und AWS-Experten, produziert von Dennis Traub, Developer Advocate bei AWS. Bei Fragen, Anregungen und Feedback wendet euch gerne direkt an Dennis auf Twitter (@dtraub) oder per Mail an traubd@amazon.com. Für mehr Infos, Tipps und Tricks rund um AWS und die Cloud folgt Dennis auf: Twitter - https://twitter.com/dtraub LinkedIn - https://www.linkedin.com/in/dennis-traub YouTube - https://www.youtube.com/dennistraub

Table of Contents 2021 State of the Industry. - 32 Crucial Technology Industry Statistics to Know in 2021 Software Engineer's Career Pathshow to stay relevant in an ever-changing industry A Typical Career Path for a Software Engineer Below is a common career path for a software engineer. Bear in mind that each company will have its own specific roadmap and this is just an example. Junior Software Engineer: At the beginning of your career you'll have limited experience and start in an entry-level position. As a junior software engineer, you'll be required to develop software to meet client requirements within a specified time frame. You'll report to your team leader, who will act as a mentor and guide you. During this period of your career, you have the opportunity to learn new skills and gain essential experience working on real-life software projects. Senior Software Engineer: After a few years, you'll become a senior software engineer. You'll learn new programming languages, and master the software development lifecycle. You may have the opportunity to train junior engineers or even manage a small team of your own. You'll start to be introduced to other business elements such as project budgets and high-level company objectives. Tech Lead: As a tech lead, you'll be responsible for the entire software development process. You'll manage a large team of professionals involved in software design and development. You'll be required to report development progress to company stakeholders and provide input into the decision-making process. Team Manager: If you have strong leadership skills, you can progress into a managerial-based role. You'll be responsible for the well-being of the entire team and will oversee their career progression. Technical Architect: As a technical architect, you're expected to overlook the entire architecture and technical design. You'll be required to build processes for the team and provide technical leadership. This role will also involve looking into the scaling of support systems. Chief Technology Officer: A CTO is the head of an organization's technological needs. They oversee R&D and employ technology to improve products and services for their clients. This is often considered the pinnacle of a software engineer's career --- Send in a voice message: https://anchor.fm/devtheory/message

Isaac talks about his experience with AWS Amplify. Shaun talks us through Tesla day and some upcoming events. Is Copilot gonna take our jobs??? We talk about it. Reach out if you want to sponsor us! sponsorship@devtheorypodcast.com --- Send in a voice message: https://anchor.fm/devtheory/message

In this episode Emily and Dave talk to Ali Spittel, who leads developer advocacy for AWS Amplify at Amazon. Ali has a passion for teaching others how to code, and helping them to become full-time developers. In her role at AWS, she works with mobile and web app creators on new tools that remove friction, and speed up development time. Ali on Twitter: https://twitter.com/ASpittel Ladybug Podcast: https://www.ladybug.dev/ AWS Amplify on Twitter: https://twitter.com/awsamplify AWS Amplify: https://docs.amplify.aws/ Amplify Discord Server: https://discord.gg/amplify Connect with Us on Twitter: Emily on Twitter: twitter.com/editingemily Dave on Twitter: twitter.com/thedavedev

In this episode, we talked to Jermaine Oppong. Jermaine Oppong is a web developer, YouTuber, and blogger. Today we focused on Dart outside of Flutter, Dart on the backend and on the web.Jermaine works on Creative Bracket. Creative Bracket is the go-to resource blog on Dart and Flutter with easy-to-understand written and video tutorials.He's got the greatest YouTube videos on Dart, and he's got great videos on different Dart backend options, Aqueduct, shelf router, Angel, as well AngularDart, Firebase, AWS Amplify, Heroku, cloud functions, GraphQL, and of course Flutter.We discussed how the Dart landscape looks like in 2021. We talked about different backend options for Dart, including Shelf, Shelf Router, Aqueduct, Angel, Alfred, and more. I also asked Jermaine whether he would use Flutter, AngularDart, OverReact, or a JavaScript framework for the web.I've got to be honest, reading the different sunsetting, deprecation, roadmap updates was kind of a bummer, but wanted to talk about the topic regardless. Hope you enjoyed the episode anyway. The shelf and shelf router projects are great, and the Alfred project is also improving quickly.Creative BracketWeb creativebracket.comYouTube Creative BracketCloud Functions with Dart Tutorial - Build a QR Code GeneratorDart Package of the Week (playlist)Build a Single Page App with Dart and Shelf Router #1 | Static File and API ServerTwitter @creativ_bracketResourcesShelfpub.dev/packages/shelfpub.dev/packages/shelf_routerCreative Bracket - Build RESTful Web APIs with Shelf_routerAlfredpub.dev/packages/alfredgithub.com/rknell/alfredAngel - Dart on the Serverangel-dart.devgithub.com/angel-dart/angelDeprecating AngelAqueductaqueduct.iogithub.com/stablekernel/aqueductAnnouncing the Sunsetting of AqueductWeb support for FlutterAngularDartgithub.com/angulardart/angularDocsAngularDart Roadmap updateOverReactGuest: Jermaine OppongTwitter  @graphicbeaconGitHub @graphicbeaconLinkedIn @jermaineoppongHost: Vince VargaTwitter @vincevargadevGitHub @vincevargadevLinkedIn @vincevargadevWeb vincevarga.dev

In this episode of the Flutter 101 Podcast, I talked to Sebastian Döll.Sebastian is a Senior Software Engineer living in Berlin. He currently works on GitHub at Microsoft. Previously, he worked as Solutions Architect at AWS. He created products at DigitalOcean, Axel Springer, Accenture, and IBM.I found his article on the AWS Open Source Blog about a Dart Runtime for AWS Lambda:Writing your functions in Dart enables you to use your skills to develop mobile applications to create serverless backends. You also can share code between your application and your backend, and use the power of a statically typed language.Sebastian explained how he was able to support the Dart language via custom Lambda runtimes, and how we can create a Lambda function in Dart.We also talked about several related topics, serverless compute, the serverless app framework, AOT vs JIT, cross-compilation (or lack thereof), alternative languages and serverless compute services, and how devs need to think about serverless architectures.ResourcesIntroducing a Dart runtime for AWS LambdaAWS Open Source Bloggithub.com/awslabs/aws-lambda-dart-runtimeAWS LambdaLambda RuntimesCustom AWS Lambda RuntimesThe Serverless Application Frameworkserverless-dartAzure FunctionsGoogle Cloud FunctionsAWS AmplifyFirebaseDart AWS APIs by Agilord on pub.devFirecrackerAWS CloudFormation (Infrastructure as Code)AWS Serverless Application Model (SAM)AWS Cloud Development Kit (CDK)Guest: Sebastian DöllTwitter @katallaxieGitHub @katallaxieWeb katallaxie.meHost: Vince VargaTwitter @vincevargadevGitHub @vincevargadevLinkedIn @vincevargadevWeb vincevarga.dev

In our best episode yet, we host Nader Dabit (@dabit3), DevRel at #AWS Cloud and AWS Amplify, Author of #FullStackServerless, top StackOverflow contributor for React, and a tried and true web and mobile developer, consultant, and founder. "Good engineers figure out how to solve a problem. Great engineers figure out how to solve themselves out of the problem." Nader tells his self-taught story taking free online Harvard and Standford courses and shares his approach of his developer workflow optimization and automation as well as his fully serverless stack of dev tools and technology. > Never miss a video // SUBSCRIBE: https://bit.ly/2PzTqAI // About The Ops Show // #TheOpsShow is a weekly YouTube show and podcast hosted by Tristan Pollock and Kyle Campbell covering the wide world of #workflows in #DevOps and the greater developer experience. Watch ALL EPISODES: https://bit.ly/2WgD1F5 + https://w.cto.ai/theopsshow > Join the community // SHIP TOGETHER: https://bit.ly/3fTPKpe // About CTO.ai // CTO.ai provides end-to-end serverless infrastructure designed for the needs of fast-moving development teams who want to optimize what the business cares about. Easy to use like Heroku, and powerful like Kubernetes, CTO.ai gives you the tools you need to workflow smarter, not harder. > Try out the platform: https://cto.ai/platform > Or come say hello: https://github.com/cto-ai https://twitter.com/CTO_ai https://www.linkedin.com/company/cto-ai/ https://www.instagram.com/cto.ai/ https://www.facebook.com/CTOdotAI/ https://www.twitch.tv/cto_ai

AWS Amplify's value proposition is very attractive. In this episode, we talk about that promise and our first-time experience using it while also delving into the Zeigarnik effect and its contribution to this experience.

In this episode Nick and Rob share the top launches from AWS including interviews with ElastiCache for Redis Global Datastore, AWS Amplify and Bottlerocket.

Nader Dabit is a Developer Advocate at AWS and Founder of React Native Training. He joins hosts Jared Palmer and Ken Wheeler on The Undefined to talk about React Europe, React hooks, the future of work, consulting, and more.FeaturingNader Dabit - Twitter, Github, Website, ConsultancyKen Wheeler – Twitter, GitHub, WebsiteJared Palmer – Twitter, GitHub, Website, AgencyLinksReact EuropeAWS AmplifyReact Native TrainingLe Centre PompidouThe Fondation Louis Vuitton"The Slaves" by MichaelangeloLes PhilosophesSupremeWhere the Heaux at? T-ShirtHTML Canvas Images - W3SchoolsMimic class properties with useEventCallbackuseSubscription hook PRurql GraphQL clientStartup Nation by Dan Senor, Saul SingerCoders are the new Rock Stars - Dan Stein aka @DJFreshUKPicksDrizlyGerhard RichterThe Clermont Lounge