SearchNode is the SaaS search solution for medium-big eCommerce companies, who want to optimize their on-site search, for maximum revenue

SearchNode

As a freelance web developer, app creator, and open-source maintainer, I have to constantly switch back and forth between multiple workflows, such as editing code, designing mockups, managing to-do lists, searching for icons and docs, executing command lines, checking emails with different accounts and so on. Each of these switches requires a constant stream of repetitive actions: Launch a code or image editor, and open the files of a specific project in it. Open a web browser, and navigate to the project in a task manager. Navigate to an icon website, set image filters, and perform a search. Open a webmail app, and switch accounts. Launch Terminal, and enter commands into it. etc… Everything is scattered in different places, and it turns the whole process into a real mess. And when working on multiple projects, things get even worse. I thought I could greatly improve my productivity by collecting everything I needed to get my work done in one place and organizing it into projects and workflows so that they had the right context. Projects and workflows will have clear boundaries, and switching between them will no longer be a nightmare. So, I came up with Freeter, an organizer app that does just that. And recently released it as a forever free and open-source project. In this short post, I'll show you how I’ve increased my productivity with Freeter, using three workflows as examples. I hope this gives you some ideas on how you too can improve your productivity. Workflows First, I analyzed my workflows and everything I often do when I’m looking for something I need while working on a project: When I’m developing an app or website, I often need to be able to access the task manager, open project files in code and image editors, search for icons and docs on specific websites, jot down quick ideas, and open the project repository in a web browser.


When I check email and Twitter DMs, I need access to the webmail and the Twitter DM page. I have multiple accounts and need to be logged in with project-specific ones.


When I release a new version of the app, I need to run the release command in the Terminal app, open the releases page in the git repository, open the task manager, and open the "planned feature" post editor in the Freeter community. Now, it’s time to turn them into Freeter workflows. App/Website Development To have quick access to the things I need to develop the app/website, I set up a workflow screen using the following widgets: Tasks: Webpage widget, to embed the project’s task manager right into the workflow screen.
Edit Code: File Opener widget, to open the project folder in the code editing program.
Edit Mockup: File Opener widget, to open the mockup file in the image editing program.
MDN: Web Query widget, to search MDN Web Docs website.
Node.js Docs: Web Query widget, to search Node.js Docs website.
Outline Icons: Web Query widget, to search a website with icons, filtered by outline icons.
Fill Icons: Web Query widget, to search a website with icons, filtered by fill icons.
Notes: Note widget, to jot down quick ideas while developing a feature.
Open Repo: Link Opener widget, to open the project repository in a web browser.
Bug Reports: Link Opener widget, to open the bug reports page in a web browser.
Feature Requests: Link Opener widget, to open the feature requests page in a web browser. This workflow allows me to immediately switch to the development context, launch everything I need to start the development process with a simple click, quickly search docs & icons, and quickly access the task list. Messages To check emails and Twitter DMs, I set up a workflow using two Webpage widgets: To embed the Google Mail inbox page. To embed the Twitter DM page. I also set Session Scope to Project in the widget settings so that I can be logged in under different accounts in other projects. This workflow allows me to quickly get simultaneous access to Google Mail and Twitter DMs for project-specific accounts. New Release To release a new version of the app, I set up a workflow with these five widgets: Release: Commander widget, to execute a command line in Terminal that asks for a new version number and starts a draft build of the new version. Open Releases: Link Opener widget, to open the releases page in the web browser. Tasks: A copy of Tasks from the App Dev workflow. I will need it to see all the Finished tasks in the current release. Planned Features: Webpage widget, to embed the Freeter community's "planned features" page into the workflow screen. With its help, I update the planned features and post about implemented features in the new release. Release steps: Note widget, to not forget to do something during the release. Thanks to this workflow, I can easily release a new version and post updates about new features. Switch Between Workflows Like a Superhero Now, when I switch between projects and workflows, I simply press Ctrl+Shift+F to bring Freeter to the front, open the workflow tab I need at the time, and get right to work. I hope this inspires you to organize your workflows too. To get started, visit the Freeter homepage. As a freelance web developer, app creator, and open-source maintainer, I have to constantly switch back and forth between multiple workflows, such as editing code, designing mockups, managing to-do lists, searching for icons and docs, executing command lines, checking emails with different accounts and so on. Each of these switches requires a constant stream of repetitive actions: Launch a code or image editor, and open the files of a specific project in it. Launch a code or image editor, and open the files of a specific project in it. Open a web browser, and navigate to the project in a task manager. Open a web browser, and navigate to the project in a task manager. Navigate to an icon website, set image filters, and perform a search. Navigate to an icon website, set image filters, and perform a search. Open a webmail app, and switch accounts. Open a webmail app, and switch accounts. Launch Terminal, and enter commands into it. Launch Terminal, and enter commands into it. etc… etc… Everything is scattered in different places, and it turns the whole process into a real mess. And when working on multiple projects, things get even worse. I thought I could greatly improve my productivity by collecting everything I needed to get my work done in one place and organizing it into projects and workflows so that they had the right context. Projects and workflows will have clear boundaries, and switching between them will no longer be a nightmare. So, I came up with Freeter , an organizer app that does just that. And recently released it as a forever free and open-source project . Freeter Freeter open-source project In this short post, I'll show you how I’ve increased my productivity with Freeter, using three workflows as examples. I hope this gives you some ideas on how you too can improve your productivity. Workflows First, I analyzed my workflows and everything I often do when I’m looking for something I need while working on a project: When I’m developing an app or website, I often need to be able to access the task manager, open project files in code and image editors, search for icons and docs on specific websites, jot down quick ideas, and open the project repository in a web browser. When I check email and Twitter DMs, I need access to the webmail and the Twitter DM page. I have multiple accounts and need to be logged in with project-specific ones. When I release a new version of the app, I need to run the release command in the Terminal app, open the releases page in the git repository, open the task manager, and open the "planned feature" post editor in the Freeter community. When I’m developing an app or website, I often need to be able to access the task manager, open project files in code and image editors, search for icons and docs on specific websites, jot down quick ideas, and open the project repository in a web browser. When I’m developing an app or website, I often need to be able to access the task manager, open project files in code and image editors, search for icons and docs on specific websites, jot down quick ideas, and open the project repository in a web browser. When I check email and Twitter DMs, I need access to the webmail and the Twitter DM page. I have multiple accounts and need to be logged in with project-specific ones. When I check email and Twitter DMs, I need access to the webmail and the Twitter DM page. I have multiple accounts and need to be logged in with project-specific ones. When I release a new version of the app, I need to run the release command in the Terminal app, open the releases page in the git repository, open the task manager, and open the "planned feature" post editor in the Freeter community. When I release a new version of the app, I need to run the release command in the Terminal app, open the releases page in the git repository, open the task manager, and open the "planned feature" post editor in the Freeter community. Now, it’s time to turn them into Freeter workflows. App/Website Development To have quick access to the things I need to develop the app/website, I set up a workflow screen using the following widgets: Tasks: Webpage widget, to embed the project’s task manager right into the workflow screen. Edit Code: File Opener widget, to open the project folder in the code editing program. Edit Mockup: File Opener widget, to open the mockup file in the image editing program. MDN: Web Query widget, to search MDN Web Docs website. Node.js Docs: Web Query widget, to search Node.js Docs website. Outline Icons: Web Query widget, to search a website with icons, filtered by outline icons. Fill Icons: Web Query widget, to search a website with icons, filtered by fill icons. Notes: Note widget, to jot down quick ideas while developing a feature. Open Repo: Link Opener widget, to open the project repository in a web browser. Bug Reports: Link Opener widget, to open the bug reports page in a web browser. Feature Requests: Link Opener widget, to open the feature requests page in a web browser. Tasks: Webpage widget, to embed the project’s task manager right into the workflow screen. Edit Code: File Opener widget, to open the project folder in the code editing program. Edit Mockup: File Opener widget, to open the mockup file in the image editing program. MDN: Web Query widget, to search MDN Web Docs website. Node.js Docs: Web Query widget, to search Node.js Docs website. Outline Icons: Web Query widget, to search a website with icons, filtered by outline icons. Fill Icons: Web Query widget, to search a website with icons, filtered by fill icons. Notes: Note widget, to jot down quick ideas while developing a feature. Open Repo: Link Opener widget, to open the project repository in a web browser. Bug Reports: Link Opener widget, to open the bug reports page in a web browser. Feature Requests: Link Opener widget, to open the feature requests page in a web browser. This workflow allows me to immediately switch to the development context, launch everything I need to start the development process with a simple click, quickly search docs & icons, and quickly access the task list. Messages To check emails and Twitter DMs, I set up a workflow using two Webpage widgets: To embed the Google Mail inbox page. To embed the Google Mail inbox page. To embed the Twitter DM page. To embed the Twitter DM page. I also set Session Scope to Project in the widget settings so that I can be logged in under different accounts in other projects. This workflow allows me to quickly get simultaneous access to Google Mail and Twitter DMs for project-specific accounts. New Release To release a new version of the app, I set up a workflow with these five widgets: Release: Commander widget, to execute a command line in Terminal that asks for a new version number and starts a draft build of the new version. Release: Commander widget, to execute a command line in Terminal that asks for a new version number and starts a draft build of the new version. Open Releases: Link Opener widget, to open the releases page in the web browser. Open Releases: Link Opener widget, to open the releases page in the web browser. Tasks: A copy of Tasks from the App Dev workflow. I will need it to see all the Finished tasks in the current release. Tasks: A copy of Tasks from the App Dev workflow. I will need it to see all the Finished tasks in the current release. Planned Features: Webpage widget, to embed the Freeter community's "planned features" page into the workflow screen. With its help, I update the planned features and post about implemented features in the new release. Planned Features: Webpage widget, to embed the Freeter community's "planned features" page into the workflow screen. With its help, I update the planned features and post about implemented features in the new release. Release steps: Note widget, to not forget to do something during the release. Release steps: Note widget, to not forget to do something during the release. Thanks to this workflow, I can easily release a new version and post updates about new features. Switch Between Workflows Like a Superhero Now, when I switch between projects and workflows, I simply press Ctrl+Shift+F to bring Freeter to the front, open the workflow tab I need at the time, and get right to work. Ctrl+Shift+F I hope this inspires you to organize your workflows too. To get started, visit the Freeter homepage . Freeter homepage Freeter homepage

How I Boosted My Productivity While Working on Multiple Projects

একাধিক প্রকল্পে কাজ করার সময় আমি কীভাবে আমার উত্পাদনশীলতা বাড়িয়েছি

Wie ich meine Produktivität bei der Arbeit an mehreren Projekten steigerte

Cómo impulsé mi productividad mientras trabajaba en varios proyectos

Comment j'ai augmenté ma productivité tout en travaillant sur plusieurs projets

मैंने कई परियोजनाओं पर काम करते हुए अपनी उत्पादकता कैसे बढ़ाई

複数のプロジェクトに取り組みながら生産性を高める方法

여러 프로젝트를 진행하면서 생산성을 높이는 방법

Como aumentei minha produtividade ao trabalhar em vários projetos

Как я повысил свою продуктивность, работая над несколькими проектами

Birden Fazla Projede Çalışırken Verimliliğimi Nasıl Artırdım

Cách tôi tăng năng suất khi làm việc trên nhiều dự án

我如何在处理多个项目时提高工作效率

Node.js Monitoring Made Easy

There can be one or many solutions to a given problem, depending on the scenario, As there can be many ways to solve that problem. Lets say you need to do something straight forward like a math multiplication. Clearly there is one correct solution, but many algorithms to multiply, depending on the size of the input. Now, take a more complicated problem, like playing a game(imagine your favorite game, chess, poker, call of duty, DOTA, anything..). In most of these games, at a given point in time, you have multiple moves that you can make, and you choose the one that gives you best possible outcome. In this scenario, there is no one correct solution, but there is a best possible solution, depending on what you want to achieve. Also, there are multiple ways to approach the problem, based on what strategy you choose to have for your game play. Think about how do you approach a problem. It has to search through the solution space to provide the best result. As to, what is considered as the best result and why a solution is preferred over another, is something we program into the AI. In this article we, will see how an Artificial Intelligence searches for the solution to a given problem. The rational agents for Artificial Intelligence approach the problems in a similar fashion. This makes search algorithms important in the study of Artificial Intelligence. To get a better understanding of Artificial Intelligence systems, refer _When you think of Artificial Intelligence, the first thing that comes to mind is either Robots or Machines with Brains…_hackernoon.com So you think you know what is Artificial Intelligence? To learn more about Rational Agents powered by Artificial Intelligence, refer _There are multiple approaches that you might take to create Artificial Intelligence, based on what we hope to achieve…_hackernoon.com Rational Agents for Artificial Intelligence Search The simple reflex agents don’t specifically search for best possible solution, as they are programmed to perform a particular action for a particular state. On the contrary, Here, the agent has to consider the impact of the action on the future states. Such agents search through all the possible solutions to find the best possible solution for the given problem. the artificially intelligent agents that work towards a goal, identify the action or series of actions that lead to the goal. The series of actions that lead to the goal becomes the solution for the given problem. Defining the problem The agent should be clear about the goal. Let’s look at the factors that need to be defined for formulation of a problem. This means we need to program the agent, such that it can clearly classify a state as goal. Since there are many ways to reach that goal, the agent should also be able to evaluate a solution and determine its preference for a solution. : The state in which the agent starts or initial condition of the agent. Initial State : All states that are reachable from initial state by any sequence of actions or all possible states that the agent can take. This is also referred to as State space. States : All possible actions that the agent can execute. Specifically, it provides the list of actions, that an agent can perform in a particular state. This is also referred to as Action space. Actions : This property describes the results of each action taken in a particular state. Transition Model : A way to check, whether a state is the goal. Goal Test : A function that assigns a numeric cost to a path w.r.t. performance measure Path Cost Problem formulation provides an easy way to design a rational agent. Search Space Unlike state space, which is a physical configuration, the search space is an abstract conﬁguration represented by a search tree or graph of possible solutions. A node has depth, path cost and associated state in the state space. A search tree is used to model the sequence of actions. It is constructed with initial state as the root. The actions taken make the branches and the nodes are results of those actions. The search space is divided into 3 regions, namely Explored Frontier Unexplored Strategical order of these moves performs a better search. The moves are . Search involves moving the nodes from unexplored region to the explored region. also known as node expansion Picking the order of node expansion has provided us with different search strategies that are suited for different kind of problems. Different search strategies are evaluated along completeness, time complexity, space complexity and optimality. The time and space complexity are measured in terms of: b: maximum branching factor of the search tree (actions per state). d: depth of the solution m: maximum depth of the state space (may be ∞) (also noted sometimes D). Types of Search There are 2 kinds of search, based on whether they use information about the goal. Uninformed Search . This means that it does not use any information that helps it reach the goal, like closeness or location of the goal. The strategies or algorithms, using this form of search, ignore where they are going until they find a goal and report success. This type of search does not use any domain knowledge The basic uninformed search strategies are: BFS(Beadth First Search): It expands the shallowest node(node having lowest depth) first. DFS(Depth First Search): It expands deepest node first. DLS(Depth Limited Search): It is DFS with a limit on depth. IDS(Iterative Deepening Search): It is DFS with increasing limit UCS(Uniform Cost Search): It expands the node with least cost(Cost for expanding the node). Informed Search It generally uses a heuristic function that estimates how close a state is to the goal. This heuristic need not be perfect. This function is used to estimate the cost from a state to the closest goal. This type of search uses domain knowledge. The basic informed search strategies are: Greedy search (best first search) : It expands the node that appears to be closest to goal A* search : Minimize the total estimated solution cost, that includes cost of reaching a state and cost of reaching goal from that state. Search Agents are just one kind of algorithms in Artificial Intelligence. Here, an AI has to choose from a large solution space, given that it has a large action space on a large state space. This involves formulating the problem, that your AI is going to solve, in the right way. Some of the real world examples, where they are being used are: Selecting the right search strategy for your Artificial Intelligence, can greatly amplify the quality of results. : Example of applications include tools for driving directions in websites, in-car systems, etc. Route finding problem : Find the shortest tour to visit each city exactly once. Travelling salesman problem : position million of components and connections on a chip to minimize area, shorten delays. VLSI Layout : Special case of route ﬁnding for robots with no speciﬁc routes or connections, where state space and action space are potentialy infinite. Robot Navigation : ﬁnd an order in which to assemble parts of an object which is a diﬃcult and expensive geometric search. Automatic assembly sequencing : ﬁnd a sequence of amino acids that will fold into a 3D protein with the right properties to cure some disease. Protein design Although, we are just scratching the surface, this article provides you with an outline of what kind of algorithms drive an AI. Depending on the problem, an Artificial Intelligence can use many other algorithms involving Machine Learning, Bayesian networks, Markov models, etc. I’ll soon be elaborating on these AI algorithms that drive rational search agents, and other algorithms including use of machine learning in Artificial Intelligence. So, for being more aware of the world of A.I., . It’s the best way to find out when I write more articles like this. follow me If you liked this article, be sure to for this article below and if you have any questions, and I will do my best to answer. show your support by clapping leave a comment You can also follow me on , or . I’d love to hear from you. Twitter at @Prashant_1722 email me directly find me on linkedin That’s all folks, Have a nice day :) Credit Content for this article is inspired and taken from, Artiﬁcial Intelligence, A Modern Approach. Stuart Russell and Peter Norvig. Third Edition. Pearson Education.

Search Algorithms in Artificial Intelligence

Node.js comes with a lot of CLI options to expose built-in debugging & to modify how V8, the JavaScript engine works. In this post, we have collected the most important CLI commands to help you become more productive. Accessing Node.js CLI Options To get a full list of all available Node.js CLI options in your current distribution of Node.js, you can access the manual page from the terminal using: $ man node

Usage: node [options] [ -e script | script.js ] [arguments]       node debug script.js [arguments]

Options:  -v, --version    print Node.js version  -e, --eval       script evaluate script  -p, --print      evaluate script and print result  -c, --check      syntax check script without executing ... As you can see in the first usage section, you have to provide the optional options before the script you want to run. Take the following file: console.log(new Buffer(100)) To take advantage of the option, you have to run your application using: --zero-fill-buffers $ node --zero-fill-buffers index.js This way the application will produce the correct output, instead of random memory garbage: <Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... > CLI Options Now as we saw how you instruct Node.js to use CLI options, let’s see what other options are there! or --version -v Using the , or short, , you can print the version of Node.js you are using. node --version node -v $ node -v v6.10.0 or --eval -e Using the option, you can run JavaScript code right from your terminal. The modules which are predefined in REPL can also be used without requiring them, like the or the module. --eval http fs $ node -e 'console.log(3 + 2)' 5 or --print -p The option works the same way as the , however it prints the result of the expression. To achieve the same output as the previous example, we can simply leave the : --print --eval console.log $ node -p '3 + 2' 5 or --check -c Available since v4.2.0 The option instructs Node.js to check the syntax of the provided file, without actually executing it. --check Take the following example again: console.log(new Buffer(100) As you can see, a closing is missing. Once you run this file using , it will produce the following output: ) node index.js /Users/gergelyke/Development/risingstack/mastering-nodejs-cli/index.js:1(function (exports, require, module, __filename, __dirname) { console.log(new Buffer(100)

^ SyntaxError: missing ) after argument list at Object.exports.runInThisContext (vm.js:76:16) at Module._compile (module.js:542:28) at Object.Module._extensions..js (module.js:579:10) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) at Module.runMain (module.js:604:10) at run (bootstrap_node.js:394:7) Using the option you can check for the same issue, without executing the script, using . : --check node --check index.js The output will be similar, except you won't get the stack trace, as the script never ran /Users/gergelyke/Development/risingstack/mastering-nodejs-cli/index.js:1(function (exports, require, module, __filename, __dirname) { console.log(new Buffer(100) 

^ SyntaxError: missing ) after argument list at startup (bootstrap_node.js:144:11) at bootstrap_node.js:509:3 The **--check** option can come handy, when you want to see if your script is syntactically correct, without executing it. --inspect[=host:port] Available since v6.3.0 Using will activate the inspector on the provided host and port. If they are not provided, the default is . The debugging tools attached to Node.js instances communicate via a tcp port using the . node --inspect 127.0.0.1:9229 Chrome Debugging Protocol --inspect-brk[=host:port] Available since v7.6.0 The has the same functionality as the option, however it pauses the execution at the first line of the user script. --inspect-brk --inspect $ node --inspect-brk index.js Debugger listening on port 9229.Warning: This is an experimental feature and could change at any time.

To start debugging, open the following URL in Chrome: 

chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/86dd44ef-c865-479e-be4d-806d622a4813 Once you have ran this command, just copy and paste the URL you got to start debugging your Node.js process. --zero-fill-buffers Available since v6.0.0 Node.js can be started using the command line option to force all newly allocated Buffer instances to be automatically zero-filled upon creation. The reason to do so is that newly allocated instances can contain sensitive data. --zero-fill-buffers Buffer It should be used when it is necessary to enforce that newly created **Buffer** instances cannot contain sensitive data, as it has significant impact on performance. Also note, that some Buffer constructors got deprecated in _v6.0.0_ : new Buffer(array) new Buffer(arrayBuffer[, byteOffset [, length]]) new Buffer(buffer) new Buffer(size) new Buffer(string[, encoding]) Instead, you should use _Buffer.alloc(size[, fill[, encoding]])_ , _Buffer.from(array)_ , _Buffer.from(buffer)_ , _Buffer.from(arrayBuffer[, byteOffset[, length]])_ and _Buffer.from(string[, encoding])_ . You can read more on the security implications of the Buffer module on the Synk blog . --prof-process Using the , the Node.js process will output the v8 profiler output. --prof-process To use it, first you have to run your applications using: node --prof index.js Once you ran it, a new file will be placed in your working directory, with the prefix. isolate- Then, you have to run the Node.js process with the option: --prof-process node --prof-process isolate-0x102001600-v8.log > output.txt This file will contain metrics from the V8 profiler, like how much time was spent in the C++ layer, or in the JavaScript part, and which function calls took how much time. Something like this: To get a full list of Node.js CLI options, check out the official documentation here . V8 Options You can print all the available V8 options using the command line option. --v8-options Currently V8 exposes more than a 100 command line options — here we just picked a few to showcase some of the functionality they can provide. Some of these options can drastically change how V8 behaves, use them with caution! --harmony With the harmony flag, you can enable all completed harmony features. --max_old_space_size With this option, you can set the maximum size of the old space on the heap, which directly affects how much memory your process can allocate. This setting can come handy when you run in low memory environments. --optimize_for_size With this option, you can instruct V8 to optimize the memory space for size — even if the application gets slower. Just as the previous option, it can be useful in low memory environments. Environment Variables NODE_DEBUG=module[,…] Setting this environment variable enables the core modules to print debug information. You can run the previous example like this to get debug information on the core component : module (instead of module, you can go for _http_ , _fs_ , etc...) $ NODE_DEBUG=module node index.js The output will be something like this: MODULE 7595: looking for "/Users/gergelyke/Development/risingstack/mastering-nodejs-cli/index.js" in ["/Users/gergelyke/.node_modules","/Users/gergelyke/.node_libraries","/Users/gergelyke/.nvm/versions/node/v6.10.0/lib/node"] 

MODULE 7595: load "/Users/gergelyke/Development/risingstack/mastering-nodejs-cli/index.js" for module "." NODE_PATH=path Using this setting, you can add extra paths for the Node.js process to search modules in. OPENSSL_CONF=file Using this environment variable, you can load an OpenSSL configuration file on startup. For a full list of supported environment variables, check out the official Node.js docs . As you can see, the CLI is a really useful tool which becomes better with each Node version! If you’d like to contribute to its advancement, you can help by checking out the currently open issues at ! https://github.com/nodejs/node/labels/cli Originally published at blog.risingstack.com on April 11, 2017.

Mastering the Node.js CLI & Command Line Options

makes it easy to build slick apps and websites for any vertical or industry. Cosmic JS has stored existing codebases on for everything from a standard to . Below I detail 5 professional web application templates that document their programming language, general layout, a demo & the ability to view and employ the code base. Cosmic JS GitHub Node.js boilerplate cross-platform iOS & Android React Native codebases If you haven’t already, with is as easy as choosing a new username and password or simply signing up through your GitHub account. You can filter through apps based on the industry, structure or programming language, all in responsive demo fashion. signing up Cosmic JS Real Estate App Bootstrap | Node.js | Multi-page App Template This real estate website satisfies some common website requirements including dynamic pages, listing management, blog articles, author management, SEO ability, contact form and website search. View demo .View codebase on .Visit Cosmic JS . here GitHub Apps Page Photography App Bootstrap | Node.js | Multi-Page App Template This slick photography website is built using Node.js on the server and Bootstrap on the frontend. It is fully responsive down to mobile, includes a contact form and a gallery section powered by . Photoswipe View demo .View codebase on .Visit Cosmic JS . here GitHub Apps Page Healthcare App Node.js | Bootstrap | Multi-Page App Template Website built using the . Fully responsive down to mobile, SEO ready, includes a contact form and full site search. Node.js Website Boilerplate View demo .View codebase on .Visit Cosmic JS . here GitHub Apps Page Roofing App Node.js | Bootstrap | Multi-page App Template Website built using the . Fully responsive down to mobile, SEO ready, includes a contact form and full site search. Node.js Website Boilerplate View demo .View codebase on .Visit Cosmic JS . here GitHub Apps Page Wedding App AngularJS | Single-Page App Template This Angular JS single page wedding website makes it easy to edit content, update photos and plan for the big day. View demo .View codebase on .Visit Cosmic JS . here GitHub Apps Page is an that makes it easy to manage applications and content. If you have questions about the Cosmic JS API, please reach out to the founders on or . Cosmic JS API-first cloud-based content management platform Twitter Slack Carson Gibbons is the Co-Founder & CMO of Cosmic JS , an API-first Cloud-based Content Management Platform that decouples content from code, allowing devs to build slick apps and websites in any programming language they want.

Industry-Tailored App Examples: Node.js | ReactJS | AngularJS | Bootstrap

In this post I'll show some tips we used at to boost our productivity thanks to a fully dockerized environment. Hunteed development This is the part 1/2 where we describe a basic configuration for a dockerized development environment. we'll explain how to put this configuration on steroids so that you never wait for a anymore. In part 2 npm install/gem install Why should I change anything to my workflow ? With a properly setup configuration, we now appreciate the following features: docker of a work-ready environment. From scratch. Yep. One-click install of specific version/dependencies. As a freelancer you might work on several projects, each one of them using different versions of node/mongo/elastic-search…etc. That should not be an issue at all. No local installation .CI and production server should work EXACTLY the same as my dev environment. If it works home, it works in prod The front-devs, designers, integrators can have partial knowledge of the infrastructure. We want an integrator to be able to work on our project without having to know how to install a mongodb server. Well, he/she should not even care about knowing if there is a database at all. No knowledge of the infrastructure is needed to work on the project. In addition to these features, we want what has now become a standard in any modern coding configuration: : changing the code should trigger a sequence of tests that are directly visible for the developer continuous testing a change in your code should appear quickly on your browser, without needing to reboot everything manually Hot reloading: is plugged in, and every commit fires a complete-testing suite on the CI-server. Continuous integration Yep. So we will basically get rid of Welcome to , let's spend 3 days together with the CTO hacking your computer until you can actually work on the project Hunteed I don't get it, it works on my machine ! How do I change my installed version of mongodb/mysql/elastic-search/node/phantom/ruby/whatever so it is compliant to your stack ? Npm install / gem install / whatever install didn't work on my machine. What are the required dependencies again ? I don’t get it, it works on my machine ! (again !?) I don't get it, it does NOT work on my machine ! (yeah, that also) All right, let's slaughter the monster ! 2. Make it work you can find a tiny demo project : Here git clone https://github.com/aherve/simple-dockerized-dev-env Let's have a look at what you can do with it before we go into the details: Build the entire environment: docker-compose build This will download the proper containers so you can use an out-of-the-box install of node, mongodb. It will also run an npm install for you. Note also that if you run this command again, docker will use cache so the npm install and images downloads are not performed twice: If you change the file, then the command will be run again. Exactly what we need ! package.json npm install One-time testing: docker-compose run test This will run the tests. If you launched this command for the first-time, did you notice how it installed everything for you ? Note that a instance is also launched. Your test suite is actually connected to a mongodb although we don't actually use it here. db_1 Launch-server/script docker-compose run hello> hello is loaded ! Continuous testing docker-compose run autotest Unlike the simple test command, this one will start a watcher that tracks a change in the code. try changing the file and watch the test fail instantly ! /src/spec.js docker run on a virtual environment when using osX. therefore, the file changes are not detected out of the box.Fortunately, took care of this problem for you. Simply install dinghy and use it as a docker virtual machine. It will then work out of the box. Note for mac-users : these guys Run any arbitrary command docker-compose run hello npm listdocker-compose run test env | grep NODE_ENV run hello <something> will simply override the default instruction of our docker-compose file. command 3. How does it work ? All the docker-related mechanics are located in two files: Dockerfile : This file describe the instructions for building a container that will be able to run our code. In this case, it consists of a pre-installation of node (alpine-node), on which we create a working directory (/app) where we put our package.json file. Then we run npm install so that the javascript libraries are available from within the container. Rubyists can compare to a command, whereas the file compares to a file. npm install gem install package.json Gemfile Note that our source code is not (yet) included in the container. 2. docker-compose: This file defines and orchestrate containers. In this example we use our main 3 times to build very similar images: and . You'll notice that these are actually the same containers, but we pass different environment variables, as well as different default commands. Dockerfile hello, autotest test The instruction will mount our local directory into the container. More importantly, any change in your local directory will have an instant impact on the running container. As a matter of fact, they are literally the same file. volumes src Unlike what is located in , the has been added by an ADD command before running an command. This means you will have to rebuild the container if the were to change. /src package.json install package.json And finally, the last image is a running image. This image is directly downloaded from docker-hub and will start a working db server out of the box. The other containers can access the db thanks to the command. db mongodb links 4. Bonus : CI servers also know about docker ! Since you can install the environment regardless of your setup…. then so does the CI-server \o/ At we use the docker-based infrastructure of for both continuous integration & deployment. Hunteed codeship Good news, they can read a docker-compose file as well as you can. Simply add a file where you tell codeship to run your tests: codeship-steps.yml And codeship will run your test with the EXACT configuration you had. How awesome is that ? 5. Conclusion So far we have a working environment that allows any contributor to onboard in one-click, regardless of his/her personnal computer configuration. The only drawback of this particular setup is that a will run a fresh everytime you change the file. This can take a lot of time, as all the libraries are re-installed from scratch. . we will improve our configuration to significantly boost this step. docker-compose build npm install package.json In part 2 Happy coding ! Go to part 2/2 to see how to put your workflow on steroid ! Further reading : Dockerized dev environment for building a node-express api using typescript

How we happily dockerized our development environment (part 1/2)

Before starting a new coding task, I find it’s usually worthwhile to spend at least a little time trying to find a related working example, especially when the task touches on unfamiliar libraries or concepts. If I can find a good example, skimming it shifts my brain in the right direction and it feels like I’m absorbing some of its lessons. My project is more likely to go smoothly, even if I don’t use a single line of code from the example. Finding that good example, however, isn’t always so easy and the search itself might waste a lot of time. This article offers tips on how to quickly find nice code samples. The Treasure Hunt Takes Too Long Usually my hope is to find a repository that uses the library or context I’m researching, some repo that’s generally well written and isn’t too huge or overwhelming. I’ve found that search engines, even ones dedicated to code search, are mostly frustrating and unproductive. Simple searches using reasonable keywords rarely work, persisting leads to madness. Search Engine Filters For our sideways search, we’ll use advanced search operators, mostly the and Google filters. Some other ones can be handy too, here's a nice reference: . inurl: site: search filter cheat sheet Bing offers but not a URL filter. If you prefer Bing, their filter should usually be an ok substitute for . similar ones intitle: inurl We’ll use these advanced filters to search non-code files, ones that are properly indexed by the search engine even when the code next to it is not. With , we can filter to specific text files like Dockerfiles or READMEs or, powerfully, dependency manifest files like Node’s , Python’s , Ruby’s , etc. inurl package.json requirements.txt Gemfile Some sites explicitly offer dependency graph search as a feature (including package managers and GitHub) but I find that Google’s page rank voodoo beats these. Example Of a Successful Search Let’s say my current task is roughing out a testing framework for an project. Electron I might start my hunt with: . (If you're not familiar with Node, is a popular testing framework.) The filter restricts results to pages with in the URL. inurl:package.json "electron" "mocha" mocha inurl package.json I’ll start opening tabs that look promising, swapping search terms now and then, maybe replacing “mocha” with “jest” (another test framework) then trying again with a filter to limit results to GitHub (with ) then GitLab. site site:github.com Want your example in TypeScript? Add a or search term. "@types" "tsc" In a couple minutes, we find and , repositories that are popular, up-to-date, and well-maintained. They’re also huge and overwhelming. I’m sure there are great lessons to learn within, but we’re in a hurry. Our search also turns up some small, wholesome repositories, ones that are easier to skim like: , and . Facebook Flipper Rocket.Chat sindresorhus/electron-serve checksum-validator I won’t say we struck gold, but evaluating these working examples offers a big productivity boost and we found them in just a few minutes. One of the smaller projects shows us how to use for headless testing, the other helps us consider using smoke tests. (Personally, the exercise helped me also decide to move all direct calls to Electron out of the User Interface via , making the exercise extra-worthwhile.) spectron @wranggle/rpc Local Collections Let’s say we’re new to Django and want to see some real world examples of it making database queries. GROUP BY Some potential search keywords pop out when skimming the official documentation on . We might try GitHub’s search tab on some, ( ) but I’ve had mostly bad luck with it. db aggregation Code Login required; submit search then click “Code” tab We might try a Google search on and that would turn up some examples, but there's a better way. "from django.db.models import Q" filetype:py Instead of searching directly for uses of our aggregation query, let’s build up a locally-saved collection of nice, well-written example projects and search that. You may have seen , but did you know you can search for topics too? Submit a , then click on the “Topic” tab. These are self-tagged by the repository owner but it’s still a great way to find sample repositories. GitHub Topics search There’s likely a nice CRM, CMS, blog, and e-commerce app in most any language. (Plus maybe even a ToDo list!) GitHub’s Topic and Repository tabs help us find polished, popular, and well-maintained projects that we can add to our local collection. I suggest saving a local copy of all that look good. You can then search them using your own IDE far more effectively than any online tool I’ve ever tried. You’ll have far better results than using GitHub’s in-repository search and will be able to revisit these same examples in the future. Sure enough, this approach reveals plenty usage examples for that aggregation query, and better yet, we can evaluate how they’re testing them. Human And Awesome Human Content When investigating some coding problem, regular searches turn up articles/tutorials, answers on StackOverflow/Gitter, discussions on HackerNews/Reddit, etc. From the perspective of finding a pre-task primer, you know best if one of these would be more helpful than sample code. Regardless, high quality resources of either type can often be found in a curated list, and the easiest to find are the . awesome lists When I yet again forget the CSS syntax for flexbox items, a plain search always takes me to , and it’s nice enough. But if I take a bit more time to find an awesome list from or by searching on , I'll find a . css-tricks awesome.re awesome flexbox great resource Code Search Sites If you want to search for a specific code blurb, might be worth a try. Of the direct code search tools, it seems to be the best when you don’t already have a list of known repositories. searchcode.com For that aggregation query, a search on seems to return decent results. "from django.db.models import Q" The same search using GitHub’s code-search feature produces far worse results. Hopefully GitHub/Microsoft will continue to invest in code search. (I would love for them to add an “exact match” feature, and a feature that does a deep code search in each repository I follow or have starred.) , a code search product, might be worth a look for teams that want to share and search their own curated list of repositories. You need to know which repositories you want to index ahead of time though. (I’ve never tried it but that feature sounds useful.) SourceGraph Noticing When it’s a Waste Of Time Let’s take a look at a rougher search process. Say our next task is to add to a different project. We haven’t yet started and we’re not (yet?) stuck, we’re just following the good general practice of doing our initial research. Webpack code splitting A search on fails, returning very few results. Changing to returns slightly more but a lot of it is noise. We find some examples but spend a lot of time sifting. "splitChunks" inurl:webpack.config.js inurl intitle:webpack.config We can’t do a dependency search as we did for our Electron task because is part of WebPack core, it doesn’t add a dependency. Scooting further sideways with a dependency search on something else in the general neighborhood ( ) produces decent results but getting to that keyword required unnecessary research. splitChunks mini-css-extract-plugin Searching for a Gist ( ) also leads us to good example uses, but not to a full example repository. (I don't know why Gist is indexed but the master repository is not. permits both.) "splitChunks" site:gist.github.com Robots.txt Overall, in this case, using human-curated resources would have been a better use of time. Or I should have stopped the search early, to possibly pick it up again after attempting the task myself. When To Stop? Searching for sample code can be an open-ended exercise. It’s really easy to spend unproductive hours searching for and reading samples. Keep in mind that finding or understanding a given sample isn’t the goal, you have your own coding project to finish. That stubborn drive to finish what you’ve started is usually a positive force, but if finding a sample isn’t vital and you’re not turning up anything useful, it’s better to move on. Otherwise, maybe set a time range for the exercise. If you’re unfamiliar with the current topic, give it a relatively higher upper bound. If you hit the limit but the exercise still feels productive, adjust it upwards. In contrast, move on early if the samples aren’t useful or if you just feel ready to start your own task. The best sign that the exercise was a success is if you’re getting ideas on how to do things better than the sample. On the lower time bound, consider spending some minimum time looking at sample code before starting a new task. Reading code is way less fun than writing it but there’s a lot to learn in other people’s repositories, even if you already know how to accomplish your task. If you have any other ideas or techniques for finding sample code, please pass them along! Photo credits in order of appearance: Elijah O'Donnell Pexels Milada Vigerova Ian Stauffer Pexels TeroVesalainen Daniel Sampaio 3D_Maennchen Prawny

Code Search is a superpower

Authors:
(1) Nicholas Farn, Microsoft Corporation {Microsoft Corporation {nifarn@microsoft.com};
(2) Richard Shin, Microsoft Corporation {eush@microsoft.com}. Table of Links Abstract and Intro Dataset Design Evaluation Methodology Experiments and Analysis Related Work Conclusion, Reproducibility, and References A. Complete list of tools B. Scenario Prompt C. Unrealistic Queries D. Nuances comparing prior work A COMPLETE LIST OF TOOLS We include the complete list of plugins and tools used in ToolTalk, and their corresponding descriptions. AccountTools This API contains tools for account management. • ChangePassword Changes the password of an account. • DeleteAccount Deletes a user’s account, requires user to be logged in. • GetAccountInformation Retrieves account information of logged in user. • LogoutUser Logs user out. • QueryUser Finds users given a username or email. • RegisterUser Register a new user. • ResetPassword Resets the password of a user using a verification code. • SendVerificationCode Initiates a password reset for a user by sending a verification code to a backup email. • UpdateAccountInformation Updates account information of a user. • UserLogin Logs in a user. Alarm This API contains tools for managing alarms. • AddAlarm Sets an alarm for a specific time. • DeleteAlarm Removes an alarm given an alarm id. • FindAlarms Finds alarms a user has set. Calendar This API lets a users manage events in their calendar. • CreateEvent Adds events to a user’s calendar. • DeleteEvent Deletes events from a user’s calendar. • ModifyEvent Allows modification of an existing event. • QueryCalendar Queries for events that occur in a time range. Email This API lets a user search and send emails. • SearchInbox Searches for emails matching filters returning 5 most recent results. • SendEmail Sends an email on behalf of a given user. Message This API lets a user search and send messages. • SearchMessages Searches messages matching filters returning 5 most recent results. • SendMessage Sends a message to another user. Reminder A suite of APIs for managing reminders for a TODO list. • AddReminder Add a reminder with an optional due date. • CompleteReminder Complete a reminder. • DeleteReminder Delete a reminder. • GetReminders Get a list of reminders. Weather Get weather information of a location. • CurrentWeather Get the current weather of a location. • ForecastWeather Get the 3-day weather forecast of a location. • HistoricWeather Get historic weather information of a location by month. B SCENARIO PROMPT Task You will be provided with a list of APIs. These APIs will have a description and a list of parameters and return types for each tool. Your task involves creating 3 varied, complex, and detailed user scenarios that require at least 5 API calls to complete involving at least 3 different APIs. One of these APIs will be explicitly provided and the other two will be chosen by you. For instance, given the APIs: SearchHotels, BookHotel, CancelBooking, GetNFLNews. Given that GetNFLNews is explicitly provided, your scenario should articulate something akin to: "The user wants to see if the Broncos won their last game (GetNFLNews). They then want to see if that qualifies them for the playoffs and who they will be playing against (GetNFLNews). The Broncos did make it into the playoffs, so the user wants watch the game in person. They want to look for hotels where the playoffs are occurring (GetNBANews + SearchHotels). After looking at the options, the user chooses to book a 3-day stay at the cheapest 4-star option (BookHotel)." This scenario exemplifies a scenario using 5 API calls. The scenario is complex, detailed, and concise as desired. The scenario also includes two APIs used in tandem, the required API, GetNBANews to search for the playoffs location and SearchHotels to find hotels based on the returned location. Usage of multiple APIs in tandem is highly desirable and will receive a higher score. Ideally each scenario should contain one or more instances of multiple APIs being used in tandem. Note that this scenario does not use all the APIs given and re-uses the " GetNBANews" API. Re-using APIs is allowed, but each scenario should involve at least 3 different APIs. Note that API usage is also included in the scenario, but exact parameters are not necessary. You must use a different combination of APIs for each scenario. All APIs must be used in at least one scenario. You can only use the APIs provided in the APIs section. Note that API calls are not explicitly mentioned and their uses are included in parentheses. This behaviour should be mimicked in your response. Deliver your response in this format: ‘‘‘ Scenario 1: <Scenario1>
Scenario 2: <Scenario2>
Scenario 3: <Scenario3> ‘‘‘ APIs ‘‘‘ {{API_DOCS}} ‘‘‘ Response Required API: {{REQUIRED_API}} Scenarios with >=5 API calls: ‘‘‘ - Scenario 1: C UNREALISTIC QUERIES Below are some examples of unrealistic queries gathered from various sources. These queries are useful for generating potentially complex tool interactions or unusual combinations of tools. However, as a consequence, they are unrealistic for various reasons such as forcing the usage of disparate APIs in situations a human is unlikely to ask for, explicitly asking for API endpoints which end users are unlikely to know of, or generally being unnaturally long and explicit. • “I’m working on a logistics project for my company and need to check the health of the SQUAKE API. Can you verify the API health by calling the ‘Checkhealth’ API endpoint? Additionally, I would like to retrieve the list of projects using the ‘Projects’ API endpoint.” (Qin et al., 2023b) • “How many singers have the average number of albums of singers in Beijing? Gives the square root of this number.” (Ruan et al., 2023) • “I am looking for x-large, red color women faux fur lined winter warm jacket coat, and price lower than 70.00 dollars.” Yao et al. (2022a) • “Can you retrieve the contact details of the ‘Gondrand’ customs agency in New Caledonia? I’m particularly interested in their postal code, email, name, and phone number. Also, please provide a list of all available transitaires. Begin!!!” Qin et al. (2023b) D NUANCES COMPARING PRIOR WORK Nuances comparing prior work from Table 5. ReAct and ART evaluate on hard QA tasks, but these tasks traditionally do not require the usage of tools to complete. We also note API-Bank fits all criteria. However, its level 1-2 examples are automated but simple. In comparison, its level 3 examples are complex but require manual evaluation. ToolBench’s tasks require hard to use tool, but have shallow solution paths. Their more complex environments have deeper solution paths, but re-use the existing datasets of WebShop (Yao et al., 2022a) and TableTop (Liang et al., 2023). This paper is available on arxiv under CC 4.0 license. Authors: (1) Nicholas Farn, Microsoft Corporation {Microsoft Corporation {nifarn@microsoft.com}; (2) Richard Shin, Microsoft Corporation {eush@microsoft.com}. Authors: Authors: (1) Nicholas Farn, Microsoft Corporation {Microsoft Corporation {nifarn@microsoft.com}; (2) Richard Shin, Microsoft Corporation {eush@microsoft.com}. Table of Links Abstract and Intro Abstract and Intro Dataset Design Dataset Design Evaluation Methodology Evaluation Methodology Experiments and Analysis Experiments and Analysis Related Work Related Work Conclusion, Reproducibility, and References Conclusion, Reproducibility, and References A. Complete list of tools A. Complete list of tools B. Scenario Prompt B. Scenario Prompt C. Unrealistic Queries C. Unrealistic Queries D. Nuances comparing prior work D. Nuances comparing prior work A COMPLETE LIST OF TOOLS We include the complete list of plugins and tools used in ToolTalk, and their corresponding descriptions. AccountTools This API contains tools for account management. AccountTools • ChangePassword Changes the password of an account. ChangePassword • DeleteAccount Deletes a user’s account, requires user to be logged in. DeleteAccount • GetAccountInformation Retrieves account information of logged in user. GetAccountInformation • LogoutUser Logs user out. LogoutUser • QueryUser Finds users given a username or email. QueryUser • RegisterUser Register a new user. • ResetPassword Resets the password of a user using a verification code. ResetPassword • SendVerificationCode Initiates a password reset for a user by sending a verification code to a backup email. SendVerificationCode • UpdateAccountInformation Updates account information of a user. UpdateAccountInformation • UserLogin Logs in a user. UserLogin Alarm This API contains tools for managing alarms. Alarm • AddAlarm Sets an alarm for a specific time. AddAlarm • DeleteAlarm Removes an alarm given an alarm id. DeleteAlarm • FindAlarms Finds alarms a user has set. FindAlarms Calendar This API lets a users manage events in their calendar. Calendar • CreateEvent Adds events to a user’s calendar. CreateEvent • DeleteEvent Deletes events from a user’s calendar. DeleteEvent • ModifyEvent Allows modification of an existing event. ModifyEvent • QueryCalendar Queries for events that occur in a time range. QueryCalendar Email This API lets a user search and send emails. Email • SearchInbox Searches for emails matching filters returning 5 most recent results. SearchInbox • SendEmail Sends an email on behalf of a given user. SendEmail Message This API lets a user search and send messages. Message • SearchMessages Searches messages matching filters returning 5 most recent results. SearchMessages • SendMessage Sends a message to another user. SendMessage Reminder A suite of APIs for managing reminders for a TODO list. Reminder • AddReminder Add a reminder with an optional due date. • CompleteReminder Complete a reminder. • DeleteReminder Delete a reminder. • GetReminders Get a list of reminders. AddReminder Weather Get weather information of a location. Weather • CurrentWeather Get the current weather of a location. CurrentWeather • ForecastWeather Get the 3-day weather forecast of a location. ForecastWeather • HistoricWeather Get historic weather information of a location by month. HistoricWeather B SCENARIO PROMPT Task You will be provided with a list of APIs. These APIs will have a description and a list of parameters and return types for each tool. Your task involves creating 3 varied, complex, and detailed user scenarios that require at least 5 API calls to complete involving at least 3 different APIs. One of these APIs will be explicitly provided and the other two will be chosen by you. For instance, given the APIs: SearchHotels, BookHotel, CancelBooking, GetNFLNews. Given that GetNFLNews is explicitly provided, your scenario should articulate something akin to: "The user wants to see if the Broncos won their last game (GetNFLNews). They then want to see if that qualifies them for the playoffs and who they will be playing against (GetNFLNews). The Broncos did make it into the playoffs, so the user wants watch the game in person. They want to look for hotels where the playoffs are occurring (GetNBANews + SearchHotels). After looking at the options, the user chooses to book a 3-day stay at the cheapest 4-star option (BookHotel)." This scenario exemplifies a scenario using 5 API calls. The scenario is complex, detailed, and concise as desired. The scenario also includes two APIs used in tandem, the required API, GetNBANews to search for the playoffs location and SearchHotels to find hotels based on the returned location. Usage of multiple APIs in tandem is highly desirable and will receive a higher score. Ideally each scenario should contain one or more instances of multiple APIs being used in tandem. Note that this scenario does not use all the APIs given and re-uses the " GetNBANews" API. Re-using APIs is allowed, but each scenario should involve at least 3 different APIs. Note that API usage is also included in the scenario, but exact parameters are not necessary. You must use a different combination of APIs for each scenario. All APIs must be used in at least one scenario. You can only use the APIs provided in the APIs section. Note that API calls are not explicitly mentioned and their uses are included in parentheses. This behaviour should be mimicked in your response. Deliver your response in this format: ‘‘‘ Scenario 1: <Scenario1> Scenario 2: <Scenario2> Scenario 3: <Scenario3> ‘‘‘ Scenario 1: <Scenario1> Scenario 2: <Scenario2> Scenario 3: <Scenario3> ‘‘‘ APIs ‘‘‘ {{API_DOCS}} ‘‘‘ Response Required API: {{REQUIRED_API}} Scenarios with >=5 API calls: ‘‘‘ - Scenario 1: C UNREALISTIC QUERIES Below are some examples of unrealistic queries gathered from various sources. These queries are useful for generating potentially complex tool interactions or unusual combinations of tools. However, as a consequence, they are unrealistic for various reasons such as forcing the usage of disparate APIs in situations a human is unlikely to ask for, explicitly asking for API endpoints which end users are unlikely to know of, or generally being unnaturally long and explicit. • “I’m working on a logistics project for my company and need to check the health of the SQUAKE API. Can you verify the API health by calling the ‘Checkhealth’ API endpoint? Additionally, I would like to retrieve the list of projects using the ‘Projects’ API endpoint.” (Qin et al., 2023b) • “How many singers have the average number of albums of singers in Beijing? Gives the square root of this number.” (Ruan et al., 2023) • “I am looking for x-large, red color women faux fur lined winter warm jacket coat, and price lower than 70.00 dollars.” Yao et al. (2022a) • “Can you retrieve the contact details of the ‘Gondrand’ customs agency in New Caledonia? I’m particularly interested in their postal code, email, name, and phone number. Also, please provide a list of all available transitaires. Begin!!!” Qin et al. (2023b) D NUANCES COMPARING PRIOR WORK Nuances comparing prior work from Table 5. ReAct and ART evaluate on hard QA tasks, but these tasks traditionally do not require the usage of tools to complete. We also note API-Bank fits all criteria. However, its level 1-2 examples are automated but simple. In comparison, its level 3 examples are complex but require manual evaluation. ToolBench’s tasks require hard to use tool, but have shallow solution paths. Their more complex environments have deeper solution paths, but re-use the existing datasets of WebShop (Yao et al., 2022a) and TableTop (Liang et al., 2023). This paper is available on arxiv under CC 4.0 license. This paper is available on arxiv under CC 4.0 license. available on arxiv

SEARCHNODE

searchnode.com

-- employees

Since n.d.

COMPANY RANKING

SEARCHNODE

EVERGREEN INDEX #21

Representing this company? Click here to claim and customize this page!

SearchNode WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

SEARCHNODE

searchnode.com

-- employees

Since n.d.

COMPANY RANKING

SEARCHNODE

EVERGREEN INDEX #21

RELATED COMPANIESRANK

STORIES ABOUT SEARCHNODE

Representing this company? Click here to claim and customize this page!

SearchNode WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!