The long way through Software Craftsmanship

Books read in 2017Q3

Sep 30, 2017 - 6 minute read - Comments - bookreading2017Q3self-studycoduranceaprendicesreading-club

Read this quarter: the senior software developer; Copeland, with the aprendices reading club Scandal in Bohemia, a; Doyle: a short novel by Sir Arthur Conan Doyle, mentioning Irene Adler and the king of Bohemia Getting things done, …; Allen (+): A book on productivity, where Allen explains his method of GTD and how to apply it. Explains what has worked and not worked for him in his many years of consulting and coaching clients.

Self-Study in September 2017

Sep 1, 2017 - 2 minute read - Comments - self-study-aggregationseptember2017androidbelen-albezacarchantal-panozzochip-heathclipboardcodingcomparisoncopy-pastecore-valuedanielle-kurtzlebendavid-piercedecisiondecision-makingearly-retirementeconomyenergy-managementfinancefinancial-independenceformatfrugalityhotspotimprovementindependenceinvestmentiosiphoneliving-standardmatt-burroughmobile-deviceopinionphoneretirementrulesecuritysocial-securityswitzerlandten-ten-ten-ruletime-managementususavalueway-of-livingwindowswork-life-balance

How the Clipboard Works, Part 1 I’ve read this article, by Matt Burrough, on how the clipboard works on windows. Explains how the API works and how the different formats and priorities are organized so the new application can decide which format to accept. Tags: windows, clipboard, matt-burrough, format, copy-paste Top developers can have a life outside coding I’ve read this article by Belen Albeza on how top coders don’t need to spend all their time programming or with activities related to programming.

Finding all pending work in progress (WIP) in your workspace

Aug 7, 2017 - 1 minute read - Comments - bashtoolopen-sourcemicroservicepending-workwipwork-in-progressleanvaluepracticecontinuous-deliverycontinuous-integrationworkspace

It is a good practice to push your local work at the end of the day. Be it for increasing the bus factor (more people have the code), be it for reducing the lifespan of the branches (less time without integrating) or just enabling visibility (your teammates to see what has been developed). If you’re using Continuous Integration (CI) or Continuous Delivery (CD), this is even more often You can even do it more often: for example before going to lunch, before a meeting, before a demo, etc.

Self-Study in August 2017

Aug 1, 2017 - 3 minute read - Comments - self-study-aggregationaugust2017adrian-colyeramazonamazon-web-serviceamir-salihefendicanalogyappastasyncattack-surfaceawsbitcoinbusinesschatchris-dixonchristian-kellnerchromechromiumcljsclojurescriptcommunicationcomparisoncontractcryptocurrencydebiandeep-workdefectdistributiondistrodoistemacsethereumflashglaciergooglehackhueinge-solvolliotjames-forshawjavascriptjslinuxlspmarko-karppinenminerminingmoocomonline-communicationpassive-incomephilipsphilips-hueppapiprivate-networkproductivityproject-zeropublic-networkquoterasqreactreagentreal-timerelease-noterustsaku-panditharatnesecurityside-businessside-projectslacksmart-contractstretchtodoisttokentwistwin32win32kwindowsworkzigbee

How I ended up paying $150 for a single 60GB download from Amazon Glacier I’ve read this article by Marko Karppinen that explains how a mistake in understanding the pricing model of AWS Glacier cost 150$ instead of the expected 0.86$ When cloud providers use uncommon and/or unpredictable pricing models, even your informed hunch about the cost can be off by several orders of magnitude, like the price differential between an iPad and a Ferrari.