Sometime, real API and documentation have deep groove. So I have decided to create document from real API request and response. At first, I have created swagger from API response. After that, I have published mkdocs documents from swagger.
1) The document discusses using OpenAPI to describe APIs and increase productivity. It introduces OpenAPI tools like Swagger UI, Swagger Editor, and bravado-core that can generate documentation, validate requests, and convert data types.
2) An actual case study is presented on a manufacturing cloud platform called Kabuku Connect that uses the OpenAPI spec to generate API documentation, client code, and validate requests from the frontend.
3) The speaker encourages contributors to help support the new OpenAPI 3.0 specification and related tools, and invites attendees to apply for open developer roles at their company to build out projects using 3D printing and other technologies.
Writing a truly consumable REST API is hard. Once exposed, documentation must be perfect before it can be consumed. Consumers often face days or weeks of work creating the client code. Many just need a command-line API. For a large API, writing these by hand and keeping them in sync is mission impossible. This session shows how to combine tooling around JAX-RS, OpenAPI, and MicroProfile REST Client to bootstrap microservice APIs that have Amazon-style Java client library, command-line API, and AsciiDoc/HTML documentation. The presentation explores generation of clients in other languages such as JavaScript and Git-inspired command-line techniques that enable REST calls to be secured via SSH keys. All perfectly documented in AsciiDoc, HTML, and man pages.
The document introduces Swagger, an open source framework for describing and documenting RESTful APIs. Swagger allows APIs to be defined in a machine-readable JSON format and generates documentation, client libraries, and servers from these definitions. This standardized interface for APIs has benefits like enabling parallel development, removing logic from clients, and facilitating code generation for multiple platforms and languages.
The document discusses different levels of REST APIs. Level 3 REST expresses everything as links in the response body. An example is given where a GET request for doctor appointment slots returns an XML response containing the slots with a link to book each slot. Level 3 REST makes APIs browsable by including links to related resources, avoiding the need for separate documentation on how to perform actions.
EuroPython 2017 - How to make money with your Python open-source projectMax Tepkeev
Developers create new open-source projects every day. As the project becomes popular they have to invest more and more time into it’s development and of course at some point a question arises: “How can I make some money with my project ?”
In this talk we will try to answer this question. We will talk about different models of making money, their pros and cons. We will concentrate on Python Open-Source projects mostly and try to answer the following questions:
What to sell ?
Where to sell ?
How to distribute ?
How to license ?
After this talk you will have a clear understanding of how you can make money with your project. What your next steps should be and how you can get the actual profit while still continuing making your customers happy.
https://github.com/alvarowolfx/react-native-shakeit-demo
Introduction to React native presentation. A little history about React web, comparison with state of art of hybrid mobile development and demo to the local community.
Cucumber is a tool that executes plain-text behavioral tests written in Gherkin and maps them to code via step definitions to automate testing; Gherkin is a business-readable language used to describe software behavior without detailing implementation; Cucumber uses Ruby and drivers like Capybara to simulate user interactions and check outcomes of the automated tests.
Building Desktop RIAs With PHP And JavaScriptfunkatron
This document summarizes a talk about building desktop applications using PHP and JavaScript. It discusses using Adobe AIR as a runtime environment and JavaScript frameworks like jQuery. It provides examples of desktop apps communicating with a PHP backend over JSON to perform tasks like uploading photos or making asynchronous calculations. The document recommends using JSON for data exchange and emphasizes that desktop apps are persistent with asynchronous calls, unlike server-side PHP apps.
1) The document discusses using OpenAPI to describe APIs and increase productivity. It introduces OpenAPI tools like Swagger UI, Swagger Editor, and bravado-core that can generate documentation, validate requests, and convert data types.
2) An actual case study is presented on a manufacturing cloud platform called Kabuku Connect that uses the OpenAPI spec to generate API documentation, client code, and validate requests from the frontend.
3) The speaker encourages contributors to help support the new OpenAPI 3.0 specification and related tools, and invites attendees to apply for open developer roles at their company to build out projects using 3D printing and other technologies.
Writing a truly consumable REST API is hard. Once exposed, documentation must be perfect before it can be consumed. Consumers often face days or weeks of work creating the client code. Many just need a command-line API. For a large API, writing these by hand and keeping them in sync is mission impossible. This session shows how to combine tooling around JAX-RS, OpenAPI, and MicroProfile REST Client to bootstrap microservice APIs that have Amazon-style Java client library, command-line API, and AsciiDoc/HTML documentation. The presentation explores generation of clients in other languages such as JavaScript and Git-inspired command-line techniques that enable REST calls to be secured via SSH keys. All perfectly documented in AsciiDoc, HTML, and man pages.
The document introduces Swagger, an open source framework for describing and documenting RESTful APIs. Swagger allows APIs to be defined in a machine-readable JSON format and generates documentation, client libraries, and servers from these definitions. This standardized interface for APIs has benefits like enabling parallel development, removing logic from clients, and facilitating code generation for multiple platforms and languages.
The document discusses different levels of REST APIs. Level 3 REST expresses everything as links in the response body. An example is given where a GET request for doctor appointment slots returns an XML response containing the slots with a link to book each slot. Level 3 REST makes APIs browsable by including links to related resources, avoiding the need for separate documentation on how to perform actions.
EuroPython 2017 - How to make money with your Python open-source projectMax Tepkeev
Developers create new open-source projects every day. As the project becomes popular they have to invest more and more time into it’s development and of course at some point a question arises: “How can I make some money with my project ?”
In this talk we will try to answer this question. We will talk about different models of making money, their pros and cons. We will concentrate on Python Open-Source projects mostly and try to answer the following questions:
What to sell ?
Where to sell ?
How to distribute ?
How to license ?
After this talk you will have a clear understanding of how you can make money with your project. What your next steps should be and how you can get the actual profit while still continuing making your customers happy.
https://github.com/alvarowolfx/react-native-shakeit-demo
Introduction to React native presentation. A little history about React web, comparison with state of art of hybrid mobile development and demo to the local community.
Cucumber is a tool that executes plain-text behavioral tests written in Gherkin and maps them to code via step definitions to automate testing; Gherkin is a business-readable language used to describe software behavior without detailing implementation; Cucumber uses Ruby and drivers like Capybara to simulate user interactions and check outcomes of the automated tests.
Building Desktop RIAs With PHP And JavaScriptfunkatron
This document summarizes a talk about building desktop applications using PHP and JavaScript. It discusses using Adobe AIR as a runtime environment and JavaScript frameworks like jQuery. It provides examples of desktop apps communicating with a PHP backend over JSON to perform tasks like uploading photos or making asynchronous calculations. The document recommends using JSON for data exchange and emphasizes that desktop apps are persistent with asynchronous calls, unlike server-side PHP apps.
Scaling up development of a modular code baseRobert Munteanu
This document summarizes Robert Munteanu's presentation on modular development at the Apache Sling & Friends Tech Meetup. The presentation covered topics like modular development vs deployment, using source control like Git with multiple repositories, continuous integration with build tools, preferences and discovery in IDEs, and communication across channels. Examples of modular development included Apache Sling's tooling in Jenkins and the use of repositories, plugins, and automation to support modular projects.
This document discusses REST APIs and the benefits of using Swagger to generate documentation for REST APIs built with Spring MVC. It explains that REST and HTTP have been widely used for decades to power APIs. Swagger allows generating interactive API documentation from code comments directly in the Spring MVC codebase. The document then provides a hands-on example of using Springfox to integrate Swagger into a Spring MVC REST API project to automatically generate API documentation.
Understanding how to use Swagger and its toolsSwagger API
Swagger is a toolset for designing, building, documenting, and using RESTful APIs. It includes tools like swagger-editor for designing APIs, swagger-ui for documenting and testing APIs, and swagger-codegen for building servers and clients from API definitions. The tools support the API lifecycle from design through documentation, testing, building, and operation. Integration workflows allow using multiple Swagger tools together such as designing an API with swagger-editor and generating servers and clients with swagger-codegen.
This document summarizes Marko Heijnen's talk on bootstrapping a WordPress plugin using automation. It discusses setting up the basic files and structure for a plugin, including internationalization, version control and compiling assets. It also covers automating common tasks like minification, validation and testing through Grunt plugins. Grunt is presented as a JavaScript task runner that can be used to define and run repetitive tasks like compressing files, validating code and deployments. Examples are provided for configuring Grunt to create POT files for internationalization, download translations from GlotPress and perform other automated tasks.
The document discusses best practices for building WordPress plugins, including improving one's workflow with version control and text editors, understanding WordPress code structure and APIs, following coding standards, defining a plugin's focus and structure, and testing plugins. It also provides examples from the speaker's own plugins and mistakes made. The speaker advocates investing in one's skills and producing well-coded, unique plugins that address user experience through standards compliance and robust testing.
What's This React Native Thing I Keep Hearing About?Evan Stone
In our daily lives as iOS developers, we can usually happily keep coding away in Swift and ignore what’s going on in other software development communities, like that of JavaScript. However, there may be some advantages to at least becoming familiar with what’s going on in the world of React Native, and in this session you will get an overview of what React Native is, and why it could be a useful addition to your toolbox an iOS developer.
These slides are based on a talk given by Evan K. Stone at the Forward Swift conference in San Francisco on March 2, 2017.
1) Grape is a framework for building REST-style APIs in Ruby. It is inspired by Sinatra and aims to make API development easy and intuitive.
2) With Grape, APIs can have their own framework separate from Rails or Sinatra. It allows for features like versioning, prefixing, namespacing, authentication helpers, and error handling in a concise syntax.
3) Grape focuses on ease of use but also plans to add more advanced features like documentation generation, content negotiation, OAuth support, plugin systems, and rate limiting to become a fully-featured API framework.
Collaborative Development: The Only CD That Matters - Brent Beer - Codemotion...Codemotion
The document discusses ways to promote collaborative development through knowledge sharing and reuse. It suggests establishing ad-hoc teams, guilds, and hubs of information to make work and expertise discoverable. It also emphasizes the importance of inclusion and adopting practices like InnerSource to engage diverse talent.
This document discusses behavior driven development (BDD) and Cucumber style testing. It provides examples of how to set up Cucumber testing for a Rails application, including installing Cucumber gems, configuring support files, and writing a sample feature file to test user sign up. Code snippets are provided for setting up Cucumber configuration files, installing necessary gems, and defining step definitions. The document aims to demonstrate how Cucumber can be used to write automated tests in a human-readable format.
The 3h workshop version of the 3d Advanced Architectures training (http://canonicalexamples.com/courses_android/#androidArch). I have delivered this one or the iOS counterpart in more than 20 cities of Europe and America. This is the latest version that shared in Minsk.
This document discusses GraphQL, a query language and execution engine that can be tied to any backend service. It notes that GraphQL avoids painful refactoring, provides a single endpoint that is easy to debug, and allows data to be aggregated and normalized easily. Additional benefits mentioned include being hierarchical, strongly typed, and version free. The document provides an overview of how GraphQL works at a high level with clients making GET/POST requests to a GraphQL server, which uses resolve functions to handle queries and aggregate data. It also mentions the GraphiQL tool for providing fast feedback, explicit errors, automatic query completion, and introspection capabilities when working with GraphQL.
Ofir Dagan - (Don’t) Blame it on React Native - Codemotion Rome 2019Codemotion
When writing large scale react native app it’s always fun to blame rn for everything that is wrong in our lives. However, what we keep finding, again and again, is that for most of the cases. Writing better performant react code can fix our performance issues. In the last couple of years our team built a huge production app in react native. In this talk I’ll go over some of our lessons learned in regards of react native performance and how to improve your app’s performance subsequently.
Matteo Manchi - React Native for multi-platform mobile applications - Codemot...Codemotion
Since its 2013 release, React has brought a new way to design UI components in the world wide web. The same fundamentals have been taken to another important environment in our contemporary world: the mobile applications. We'll see the philosophy behind React Native - learn once, write anywhere - and how this new framework helps developers to build native apps using React.
Integration of automation framework with ci toolsvodQA
This document discusses continuous integration (CI) and how to integrate an automation testing framework with a CI tool. It defines key CI concepts like pipelines, stages, jobs, and tasks. A pipeline contains multiple stages that run sequentially, with each stage containing parallel jobs made up of sequential tasks. The document also provides instructions on downloading, installing, and configuring a Go CI server and agent to run an automation test suite through CI pipelines.
React Native allows developers to write mobile apps using JavaScript and React while also being able to use native UI components. It uses the same fundamental UI building blocks as regular React apps but includes additional components better suited for mobile. Apps are compiled to native code, so they can access the same native platform features and performance as apps written in Java, Objective-C, or Swift. React Native is mature and used by many large companies for their mobile apps. It is a good option for building cross-platform mobile apps since developers can reuse their web skills and share code between Android and iOS platforms.
React Native allows developers to build mobile apps using only JavaScript. It uses the same fundamental UI building blocks as regular Android and iOS apps. Developers can share code across platforms and rapidly develop and deploy apps. React Native apps run fully native and can access many native platform features such as TouchID. It has gained popularity due to its powerful developer experience and high performance.
Creating BananaJS with Angular 2, Angular CLI, and Material DesignTracy Lee
The document is a presentation slide deck about building applications with Angular 2 and Angular CLI. It discusses configuring Materialize CSS, generating components, deploying to Firebase, using template-driven forms, and the new Angular router. The presentation provides steps to create an Angular CLI project, add Materialize CSS, generate components, and deploy the application to Firebase. It also lists additional learning resources and community members that can provide help.
DevOps Fest 2019. Gianluca Arbezzano. DevOps never sleeps. What we learned fr...DevOps_Fest
Where a company with an OpenSource project announce that they are working on a new major release there is always a lot of chatting going on in the community because you never know how much this is going to break your system. Gianluca Arbezzano SRE at InfluxData will speak about the journey the company is facing from a DevOps perspective to move from InfluxDB v1 to version 2 a fully integrated platform that starts from the strong background we built running a database like InfluxDB at scale in our SaaS offer. This is not just a story about how a project evolved but it touches all the company in particular for what concern DevOpsFest everything around Kubernetes, Container and automation. How the SRE team managed the onboard of 20 developers on a cloud based project where operating and observing the system is a key concept to learn how to build a more solid and sustainable product.
API Documentation Workshop tcworld India 2015Tom Johnson
This is a workshop I gave on API documentation at tcworld India 2015. The workshop covers 3 main areas:
- General overview of API documentation
- Deep dive into REST API documentation
- Deep dive into Javadoc documentation
Scaling up development of a modular code baseRobert Munteanu
This document summarizes Robert Munteanu's presentation on modular development at the Apache Sling & Friends Tech Meetup. The presentation covered topics like modular development vs deployment, using source control like Git with multiple repositories, continuous integration with build tools, preferences and discovery in IDEs, and communication across channels. Examples of modular development included Apache Sling's tooling in Jenkins and the use of repositories, plugins, and automation to support modular projects.
This document discusses REST APIs and the benefits of using Swagger to generate documentation for REST APIs built with Spring MVC. It explains that REST and HTTP have been widely used for decades to power APIs. Swagger allows generating interactive API documentation from code comments directly in the Spring MVC codebase. The document then provides a hands-on example of using Springfox to integrate Swagger into a Spring MVC REST API project to automatically generate API documentation.
Understanding how to use Swagger and its toolsSwagger API
Swagger is a toolset for designing, building, documenting, and using RESTful APIs. It includes tools like swagger-editor for designing APIs, swagger-ui for documenting and testing APIs, and swagger-codegen for building servers and clients from API definitions. The tools support the API lifecycle from design through documentation, testing, building, and operation. Integration workflows allow using multiple Swagger tools together such as designing an API with swagger-editor and generating servers and clients with swagger-codegen.
This document summarizes Marko Heijnen's talk on bootstrapping a WordPress plugin using automation. It discusses setting up the basic files and structure for a plugin, including internationalization, version control and compiling assets. It also covers automating common tasks like minification, validation and testing through Grunt plugins. Grunt is presented as a JavaScript task runner that can be used to define and run repetitive tasks like compressing files, validating code and deployments. Examples are provided for configuring Grunt to create POT files for internationalization, download translations from GlotPress and perform other automated tasks.
The document discusses best practices for building WordPress plugins, including improving one's workflow with version control and text editors, understanding WordPress code structure and APIs, following coding standards, defining a plugin's focus and structure, and testing plugins. It also provides examples from the speaker's own plugins and mistakes made. The speaker advocates investing in one's skills and producing well-coded, unique plugins that address user experience through standards compliance and robust testing.
What's This React Native Thing I Keep Hearing About?Evan Stone
In our daily lives as iOS developers, we can usually happily keep coding away in Swift and ignore what’s going on in other software development communities, like that of JavaScript. However, there may be some advantages to at least becoming familiar with what’s going on in the world of React Native, and in this session you will get an overview of what React Native is, and why it could be a useful addition to your toolbox an iOS developer.
These slides are based on a talk given by Evan K. Stone at the Forward Swift conference in San Francisco on March 2, 2017.
1) Grape is a framework for building REST-style APIs in Ruby. It is inspired by Sinatra and aims to make API development easy and intuitive.
2) With Grape, APIs can have their own framework separate from Rails or Sinatra. It allows for features like versioning, prefixing, namespacing, authentication helpers, and error handling in a concise syntax.
3) Grape focuses on ease of use but also plans to add more advanced features like documentation generation, content negotiation, OAuth support, plugin systems, and rate limiting to become a fully-featured API framework.
Collaborative Development: The Only CD That Matters - Brent Beer - Codemotion...Codemotion
The document discusses ways to promote collaborative development through knowledge sharing and reuse. It suggests establishing ad-hoc teams, guilds, and hubs of information to make work and expertise discoverable. It also emphasizes the importance of inclusion and adopting practices like InnerSource to engage diverse talent.
This document discusses behavior driven development (BDD) and Cucumber style testing. It provides examples of how to set up Cucumber testing for a Rails application, including installing Cucumber gems, configuring support files, and writing a sample feature file to test user sign up. Code snippets are provided for setting up Cucumber configuration files, installing necessary gems, and defining step definitions. The document aims to demonstrate how Cucumber can be used to write automated tests in a human-readable format.
The 3h workshop version of the 3d Advanced Architectures training (http://canonicalexamples.com/courses_android/#androidArch). I have delivered this one or the iOS counterpart in more than 20 cities of Europe and America. This is the latest version that shared in Minsk.
This document discusses GraphQL, a query language and execution engine that can be tied to any backend service. It notes that GraphQL avoids painful refactoring, provides a single endpoint that is easy to debug, and allows data to be aggregated and normalized easily. Additional benefits mentioned include being hierarchical, strongly typed, and version free. The document provides an overview of how GraphQL works at a high level with clients making GET/POST requests to a GraphQL server, which uses resolve functions to handle queries and aggregate data. It also mentions the GraphiQL tool for providing fast feedback, explicit errors, automatic query completion, and introspection capabilities when working with GraphQL.
Ofir Dagan - (Don’t) Blame it on React Native - Codemotion Rome 2019Codemotion
When writing large scale react native app it’s always fun to blame rn for everything that is wrong in our lives. However, what we keep finding, again and again, is that for most of the cases. Writing better performant react code can fix our performance issues. In the last couple of years our team built a huge production app in react native. In this talk I’ll go over some of our lessons learned in regards of react native performance and how to improve your app’s performance subsequently.
Matteo Manchi - React Native for multi-platform mobile applications - Codemot...Codemotion
Since its 2013 release, React has brought a new way to design UI components in the world wide web. The same fundamentals have been taken to another important environment in our contemporary world: the mobile applications. We'll see the philosophy behind React Native - learn once, write anywhere - and how this new framework helps developers to build native apps using React.
Integration of automation framework with ci toolsvodQA
This document discusses continuous integration (CI) and how to integrate an automation testing framework with a CI tool. It defines key CI concepts like pipelines, stages, jobs, and tasks. A pipeline contains multiple stages that run sequentially, with each stage containing parallel jobs made up of sequential tasks. The document also provides instructions on downloading, installing, and configuring a Go CI server and agent to run an automation test suite through CI pipelines.
React Native allows developers to write mobile apps using JavaScript and React while also being able to use native UI components. It uses the same fundamental UI building blocks as regular React apps but includes additional components better suited for mobile. Apps are compiled to native code, so they can access the same native platform features and performance as apps written in Java, Objective-C, or Swift. React Native is mature and used by many large companies for their mobile apps. It is a good option for building cross-platform mobile apps since developers can reuse their web skills and share code between Android and iOS platforms.
React Native allows developers to build mobile apps using only JavaScript. It uses the same fundamental UI building blocks as regular Android and iOS apps. Developers can share code across platforms and rapidly develop and deploy apps. React Native apps run fully native and can access many native platform features such as TouchID. It has gained popularity due to its powerful developer experience and high performance.
Creating BananaJS with Angular 2, Angular CLI, and Material DesignTracy Lee
The document is a presentation slide deck about building applications with Angular 2 and Angular CLI. It discusses configuring Materialize CSS, generating components, deploying to Firebase, using template-driven forms, and the new Angular router. The presentation provides steps to create an Angular CLI project, add Materialize CSS, generate components, and deploy the application to Firebase. It also lists additional learning resources and community members that can provide help.
DevOps Fest 2019. Gianluca Arbezzano. DevOps never sleeps. What we learned fr...DevOps_Fest
Where a company with an OpenSource project announce that they are working on a new major release there is always a lot of chatting going on in the community because you never know how much this is going to break your system. Gianluca Arbezzano SRE at InfluxData will speak about the journey the company is facing from a DevOps perspective to move from InfluxDB v1 to version 2 a fully integrated platform that starts from the strong background we built running a database like InfluxDB at scale in our SaaS offer. This is not just a story about how a project evolved but it touches all the company in particular for what concern DevOpsFest everything around Kubernetes, Container and automation. How the SRE team managed the onboard of 20 developers on a cloud based project where operating and observing the system is a key concept to learn how to build a more solid and sustainable product.
API Documentation Workshop tcworld India 2015Tom Johnson
This is a workshop I gave on API documentation at tcworld India 2015. The workshop covers 3 main areas:
- General overview of API documentation
- Deep dive into REST API documentation
- Deep dive into Javadoc documentation
API Documentation presentation to East Bay STC ChapterTom Johnson
This document summarizes Tom Johnson's presentation on strategies for API documentation. It discusses different types of APIs like platform and REST APIs. For platform APIs, documentation is often generated from source code comments. REST API documentation should cover endpoints, parameters, response formats, and example calls. The document also summarizes a survey of API documentation practices. Popular publishing approaches include single page sites with code samples and interactive documentation. It raises questions for documentation writers around technical skills, interest, and career entry points.
API Documentation -- Presentation to East Bay STC ChapterTom Johnson
This document summarizes Tom Johnson's presentation on strategies for API documentation. It discusses different types of APIs like platform and REST APIs. For platform APIs, documentation is often generated from source code comments. REST API documentation should cover endpoints, parameters, response formats, and example calls. The document also summarizes a survey of API documentation practices. Popular publishing approaches include single page sites with code samples and interactive documentation. It raises questions for documentation writers to consider their technical skills and career paths.
Chasing the RESTful Trinity - Client CLI and DocumentationRoberto Cortez
The learning curve for REST API security is severe and unforgiving. Specifications promise infinite flexibility, habitually give old concepts new names, and almost seem designed to deliberately confuse. With an aggressive distaste for fancy terminology, this session delves into OAuth 2.0 with and without JWT for user identity; AWS-style security for B2B with API keys; and OAuth 2.0 Proof of Possession, which merges both into two-factor bliss. Using a baseline microservice architecture, the presentation compares them, with a heavy focus on the wire, showing actual HTTP messages and analyzing their impact on load and security. Starting with basic authentication and a brief intro to hashing and signing, this is the perfect session to align the whole team.
Survival Strategies for API Documentation: Presentation to Southwestern Ontar...Tom Johnson
This is a presentation I gave to the Southwestern Ontario STC chapter on API documentation on Feb 2, 2015. For more details, see my blog at http://idratherbewriting.com. You can listen to the recorded presentation here: http://youtu.be/I8rGe2w1sAo.
apidays LIVE Australia 2020 - Contract-first API development with Spot by Fra...apidays
apidays LIVE Australia 2020 - Building Business Ecosystems
Contract-first API development with Spot
Francois Wout, Developer Happiness Engineer at Airtasker
Publishing API documentation -- WorkshopTom Johnson
These slides are from the REST API documentation workshop that I gave at the STC Summit 2015. For more details, see http://idratherbewriting.com/publishingapidocs.
No REST - Architecting Real-time Bulk Async APIsC4Media
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2eapFFq.
Michael Uzquiano talks about how to scale API to accept many items. He examines how to evolve the Evolution of ReST over HTTP to transactional, asynchronous bulk operations. He covers job descriptors, workers, the job queue and scaling workers across an API cluster elastically. He also talks about polling methods for job completion including HTTP long polling and WebSockets. Filmed at qconnewyork.com.
Michael Uzquiano is Founder and CTO of CloudCMS and Alpaca.js Committer.
Great Tools Heavily Used In Japan, You Don't Know.Junichi Ishida
The document discusses Japanese Perl developers who attended YAPC::EU 2015. It introduces many popular Perl modules created by Japanese developers, such as WebService::Simple for making web service requests, Riji for creating blogs, and GrowthForecast for visualizing metrics graphs. It encourages attendees to talk to the Japanese developers about their work or any questions. It emphasizes that Japanese developers prioritize speed and simplicity in their modules due to their culture of valuing efficiency.
Developing Rich Internet Applications with Perl and JavaScriptnohuhu
This document discusses developing Rich Internet Applications (RIAs) using the Ext JS JavaScript framework and the Perl RPC::ExtDirect module. It describes how RIAs work by handling all client interaction in JavaScript, communicating with the server asynchronously via AJAX calls. The Ext JS framework provides cross-browser compatibility, clean MVC architecture and low server overhead. RPC::ExtDirect allows Perl to serve as the backend, implementing the Ext.Direct protocol to integrate existing Perl code and work on any platform. Examples are given of using RPC::ExtDirect in a CGI application to publish APIs and route requests.
This document provides an overview of REST APIs and automated API documentation solutions. It discusses REST architecture and best practices for documenting REST APIs. It also covers popular automated documentation solutions like Swagger and RAML that can generate reference documentation from API specifications. The document demonstrates how to use Swagger and RAML specifications to automatically generate API documentation websites and interactive consoles. It compares the pros and cons of Swagger versus RAML and provides examples of professionally designed API documentation websites.
Continuous Integration with Open Source Tools - PHPUgFfm 2014-11-20Michael Lihs
Presentation about open source tools to set up continuous integration and continuous deployment. Covers Git, Gitlab, Chef, Vagrant, Jenkins, Gatling, Dashing, TYPO3 Surf and some other tools. Shows some best practices for testing with Behat and Functional Testing.
This document summarizes a developer's process in building a mobile-first dashboard application called Dashery over 2016. It involved standing up a Rails web app, building an Express API, creating a CLI with COA, developing a React Native mobile app, and integrating Azure Functions for serverless components. Challenges included learning new technologies like Docker, Kubernetes, React, Redux, and React Native. The developer also worked to design APIs, SDKs, and automate builds and deployments to launch the minimum viable product.
- Mojolicious is a web development framework for Perl that aims to rethink web development
- It provides a powerful routing system, full HTTP implementation, simple templating, built-in JSON support, elegant plugin system, and class reloader
- Installation is simple using CPAN and has no dependencies beyond Perl 5.8.1
- It includes classes for requests, responses, templates, JSON encoding/decoding, and more
- Plugins can hook into various stages of the request lifecycle
- Supports generating applications, running commands, and provides a simple but powerful way to build web applications and services in Perl
Are you interested in harnessing and analyzing the data that drives the Spark Web UI?
Are you keen to use that data to tune your applications or understand fluctuations in
runtime of your production applications? Do you want to understand the efficiency of
your Spark executors and system resources?
This presentation will help you do that and more, by walking through the wealth of data in
Spark application events. The event data can be used as a foundation for a Spark profiler and
advisor that analyzes application events in batch or real-time.
At the very least, you will be able to use the data to generate a summary page of your application execution, similar to the Hadoop job summary page, allowing you to compare executions.
Semelhante a How to Create the API Document from Real API and Localization (20)
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
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
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!
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
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.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
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.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
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.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
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.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
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.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
4. PAGEDAY2017/11/01#MOONGIFT/12
About this talk
• It is based on my experience
• I will share with you how to improving document
maintenance environment
• It’s not high level and no smart, but it’s realistic
4
7. PAGEDAY2017/11/01#MOONGIFT/12
GitHub Wiki
• 👍 Updating content on web browser and supporting version management.
• 👎 Dividing code and document. Don’t support pull request workflow.
• 👎 Don’t support localization.
7
8. PAGEDAY2017/11/01#MOONGIFT/12
Un documentation API
• Wiki didn’t cover everything and every update.
• Checking is very hard job that what is collect or not.
• Halfway document disturbs my job.
8
I've decided creating document from zero.
12. PAGEDAY2017/11/01#MOONGIFT/12
Translating is not localization
• Structure of sentence is completely different
• Many times, English needs longer sentence than Japanese
• Japanese has 3 types characters (Hiragana/Katakana/Kanji)
12
13. PAGEDAY2017/11/01#MOONGIFT/12
Document in Code
• 👍 Connecting code and document
• 👎 Too much comment in code for
documentation
• 👎 Programmer is NOT necessarily able
to write high readability document
• 👎 Most document generators don’t
support i18n.
13
desc 'Returns your public timeline.' do
summary 'summary'
detail 'more details'
params API::Entities::Status.documentation
success API::Entities::Entity
failure [[401, 'Unauthorized', 'Entities::Error']]
named 'My named route'
headers XAuthToken: {
description: 'Validates your identity',
required: true
},
XOptionalHeader: {
description: 'Not really needed',
required: false
}
hidden false
deprecated false
is_array true
nickname 'nickname'
produces ['application/json']
consumes ['application/json']
tags ['tag1', 'tag2']
end
get :public_timeline do
Status.limit(20)
end
26. PAGEDAY2017/11/01#MOONGIFT/12
Why Markdown?
• Most swagger based document generators don’t support localization.
• Many static site generators support Markdown format
• We can add more contents like tutorials, getting started, SDK help and more!
• We choose MkDocs for documentation.
26
https://www.mkdocs.org
28. PAGEDAY2017/11/01#MOONGIFT/12
API to Document
• Document is not code
• Too many comments lower readability of code
• Test code or kitchen sink is good tutorial for programmers
• 1 correct code is more worth than 100 words
28