
Do you want to automate tasks without writing a single line of code? If the answer is yes, then you’ve come to the right place. In this simple tutorial, I’m going to show you how you can create your first automated workflow using a tool called n8n.
Build automation systems
Do you want to automate tasks without writing a single line of code? If the answer is yes, then you’ve come to the right place. In this simple tutorial, I’m going to show you how you can create your first automated workflow using a tool called n8n.
From the earliest days, we used MSVC to compile the PVS-Studio C++ analyzer for Windows - then, in 2006, known as Viva64, version 1.00. With new releases, the analyzer's C++ core learned to work on Linux and macOS, and we modified the project's structure to support CMake. However, we kept using the MSVC compiler to build the analyzer's version for Windows. Then, in 2019, on April 29th, Visual Studio developers announced they had included the LLVM utilities and Clang compiler in the IDE. And just recently we've gotten around to try it.
In some projects, the build script is playing the role of Cinderella. The team focuses its main effort on code development. And the build process itself could be handled by people who are far from development (for example, those responsible for operation or deployment). If the build script works somehow, then everyone prefers not to touch it, and noone ever is thinking about optimization. However, in large heterogeneous projects, the build process could be quite complex, and it is possible to approach it as an independent project. If however you treat the build script as a secondary unimportant project, then the result will be an indigestible imperative script, the support of which will be rather difficult.
In the previous post we looked at what criteria we used to choose the toolkit, and why we chose gradle/kotlin, and in this post we will take a look at how we use gradle/kotlin to automate the build of non-JVM projects. (There is also a Russian version.)
Gradle for JVM projects is a universally recognized tool and does not need additional recommendations. For projects outside of the JVM platform, it is also used. For instance, the official documentation describes usage scenarios for C++ and Swift projects. We use gradle to automate the build, test, and deployment of a heterogeneous project that includes modules in node.js, golang, terraform.
In some projects, the build script is playing the role of Cinderella. The team focuses its main effort on code development. And the build process itself could be handled by people who are far from development (for example, those responsible for operation or deployment). If the build script works somehow, then everyone prefers not to touch it, and no one ever is thinking about optimization. However, in large heterogeneous projects, the build process could be quite complex, and it is possible to approach it as an independent project.If you treat the build script as a secondary unimportant project, then the result will be an indigestible imperative script, the support of which will be rather difficult.
In this note we will take look at the criteria by which we chose the toolkit, and in the next one — how we use this toolkit. (There is also a Russian version.)
Custom development is different from commercially distributed software or existing open source software. Individual development either creates a new application or expands the functionality of an existing one and can be executed by its own or third-party developers.
How do you know that it’s time for you to launch your online marketplace? When do you see the necessity to provide the ultimate clear and fast “brand – consumer” communications? The point of an online marketplace is to grow customers loyalty by offering them an ever-expanding range of products.
A brand, whether online or not, must use its reputation and expertise to make its marketplace successful.
Let's take a look at the benefits of marketplaces and the reliability of Ruby on Rails as the strongest development tool.
The manual work of the accountant went into oblivion. Today everyone makes machines, but, of course, controlled by a specialist. Although in our last project we have carefully worked on the topic of artificial intelligence and some accounting operations can already occur with little or no human intervention. Let's look at what systems we attracted, and what exactly was done to save time on daily routine operations.
E-commerce today has become so frequent that it has become almost a standard chain of stores, where most people make purchases. But even online stores are trying to save money by becoming drop shippers and more working on additional implementations, rather than on the maintenance and payment of huge storage spaces.
make
is very stable and widely-used I personally like cross-platform solutions. It is 2019 after all, not 1977. One can argue that make itself is cross-platform, but in reality you will have troubles and will spend time on fixing your tool rather than on doing the actual work. So I decided to have a look around and to check out what other tools are available. Yes, I decided to spend some time on tools.