The long way through Software Craftsmanship

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.

The Nature of Software Development: Part I

Jul 9, 2017 - 7 minute read - Comments - bookron-jeffriesquotereading-breadcrumbthoughtnature-software-developmentpartagilemanagementsoftware-processthinking-processminimum-marketable-featuremmf

The Nature of Software development: reading breadcrumbs, quotes, thoughts Preface The Natural Way serves end users well because it delivers value to them sooner. serves the business […] because it provides important information quickly, and because it provides the ability to adjust direction as needed. serves management […] see what’s really going on inside the project so that when action is needed, there will be time to act. And it reduces management’s problems by making information visible […]

The Search for Value (a quote)

Jul 9, 2017 - 2 minute read - Comments - booknature-software-developmentquoteron-jeffriesdeaprendicesvalueguidingorganizingplanningbuildingslicingsearch-for-valuenatural-waysoftware-developmentprocess

A quote from the book The Nature of Software Development by Ron Jeffries, talking about value (in software) and the building blocks to achieve it: Value. Value, we’ll see, is “what you want.” […] We’ll tell the story by building up from the bottom of the pyramid, describing how to guide, organize, plan, and build our product, in small slices, with a focus on quality. The value we produce is based on these.

Self-Study in July 2017

Jul 1, 2017 - 2 minute read - Comments - self-study-aggregationjuly2017analyticsanarchybenedict-evanscitusdbcloudflarecomparisoncrypto-anarchismcryptographydan-luudiana-kanderencryptionenergyflakeforecastgogolangharvard-business-reviewhbrhidhuman-interaction-devicehunter-blanksimplementation-historyinteractioninterfaceinventionjavaslangkafkakeyboardksuidlibrarylogmarketmichal-chmielarzmouseno-cultureno-peopleoptionoptionalpet-projectphilosophypredictionprioritypublic-key-encryptionresourcesrick-bransonsite-reliability-engineeringsnowflakesretechnologytimetimothy-mayuidusageuser-experienceuuidvavrwhat-did-not-workwhat-workedwolfgang-pauliyes-cultureyes-peoplezero-knowledge-proof

A Brief History of the UUID I’ve read this article by Rick Branson on the history of UUID. Describes the history of uid, uuid, early computing (both networked and not networked) and their own implementation of a uuid library Tags: uuid, uid, flake, snowflake, ksuid, go, golang, rick-branson, library, implementation-history More data, more data I’ve read this article about how cloudflare manages its logs. By Hunter Blanks Tags: log, cloudflare, comparison, what-worked, what-did-not-work, kafka, citusdb, sre, site-reliability-engineering, analytics, hunter-blanks