The long way through Software Craftsmanship

Self-Study in May 2017

May 1, 2017 - 4 minute read - Comments - self-study-aggregationmay2017readadadblockadvertisementbeliefblogcareerchapterclean-architecturecomiccommunicationcomparisoncomputer-visioncssdefinitionguildhappinesshenrik-kniberghistoryhtmlian-malpassjason-koeblerjavier-garzasjohn-sonmezlanguage-programmerlauren-moonleadershiplisticlematthew-inmanmodel-view-controllermodel-view-presentermosaicmvcmvpoatmealpeoplepersonalpluginprogrammerquoteremoteremote-workrobert-martinroyaltysabbaticalsharky-laguanasimon-lancasterspeechspotifysquadteam-managementtedtedxtrellotribeublockuncle-bobvideoviolawwwzack-bloom

The real reason why the Spotify model is broken I’ve read this article by Sharky Laguana, comparing several royalty models for spotify Tags: sharky-laguana, spotify, comparison, royalty [Day 3 of 7] “Badass” developer gets a RUDE awakening I’ve read this email that John Sonmez sends, about being a programmer vs a language programmer. Some quotes: Someone who could tear apart complex, confusing puzzles and engineer elegant, reliable solutions… whether those challenges were software, hardware or “wetware.

Self-Study in April 2017

Apr 1, 2017 - 1 minute read - Comments - self-study-aggregationapril2017readaustin-gunterblunderboo-booborednesscareerconferencedefinitionderick-baileydockerfailurefaultgerald-weinberginterviewmanagermichael-loppmicroservicemicroservice-practitionersmythorganize-a-conferencepeoplepodcastproject-mercuryqualityquoterichard-lisoftware-engineering-dailysoftware-qualityteam-managementtech-lead

10 Myths About Docker That Stop Developers Cold I’ve read this listicle of docker myths. By Derick Bailey Tags: derick-bailey, docker, myth Bored People Quit I’ve read this article by Michael Lopp on what are some mechanisms why bored people quit. Some interesting quotes: My gig is the care and feeding of engineers, and their productivity is my productivity. If they all leave, I have exactly no job.

Books read in 2017Q1

Mar 31, 2017 - 1 minute read - Comments - bookreading2017Q1self-studycodurance

Books I’ve read this quarter1: Books started, not yet finished (WIP): Books I want to finish. Usually come from another quarter: 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 that have entered the queue: Non-technical that have entered the queue: The ending date of the quarter is the same as the publication date [return]

On the Make, Buy or Rent decision: Stateful vs Stateless components

Mar 16, 2017 - 2 minute read - Comments - lessons-learnedclientstatefulstateful-componentstatelessstateless-componentseparationresource-managementmake-buy-rentphil-simonit-managertotal-cost-ownershiptcoquotedecision

From the Make, Buy or Rent article: […] [T]he three main system options for organizations seeking to upgrade their systems [are :] Make Buy Rent IT managers have different criteria for deciding which components to assign in each category. Another criteria for deciding At a client, they have taken the decision to split their core IT systems in to the three options: make, buy, rent.

Modifying titles in a Trello Board

Mar 16, 2017 - 1 minute read - Comments - trelloautomationscriptcodetool

A teammate and I have created a small tool to modify the titles of the trello card in a trello board. Technical description It works by applying a function to the existing title (because we wanted to remove a prefix from the existing title). The modification is done, not through the API, but simulating user interaction: Click to edit the card Input the new title Save The full code is available here

Convert a project from npm to yarn

Mar 3, 2017 - 1 minute read - Comments - dockertoolpipelinejenkinsyarnnpmjavascript

At a client, we’re converting all projects (i.e., sites, services, libraries) from npm to yarn. Mostly for the speed (as it uses the internal cache). Step by step guide Install yarn in your local environment https://yarnpkg.com/lang/en/docs/install/ Run yarn install This will create a yarn.lock file Add that file to the repo: git add yarn.lock Modify Dockerfile Install yarn (in the Dockerfile). Idea: shortcut this execution with yarn --version in case it is installed Configure the PATH variable (ENV PATH …) ADD yarn.