Captain's log, stardate d370.y38/AB

If you want to join the Martian crew working with Node.js, this is your chance to do it! Join our growing team!

Captain's log, stardate d193.y38/AB

2019 is bringing many changes to our company. As a technology company, we always review our techstack every year to keep up with the market.

We would like to announce that we're officially adopting Node.js as a de facto development environment for our backend projects, in addition to Rails.

Captain's log, stardate d614.y37/AB

Hi everyone (again)!

In my previous blog entry, I wrote the first part of our guide to create APIs using Node.js.

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.

Are you ready to learn how express.js works? Let's dive into it!

Captain's log, stardate d593.y37/AB

Hi everyone!

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.