We tend to call it Developer portal, but in reality we have to address many more stakeholders than “just” developers. Especially when your APIs are linked to a complex (although market-leading!) B2B trade insurance product. We give it a try…
Two years ago, Adyen realized the Swagger UI wasn’t meeting their needs... so they decided to build their own. We’ll share how we designed and built our new API Explorer - making it more extendable, and easier for Developers and Technical Writers to maintain. We’ll also talk about our future plans, including open sourcing it for the community.
The talk covers Onfido's journey as a company from developer-led documentation to a full-time holistic focus on Developer Experience— and what that means for us. Some examples are achieving consistency across our API client libraries and moving on from OpenAPI-generated libraries, trialling a documentation-led approach for developing the newest version of the Onfido API, and separating our product and technical documentation without compromising on user experience.
Leveraging API Docs and Tools at Mercedes-Benz /developersPronovix
Mercedes-Benz has launched a developer portal to engage developers and unlock new ideas using Mercedes-Benz digital assets and data. Over time, the portal has grown to include 15 public APIs and additional private APIs, SDKs, and tools to help developers build applications. The portal provides documentation, code samples, tutorials and other resources to help audiences beyond just developers, including businesses. Mercedes-Benz aims to continue expanding its API ecosystem and improving documentation, tools and processes to better manage the product lifecycle and leverage its business value.
Many of us have heard about Docs As Code. Applying the same tooling and delivery CI/CD (Continuous Integration and Continuous Delivery) pipelines as developers to improve the quality of (API) documentation sounds nifty. We’ll take a look at the philosophy, best practices and how to get started.
Your customers’ success depends not just o running Hello World, but using your API in a complete app to accomplish a business goal. Getting started is definitely important, but it’s just the first step towards the customers’ ultimate goal: getting finished! Let me help you help them finish!
Most of us are not going to change the world. Don’t let that stop you. You can still change the way APIs are created in your community, and reap the benefits of the spec-first design approach. Be the hero your community needs and your APIs deserve.
Imagine a place where a lone technical writer is creating API specs by hand, from scratch, for a bunch of existing APIs. A place where developers don’t know if an API exists at all because there’s no documentation for it. Where product owners design new APIs in a single Excel spreadsheet.
Places like that exist; maybe you’ve experienced something similar first-hand. Perhaps you thought to yourself, “I wish I could turn this place around”. And you can. You’re not “just a technical writer” - your perspective, insight, and skills are crucial for not just documenting, but also designing and developing usable APIs.
In this talk, you will hear some ideas for what technical writers can do to make their job documenting APIs easier and collaboration with stakeholders stronger. We will look at the benefits of the spec-first approach, strategies for implementing it, and challenges you may encounter. A real-world example of building a spec-first API culture within a company will illustrate how long it took, what worked (and what didn’t), and where improvement is still needed.
The goal is to equip technical writers with advice and motivation to start influencing API design decisions in their community. Documentarians represent the voice of the user to a great extent, but this voice is not always heard. Luckily, it’s not too late to change that.
From Zero to Sixty: Driving a DocOps Based Approach to APIs at Ford Motor Com...Pronovix
How does a 115 year old automaker transform into a Mobility company? Platform Enablement! The session take a look under the hood at Ford and will highlight Ford’s ongoing journey into building and cultivating a DocOps and developer centric approach to APIs.
INTERFACE, by apidays - API Design is where culture and tech meet each other...apidays
INTERFACE, by apidays 2021 - It’s APIs all the way down
June 30, July 1 & 2, 2021
API Design is where culture and tech meet each other
Aleksei Akimov, Head of API at Adyen
Two years ago, Adyen realized the Swagger UI wasn’t meeting their needs... so they decided to build their own. We’ll share how we designed and built our new API Explorer - making it more extendable, and easier for Developers and Technical Writers to maintain. We’ll also talk about our future plans, including open sourcing it for the community.
The talk covers Onfido's journey as a company from developer-led documentation to a full-time holistic focus on Developer Experience— and what that means for us. Some examples are achieving consistency across our API client libraries and moving on from OpenAPI-generated libraries, trialling a documentation-led approach for developing the newest version of the Onfido API, and separating our product and technical documentation without compromising on user experience.
Leveraging API Docs and Tools at Mercedes-Benz /developersPronovix
Mercedes-Benz has launched a developer portal to engage developers and unlock new ideas using Mercedes-Benz digital assets and data. Over time, the portal has grown to include 15 public APIs and additional private APIs, SDKs, and tools to help developers build applications. The portal provides documentation, code samples, tutorials and other resources to help audiences beyond just developers, including businesses. Mercedes-Benz aims to continue expanding its API ecosystem and improving documentation, tools and processes to better manage the product lifecycle and leverage its business value.
Many of us have heard about Docs As Code. Applying the same tooling and delivery CI/CD (Continuous Integration and Continuous Delivery) pipelines as developers to improve the quality of (API) documentation sounds nifty. We’ll take a look at the philosophy, best practices and how to get started.
Your customers’ success depends not just o running Hello World, but using your API in a complete app to accomplish a business goal. Getting started is definitely important, but it’s just the first step towards the customers’ ultimate goal: getting finished! Let me help you help them finish!
Most of us are not going to change the world. Don’t let that stop you. You can still change the way APIs are created in your community, and reap the benefits of the spec-first design approach. Be the hero your community needs and your APIs deserve.
Imagine a place where a lone technical writer is creating API specs by hand, from scratch, for a bunch of existing APIs. A place where developers don’t know if an API exists at all because there’s no documentation for it. Where product owners design new APIs in a single Excel spreadsheet.
Places like that exist; maybe you’ve experienced something similar first-hand. Perhaps you thought to yourself, “I wish I could turn this place around”. And you can. You’re not “just a technical writer” - your perspective, insight, and skills are crucial for not just documenting, but also designing and developing usable APIs.
In this talk, you will hear some ideas for what technical writers can do to make their job documenting APIs easier and collaboration with stakeholders stronger. We will look at the benefits of the spec-first approach, strategies for implementing it, and challenges you may encounter. A real-world example of building a spec-first API culture within a company will illustrate how long it took, what worked (and what didn’t), and where improvement is still needed.
The goal is to equip technical writers with advice and motivation to start influencing API design decisions in their community. Documentarians represent the voice of the user to a great extent, but this voice is not always heard. Luckily, it’s not too late to change that.
From Zero to Sixty: Driving a DocOps Based Approach to APIs at Ford Motor Com...Pronovix
How does a 115 year old automaker transform into a Mobility company? Platform Enablement! The session take a look under the hood at Ford and will highlight Ford’s ongoing journey into building and cultivating a DocOps and developer centric approach to APIs.
INTERFACE, by apidays - API Design is where culture and tech meet each other...apidays
INTERFACE, by apidays 2021 - It’s APIs all the way down
June 30, July 1 & 2, 2021
API Design is where culture and tech meet each other
Aleksei Akimov, Head of API at Adyen
Want some practical ways to benchmark the launch or improvement of your developer portal? As an expert in technical communication, APIs, and developer experience, I’ll share ways to increase your digital presence to engage and compel your audience to keep coming back for more!
The document discusses embedding an API-as-a-product culture within an organization. It addresses common resistance to thinking of APIs as products and provides tips for product managers to establish APIs as true products. This includes establishing frameworks, guidelines and governance around API design, development and management. Leadership support is key to ensuring adherence to processes and a long-term focus is needed to fully embed an API-as-a-product mindset.
apidays LIVE Paris 2021 - Test developer experience, not code by Kathrine Osa...apidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Test developer experience, not code
Kathrine Osadchenko, API Technical Writer & Content Developer at WIX.com
apidays LIVE Paris 2021 - Building an analytics API by David Wobrock, Botifyapidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Building an analytics API
David Wobrock, Senior Lead API Engineer at Botify
INTERFACE, by apidays - Low code APIs that don't break by Zdenek Nemec, Supe...apidays
This document discusses how to prevent APIs from breaking by decoupling clients and servers. It recommends:
1. Programming clients for business capabilities rather than technical API details to reduce dependencies on any single API.
2. Representing capabilities, not internal systems, in APIs to minimize the need for changes.
3. Following best practices like defensive programming, retry policies, and redundancy to make clients more resilient to potential API issues.
This approach aims to dramatically reduce codebases, documentation needs, and downtime while increasing API client resilience and competition between providers.
An Inside Look at a Large-scale Writer-driven REST API Doc Solution at Salesf...Pronovix
23 different REST APIs, 26+ teams, 150+ writers — how we built a unified solution. In this session, hear the inside story of how a handful of writers developed a REST API doc solution and earned the trust of executives and engineering teams across Salesforce along the way.
apidays LIVE Australia 2021 - Confessions of a Product Geek : My First API BY...apidays
apidays LIVE Australia 2021 - Accelerating Digital
September 15 & 16, 2021
Confessions of a Product Geek : My First API
Rosemary Missier, Product Manager at Xero
apidays LIVE Paris - How to position the API driven Architecture to support t...apidays
apidays LIVE Paris - Responding to the New Normal with APIs for Business, People and Society
December 8, 9 & 10, 2020
How to position the API driven Architecture to support the digital transformation?
Jarvis Ka, Enterprise Architect at Indiana Farm Bureau Insurance
[WSO2Con EU 2018] APIs - Technology That Can Transform Your Business Into a P...WSO2
This presentation focuses on how an organization would work on a successful API strategy that aligns with their business vision. We will use best practices and case studies from WSO2 deployments as well as public case studies.
iFlair is a leading web development company specialized in CodeIgniter development. They have a team of professional developers that can deliver designs and applications to meet client requirements. iFlair has delivered over 500 CodeIgniter projects for clients ranging from small companies to large enterprises, offering services such as CodeIgniter website development, application development, ecommerce development, and more. They can hire expert CodeIgniter developers at affordable prices for all web and mobile app needs.
apidays LIVE India - The link between technical documentation and developer e...apidays
Developer documentation and developer relations both aim to educate and engage developers. While multimedia content like videos are commonly used in user documentation, they can also be effective in developer documentation. Videos can demonstrate API demos, explain the purpose of an API, or provide usage scenarios. Developer relations teams support developers through various educational resources including multimedia content, blogs, events and more. Incorporating more multimedia content into developer documentation may help educate engineers and increase engagement, just as developer relations efforts do.
apidays LIVE LONDON - Lessons learnt supporting developer communities by Math...apidays
apidays LIVE LONDON - The Road to Embedded Finance, Banking and Insurance with APIs
Lessons learnt supporting developer communities
Mathieu Pincovai, Customer Success Specialist at Amadeus for Developers
The motivation on why and when to use API-First service design. What are the real-life poblems in application development with regard to API's ? And how to solve these using tools like Swagger Editor , Swagger UI and Swagger-codegen. And how can an API Manager tool help to manage the Apllication Lifecycle of your API ( publishing , versioning, registration of consumers , quota's and rate-limiting )
1. The document discusses the importance of companies dogfooding or using their own APIs internally to improve API design and catch issues.
2. It recommends that development teams should only communicate with each other through API interfaces and these interfaces should be designed from the beginning to be externalizable.
3. The document also provides tips for API design such as using versioning, consistent behavior, simplicty, standards, caching and personalized onboarding to improve APIs and user experience.
apidays LIVE Paris - Level up: Autonomous Integration Mesh by Zdenek Nemecapidays
apidays LIVE Paris - Responding to the New Normal with APIs for Business, People and Society
December 8, 9 & 10, 2020
Level up: Autonomous Integration Mesh
Zdenek Nemec, Founder and CTO at Superface.ai
apidays LIVE Jakarta - What will the next generation of API Portals look like...apidays
apidays LIVE Jakarta 2021 - Accelerating Digitisation
February 24, 2021
What will the next generation of API Portals look like?
Allan Knabe, API Product Manager & Co-founder at apiable.io
Bulletproofing Your APIs: Why Users’ Feedback MattersPronovix
This document discusses the importance of gathering user feedback throughout the API development process. It recommends conducting user interviews early on to understand needs and frustrations. It also suggests usability testing the API prototype to observe how users interact with it and identify issues. Throughout the development stages of concept, design, build, and manage, gathering feedback through methods like card sorting, beta testing, hackathons, surveys, and support channels can help validate the business, refine the product roadmap, and build a strong developer community. The overall message is that listening to users will help uncover blind spots and guide the API design in a positive direction.
apidays LIVE Australia 2021 - Designing Embedded Platforms by Jeremy Glassenb...apidays
apidays LIVE Australia 2021 - Accelerating Digital
September 15 & 16, 2021
Designing Embedded Platforms: Lessons from Industry Success & Failure
Jeremy Glassenberg, Product Lead, APIs at Docusign
apidays LIVE London 2021 - Human-centred API Governance by Arnaud Lauret, Nat...apidays
apidays LIVE London 2021 - Reaching Maximum Potential in Banking & Insurance with API Mindset
October 27 & 28, 2021
APIs in Finance: The Next Evolution
Human-centred API Governance
Arnaud Lauret, Senior API Architect at Natixis & Author of "Design of Web APIs"
apidays LIVE LONDON - Revolut Marketplace & APIs by Stijn Pieperapidays
apidays LIVE LONDON - The Road to Embedded Finance, Banking and Insurance with APIs
Revolut Marketplace & APIs
Stijn Pieper, Lead Product Owner at Revolut
Want some practical ways to benchmark the launch or improvement of your developer portal? As an expert in technical communication, APIs, and developer experience, I’ll share ways to increase your digital presence to engage and compel your audience to keep coming back for more!
The document discusses embedding an API-as-a-product culture within an organization. It addresses common resistance to thinking of APIs as products and provides tips for product managers to establish APIs as true products. This includes establishing frameworks, guidelines and governance around API design, development and management. Leadership support is key to ensuring adherence to processes and a long-term focus is needed to fully embed an API-as-a-product mindset.
apidays LIVE Paris 2021 - Test developer experience, not code by Kathrine Osa...apidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Test developer experience, not code
Kathrine Osadchenko, API Technical Writer & Content Developer at WIX.com
apidays LIVE Paris 2021 - Building an analytics API by David Wobrock, Botifyapidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Building an analytics API
David Wobrock, Senior Lead API Engineer at Botify
INTERFACE, by apidays - Low code APIs that don't break by Zdenek Nemec, Supe...apidays
This document discusses how to prevent APIs from breaking by decoupling clients and servers. It recommends:
1. Programming clients for business capabilities rather than technical API details to reduce dependencies on any single API.
2. Representing capabilities, not internal systems, in APIs to minimize the need for changes.
3. Following best practices like defensive programming, retry policies, and redundancy to make clients more resilient to potential API issues.
This approach aims to dramatically reduce codebases, documentation needs, and downtime while increasing API client resilience and competition between providers.
An Inside Look at a Large-scale Writer-driven REST API Doc Solution at Salesf...Pronovix
23 different REST APIs, 26+ teams, 150+ writers — how we built a unified solution. In this session, hear the inside story of how a handful of writers developed a REST API doc solution and earned the trust of executives and engineering teams across Salesforce along the way.
apidays LIVE Australia 2021 - Confessions of a Product Geek : My First API BY...apidays
apidays LIVE Australia 2021 - Accelerating Digital
September 15 & 16, 2021
Confessions of a Product Geek : My First API
Rosemary Missier, Product Manager at Xero
apidays LIVE Paris - How to position the API driven Architecture to support t...apidays
apidays LIVE Paris - Responding to the New Normal with APIs for Business, People and Society
December 8, 9 & 10, 2020
How to position the API driven Architecture to support the digital transformation?
Jarvis Ka, Enterprise Architect at Indiana Farm Bureau Insurance
[WSO2Con EU 2018] APIs - Technology That Can Transform Your Business Into a P...WSO2
This presentation focuses on how an organization would work on a successful API strategy that aligns with their business vision. We will use best practices and case studies from WSO2 deployments as well as public case studies.
iFlair is a leading web development company specialized in CodeIgniter development. They have a team of professional developers that can deliver designs and applications to meet client requirements. iFlair has delivered over 500 CodeIgniter projects for clients ranging from small companies to large enterprises, offering services such as CodeIgniter website development, application development, ecommerce development, and more. They can hire expert CodeIgniter developers at affordable prices for all web and mobile app needs.
apidays LIVE India - The link between technical documentation and developer e...apidays
Developer documentation and developer relations both aim to educate and engage developers. While multimedia content like videos are commonly used in user documentation, they can also be effective in developer documentation. Videos can demonstrate API demos, explain the purpose of an API, or provide usage scenarios. Developer relations teams support developers through various educational resources including multimedia content, blogs, events and more. Incorporating more multimedia content into developer documentation may help educate engineers and increase engagement, just as developer relations efforts do.
apidays LIVE LONDON - Lessons learnt supporting developer communities by Math...apidays
apidays LIVE LONDON - The Road to Embedded Finance, Banking and Insurance with APIs
Lessons learnt supporting developer communities
Mathieu Pincovai, Customer Success Specialist at Amadeus for Developers
The motivation on why and when to use API-First service design. What are the real-life poblems in application development with regard to API's ? And how to solve these using tools like Swagger Editor , Swagger UI and Swagger-codegen. And how can an API Manager tool help to manage the Apllication Lifecycle of your API ( publishing , versioning, registration of consumers , quota's and rate-limiting )
1. The document discusses the importance of companies dogfooding or using their own APIs internally to improve API design and catch issues.
2. It recommends that development teams should only communicate with each other through API interfaces and these interfaces should be designed from the beginning to be externalizable.
3. The document also provides tips for API design such as using versioning, consistent behavior, simplicty, standards, caching and personalized onboarding to improve APIs and user experience.
apidays LIVE Paris - Level up: Autonomous Integration Mesh by Zdenek Nemecapidays
apidays LIVE Paris - Responding to the New Normal with APIs for Business, People and Society
December 8, 9 & 10, 2020
Level up: Autonomous Integration Mesh
Zdenek Nemec, Founder and CTO at Superface.ai
apidays LIVE Jakarta - What will the next generation of API Portals look like...apidays
apidays LIVE Jakarta 2021 - Accelerating Digitisation
February 24, 2021
What will the next generation of API Portals look like?
Allan Knabe, API Product Manager & Co-founder at apiable.io
Bulletproofing Your APIs: Why Users’ Feedback MattersPronovix
This document discusses the importance of gathering user feedback throughout the API development process. It recommends conducting user interviews early on to understand needs and frustrations. It also suggests usability testing the API prototype to observe how users interact with it and identify issues. Throughout the development stages of concept, design, build, and manage, gathering feedback through methods like card sorting, beta testing, hackathons, surveys, and support channels can help validate the business, refine the product roadmap, and build a strong developer community. The overall message is that listening to users will help uncover blind spots and guide the API design in a positive direction.
apidays LIVE Australia 2021 - Designing Embedded Platforms by Jeremy Glassenb...apidays
apidays LIVE Australia 2021 - Accelerating Digital
September 15 & 16, 2021
Designing Embedded Platforms: Lessons from Industry Success & Failure
Jeremy Glassenberg, Product Lead, APIs at Docusign
apidays LIVE London 2021 - Human-centred API Governance by Arnaud Lauret, Nat...apidays
apidays LIVE London 2021 - Reaching Maximum Potential in Banking & Insurance with API Mindset
October 27 & 28, 2021
APIs in Finance: The Next Evolution
Human-centred API Governance
Arnaud Lauret, Senior API Architect at Natixis & Author of "Design of Web APIs"
apidays LIVE LONDON - Revolut Marketplace & APIs by Stijn Pieperapidays
apidays LIVE LONDON - The Road to Embedded Finance, Banking and Insurance with APIs
Revolut Marketplace & APIs
Stijn Pieper, Lead Product Owner at Revolut
Success of foreign investment attraction by outsource/service companies.ITEM
This document provides information about Zazmic, a software development company, and their team productivity tool called Z-Stream that was built on Google Cloud Platform (GCP). It discusses Zazmic's motivation for building their own product, some of their clients and projects, their core engineering competencies including cloud, AI and mobile, and their Google Cloud skills and partnership. It also briefly touches on incubators within large service companies and foreign investment in Ukraine.
Nur durch qualitativ hochwertiges und zielgerichtetes API Management können lebendige API-Ökosysteme geschaffen werden. Diese API-Ökosysteme bieten Unternehmen die Chance ihre IT-Assets optimal an interne und externe Stakeholder anzubinden. Dadurch bietet sich ein hohes Potenzial, Unternehmen können sowohl bestehende IT-Systeme optimieren als auch komplett neue Geschäftsideen und Partnerschaften umsetzen. Doch was bedeutet qualitativ hochwertiges und zielgerichtetes API Management? Und wie kann man die Integration in bestehende, stark regulierte IT Landschaften schaffen und dabei Mehrwert für interne Beteiligten als auch externe Partner generieren? Wir stellen unseren Ansatz und Erfahrungen mit der SaaS Plattform und API Marketplace 'Syncier Marketplace' vor und gehen auf die Herausforderungen in der Versicherungsbranche ein.
apidays LIVE Australia 2020 - API Value Chain by Christian Raquelapidays
apidays LIVE Australia 2020 - Building Business Ecosystems
API Value Chain - Identifying and developing business assets that deliver the most value
Christian Raquel, Director - Engineering at Industrie & Co
The OLB Group is a FinTech company offering a suite of product
solutions in the merchant services and payment facilitator verticals,
including a cloud-based omni-channel commerce platform for SMBs,
electronic payment processing, and crowd funding services for
issuers and broker/dealers.
Best of NOAH 16 London Startups - Presentation by Brian Smillie, Founder & CEO and Roger Gosine, Co-Founder of Beezer at the NOAH Conference Berlin 2017, Tempodrom on the 23rd of June 2017.
Observability with Elastic at Audi Business InnovationElasticsearch
In the automotive world, time to market and innovation are critical. This includes digital solutions driven by software teams. Audi Business Innovation (ABI), a subsidiary of AUDI AG, uses Elastic to provide observability as a service to all developers within the VW-Group, helping them rapidly bring digital solutions to market. Learn how Elasticsearch Service helps them focus on delivering value to their customers, while saving time and costs.
This document provides an overview of Prodyna, an IT consulting company with 320 employees across Europe. It summarizes Prodyna's financial information, locations, business areas in conception, development and training. It also outlines Prodyna's portfolio of partners and technologies to support clients' digital transformations. The presentation concludes by listing some of Prodyna's reference customers across various industries.
ADFILE is a cloud based workflow management system created for time-based businesses to track jobs from lead generation through to invoicing, reducing paperwork and giving back valuable time.
Open APIs - Open Banking - Digital Transformation WSO2
Technology continues to be a driving force behind the progression and innovation of the financial services sector. The UK’s Open Banking initiative, coupled with recent legislative changes, will give customers greater clarity, control and ownership of their data, opening the sector to further innovation.
This session was presented by Seshika Fernando, Head of Financial Solutions at WSO2 at Tech UK's event on Open Banking, PSD2 and the Cyber Challenges Facing the Financial Services Sector
Adeptical Solutions is an IT company that provides efficient and scalable technology solutions. They offer services including mobile app development, cloud services, product development, open source customization, and consultancy. Their clients include companies in various industries like finance, ecommerce, shipping, and more. Adeptical has experience across technologies like Java, PHP, Python, and platforms like AWS, Azure, and has expertise in Agile methodology.
Adeptical Solutions is a leading IT consultancy, offshore product development, architecture optimization, and website design & development firm based out of India. Our rich domain expertise keeps us going and providing better value to our clients.
Bankir.ru 22.03.2017
Life.SREDA VC is a venture capital firm that has made 13 investments in companies located in the US, UK, Germany and CIS countries, with 7 successful exits. It has also made 8 investments in Southeast Asia. The firm is launching a new venture fund focused on blockchain investments and operates accelerators and co-working spaces for fintech projects in Singapore and Kazan.
1) The document discusses integrating Primavera and SAP software at Selex ES, an Italian defense company, to better manage projects.
2) An initial implementation in 2006 used Primavera and SAP R/3 via an SDK. In 2008, interfaces were developed between Primavera, SAP BW, and SAP SEM using APIs and Websphere.
3) By 2010, Primavera was integrated with SAP MRP to share work breakdown structures, resource assignments, actual costs and units, operation planning, and forecasts between the two systems for improved project timeframe and cost control.
Alpine 4 Technologies is a holding company that acquires companies in diverse industries. It currently has three subsidiaries - ALTIA, Quality Circuit Assembly, and Venture West Energy Services. Alpine 4's strategy is to acquire companies that are drivers of growth, stabilizers with consistent revenue, or facilitators that enhance synergies. It is pursuing acquisitions of Lattice, Build Block, Ardent Systems, and UMC Print to add an estimated $31 million in annual revenue in 2018. Alpine 4 aims to reach $107 million in annualized revenue by the end of 2018 through organic growth of existing subsidiaries and new acquisitions.
What's the right funding option for your Salesforce biz? Watch this webinar and hear directly from investors at Emergence Capital & Lighter Capital.
Learn which funding options best suit each stage of the business growth cycle - from startup through the $10M revenue milestone - and what to consider when evaluating those options for your business.
5 Key Success Factors in Building a SaaS Business in GermanySaaStock
The document summarizes 5 traps to avoid when building a SaaS business:
1. Choosing the wrong customers from the beginning and focusing on top-down sales instead of building a customer base from the bottom-up.
2. Having the wrong mindset, especially outdated sales and marketing approaches that fail in the current SaaS market.
3. Lacking proper architecture like not following an API-first approach.
4. Lacking focus and trying to operate all business processes instead of concentrating on the core competence.
5. Lacking scalability by not automating processes soon enough or offering the right payment methods based on business volume. Automation and payments should scale as the
By the time they're reading the docs, it's already too latePronovix
Your relationship with a developer begins before they even know your product's name. In fact, before they know they need a product like yours.
In this talk, Matthew will make the case that developer marketing, developer experience, and developer education are part of a continuum. And that if you're thinking of documentation as something that happens only after someone has signed-up for your API, then you're leaving it too late. He'll draw on pedagogical and marketing research to propose a model for the developer learning journey where traditional API documentation is just one stop along the way.
Attend this talk and you'll come away with practical ideas for how to start educating developers earlier in their product evaluation and learning journey.
Optimizing Dev Portals with Analytics and FeedbackPronovix
Making informed decisions on which features to prioritize in a developer portal can be a daunting task. In this session, we'll show you how to leverage experiments, data, and user feedback to evaluate their potential and refine your approach. We'll explore how testing ideas with minimal investment, akin to an MVP, can help you avoid building features that don't meet your users' needs.
Success metrics when launching your first developer portalPronovix
Building our a developer portal may seem easy at the onset with off the shelf options, but when you're building a custom portal to match the needs of your company, it's not as easy. In this session, we'll talk about our process in determining the right places to start with success metrics and features through an early stage feedback back before having customers. You'll see our intention is to tell a story with multiple facets for multiple people, developers, product managers, C suite decision makers etc... Stories around API usage, health, cost, errors and support to provide our users with an overall of their business performance through our APIs.
This document discusses challenges with API integration and proposes augmented approaches using AI. It notes that API integration takes a long time on average of 700 days due to difficulties understanding documentation, requirements, and ecosystems. Common obstacles include domain modeling, use cases, documentation quality, and access issues. The document advocates improving documentation to explain business and product aspects beyond technical references. It envisions next-gen integration using AI like NLP to help analyze APIs and generate integration code on demand. This could enhance documentation with interactive capabilities and help applications autonomously discover and connect APIs.
Making sense of analytics for documentation pagesPronovix
As content producers, we invest considerable time and effort in developing, packaging, and delivering content that we think our users need. After publishing the content, we hope that users find our content useful. And we often wonder how users really navigate and consume our content. Web page analytics can help us gauge the information needs of our customers, assess their content consumption behavior, and find opportunities to improve our content and how we deliver it.
Kumar explores the basics of web analytics, pitfalls of relying too much on web analytics for important decisions, the typical web analytics process, and he will share some guidelines for interpreting web analytics numbers.
Feedback cycles and their role in improving overall developer experiencesPronovix
Drawing from experiences from open source work and her time at Spotify, Serah’s talk cover the challenges, opportunities and hacks around proactive and reactive monitoring, processing, tracking and acting on stakeholder and community feedback, and argue for the centricity of well-defined feedback loops in improving the overall developer experiences for any product and features you are responsible for.
GraphQL Isn't An Excuse To Stop Writing DocsPronovix
The main goal of API documentation is to help developers understand how to use an API. With GraphQL, developers often assume it's self-documenting capabilities are sufficient for anyone that consumes their GraphQL API. But did you ever validate this?
Good API documentation offers both static and interactive ways to learn how to consume the API. API's that support GraphQL often only come with interactive documentation, in the shape of a GraphiQL Playground. However, the first time you (or your users) use a GraphQL API can be very frustrating as GraphQL APIs typically only have an interactive playground. it increases the complexity for newcomers to GraphQL as it assumes you’re already familiar with GraphQL. But with GraphQL, you’re not limited to just an interactive playground, as you can create static or interactive documentation next to having this playground. This talk explores which forms of documentation you can use and how they add value to your GraphQL API.
This document provides guidance for writing documentation about Web3 technologies. It begins with an introduction to the author and their background in technical writing. The document then discusses what Web3 is and how it differs from Web2. It emphasizes that Web3 documentation should use familiar formats from Web2, include detailed examples and code snippets, and use clear language to explain challenging new concepts. Constant research is important given the rapidly evolving nature of Web3 projects. The goal of documentation is to accelerate understanding and adoption of new decentralized technologies.
Why your API doesn’t solve my problem: A use case-driven API designPronovix
API docs frequently fail to address developers’ needs by omitting common usage scenarios and use cases. Let’s take a look at good and bad practices for documenting API use cases, and take steps to ensure that developers get from our API and docs what they really want.
You wrote an API specification, documented your endpoints, and published SDKs. Here’s a question, though: Does your API actually solve your users’ problems?
API providers often fail to address common use cases to solve users’ needs, or their assumptions don’t match the reality. This may end up in frustration and loss of users.
In this talk, we will take a peek into developers’ mindset. I will show how to better understand the developers’ needs by researching the usage patterns, existing libraries and 3rd party experience layers, provide examples of good and bad practices, and suggest actionable steps to improve developer experience for your API.
At times, you have to build docs that cover not only REST-y APIs but also frontend SDKs. What do you do, when you have to offer docs for multiple such SDKs, based on different frameworks, under rapid, uncoordinated development with multiple feature enhancements per iteration and at times, with breaking changes, but versioned and searchable?
Developing a best-in-class deprecation policy for your APIsPronovix
Nobody likes ambiguity—especially when it comes to the stability of APIs and the expectations for availability long term. Avoid common pitfalls and explore a critical area where trust is built with developers through thoughtful policy and the development of best-in-class documentation.
A good deprecation policy involves a lot of forward thinking and an awareness of how developers or end users are currently leveraging your capabilities, and how a given API or feature deprecation could affect them in the future. The hard-earned trust that you’ve built and maintained with these individuals is at risk with any type of policy or documentation that is unclear.
The road to developing a clear, trustworthy deprecation policy is a multi-faceted initiative with input from product, engineering, customer success and other cross-functional teams, as well as external market awareness.
Knowing which voices to have in the room, what the industry standards are, and formulating appropriate communication timelines will ensure a world class policy is developed and documented before it’s needed.
Join us as we dive into the nuances of this process and how to avoid the common pitfalls that come from lacking a strategic, thoughtful approach to documenting a deprecation policy for your APIs.
At MongoDB, we now generate REST API references for MongoDB Atlas from annotations in the product’s source. Our team’s writers proposed, planned, led, and implemented this project–and learned a lot along the way. We’ll share how we got buy-in from engineering and product stakeholders, coordinated the project across teams, implemented swagger-core annotations in Java, and drove positive change to benefit our team, the company, and our users.
What do developers do when it comes to understanding and using APIs?Pronovix
- The document discusses different approaches that developers take to learning APIs: the systematic approach, where developers want to be in control and fully understand what they are doing; the opportunistic approach, where developers quickly experiment and reuse examples; and the pragmatic approach, which combines elements of the first two.
- It also discusses the concept of "flow" in software development and lists some triggers for getting into a state of flow such as clear goals, immediate feedback, and a rich environment.
- The document concludes by asking questions about how to maximize the chance that developers experience flow when using documentation.
Inclusive, Accessible Tech: Bias-Free Language in Code and ConfigurationsPronovix
It's time to take the bias out of code, UI, docs, configurations, or our everyday language by ensuring we choose our words carefully to avoid harmful subtext or exclusion. We can do our part and take steps by examining assets from code to config files to API specifications to standards.
Heard of suss? You can suss out more information or you can find someone's information to be suss. "Suss" shows the flexibility of language. It’s an ongoing process to change how we use certain words. It's important to choose words carefully to convey the correct meaning and avoid harmful subtext or exclusion. Let's explore some of the tools and triage methods that it takes from an engineering viewpoint to make bias-free choices. How can you ensure that biased words do not sneak into code, UI, docs, configurations, or our everyday language?
First, let's walk through how to take an inventory of assets from code to config files to API specifications to standards. Next, by placing those findings into categories, prioritize the work to substitute with inclusive alternatives. Let's examine some examples using both API and code assets. Next is a demonstration of how to automate analyzing your source code or documentation with a linter, looking for patterns based on rules that are fed into the tool.
What's in the future for these efforts? Inclusive language should expand beyond English and North America efforts. To do so, let's organize the work with automation tooling, as engineers do.
Creating API documentation for international communitiesPronovix
How to create documentation and write code for an international audience, not just the people who speak and think like you. Make your APIs more useful for everyone on the planet.
Much of the documentation supplied by both Open Source and Close Souce projects assume the community have a good understanding of the English language and often North American culture as well. This creates barriers for many solution providers, who are the gateway to potentially huge markets for your project.
This talk discusses some of the cultural differences, particularly for people from Asia, in using English language API documentation. It suggests some strategies to help diverse audiences understand you APIs and create solutions using them.
The talk will cover not only differences in language but also other cultural differences that are often not obvious. For example:
Different expectations about publication formats, release processes, levels of support during the development process
Meeting and communications styles
Software development workflows, processes, and tools
Supporting people who are visually impaired will also be briefly discussed.
As well as discussing these issues, specific suggestions will be provided to make API docs accessible for as many people as possible.
This talk is based on Alec's work with customers in Europe, North America, Middle East, Asia, and Australasia. The last five have been spent as a developer evangelist working with PaperCut partners in China, Japan, Korea, US and Europe.
APIs in a modern enterprise are rarely uniform or all of the same type. The multitude of API types can be due to organic growth, mergers and acquisitions, or any number of other reasons. Regardless of their origin, APIs of all types need to be fully documented to facilitate a developer’s journey as they interact with your API ecosystem in order to develop useful applications. In this talk I will show examples of how we have augmented developer portals to document APIs that are not of the REST variety, such as AsyncAPI, GraphQL, SOAP, gRPC, and more, such that all API documentation can seamlessly live side-by-side.
Docs-as-Code: Evolving the API Documentation ExperiencePronovix
We are a software engineering team creating API docs. Docs are authored using Instructional Design principles to narrate use-cases and practical API implementations. This talk shares why & how we've applied software development practices to evolve our document tooling, creation, & delivery methods.
Our APIs describe asynchronous protocols used for embedded software (firmware) components in a digital 2-way radio communications system. The API is protocol data unit (PDU) based and its definition is described in a proprietary format; consequently, well-known API formats, such as Swagger/OpenAPI, or tools, such as doxygen, are not used.
Our product training and technical writing teams are very experienced in Instructional Design methods, but these teams have only written documentation for an end-user audience. Understanding software development processes is equally important as understanding two-way radio networks in order to successfully integrate with the APIs. This is the rationale for having a software engineering team develop the skillsets to write API documentation for a developer audience.
With a solid foundation of API documentation in place, regular examination of engineering efficiency and developer experience is appropriate. Repeated actions can be replaced by automation. Content can be modular and re-usable. Formats can be streamlined for easier consumption. Docs can be made portable and lightweight for faster delivery.
Developer journey - make it easy for devs to love your productPronovix
Ever wonder how some products are just lovable and easy to use while other are not? The good products have optimized onboarding into their ecosystem where you get the information served at the right time.
That’s thanks to developer journey and we will teach you how to get it right!
We will go through the basics such as how to analyze existing and non-existing developer touchpoints, set metrics and optimize them to increase the conversion.
Deliberate Complexity Conferences - 19 JULY 2022
Alicia Juarrero - Complexity is not complicatedness
Professor Alicia Juarrero, a leading complexity theory philosopher and academic, as well as the founder and president of VectorAnalytica, a technology company that specializes in large scale scientific data capture and real time analysis tools. Alicia's work in complexity theory is widely quoted by thought leaders in the technology space and referenced in many recent complexity-informed approaches for managing highly dynamic systems, as well as in knowledge management.
How cognitive biases and ranking can foster an ineffective architecture and d...Pronovix
Deliberate Complexity Conferences - Building Successful Platforms and APIs (29 June). Kenny Baas-Schwegler & Evelyn van Kelle - How cognitive biases and ranking can foster an ineffective architecture and design
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
National Security Agency - NSA mobile device best practices
The API BizDevportal
1. THE BIZDEV
PORTAL
Or “why great Dx is not enough“
London / 9th of Nov 2018
Sophie Rutard
Head of API
Euler Hermes
2. WHO WE ARE – EULER HERMES
▪ B2B insurance, covering companies against loss of
payments since >100 years
▪ Global market leader, with ~850 bn € of global coverage
▪ ~6.000 Employees
▪ Part of Allianz – 2nd largest insurer worldwide
2
3. OUR API BACKGROUND
▪ We released our first API in Germany in 2007 (SOAP)
▪ Adapted it to worldwide needs in 2012 – backed by a
specialist consultancy team
▪ Once our customers have it they’re really happy!
▪ But our current setup isn’t really scalable
3
4. WHAT IS CREDIT INSURANCE?
4
Grey company
Green company
60 days terms
5. HOW DO WE DO IT?
5
Grey company
Green company Risk assessment and
continuous monitoring
THIS IS WHERE THE
API COMES IN!
Individual coverage for each buyer
6. A TYPICAL B2B SALES PROCESS
Prospecting
Mia is using
Salesforce
Sales & Order
mgmt
Katie is using a
bespoke warehouse
mgmt software
Credit mgmt &
accounting
Sabine is using SAP
Debt Collectiont
David is an external
broker, using
bespoke software.
Mark is an external
lawyer, using
bespoke software.
Although working in different departments and systems, all these business experts rely on valid and up-to-date
information provided by Euler Hermes. Our API is made to deliver the data where they need it - real-time.
PhotosbyMarilyTorresfromPexels
< API >
< API >
< API >
< API >
< API >
7. WHAT IT TAKES TO INTEGRATE
OUR API
Mia, Katie, Sabine, Mark
and David are brilliant
business experts.
They want to increase
efficiency, but they don’t
know much about APIs!
PhotosbyMarilyTorres,rawpixel.comandHiteshChoudharyfromPexels
Nina agrees to setup a project
and hire Nitin.
He is a great developer, but he
never heard of credit
insurance before…
They ask Nina for budget.
Being the CEO, Nina
understands the business
case, but she’s not an API
expert. She just needs
facts to agree on funding.
8. KEY REQUIREMENTS - BUSINESS
▪ Non-technical demonstration of the API’s business value
▪ Functional API catalogue
▪ Inspirational usecases beyond the API, helping to improve our
customer’s end-to-end Ux
▪ Support for estimation of project efforts and business case
calculation
▪ Easy communication channel to handle issues and to inform
about functional API enhancements
▪ Clearly defined contacts for 2nd level support
9. KEY REQUIREMENTS - DEVELOPERS
▪ Tutorials: Easy introduction to the business context
▪ Detailed explanation of key legal requirements
(audit proof logs, contractual obligations from the insurance product, etc.)
▪ Highlight business consequences of functional errors
▪ Clear link between API doc and related functional usecases
▪ Plus the usual elements:
▪ API key generation
▪ Functional API documentation
▪ API ref
▪ Sandbox environment
▪ Release notes
▪ Versioning policy
▪ SLA / performance tracking
▪ …
10. THE BIZDEVPORTAL MUST…
Enable a mixed team of biz and IT experts to be autonomous in delivering
something that:
▪ Enhances the end-to-end Ux
▪ Complies with legal requirements
▪ Is backed by professional support when needed
11. MY KEY MESSAGES
1. Know who your stakeholders are. Address them in their language.
2. If the business people don’t buy in, a developer won’t even have a look at
your dev portal.
3. The project will only suceed if developer and biz experts work together; The
BizDevPortal needs to support such collaboration.
12. Sophie Rutard
Head of API@EH
sophie.rutard@eulerhermes.com
LinkedIn: https://www.linkedin.com/in/sophie-rutard-7081baab
Currently hiring an API Senior Analyst
in Paris!
THANK
YOU!