Alright, I know the saying isn't exactly like this. I wanted to give the famous Shoot for the moon. Even if you miss, you'll land among the stars by the American author Norman Vincent Peale a little twist.

We have just wrapped up our fourth year of operations, running our specialised Ruby on Rails & Angular development agency, and we wanted to share the things we've learnt in the last year in this post.

In this part, I'll give a quick introduction to express.js in order to understand how the Processes engine is organised (and the rationale behind). This is a pure technical javascript post, so be warned! ⚠️

Disclaimer: the source code examples are, in most of the cases, a simplification of the real code for easier legibility and to avoid compromising our client's code.

One of the most frightening parts of being a developer is the recurring feeling that the
solution that you are building is not going to work as intended, it is going to scale poorly or some of your coworkers
will dislike working on top of it.

To give the best of yourself as a developer, you need to learn how to move away from these toxic feelings.

I want to share with you how I built a Node.js API for one of our biggest clients, where I will describe some patterns and javascript conventions I've used. I will make it easy to export these ideas elsewhere so they can be useful for your projects.

I will break down this guide into several parts. My goal with this series posts is to make it easy to understand the rationale behind my decisions regarding code structure and conventions.

Disclaimer: the source code examples are, in most of the cases, a simplification of the real code for easier legibility and to avoid compromising our client's code.