I did some interviews in the last few days, the role we were searching was “super-duper senior javascript master” so I asked this very simple question as starter:

Suppose you see that a website, or a URL, that seems to be unaccessible.

The purpose of this post is to give you, dear reader, an example of the configuration I use on some projects. Configuring the whole stack is sometimes frustrating. Here’s what works for me.

Hey there, after digging about how Typescript settings mesh together, I decided to write my article about what I found the hard way, hoping to clear the path for newcomers.

Do you love meetings? Do you enjoy taking a break from your work and talk - ehm, listen to your managers, stakeholders, customers, peers? I suppose you not. If you’re like me, 99% of your work life meetings have been a total waste of time.

SSH is one of the basic commands you need to master, no matter what’s your platform of choice. Because you’ll always end up working on some random server, and you’ll have to login to see logs or restarting services. Also, you’ll never see it as a skill to show because it’s implicit that you have to know how to use it, at least for logging in to some website.

Browserify belongs to the very first generation of module bundlers and it basically allowed one thing, that is, use the require function from NodeJS in the browser. Browserify’s only job was to concatenate files wrapping them in functions that were then called by other fils.

Prior to work in an ads company I had no idea of how ads are actually rendered on a page. I mean, I had a vague sense of what was going on, but the actual world behind it … well, it’s huge :)

At my new job I maintain a medium-sized typescript library that is critical to the success of the company.

Two years ago I wrote about quitting a job in a big italian corporation to join a smaller reality that worked in fintech.