API Intersection

API Intersection

By StoplightBusinessTechnology
Download on the App Store

API Intersection episodes

  • Developing internal standards for APIs feat. Stève Sfartz, Principal Architect at Cisco

    When Stève Sfartz joined Cisco’s DevNet after decades of experience in technical programs management, enterprise transformation, and software architecture, he was skeptical about the value of establishing standards and scoring for API developers. 


    Today, he is a passionate advocate of the value and long-term benefits to be gained from building not one- but two-level standards to ensure consistency, enhance API value, and optimize developer community experience.  


    In this episode, Stève explains how cloud computing changed the landscape of API development by breaking traditional silos and forcing developers to think in terms of sustainable project and industry growth instead of remaining focused on a single API project.


    He also shares insight into both the long-term benefits of establishing internal development standards and scoring as well as some tips on what to measure and how to measure it.

    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/

    47 min
  • Prioritizing Security From the Start feat. Isabelle Mauny, Field CTO at 42Crunch

    Although security may not be the first thing that comes to mind when building a great API, it can catch up to you faster than you can say data breach. That’s why Isabelle Mauny, field CTO and co-founder of API security platform 42Crunch, does what she does.

    Despite the advances in attitudes towards API security, Isabelle says it’s still undervalued. Look at your team and see if she’s right: If you have, say, 100 developers and only one person dedicated to security, you may need to adjust your prioritization. 

    No matter the ratio, the development and security teams will have to work together to find a balance between their respective goals. Security shouldn’t put limitations on the developers’ aims. But developers need to know that what they’re building can withstand poking and prodding if they don’t want it taken apart.

    On this episode of API Intersection, Isabelle explains the most important factors in creating a secure API, why internal APIs can be just as complex as external APIs, and the impact of scaling.

    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/

    44 min
  • Putting Empathy Into APIs feat. Matthew Reinbold, API Design Architect

    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/

    59 min
  • This Is API Intersection
    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.
    3 min

About API Intersection

From the publisher's feed

Building a successful API requires more than just coding.