The long way through Software Craftsmanship

Books read in 2016Q4

Dec 31, 2016 - 1 minute read - Comments - bookreading2016Q4self-studycodurance

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 [return]

A common misunderstanding about `reduce`

Dec 14, 2016 - 2 minute read - Comments - functional-programmingclojurehaskelljavascriptmisunderstandingreducefoldhigher-order-functionquotemozilla-developer-network

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.

Self-Study in December 2016

Dec 1, 2016 - 5 minute read - Comments - self-study-aggregationdecember2016readalex-williamsanalogyautomationautopilotbob-wisebull-in-a-china-shopbytecode-generationcobra-effectcompanycompany-practicecomplacencycontainercopy-pastecppcurious-geordedebugdecoratordevopsdisable-pastedockerdocker-swarmeurekaflat-hierarchyfunctional-programminghackerhaskellimmutabilityinternet-of-thingsiotjames-sinclairjavajavascriptjoab-jacksonkuberneteslearninglearning-programming-languagemanagementmaria-konnikovamario-brosmatthew-garrettmetaprogrammingmonadmonad-explanationmonitoringnpmnpm-linkobi-wan-kenobiociodeopen-salarypassword-fieldpastepawel-brodzinskiphilippa-warrprogramming-languagepromisepythonreal-worldrequestrubysalarysecuritysimeon-simeonovsinging-in-the-rainsource-codetealteal-organizationtoby-retallicktooltroy-huntusabilityuxvalvewatch-expression

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.

Self-Study in November 2016

Nov 1, 2016 - 2 minute read - Comments - self-study-aggregationnovember2016readadvicebartosz-milewskicate-hustoncommitcommit-messagedavid-heinemeier-hanssondhhfeaturefunctional-iofunctional-programminghaskelliojohn-cutlermanagementmicrosoftmonadone-on-oneproduct-developmentproduct-managementpsychologyrantrunar-bjarnasonscalaschool-of-haskelltalktaotao-te-chingtim-popetoolvaluevideo

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.

Support for out of hours on-call support

Oct 5, 2016 - 1 minute read - Comments - on-callsupportreadme

As the preface for the guide for on-call support, a positive note: README You’re cool. I know it. Do not trust yourself, trust me that I trust you. You might be sleepy. It’s OK Everything is going to be fine. Take 5 minutes to think about anything, anytime. Especially before any rash decision. With great power comes great responsibility. Use it wisely. Restoring the services comes first, investigation comes second Do the very minimum of investigation after the incident (collect things that might disappear), leave the rest for the next day on office hours Whenever everything is done, go to sleep but keep an eye on your phone.

Self-Study in October 2016

Oct 1, 2016 - 3 minute read - Comments - self-study-aggregationoctober2016read.netagileappleargumentattackcap-watkinscareer-changecarlos-blecodesaicomparisoncompilationcompiled-javascriptcompiled-languagecompiled-to-javascriptcomputer-scienceconvincingcross-functionaldan-billingdavid-hataniandecision-makingdesigndestructuringdiscussionexampleexchangefeedbackfunctional-programminghaskellhonestyhoneypotinheritancejavascriptjeremy-ashkenasjohn-de-goeslawlessons-learnedliskovlspmacmdnmeetingmodesto-san-juanmonoidnewtype-clasesowen-williamspeoplepost-mortemprecogprocessryan-hewittscrumsecuritysigilsliding-scalesolidstartupstrategythree-amigosticket-magpietype-classesuiuxwikipedia

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.