Books I’ve read this quarter1:
Books started, not yet finished (WIP):
Functional Programming in Scala, by Chiusano and Bjarnason. Doing the exercises with the codurance team Gödel, Escher, Bach: An Eternal Golden Braid, Hofstadter Books I want to finish. Usually come from another quarter:
Books that have entered the queue:
Non-technical that have entered the queue:
La psicología del dinero, Hammond Invirtiendo a largo plazo, García Paramés Quién domina el mundo, Chomsky Homenaje a Cataluña, Orwell El camino al 18J, Payne Cartas desde la revolución bolchevique, Sadoul Shogun: The Life of Tokugawa Ieyasu, Sadler Els jueus i Catalunya, Villatoro Russell en 90 minutos, Strathern El problema de los tres cuerpos, Liu The ending date of the quarter is the same as the publication date ↩︎
Misconception I’ve read in several places that reduce reduces an array1 of values to a single one. The main characteristic of this function is not to reduce to a ‘smaller element’ / ‘single element’, but to have access to the accumulated results and the elements, one by one. Quoting Mozilla Developer Network’s (MDN) Javascript reference:
The reduce() method applies a function against an accumulator and each value of the array (from left-to-right) to reduce it to a single value.
A Docker Fork: Talk of a Split Is Now on the Table I’ve read this article by Alex Williams and Joab Jackson about the possible split in the Docker environment following Docker’s and other providers' product roadmaps. Each own has their policies and priorities and they collide in this case
Tags: docker, alex-williams, joab-jackson, container, oci, kubernetes, devops, tool
An Ode to Boring: Creating Open and Stable Container World I’ve read this article by Bob Wise, in which he describes the state of the Docker tool and the Docker Engine.
Advice for white men I’ve read this article by Cate Huston about how advice affects different people.
But here are some things to consider:
Advice on failure is different for people who are judged on performance rather than potential. Advice on saying no is different for people who aren’t appreciated for doing work for the collective… but who are punished if they don’t. Advice on negotiation is different for people who are perceived negatively when they do negotiate.
Should Engineers Design? I’ve read this article by Cap Watkins where he explains the relationship between designers and programmers and how to get the latter involved in the design / UX / UI process.
Tags: cap-watkins, design, ux, ui, exchange, cross-functional
The Sliding Scale of Giving a Fuck I’ve read this article by Cap Watkins where he explains that different topics have a different importance to each one of us: this topic might be very important for someone else, ergo, it makes mores sense to evaluate their option more carefully.
Books I’ve read this quarter1:
Extreme Programming Pocket Guide by Chromatic Notes to a Software Team Leader (1st Edition), by Roy Osherove Non-technical:
The Zero Marginal Cost Society: The Internet of Things, the Collaborative Commons, and the Eclipse of Capitalism, by Jeremy Rifkin Snow Crash, by Neal Stephenson La guerra no tiene rostro de mujer, by Svetlana Aleksiévich Books started, not yet finished (WIP):
Talking with Tech Leads: From Novices to Practitioners by Patrick Kua Books I want to finish.