Podcasts about api design

Mark Ericksen, creator of the Elixir LangChain framework, joins the Elixir Wizards to talk about LLM integration in Elixir apps. He explains how LangChain abstracts away the quirks of different AI providers (OpenAI, Anthropic's Claude, Google's Gemini) so you can work with any LLM in one more consistent API. We dig into core features like conversation chaining, tool execution, automatic retries, and production-grade fallback strategies. Mark shares his experiences maintaining LangChain in a fast-moving AI world: how it shields developers from API drift, manages token budgets, and handles rate limits and outages. He also reveals testing tactics for non-deterministic AI outputs, configuration tips for custom authentication, and the highlights of the new v0.4 release, including “content parts” support for thinking-style models. Key topics discussed in this episode: • Abstracting LLM APIs behind a unified Elixir interface • Building and managing conversation chains across multiple models • Exposing application functionality to LLMs through tool integrations • Automatic retries and fallback chains for production resilience • Supporting a variety of LLM providers • Tracking and optimizing token usage for cost control • Configuring API keys, authentication, and provider-specific settings • Handling rate limits and service outages with degradation • Processing multimodal inputs (text, images) in Langchain workflows • Extracting structured data from unstructured LLM responses • Leveraging “content parts” in v0.4 for advanced thinking-model support • Debugging LLM interactions using verbose logging and telemetry • Kickstarting experiments in LiveBook notebooks and demos • Comparing Elixir LangChain to the original Python implementation • Crafting human-in-the-loop workflows for interactive AI features • Integrating Langchain with the Ash framework for chat-driven interfaces • Contributing to open-source LLM adapters and staying ahead of API changes • Building fallback chains (e.g., OpenAI → Azure) for seamless continuity • Embedding business logic decisions directly into AI-powered tools • Summarization techniques for token efficiency in ongoing conversations • Batch processing tactics to leverage lower-cost API rate tiers • Real-world lessons on maintaining uptime amid LLM service disruptions Links mentioned: https://rubyonrails.org/ https://fly.io/ https://zionnationalpark.com/ https://podcast.thinkingelixir.com/ https://github.com/brainlid/langchain https://openai.com/ https://claude.ai/ https://gemini.google.com/ https://www.anthropic.com/ Vertex AI Studio https://cloud.google.com/generative-ai-studio https://www.perplexity.ai/ https://azure.microsoft.com/ https://hexdocs.pm/ecto/Ecto.html https://oban.pro/ Chris McCord's ElixirConf EU 2025 Talk https://www.youtube.com/watch?v=ojL_VHc4gLk Getting started: https://hexdocs.pm/langchain/gettingstarted.html https://ash-hq.org/ https://hex.pm/packages/langchain https://hexdocs.pm/igniter/readme.html https://www.youtube.com/watch?v=WM9iQlQSFg @brainlid on Twitter and BlueSky Special Guest: Mark Ericksen.

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereThomas Johnson - Co-Founder & CTO at MultiplayerJulian Wood - Serverless Developer Advocate at AWSRESOURCESTomhttps://x.com/tomjohnson3https://www.linkedin.com/in/tomjohnson3https://github.com/tomjohnson3Julianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodLinkshttps://www.multiplayer.appDESCRIPTIONJulian Wood and Tom Johnson explore the complexities of modern software development, with Tom sharing his journey from machine learning and distributed systems to founding Multiplayer, a company focused on simplifying development by automating documentation, debugging, and system design.They discuss the challenges of building and managing complex software architectures, especially with microservices and cloud platforms, and the need for better tooling to address these issues. Tom emphasizes the importance of simplicity, collaboration, and transparency in development, especially when it comes to API design and managing system dependencies. They also explore best practices for team communication, the evolving role of platform engineering, and the shift toward a future where infrastructure is abstracted away, allowing developers to focus on software creation.Together, they envision a world where better tools and AI lower the barrier to entry for developers, driving innovation and enabling more people to bring their ideas to life.RECOMMENDED BOOKSSimon Brown • Software Architecture for Developers Vol. 2David Farley • Modern Software EngineeringKim, Humble, Debois, Willis & Forsgren • The DevOps HandbookSimon Wardley • Wardley MapsSimon Wardley • Wardley Mapping, The KnowledgeDavid Anderson, Marck McCann & Michael O'Reilly • The Value Flywheel EffectMike Amundsen • Restful Web API Patterns & Practices CookbookBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Join Allen Wyma and Arnaud Lauret, author of The Design of Web APIs, Second Edition, as they discuss creating user-friendly, secure, and efficient APIs. 

17: Aligning API Design to Business Outcomes with James Higginbotham, LaunchAny by Moesif API Observability

Join us as Tanner Linsley, the creator and founder of TanStack Start talks about its transition from Vinci to a more streamlined architecture built on Nitro. Learn about the framework's innovative approach to server functions, its isomorphic design philosophy, and how it differs from other frameworks like Remix. Tanner also shares insights into TanStack's sustainable open-source business model and his journey to building developer tools that prioritize user experience over rapid growth.Show Notes0:00 - Intro0:38 - Welcome Tanner Linsley3:43 - React Server Components and TanStack Evolution6:04 - TanStack Start Overview and Vinci Transition11:26 - Nitro Integration and Framework Architecture15:19 - Server Functions and Framework Comparisons20:58 - API Design Philosophy24:19 - Testing and Development Process30:58 - Team and Collaboration Discussion33:38 - Open Source Sponsorship Strategy36:32 - Netlify Partnership Announcement38:37 - Open Source Sustainability Discussion41:03 - Picks and Plugs LinksProducts & Tools:TanStackVinxi by Nikhil SarafNitroReact RouterTRPCRemixH3 (web request library)XPro (Tweet Deck)Deck.blue (BlueSky client)MOTU M4 audio interfaceBamboo Lab A1 3D printerLashbrook Designs (Brad's wedding band)Companies & Sponsors:ConvexClerkAG GridSentryNetlifyGames & Entertainment:Blockus (board game)Severance (TV Show on Apple TV+)"First Lie Wins" (book)Personal Projects & Links:buildtwelve.com (Amy's project)Brad on BlueSky (@bradgaropy.com)Nozzle (Tanner's startup)Technical Resources:Babel Dead Code Elimination (by Pedro Katori)GitHub 3D Contribution Graph GeneratorReact Server Components documentationOther Projects Mentioned:Solid StartAstro

In today's jam-packed episode, they dive deep into the world of API design, logging best practices, and effective configuration management. Our esteemed guests, Michael Dawson, James Snell, Matteo Collina, and Natalia Venditto, bring their extensive expertise to the table, discussing the nuances between GraphQL and REST/Open API, the merits of API First vs. Code First approaches, and the impacts of global states in Node.js applications.You'll hear insights on how to maintain effective API contracts, avoid common pitfalls in software development, and implement robust error handling and logging mechanisms. Additionally, the episode covers practical advice on optimizing large-scale ecosystems with tools like Pino and managing dependencies thoughtfully to avoid technical debt.They also touch on the personal side of development, with James Snell emphasizing the importance of well-being by taking regular breaks. Charles Max Wood shares his recent experience at a board game convention and recommends the TV show "Reacher" for some downtime entertainment.So, sit back and enjoy this enlightening conversation that spans across technical deep dives and light-hearted discussions, offering valuable takeaways for developers at all levels.SocialsLinkedIn: James SnellLinkedIn: Michael DawsonLinkedIn: Matteo CollinaLinkedIn: Natalia VendittoPicksCharles - Gnome Hollow | Board GameCharles - Reacher (TV Series 2022Michael - MakerWorld: Download Free 3D Printing Models Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Send us a textUnlock the secrets of API design and elevate your system design skills with our latest episode featuring me, Benny Kitchell. Explore the pivotal role APIs play in system design interviews and real-world development, where they act like the seamless communication between waiters, cooks, and customers in a restaurant. Learn how to craft APIs that are tailored to both internal and external developers by understanding their specific needs and objectives, ensuring a smooth and efficient user experience.We also shine a light on the critical aspects of designing API routes. Understanding user needs and addressing core problems are the bedrock of effective API design. By focusing on functional and non-functional requirements, you'll be equipped to create API routes that meet real-world demands. Discover the importance of API versioning through our Spotify example, where future-proofing your design becomes crucial in maintaining user satisfaction and facilitating seamless updates.Finally, we delve into the world of real-time data transfer, examining both synchronous and asynchronous communication methods. From the traditional request-response model to the innovative use of WebSockets for instantaneous data exchanges, we break down the strengths and limitations of each approach. Equip yourself with the knowledge to choose the best method for your client-server interactions, ensuring your system design is robust, flexible, and ready for any challenge.Support the showDedicated to the memory of Crystal Rose.Email me at LearnSystemDesignPod@gmail.comJoin the free Discord Consider supporting us on PatreonSpecial thanks to Aimless Orbiter for the wonderful music.Please consider giving us a rating on ITunes or wherever you listen to new episodes.

We're talking OpenAPI this week! Kris & Johnny are joined by Jamie Tanna, one of the maintainers of oapi-codegen, to discuss OpenAPI, API design philosophies, versioning, and open source maintenance and sustainability. In addition to the usual laughs and unpopular opinions, this week's episode includes a Changelog++ section that you don't want to miss.

We're talking OpenAPI this week! Kris & Johnny are joined by Jamie Tanna, one of the maintainers of oapi-codegen, to discuss OpenAPI, API design philosophies, versioning, and open source maintenance and sustainability. In addition to the usual laughs and unpopular opinions, this week's episode includes a Changelog++ section that you don't want to miss.

A common challenge for developers of SaaS products is integrating with existing services, including services that customers might already be using. For example, a SaaS product might need to integrate with customers using Salesforce, HubSpot, or another CRM system. However, this can be demanding for developers when 3rd party APIs are poorly documented or inconsistent. The post The Challenge of API Design with Lauren Long appeared first on Software Engineering Daily.

“Always remember that system design interview is not about perfection. It is about trade-offs and being able to communicate them clearly and concisely." Zhiyong Tan is the author of “Acing the System Design Interview”. In this episode, he joins me in demystifying the system design interview process. He shares insights into what to expect, how to tackle common challenges like time management, anxiety, and knowledge gaps, and reveals the core principles that guide successful system design interview. Zhiyong dives deep into common pitfalls, offering advice on handling tricky topics like requirements gathering, data consistency, scaling problems, and service design. He also provides practical tips on how to learn and grow from system design interview failures, turning setbacks into stepping stones towards success. Whether you're a seasoned engineer or just starting your tech career, this episode offers valuable insights and actionable advice to help you ace your next system design interview.   Listen out for: Career Journey - [00:01:43] System Design Interview - [00:05:03] Trade-offs - [00:07:36] Managing the Time - [00:09:51] Handling What You Don't Know - [00:13:27] Managing Anxiety - [00:15:40] System Design Interview Principles - [00:18:32] Non-Functional Requirements - [00:21:22] Data Consistency - [00:25:11] Database Scaling Problem - [00:28:41] Distributed Transactions - [00:33:09] Functional Requirements & API Design - [00:36:31] Failing System Design Interview - [00:38:38] 3 Tech Lead Wisdom - [00:42:02] _____ Zhiyong Tan's BioZhiyong Tan is the author of Acing the System Design Interview. He is the founder of Tingxie, an app for learning Chinese as a second language. Previously, he was an Engineering Manager and Staff Engineer at PayPal, a senior software engineer at Uber, and a software and data engineer at various startups. Follow Zhiyong: LinkedIn – linkedin.com/in/zytan Acing System Design Interview – https://www.manning.com/books/acing-the-system-design-interview Tingxie (iOS) – https://apps.apple.com/us/app/%E5%90%AC%E5%86%99-chinese-spelling-dictation/id6462944919 Tingxie (Android) – https://play.google.com/store/apps/details?id=com.zhiyong.tingxie Jointgoals.com – https://www.jointgoals.com/ Manning forum – https://livebook.manning.com/forum _____ Our Sponsors Enjoy an exceptional developer experience with JetBrains. Whatever programming language and technology you use, JetBrains IDEs provide the tools you need to go beyond simple code editing and excel as a developer.Check out FREE coding software options and special offers on jetbrains.com/store/#discounts.Make it happen. With code. Manning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 45% discount for Tech Lead Journal listeners by using the code techlead45 for all products in all formats. Like this episode? Show notes & transcript: techleadjournal.dev/episodes/176. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Buy me a coffee or become a patron.

In Elixir Wizards Office Hours Episode 2, "Discovery Discoveries," SmartLogic's Project Manager Alicia Brindisi and VP of Delivery Bri LaVorgna join Elixir Wizards Sundi Myint and Owen Bickford on an exploratory journey through the discovery phase of the software development lifecycle. This episode highlights how collaboration and communication transform the client-project team dynamic into a customized expedition. The goal of discovery is to reveal clear business goals, understand the end user, pinpoint key project objectives, and meticulously document the path forward in a Product Requirements Document (PRD). The discussion emphasizes the importance of fostering transparency, trust, and open communication. Through a mutual exchange of ideas, we are able to create the most tailored, efficient solutions that meet the client's current goals and their vision for the future. Key topics discussed in this episode: Mastering the art of tailored, collaborative discovery Navigating business landscapes and user experiences with empathy Sculpting project objectives and architectural blueprints Continuously capturing discoveries and refining documentation Striking the perfect balance between flexibility and structured processes Steering clear of scope creep while managing expectations Tapping into collective wisdom for ongoing discovery Building and sustaining a foundation of trust and transparency Links mentioned in this episode: https://smartlogic.io/ Follow SmartLogic on social media: https://twitter.com/smartlogic Contact Bri: bri@smartlogic.io What is a PRD? https://en.wikipedia.org/wiki/Productrequirementsdocument Special Guests: Alicia Brindisi and Bri LaVorgna.

“A good API doesn't expose the internal data models or internal logic too much. And the more your clients are not under your control, the less you want to do that." Today's clip is from Tech Lead Journal episode 125 with Daniel Luebke, a software architect and the co-author of “Patterns for API Design”. In this clip, we discussed some API design patterns and best practices taken from his book. Daniel shared the importance of understanding domain requirements for building APIs and several API and message best practices.  Listen out for: Writing API Design Book - [00:00:26] Loosely Coupled Message Exchanges - [00:04:29] API Design Best Practices - [00:07:07] Message Best Practices - [00:12:24] _____ Daniel Luebke's BioDaniel Lübke is an independent coding and consulting software architect with a focus on business process automation and digitization projects. His interests are software architecture, business process design, and system integration, which inherently require APIs to develop solutions. He received his PhD at the Leibniz Universität Hannover, Germany, in 2007 and has worked in many industry projects in different domains since then. Daniel is author and editor of several books, articles, and research papers; gives training; and regularly presents at conferences on topics of APIs and software architecture. Follow Daniel: LinkedIn – linkedin.com/in/danielluebke Twitter – @dluebke Blog – digital-solution-architecture.com _____ Our Sponsors Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags available by visiting techleadjournal.dev/shop. And don't forget to brag yourself once you receive any of those swags. Like this episode? Show notes & transcript: techleadjournal.dev/episodes/125. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Buy me a coffee or become a patron.

As programmers and global travelers, we understand the importance of being well-versed in multiple languages. However, there's one language that holds a special place in our hearts: the language of API Design. It's a skill that requires a delicate balance of consistency, developer experience, and stakeholder involvement. In our quest for knowledge, we came across the enlightening API Design Matters Substack by David Biesack, a renowned expert in the field. We couldn't resist inviting him to our API Intersection podcast to share his invaluable insights on all things design-related.As the Chief API Officer at Apiture, David focuses on API design and utilizes OpenAPI. Let's look at some of the benefits of OpenAPI for documenting and designing APIs and the importance of consistency in API design. Catch David's series on the language of api design at apidesignmatters.substack.com and check out his LinkedIn *disclaimer (31:24): When discussing application/problem+json, the wrong RFC is cited. The correct one is RFC 7807 -- see https://datatracker.ietf.org/doc/html/rfc7807 (Erik Wilde is one of the authors)_____To subscribe to the podcast, visit https://stoplight.io/podcast--- API Intersection Podcast listeners are invited to sign up for Stoplight and save up to $650! Use code INTERSECTION10 to get 10% off a new subscription to Stoplight Platform Starter or Pro.Offer good for annual or monthly payment option for first-time subscribers. 10% off an annual plan ($650 savings for Pro and $94.80 for Starter) or 10% off your first month ($9.99 for Starter and $39 for Pro).

“A good API doesn't expose the internal data models or internal logic too much. And the more your clients are not under your control, the less you want to do that." Daniel Luebke is a software architect and the co-author of “Patterns for API Design”. In this episode, we discussed some API design patterns and best practices taken from his book. Daniel first shared the importance of understanding domain requirements for building APIs and several API and message best practices, such as API first design, how to design loosely coupled message exchanges, the tradeoff between generic and specialized API operations, and the risk of exposing too much internal data model and logic in our APIs. Daniel also introduced the microservices domain-specific languages (MSDL) as an alternative to Open API for specifying APIs independent of the technology implementation. Towards the end, Daniel explained the importance of defining the API lifecycle, how to support backward compatibility, and the different API versioning strategies we can use to evolve our APIs.   Listen out for: Career Journey - [00:04:17] Writing API Design Book - [00:08:26] Loosely Coupled Message Exchanges - [00:12:53] API Design Best Practices - [00:15:31] Message Best Practices - [00:20:48] Generic vs Specialized API - [00:24:51] Exposing Internal Data Model - [00:27:13] Microservices Domain-Specific Language - [00:30:37] API Evolution - [00:33:23] API Versioning - [00:39:27] 3 Tech Lead Wisdom - [00:44:27] _____ Daniel Luebke's BioDaniel Lübke is an independent coding and consulting software architect with a focus on business process automation and digitization projects. His interests are software architecture, business process design, and system integration, which inherently require APIs to develop solutions. He received his PhD at the Leibniz Universität Hannover, Germany, in 2007 and has worked in many industry projects in different domains since then. Daniel is author and editor of several books, articles, and research papers; gives training; and regularly presents at conferences on topics of APIs and software architecture. Follow Daniel: LinkedIn – linkedin.com/in/danielluebke Twitter – @dluebke Blog – digital-solution-architecture.com _____ Our Sponsors Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags available by visiting techleadjournal.dev/shop. And don't forget to brag yourself once you receive any of those swags. Like this episode? Show Notes: techleadjournal.dev/episodes/125 Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Buy me a coffee or become a patron.

With several great books on API design already on our shelves, this one stands out as a hefty pattern language and catalog for API designers. It's chock full of about everything you could need to design an industrial-strength API. Our discussion steps through the pattern writing process, including working as a team of five industry and academic professionals. Learn insights from one of the book's co-authors and pattern writers—a software industry practitioner—including his favorite and most challenging pattern in the book.Daniel Lübke is a Software and Business Process Architect working at Digital Solution Architecture GmbH in Hanover, Germany. He received his PhD in Software Engineering in 2007. Since then he is working as a consulting and coding software architect in client projects. He is one of the contributors to the API Pattern collection, author and editor of several books and other publications, and is frequently sharing his experience in conference talks and lectures. Hosted on Acast. See acast.com/privacy for more information.

Richard talks with Swift expert Rob Napier about Swift, Unicode, and API design.

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

In this Breaking Changes, Postman Chief Evangelist Kin Lane welcomes James Pozenel, a Solution Architect at Dominos Pizza, to discuss how they have employed very pragmatic approaches to delivering APIs, taking advantage of simple low-cost HTTP APIs to meet the demands of feeding the world pizza!

Matt McLarty (@mattmclartybc) is the Global Field CTO at MuleSoft. He works closely with organizations to define digital strategies, as well as design and implement enterprise-grade API and microservices solutions. An experienced software architect, Matt has worked extensively in the field of integration and real-time data distribution. He is the co-author of the O'Reilly books Microservice Architecture and Securing Microservice APIs, co-author of the ebook Develop a Winning API Product Strategy, co-author of the HBR article “APIs Aren't Just for Tech Companies” and co-host of the APIs Unplugged podcast. Hosted on Acast. See acast.com/privacy for more information.

In this episode, we talk about the “smells” in API design that one should look out for. Keith Casey from ngrok's Product and GTM Team tells us how to evaluate your API design, what a great (and terrible) API design looks like and how API design smells can be dealt with. He also talks to us about his time trying to figure out how much data is in the Library of Congress and his underlying goal of bringing good technology to the hands of good people.

In this episode of Breaking Changes, Kin Lane is joined by Douglas Gubert, Tech Lead over at Rocket Chat, to share how they respect data sovereignty by providing a plugin-driven, on-premises solution for air-gapped networks, making privacy and security a top priority when producing and consuming APIs within a company.

What is and isn't an API? How has the technology changed over time? What are new considerations that have arisen? Hosts James & Josh discuss a variety of APIs and the benefits and faults that help refine the APIs of today. 00 - What is an API? 03 - S.O.A.P 05 - Restful API 06 - RSS & JSON 07 - Public API's 10 - Documentation driven development 13 - React API & GitHub 16 - Graph QL 19 - Twilio 20 - Stripe Payment 23 - Paypal 24 - Web hooks 27 - Pusher 30 - Modern API Considerations 31 - Cloud Front/ API Gateway 34 - Documentation - What is design without documentation 37 - Facebook & Open Graph 40 - PAW MAC API 44 - 3D Secure Resources: * https://pusher.com/ * https://graphql.org/ * https://paw.cloud/ * https://github.com/ Find out more about Stac and Parallax: * Stac (https://stac.works) * Parallax (https://parall.ax)

This interview was recorded for the GOTO Book Club.gotopia.tech/bookclubRead the full transcription of the interview hereMike Amundsen - Author of "Restful Web API Patterns & Practices Cookbook" and (Co-)Author of Many More BooksAlianna Inzana - Vice President of Product at WeTransferDESCRIPTIONThe API ecosystem is evolving and the focus is changing from “how to design them” to “how to implement them”. Mike Amundsen, author of "Restful Web API Patterns & Practices Cookbook", and Alianna Inzana, VP of Product at WeTransfer, cover the recent changes while also touching on broader subjects like evolvable architectures. Join them in this conversation around restful web API.The interview is based on Mike's book "Restful Web API Patterns & Practices Cookbook"RECOMMENDED BOOKSMike Amundsen • Restful Web API Patterns & Practices CookbookMike Amundsen • Design and Build Great Web APIsMike Amundsen • RESTful Web ClientsRonnie Mitra & Irakli Nadareishvili • Microservices: Up and RunningRonnie Mitra, Irakli Nadareishvili, Matt McLarty & Mike Amundsen • Microservice ArchitectureRonnie Mitra, Mehdi Medjaoui, Erik Wilde & Mike Amundsen • Continuous API ManagementRonnie Mitra & many more • DataPower SOA Appliance Administration, Deployment, and Best PracticesJames Higginbotham • Principles of Web API DesignTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.

This interview was recorded for the GOTO Book Club.gotopia.tech/bookclubRead the full transcription of the interview hereJames Higginbotham - Author of "Principles of Web API Design" and Executive API Consultant at LaunchAnyMike Amundsen - Author of "Design and Build Great Web APIs" and (Co-)Author of Many More BooksDESCRIPTIONJames Higginbotham, author of “Principles of Web API Design”, outlines the key points of creating and using APIs in today's world. In the conversation with Mike Amundsen, author of “RESTful Patterns and Best Practices for API's Cookbook” you discover the principles of James' ADDR process and how job stories and event storming contribute to a successful API launch. Furthermore, they touch upon key terms such as minimum viable portal and why API boundaries are so hot at the moment. The interview is based on James's book "Principles of Web API Design".RECOMMENDED BOOKSJames Higginbotham • Principles of Web API DesignMike Amundsen • Design and Build Great Web APIsMike Amundsen • RESTful Web ClientsRonnie Mitra & Irakli Nadareishvili • Microservices: Up and RunningRonnie Mitra, Irakli Nadareishvili, Matt McLarty & Mike Amundsen • Microservice ArchitectureRonnie Mitra, Mehdi Medjaoui, Erik Wilde & Mike Amundsen • Continuous API ManagementRonnie Mitra & many more • DataPower SOA Appliance Administration, Deployment, and Best PracticesTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.Discovery MattersA collection of stories and insights on matters of discovery that advance life...Listen on: Apple Podcasts Spotify Health, Wellness & Performance Catalyst w/ Dr. Brad CooperLooking for a catalyst to optimize your health, wellness & performance? You've found it!!Listen on: Apple Podcasts Spotify

Parse, Don't Validateetaque/elm-formCodecs episodeSome similarities in the design for how you build up Custom Type codecs with elm-codec

Hey Everyone,  Welcome to the API design masterclass with our guest Deepak Patil, who works as a Principal Architect at iCertis and has decades of experience building and architecting mission critical experience.   This is the Part-2 of the masterclass and we are going to continue where we left and talk about more practical stuff.   00:00 Sync, Async, Bulk, Composite APIs  10:16 Timeouts, Retries and Idempotency  17:08 Structure of an API  21:00 Versioning  26:45 How to choose REST vs GraphQL vs gRPC  36:30 API Lifecycle and Governance  38:50 Security, Scalability, Availability, Fault Tolerance, performance and Monitoring   I hope you enjoyed the discussion in the two parts series and now know a lot about API Design.  Please like, share and subscribe to the channel for more content like these.    Cheers,  The GeekNarrator

Hey Everyone, Welcome to the API design masterclass with our guest Deepak Patil, who works as a Principal Architect at iCertis (https://www.linkedin.com/in/01patilde...) and has decades of experience building and architecting mission critical experience. We talk about: Basic API Discussion 00:00 Introduction 03:50 What is an API? 07:10 Why do we want to implement APIs? 10:22 How do we plan to execute the API program? 14:45 Practical API Design 24:40 Dominant Styles of API Entity vs Behaviour oriented 31:50 Fine Grained vs Coarse grained APIs 43:45 Pagination I hope you enjoyed the discussion in the part-1, please do listen to part-2 for more advanced topics and more practical examples. Cheers, The GeekNarrator

Die meisten kennen Moore's Law oder auch Murphy's Law, aber was ist eigentlich Hyrum's Law? In dieser Folge sprechen wir über die Aussage dieses Gesetzes und was das für das Design von Schnittstellen und APIs bedeutet. Habt ihr selber Beispiele für Hyrum's Law erlebt? Dann lasst es uns wissen. Links: Hyrum's Law: https://www.hyrumslaw.com/ Comic von XKCD zu Hyrum's Law: https://xkcd.com/1172/ Malte auf Twitter: https://twitter.com/MalteLantin Robin-Manuel auf Twitter: https://twitter.com/robinmanuelt Feedback und Anregungen: todopodcast@outlook.com

Do you understand how a hash table works? What if you could learn about building one while practicing test-driven development? What are best practices when designing a REST API? This week on the show, Christopher Trudeau is here, and he's brought another batch of PyCoder's Weekly articles and projects.

In this episode: We discuss the world of protocols like tcp and httpThe protocols for API building (REST, GraphQL, RPC)Apache Arrow and why it is a great RPC use case MY RECENT ARTICLE ON APACHE ARROW FLIGHT SQL: https://www.dremio.com/subsurface/an-introduction-to-apache-arrow-flight-sql/ MY RECENT ARTICLE ON RPC: https://dev.to/alexmercedcoder/understanding-rpc-tour-of-api-protocols-grpc-nodejs-walkthrough-and-apache-arrow-flight-55bd LINK TO REGISTER FOR SUBSURFACE CONFERENCE: https://www.dremio.com/subsurface/live/winter2022/?utm_medium=social&utm_source=dremio&utm_term=alexmercedsocial&utm_content=na&utm_campaign=event-subsurface-2022

Cal sits down with renowned API architect James Higginbotham to discuss building APIs, what makes a good one, and what to include, even though you're sure your API won't need scalability.Check out James's book with Keith Casey, A Practical Approach to API Design and his latest solo work, Principles of Web API Design, which came out this month. See acast.com/privacy for privacy and opt-out information.

In our latest podcast episode, we spoke with Aleksei Akimov, Head of API at Adyen. He talks about pushing for a design-first, high-collaboration style approach. He also speaks on how API review is not done in a vacuum. Rather, it should include a variety of opinions from people in different positions. Finally, Aleksei suggests using automated style guides to sift out the boring stuff, allowing for discussion on bigger topics, for example, how customer-centric is your API?Do you have a question you'd like answered, or a topic you want to see in a future episode? Let us know here:https://stoplight.io/question/

In this episode, I review a few books on API Design. The Design of Web APIs by Arnaud Lauret the API Handyman, Irresistible APIs by Kirsten Hunter, and API Design Patterns by JJ Geewax. I also brainfart may refer to Kirsten Hunter as Kirsten Stewart so just ignore that. Act 1 - What is the goal of the API? API Goal Canvas - Who - What - How - Inputs - Outputs - Goals Alan's Digital Garden if the Manning link doesn't work in the future. Act 2 - What makes a “good” API? Act 3 - RESTful HTTP Guidance and Support Summary Define the goals and metrics of the API via design discussions and the API Goal Canvas and get feedback. A good API is fit for purpose, consistent, and expressive. RESTful HTTP Guidance and Supporting your API is more than the implementation. Support, Examples, Tutorials, workflows. etc.

In this episode, I review a few books on API Design. The Design of Web APIs by Arnaud Lauret the API Handyman, Irresistible APIs by Kirsten Hunter, and API Design Patterns by JJ Geewax. I also brainfart may refer to Kirsten Hunter as Kirsten Stewart so just ignore that. Act 1 - What is the goal of the API? API Goal Canvas - Who - What - How - Inputs - Outputs - Goals Alan's Digital Garden if the Manning link doesn't work in the future. Act 2 - What makes a “good” API? Act 3 - RESTful HTTP Guidance and Support Summary Define the goals and metrics of the API via design discussions and the API Goal Canvas and get feedback. A good API is fit for purpose, consistent, and expressive. RESTful HTTP Guidance and Supporting your API is more than the implementation. Support, Examples, Tutorials, workflows. etc.

In this episode, Damir and I take a deep dive on API design.Damir.Svrtan.meDamir Svrtan on TwitterDamir Svrtan on GitHub

In this episode, Saurabh Sahni and Taylor Singletary of Slack share their experiences and best practices for designing APIs and building developer communities.

What is design Mike Montiero says, "A designer solves problems within a set of constraints". What is API Design? The goal of API design is to try and get the defined API interface as right as possible at the beginning because the consequences are severe and lasting when you don't get them right. The reason it is severe is because people can build on top of the API and you cannot change it easily after that. The goal of API design is to try and get the defined API interface as right as possible at the beginning because the consequences are severe and lasting when you don't get them right. The reason it is severe is because people can build on top of the API and you cannot change it easily after that. API design is a cultural change in how people apply a process to doing their work. Microservices, domain driven design, cloud native, project to product, and inner sourcing are types of cultural transformations companies go on. The Goal of Design You are responsible for the work you put into the world based on Mike Montiero's summary of Victor Papanek's Design for the Real World. API-First Design versus Code-First? According to Kevin Sookocheff, this might be a false dichotomy with api development existing on a continuum. API Description First Coded API Description API Framework Implementation First Implementation First suffers from two problems that other practices do not. A lack of forethought in API design and the risk of the API description becoming out of synchronization with the API description. Good APIs according to JJ Geewax. Operational Expressive Simple Predictable API Creation Process according to Kirsten Hunter Business Value Metrics Use Cases API Design & schema model As designers of software it is our job to frame for others the decisions they are making. Publishing an API is a consequential and irreversible decision. By adding friction to this activity we can create compounding leverage by developing a foundation of proven API design patterns to start with instead of starting from scratch each time. We can create better software products by removing the friction that makes doing work hard for no good reason. We can also improve what we make by adding friction that results in better quality experiences. Poor designs cause real problems in the world like the Amazon s3 cli that cause an outage and the Citibank $500,000,000 UI problem.

What is design Mike Montiero says, "A designer solves problems within a set of constraints". What is API Design? The goal of API design is to try and get the defined API interface as right as possible at the beginning because the consequences are severe and lasting when you don't get them right. The reason it is severe is because people can build on top of the API and you cannot change it easily after that. The goal of API design is to try and get the defined API interface as right as possible at the beginning because the consequences are severe and lasting when you don't get them right. The reason it is severe is because people can build on top of the API and you cannot change it easily after that. API design is a cultural change in how people apply a process to doing their work. Microservices, domain driven design, cloud native, project to product, and inner sourcing are types of cultural transformations companies go on. The Goal of Design You are responsible for the work you put into the world based on Mike Montiero's summary of Victor Papanek's Design for the Real World. API-First Design versus Code-First? According to Kevin Sookocheff, this might be a false dichotomy with api development existing on a continuum. API Description First Coded API Description API Framework Implementation First Implementation First suffers from two problems that other practices do not. A lack of forethought in API design and the risk of the API description becoming out of synchronization with the API description. Good APIs according to JJ Geewax. Operational Expressive Simple Predictable API Creation Process according to Kirsten Hunter Business Value Metrics Use Cases API Design & schema model As designers of software it is our job to frame for others the decisions they are making. Publishing an API is a consequential and irreversible decision. By adding friction to this activity we can create compounding leverage by developing a foundation of proven API design patterns to start with instead of starting from scratch each time. We can create better software products by removing the friction that makes doing work hard for no good reason. We can also improve what we make by adding friction that results in better quality experiences. Poor designs cause real problems in the world like the Amazon s3 cli that cause an outage and the Citibank $500,000,000 UI problem.

Video link: https://www.youtube.com/watch?v=ddKDPikKbNkTimestamps00:00:00 Intro[00:00:11] Four Components of Developer Experience [00:02:08] API Design [00:03:27] Documentation [00:06:52] Learning Journey [00:07:59] Feature Mapping Presentation [00:11:10] Companies With Great DX [00:12:58] Most Misunderstood thing about Developer Experience [00:15:46] Docs as Service Team not Endpoint [00:19:33] How to Focus

APIs are part of our daily roles as software developers, but what are they? What different types are there? And how can you design a good one? Show Notes [01:53] What is an API? [03:37] Types of APIS [15:02] GraphQL [19:49] REST [28:25] API Design [44:35] Shoutouts Resources The Happiness Project Shopify developer community BrainF**k OneGraph Scott Moss's YouTube Transcript Here is this week's transcript.

Good APIs are hard to design! Making them long lasting and scalable is even harder. We discussed two aspects of API design. First, making about Event Bus for system integration and then RackN CTO, Greg Althaus, discusses what his team considers a good API design from Digital Rebar. Transcript: https://otter.ai/u/2Pz3LwG4qPl58s3ewwGFCCFmg8w Photo by Tsunami Green from Pexels [ID 5192790]

Get insights into the challenges and opportunities faced by API practitioners, and get a sneak-peek into Mike's globe-trotting journey sharing API stories. 

Lexical and dynamic scoping are useful tools to reason about various API design choices in PyTorch, related to context managers, global flags, dynamic dispatch, and how to deal with BC-breaking changes. I'll walk through three case studies, one from Python itself (changing the meaning of division to true division), and two from PyTorch (device context managers, and torch function for factory functions).Further reading.Me unsuccessfully asking around if there was a way to simulate __future__ in libraries https://stackoverflow.com/questions/66927362/way-to-opt-into-bc-breaking-changes-on-methods-within-a-single-moduleA very old issue asking for a way to change the default GPU device https://github.com/pytorch/pytorch/issues/260 and a global GPU flag https://github.com/pytorch/pytorch/issues/7535A more modern issue based off the lexical module idea https://github.com/pytorch/pytorch/issues/27878Array module NEP https://numpy.org/neps/nep-0037-array-module.html

Idiomatic Elm package guidedillonkearns/elm-package-starterLessonsAvoid unexpected or silent behaviorGive context/feedback when things go wrong so the user knows their change was registered, to enhance trustGood errors aren't just for beginners - Curb Cut EffectSandi metz - code has a tendency to be duplicated - be a good role model - we're influenced by precedenceMatt Griffith - API design is holistic. It's a problem domain. Rethink from the ground up.Learn from the domain and terms, but don't limit yourself to it when you can create better abstractions.Linus Torvalds' definition of elegance/good taste - recognize two code paths as one. Reduce the number of concepts in your API when you can treat two things as one, then things compose more easily. How Elm Code Tends Towards Simplicity.You don't need a direct mapping of your domain, but start with the spec and terms. Leverage existing concepts, and have an economy of concepts. Tereza's talk: elm-plot The Big PictureAPI design is a tool to help you solve problems.There's a qualitative difference when you wire up feedback before you up front.Avoid toy examples, use meaningful use cases to direct your design.Design for concrete use cases, and drive changes through feedback from concrete use cases. Legal standing. Better to do it right than to do it right now Evan's concept from the Elm philosophy. If you don't have a motivating use case, then wait. Extract APIs from real world code. It's okay for there to be duplication. Premature abstraction is the root of all evil. sSmplicity is the best thing you can do to anticipate future API design needs.Come up with an API with the most benefits and the least pain points.If there's something that you want to make really good, invest in giving it a good feedback mechanism.Rich Hickey's talk Hammock Driven Development. We don't design APIs, our extremely creative subconscious designs APIs - let your conscious brain do the hard work to put all the information in front of your subconscious so it can do what it does best. elm-pages 2.0 screencast with Jeroen and Dillon.Pay no attention to the man behind the curtain. Parse, Don't validate at the high level, but under the hood you may need a low level implementation.Have a clear message/purpose - whether it's an API, or an internal module.Take responsibility for user experiences.

APIs are fundamentally supposed to smooth out paths of communication. But you can't build that road if you don't understand what's happening at the destination. For API design architect Matt Reinbold, empathy for the end-user is a vital and often missing component of API design.A quick look at Matt's career with Fortune 500 companies and his own software consultancy shows that he has successfully balanced his interests in the human and technical aspects of software. Experience, occasionally learned the hard way, has taught Matt that factoring in the end-user early saves future headaches for you and them. It follows that Matt takes an anti-autocracy stance on API governance. When you're on top, it's easy enough to make the rules without input from others. But consulting the grassroots is more effective for company morale and productivity. Again, it all comes back to empathy.On this episode of API Intersection, Matt explains why organizing governance is never over, how to get everyone speaking the same technical language, and how to persuade leadership to lean into innovation.For full show notes and more info go to https://stoplight.io/podcast/Do you have a question you'd like answered, or a topic you want to see in a future episode? Let us know here:https://stoplight.io/question/

Building a great API requires more than code. First, you have to design one collaboratively with your team. Then you have to build it with the intention of providing a great developer experience. Once it's built, you have to focus on governance and consistency. And ultimately, you need to focus on maximizing your API's profitability, all while ensuring everyone on your team is on the same page. Jason Hartman has been working with APIs for over a decade, serving currently as CTO of Stoplight, and formerly as Head of API Design at PayPal, and CTO of Typeform, among others. On API Intersection, Jason and a few co-hosts are going to help you design, build, and maintain world-class APIs that better serve your end-user and your company. Each week, you'll hear from professionals running APIs at some of the most successful companies in the world, topical episodes breaking down things like API design, Governance, Platform Transformation (and more), or AMA episodes answering listener questions. We hope you enjoy it, and we'll see you in the next episode.

All super heroes have an origin story. And, *so do nerds*. Many of us can remember back to that moment when we realized that there was magic in the world - magic that we could be part of; and, magic that we could help create. This week, we get personal with the crew and learn more about where they came from, what kind of stuff makes them tick, and what it is that they love about being web application developers. This Part II of a two-part series. Part II will includes Carol and Adam. Part I was Ben and Tim. But *(drum roll please)* thank you to our first patrons! You are helping us make this podcast better. For anyone who wants to know more, check out our Patreon listed at the end of the show notes. *Triumphs & Fails* * *Ben's Failure* - He, like many of us, just doesn't "people" well at times. He makes an effort to improve this by staring emails with the goal being a reply. But with weeks of stared emails lacking replies, the effort feels a tad null. Maybe he should accept this flaw and consider it a feature. And... if he hasn't replied to your text message yet, don't feel bad, yours is only 1 of 1248. * *Carol's Triumph* - She mentioned last week that she was feeling a tad bit down at work, struggling to learn the business side as fast as she expected herself to. The self-induced kind of worries. This week during her 1-on-1, she was provided feedback which put that worries to rest. She is feeling less stress and more fresh. * *Tim's Failure & Triumph* - Boy oh boy, has Tim failed. He turned the chipper marketing team at work into a slightly less chipper set of people by avoiding delivering of a marketing approach he was on the hook for. No sweat team, he *will* get around to it. His Triumph for the week stem from our previous episode about 2021 Hopes and Goals. He wrote his own blockchain! The man is non stop! He also revels a great idea for using his new found blockchaining power. Perhaps a podcast coin? * *Adam's Triumph* - He's seesawing on if his triumph is a real triumph or not, and it is! He made it an entire day without sitting down. He is making an effort to stand more with the assistance of an electric sit/sand desk. *Notes & Links* * Tinker ( https://www.merriam-webster.com/dictionary/tinker ) - Means: to work in the manner of a tinker especially : to repair, adjust, or work with something in an unskilled or experimental manner * The Oregon Trail ( https://classicreload.com/oregon-trail.html ) - A popular game for kids of the 90's to play. The game was released in 1990 and was developed by MECC. * Tent.io ( https://indieweb.org/Tent.io ) - Was a suite of distributed networking protocols which had a goal to provide a consistent data layer that any app could tie into. In 2019 they closed shop due to funding. * Our first search engines: *Carol* : Ask Jeeves ( https://www.ask.com/ ) , *Tim:* Altavista ( http://www.altavista.com/ ) , *Ben:* HotBot ( https://en.wikipedia.org/wiki/HotBot ) , *Adam:* Dogpile ( https://www.dogpile.com/ ) * Welcome to the Machine ( https://www.youtube.com/watch?v=lt-udg9zQSE ) * Terminal Velocity ( https://www.gog.com/game/terminal_velocity ) * Teach yourself VB4 in 21 days ( https://dl.acm.org/doi/book/10.5555/550306 ) - Adams entry book into learning how to write code. * Church of Mountain Dew ( http://tutt.xyz/churchofdew ) - Web archive to the original church of mountain dew webpage * First stop to find the church of dew ( http://tutt.xyz/dew1 ) * Another relic to the church of dew ( http://tutt.xyz/dew2 ) * 12 year old Adam created his own Church of Mountian Dew in a notepad text editor. * The token ring network ( https://searchnetworking.techtarget.com/definition/Token-Ring ) - A token ring network is a local area network (LAN) in which all computers are connected in a ring or star topology and pass one or more logical tokens from host to host. Only a host that holds a token can send data, and tokens are released when receipt of the data is confirmed. * REST Assured ( https://restassuredbook.com/ ) - If you think rest is napping, pick up Adams book to understand Rest and API Design. * Taffy ( https://taffy.io/ ) - Adams REST Web Service Framework for ColdFusion and Lucee * Christian Ready ( https://christianready.com/ ) - Christian Ready is a great friend of ours. We all love his work and listening to him present any chance we get. Check him out on YouTube ( https://www.youtube.com/christianready ). Follow the show! Our website is workingcode.dev ( https://workingcode.dev/ ) and we're @WorkingCodePod on Twitter ( https://twitter.com/WorkingCodePod ) and Instagram ( https://www.instagram.com/workingcodepod/ ). New episodes weekly on Wednesday. And, if you're *feeling the love* , support us on Patreon ( https://www.patreon.com/workingcodepod ).

We've started considering options for how we'll get to our break-even point, which could include client work or possibly taking on investors. We also discuss our early strategy for the Arrows API and rollout.

Hi, Spring fans! Welcome to another installment of _A Bootiful Podcast_. In this installment [Josh Long (@starbuxman)](http://twitter.com/starbuxman) talks to longtime Spring Framework engineer and team "bass player" [Arjen Poutsma (@poutsma)](http://twitter.com/poutsma)

Every experienced software engineer can tell you a story about a standardization effort that ended up causing more problems than it solved. Queen Elizabeth's decree adding 280 feet to each mile made it easy to divide up acres, but has haunted those of us stuck with Imperial units ever since. Sara dives into micro frontend services and how they can help to add agility to a modern development team. There is a nice article on the topic here, and Sara found it through the Thought Works  Tech Radar.Pinterest paid just under $90 million dollars to break its lease in San Francisco. Paul and Sara are hearing about lots of developers who are fleeing major cities, and it seems clear that Pinterest won't be the last company to abandon expansion plans or ditch fancy corporate offices for at least the next few years. Our lifeboat badge of the week the week goes to Sravya Nagumalli, who explained why Angular is associated with the Single Page App and just what an SPA is anyway. Thanks for sharing some knowledge, Sravya!

Every experienced software engineer can tell you a story about a standardization effort that ended up causing more problems than it solved. Queen Elizabeth's decree adding 280 feet to each mile made it easy to divide up acres, but has haunted those of us stuck with Imperial units ever since. Sara dives into micro frontend services and how they can help to add agility to a modern development team. There is a nice article on the topic here, and Sara found it through the Thought Works  Tech Radar.Pinterest paid just under $90 million dollars to break its lease in San Francisco. Paul and Sara are hearing about lots of developers who are fleeing major cities, and it seems clear that Pinterest won't be the last company to abandon expansion plans or ditch fancy corporate offices for at least the next few years. Our lifeboat badge of the week the week goes to Sravya Nagumalli, who explained why Angular is associated with the Single Page App and just what an SPA is anyway. Thanks for sharing some knowledge, Sravya!

Matt and Brandon discuss VMware’s flex, recap Kubecon and aww at the sight of Zoom’s latest earnings. Plus, we are enlisting all listeners to come help stress test Slack Threads. The Rundown VMware’s app modernization chief: ‘We’ve put to bed the debate about containers versus virtual machines’ (https://siliconangle.com/2020/09/01/vmwares-app-modernization-chief-weve-put-bed-debate-containers-versus-virtual-machines/) Zoom — Fad or new dominant over lord Zoom crushes Q2 analyst expectations amid pandemic (https://www.axios.com/zoom-crushes-q2-analyst-expectations-amid-pandemic-8d2efec7-0aa4-4a8d-9fba-b278709c6a4f.html?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) I have never seen such numbers in my life. $ZM. (https://twitter.com/_ram_/status/1300538139971260416?s=21) What happened at Kubecon: KubeCon + CloudNativeCon Europe 2020 Keynote Summary (https://www.infoq.com/news/2020/08/kubecon-cloudnativecon-summary/) BPF Performance Tools (http://www.brendangregg.com/bpf-performance-tools-book.html) Security Valley private equity firm pays Dell $2.1B for RSA security business (https://www.bizjournals.com/sanjose/news/2020/02/19/palo-alto-private-equity-firm-buys-rsa-security.html) Engineer admits he wiped 456 Cisco WebEx VMs from AWS after leaving the biz, derailed 16,000 Teams accounts (https://www.theregister.com/2020/08/26/former_cisco_engineer_aws_webex_teams/) Stolen Fortnite Accounts Sold as Part of $1 Billion Black Market (https://www.bloomberg.com/news/articles/2020-08-27/stolen-fortnite-accounts-sold-as-part-of-1-billion-black-market) Follow up Discord is a thing…Discord looks to grow beyond its gaming roots (https://www.axios.com/newsletters/axios-login-d2587314-f65c-4cf0-b20f-50ab02564d47.html?chunk=1&utm_term=twsocialshare#story1) Apple New Apple TV in the works with 'upgraded' remote, Find My Apple TV remote feature (https://9to5mac.com/2020/08/31/bloomberg-apple-tv-new-remote/) Opinion | Apple's image is angelic, but it's actually the devil (https://www.nbcnews.com/think/opinion/apple-google-or-facebook-fortnite-lawsuit-shows-who-s-been-ncna1238775) Is anyone going to buy TikTok Poll: Google is the best fit to buy TikTok (https://www.axios.com/newsletters/axios-login-7faca673-ebfe-4d17-acd4-de2c17c60823.html?chunk=2&utm_term=emshare#story2) Relevant to your Interests AWS launches its Bottlerocket container operating system into general availability (https://siliconangle.com/2020/08/31/aws-launches-bottlerocket-container-operating-system-general-availability/) Facebook may block news from being shared on its platforms in Australia (https://www.theverge.com/platform/amp/2020/8/31/21409644/facebook-block-news-australia-legislation-google-publishers) Tencent's Dreams, Part II: Investing In The Metaverse (https://seekingalpha.com/article/4371548-tencents-dreams-part-ii-investing-in-metaverse?utm_medium=email&utm_source=seeking_alpha&mail_subject=must-read-tencent-s-dreams-part-ii-investing-in-the-metaverse&utm_campaign=nl-must-read&utm_content=link-1) Dell enjoys solid earnings beat thanks to remote-work demand surge (https://siliconangle.com/2020/08/27/dell-enjoys-solid-earnings-beat-thanks-remote-work-demand-surge/) Nonsense The Resilience of Costco (https://issuu.com/slowappreciation/docs/costco_deck) Heyyyyyyyyyyyy.com | email with nuance (https://heyyyyyyyyyyyy.com/) Airline pilots reported seeing 'a guy in a jetpack' flying 3,000 feet over Los Angeles (https://www.nbcnews.com/news/us-news/airline-pilots-reported-seeing-guy-jetpack-flying-3-000-feet-n1239027?cid=sm_npd_nn_tw_ma) Joseph Ducreux’s Self-Portraits (ca. 1790) (https://publicdomainreview.org/collection/joseph-ducreux-self-portraits) Sponsor strongDM strongDM — Manage and audit remote access to infrastructure. Start your free 14-day trial today at: strongdm.com/SDT (http://strongdm.com/SDT) Listener Feedback Sent stickers to Johan in Sweden. Sent to stickers to Sacha in Belgium Conferences Devops World 2020 by CloudBees | The Future of DevOps & Jenkins (https://www.cloudbees.com/devops-world). September 22-24, 2020 EnvoyCon 2020 (https://events.linuxfoundation.org/envoycon/) October 15, 2020 KubeCon + CloudNativeCon November 17 – 20 (https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/) SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/) and LinkedIn (https://www.linkedin.com/company/software-defined-talk/). Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=8) and he wants you to buy it for $0.99. Use the code SDT to get $20 off Coté’s book, (https://leanpub.com/digitalwtf/c/sdt) Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Listen to Brandon’s Interview Alexandra Martinez on MuleSoft and API Design (https://www.softwaredefinedtalk.com/254) Recommendations Matt Ray: FTL: Faster Than Light (https://subsetgames.com/ftl.html) Brandon: The Vow on HBO (https://www.hbo.com/the-vow) Photo Credit (https://unsplash.com/photos/qkQwDvRqQY8) Photo Credit (https://twitter.com/_ram_/status/1300538139971260416/photo/1)

Brandon interviews Alexandra Martinez (https://www.linkedin.com/in/alexandra-n-martinez/) and they discuss the MuleSoft Anypoint Platform, API Design and ProstDev. Plus, Alexandra recommends the best tacos in Monterrey, Mexico. Show links ProstDev (https://www.prostdev.com/) MuleSoft Anypoint Platform (https://www.mulesoft.com/platform/enterprise-integration-c?utm_source=google&utm_medium=cpc&utm_campaign=g-brands-na-search-anypoint-platform&utm_term=%2Bmulesoft%20%2Banypoint&utm_content=g-b-c&gclid=Cj0KCQjw1qL6BRCmARIsADV9Jtai-IvZwkHzjPub5fqPMYbhvo_CBmYs7E8tIq4uFXB4XSTcfeV_NkoaAne7EALw_wcB) Contact Alexandra (https://www.prostdev.com/alexandramartinez) Image Credit (https://unsplash.com/s/photos/monterrey-mexico) Special Guest: Alexandra N. Martinez.

This week we are diving into System and API Design! I have been going through a lot of System and API design with success, so I figured I would share what the resources and what I have found to be the best to tackle these interviews. Sponsors: AUDIBLE: Get your free 30-day trial and free…More

In episode 8 of the Vaadin Insider Podcast, Ankurman interviews Leif Åstrand who leads product architecture at Vaadin. We discuss everything API design related including: What is API Design and how it differs within the scope of a single application ( with an enterprise architecture) and within the scope of a reusable framework (or a library), The long-term cost implications for enterprise systems due to improper API Design, The questions that Enterprise Architects can ask themselves to better audit their legacy APIs as they gear up for digital transformation, and more. You can connect with Leif on: Twitter: @leifastrand Message to our listeners If you enjoyed listening to this episode of the Vaadin Insider Podcast, we would love to hear from you. You can directly share your favorite lessons on Twitter and ask the topics you would like to learn more about. Just tag @vaadin (or @ankurmans) and who knows we may also extend an invite for you to come to the show and win some free goodies for helping spread the word.

Also native filesystem, listener questions, and TMI.

“The Little Manual of API Design” is a very nice paper written by Jasmin Blanchette has released a paper while working in trolltech, which is a Nokia company. I found it to be very clear and concise, and reassuring what we think of API design. It’s a difficult task that includes both artistic, social, programming and scientific skills. We are going to summarize this paper for you.

Arnaud Lauret, also known as the API Handyman, recently published a book called The Design of Web APIs. In this podcast, I chat with Arnaud about his book, specifically exploring best practices for designing web APIs and focusing on the roles technical writers can play.

Phil builds API Design tools for Stoplight.io, writes articles and books about pragmatic API design and systems architecture, lives on a bike, and occasionally upsets hordes of mens rights activists on Reddit.  Show Notes APIs You Won't Hate (https://apisyouwonthate.com/books/build-apis-you-wont-hate) Surviving Other People's APIs (https://apisyouwonthate.com/books/surviving-other-peoples-apis) WeWork (https://www.wework.com/) Chaos Monkey (https://netflix.github.io/chaosmonkey/) Stoplight (https://stoplight.io/) maps.me (https://maps.me/) EuroVelo (http://www.eurovelo.org/) Joren De Groof (https://www.parallelpassion.com/21) Dubrovnik (https://en.wikipedia.org/wiki/Dubrovnik) Offset Earth (https://offset.earth/philsturgeon) Awesome Earth (https://github.com/philsturgeon/awesome-earth) AquaLoop (https://www.youtube.com/watch?v=Ihw3OZWxp9g) Cyclocross (https://en.wikipedia.org/wiki/Cyclo-cross) Tough Mudder (https://en.wikipedia.org/wiki/Tough_Mudder) Photo from a cyclo cross event Phil was in (https://www.instagram.com/p/Bo5TSVZh2HB/) Couchsurfing (https://www.couchsurfing.com/) Warmshowers (https://www.warmshowers.org/) Recommendations Blogging Applying to speak at conferences Explore the world Phil Sturgeon Twitter (https://twitter.com/philsturgeon) Instagram (https://www.instagram.com/philsturgeon/) Phil.Bike (https://phil.bike/) Phil.Tech (https://phil.tech/) Parallel Passion Patreon (https://www.patreon.com/parpaspod) Twitter (https://www.twitter.com/parpaspod) Instagram (https://www.instagram.com/parpaspod) Facebook (https://www.facebook.com/parpaspod) Credits Shane Rounce (https://unsplash.com/@shanerounce) for the header photo Tina Tavčar (https://twitter.com/tinatavcar) for Parallel Passion logo Jan Jenko (https://twitter.com/JanJenko) for intro/outro music

Last time on APIs You Won't Hate, we laid the ground work for this podcast. This time (after a failed attempt when Phil didn't press record) Mike, Phil, and Matt talk about whats new with Stoplight.io, how front end developers like Mike can use the Stoplight suite of OSS products to make Front End Development better, and where they are with the books! Notes: https://stoplight.io https://github.com/stoplight https://twitter.com/philsturgeon https://twitter.com/irreverentmike https://twitter.com/matthewtrask Sponsors: Huge thank you to Stoplight.io (https://stoplight.io) for sponsoring this episode! If you are looking to make your API workflow better, check them out for tools ranging from linting (Spectral) to mocking (Prism) to their new release Studio! --- Support this podcast: https://anchor.fm/apisyouwonthate/support

Podcasts are a great thing – the good parts of a radio show, the powerful snippets from an audio book, with all the content control of a topical news feed. Yet, there was something missing when Leah Culver tried to find her next episode to listen to, while training for her 1st marathon.

RESTful APIs quickly established themselves as useful architectural style for replatforming legacy systems with web-based ones. But increasingly, developers are running into the boundaries of deploying REST and API purity — confronting real world issues such as the rapid evolution of APIs for frontend layers where connectivity is patchy and where APIs should meet the changing visual representation and behavior of the frontend, where we increasingly see the adoption of alternatives such as GraphQL.   In this episode, co-hosts Mike Mason and Zhamak Dehghani are joined by Brandon Byars, Market Technical Principal at ThoughtWorks North America and James Gregory, Tech Lead at ThoughtWorks Australia to explore the current state of API design and look at the impact of event-based architectures.

In this episode, Jesse and JP dive in to opaque result types, which could help prevent leaking of implementation details to library consumers.

Chris and Spencer discuss the Principles of Component API Design (or Prop Design) and lessons they've learned while creating components. Principles of Component API (Prop) Design Make Impossible States Impossible Using component dot notation with TypeScript to create a set of components Building the Next Generation of Search at Handshake

Show Notes Phil's Twitter Phil's Blog Phil's Bike Blog API's You Won't Hate Book: Building API's You Won't Hate Book: Surviving Other People's API's

In this show I talk with close friend Keith Casey. Keith is in love with APIs and the security around them and while our conversation starts with API’s it finishes with the dumpster fire around security and our responsibilities as a developer today. Keith Casey currently serves on the Platform Team at Okta working on Identity and Authentication APIs. Previously, he served as an early Developer Evangelist at Twilio and before that worked on the Ultimate Geek Question at the Library of Congress. His underlying goal is to get good technology into the hands of good people to do great things. In his spare time, he helps build and support the Austin tech community, blogs at CaseySoftware.com and is fascinated by monkeys. He is also a co-author of “A Practical Approach to API Design” from Leanpub. https://caseysoftware.com 

Tim Wingfield is using lots of APIs. This episode is sponsored by Smartsheet. Show Notes: FireEye Ruby on Rails REST: REpresentational State Transfer CRUD: Create, Read, Update, Delete HTTP Request Methods: PUT, POST, GET, PATCH, DELETE Tim Wingfield is on Twitter. Want to be on the next episode? You can! All you need is the willingness to talk about something technical. Music is by Joe Ferg, check out more music on JoeFerg.com!

To create design time data or not to create design time data, that is the question? Or is it better to mock out all of your interfaces or say heck let's code straight to the API end points? When you are developing a large project and desire the "blendability", what approach is best to take, and what works well with design time tools like Blend and the Xamarin Live Player? We discuss all this and more on this week's episode. Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Music : Amethyst Seer - Citrine by Adventureface Proudly recorded on Zencastr

To create design time data or not to create design time data, that is the question? Or is it better to mock out all of your interfaces or say heck let's code straight to the API end points? When you are developing a large project and desire the "blendability", what approach is best to take, and what works well with design time tools like Blend and the Xamarin Live Player? We discuss all this and more on this week's episode. Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Music : Amethyst Seer - Citrine by Adventureface Proudly recorded on Zencastr

This week I sit with Rohit and we continue our discussion of his 10 step process for Microservice API design. 

There are various standards at play when creating and consuming Application Program Interfaces (APIs).  These standards, though, are mostly technical and mostly lower-level than the content of the API. Andy Beier has experienced the broad range of API quality in his role with Domo in creating integrations with other businesses.  He has made standardization of The post API Design Standards with Andy Beier appeared first on Software Engineering Daily.

The NFJS podcast is back for the 2017 Season! This week I sit with Rohit and discuss his 10 step process for Microservice API design. 

Keith Casey is co-author of A Practical Approach to API design: From Principles to Practice. Former Developer Evangelist at Twilio, his current work with Okta focuses on identity and authentication APIs. Keith is a software engineer focusing on creating open architecture, specifically APIs. His goal is to get good technology into the hands of good people to do great things.   Key Takeaways: [2:43] Keith Casey describes APIs from a business perspective. [5:04] Why would a business adopt an API strategy? [7:01] Twilio eliminates the need for a carrier contract and provides enterprises with immediate cost structure. [10:03] Zapier captures an event and then sends the information to another system. [12:48] Jeff Bezos’ memo ensured APIs would be part of Amazon’s future. [19:23] Salesforce and their development community built APIs to integrate with other systems and platforms. [21:45] The concept of API-First gives users a toolbox instead of a finished product. [25:45] Security implications shouldn’t keep a business from designing an API strategy.   Mentioned in This Episode: The API Design Book Casey Software @Caseysoftware on Twitter Praxent @PraxentSoftware on Twitter  

In this episode, Adam talks to Jonathan Reinink of Code Distillery about common API design challenges and how to fix them. Topics include: Does it make sense to scope resources to the authenticated user or should you always use sub-resources? When to use nested resources and when to avoid them Strategies for dealing with actions that don't seem to fit into REST Breaking the mapping between your API and your database Using singular sub-resources and optional fields to simplify your responses Links: Jonathan's personal website Plates templating library Glide image manipulation library Nesting resources by Jamis Buck There's a model hiding in your REST API Build APIs You Won't Hate by Phil Sturgeon Sponsored by Laracasts

Yehuda Katz joined the show to talk about JSON.API — where the spec came from, who’s involved, compliance, API design, the future, and more. We also finally got Yehuda on the show alone, so we were able to talk with him about his origins, how he got started as a programmer, and his thoughts on struggle vs aptitude.

Yehuda Katz joined the show to talk about JSON.API — where the spec came from, who’s involved, compliance, API design, the future, and more. We also finally got Yehuda on the show alone, so we were able to talk with him about his origins, how he got started as a programmer, and his thoughts on struggle vs aptitude.

 02:25 - Daniel Jacobson Introduction Twitter Blog SlideShare LinkedIn Netflix @netflix Netflix Techblog Netflix GitHub 02:46 - How Netflix Looks at Programming and Development Team Context and Control Freedom and Responsibility Netflix: Freedom & Responsibility Culture (Version 1) Netflix Culture: Freedom & Responsibility (Version 2)   Amazon AWS JVM (Java Virtual Machine) “Specialties” 05:03 - Maintaining a Consistent Culture Setting Context 06:37 - Onboarding Process 08:15 - Engineering spirals: 10 philosophies to facilitate innovation Introspection Transformations: Staffed Up Solving the Resiliency Problem hystrix 15:04 - Making Space for Innovation Building Expectations Incrementing Deliverables Building Trust and Confidence          Maintenance Mode 23:12 - APIs Why REST Keeps Me Up At Night API Orchestration Layers (Separation of Concerns) Gather Format Deliver 29:32 - Solving Real Problems, The Groovy Layer The Groovy Programming Language 31:34 - hystrix and Patterns for Making Systems Resilient Chaos Monkey SimianArmy Event Isolation ReactiveX 39:14 - RxJava 41:17 - The Dynamic of Senior Engineers Screening Process 44:02 - Conway's Law 47:44 - Best and Most Challenging Parts About Working for Netflix Scaling and Maintaining  Picks Fund Club (Coraline) The Codeless Code (Avdi) Trotro (Avdi) Serial Podcast (Chuck) Happy Father’s Day! (Chuck) RailsClips (Chuck) StartUp (Daniel) Reply All (Daniel) Mystery Show (Daniel) Chris Messina: Seeking Genius in Negative Space (Daniel) Chris Messina: Full Stack Employee (Daniel) Netflix Techblog (Daniel) Netflix GitHub (Daniel)

 02:25 - Daniel Jacobson Introduction Twitter Blog SlideShare LinkedIn Netflix @netflix Netflix Techblog Netflix GitHub 02:46 - How Netflix Looks at Programming and Development Team Context and Control Freedom and Responsibility Netflix: Freedom & Responsibility Culture (Version 1) Netflix Culture: Freedom & Responsibility (Version 2)   Amazon AWS JVM (Java Virtual Machine) “Specialties” 05:03 - Maintaining a Consistent Culture Setting Context 06:37 - Onboarding Process 08:15 - Engineering spirals: 10 philosophies to facilitate innovation Introspection Transformations: Staffed Up Solving the Resiliency Problem hystrix 15:04 - Making Space for Innovation Building Expectations Incrementing Deliverables Building Trust and Confidence          Maintenance Mode 23:12 - APIs Why REST Keeps Me Up At Night API Orchestration Layers (Separation of Concerns) Gather Format Deliver 29:32 - Solving Real Problems, The Groovy Layer The Groovy Programming Language 31:34 - hystrix and Patterns for Making Systems Resilient Chaos Monkey SimianArmy Event Isolation ReactiveX 39:14 - RxJava 41:17 - The Dynamic of Senior Engineers Screening Process 44:02 - Conway's Law 47:44 - Best and Most Challenging Parts About Working for Netflix Scaling and Maintaining  Picks Fund Club (Coraline) The Codeless Code (Avdi) Trotro (Avdi) Serial Podcast (Chuck) Happy Father’s Day! (Chuck) RailsClips (Chuck) StartUp (Daniel) Reply All (Daniel) Mystery Show (Daniel) Chris Messina: Seeking Genius in Negative Space (Daniel) Chris Messina: Full Stack Employee (Daniel) Netflix Techblog (Daniel) Netflix GitHub (Daniel)

 02:25 - Daniel Jacobson Introduction Twitter Blog SlideShare LinkedIn Netflix @netflix Netflix Techblog Netflix GitHub 02:46 - How Netflix Looks at Programming and Development Team Context and Control Freedom and Responsibility Netflix: Freedom & Responsibility Culture (Version 1) Netflix Culture: Freedom & Responsibility (Version 2)   Amazon AWS JVM (Java Virtual Machine) “Specialties” 05:03 - Maintaining a Consistent Culture Setting Context 06:37 - Onboarding Process 08:15 - Engineering spirals: 10 philosophies to facilitate innovation Introspection Transformations: Staffed Up Solving the Resiliency Problem hystrix 15:04 - Making Space for Innovation Building Expectations Incrementing Deliverables Building Trust and Confidence          Maintenance Mode 23:12 - APIs Why REST Keeps Me Up At Night API Orchestration Layers (Separation of Concerns) Gather Format Deliver 29:32 - Solving Real Problems, The Groovy Layer The Groovy Programming Language 31:34 - hystrix and Patterns for Making Systems Resilient Chaos Monkey SimianArmy Event Isolation ReactiveX 39:14 - RxJava 41:17 - The Dynamic of Senior Engineers Screening Process 44:02 - Conway's Law 47:44 - Best and Most Challenging Parts About Working for Netflix Scaling and Maintaining  Picks Fund Club (Coraline) The Codeless Code (Avdi) Trotro (Avdi) Serial Podcast (Chuck) Happy Father’s Day! (Chuck) RailsClips (Chuck) StartUp (Daniel) Reply All (Daniel) Mystery Show (Daniel) Chris Messina: Seeking Genius in Negative Space (Daniel) Chris Messina: Full Stack Employee (Daniel) Netflix Techblog (Daniel) Netflix GitHub (Daniel)

Support the shows at devchat.tv/kickstarter!   01:45 - Michele Titolo Introduction Twitter Blog Reddit Women Who Code Ruby Rogues Episode #147: APIs That Don't Suck with Michele Titolo 02:26 - Deconstructing and Decoupling Reuse Goals 08:36 - Having Seams in Your Code to Avoid Conflict 8 Patterns to Help You Destroy Massive View Controller 11:35 - The Deconstructing Mindset (Finding Reuse Patterns) The Rule of Three Inheritance 17:48 - The Decorator Pattern 18:43 - Categories 21:34 - Sharing UI (User Interface) Codes 23:55 - Mechanics of Sharing Code Between Apps Jeffrey Jackson: Private Cocoapods CocoaPods Guide: Podspec Syntax Reference 29:02 - Lessons Learned: Easy Ways/Patterns to Know When to Break Up Small Functionalities Separate as Soon As Possible Do a Local Pod Using the Path Option (Path is Your Friend!) CocoaPods Guide: Private Pods Have a Good Code Review Process 33:23 - Cocoapods: Commit to Source or Not? 39:59 - Team Collaboration Spotify [YouTube] Kent Beck: Software G Forces: The Effects of Acceleration Picks Refactoring: Improving the Design of Existing Code by Martin Fowler (Pete) Working Effectively with Legacy Code by Michael Feathers (Pete) Refactoring To Patterns by Joshua Kerievsky (Pete) WWDC 2010 Session 138: API Design for Cocoa and Cocoa Touch (Andrew) [Slides] Michele Titolo: Cocoa Design Patterns in Swift (Andrew) The Cocotron (Andrew) Matt Gallagher: Design of a multi-platform app using The Cocotron (Andrew) Zombie Monkie by Tallgrass Brewing Company (Jaim) Getting out and participating in programming language communities (Chuck) The Earthsea Cycle Series Book Series by Ursula K. Le Guin (Chuck) The Pixar Touch by David A. Price (Chuck) 8 Patterns to Help You Destroy Massive View Controller (Michele) Artsy - iOS at Scale - objc.io issue #22 (Michele)

Support the shows at devchat.tv/kickstarter!   01:45 - Michele Titolo Introduction Twitter Blog Reddit Women Who Code Ruby Rogues Episode #147: APIs That Don't Suck with Michele Titolo 02:26 - Deconstructing and Decoupling Reuse Goals 08:36 - Having Seams in Your Code to Avoid Conflict 8 Patterns to Help You Destroy Massive View Controller 11:35 - The Deconstructing Mindset (Finding Reuse Patterns) The Rule of Three Inheritance 17:48 - The Decorator Pattern 18:43 - Categories 21:34 - Sharing UI (User Interface) Codes 23:55 - Mechanics of Sharing Code Between Apps Jeffrey Jackson: Private Cocoapods CocoaPods Guide: Podspec Syntax Reference 29:02 - Lessons Learned: Easy Ways/Patterns to Know When to Break Up Small Functionalities Separate as Soon As Possible Do a Local Pod Using the Path Option (Path is Your Friend!) CocoaPods Guide: Private Pods Have a Good Code Review Process 33:23 - Cocoapods: Commit to Source or Not? 39:59 - Team Collaboration Spotify [YouTube] Kent Beck: Software G Forces: The Effects of Acceleration Picks Refactoring: Improving the Design of Existing Code by Martin Fowler (Pete) Working Effectively with Legacy Code by Michael Feathers (Pete) Refactoring To Patterns by Joshua Kerievsky (Pete) WWDC 2010 Session 138: API Design for Cocoa and Cocoa Touch (Andrew) [Slides] Michele Titolo: Cocoa Design Patterns in Swift (Andrew) The Cocotron (Andrew) Matt Gallagher: Design of a multi-platform app using The Cocotron (Andrew) Zombie Monkie by Tallgrass Brewing Company (Jaim) Getting out and participating in programming language communities (Chuck) The Earthsea Cycle Series Book Series by Ursula K. Le Guin (Chuck) The Pixar Touch by David A. Price (Chuck) 8 Patterns to Help You Destroy Massive View Controller (Michele) Artsy - iOS at Scale - objc.io issue #22 (Michele)

Hans, Schepp und Stefan erzählen diesmal von ihren Erfahrungen in der Zusammenarbeit zwischen Backend und Frontend Entwicklern bei Schnittstellendefinitionen. [00:00:16] News YUI Yahoo stellt die Entwicklung des in die Jahre gekommenen YUI Frameworks ein. Bei der künftigen Technologiewahl durchaus zu berücksichtigen. Schaunotizen [00:01:06] Schnittstellendesign Schepp und Stefan resümieren über ein paar Tools für Entwickler, die […]

The panelists discuss mobile backend services, API design & hypermedia with Stewart Gleadow.

The panelists discuss mobile backend services, API design & hypermedia with Stewart Gleadow.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about the latest in web design, web development, html5, front end development, and more.

In this episode of The Treehouse Show, Nick Pettit (@nickrp) and Jason Seifer (@jseifer) talk about the latest in web design, web development, html5, front end development, and more.

Designing APIs - from the REPL to Application Clojure after the honeymoon ( pdf slides ) Database Migrations dbng from Mark Derricutt git-migration experiment also from Mark Derricutt MyBatis Migrations Liquibase

Scott sits down with Jonathan Carter to brainstorm about optimizing APIs for programmer happiness, rather than programmer productivity.

This episode is a discussion with Jim Des Rivieres about APIs: How to design good APIs, the role of the documentation/specification in APIs, API evolution and other relevant topics.

This episode is a discussion with Jim Des Rivieres about APIs: How to design good APIs, the role of the documentation/specification in APIs, API evolution and other relevant topics.

This episode is a discussion with Jim Des Rivieres about APIs: How to design good APIs, the role of the documentation/specification in APIs, API evolution and other relevant topics.