The long way through Software Craftsmanship

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.

Books read in 2016Q3

Sep 30, 2016 - 1 minute read - Comments - bookreading2016Q3self-study

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.

Refactoring functional code

Sep 28, 2016 - 1 minute read - Comments - clean-codefunctional-coderefactoringrefactorcode-snippetsnippet

With my pairing mate we have refactored this piece of functional code. Original code: function filterTokens (rawTokens) { const cleanedTokens = rawTokens.map(token => (token.length && token[0] === '-') ? token.substring(1) : token) return cleanedTokens.filter(token => token !== '' && stopWordsArray.indexOf(token) === -1) } Refactored code: function filterTokens (rawTokens) { const cleanedTokens = rawTokens.map(token => startsWithADash(token) ? removeDashFrom(token) : token) const processedTokens = cleanedTokens.filter(token => isNotEmpty(token) && isNotAStopWord(token)) return processedTokens function startsWithADash (token) { return (token.

Self-Study in August 2016

Aug 1, 2016 - 3 minute read - Comments - self-study-aggregationaugust2016read2faaaron-kraussagileamazonbill-sourourbindingcareerconfconferenceconstdegreedevin-coldeweydevopses2015eventual-consistencyexperiencefull-stack-developerfunctionhand-signalsholberton-schoolinterview-processjavascriptjosip-franjkovicjuan-hernandezkyle-younglead-devlessons-learnedlifecyclemaryam-labibnistoccupy-movementon-callopinionpair-programmingpivotalprofessional-careerrace-conditionregulationrestrest-apiryan-alexandersecuritysemicolonsmsspanishstylesylvain-kalachesyntaxtddtdzteamtemporal-dead-zonetitleuniversityus-nistvarweb

Lessons in Agile: Six Months at Pivotal I’ve read this article by Maryam Labib where she explains what she has learned in the last 6 months at Pivotal: how to pair program, how to TDD and some good practices to be a better developer. Tags: maryam-labib, pivotal, career, professional-career, tdd, pair-programming, team, lessons-learned, experience Hacking verbal communication systems I’ve watched this talk by Ryan Alexander on what kind of systems humans use to communicate and how to improve them.

AWS Kinesis Zombieland

Jul 28, 2016 - 1 minute read - Comments - aws-kinesisawsciberadoworkshopworkshop-notesnotes

I attended a workshop on AWS Kinesis, called AWS Kinesis Zombieland by Javi Moreno at capside. Notes AWS Kinesis Zombieland muy importante escoger bien la clave de particionado (id de shard) KPL librería de kinesis que te permite hacer batching, timeout, … la otra se llama KCL. KCL permite mantener estado cuando te pidan una app de big data, pregunta para qué lo quieren, lo mismo que con cualquier proyecto de software latitud = Y, longitud = x el canal se llama stream, la capacidad se llama shard el shard sólo permite 5 lecturas por segundo, 2MB/s usar el shard como buffer usar la clave de particionado como algoritmo de agregación cada vez que tienes una tabla en dynamodb, tienes que poner una alerta de throughput nota: lo que no puedes hacer es guardarlos todos y luego procesarlo.