The UX of DX: User Testing in the Invisible World of APIs
•
2 gostaram•135 visualizações
As anyone who has tried to call certain endpoints knows, being RESTful isn’t the only requirement to making your API product easy to use. Developers are people too and as DX experts we owe them the same UX testing we do with our front-end products.
Denunciar
Compartilhar
Denunciar
Compartilhar
Baixar para ler offline
Recomendados
User Testing in the Invisible World of APIs
How you name, design, and structure your APIs all has a huge impact on usability. What you request and what you return in any given call can change your developer’s experience, and so just as we test usability in an app on a phone, we need to test usability of our products. In this session, we’ll cover a few different techniques and strategies you can use to run user testing on your APIs. Learn how to prototype and get quick answers to little questions, as well as how to conduct some more extensive studies to really target future features and major fixes for your product.
How to develop an API ecosystem in the fintech industry from the ground up
In this talk, we are going to explain what we did @ MODO (a new mobile payment solution similar to Bizum) to develop from the ground up a single platform that provides multiple functionalities to the biggest banks in Argentina, using OpenAPI/Swagger and a design-first approach.
Automating the API Product Lifecycle
Looking at the full API Product Lifecycle, from defining an API and implementing the API, to launching with a solid developer site and experience, let’s see the newest tools - and potentially upcoming opportunities - to automate the creation of a solid developer experience.
Creating a successful API requires a proper process from concept and design, through development, and into ongoing maintenance and responsive developer support. As developer expectations for better-quality APIs increase, tools have made it easier to implement this well. Thanks to standards like OpenAPIs, it’s easier to create a quality API, developer site, and overall experience. Many of us create API documentation or code libraries automatically from an OpenAPI spec, but there’s a lot more coming along to make our lives easier, and to make our APIs look better. In reviewing the full API Product Lifecycle to design an API people will use, let’s see the newest tools - and potentially upcoming opportunities - to better automate the creation of a compelling developer program.
Leaping Forward: Finding The Future of Your API Docs
Learn how to scale beyond old choices and find the next big thing for your API documentation. This talk will use the past, present, and future of Marqeta’s docs to provide a framework for growing and evolving your own.
Bulletproofing Your APIs: Why Users’ Feedback Matters
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.
Content Strategy for DevPortals
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!
Why you need a Developer Relations team for your API
Providing a good API product to your users is the minimum. With all the competition developers have many more expectations than quality APIs; developer community, documentation, tutorials, developer tools and this is exactly where the Developer Relations (DevRel) team fits. In this talk we’ll discuss why your API product needs a DevRel team and how it can drastically upgrade the face of your API program and satisfy your users. We’ll talk about how the DevRel team can engage your users to nurture a long-term community and make your API product successful.
apidays LIVE New York 2021 - Why Software Teams Struggle with API Security Te...
apidays LIVE New York 2021 - API-driven Regulations for Finance, Insurance, and Healthcare
July 28 & 29, 2021
Why Software Teams Struggle with API Security Testing
Scott Gerlach, Co-Founder & Chief Security Officer at StackHawk
Recomendados
User Testing in the Invisible World of APIs
How you name, design, and structure your APIs all has a huge impact on usability. What you request and what you return in any given call can change your developer’s experience, and so just as we test usability in an app on a phone, we need to test usability of our products. In this session, we’ll cover a few different techniques and strategies you can use to run user testing on your APIs. Learn how to prototype and get quick answers to little questions, as well as how to conduct some more extensive studies to really target future features and major fixes for your product.
How to develop an API ecosystem in the fintech industry from the ground up
In this talk, we are going to explain what we did @ MODO (a new mobile payment solution similar to Bizum) to develop from the ground up a single platform that provides multiple functionalities to the biggest banks in Argentina, using OpenAPI/Swagger and a design-first approach.
Automating the API Product Lifecycle
Looking at the full API Product Lifecycle, from defining an API and implementing the API, to launching with a solid developer site and experience, let’s see the newest tools - and potentially upcoming opportunities - to automate the creation of a solid developer experience.
Creating a successful API requires a proper process from concept and design, through development, and into ongoing maintenance and responsive developer support. As developer expectations for better-quality APIs increase, tools have made it easier to implement this well. Thanks to standards like OpenAPIs, it’s easier to create a quality API, developer site, and overall experience. Many of us create API documentation or code libraries automatically from an OpenAPI spec, but there’s a lot more coming along to make our lives easier, and to make our APIs look better. In reviewing the full API Product Lifecycle to design an API people will use, let’s see the newest tools - and potentially upcoming opportunities - to better automate the creation of a compelling developer program.
Leaping Forward: Finding The Future of Your API Docs
Learn how to scale beyond old choices and find the next big thing for your API documentation. This talk will use the past, present, and future of Marqeta’s docs to provide a framework for growing and evolving your own.
Bulletproofing Your APIs: Why Users’ Feedback Matters
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.
Content Strategy for DevPortals
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!
Why you need a Developer Relations team for your API
Providing a good API product to your users is the minimum. With all the competition developers have many more expectations than quality APIs; developer community, documentation, tutorials, developer tools and this is exactly where the Developer Relations (DevRel) team fits. In this talk we’ll discuss why your API product needs a DevRel team and how it can drastically upgrade the face of your API program and satisfy your users. We’ll talk about how the DevRel team can engage your users to nurture a long-term community and make your API product successful.
apidays LIVE New York 2021 - Why Software Teams Struggle with API Security Te...
apidays LIVE New York 2021 - API-driven Regulations for Finance, Insurance, and Healthcare
July 28 & 29, 2021
Why Software Teams Struggle with API Security Testing
Scott Gerlach, Co-Founder & Chief Security Officer at StackHawk
apidays LIVE New York 2021 - Designing embedded platforms: Lessons from indus...
apidays LIVE New York 2021 - API-driven Regulations for Finance, Insurance, and Healthcare
July 28 & 29, 2021
Designing embedded platforms: Lessons from industry success & failure
Jeremy Glassenberg, Product Lead, APIs at Docusign
5 Important Considerations For Mobile Application Development Process
The document discusses considerations for mobile app development. It recommends connecting to cloud-based systems to enjoy scalable functionality. It also suggests using component-based development methodologies for flexible, reliable and reusable systems. Additionally, it advises implementing test-driven development by always writing test cases to ensure new functionality works properly. The document emphasizes choosing a mobile app development partner wisely to make crucial decisions associated with app development.
apidays LIVE Australia 2021 - From apps to APIs: how no-code is transforming ...
apidays LIVE Australia 2021 - Accelerating Digital
September 15 & 16, 2021
From apps to APIs: how no-code is transforming the tech industry
Carmen Chung, Senior Product Manager at Linktree
E031202024029
This document discusses the design and development of a Service Oriented Architecture (SOA) interface for mobile device testing. It proposes using a SOA approach to address the challenges of mobile device testing, which is made difficult by the complex and evolving nature of mobile software and hardware. The paper describes building modular components according to SOA principles and using a common interface to allow components to communicate and reuse test cases. It outlines developing fault injection techniques and a taxonomy of faults specific to SOA to test the reliability of the proposed interface. The goal is to create a more flexible and reusable framework for mobile device testing.
{Re}designing a Developer Portal
Your Developer Portal is the primary interface that developers will have with your company’s product. So what does your developer portal say about you? We’ll share what we’ve learned at BigCommerce about redesigning a developer portal that helps your developers–and your company–meet their goals.
Beyond API Spray & Pray: Developer Portals in Digital Transformation
For some organizations digital transformation is “buzzword whack-a-mole”: they chase hype after hype, implement digital platform after platform but never invest enough to really be successful. One of these strategies that I’ve seen up close recently is the “spray & pray API strategy”: build loads of API services and then sell them on an API marketplace. But it is not clear what exactly the product portfolio is, what market is being targeted, or even who the customers will be…
If you build it, they will come - right?
Developer portals can be the backbone for a digital transformation initiative. Providing an interface of interfaces that allows you to build digital platforms, plugin marketplaces, API ecosystems, service aggregators, and procurement switchboards. But to be successful, you need a strategy - your developer portal needs to be more than a dumping ground for API documentation.
In this talk Kristof will share an overview of the different types of developer portals he is currently aware of, and the types of digital transformation tactics they enable. He will use a complexity & systems lens to explain what he thinks is driving the need for digital transformation. Finally, he will explore a deliberate complexity architecture inspired by biology, that organizations can use to become more resilient & adaptive while maintaining efficiency.
Mobile SDK: Considerations & Best Practices
Mobile SDKs are a great way to make your service or API easily consumable by the large number of developers out there looking for state of the art tools to make their apps stand out in the competitive marketplaces, but building a stable, compatible and successful SDK is quite a challenge.
In this talk we the technical and design challenges involved in developing an efficient mobile SDK that is highly compatible with its host mobile app, and the various considerations we took into account and the lessons we’ve learned while designing and building LivePerson’s native mobile SDK.
Engineer Stunning (API) documentation
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.
A Starters Guide to Building APIs with Javascript
Presented by: Tom Wilson, hyper63
Presented at the All Things Open Virtual Meetup
Abstract: APIs (Application Program Interfaces) is how programs can talk with other programs and is a design consideration for many products. Let’s discuss: Why you should build an application with an API? What are the top 5 requirements of designing an API with examples? Some open-source javascript frameworks that can help you design and build your API.
In order to get the most out of this talk, you should have a good understanding of http REST protocol and general application development. Familiarity with javascript and technologies like NodeJS and Express would be a plus.
In this talk, you should come away with a good understanding of why you should consider building an API in your application, key good practices every API should include, and how you could implement an API using Javascript.
apidays LIVE Hong Kong 2021 - Automating the API Product Lifecycle by Jeremy ...
apidays LIVE Hong Kong 2021 - API Ecosystem & Data Interchange
August 25 & 26, 2021
Automating the API Product Lifecycle
Jeremy Glassenberg, Product Lead, APIs at Docusign
Voxxed days 2015-hakansaglam-codereview
At Peak Games, one of the most important development practices is Code Review. We believe that, with Code Review we have
* increased the code quality
* decreased the bugs
* encouraged collaboration
* kept the code maintainable
* created common language in the team
In this presentation I try to give some samples and practices about
* How we are doing Code Review.
* What are the findings to be able to make it more effective.
* What are we doing to make “Code Review” as a part of our development culture.
Lessons Learned from Revamping Our Doc Site
Learn what went well and what didn’t, when Ilona, a technical writer, and Prabhjot, a software engineer, share the story of revamping the developer documentation website at Twitch. Some hints: getting it done required more than just engineering, content, and design. Together they learned how to “manage up” and that the whole project went better because they worked so well as a team.
What are APIs?
Master the art of Low-Code.
Learn the coding basics you need to supercharge your no-code projects.
Discover the whole course content including videos, transcripts and examples: lowcodestarterpack.com
apidays LIVE Singapore - Your API documentation powered by AI by Hervé Vu Rou...
apidays LIVE Singapore - Connected Development
Your API documentation powered by AI
Hervé Vu Roussel, Co-founder at Quod ai
Branching Your Way to Low-Code Perfection
With the introduction of code branching into the OutSystems platform, development teams have the flexibility to collaborate more effectively. From feature branches, to refactoring, to hotfixing production code, OutSystems’ new branching capability allows you to maintain power of built-in dependency analysis along with flexibility that multiple parallel code lines enables.
API-first development
The API-first design approach treats APIs as first-class citizens. The entire system or project is built around the idea that components connect via APIs. The first step is, therefore, to design the APIs and their connections.
However, there is a gap between the beautiful world of API specifications and the reality of agile development. This gap means that published API specifications are often incomplete, missing examples or simply outdated. The API specification meant to help developers can be a thorn in one’s side because keeping the specification in sync with its implementation is a manual process, tedious and prone to be forgotten during the rush to deliver.
We show how this gap can be bridged effectively using the API specification as the only source of truth driving the API implementation with proven tools enabling automation.
apidays LIVE New York 2021 - Designing API's: Less Data is More! by Damir Svr...
apidays LIVE New York 2021 - API-driven Regulations for Finance, Insurance, and Healthcare
July 28 & 29, 2021
Designing API's: Less Data is More!
Damir Svrtan, Senior Software Engineer at Netflix
apidays LIVE Hong Kong 2021 - Less Data is More by Damir Svrtan, Netflix
apidays LIVE Hong Kong 2021 - API Ecosystem & Data Interchange
August 25 & 26, 2021
Less Data is More
Damir Svrtan, Senior Software Engineer at Netflix
Top 5 Javascript Frameworks for Web and Mobile App Development
Why Frontend JavaScript Frameworks?
The process of web app development starts with the idea of how the app will look on screen. So far so good. Next, these images are HTMLised by a frontend designer which is then converted by the developer into a fully working webs development page. But hey! Here is the catch.
Hence came the need to standardize the web app designing so that the backend workflow injection part can be easily coded. And going by the example of HTML and CSS frameworks such as Bootstrap and Foundation, coders created JavaScript frontend frameworks to formulate web apps.
Complete JS Frameworks
There are many so called JavaScript frameworks in the market, but in reality not all are complete frameworks. That means that not every framework out there can be used to create every aspect of an app. Most of them can be categorized as a set of tools that can make your coding easier but you may have to rely on other tools as well to get the job done.
AngularJS
This is the framework that works on the concept of two-way data binding, and this was the framework that revolutionized the concept of model view controller architecture in web apps. Also, this is a comprehensive framework and reduces the need to introduce other JS libraries into the development process.
EmberJS
EmberJS is the framework for those who focus on conventions rather than configurations. EmberJS has a very robust routing framework and thus is a good candidate to go with when you have complex nested routes and templates within a page.
CanJS
CanJS is a relatively new framework so it lacks in terms of popularity. But we were greatly impressed by its ease-of-use and flexibility in our projects so I thought its prudent to include it in the list. CanJS also ranks higher than the other three in terms of performance, especially when you have to render lots of view binding.
JavaScript toolkits that can work as frameworks
KnockoutJS
KnockoutJS is a very popular toolkit among JS web app designers. It’s very lightweight, has every basic view rendering feature an app would need and it’s a perfect tool for those app projects for which you may have to develop your own framework.
BackBoneJS
BackboneJS is awesome if you want to define your templating or use jQuery-like event binding. However the framework Tool-kit is only for advanced developers and it has a steep learning curve. BackBoneJS is good at handling requests, module loading and request routing.
Conclusion
AngularJS is only stand alone framework that does not need help of any other library to work, and it is also the largest frontend JS framework out there. Ember and CanJS need support from additional libraries but are great in their own ways. BackboneJS and KnockoutJS are awesome for small app development projects or for those large app development projects in which you may have to build your own framework.
An overview of devportal technologies and their (dis)advantages
It is really hard to chose the right technology to use to build your devportal.
The various types of devportals support 3 authoring experiences:
-CMS based authoring - tight coupling between the content model and a UI
-docs as code - code repo, or file based CMS
-API based authoring - command line/endpoint as the interface
We will discuss how things can go wrong if you don’t cater to your different authors
The UX of DX: User testing in the invisible world of APIs
1) The document discusses applying user experience (UX) methods like empathy, ideation, prototyping, and testing to improve the usability of application programming interfaces (APIs).
2) It provides an overview of techniques for each step of the process, including discovery, taxonomy, mockups/prototyping, and usability testing.
3) The goal is to make APIs easier for developers to navigate, understand, and use through applying UX best practices and getting feedback from both developers and end users.
JOSA TechTalks - RESTful API Concepts and Best Practices
Everyday we create services for our systems. A lot of people create RESTful APIs but much more can be accomplished by following best practices and treating your APIs as a product to be consumed by fellow team members, systems and 3rd party consumers.
We will discuss what makes a great RESTful API and share some of our experiences building some that power real systems.
This was part of JOSA TechTalks project within Jordan Open Source Association, presented by Yazan Quteishat and Tambi Jalouqa.
Mais conteúdo relacionado
Mais procurados
apidays LIVE New York 2021 - Designing embedded platforms: Lessons from indus...
apidays LIVE New York 2021 - API-driven Regulations for Finance, Insurance, and Healthcare
July 28 & 29, 2021
Designing embedded platforms: Lessons from industry success & failure
Jeremy Glassenberg, Product Lead, APIs at Docusign
5 Important Considerations For Mobile Application Development Process
The document discusses considerations for mobile app development. It recommends connecting to cloud-based systems to enjoy scalable functionality. It also suggests using component-based development methodologies for flexible, reliable and reusable systems. Additionally, it advises implementing test-driven development by always writing test cases to ensure new functionality works properly. The document emphasizes choosing a mobile app development partner wisely to make crucial decisions associated with app development.
apidays LIVE Australia 2021 - From apps to APIs: how no-code is transforming ...
apidays LIVE Australia 2021 - Accelerating Digital
September 15 & 16, 2021
From apps to APIs: how no-code is transforming the tech industry
Carmen Chung, Senior Product Manager at Linktree
E031202024029
This document discusses the design and development of a Service Oriented Architecture (SOA) interface for mobile device testing. It proposes using a SOA approach to address the challenges of mobile device testing, which is made difficult by the complex and evolving nature of mobile software and hardware. The paper describes building modular components according to SOA principles and using a common interface to allow components to communicate and reuse test cases. It outlines developing fault injection techniques and a taxonomy of faults specific to SOA to test the reliability of the proposed interface. The goal is to create a more flexible and reusable framework for mobile device testing.
{Re}designing a Developer Portal
Your Developer Portal is the primary interface that developers will have with your company’s product. So what does your developer portal say about you? We’ll share what we’ve learned at BigCommerce about redesigning a developer portal that helps your developers–and your company–meet their goals.
Beyond API Spray & Pray: Developer Portals in Digital Transformation
For some organizations digital transformation is “buzzword whack-a-mole”: they chase hype after hype, implement digital platform after platform but never invest enough to really be successful. One of these strategies that I’ve seen up close recently is the “spray & pray API strategy”: build loads of API services and then sell them on an API marketplace. But it is not clear what exactly the product portfolio is, what market is being targeted, or even who the customers will be…
If you build it, they will come - right?
Developer portals can be the backbone for a digital transformation initiative. Providing an interface of interfaces that allows you to build digital platforms, plugin marketplaces, API ecosystems, service aggregators, and procurement switchboards. But to be successful, you need a strategy - your developer portal needs to be more than a dumping ground for API documentation.
In this talk Kristof will share an overview of the different types of developer portals he is currently aware of, and the types of digital transformation tactics they enable. He will use a complexity & systems lens to explain what he thinks is driving the need for digital transformation. Finally, he will explore a deliberate complexity architecture inspired by biology, that organizations can use to become more resilient & adaptive while maintaining efficiency.
Mobile SDK: Considerations & Best Practices
Mobile SDKs are a great way to make your service or API easily consumable by the large number of developers out there looking for state of the art tools to make their apps stand out in the competitive marketplaces, but building a stable, compatible and successful SDK is quite a challenge.
In this talk we the technical and design challenges involved in developing an efficient mobile SDK that is highly compatible with its host mobile app, and the various considerations we took into account and the lessons we’ve learned while designing and building LivePerson’s native mobile SDK.
Engineer Stunning (API) documentation
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.
A Starters Guide to Building APIs with Javascript
Presented by: Tom Wilson, hyper63
Presented at the All Things Open Virtual Meetup
Abstract: APIs (Application Program Interfaces) is how programs can talk with other programs and is a design consideration for many products. Let’s discuss: Why you should build an application with an API? What are the top 5 requirements of designing an API with examples? Some open-source javascript frameworks that can help you design and build your API.
In order to get the most out of this talk, you should have a good understanding of http REST protocol and general application development. Familiarity with javascript and technologies like NodeJS and Express would be a plus.
In this talk, you should come away with a good understanding of why you should consider building an API in your application, key good practices every API should include, and how you could implement an API using Javascript.
apidays LIVE Hong Kong 2021 - Automating the API Product Lifecycle by Jeremy ...
apidays LIVE Hong Kong 2021 - API Ecosystem & Data Interchange
August 25 & 26, 2021
Automating the API Product Lifecycle
Jeremy Glassenberg, Product Lead, APIs at Docusign
Voxxed days 2015-hakansaglam-codereview
At Peak Games, one of the most important development practices is Code Review. We believe that, with Code Review we have
* increased the code quality
* decreased the bugs
* encouraged collaboration
* kept the code maintainable
* created common language in the team
In this presentation I try to give some samples and practices about
* How we are doing Code Review.
* What are the findings to be able to make it more effective.
* What are we doing to make “Code Review” as a part of our development culture.
Lessons Learned from Revamping Our Doc Site
Learn what went well and what didn’t, when Ilona, a technical writer, and Prabhjot, a software engineer, share the story of revamping the developer documentation website at Twitch. Some hints: getting it done required more than just engineering, content, and design. Together they learned how to “manage up” and that the whole project went better because they worked so well as a team.
What are APIs?
Master the art of Low-Code.
Learn the coding basics you need to supercharge your no-code projects.
Discover the whole course content including videos, transcripts and examples: lowcodestarterpack.com
apidays LIVE Singapore - Your API documentation powered by AI by Hervé Vu Rou...
apidays LIVE Singapore - Connected Development
Your API documentation powered by AI
Hervé Vu Roussel, Co-founder at Quod ai
Branching Your Way to Low-Code Perfection
With the introduction of code branching into the OutSystems platform, development teams have the flexibility to collaborate more effectively. From feature branches, to refactoring, to hotfixing production code, OutSystems’ new branching capability allows you to maintain power of built-in dependency analysis along with flexibility that multiple parallel code lines enables.
API-first development
The API-first design approach treats APIs as first-class citizens. The entire system or project is built around the idea that components connect via APIs. The first step is, therefore, to design the APIs and their connections.
However, there is a gap between the beautiful world of API specifications and the reality of agile development. This gap means that published API specifications are often incomplete, missing examples or simply outdated. The API specification meant to help developers can be a thorn in one’s side because keeping the specification in sync with its implementation is a manual process, tedious and prone to be forgotten during the rush to deliver.
We show how this gap can be bridged effectively using the API specification as the only source of truth driving the API implementation with proven tools enabling automation.
apidays LIVE New York 2021 - Designing API's: Less Data is More! by Damir Svr...
apidays LIVE New York 2021 - API-driven Regulations for Finance, Insurance, and Healthcare
July 28 & 29, 2021
Designing API's: Less Data is More!
Damir Svrtan, Senior Software Engineer at Netflix
apidays LIVE Hong Kong 2021 - Less Data is More by Damir Svrtan, Netflix
apidays LIVE Hong Kong 2021 - API Ecosystem & Data Interchange
August 25 & 26, 2021
Less Data is More
Damir Svrtan, Senior Software Engineer at Netflix
Top 5 Javascript Frameworks for Web and Mobile App Development
Why Frontend JavaScript Frameworks?
The process of web app development starts with the idea of how the app will look on screen. So far so good. Next, these images are HTMLised by a frontend designer which is then converted by the developer into a fully working webs development page. But hey! Here is the catch.
Hence came the need to standardize the web app designing so that the backend workflow injection part can be easily coded. And going by the example of HTML and CSS frameworks such as Bootstrap and Foundation, coders created JavaScript frontend frameworks to formulate web apps.
Complete JS Frameworks
There are many so called JavaScript frameworks in the market, but in reality not all are complete frameworks. That means that not every framework out there can be used to create every aspect of an app. Most of them can be categorized as a set of tools that can make your coding easier but you may have to rely on other tools as well to get the job done.
AngularJS
This is the framework that works on the concept of two-way data binding, and this was the framework that revolutionized the concept of model view controller architecture in web apps. Also, this is a comprehensive framework and reduces the need to introduce other JS libraries into the development process.
EmberJS
EmberJS is the framework for those who focus on conventions rather than configurations. EmberJS has a very robust routing framework and thus is a good candidate to go with when you have complex nested routes and templates within a page.
CanJS
CanJS is a relatively new framework so it lacks in terms of popularity. But we were greatly impressed by its ease-of-use and flexibility in our projects so I thought its prudent to include it in the list. CanJS also ranks higher than the other three in terms of performance, especially when you have to render lots of view binding.
JavaScript toolkits that can work as frameworks
KnockoutJS
KnockoutJS is a very popular toolkit among JS web app designers. It’s very lightweight, has every basic view rendering feature an app would need and it’s a perfect tool for those app projects for which you may have to develop your own framework.
BackBoneJS
BackboneJS is awesome if you want to define your templating or use jQuery-like event binding. However the framework Tool-kit is only for advanced developers and it has a steep learning curve. BackBoneJS is good at handling requests, module loading and request routing.
Conclusion
AngularJS is only stand alone framework that does not need help of any other library to work, and it is also the largest frontend JS framework out there. Ember and CanJS need support from additional libraries but are great in their own ways. BackboneJS and KnockoutJS are awesome for small app development projects or for those large app development projects in which you may have to build your own framework.
An overview of devportal technologies and their (dis)advantages
It is really hard to chose the right technology to use to build your devportal.
The various types of devportals support 3 authoring experiences:
-CMS based authoring - tight coupling between the content model and a UI
-docs as code - code repo, or file based CMS
-API based authoring - command line/endpoint as the interface
We will discuss how things can go wrong if you don’t cater to your different authors
Mais procurados (20)
apidays LIVE New York 2021 - Designing embedded platforms: Lessons from indus...
apidays LIVE New York 2021 - Designing embedded platforms: Lessons from indus...
5 Important Considerations For Mobile Application Development Process
5 Important Considerations For Mobile Application Development Process
apidays LIVE Australia 2021 - From apps to APIs: how no-code is transforming ...
apidays LIVE Australia 2021 - From apps to APIs: how no-code is transforming ...
Beyond API Spray & Pray: Developer Portals in Digital Transformation
Beyond API Spray & Pray: Developer Portals in Digital Transformation
apidays LIVE Hong Kong 2021 - Automating the API Product Lifecycle by Jeremy ...
apidays LIVE Hong Kong 2021 - Automating the API Product Lifecycle by Jeremy ...
apidays LIVE Singapore - Your API documentation powered by AI by Hervé Vu Rou...
apidays LIVE Singapore - Your API documentation powered by AI by Hervé Vu Rou...
apidays LIVE New York 2021 - Designing API's: Less Data is More! by Damir Svr...
apidays LIVE New York 2021 - Designing API's: Less Data is More! by Damir Svr...
apidays LIVE Hong Kong 2021 - Less Data is More by Damir Svrtan, Netflix
apidays LIVE Hong Kong 2021 - Less Data is More by Damir Svrtan, Netflix
Top 5 Javascript Frameworks for Web and Mobile App Development
Top 5 Javascript Frameworks for Web and Mobile App Development
An overview of devportal technologies and their (dis)advantages
An overview of devportal technologies and their (dis)advantages
Semelhante a The UX of DX: User Testing in the Invisible World of APIs
The UX of DX: User testing in the invisible world of APIs
1) The document discusses applying user experience (UX) methods like empathy, ideation, prototyping, and testing to improve the usability of application programming interfaces (APIs).
2) It provides an overview of techniques for each step of the process, including discovery, taxonomy, mockups/prototyping, and usability testing.
3) The goal is to make APIs easier for developers to navigate, understand, and use through applying UX best practices and getting feedback from both developers and end users.
JOSA TechTalks - RESTful API Concepts and Best Practices
Everyday we create services for our systems. A lot of people create RESTful APIs but much more can be accomplished by following best practices and treating your APIs as a product to be consumed by fellow team members, systems and 3rd party consumers.
We will discuss what makes a great RESTful API and share some of our experiences building some that power real systems.
This was part of JOSA TechTalks project within Jordan Open Source Association, presented by Yazan Quteishat and Tambi Jalouqa.
Prototyping invision vs axure
How to create prototype and communicate it to other people.
Well known prototyping tools pros & cons.
App to AppExchange - A Journey from Idea to Market for Salesforce Developers
This document summarizes the journey of developing an app for the Salesforce AppExchange marketplace. It describes conceptualizing the app idea as a set of REST APIs, developing the APIs using Swagger code generation, and packaging it for the Salesforce platform. It then details the challenges of the AppExchange security review process and requirements for ongoing app management, release management and responsible for own marketing to drive customers. The overall document provides guidance on developing an app for the AppExchange from concept to market.
DevOps on AWS: Accelerating Software Delivery with AWS Developer Tools | AWS ...
Software release cycles are now measured in days instead of months. Cutting-edge companies are continuously delivering high-quality software at a fast pace. In this session, you will learn how to begin your DevOps journey through best practices and tools used by the "two pizza" engineering teams at Amazon. We will showcase how you can accelerate developer productivity by implementing continuous integration and delivery workflows. We will also cover an introduction to AWS CodeStar, AWS CodeCommit, AWS CodeBuild, AWS CodePipeline, and AWS CodeDeploy - the services inspired by Amazon's internal developer tools and DevOps practice. Learn More: https://aws.amazon.com/government-education/
Karthikeyan_Resume
Karthik has over 8 years of experience developing .NET and SharePoint applications, including SharePoint add-ins, workflows, and Azure services. He is proficient in C#, JavaScript, SQL Server, and Azure technologies. His experience includes projects for Johnson Controls involving SharePoint development and Azure web jobs, and asset tracking and power trading systems for other clients.
From Python to Java
This document discusses Uber's growth and engineering challenges over time. It covers topics like Uber reaching 1 billion and 2 billion trips, microservices, tradeoffs between different programming languages, and tools used for building, deploying, and monitoring Uber's systems and services. The document also highlights advantages of various languages and technologies as well as Uber's open source projects that address common problems.
B4UConference_Sexy Angular Stack
Angular State Container
ES6+
TypeScript
Linter
UI kit Unit Test Webpack VS Code
Take away + Demo
Midhun new
Midhun Kumar Addanki is a software developer with over 2 years of experience developing .NET applications using technologies like C#, ASP.NET MVC, SQL Server, and AngularJS. He has experience designing and developing 3-tier web applications and writing unit tests using Microsoft Fakes and MOQ. Some of his projects include developing a carpooling app for Wipro using Node.js, AngularJS and Azure Document DB, and an internal community application using ASP.NET MVC, SQL Server and testing frameworks. He is proficient in .NET, JavaScript and relational and NoSQL databases.
EBSCO Digital Transformation with AWS
EBSCO is a large research platform provider with over 3,200 employees and 150,000 library customers worldwide. Kenzan is a consulting firm that helps companies with digital transformation, including application development and cloud migration. EBSCO is working with Kenzan to migrate its platforms to AWS to achieve goals like high velocity value creation and margin protection through a culture and technology transformation. This involves moving to a microservices architecture in AWS, adopting agile methods, and transitioning to a "development centric operating model" where developers build, deploy, and manage their own software. The transformation aims to increase new feature development by 25% and decrease non-developer labor by 80% through practices like continuous delivery, immutable infrastructure, and automated
TechTalk: Wind Tunnel, Personas, and Testing Real UX
Persona-based testing has never been easier
Covered in this webinar:
- Intro to Perfecto
- Digital Challenges
- Perfecto CQ Lab and Wind Tunnel™ Overview
- Wind Tunnel Deep Dive
- How to Add Wind Tunnel to your Test
- Demo
- Q&A
By the end of this webinar, you'll be a master at adding UX to each of your tests!
AJAX Patterns with ASP.NET
This session takes a deeper look at the AJAX paradigm by discussing key development patterns. It demonstrates implementing them using a combination of out-of-the-box features and as well as features built by leveraging the extensibility of the platform. Patterns covered range from fundamentals such as networking, search optimization, navigation, and unobtrusive script attachment to user interface usability techniques such as visual notifications, and customization. The demonstrations are illustrated in the context of a simple scenario, but are designed to be applied directly to real-world applications.
Dot NET Solution Architect Roadmap By Scholarhat PDF
Dot NET Solution Architect Roadmap By Scholarhat PDF
Aakanksha_Agnani_j2016
The document provides a resume for Aakanksha Agnani. It summarizes her professional experience as a software engineer at Gap Inc. and Accenture, where she developed applications using technologies like Java, Python, Oracle and PostgreSQL. It also lists her education as a Master's in Computer Science from Ohio State University and Bachelor's from University of Mumbai.
Building the Eventbrite API Ecosystem
We describe how we built the Eventbrite API ecosystem. Such as finding API product fit, building a partner program, and incentive developers.
A Test Automation Platform Designed for the Future
Looking for cutting-edge AI-based test automation tools to level up your SDLC today? In this webinar, we will hit reset on the industry expectations around what your tooling needs to look and act like—and give you a preview of the new product we’ve been pouring ourselves into. You will see why now is the time to shake things up and push beyond what you thought possible in your test automation practice.
Fathima Resume
Fathima Zohra has over 5 years of experience in manual, automation, and ETL testing using tools like HP Quality Center, ClearQuest, PRISM, Bugzilla, Eclipse, and IBM Rational Tester. She has worked as a test lead and software engineer on various projects for clients like IBM, Infosys, AT&T, and Bell Canada. Her areas of expertise include application testing, database testing, web services testing, and testing across the SDLC. She is proficient in languages like C#, C++, SQL, and scripting languages.
The Developer Experience
What makes for a good developer experience? How do you improve yours? That's what I explore in this talk, given at Atlassian Summit 2012.
Pradeep Kumar _Profile
This document provides a summary of Pradeep Kumar C's work experience and qualifications. He has over 11 years of experience in software development using technologies like C#, .NET, AngularJS, SQL Server, and Delphi. Some of his responsibilities have included designing applications, writing code, testing, code reviews, and acting as a team leader. He has worked on projects for banks involving check processing, payments, and remote deposit capture.
Veena_Tiwari
- Veena Tiwari is a software engineer with over 3.5 years of experience working with various organizations on mobile application testing, automation, and manual testing of web and SaaS applications.
- She has experience in test automation using Appium, Selenium WebDriver, TestNG, Java, and other tools.
- She is currently working as a software engineer at Tech Mahindra on automation testing of Philips' web and mobile apps (iOS and Android).
Semelhante a The UX of DX: User Testing in the Invisible World of APIs (20)
The UX of DX: User testing in the invisible world of APIs
The UX of DX: User testing in the invisible world of APIs
JOSA TechTalks - RESTful API Concepts and Best Practices
JOSA TechTalks - RESTful API Concepts and Best Practices
App to AppExchange - A Journey from Idea to Market for Salesforce Developers
App to AppExchange - A Journey from Idea to Market for Salesforce Developers
DevOps on AWS: Accelerating Software Delivery with AWS Developer Tools | AWS ...
DevOps on AWS: Accelerating Software Delivery with AWS Developer Tools | AWS ...
TechTalk: Wind Tunnel, Personas, and Testing Real UX
TechTalk: Wind Tunnel, Personas, and Testing Real UX
Dot NET Solution Architect Roadmap By Scholarhat PDF
Dot NET Solution Architect Roadmap By Scholarhat PDF
A Test Automation Platform Designed for the Future
A Test Automation Platform Designed for the Future
Mais de Pronovix
By the time they're reading the docs, it's already too late
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 Feedback
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 portal
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.
Documentation, APIs & AI
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 pages
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 experiences
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 Docs
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.
API Documentation For Web3
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 design
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.
unREST among the docs
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 APIs
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.
Annotate, Automate & Educate: Driving generated OpenAPI docs to benefit everyone
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?
- 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 Configurations
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 communities
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.
One Developer Portal to Document Them All
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 Experience
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 product
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.
Complexity is not complicatedness
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...
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
Mais de Pronovix (20)
By the time they're reading the docs, it's already too late
By the time they're reading the docs, it's already too late
Optimizing Dev Portals with Analytics and Feedback
Optimizing Dev Portals with Analytics and Feedback
Success metrics when launching your first developer portal
Success metrics when launching your first developer portal
Feedback cycles and their role in improving overall developer experiences
Feedback cycles and their role in improving overall developer experiences
Why your API doesn’t solve my problem: A use case-driven API design
Why your API doesn’t solve my problem: A use case-driven API design
Developing a best-in-class deprecation policy for your APIs
Developing a best-in-class deprecation policy for your APIs
Annotate, Automate & Educate: Driving generated OpenAPI docs to benefit everyone
Annotate, Automate & Educate: Driving generated OpenAPI docs to benefit everyone
What do developers do when it comes to understanding and using APIs?
What do developers do when it comes to understanding and using APIs?
Inclusive, Accessible Tech: Bias-Free Language in Code and Configurations
Inclusive, Accessible Tech: Bias-Free Language in Code and Configurations
Creating API documentation for international communities
Creating API documentation for international communities
Docs-as-Code: Evolving the API Documentation Experience
Docs-as-Code: Evolving the API Documentation Experience
Developer journey - make it easy for devs to love your product
Developer journey - make it easy for devs to love your product
How cognitive biases and ranking can foster an ineffective architecture and d...
How cognitive biases and ranking can foster an ineffective architecture and d...
Último
Essentials of Automations: Exploring Attributes & Automation Parameters
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.GNSS spoofing via SDR (Criptored Talks 2024)
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...Pitangent Analytics & Technology Solutions Pvt. Ltd
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.Northern Engraving | Nameplate Manufacturing Process - 2024
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Principle of conventional tomography-Bibash Shahi ppt..pptx
before the computed tomography, it had been widely used.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Último (20)
Essentials of Automations: Exploring Attributes & Automation Parameters
Essentials of Automations: Exploring Attributes & Automation Parameters
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Northern Engraving | Nameplate Manufacturing Process - 2024
Northern Engraving | Nameplate Manufacturing Process - 2024
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Principle of conventional tomography-Bibash Shahi ppt..pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
The UX of DX: User Testing in the Invisible World of APIs
- 1. The UX of DX: User Testing in the Invisible World of APIs Jenny Wanger @jennydove
- 2. Improve API Usability by applying UX Methods Empathize Scope Ideate Prototype Test Iterate {dev}
- 3. Discovery Build something useful Make it easy to navigateTaxonomy Get the structures rightMock & Prototype Find perfectionUsability Our UX Framework
- 4. Interviews Site Visits Ethnography TECHNIQUES • Collaborate with your end user to develop use cases • Determine what information to include that solves for their need Discovery Taxonomy Usability Mock & Prototype
- 5. DISCOVERY Observation > Conversation Look for the point of marginal return # of users learnings Developers + End Users
- 7. Discovery Taxonomy Usability Mock & Prototype Card Sort Tree Testing TECHNIQUES • Use user personas to create different journeys for your developers • Focus on method and resource names, order of operations
- 8. TAXONOMY User BIRTHPLACE AGE PET Chicago 26 yrs old 3 Cats /details /attributes /characteristics /randomThings /tags /data
- 10. Discovery Taxonomy Usability Mock & Prototype Paper Prototypes Instant Messenger APIs TECHNIQUES • Think through the structure of the API request and response body • The goal is to get a basic outline of each endpoint
- 11. MOCK & PROTOTYPE GET forecast/London },{ "period": 3, "title": "Wednesday Night", "fcttext": "Overcast. Fog overnight. Low of 54F. Winds from the WSW at 5 to 15 mph.", "fcttext_metric": "Overcast. Fog overnight. Low of 12C. Breezy. Winds from the WSW at 10 to 20 km/h.", “precipitation": "0" },{ Percent or inches? Why is only one FCT tagged with the units? Should be fcttext_imperial and fcttext_metric
- 13. Discovery Taxonomy Usability Mock & Prototype Usability Testing via Postman or Swagger TECHNIQUES • Mock up your API in full detail without a back end • Follow UX usability testing techniques to run testing • This is where you decide on the fine details: units, headers, etc.
- 14. USABILITY • Charge a credit card for $12.50 • Apply a discount of 10% for every person who uses the code “API THE DOCS” • Create a pricing chart for lattes, cappuccinos, and mochas
- 16. Let’s build an API! Testing Completed
- 17. Assess Vision Don’t let an already-built API stop you from building the right API Version 17 APIs that are live today
- 18. CREATIVE FIXES GET reports type: {periodic, summary, histogram} If periodic , please supply… If summary, please supply… If histogram, please supply…
- 19. HIDE WITH DOCS GET reports/periodic type: periodic Start_date: 10092017 End_date: 10102017 Start_time: 1124 End_time: 1909 Interval_length: 2 Interval_units: hours
- 20. Questions? Users first Thanks to Emily Ryou for her contributions to this presentation. @jennydove