Year 2017 review and resolutions

Every time a new year passes by I feel a mix of two reactions: on one side, my first impression is always of a slight disappointment, as if I had not accomplished anything worth mentioning or hadn't made much more of a change compared to how I was when the year first started.

Then, I try to keep a cold mind and start enumerating the nice, interesting things I have done and learned, as well as all the new friendships made and the strengthening of existing ones, and slowly I tear down the thin depression web I made myself lay upon me.


I don't really count Belgium since this is my third year living here, and 2018 will start as my fourth year outside my beloved Spain.

I have been to quite some nice places though. Some of them I had already been there, some of them were new, bust mostly I prioritized people over places themselves. Almost every new city or country I went to was due to the interest of catching up with old friends or traveling together for a long weekend. Theres is however one long trip exception. I don't have the places noted down so I'll try to draw them directly from memory.

  • Germany: Berlin.
  • The Netherlands: Amsterdam, Den Haag, Maastricht, Rotterdam.
  • Spain: Barcelona, Madrid.
  • United Kingdom: London.
  • Norway: Bergen.
  • France: Paris, Reunion Island.
  • Bulgaria: Sunny Beach.

Most of the places I went to were due to friends living there, visiting over, or just an excuse to make a small trip. Reunion Island was the best trip I have ever done in my life. The island is a Département d'Outre Mer belonging to France, a small island in the Indic Ocean, next to Madagascar and Mauritius, is a paradise on earth, a territory full of incredible mountains, beautiful views, amazing food and unbelievably welcoming people.

A hodgepodge of cultures, religions and origins. A hidden oasis for those who seek for an inner voyage.


Best. Place. Ever.

Work & Technologies

The year started quite strong, I had moved in October to the Semantic Technology branch of my company at the last part of year 2016 and I had to learn quite fast all the new technologies and stacks that were used in my new team. I won't make an exhaustive list, just some things were I feel I have sensibly improved.

  • Javascript & Ember.js: I still kept strengthening my position as the javascript fan of the company, but as new challenges kept coming, I had to quickly adapt to new scenarios and projects si I had to put those skills a little aside.
  • Python: I developed & maintained several microservices in this language, so I needed to brush up on the it and its particularities. I enjoyed a lot working with async/await, list comprehensions, lambda functions and OOP back again. I am lucky I have a very patient mentor, my colleague @cecton, a pouring fountain of python know-how.
  • Docker: I had to learn, fight and dive into docker containers, images, volumes, docker networking and docker-compose applications, suffering several quirks, since the majority of the projects were developed in this manner.
  • Linux Makefiles: This was equally annoying and fun. I had to extend a data transformation pipeline using a Makefile, so I needed to deal for several weeks with it, it was very nice when I discovered that you can define functions inside Makefiles to avoid repeating code for very similar build targets!
  • SPARQL: Since I work in a Linked Data oriented team, we store data in triplestores accessed with the SPARQL query language, so I needed to learn the basics.
  • Elasticsearch & Kibana: I became familiar with Elasticsearch & Kibana due to a new project that came up and I was the available developer by then. It proved a lucky strike since I had a lot of fun learning them and they are widely used in the industry.

General Learning

  • I had a double improvement: I improved both my presentational skills and my English as the result of doing small presentations and exposing my work to colleagues.
  • I have written quite some blog posts and therefore my technical communication skills feel cleaner.
  • I practiced some Dutch for fun and before I realized I was able to maintain simple but complete conversations while doing my daily tasks.
  • I learned how to sew very very basicly.
  • I managed to cook some cool dishes when cooking for friends!


I have not done as much sport this year as I would've liked but I've had my fair share of fun.

  • Running: on the beach, in the woods, anywhere.
  • Trampoline park: they opened one in my hometown and had to test it.
  • Gymnastics: this was tough.
  • Climbing: a colleague and I have tested multiple boulder and climbing walls around.
  • Swimming.
  • Crossfit: a single day, very physically taxing, I would think twice before repeating.
  • Working out at the gym: as always, just to stay as fit as possible.

New Year 2018 Resolutions

  • Reading at least 3 technical books.
  • Starting to learn a new language: this is very tricky, since I genuinely enjoy languages and choosing a new one is hard. I want a very complicated one that forces my mind to twist, so I was thinking between chinese, arabic, russian or german.
  • Giving a talk at a conference/meetup: the worst part of this is going to be deciding about the topic..
  • Travel to another continent. Hell, I have never left Europe yet!
  • Learn a new programming language/paradigm. I am thinking in Rust or Clojure.
  • Create a stock market portfolio and perform my first investment.
  • Be able to perform three consecutive muscle-up.

That's it. I think I will be able to do all of them.

Have fun!

mdlink: Linking multiple node modules with a single command


As part of the process of working in node.js applications, developers usually use additional libraries and frameworks to ease and speed their development time, and more than often the number of libraries they rely upon is quite high.

It is also not uncommon to need to modify any of those libraries to fix a bug, or fork them to add additional functionality required for the project they are being used in.

The usual way to do this in a node.js project is:

  1. Clone the library's repository in your local machine
  2. cd your library's folder.
  3. sudo npm link to link the module globally.
  4. cd to your project's folder.
  5. npm link <library_name> to link to the library.

If you have multiple libraries that you need to be linking at the same time, or you have to link a library that depends on another library that you may need to link as well, it can be quite cumbersome to link them one by one.

In my free time I developed mdlink. It is a small utility that allows to easily npm link multiple node modules in a given project.

It was born as a reaction of my annoyance while I was developing Ember.js applications with multiple addons at the same time. Per each addon I'd need to clone it and link it. This tool intends to provide an easy way of bulk npm link and removing those links later while not necessary.

Modules are specified in the mdlink.config.json configuration file. e.g:

  "base_modules_path": "~/gits/test",
  "modules": {
    "mdlink": {
      "url": "",
      "path": "~/gits/test/mdlink"

Each module to be linked is stated in the modules object. It can have both url & path together, or only one of each.

The base_modules_path is used for the case where there is no path but a url is yet specified. The module will be cloned in base_modules_path/module_name instead.

Let's see an example with a new Ember application. First, download mdlink with npm and create the application:

test-ember:master* λ sudo npm install -g mdlink
test-ember:master* λ ember new test-ember

Then, create a new mdlink.config.json file inside the test-ember app.

test-ember:master* λ mdlink init

And let's say that in our new application we want to locally modify both ember-moment and ember-promise-helpers. We modify the mdlink.config.json file like this:

  "base_modules_path": "/home/esteban/gits/test",
  "modules": {
    "ember-moment": {
      "url": "",
      "path": "/home/esteban/gits/test/ember-moment"
    "ember-promise-helpers": {
      "url": "",
      "path": "/home/esteban/gits/test/ember-promise-helpers"

Do the linking:

test-ember:master* λ mdlink s
[+] Path /home/esteban/gits/test-ember/node_modules/ember-moment already exists, removing it.
[+] <path exists> . Successfully cloned in path: /home/esteban/gits/test/ember-moment
[+] Create link from /usr/lib/node_modules/ember-moment -> /home/esteban/gits/test/ember-moment
[+] <path exists> . Successfully cloned in path: /home/esteban/gits/test/ember-promise-helpers
[+] Create link from /usr/lib/node_modules/ember-promise-helpers -> /home/esteban/gits/test/ember-promise-helpers

Verify both modules where properly cloned:

test λ ls -la ~/gits/test/
drwxrwxr-x  4 esteban esteban 4,0K Dez 19 22:07 ./
drwxrwxr-x  8 esteban esteban 4,0K Dez 19 22:05 ../
drwxrwxr-x 10 esteban esteban 4,0K Dez 19 22:36 ember-moment/
drwxrwxr-x  9 esteban esteban 4,0K Dez 19 22:07 ember-promise-helpers/

Modify index.js in both modules, and ember s from the test-ember app folder:

test-ember:master* λ ember s
Linked ember-moment
Linked ember-promise-helpers
Could not start watchman
Visit for more info.
Livereload server on http://localhost:7020

Build successful (14117ms) – Serving on http://localhost:4200/

Have fun!

Ember.js cookies over SSL


I am currently working on an issue in a very old Ember.js application (version 1.13.0 of the ember-cli). After performing the regular ritual: npm install; bower install; ember s --proxy <proxy> I was presented with the application's login screen, but what was my surprise that after introducing a valid set of credentials, the next http call invariably failed.

Client -> POST /sessions -> Server API (works)
Client -> GET /settings -> Server API (fails)

Now, the code wasn't changed in the frontend so there was a slight chance the backend would be the culprit. Checking the differences between a working production environment two things stood out:

  • In the working environment both frontend & backend are in the same server. While developing with ember s I have a server running locally and I make calls to the external API, so this might be a problem of related with making cross-origin requests.
  • After being successfully authenticated, the server sends a session cookie using the Set-Cookie header, and in subsequent calls the browser will send that cookie in the request headers. Usual behavior. But in the failing environment, after a successful login, the browser received the cookie but never sent it back again.

I quickly discarded the first case, since when you use ember s --proxy you are really making a call to the same origin and then the proxy will route it to the external API. On the other side... why was my cookie not being set?! It was not until a coworker pointed out the Secure flag in the session cookie. What was that?

It turns out, as seen here, the Secure flag is set to prevent third parties to observe sensitive cookies being sent in clear text, hence, those cookies won't be resent unless they are received & sent over HTTPS, and the development server was running over regular HTTP.


The solution was indeed quite simple! The ember-cli provides an easy way to serve traffic over SSL using a personal certificate. For developing purposes, I just created a self-signed certificate following the instructions in the heroku dev center. After that you would have a server.key and server.crt key & certificate.

Then you can run the ember-cli specifying the ssl options in .ember-cli:

  "disableAnalytics": false,
  "ssl": true,
  "ssl-key": "path/to/server.key",
  "ssl-cert": "path/to/server.crt"

By default ember will look into the ssl/ folder for the server.key and the server.crt files, so creating those files inside the folder and running

$ ember s --ssl=true --proxy <proxy>

Will make the thing run.

Have fun!

Array of extended objects in python using list comprehensions and lambda functions.


It's been a while since I don't write any posts, so I thought that even though the idea might be initially quite silly, it will help me to kickoff again the habit by writing about a small problem I encountered the other day.

I was developing a very simple microservice that would receive a GET request with two parameters, issue a SPARQL query to a Virtuoso store and then, transform the returned array of objects by extending each object with the same additional meta information per object. Say:

res = [{ 'title': 'Oh boy' }, { 'title': 'Oh girl'}]

And then add some additional metadata like { 'meta': { 'author': 'Myself'}}

Ending up with

res = [ {
        'title': 'Oh boy',
        'meta':  {
          'author': 'Myself'
          'title': 'Oh girl',
          'meta': {
            'author': 'Myself'


I wanted to do something self contained and as functional as possible, by using list comprehensions for example. Unfortunately, there is no method in python to update a dictionary and return the new dictionary updated. The regular way is like:

a = { 'b': 3 }
a.update({'c': 5}) # Dict updated, does not return anything
print(a) # {'c': 5, 'b': 3}

Ultimately I came up with a small solution:

result = [(lambda x, y=z.copy(): (y.update(x), y))({ 'meta': { 'author': 'Myself' } })[1] for z in res]

Tada! Combining list comprehensions, lambda functions and the built-in dictionary copy() function we can return a new array with a copy of each object already extended.

By using a lambda function that accepts a tuple we can specify that the first argument is passed as a parameter and the second one will be a copy of each element in the array (assuming it is an object). Then, the object is extended with the argument and the newly extended object is returned as the second element of the tuple.

We could even bake this into a function:

def map_extend(array=[], ext={}):
  return [(lambda x, y=z.copy(): (y.update(x), y))(ext)[1] for z in array]
>>> res
[{'title': 'Oh boy'}, {'title': 'Oh girl'}]
>>> ext = { 'meta': {'author': 'Hola'}}                                                     
>>> map_extend(res, ext)
[{'meta': {'author': 'Hola'}, 'title': 'Oh boy'}, {'meta': {'author': 'Hola'}, 'title': 'Oh girl'}]
>>> map_extend(res, {})                                                                     
[{'title': 'Oh boy'}, {'title': 'Oh girl'}]
>>> map_extend([], {})                                                                      

Have fun!

Clojure threading macros in ES6

While working in the functionality for getting a docker-compose path from the cursor position, I realized at some point I was writing constantly code like this:

let first_result = func_call1(val);
let second_result = func_call2(first_result);
let third_result = func_call3(second_result);


This is not necessarily bad, it improves code readability and helps to reason about the flow of execution, normally better than calling those functions in a nested way:

func_call3(func_call2(func_call1(val))); // Phew.

But yet, it feels somewhat cumbersome to nest too many function calls that way. Some time ago I started looking into Clojure for fun and discovered threading macros. Thread first ('->') and Thread last(->>) macros pipe the result of the application of a function to a value to the next function in the list. The difference is that thread first adds the result as the first argument to the next function and thread last to the last one.

Wouldn't it be nice to have some kind of mechanism in Javascript?. Looking around I found someone had already written a nice article about it. The target is to have a function to be called like this:

let result = thread("->", "3", 
                        [sum, 3],
                        [diff, 10],
                        str); // "-4"

And what would be going on under the hood is this:

let sameresult = diff(sum(3, parseInt("3")), 10);

So I decided to reimplement the code taking advantage of the new features that came along with ES6(arrow functions, destructuring, rest parameters...).

const thread = (operator, first, ...args) => {
    let isThreadFirst;
    switch (operator) {
        case '->>':
            isThreadFirst = false;
        case '->':
            isThreadFirst = true;
            throw new Error('Operator not supported');
    return args.reduce((prev, next) => {
        if (Array.isArray(next)) {
            const [head, ...tail] = next;
            return isThreadFirst ? head.apply(this, [prev, ...tail]) : head.apply(this, tail.concat(prev));
        else {
            return, prev);
    }, first);

So when executing the code using the thread first operator for example:

let result = thread("->", "3", 
                        [sum, 3],
                        [diff, 10],
                        str); // "-4"

console.log(result); // -4 

and using the thread last operator:

let result = thread("->>", "3", 
                        [sum, 3],
                        [diff, 10],
                        str); // "-4"

console.log(result); // 4 

Have fun!