Master on Libre Software Planet

December 02, 2017

Andrés Maneiro

Afuega’l Pitu

Saturday occupation: eating spicy cheese made of cow milk and paprika.

by Andrés at December 02, 2017 02:34 PM

December 01, 2017

Andrés Maneiro

Shelter from the Storm

Mars soundtrack (the National Geographic tv-show) is fantastic. Nick Cave is just the perfect voice to convey that feeling of exploration and fear. Moon, Interstellar, The Martian, etc; it seems sci-fi movies got an appreciation for soundtracks that have a major role in the film – and I enjoy that.

As much as I like Cave’s main theme for Mars, after a few episodes, I was in the need of something like Dylan’s Shelter from the Storm. Exploration needs joy and celebration.

by Andrés at December 01, 2017 02:51 PM

November 25, 2017

Andrés Maneiro

Agile according to Basecamp

Running in Circles is Basecamp’s view of agile product management. They acknowledge the value of working in cycles, but add three pieces: having the time to focus, being able to modify the original plan, and tackle the core unknowns of the feature first.

The first two are enablers that are provided to the makers by management. The last part is how the maker make the most of those powers. Together, they form a process that is nicely captured with the uphill / downhill metaphor. Uphill you are discovering the unknowns and making decisions about what goes in, downhill everything is clear and you are implementing it at warp factor 10:

by Andrés at November 25, 2017 01:07 PM

November 23, 2017

Andrés Maneiro

Ten years of mobile

10 years of mobile by Luke Wroblewski packs a lot of knowledge in one hour and a half. If I could only watch one talk about mobile, I'd make it this.

by Andrés at November 23, 2017 08:12 PM

November 22, 2017

Andrés Maneiro

Module counts

I came across Module Counts, which tracks the number of published modules for major language package managers. At this point, npm has 600k packages published, which is 3 to 4 times what any other package manager has. I’m not aware of download statistic across different package managers, but npm has surpassed the 2 billions downloads a week mark.

by Andrés at November 22, 2017 02:41 PM

November 18, 2017

Andrés Maneiro

Are you serious

This puts me in the perfect mood before going for a walk in this sunny and cold Saturday.

by Andrés at November 18, 2017 03:25 PM

November 12, 2017

Andrés Maneiro

Software architecture failing

Software architecture failing: tech writing is biased towards what the big ones do, which usually doesn’t fit most other contexts – but, who got fired for choosing IBM, right? Although I feel connected to this rant at an emotional level, I do think it’s necessary to elaborate more and make a positive contribution: help to create and spread that alternate history of software development. How do you do it? Hat tip: Fran.

by Andrés at November 12, 2017 10:30 PM

The language of programming

The language of programming is about the struggles non-native English speakers face when learning to program. Hat tip: Manuel.

by Andrés at November 12, 2017 10:15 PM

November 01, 2017

Andrés Maneiro

Touch typing in Dvorak

On November 2016 I had a free month between jobs. Apart from some resting, reading, and general preparations for my new adventure, I still had quite a bit of free time to do new things or build good habits. It was while cleaning my office that I found a keyboard I had bought a couple of years back:

Its layout was a beautiful matrix -which is good for your fingers- and came with Dvorak by default. So it struck me: how about improving my typing during the coming weeks?

As a programmer, typing is an essential skill for me. I had been doing it for more than 15 years in a learn-by-doing way, and I plan to keep typing for years to come. I thought it would be fun to spend a couple of hours a day training in touch-typing and give Dvorak a second try. And so I did.

The experience

Before I switched, I recorded about 15 typing sessions at TypeRacer using the QWERTY layout, which logs typing speed (words per minute) and accuracy (% characters right over the total). I was at 67 wpm and about 95% accuracy at the time.

Progress was very humbling at the beginning; it felt like learning to walk again, and I swear that, sometimes, I could even hear my brain circuits being reconfigured! After a few weeks, though, I was under 40 wpm and, by the end of the month, I was under 50 wpm. I stopped quantifying myself by then: as I started working, I had a lot of typing to do anyway.

During the first months, the only moments I struggled and felt like perhaps the switch wasn’t a good idea after all was during real-time communication: chats, slack, etc. I don’t know what people thought of me, but my velocity at the time was typing-bounded – I was certainly a very slow touch-typist by my own standards.

But time passed and I improved.

Spáñish Dvorak and symbols

Throughout the process I changed my setup quite a bit: I started my journey using the Programmer Dvorak layout with a TypeMatrix keyboard. After a few months, I switched back to my good old ThinkPad keyboard because having to use a mouse again after years not using it was a pain. A few months later, I switched to the Dvorak international, because the Programmers Dvorak layout didn’t quite suit me. Then, I tweaked the common symbols I use for programming so they were better positioned. Besides, although the bulk of my typing is in English, I still need to write decent Spáñish, which basically means using tildes on vowels and ñ. TLDR: the Spanish Dvorak version made things more difficult, so I’ve just tweaked the Dvorak international to accommodate tildes and ñ as I see fit.

At this point, I believe I can patent my own layout:

All the changes I did to the symbol positions have affected my ability to build muscle memory for them – sometimes I still need to look at some specific symbol on the keyboard. However, the current version has been unchanged for months, so I only need a bit more time for them to stick.

The numbers

Given that I was a QWERTY user for 15 years, I thought I would give the new layout a year before comparing any statistics. The fair thing to do would be comparing after 15 years, but I’m a bit impatient for that. I went to TypeRacer again and noted down the results for about 20 races. These are the numbers of this totally unscientific experiment:

A few remarks:

  • In terms of speed, it seems that I’m mostly there. My median speed now is 65 wpm, 2 words per minute less than before. I had a higher peak (83 vs 79) in one of the current typing sessions, but I was under 60wpm in more sessions this time.
  • In terms of accuracy, I’ve improved a bit. My median accuracy has increased by 1,5 points, and I had only 2 sessions below 95% of accuracy this time.


Overall, I’m very happy with the switch to Dvorak. My accuracy has improved, meaning that I can maintain a longer typing rhythm. Not having to correct mistakes makes me a faster typist as well, and by learning to touch-type I also have grown more endurance.

This experiment was very humbling but fun. I believe it increased my brain plasticity by an order of magnitude, and I’m hoping to improve my numbers as years pass as well. However that turns out, though, I think of this as a gift to the elder me, a way to prevent typing pain in the future and promote a healthy use of the tools I heavily depend upon.

by Andrés at November 01, 2017 03:45 PM

October 25, 2017

Andrés Maneiro

I spent the weekend reorganizing things, including my blog. I’ve got a new WordPress theme (independent publisher) which looks a lot more lightweight. I’ve consolidated the essays section with stuff that grew out of individual posts (I keep thinking that someday I’ll have the time to publish them as independent e-books), polished the about, fixed some links in the glossary, and started to reorganize the archives.

I’m also going to try a different approach in the following months: instead of having separate blogs for music, lifestream, thoughts, etc I’m going to publish everything here – I do not publish that much anyway, and I like the idea of this having a more personal touch.

by Andrés at October 25, 2017 07:16 PM

October 22, 2017

Andrés Maneiro

Learning to learn

When we want to acquire a new skill, we are faced with two choices: trial-error, or instruction. One is experience-driven or practice-based, the other is concept-driven or theory-based.

The trade-offs

Trial-error is the built-in mechanism humans come with to acquire knowledge and skills – our thinking processes are optimized for that. However, it may be expensive and impractical in some situations. For instance, learning to pilot an aircraft by trial-error is risky should you want to keep the chances of learning in the future high. We have developed systems that lower the cost of trial-error, though, such as pilot simulators. It can also be time-consuming: we just don’t have the time to trial-error every piece of knowledge our society is based upon!

Learning by instruction appears to be more efficient: we are presented with models and recipes that work, saving us a lot of time that we can use to advance our knowledge further. Nevertheless, the instruction is not always possible; sometimes the map of knowledge of a certain domain isn’t built yet, so we need to rely on the trial-error approach. Even most important is the fact that internalizing abstract knowledge not based on direct experience seems to be more difficult for humans.

This poses a question: how shall we learn?

The Dreyfuss model

In February 1980, Dreyfuss brothers published a seminal paper on how to teach: «A five-stage model of the mental activities involved in directed skill acquisition». This work was supported by the US Air Force, which was interested in improving their training programs.

What they said is 1) we should recognize the role of the first-hand experience in acquiring knowledge and 2) to become an expert it is necessary to learn the rules, guidelines, and maxims of the particular skill we are interested in.

The rules are the principles that always apply, they don’t depend on anything so they are context-free or non-situational. Examples of rules are the valid movements of a piece in the go game, the set of instructions in programming, the techniques in the Aikido martial art.

The guidelines are the principles that only apply in specifics contexts, so they are context-bound or situational. Things like josekis in the go game (sequences of moves in a specific part of the board), the design patterns in programming, or the katas in Aikido.

The maxims are principles that guide us towards achieving our long-term goal, they help us by assigning a value to guidelines: is this joseki worth it if I’m playing for territory in go? Is the ability to grow new features necessary for this specific part of the application? What specific throw should I use if I want to face the next adversary?

For one to become an expert, rules, guidelines, and maxims should be second nature.

Dreyfuss defines a 5-step process someone goes through to gain knowledge: novice, competence, proficiency, expertise, mastery. Others outline different systems that include three stages. What’s important is to realize that the learning process is at its best when we take a practical approach and theory is presented to the learner as they are prepared to assimilate the next artifact – rules, guidelines, maxims.


Learning to learn is probably one of the more important skills when we no longer know what’s coming next. The real world TM tends to be more chaotic and intertwined than the sequential process outlined by Dreyfuss. Realizing where are you at a particular skill will help you in making decisions about what focus on. For instance, am I a novice at skill X? Well, at this point, I’m better off focusing on learning the rules and imitate what others have done. And so on.

Learning also takes a lot of time – someone has even published a number, about 10.000 hours to become an expert in anything. It’s a lot! It may be discouraging. Luckily, a practice-based approach makes things more rewarding, and time flies when we are enjoying the process.

by Andrés at October 22, 2017 11:13 AM

October 16, 2017

Andrés Maneiro

The thing that get us to the thing

Past Saturday, AMC aired Halt and Catch Fire season finale. I saw this tv-show grow over 4 seasons and I’m sad it’s over.

HACF resonated with me because it was about the pleasure of making things work and the cost of pursuing your dreams. We need a whole lot more stories about the woes and joys of creation to learn how to navigate that world and to inspire us. We need more builders and dreamers capable of not burning themselves out.

Bonus points for using the evolution of computers as the McGuffin. But, as much as I liked the history of computers being the central plot of a well done period  drama, HACF wasn’t about computers. The computers aren’t the thing. They are the thing that get us to the thing.

by Andrés at October 16, 2017 10:13 PM

October 06, 2017

Andrés Maneiro

The pleasure of finding things out

This was the first book listening experience that I’ve actually finished. Sean Runnette‘s voice was adequate for setting the tone and rhythm – actually, sometimes I felt I was listening to Feinmann himself!

Having read Surely You’re Joking, Mr. Feynman!What Do You Care What Other People Think? and some other papers/videos, most of the stories in the book I already knew, but it had some new material that made it interesting nonetheless. This is more mathematical/physical intense than the others, probably because it’s mostly focused on the scientific and less in the human Feynman – but also because many chapters are directly transcribed from conferences he gave. It’s also worth noting that, unlike the other two, this book was published without Feynmann intervention: it’s published 10 years after his death.

If I had to choose only a Feynman book I’d choose Surely You’re Joking, Mr. Feynmann! It’s better edited and has more variety. Then, if you are hungry for more, What do you care what other people think? contains new stories. I liked this one, but I doubt it’s a good introduction to Feynmann lifestyle, work, values, and character.

by Andrés at October 06, 2017 01:25 PM

September 28, 2017

Andrés Maneiro

Code simplicity


I’ve just finished the book Code Simplicity. It presents a framework for thinking about software development in the form of laws and rules. It’s short but comprehensive. From my experience, the laws and rules hold true. I think the book has value as an overall perspective of what’s important in software development, and there are some chapters that are really spot on: for example, the equation of software design – something that I’ve already included in my glossary and plan to expand.

Code Simplicity doesn’t intend to land the laws and rules to something actionable, though. I’m at a point in my career where I’m focused on consolidating and reflecting upon how to achieve simplicity in software design – that means that I crave for specifics so I can compare them with mine.

As a cross-recommendation, if you are interested in learning about the laws of software development in a manner that is actionable, I’d suggest reading the Beck’s trilogy: Extreme Programming Explained: Embrace Change, Test Driven Development: by example, and Implementation Patterns. Those three books make a great combination of macro-forces (at a project level) and micro-forces (at a coding level) in software design. They were fundamental in consolidating my experiences as a programmer, so I’m highly biased towards them.

Hat tip for the Code Simplicity recommendation: Nikolay.

by Andrés at September 28, 2017 09:56 PM

September 08, 2017

Andrés Maneiro

September 01, 2017

Andrés Maneiro

Turns out algorithms are racists

«Technology is neither good nor bad; nor is it neutral.»

Melvin Kranzberg’s six laws of technology

One of the things I was very into a decade ago was studying the intertwine between technology, culture, and society. From those years, I developed a sensitivity about my role as an engineer, or as an enabler of possible worlds.

This is one of the things I wanted to avoid:

A person isn’t able to clean his hands because the machine sensors are only prepared to detect white hands! That’s a horror story that could make a BlackMirror episode.

This made me think about the mainstream perception of Machine Learning and Artificial Intelligence technology. Lately, some friends of mine are sharing with me clickbait news like Facebook shuts down robots after they invent their own language. They ask me if robots could take over, soon. Well, I can tell you something: at this stage of technology, I am not worried about robots taking over. What I do worry about is how our inability to understand technology creates racists algorithms that reinforce our biases.

by Andrés at September 01, 2017 08:31 AM

August 28, 2017

Andrés Maneiro

August 27, 2017

Andrés Maneiro

(…) the number-one indicator of a successful team wasn’t tenure, seniority or salary levels, but psychological safety. Think of a team you work with closely. How strongly do you agree with these five statements?

  1. If I take a chance, and screw up, it will be held against me
  2. Our team has a strong sense of culture that can be hard for new people to join.
  3. My team is slow to offer help to people who are struggling.
  4. Using my unique skills and talents come second to the objectives of the team.
  5. It’s uncomfortable to have open honest conversations about our team’s sensitive issues.

Teams that score high on questions like these can be deemed to be “unsafe”. Unsafe to innovate, unsafe to resolve conflict, unsafe to admit they need help.

— Engineering a culture of psychological safety.

by Andrés at August 27, 2017 09:10 PM

August 08, 2017

Andrés Maneiro

Highly recommended article: Born for it, on how the image of software developers came about.

by Andrés at August 08, 2017 09:12 PM

July 31, 2017

Andrés Maneiro

Code and decision trees

A lot of what programs do is transforming inputs into outputs. Take, for example, a piece of JavaScript code like this:

itemsToMarkup( items, viewType, galleryType ) {

    let markup;

    switch ( viewType ) {
        case 'gallery':
            if ( 'individual' === galleryType ) ) {
                markup = getHTML( items );
            } else {
                markup = getShortcode( items );

        case 'image':
            markup = getHTML( items );

    return markup;

What’s the purpose of this code? It takes some input data structures and outputs a markup, either proper HTML or a code to be processed by later stages of the pipeline. At the core, what we are doing is taking a decision based on the input’s state so it can be modeled as a decision tree:

By restating the problem in a more simple language, the structure is made more evident. We are free of the biases that code as a language for thinking introduces (code size, good-looking indenting, a certain preference to use switch or if statements, etc). In this case, conflating the two checks into one reduces the tree depth and the number of leaves:

Which back to code could be something like:

itemsToMarkup( items, viewType, galleryType ) {

    let markup;
    const isGalleryButNotIndividual = ( view, gallery ) => view === 'gallery' && gallery !== 'individual';

    if( isGalleryButNotIndividual( viewType, galleryType ) ) {
        markup = getShortcode( items );
    } else {
        markup = getHTML( items );

    return markup;


By having a simpler decision tree, the second piece of code makes the input/output mapping more explicit and concise.

by Andrés at July 31, 2017 05:23 PM

June 26, 2017

Andrés Maneiro

A new middle class?

In this paper, we make the case that the high-productivity digital firms are starting to generate a new middle class. It’s a virtuous circle. Consumers flock to those firms because they offer lower prices and better service. Workers migrate there from low-productivity firms because the high-productivity firms offer better wages for the same occupations—and, often, steadier hours and better benefits.

— The Creation of a New Middle Class?: A Historical and Analytic Perspective on Job and Wage Growth in the Digital Sector. [PDF]

by Andrés at June 26, 2017 01:41 PM

June 22, 2017

Andrés Maneiro

The Google repository

I’ve been reading how Google organizes its codebase: they maintain a hyper-large repository containing everything, since the beginning of the company. I guess you may find Gmail, Photos, or AdWords there. You won’t find Android or Chrome, though – these are open source projects.

The repository is 86Tb of data, 1 billion of files, and 35 billion of commits. To manage this complexity, they needed to build their own tools: a home-grown Version Control System that can work effectively with such a repository at this scale, editor integration, building and automated testing tools, etc.

They develop all the code against trunk/master, meaning that if you are updating a library, you’ll also need to fix all applications that depend on it. Every project will be up-to-date, even abandoned projects.

The advantages

The main reasons they claim this approach works for them are: it makes easier reusing blocks of knowledge company-wide and reduces the friction to contribute between projects/teams. UI primitives, building tools, etc, all are shared by any project that wants them, it’s just a matter of depending on the master version. It minimizes the costs of versioning/integration and the curse of being left behind when something is updated and you cannot keep up with the changes (the experts will do it for you!).

As a side effect, when working on libraries/frameworks it’s easier to understand the performance/impact/etc of a specific change (you can run tests on real projects) and to put together a task-force to fix issues affecting several applications.

The disadvantages

This approach comes with downsides as well: they mention the amount of maintenance this setup requires even with all the tooling they have already built. With a monolithic repo, it’s easy to run into unnecessary dependencies that bloat the binary size of a project (and they do), the costs inherent to updating basic blocks used through the whole company, etc.

Another point is that it makes difficult having external contributors. Although they have a space in the repository for public/open-sourced projects, the article is unclear on how they manage 3rd-party contributions there – external programmers don’t have access to the internal building tools that Google programmers have. High-profile products like Android or Chrome -where outside contributors are expected and encouraged- have walked away from this approach.


I highly recommend reading the paper, it’s a pretty unique approach, and the article does a good job on presenting a balanced perspective.

by Andrés at June 22, 2017 05:45 PM

May 01, 2017

Andrés Maneiro

How comparing things is faster and simpler with immutability

In the previous post of the series, I wrote about the nature of value and reference data types, and the differences between shallow and deep operations. In particular, the fact that we need to rely on deep operations to compare things is a major source of complexity in our codebases. But we can do better.

Comparing mutable structures

When working with mutable data structures, things like determining whether an object has been changed or not is not so simple:

var film = {
    'title': 'Piratees of the Caribean', 
    'released': 2003

// At some point, we receive an object and one of its properties
// might have changed. But how do we know?
newFilm = doSomething( film );

film === newFilm; // What does a shallow equality yield?

If we are allowed to mutate objects, although film and newFilm identifiers are equal, the payload might have been updated: a shallow equality check won’t suffice, we’ll need to perform a deep equality operation with the original object to know.

Comparing immutable structures

In JavaScript, primitives (numbers, strings, …) are immutable, and reference data types (object, arrays, …) are not. But if mutable structures are the reason why comparing things is difficult, what would happen if we worked with reference data types as if they were immutable?

Let’s see how this would work:

If something changes, instead of mutating the original object, we’ll create a new one with the adequate properties. As the new and the old object will have different identifiers, a shallow equality check will set them apart.

var film = {
    'title': 'Piratees of the Caribean', 
    'released': 2003

var doSomeThing = function( film ) { 
    // ... 
    return Object.assign( 
        {'title': 'The curse of the Black Pearl'} 

var newFilm = doSomething( film ); 

film === newFilm; // false

If nothing changes, we’ll return the same object. Because the identifier is the same, the shallow equality check will yield true.

var film = {
    'title': 'Piratees of the Caribean', 
    'released': 2003

var doSomeThing = function( film ) { 
    // ... 
    return film; 

var newFilm = doSomething( film ); 

film === newFilm; // true

It is easier to tell what have changed when reference data types are immutable because we can leverage the shallow equality operations.

As a side-effect, it takes less effort to build a whole lot of systems that depend on calculating differences: undo/redo operations, memoization and cache invalidation, state machines, frameworks to build interfaces with the immediate mode paradigm, etc.


One of the reasons I started this series of posts was to explain how using immutable reference data types was one of the tricks at the core of Redux and React. Their success is teaching us a valuable lesson: immutability and pure functions are the core ideas of the current cycle of building applications – being the separation between API and interface the dominant idea of the previous cycle.

I have already mentioned this some time ago, but, at the time, I wasn’t fully aware of how quick these ideas will spread to other areas of the industry or how that will force us to gain a deeper understanding of language fundamentals.

I’m glad they did because I believe that investing in core concepts is what really matters to stay relevant and make smart decisions in the long term.

by Andrés at May 01, 2017 07:51 PM

April 30, 2017

Andrés Maneiro

How equality and copy operations work

In the introductory post of this series we talked about the differences between value and reference data types:

  • Value data types store their payload as the contents of the variable.
  • Reference data types store an identifier as the contents of the variable, and that identifier is a reference to the actual payload in an external structure.

Through this post will see how the equality and copy operations use the content of the variable, meaning that they’ll use the payload for data types and the identifier for reference types.

Working with value data types

Let’s say we have the following value variables:

In plain JavaScript, this would be:

var foo = 42;
var bar = 42;
foo === bar; // this yields true

If we were copying variables instead:

var foo = 42;
var bar = foo;
foo === bar; // true

foo = 23;
foo === bar; // false

As the content of the variables is the mere payload, the operations are straightforward.

Working with reference data types

Let’s say now that we are working with reference data type variables:

In JavaScript, this would translate as:

var x = {'42': 'is the answer to the ultimate question'};
var y = {'42': 'is the answer to the ultimate question'};
x === y; // This yields false.

When we create new reference data type variables, they are going to have a brand new identifier, no matter whether the payload is actually the same than other existing variable. Because the language interpreter is comparing identifiers, and they are different, the equality check yields false.

What if we were copying variables instead:

var x = {'42': 'is the answer to the ultimate question'};
var y = x; // Copies x identifier to y.
x === y; // This yields true.

It is important to realize why these are equal: because their identifiers are equal, meaning that both variables are indexing the same payload.

With that in mind, what would happen on modifying the payload?

x['42'] = 'the meaning of life'; // Changes the payload.

x === y; // Still true, the identifiers haven't changed.
console.log(y['42']); // Yields 'the meaning of life'.


var x = {'42': 'is the answer to the ultimate question'};
var y = x; // Copies x identifier
x === y; // We already know this is true.

x = {'42': 'the meaning of life'}; // New identifier and payload.

x === y; // This would yield false.
console.log(x['42']); // 'the meaning of life'
console.log(y['42']); // 'is the answer to the ultimate question'

The reason is that x = {'42': 'the meaning of life'} assigns a new identifier to x, that references a different payload – so we’ll be back to the first scenario shown in this block.

(A short aside: in the introduction, I mentioned that references and pointers were different. The above case is a good example of how they’re different: if y was a pointer, it would index the contents of x, so both variables would remain equals after x contents change.)

In computer science, the operations that work with the contents of the variable (be it values or reference identifiers) are called shallow operations, meaning that they don’t go the extra step to find and work with the actual payload. On the other hand, deep operations do the extra lookup and work with the actual payload. Languages usually have shallow/deep equality checks and shallow/deep copy operations.

JavaScript, in particular, doesn’t provide built-in mechanisms for deep equality checks or deep copy operations, these are things that either we build ourselves or use an external library.

An example with nested reference data types

A JavaScript idiom to create new objects by reusing parts of existing ones is using the method Object.assign(target, …sources):

var x = {'42': 'meaning of life'};
var y = Object.assign({}, x);
x === y; // Yields false, identifiers are different.
x[42] === y[42]; // Yields true, we are comparing values.

Object.assign creates a shallow copy of every own property in the source objects into the target object. If the target has the same prop, it’ll be overwritten. In the example above, we’re assigning a new identifier to the variable y, whose own properties will be the ones present in the object x.

This works as expected for objects whose own properties are value data structures, such as string or number. If any property is a reference data structure, we need to remember that we’ll be working with the identifiers.

For example:

var book = {
    'title': 'The dispossesed',
    'genre': 'Science fiction',
    'author': {
        'name': 'Ursula K. Le Guin',
        'born': '1929-10-29'

// We are creating a newBook object:
// * the identifier would be new
// * the payload would be created by shallow copying 
//   every book's own property
var newBook = Object.assign({}, book);

newBook === book; // false, identifiers are different

// Compare value data types properties:
newBook['title'] === book['title']; // true
newBook['genre'] === book['genre']; // true

// Compare reference data types properties:
newBook['author'] === book['author']; // true

Both newBook and book objects have the same identifier for the property author, that references the same payload. Effectively, we have two different objects with some shared parts:

If we change some properties, but not the author identifier, both book and newBook will still see the same author payload:

book['title'] = 'Decisive moments in History';
book['genre'] = 'Historical fiction';
book['author']['name'] = 'Stefan Zweig';
book['author']['born'] = '1881-11-28';

newBook === book; // Yields false, identifiers are still different.

// Value variables have diverged.
newBook['title'] === book['title']; // false
newBook['genre'] === book['genre']; // false

// The author identifier hasn't changed, its payload did.
newBook['author'] === book['author']; // true 
newBook['author']['name'] === book['author']['name']; // true 
newBook['author']['born'] === book['author']['born']; // true

For both objects to be completely separate entities, we need to dereference the author identifier in some of them. For example:

book['title'] = 'Red Star';
book['genre'] = 'Science fiction';
book['author'] = { // this assigns a new identifier and payload
    'name': 'Alexander Bogdanov',
    'born': '1873-08-22'

newBook === book; // Yields false, identifiers are still different.

// Reference identifier for author changed,
// and are different objects now.
newBook['author'] === book['author']; // false


Humans have superpowers when it comes to pattern matching, so we are biased towards using that superpower whenever we can. That may be the reason why the reference abstraction is sometimes confusing and why the behavior of shallow operations might seem inconvenient. At the end, we just want to manipulate some payload, why would do be interested in working with identifiers?

The thing to remember is that programming is a space-time bound activity: we want to work with potentially big data structures in a quick way, and without running out of memory. Achieving that goal require trade-offs, and one that most languages do is having fixed memory structures (for the value data types and reference identifiers) and dynamic memory structures (for the reference payload). This is an oversimplification, but I believe it helps us to understand the role of these abstractions. Having fast equality checks is a side-effect of comparing fixed memory structures, and we can write more memory efficient programs because the copy operation works with identifiers instead of the actual payload.

Working with abstractions is both a burden and a bless, and we need to understand them and learn how to use them to write code that is simple. In the next post, we shall talk about one of the tricks that we have: immutable data structures.

by Andrés at April 30, 2017 07:55 PM

Value and reference data types

There are a number of ways to classify data types in computer science. Of all of them, I find that the difference between value data types and reference data types is a useful classification for the daily life of application programmers – knowing the differences results in fewer bugs, less time to understand code, and more confidence to sleep well at night.

One way to think about them is by considering what is the content of the variable for each data type:

  • Value data types store their payload as the contents of the variable.
  • Reference data types store an identifier as the contents of the variable, and that identifier is a reference to the actual payload in an external structure.

Let’s say the FOO variable is a value data type and its payload is 42, while the BAR variable is a reference data type and has 42 as payload. A visual representation of this might look like:

We usually are interested in the payload of the variable (in green), not in their metadata (in red), yet fundamental operations of the languages we use every day have a different behavior depending on whether the variable content is a value or a reference.

For example, JavaScript has value and reference data types: the primitive data types are value data types – number, boolean, or string- and all the rest are reference data types – objects or arrays.

In terms of memory management, it is common for value data types and reference identifiers to be assigned a fixed amount of memory, and to live in a part of the memory called the stack. On the other hand, the reference payload usually doesn’t have a fixed amount of memory assigned so it can grow to any length, and tends to be stored in a different part of the memory sometimes called the heap. This is a generalization and an area that depends heavily on the language and its interpreters, but the reason this distinction exists in some manner is that we want fast and easy operations for an unlimited amount of data: operating with fixed memory variables is easier and faster, but dynamic memory allocation makes a better use of the limited space in memory – it’s a space/time tradeoff.

Boxing and unboxing

Languages with both value and reference data types, tend to provide ways to convert values into references, and vice-versa. This is called boxing and unboxing.

It is common that each value has a reference counterpart. For example, in JavaScript, there is the string primitive and the String object, the number primitive and the Number object, the boolean primitive and the Boolean object.

Also, languages tend to provide automatic boxing and unboxing in some situations. For example, JavaScript primitives don’t have methods or extra properties like the reference objects have; yet, they’ll be automatically boxed to the equivalent reference object when you’re trying to use one of its methods or properties.

This is a source of confusion, and the reason why:

var foo = 'meaning of life';
// Defines foo as a primitive string.
// To define it as the reference object String we'd do
// var foo = new String('meaning of life');

// This yields 'MEANING OF LIFE'.
// Although foo is a primitive we can use the object methods
// thanks to the autoboxing.
// We could think of it as a type conversion in other languages: 
// ((String) foo).toUpperCase();

foo.constructor === String;
// This yields true.
// When we call a property or method belonging the object String,
// foo will automatically boxed, so it behaves like the object.

foo instanceof String; 
// This yields false.
// In this case foo is in its natural state (unboxed),
// so we are comparing the primitive to the reference.

typeof foo;
// This yields 'string'.
// In this case, foo is in its natural state (unboxed),
// so we are asking the system what kind of variable it is.

A note about references VS pointers

Some may argue that reference is how Object Oriented languages coined the old pointer data type. They are different things, though. The way I set them apart is by picturing what are the contents of the variables. References contain an identifier of the payload in an external structure; pointers index the content of another variable.

If, for example, a language would allow us to define a variable called Z as a pointer to X, visually it might look like this:

Although the difference between pointers and reference might be subtle, it has deep connotations when it comes to how operations work with them.


We, applications programmers, are mostly interested in the payload of the variables, but our programs consist of wrangling variables around with operations such as equality checks, copying, and passing arguments to other functions. These operations depend on the nature of the data they work with, so we are bound to deeply understand their inner workings. That will be the topic for the next post of the series.

by Andrés at April 30, 2017 09:48 AM

April 04, 2017

Andrés Maneiro

CSS Grid, from Galifornia

One of the bigger milestones in Q1 2017 was the landing of the new CSS Grid standard in all major browsers.

Personally, the cool thing about this is that support for webkit and blink (namely, safari and chrome browser) was led and developed by IGALIA with a team of people (Manuel, Javier, and Sergio) from Galicia. I love seeing how Baiona or A Coruña can be attractive places for high-tech talent. We are Galifornia!

by Andrés at April 04, 2017 04:25 PM

March 27, 2017

Andrés Maneiro

A FPJS week

Just this week, two of my colleagues at Automattic have written about Functional Programming concepts. Check Grzegorz’s A journey to Functional JavaScript and Miguel’s Functors and monads: an introduction.

by Andrés at March 27, 2017 09:23 PM

February 28, 2017

Andrés Maneiro


After the last blog categories reorganization, I realized that I talk less about what I do and more about what others do. That make sense, as this blog is part of my learning process and I’m always looking around to find ways to improve myself. Yet, I’d like to start writing more about the little things I do. Writing helps me to reflect upon the how, so eventually I’ll learn more about my thought processes. These are likely to be very small things.


sum-csv is a small utility I have built to help me to crunch some statistics I was working with. I had a complete dataset in a CSV file, but what I wanted was an ordered list of the number of times something happened.

Original CSV: What I wanted:

A data transformation

This is a small task – my old self whispered. Yet, instead of opening the editor and start coding right away, the first thing I did was drawing things. I am a visual person and drawing helps me to gain understanding. The algorithm I came up with was a succession of mathematical transformations: Which is to say:

  • transpose the original matrix
  • eliminate the rows I was not interested in
  • for each row, group all numerical values (from column 1 onwards) by adding them, to calculate the total
  • sort the rows by the total

Now, I was prepared to write some code. Amusingly, the gist of it is almost pure English:

d3-array.transpose( matrix ).filter( isWhitelisted ).map( format ).sort( byCount );


Creating production-ready code took me four times the effort of devising an initial solution: finding good and tested libraries for some of the operations not built-in in the language such as reading a CSV into a matrix or transpose the matrix itself, creating the tests for being able to sleep well at night, distributing the code in a way which is findable (GitHub/npm) and usable by others/my future self, and, actually, writing the code.

I am not always able to write code as a series of mathematical transformations, but I find pleasure when I do: it is much easier to conceptually proof whether the code is correct. I also like how the code embodied some of the ideas I’m more interested in lately, such as how a better vocabulary helps you to make things simpler.

by Andrés at February 28, 2017 01:41 PM

February 19, 2017

Andrés Maneiro

A more expressive vocabulary for programming

map and friends are more precise, sophisticated ways to talk about consistent patterns in data manipulation. Using them over for is analogous to using the word “cake” instead of “the kind of food that you make by whipping egg whites and maybe adding sugar”.

Interestingly, you can eventually add new layers of category on top of established layers: just like saying that butter cakes constitute a specific family of cakes, one could say that pluck is a specialization of map.

Of vocabulary and contracts, Miguel Fonseca.

by Andrés at February 19, 2017 04:39 PM

February 10, 2017

Andrés Maneiro

Simple made easy

Precise words make communication more efficient. Arguably, software development is about managing conceptual complexity. Simple made easy, by Rich Hickey is a talk that tackles those two topics.

Two takeaways from this talk:

  • The differences between simple and easy.
    • Simplicity is an objective measure, and its units are the level of interleaving (of concepts). Simplicity should not be measured by the cardinality, the number of concepts/units.
    • Easiness is a subjective measure, and it is related to how familiar you are with some topic or your past experience.
  • We can make things simple with the tools we already have by favoring concepts that make things simpler to reason about, not quicker to write. He recommends:

See also:

by Andrés at February 10, 2017 06:00 AM

January 28, 2017

Andrés Maneiro

La La Land

Now, this is a musical that I like. Entertaining, moving, and complex.

I wouldn’t say musicals are my kind of films. My personal favorite is Sweeney Todd: The Demon Barber of Fleet Street, which is typical Burton. I didn’t like Les Misérables and haven’t watched Moulin Rouge. That’s my track record. Yet, this film is energizing, jazz everywhere, a colorful photography, with brilliant performances by Stone & Gosling.

At the core, I’d say this is a wonderful love story, with a positive and naïve message – just what we need right now. That’d be enough to recommend it. At the same time, it is not what would you expect from a Hollywood film: it is sad in many and fundamental ways, which makes the film a modern story about love, life, and personal growth. And has an epic soundtrack.

by Andrés at January 28, 2017 12:04 PM

January 26, 2017

Andrés Maneiro

To the hackers that grew older

The hacker ethic and the spirit of the information age, by Pekka Himanen, was one of these essays that had a big influence on my early yo. It resonated with how I felt about a lot of things: discovery & learning as a fundamental part of myself or work attached to meaning are two that I remember now. It was the first time I thought about how we divide life into chunks of time, more or less isolated.

One thing I didn’t realize at the time was who this essay was written for: a generation of individuals, with friends & family, but that see themselves as the unit of life in Earth. Given that the book defined the spirit that has driven one of the major social and cultural changes of the human race, this is no minor issue. As Jack Sparrow in the Pirates of the Caribbean, this generation had a mindset of fighting for their liberty against companies and governments. As individuals.

That attitude towards life, I believe, is one of the reasons why the products we create and consume are tailored for the individual and not for the communities: we have a personal music account, a personal pictures account, a personal mail account, etc. Solutions that take the group into account are rare and mostly exist for production-driven organizations (companies or volunteer based bodies), but less for leisure or consumption communities.

As we grew older and our communities became online, they asked us for help. So we create the “pay the service for user” feature as to pay for our relatives accounts, the family plans in our music and video stores, or the network setup for our publishing platform. These changes reflect a fundamental and more humane way to interact with others through technology. We are still in the early stages, but I expect this pattern to become stronger because one of the drivers for this to happen is that we have grown older in the same way that any other generation did in the past: realizing that we are weak as individuals, our natural state is to tribe within groups. Jack Sparrow struggled with this as well; he found out that the Black Pearl can be easily lost if you are on your own, and that you need a team if you want to navigate the ocean in freedom.

I, for one, look forward to a future more community-oriented. What specific shapes it will take is something that only we can invent; so let’s do it.

by Andrés at January 26, 2017 06:15 PM

January 20, 2017

Andrés Maneiro

My office i4

I’ve been working from home for more than 3 years now, and my setup has gone through several iterations – the current one is i4.

After joining Automattic, I was encouraged to think about my office setup. The company sponsors the kind of high-quality office perks that you’ll expect in companies at this level, and I took that opportunity to upgrade my own in ways I had been already thinking about. The fact that you are not in their offices, but in your home adds a different feeling to it. Although I appreciate the company efforts and perks, I’d like to stay frugal within comfortable limits, so I didn’t get anything I wouldn’t buy with my own money. I think of my office setup as a gift for the elder me – I wish he’ll be proud of what his younger self is doing for him.

For i4, these are the new additions to my office:

HAG Capisco 8016 chair, which promotes and supports several seating positions.

DIY kit from Autonomous, to build my own height adjustable desktop so I could change between seating and standing positions.

We, humans, are not designed for seating. A lot has been said about the optimal seating position, but an idea that has gained recognition in ergonomics is that changing positions frequently may be the best long-term strategy.

For the past two months, I’ve been experimenting with that idea to learn what works better for me. I’ve used three main positions -traditional seating, saddle seating, and standing- and a lot of other crazy ones. What I’ve found out is that I change positions through the day as my body asks for it, but I mainly use the saddle position (most of the time, but especially when I need to write) and standing (for consuming information). The traditional seating feels a bit unnatural to me now, although it may be a side effect of using the Capisco which is more tailored for other postures. I also have a more traditional chair at home, but I rarely use it.

This is i4. This setup fits me so well that I cannot imagine what i5 will look like yet.

by Andrés at January 20, 2017 07:00 AM

January 19, 2017

Andrés Maneiro

git time machine

I really like this interface for navigating the git log. If only I could select a stretch of time and make zoom – that’d be spectacular.


by Andrés at January 19, 2017 11:50 AM

November 28, 2016

Andrés Maneiro

Howdy Automattic

This is part of the invitation I was sent to join Automattic. I accepted. Today marks my first day as an automattician, and I am excited to become part of this family. My day-to-day will be filled with the joys and woes of programming but under Automattic’s creed, I feel safe, motivated and happy to do my best. Fun times ahead!

by Andrés at November 28, 2016 09:19 AM

October 23, 2016

Andrés Maneiro

iot hacked

El viernes pasado, varias webs (twitter, github, etc) estuvieron caídas durante gran parte del día debido a un ataque DDOS contra sus servicios DNS. Lo interesante de esta noticia es que los dispositivos usados para atacar no fueron computadoras zombie, sino cámaras y grabadores de video digital conectados a internet. La internet de las cosas hackeada. No directamente relacionado con este caso, pero que puede parecer relevante ahora: Scheiner dice que alguien está aprendiendo a bloquear internet.

by Andrés at October 23, 2016 08:43 PM

October 22, 2016

Andrés Maneiro


Acabo de participar en la campaña de crowfunding de CALIFACTOS, de Juan. Una serie de calendarios y tarjetas navideñas realizadas a partir de objetos pictórico-sonoros que ha ido creando a lo largo de este año.

Os dejo que él mismo os los presente:

Algún amigo ha definido los CALIFACTOS como “fogonazos”, otros de “destellos fugaces”, algunos afirman que se les quedan prendidos de la memoria. Quizás se deba a que fusionan la vista con el oído y a que intento que ambos tipos de percepción se coordinen para poder ofrecer un significado que no resulta del todo evidente ni único.

No me reprimo de afirmar que están animados de un sentido libertario que resulta fácil percibir y espero que sentir. No sabría definir la libertad, pero creo que cada CALIFACTO expresa un deseo e incita a una acción comprometida con la liberación, la emancipación y la autonomía, con el anhelo de vincularnos libremente con el prójimo sin mediadores y sin coerción. A este espíritu le dedico estas emociones que pinto y escribo, y que deseo transformar en la materialidad de unos CALENDARIOS que os acompañen al menos durante el año 2017.

Si quieres calendarios y tarjetas para esta Navidad estás a tiempo de participar y apoyar económicamente el proyecto.

by Andrés at October 22, 2016 01:24 PM

October 14, 2016

Andrés Maneiro

Taking PHP seriously

Slack se une al club de los que usan PHP:

Most programmers who have only casually used PHP know two things about it: that it is a bad language, which they would never use if given the choice; and that some of the most extraordinarily successful projects in history use it. This is not quite a contradiction, but it should make us curious. Did Facebook, Wikipedia, WordPress, Etsy, Baidu, Box, and more recently Slack all succeed in spite of using PHP? Would they all have been better off expressing their application in Ruby? Erlang? Haskell?

Relacionados: inversión y amortización en la selección tecnológica.

by Andrés at October 14, 2016 01:45 PM

October 10, 2016

Andrés Maneiro

Por qué patrocino Eŭropano

Hoy mismo me he convertido en patrocinador de Eŭropano. El compromiso económico inicial es por 6 meses, hasta primavera de 2017. Durante ese tiempo y de manera mensual aportaré 5€ al proyecto. La razón por la que lo hago es que comparto la filosofía del proyecto: crear una esfera pan-europea de debate y acceso a información en una lengua neutral, no ligada a ningún país de la Unión Europea.

La idea base es que la publicación sirva de palanca para eliminar las desigualdades de acceso a la información entre ciudadanos europeos y, por lo tanto, también de acceso a recursos económicos. Si creemos en los mercados como herramienta para el empoderamiento de personas y comunidades, debemos ser sensibles a la actual asimetría de información existente en la Unión Europea y cómo eso favorece la extracción de rentas para unos pocos.

El idioma elegido para la publicación ha sido el esperanto. Lo cierto es que yo no soy hablante de esperanto por el momento y eso requerirá un esfuerzo por mi parte para entender todo lo que se publica. Pero aunque no lea diariamente Eŭropano, el mero hecho de que exista esta iniciativa es positivo para mí y para todos los que creen en la igualdad de oportunidades.

Si queremos cambiar el status quo, no hay más alternativa que participar y ser activo. Hacerlo a través del mercado es una de los superpoderes que tenemos.

Otros patrocinios que he hecho en el pasado:

by Andrés at October 10, 2016 01:45 PM

September 29, 2016

Andrés Maneiro

React antes de React

Our first 50.000 stars, es la historia de React antes de ser React.

While it might look like an overnight success in hindsight, the story of React is actually a great example of how new ideas often need to go through several rounds of refinement, iteration, and course correction over a long period of time before reaching their full potential.


by Andrés at September 29, 2016 01:35 PM

September 21, 2016

Andrés Maneiro


Javi se ha marcado un post maravilloso sobre los inicios d Pokémon, la sensación del verano.

by Andrés at September 21, 2016 03:10 PM

September 04, 2016

Andrés Maneiro

La globalización de las artes marciales

¿Por qué se popularizaron las artes marciales asiáticas pero no la esgrima o los métodos de lucha cuerpo a cuerpo occidentales?

Ésta es una de esas preguntas que lleva tiempo rondando mi cabeza y para la que nunca tuve una respuesta. Hace unos días, comentando en casa nuestra primera clase de Aikido, la conversación nos llevó a resolver este pequeño misterio.


El Aikido es un arte marcial de las consideradas modernas en Japón. Aunque las diferencias entre las artes marciales japonesas tradicionales y modernas son significativas en cuanto a los métodos de entrenamiento y filosofía, la divisoria entre ellas es básicamente el año en que fueron creadas: si es posterior a 1868, es moderna. ¿Por qué ese año en concreto?

Desde el siglo XII, Japón había estado bajo un dictadura militar conocida como shogunato, donde el rol del emperador era ceremonial. La sociedad se organizaba según un sistema feudal con cuatro clases sociales – por orden de importancia: samuráis, granjeros, artesanos y comerciantes. Los samuráis no sólo eran guerreros, sino también guardianes de las tradiciones y la cultura. Su rol era el de aristócratas bajo las órdenes de un señor feudal o daimyo. Durante los primeros siglos del shogunato sus habilidades marciales estuvieron muy demandadas, por lo que se convirtieron en una pieza clave de la estabilidad y poder, llegando a suponer el 10% de la población japonesa. Para hacernos una idea de su presencia en la sociedad, comparando ese porcentaje con la España de 2015, significaría que toda la gente que trabaja en agricultura/ganadería, construcción o industria sería samurái.

Sin embargo, del siglo XVII al XIX, Japón vivió un largo período de casi 250 años con relativa paz, por lo que las habilidades marciales de los samuráis fueron menos demandadas y se introdujeron medidas para restringir su influencia y privilegios. Muchos se reconvirtieron en burócratas, maestros o artistas gracias a su formación. Otros muchos, al morir sus daimyo, no encontraron un reemplazo y se convirtieron en rōnin, vagabundos errantes sin amo ni clan. Estamos en el período Edo durante el shogunato Tukogawa, una época de aislacionismo extremo (sakoku), donde se cerraron las relaciones comerciales con el exterior y entrar o salir de Japón se castigaba con la pena de muerte.

Flash forward al 8 de Julio de 1853.

Ésa es la fecha en la que el Comodoro Perry atraca en la bahía de Edo (actual Tokio) con una pequeña armada a vapor y el objetivo de firmar un tratado comercial. A golpe de cañón, consigue entregar una carta del presidente de los Estados Unidos dirigida al jefe de estado japonés, para negociar el tratado comercial. Los japones recogen forzados la carta y le dan largas. El Comodoro Perry sigue su ruta por Asia. Mientras, los japoneses, fortifican la isla de Odaiba para protegerse de un ataque naval. Dos años después, Perry vuelve a Japón con una armada el doble de grande para recibir una respuesta positiva y firmar el Tratado de Kanagawa. Este episodio hizo evidente que los siglos de aislacionismo habían impedido que Japón se modernizase y abrió un debate entre las élites del shogunato: ¿cómo evitar ser colonizados? Como reacción al evento, se abrieron escuelas navales y se dieron los primeros pasos hacia la industrialización, se formaron cuadros en las nuevas técnicas de la guerra, etc. Pero el mayor cambio se produjo en el marco de pensamiento de las élites: una década después de la llegada de los barcos negros de Perry a la bahía de Tokio, la ruptura es evidente y en 1868 se inicia una guerra civil conocida como la guerra Boshin, que finaliza con la dictadura militar y pone las bases del Japón moderno. 1868, la divisoria simbólica entre las artes marciales tradicionales y modernas en Japón.

En los años posteriores, conocidos como Restauración Meiji, algunos samuráis que habían apoyado al emperador reciben cargos en el nuevo gobierno como premio, pero la industrialización de la guerra y la modernización de las estructuras sociales japonesas aceleran la progresiva pérdida de privilegios e influencia de la clase samurái en su conjunto: pierden el derecho a portar sus katanas en público, el permiso a matar a otros por honor y la recepción de una paga del estado. Este período supuso un gran ERE de la clase samurái, que da sus últimos estertores en 1877, con la rebelión de Satsuma.

¿Qué hacer con los conocimientos sobre arte de la guerra que ahora nadie necesita?

Ésta fue la gran pregunta que respondieron las artes marciales modernas como el Judo o el Aikido: algunos maestros se dieron cuenta de que había un mercado para las artes marciales como programas de desarrollo personal que además pusieran en valor las tradiciones japonesas, siempre que se modernizasen las formas y el entrenamiento. Inicialmente, los compradores fueron la nueva aristocracia japonesa y ciertos sectores del gobierno que requerían sus servicios para formar a los nuevos cuerpos de seguridad con técnicas de lucha cuerpo a cuerpo.

Si trazásemos la evolución de las artes marciales europeas, no sería muy diferente: obtienen privilegios e influencia derivada de su importancia militar durante la época feudal y caen en desgracia a partir del momento en que se convierten en irrelevantes por la industrialización de la guerra y la modernización social. Sin embargo, las artes marciales japonesas -y todas las asiáticas- tuvieron la fortuna de que justo en el momento en que pasaron a tener que sobrevivir lejos de las rentas del estado, se abrió para ellos un mercado global.

Y mientras, en Occidente…

Gracias a la reciente apertura comercial, a finales del siglo XIX lo japonés está de moda. Mackintosh y McDonald diseñan con motivos japoneses las casas del té de la señorita Catherine Craston para la burguesía de Glasgow; el espíritu del Art Noveau recorre Europa con formas, colores y diseños japoneses; el gran hit de las óperas a principios de siglo XX es Madama Butterfly que bajo un relato de amor/desamor para las masas, narra una historia muy similar a la llegada de los barcos negros del Comodoro Perry a Japón y la lucha entre lo tradicional/moderno que vino después. Pero con la apertura, no sólo se abre el comercio de productos e ideas, también de personas. Aumenta la emigración a Occidente y con ella emigra también el aprendizaje de artes marciales.

La globalización durante el siglo XX no hace más que servir de abono a la extensión de la práctica: la segunda guerra mundial y la guerra de Vietnam ponen masivamente en contacto a los ejércitos occidentales con las prácticas militares asiáticas; la industria cinematográfica americana populariza en la segunda mitad del siglo XX las artes marciales como programa de desarrollo personal creando estrellas como Bruce Lee y series de culto como Kung fu; los gobiernos nacionales de Japón, China y Corea ven la oportunidad de usar el arte marcial como embajador de su cultura y mercado, llegando al punto de convertirlo en deporte olímpico (Japón/Judo desde el 64, Corea/Taekwondo desde el 88), etc.


Es un lujo que hoy en día podamos disfrutar de artes marciales como el Aikido o el Taichi. Su ritualidad y práctica codifican siglos de enseñanzas sólo matizadas por el paso del tiempo. Por otro lado, me resulta muy interesante su comportamiento interno, que se parece al de los gremios medievales que trató de recuperar Morris: la transmisión de conocimiento se basa en la práctica y la mejora continua dentro de un grupo, que comparte unos valores y código ético.

Probablemente, la principal razón por la cual todavía existen las artes marciales asiáticas es que se desmilitarizaron justo en el momento en que emergió un mercado global para los programas de desarrollo personal. Un poco de suerte y un poco de adaptación. Ahora que este pequeño misterio que me rondaba la cabeza está resuelto, ya puedo concentrarme en la práctica.

by Andrés at September 04, 2016 10:23 AM

September 03, 2016

Andrés Maneiro

La sociedad de la reacción

A person like Martin Luther King Jr. wouldn’t be able to rally people to realize his great dream today. He would be as desperate for hourly retweets as the rest of us, gathering “likes” from followers on Facebook as a substitute for marching with them. Imagine John F. Kennedy attempting to rally national support for a decade-long race to the moon? The extreme present is not an environment conducive to building lasting movements.

But without a guiding narrative to make sense and create purpose, we end up relying too much on whatever happens to be happening in the moment. When it occurs, we over-respond to the latest school shooting. But over the long term, we lack the resolve or attention span to do anything to stop others from occurring.

How technology killed the future, Douglas Rushkoff

by Andrés at September 03, 2016 09:12 AM

September 01, 2016

Andrés Maneiro

Por no mencionar al perro

¿Puede un libro ser a la vez una comedia de enredos, una novela de detectives, una sátira ambientada en la época victoriana y una obra de ciencia ficción? Todo eso, y más, es “Por no mencionar al perro” de Connie Willis.

De esta autora había leído Oveja Mansa. Aunque son libros y temáticas distintas, hay ciertas reflexiones compartidas; por ejemplo, las que tienen que ver con los sistemas complejos y la teoría del caos, reflexiones sobre si el progreso y la Historia es causal o casual. Quizás se deba a que las dos novelas han sido escritas durante el mismo período y Connie Willis no es inmune a la obsesividad que conlleva el aprendizaje sobre un tema (Spielberg hizo varias películas muy seguidas sobre los extraterrestres o la segunda guerra mundial, Stephenson amortizó su tiempo de investigación sobre mitología sumeria y griega en varios libros, etc). Ambas comparten también cierta manera de tejer el argumento que definiría como característica de Willis: su interés por los usos/modas/costumbres en distintos momentos históricos, las aventuras basadas en situaciones cotidianas y una escritura ligera que saca lo mejor de las comedias románticas.

¿Qué se puede decir de esta novela sin destripar la gracia del argumento?

Para empezar, que está ambientada en el año 2.057, donde existe una máquina de viajes en el tiempo que usan sólo los historiadores de Oxford porque no es rentable para nada más. Luego, que los historiadores Ned Henry y Kindle necesitan deshacer una paradoja temporal, de ésas que a la que despistas modifican el curso de la Historia de tal manera que provocan que los nazis ganen la 2ª guerra mundial, por ejemplo. Las paradojas temporales tienen un papel principal en esta novela; sin embargo, con lo que he disfrutado de verdad es con la aparición estelar de la Luftwaffe y la RAF, con el proyecto de reconstrucción de la catedral de Coventry que habría sido vendida primero a una secta espiritista y luego sustituida por un centro comercial, con el viaje que supone leer sobre la sociedad victoriana del siglo XIX durante la segunda revolución industrial o con los paseos en barco por el Támesis que son en sí mismos una road-movie.

Aunque es una novela larga con varios tirabuzones en el argumento, se hace entretenida gracias a la fina ironía y sátira que impregna el estilo de Connie Willis, así como a su capacidad para sacar jugo a los tópicos del género detectivesco y romántico. Quizás no me arrancó tantas carcajadas como en Oveja Mansa, pero sí me puso de buen humor.

Si eres fan del Ministerio del Tiempo o te gustó la película About Time, es probable que también disfrutes de esta novela donde la Historia es un personaje más. Por no mencionar al perro.

by Andrés at September 01, 2016 01:26 PM

August 20, 2016

Andrés Maneiro

Que empiece la temporada

Está siendo un magnífico verano y aunque nos queda un mes completo todavía, ya el ambiente empieza a oler a Otoño. Y a series. El próximo martes 23 se estrena la tercera temporada de Halt and Catch Fire. Dos días después de que acabe, el 21 de Octubre, empieza BlackMirror. Los astros se alinean para darnos un respiro y que podamos compaginar todo. Qué gustazo. ¡Estamos listos para empezar la temporada!

by Andrés at August 20, 2016 10:09 AM

August 19, 2016

Andrés Maneiro

Send in the clowns

En la misma línea de Stephenson -pero mucho más ácido y humorístico- Max Barry se pregunta a dónde nos lleva esta sucesión de payasadas, por decirlo en sus palabras.

I was thinking about how unfair it is that reality has evil right-wing corporate overlords named the Koch Brothers while if I wrote that in a novel people would call me shallow and juvenile. I mean, it would be true. But also unfair. You’re supposed to have more creative license in fiction, not less. Then there’s Trump, who does things on a daily basis that no satirical character could get away with. It makes you wonder where there is left to go.

Send it the clowns, Max Barry.

Sugiere, además, que la política del espectáculo nos empuja a una situación donde veremos a dos payasos competir por ser presidente – o a un nuevo Hitler ascendiendo al poder. No sabría decidirme entre si será eso lo que viene o más bien deberíamos prepararnos para un oso azul en 3D como próximo diputado de las cortes, como propuso Charlie Brooker en BlackMirror. Y pienso que ahora que las anteriores temporadas se parecen más a un documental que a ciencia ficción futurista, es un alivio que el estreno de la siguiente sea el 21 Octubre. Necesito otra dosis de la vacuna contra la realidad.

by Andrés at August 19, 2016 07:40 AM

August 11, 2016

Andrés Maneiro


Como parte de mi refuerzo de aprendizaje del inglés, en los últimos meses he estado escribiendo varios textos: formales, informales, críticas, emails, académicos, informes, etc. Mi herramienta favorita actual para esos momentos es Grammarly. Las sugerencias van más allá de la mera corrección ortográfica y son contextuales al estilo de la redacción, te recomienda sinónimos a palabras usadas en exceso, se integra en mi flujo diario de trabajo digital (email, Simplenote, etc) y me envía informes semanales de los errores más habituales que cometo, en el navegador funciona como tesauro al seleccionar una palabra, etc ¿qué más se puede pedir?

Al poco de experimentar la versión gratuita me hice premium; fue un flechazo a primera vista. Aunque no lo he usado todavía me gusta además que, de manera natural, te invite a contactar con un humano para revisar textos que son devueltos en menos de media hora, 3h o un día. Han visto muy bien que la gente con la sensibilidad para usar este tipo de herramientas son presciptores naturales de un servicio de traducción humano.

Como todo buen software, tiene sus peculiaridades que hace que les tengas cariño: por ejemplo, las comas de Oxford han sido un descubrimiento y todavía estoy decidiendo de qué bando estoy. Por el momento, lo único que verdaderamente me molesta es que sólo pueda usarla con los textos de inglés. Me gustaría ver algo así para el español, gallego o portugués. ¿Una especie del famoso dardo en la palabra actualizado al siglo XXI?

by Andrés at August 11, 2016 05:52 AM

August 03, 2016

Andrés Maneiro

Dumb Redux

I want to push the idea that concepts are the real win, and they can be expressed in many different ways.

— Tom MacWright, Dumb Redux.

by Andrés at August 03, 2016 04:47 PM

August 02, 2016

Andrés Maneiro

Neal Stephenson on getting big stuff done

En esta charla, Stephenson, introduce la idea de que, como sociedad, nos hemos olvidado de cómo llevar a cabo grandes empresas, esas que se consideran imposible. Hasta que se consiguen. Considera que en la raíz de esto está la pérdida de apoyo a lo cientifíco, que se evidencia en detalles diarios como padres que no quieren vacunar a sus hijos, etc. Pero también que no tenemos la mentalidad adecuada para embarcarnos y asumir el coste de una aventura con riesgo.

Si el mismo tema os resulta interesante, os recomiendo una de las mejores películas de la década: Interstellar. Porque los dioses somos nosotros.

by Andrés at August 02, 2016 05:52 AM

July 31, 2016

Andrés Maneiro

Paul Romer

In a sense, Britain inadvertently, through its actions in Hong Kong, did more to reduce world poverty than all the aid programs that we’ve undertaken in the last century.

The politically incorrect guide to ending poverty. Un perfil de Paul Romer, el nuevo economista jefe del banco mundial.

by Andrés at July 31, 2016 03:15 PM