Hello, this is my 33th open source contribution for Utopian and DaVinci as translator. I have been translating different Node.js Files during the past few months. This time, I continued translating "process.md" file, because it is a very interesting part of all Node.js because it is a control tool that improve the perforance of each process.

I work with an extensive team of translators team whose performance has been excellent. By this time a 37% of this huge project has been translated in a few months. I must say that I'm very excited about that.

I invite you to read this post because it is a knowledge font that provides tools for the people who are working with Node.js or any other open source project development. I hope this contribution is useful.

It looks difficult to understand at first, but let me explain it with the next example.

Imagine that you have been developing a new android app that uses the APIs from Google Maps and Twitter. When testing the app, you realize that both APIs are written in different languages and you must change one of them to make it work, but that's a lot of work and goes against the reasons to use an API. Node.js is the solution to problems like this because it allows the union between different programming languages without affecting its performance.

I decided to translate this project because I'm an engineering student and innovation is my passion; I love creating solutions to problems like this. Also, I like sharing information and a way to do it is translating the content of a big project like this so people around the world can access to it and share it too.

In Node.js a process is an object that is "a global that provides information about, and control over, the current Node.js process. As a global, it is always available to Node.js applications without using require()." This object is very important because allows control over the process that is running; this improves the Node.js performance.

Reading this document I found out a new interesting event and it is called 'warning'. A warning is "emitted whenever Node.js emits a process warning.". I know it looks simple, but it is a way to warn the user about potential issues or even possible errors during the process, without executing it. More specifically, it is "similar to an error in that it describes exceptional conditions that are being brought to the user's attention.". The most important thing to understand is that a warning informs the user about future non-optimal performance or any other issue that will damage all the process.

An interesting setting that can be configured in warnings is the possibility to customize them, depending the objective of the process developed. Very useful for those who are creating programs with their own warnings.

The original language of this change log is English and it was translated into Spanish, which is my native language. I have experience translating in projects like Loopring wallet and Yapbam. These projects make me grow and learn a lot about open source projects.

You can visit my profile (navx) on Crowdin's website to find proof of authorship. Also, you can visit the Activity tab in the Node.js project and filter my contributions between December 7th and 8th, and December 9th, which were the dates of the translation and the corrections respectively.