The long way through Software Craftsmanship

Books read in 2019Q1

Mar 31, 2019 - 14 minute read - Comments - bookreading2019Q1self-studyaprendicesreading-club

This quarter I’ve focused my efforts on a mix of everything:

  • business books: Traction, The Goal
  • philosophy: Stoicism and personal philosophy
  • some finance: classic: Malkiel, personal finance: Robin
  • some classic psychology: Frankl
  • a classic novel: The Metamorphosis (Kafka)

Read this quarter:

  • Hombre en busca del sentido, el; Frankl; own-it, non-technical
  • Metamorfosis; Kafka; own-it, non-technical
  • Your money or your life; Dominguez, Robin; non-technical, finance, own-it
  • Traction; Wickman; own-it, non-technical
  • How to Be a Stoic: Using Ancient Philosophy to Live a Modern Life; Pigliucci; own-it, non-technical
  • Guide to the Good Life, The Ancient Art of Stoic Joy, a; Irvine; non-technical, own-it
  • Goal, the; Goldratt (+); own-it
  • Random walk down wall street a; Malkiel [Parts I, II, III]; own-it

Note: re+read means I’m re-reading this book. The (+) stands for one-or-more times, as in the regexes.

Note: As a curiosity, I’ve added 30 books to the queue in this quarter, while only reading 8. So the list will naturally grow over time.

El hombre en busca del sentido; Frankl (Man’s Search for Meaning)

In this book, Viktor Frankl relates his experiences and learning at the concentration camp.

One of Frankl’s main claims in the book is that a positive attitude was essential to surviving the camps. Consequently, he implied that those who died had given up

https://en.wikipedia.org/wiki/Man%27s_Search_for_Meaning#Reception

Metamorfosis; Kafka

The Metamorphosis tells the story of salesman Gregor Samsa who wakes one morning to find himself inexplicably transformed into a huge insect and subsequently struggling to adjust to this new condition

https://en.wikipedia.org/wiki/The_Metamorphosis

Your money or your life; Dominguez, Robin

This book is split in two parts:

  • Introduction to its philosophy
  • Practical advice for implementing said philosophy

Philosophy

In the first part, the authors give your a framework for computing your real hourly wage: (salary - expenses) / (work time*). where:

  • salary: net income from your job/employment
  • expenses: monetary expenses needed to maintain said job (e.g., car to commute to work, work clothing, work lunches)
  • work time*: hours of work + hours of everything related to work (e.g., commuting, shopping for work clothing, rest time when you are very stressed at work)

They explain the importance of doing the things that motivate us, that bring a positive impact to society and to the world

Traction; Wickman

Recommended by Evgeny Predein, who runs Apiumhub following the advice from this book.

A book report can be found here

How to Be a Stoic: Using Ancient Philosophy to Live a Modern Life; Pigliucci

In this book, which was published after Guide to the Good Life (Irvine), there a few twists to this other referenced book.

Has many examples of how the author lives his life according to this philosophy.

Explains the history of Stoicism (from the Stoa Poikile - the painted Stoa [stoa = portico, porch]).

Guide to the Good Life, The Ancient Art of Stoic Joy, a; Irvine; non-technical

Explains the concept of personal philosophy of life. That it is more important to have one than to have the correct one. That many people don’t have one, don’t even know this concept and go their whole lives without wondering if such thing exists.

Tries to adapt the ancient Stoic philosophy to the modern environment. There are a few twists to the Greek & Roman setups (the Greeks mostly valued virtue, the Romans mostly valued tranquility)

Explains the Stoic virtues, some exercises.

Goal, the; Goldratt (+)

Recommended by Evgeny Predein.

A management-oriented novel […]

https://en.wikipedia.org/wiki/The_Goal_(novel)

The main goal of this novel is to teach using the Socratic method. The authors believe this is a good setup for practicing this concept. It also appears inside the novel, when the wife of the main character also references the Socractic dialogues.

In the introduction, the authors also try to explain the purpose of the book: doing science - coming up with hypotheses, experimenting, validating/invalidating them.

Introduces the concept of the mentor (in the form of a hippie business consultant), for someone who is not available all the time, who aims to provide tips for change itself, rather than making the change.

This book has inspired ‘The Phoenix Project’ (which I also read in the past).

Random walk down wall street a; Malkiel [Parts I, II, III]

(notes from 2019-03-23)

This is a practical guide to understanding finances at an amateur investor level.

Explains concepts such as:

  • Efficient Market Theory (EMT)
  • Capital-Asset Pricing Model (CAPM)
  • Beta (systematic risk from CAPM) and unsystematic risk
  • Modern Portfolio Theory (MPT)
  • Technical and Fundamental Analysis
  • Castles-in-the-air vs Firm-Foundation Theories

Explains the background to the current investment scenario: the bubbles, the analysts, the conflicts of interest.

All of that in readable prose, well-connected story.

Also provides a practical guide for the investor, mostly targeted at the US investor (e.g., IRA, Roth IRA, 529s, 401(k))

Spoiler: a random walk is defined as a path in which the next step (to be taken) bears no relationship to the past. This is what the author suggests in relation to the stock prices.

Export from my backlog

backlog (partially sorted):

  • unsorted V
  • The Machine That Changed the World: The Story of Lean Production
  • Haskell Programming
  • Software Architecture in Practice
  • lucha por la desigualdad, la; Pontón; non-technical
  • psicología del dinero, la; Hammond; non-technical
  • Invirtiendo a largo plazo; García Paramés; non-technical, finance
  • Well-Grounded Java Developer, the; own-it
  • Learn You a Haskell for Great Good!; own-it
  • camino al 18J, el; Payne; non-technical
  • Cartas desde la revolución bolchevique; Sadoul; non-technical
  • Java Performance: The Definitive Guide
  • Why programmers work at night
  • Shogun: The Life of Tokugawa Ieyasu; Sadler; non-technical
  • Scrum and XP from the trenches, 2nd edition;
  • Els jueus i Catalunya; Villatoro; non-technical
  • El problema de los tres cuerpos; Liu; non-technical
  • Amazon Web Services in Action; own-it
  • Clojure Programming - Practical Lisp for the Java World
  • Mature optimization
  • XUnit Test Patterns
  • Let Over Lambda
  • The Haskell Road to Logic, Math and Programming
  • Types and Programming Languages
  • Fundamentals of Object-oriented Design in UML
  • Clojure for the brave and true
  • How to Solve It: A New Aspect of Mathematical Method
  • Conceptual Mathematics: A First Introduction to Categories
  • Understanding Computation: From Simple Machines to Impossible Programs
  • Programming in Haskell
  • Programming Languages: Application and Interpretation
  • Doing Math with Python
  • Perfect Software: And Other Illusions about Testing
  • Computability and Complexity - From a Programming Perspective
  • Thinking Forth: a language and philosophy for solving problems
  • Concepts, Techniques, and Models of Computer Programming
  • Bridging the Communication Gap; Adzic
  • Specification by Example; Adzic
  • Cucumber book, the; Adzic
  • Software Architecture for Developers; Brown
  • Object Design: Roles, Responsibilities, and Collaborations
  • RESTful Web APIs
  • RESTful Web Services Cookbook
  • Building Maintainable Software
  • Serverless - Patterns of Modern Application Design Using Microservices (Amazon Web Services Edition)
  • A Pattern Language; Alexander
  • Types and Programming Languages, TAPL; Pierce; own-it
  • Speed Reading Book: Read More, Learn More, Achieve More, the; Buzan
  • Cómo crear mapas mentales (Crecimiento personal); Buzan
  • First things first; Covey
  • What’s best next; Perman
  • problems of philosophy, the; Russell
  • Requiem for the American dream; Chomsky
  • sun also rises, the; Hemingway
  • travels, the; Polo; non-technical
  • Homo Deus: A Brief History of Tomorrow; Harari; non-technical
  • Books by Aristotle; non-technical
  • Books by Plato; non-technical
  • Books by Descartes; non-technical
  • The idea of culture; Eagleton; non-technical
  • Hereditary Intelligence; Galton; non-technical
  • Lean Software Development: An Agile Toolkit; Poppendieck (+)
  • Chaos Monkeys: Obscene Fortune and Random Failure; Garcia Martinez
  • Implementing Lean Software Development: From Concept to Cash; Poppendieck
  • Joel on Software; Spolsky
  • Death March; Yourdon
  • Psychology of Computer Programming, The; Weinberg
  • Introduction to General Systems Thinking; Weinberg
  • Lao Tzu : Tao Te Ching : A Book About the Way and the Power of the Way; Tzu, Le Guin; non-technical
  • Gay Science, the; Nietzsche; non-technical
  • Being Geek; Lopp
  • Finance for Freelancers; Retallick; non-technical, finance
  • Object-oriented software engineering: a use case driven approach; Jacobson
  • Patterns of Enterprise Application Architecture; Fowler; own-it
  • Romeo y Julieta; Shakespeare; non-technical
  • Computer Systems: A Programmer’s Perspective; Bryant, O’Hallaron
  • My Journey to Lhasa: The Classic Story of the Only Western Woman Who Succeeded in Entering the Forbidden City; David-Néel; non-technical
  • Cathedral and the bazaar, the ; Raymond
  • Coding dojo handbook, the; Bache; own-it
  • Making software; Oram and Wilson; own-it
  • Code complete; McConnell; own-it
  • Soft skills; Sonmez; own-it
  • DSLs in action; Ghosh; own-it
  • Purely functional data structures; Okasaki; own-it
  • Working effectively with unit tests; Fields (+); own-it
  • First Nazi, the; Ludendorff; non-technical
  • Greatest story ever told … so far; Krauss; non-technical
  • Master algorithm, the; Domingos; non-technical
  • Invention of Science, the; Wootton; non-technical
  • Tesla: Inventor of the electrical age; Bernard Carlson; non-technical
  • Psychology in minutes; Weeks; non-technical
  • Alan Turing: The Enigma; Hodges; non-technical
  • How to think more about sex; de Botton; non-technical
  • Piccolo manuale di persuasione; Taylor; non-technical
  • arte de la guerra, el; Sun Tzu; non-technical, own-it
  • Piccolo manuale di leadership Confuciana; Adair; non-technical
  • How to Stop Worrying and Start Living; Carnegie; non-technical
  • Uomo - Guida allo stile; Roetzel; non-technical
  • Unwritten Laws of Engineering: Revised and Updated Edition; King
  • Test-Driven JavaScript Development (Developer’s Library); Johansen
  • Test Driven Development: By Example; Beck
  • Arquitectura Java JPA Domain Driven Design; Alvárez, Peláez
  • End of loyalty, the; Wartzman; non-technical
  • Basic Economics; Sowell; non-technical
  • Introduction to Economic Analysis; McAfee; non-technical
  • Patterns of Software; Gabriel
  • Coders at work; Seibel
  • Clean architecture; Martin
  • How to be a stoic - Pugliucci; non-technical
  • Introduction to Object-Oriented Programming, an; Budd
  • Gafas de la felicidad, las; Santandreu; non-technical
  • Ser feliz en Alaska; Santandreu; own-it, non-technical
  • Mochila para el universo, una; Punset; non-technical
  • Gods themselves, the; Asimov; non-technical
  • Panamá papers, the; Obermayer, Obermaier; non-technical
  • Originals; Grant; non-technical
  • Optimism over despair; Chomsky; non-technical
  • SCIENCE OF BREATH: A Practical Guide; Ballentine, Hymes; non-technical
  • Yoga Explained: A New Step-by-step Approach to Understanding and Practising Yoga; Mehta,‎ Arjunwadkar; non-technical
  • Wanderlust: A Modern Yogi’s Guide to Discovering Your Best Self; Krasno; non-technical
  • How to Think About Money; Clements; non-technical, finance
  • By Way of Deception; Ostrovsky; non-technical
  • Printemps des sayanim, le; Cohen; own-it, non-technical
  • Deep work; Newport; non-technical, own-it
  • Hooked: How to Build Habit-Forming Products; Eyal, Hoover; non-technical
  • Irresistible: The Rise of Addictive Technology and the Business of Keeping Us Hooked; Alter; non-technical
  • The Attention Merchants: The Epic Scramble to Get Inside Our Heads; Wu; non-technical
  • Willpower: Why Self-Control is The Secret to Success; Baumeister, Tierney; non-technical
  • Principles of Psychology, the; James; own-it, non-technical
  • Our mutual friend; Dickens; non-technical
  • Crucial Conversations: Tools for Talking When Stakes Are High, Second Edition; Patterson, Grenny, McMillan, Switzler; non-technical
  • Amusing Ourselves to Death - Public Discourse in the Age of Show Business; Postman; non-technical
  • Mastery; Greene; non-technical, own-it
  • Silence in the age of noise; Kagge; non-technical
  • Functional programming simplified; Alexander; own-it
  • Batalla del Ebro, la; Reverte; non-technical
  • Historia de la guerra civil española; Rojo; non-technical
  • Lucha por el poder, la; Evans; non-technical
  • Revolución rusa, la; Pipes; non-technical
  • Holocausto, el; Rees; non-technical
  • Martín Lutero, renegado y Profeta; Roper; non-technical
  • Siglo de la revolución, el ; Fontana; non-technical
  • Història de la revolución rusa; Trotsky; non-technical
  • Dispossessed, the; Le Guin; non-technical
  • Left hand of darkness; Le Guin; non-technical
  • Lathe of heaven; Le Guin; non-technical
  • https://www.amazon.com/Schopenhauer-Cure-Novel-Irvin-Yalom/dp/0060938102/
  • https://www.amazon.com/How-Schopenhauer-Through-Mid-Life-Crisis-ebook/dp/B00QXNB5PC/
  • Books in general – Epstein
  • Affluent society, the; Galbraith; non-technical, finance
  • Philosophy of the Buddha; Bahm; non-technical
  • Tribe of mentors; non-technical, own-it
  • 5 dysfunctions of a team; non-technical
  • Ziglar’s Top Performance; non-technical
  • Pragmatic Programmer (+)
  • High Output Management; Grove; non-technical
  • First Break All the Rules; non-technical
  • Managing for happiness; Appelo; non-technical
  • Meditations; Marcus Aurelius; non-technical, own-it
  • Why budism is true; Wright; non-technical, own-it
  • 7 hábitos de la gente altamente productiva
  • art of readable code
  • Domain modeling made functional
  • Sketchbook handbook; own-it
  • Agile samurai, the
  • Miracle of Mindfulness, the; Hanh; non-technical, own-it
  • No mud, no lotus: The Art of Transforming Suffering; Hahn; non-technical
  • Lean Architecture: for Agile Software Development; Coplien, Bjørnvig
  • Agile IT Organization Design: For Digital Transformation and Continuous Delivery; Sriram Narayan
  • Philosophy of Software Design, a; Ousterhout
  • Hope in the Dark; Solnit
  • Agile!: The Good, the Hype and the Ugly; Meyer
  • Common Stocks and Uncommon Profits and Other Writings; Fisher, Fisher; non-technical, finance
  • Prize: The Epic Quest for Oil, Money & Power, the; Yergin; non-technical
  • So good they can’t ignore you; Newport
  • Creating a Software Engineering Culture; Wiegers
  • Managing Humans: Biting and Humorous Tales of a Software Engineering Manager; Lopp
  • Don’t make me think; Krug
  • Leaders eat last; Sinek; own-it
  • art of the start, 2, the; Kawasaki; own-it
  • Unlimited memory; own-it
  • Selfish gene, the; Dawkins; own-it
  • Public speaking skills for dummies; own-it
  • 365 days with discipline; own-it
  • How to fight; Hahn; own-it
  • 33 strategies of war; own-it
  • Leader who had no title, the; own-it
  • greatness guide, the; own-it
  • Year of happy living, the; own-it
  • 4 hour chef, the;; own-it
  • Finish what you start; own-it
  • Personal MBA, the; Kaufmann; own-it
  • Richest man in Babylon, the; own-it
  • Think and grow rich; Hill; own-it
  • Why Buddhism is true; own-it
  • Wisdom of Hypatia: Ancient Spiritual Practices for a More Meaningful Life, the; MacLennan; non-technical
  • Just enough software architecture
  • Elastic leadership; Osherove; own-it, non-technical
  • Taking smart notes; own-it, non-technical
  • Secure by design; own-it
  • Reset; Sawyer; non-technical, finance
  • Investor’s manifesto, the; Bernstein; own-it, non-technical, finance
  • Splendid exchange, a; Bernstein; own-it, non-technical, finance
  • Birth of plenty, the; Bernstein; own-it, non-technical, finance
  • Simple path to wealth, the; Collins; own-it, non-technical, finance

unfinished (unsorted):

  • Working Effectively with Legacy Code (+); Feathers; own-it
  • Nonviolent communication (+); Rosenberg; own-it, non-technical
  • Introduction to Buddhism: Teachings, History and Practices, an; Harvey; non-technical, own-it
  • Effective Java; Bloch; own-it
  • Functional Programming Patterns in Scala and Clojure; own-it
  • Release It! - Design and Deploy Production-Ready Software; own-it
  • Refactoring (+); Fowler; own-it
  • Leprechauns of Software Engineering (+), the; Bossavit; own-it
  • Domain-Driven Design: Tackling Complexity in the Heart of Software; Vernon (+); own-it
  • Pragmatic Thinking and Learning: Refactor Your Wetware; own-it
  • Readings in Database Systems, 5th Edition; own-it
  • Structure and Interpretation of Computer Programs (SICP); Abelson, Sussmann, Sussmann; own-it
  • La Sociedad De Coste Marginal Cero (Estado y Sociedad); Rifkin; non-technical
  • Odisea; Homero; non-technical
  • Switch: How to Change Things When Change Is Hard; Heath, Heath; own-it, non-technical
  • Cómo leer un libro; Adler, van Doren; non-technical, own-it

next:

  • Mundo nuevo, ahora, un; Tolle; own-it, non-technical
  • Continuous Delivery; Humble, Farley; own-it
  • Java Concurrency in Practice (JCIP); Goetz
  • Thinking fast and slow; Kahneman; non-technical
  • Your money or your life (+); Dominguez, Robin; finance, non-technical, own-it
  • five dysfunctions of a team: a leadership fable, the; Lencioni; non-technical
  • Who rules the world?; Chomsky; non-technical, own-it
  • Random walk down wall street a; Malkiel [Part IV]; own-it

wip (2):

  • Hombre multiorgásmico, el; Chía, Arava; own-it, non-technical
  • Object-Oriented Design Heuristics; Riel
  • 4 pillars of investment, the; Bernstein; own-it, finance, non-technical

done:

  • Hombre en busca del sentido, el; Frankl; own-it, non-technical
  • Metamorfosis; Kafka; own-it, non-technical
  • Your money or your life; Dominguez, Robin; non-technical, finance, own-it
  • Traction; Wickman; own-it, non-technical
  • How to Be a Stoic: Using Ancient Philosophy to Live a Modern Life; Pigliucci; own-it, non-technical
  • Guide to the Good Life, The Ancient Art of Stoic Joy, a; Irvine; non-technical, own-it
  • goal, the; Goldratt (+); own-it
  • Random walk down wall street a; Malkiel [Parts I, II, III]; own-it

rejected:

  • Stanger in a strange land; Heinlein; own-it, non-technical

lists:

past-done:

  • Prince, the; Macchiavello; non-technical, own-it
  • Nuevo kama-sutra ilustrado, el; Gallotti; non-technical
  • Quien se ha llevado mi queso; Johnson; own-it
  • One minute manager, the; Blanchard; own-it, non-technical
  • En defensa de los ociosos; Stevenson; non-technical, own-it
  • Ladybird Book of Mindfulness, the (Ladybirds for Grown-Ups); Hazeley, Morris; non-technical
  • Art of the start, the; Kawasaki; own-it, non-technical
  • Getting started with NoFap; non-technical
  • Emotional intelligence; Goleman; non-technical
  • Old man’s war; Scalzi; non-technical, own-it
  • Nightfall; Asimov, Silverberg; own-it, non-technical
  • Interface; Stephenson, George; non-technical, own-it
  • Man who sold the moon, the; Heinlein; own-it, non-technical
  • Agents of innocence; Ignatius; own-it, non-technical
  • Fist of god, the; Forsyth; own-it, non-technical
  • Avaro, el; Molière; own-it, non-technical
  • Bogleheads’ Guide to Investing, the; Larimore, Lindauer, LeBoeuf; own-it, non-technical, finance
  • Lazyperson’s guide to investment; Farrell; own-it, non-technical, finance
  • Millionaire next door, the; Stanley, Danko; own-it, non-technical, finance
  • Little Book of Common Sense Investing; Bogle; own-it, non-technical, finance
  • Monje que vendió su Ferrari, el; Sharma; own-it, non-technical
  • Siddhartha; Hesse; non-technical, own-it
  • If you can: how millenials can get rich slowly; Bernstein; own-it, non-technical, finance
  • Odessa; Forsyth; non-technical, own-it
  • Bogle on mutual funds: new perspectives for the intelligent investor; Bogle; own-it, non-technical, finance
  • Perros de la guerra, los; Forsyth; own-it, non-technical
  • avaro y el oro, el; Esopo; non-technical
  • Aulularia; Plauto; own-it, non-technical
  • Alternativa del Diablo, la; Forsyth; own-it, non-technical
  • Guía, el; Forsyth; own-it, non-technical
  • Pied piper; Forsyth; own-it, non-technical
  • Hunt for the Red October, the; Clancy; own-it, non-technical
  • Time to kill, a; Grisham; own-it, non-technical
  • Ética promiscua; Easton, Hardy; own-it, non-technical
  • Checklist manifesto, the; Gawande; own-it, non-technical
  • Team geek (+); own-it
  • Kata de la voluntad; non-technical
  • Obstacle is the way, the; non-technical
  • Guide to stoicism, a; Stock; own-it, non-technical
  • Senior software developer, the; Copeland; own-it
  • Scandal in Bohemia, a; Doyle; own-it
  • Getting things done, …; Allen (+); own-it, non-technical
  • Nature of Software Development, the; Jeffries; own-it
  • Team Geek; Fitzpatrick, Collins-Sussman; own-it
  • Aprendo Yoga; Van Lysebeth; non-technical, own-it
  • Clean Coder: A Code of Conduct for Professional Programmers, the; Martin; own-it
  • ML for the working programmer, 2nd edition [5th chapter only]; Paulson; own-it
  • Lazarillo de Tormes, el; anónimo; non-technical
  • Tom Clancy’s power plays - Politika; Preisler; own-it, non-technical
  • Moon is a harsh mistress, the; Heinlein; own-it, non-technical
  • Tus zonas erróneas; Dyer; non-technical, own-it
  • Peopleware; DeMarco, Lister (+); own-it
  • Phoenix project, the ; Kim, Behr, Spafford; own-it
  • Ética a Nicómaco; Aristotle; own-it, non-technical
  • Book of transformation; Dalai Lama; non-technical
  • Como ganar amigos e influir sobre las personas; Carnegie (+); own-it
  • Oliver Twist; Dickens; own-it, non-technical
  • Building evolutionary architecture; Ford, Parsons; own-it
  • Selfie: How We Became So Self-Obsessed and What It’s Doing To Us; Storr. Just chapter 1: The dying self; own-it, non-technical
  • Sota la cistella; Gasol; own-it, non-technical

Self-Study in March 2019

Mar 1, 2019 - 9 minute read - Comments - self-study-aggregationmarch2019abstractionadviceagileagile-developmentanalogyandroidanti-architecturearchitectureask-hnaustraliabootstrapburtonatorcareer-changecareer-managementchangechasmclientclosedclosed-standardclscomparisonconsultingcontinuation-local-storagecreativitycritical-pathdesigndev-toolseconomic-perspectiveend-user-programmingengineerextensibilityextensionfinanceflexibilityfor-profitfounderfreelancegooglegotifygps-driftgrid-layouthackernewshealthy-eatinghealthy-testinghistoryhooki18nintegration-testkent-c-doddsleaderlean-testingleapfrog-solutionlearningloggingmaintenancemanagementmetaphormichael-pollanmoficationmoney-managementmoney-wealthmythnodejsnotificationnotification-serviceocpopenopen-closed-principleopen-sourceopen-standardpersonal-knowledge-basepolarizedprint-designprofessional-growthprogrammingprogressionproject-managementprotocolproxypublic-speakingquotereflectionreplresourcereturn-on-investmentrevenuereviewroiruleself-hostedside-businessside-hustlesolo-founderspeakspeakingspreadsheetsqlstartuptest-pyramidtestingtesting-pyramidtesting-trophytheorythread-localthread-local-storagetime-managementtime-wealthtlstooltrace-idtracingunit-testunixuserw3wwarcwarchweb-2.0web-3.0web-archiveweb-builderweb-designweb-design-3.0what-three-words

NodeJS logging made right

Explains logging and tracing in nodejs.

Usage of thread-local storage, trace id, continuation local storage.

Tags: nodejs, logging, tracing, thread-local, thread-local-storage, trace-id, continuation-local-storage, cls, tls, proxy, hook

Id: 5bed4596-3f5b-11e9-83e1-0242ac110005 Read: Tue, 05 Mar 2019 15:28:42 +0000

Web Design 3.0: When Your Web Design Really Matters

In Chapter 1, we will find out how Web Design is changing. Also, you will learn about the birth of the new generation of web designers, who are designing web pages in Web Design 3.0.

In Chapter 2, we will talk about website builders that are lagging behind the trends and slowing down the Web Design evolution.

In Chapter 3, you will learn how to create modern web designs quickly and easily in a new way.

Has walk through the different design phases, techniques; both in press (printed) design as in web design.

Explains some web builders.

Explains the concept of the web 3.0:

  • Free positioning.
  • Element overlapping.
  • Breaking the limitations of Bootstrap-like Grids.

States the different needs for webmasters and designers:

Web Designers need:

  • Free positioning
  • Removing table constraints
  • Layers
  • Property Panel for elements
  • Support for Windows and Mac OS

Webmasters need:

  • Clean HTML and CSS
  • Mobile device support
  • WordPress and Joomla support
  • Building websites online

Summary

Website builders are lagging behind the rapidly changing Web Design world.

The history of web design tools has involved several transitions. However, progress has stopped. There are numerous signs that the new transition must happen.

There are separate markets for web designers and webmasters. Popular website builders do not support the main features of Web Design 3.0: free positioning, modern grids, and layers.

Tags: comparison, web-design, print-design, web-builder, creativity, metaphor, grid-layout, bootstrap, flexibility, design, web-3.0, web-design-3.0, web-2.0, progression

Id: 5101ce2e-3f5e-11e9-83d9-0242ac110005 Read: Tue, 05 Mar 2019 15:49:52 +0000

Gotify – a self-hosted push-notifications service

Tags: gotify, self-hosted, notification, notification-service, android, open-source

Id: e839c82a-4367-11e9-b34d-0242ac110007 Read: Sun, 10 Mar 2019 19:08:36 +0000

Ask HN: How to speak like a leader, not like an engineer?

Links and resources for speaking like a leader

Tags: leader, engineer, comparison, change, public-speaking, speak, speaking, career-management, career-change, professional-growth, resource:

Id: 1a478fc8-4368-11e9-b657-0242ac110007 Read: Sun, 10 Mar 2019 19:10:00 +0000

ArchiveBox: Open-source self-hosted web archive

Tools for archiving purposes. Has links to other sites:

https://github.com/machawk1/warcreate https://getpolarized.io/

Tags: burtonator, web-archive, polarized, warch, warc, personal-knowledge-base

Id: 4168161c-436e-11e9-aa0d-0242ac110007 Read: Sun, 10 Mar 2019 19:54:03 +0000

Ask HN: As a freelancer, what’s the best app to track finances?

Describes tools for finance for freelancers. Stresses the importance of time wealth

Tags: time-management, money-management, freelance, tool, ask-hn, hackernews, finance, time-wealth, money-wealth

Id: b74a6696-4c83-11e9-99bd-0242ac110005 Read: Fri, 22 Mar 2019 09:20:21 +0000

What I Learned in My First Year as a Solo Founder

Learnings by a solo founder.

Benefits of having a side project or side hustle

Tags: side-hustle, side-business, learning, reflection, solo-founder, founder, revenue

Id: f0dee42c-5142-11e9-9444-0242ac110006 Read: Thu, 28 Mar 2019 10:19:16 +0000

Write tests. Not too many. Mostly integration.

This is a paraphrasing of some advice for healthy eating: ‘Eat food, not too much, mostly plants.’ (Pollan)

Write tests.

Often I find myself saving time when I put time in to write tests

Not too many: you get diminishing returns on your tests as the coverage increases […]

Mostly integration: as you move up the pyramid, the confidence quotient of each form of testing increases

Integration tests strike a great balance on the trade-offs between confidence and speed/expense

Tags: unit-test, testing, test-pyramid, healthy-testing, advice, integration-test, quote, kent-c-dodds, analogy

Id: d148d774-5144-11e9-94d8-0242ac110006 Read: Thu, 28 Mar 2019 10:32:42 +0000

7 Rules for Eating

In this reference article, Michael Pollan explains his seven rules for eating:

  1. Don’t eat anything your great grandmother wouldn’t recognize as food. “When you pick up that box of portable yogurt tubes, or eat something with 15 ingredients you can’t pronounce, ask yourself, “What are those things doing there?” Pollan says.
  2. Don’t eat anything with more than five ingredients, or ingredients you can’t pronounce.
  3. Stay out of the middle of the supermarket; shop on the perimeter of the store. Real food tends to be on the outer edge of the store near the loading docks, where it can be replaced with fresh foods when it goes bad.
  4. Don’t eat anything that won’t eventually rot. “There are exceptions – honey – but as a rule, things like Twinkies that never go bad aren’t food,” Pollan says.
  5. It is not just what you eat but how you eat. “Always leave the table a little hungry,” Pollan says. “Many cultures have rules that you stop eating before you are full. In Japan, they say eat until you are four-fifths full. Islamic culture has a similar rule, and in German culture they say, ‘Tie off the sack before it’s full.'”
  6. Families traditionally ate together, around a table and not a TV, at regular meal times. It’s a good tradition. Enjoy meals with the people you love. “Remember when eating between meals felt wrong?” Pollan asks.
  7. Don’t buy food where you buy your gasoline. In the U.S., 20% of food is eaten in the car.

Also, four myths:

  1. Food is a delivery vehicle for nutrients. What really matters isn’t broccoli but its fiber and antioxidants. If we get that right, we get our diet right. Foods kind of get in the way.
  2. We need experts to tell us how to eat. Nutrients are invisible and mysterious. “It is a little like religion,” Pollan said. “If a powerful entity is invisible, you need a priesthood to mediate your relation with food.”
  3. The whole point of eating is to maintain and promote bodily health. “You are either improving or ruining your health when you eat – that is a very American idea,” Pollan says. “But there are many other reasons to eat food: pleasure, social community, identity, and ritual. Health is not the only thing going on on our plates.”
  4. There are evil foods and good foods. “At any given time there is an evil nutrient we try to drive like Satan from the food supply – first it was saturated fats, then it was trans fat,” Pollan says. “Then there is the evil nutrient’s doppelganger, the blessed nutrient. If we get enough of that we, will be healthy and maybe live forever. It’s funny through history how the good and bad guys keep changing.”

This can all be summarized as “Eat food, not too much, mostly plants.”

Tags: healthy-eating, michael-pollan, rule, advice, myth, analogy

Id: 30ece1fc-5145-11e9-87de-0242ac110006 Read: Thu, 28 Mar 2019 10:35:22 +0000

Lean Testing or Why Unit Tests are Worse than You Think

This article puts testing in an economic perspective. Calls it lean testing

Also references/paraphrases Michael Pollan’s Rules for eating ().

Creates a testing trophy, a figure to explain the best testing pattern, replacing the testing pyramid

Explains return on investment (ROI) on tests

integration tests provide the best balance of cost, speed and confidence

Integration tests lie somewhere between unit tests and end-to-end tests so they provide the best balance. Therefore, they have the highest ROI.

The main idea is to just not mock so much

Tags: economic-perspective, lean-testing, testing-trophy, testing-pyramid, return-on-investment, roi, critical-path, testing, unit-test, anti-architecture, architecture, maintenance

Id: efe85d00-5147-11e9-87ce-0242ac110006 Read: Thu, 28 Mar 2019 10:55:02 +0000

End-user programming

In this article, the writer explains some of the end-user modifications to programs. Examples include: adding download capabilities to instagram, generating backups for files.

On the other hand, applications (especially mobile) are tightly sealed, not allowing modification or extension. Even FOSS (free, open source software), modification implies the learning curve / entry barrier of having to setup, compile, debug the original program and modifications.

Gives the example of the UNIX command line, as a programming environment. One that provides (one of) the best REPL examples.

Characterizes spreadsheets as ad-hoc databases, programs; mostly created by domain experts (aka subject matter experts), than professional software engineers. Take into account that these hats are non-exclusive: a domain expert can also be a professional software engineer.

The author tries to coin the term “end-user programming” to differentiate it from programming by professional software developers, who try to build general-purpose apps, to be used by thousands of people.

This also means, that a professional software developer can be an “end-user programmer”, when creating solutions for themselves (limited user group), rather than for the general public. Maybe those one-off scripts that we create, are some kind of end-user programs. This is described in the article as well.

Talks of the chasm the user has to cross in order to customize the behaviour of their software. This is related to working in a framework or a library, in the sense of ‘who keeps the control’. In an UNIX, filesystem environment, you keep the control.

References “citizen developers” (https://www.gartner.com/it-glossary/citizen-developer/)

Three qualities for end-user programming: embodiment, living systems, and in-place toolchains

Embodiment: it requires the programmer hold many abstractions in their mind. Related to abstract reasoning. Mentions that many end-users don’t have these abstractions in their mind, but are capable of abstract reasoning in their own domains of expertise. Mentions that via visual representations onscreen, we can help the end-user. An example: preview formula results in a spreadsheet; highlight the cells in a spreadsheet.

Embodiment means, broadly, making elements of the programming experience more concrete and visual

Living systems: interaction with them. Refers to shortening the feedback cycle

“Live programming gives the programmer immediate feedback on the behavior of a program as it is edited, replacing the edit compile-debug cycle with a fluid programming experience.“

But only short feedback loops, but also to change the system behaviour from within, such as the LISP compiler reading and compiling the source code from inside a program.

In-place tool chains

The user should be able to edit their programs without installing additional tools or programs

a Unix shell script is just a series of commands saved into a text file

Meaning that the user is already accustomed to issuing those commands. A script is just grouping those commands.

Gives examples of end-user programming success stories: spreadsheets, SQL, browser dev tools,

Tags: end-user-programming, programming, extensibility, open-closed-principle, ocp, mofication, user, extension, unix, repl, spreadsheet, reflection, theory, history, review, sql, dev-tools, chasm, abstraction

Id: 4490792a-514b-11e9-9861-0242ac110006 Read: Thu, 28 Mar 2019 11:18:52 +0000

Why developers consider Agile development to be nonsense

This article explains how Agile development is apt and indicated for short-term software development, especially for contracting or consulting companies, where the client is external to the team.

Why it does not make as much sense in products/services where there is a leapfrog solution.

Don’t give the customer what they ask for; understand them, and revolutionize their world.

Tags: leapfrog-solution, google, agile, agile-development, comparison, project-management, client, consulting, management

Id: 9035ea3c-514f-11e9-9676-0242ac110006 Read: Thu, 28 Mar 2019 11:49:37 +0000

Why bother with What Three Words?

In this article, the author questions why using a closed protocol for translating geo-coordinates to words.

The author complains that it is masquerading a for-profit, closed algorithm as an open standard.

Also, that the GPS locations are drifting very quickly in some places, therefore the translated address changes, but the local address (e.g., 1 Wall Street), does not.

Tags: gps-drift, australia, open-standard, closed-standard, for-profit, protocol, open, closed, what-three-words, w3w, i18n, startup

Id: 960e6750-5202-11e9-bb40-0242ac110008 Read: Fri, 29 Mar 2019 09:11:07 +0000

Refactoring: split loop + loop/map equivalence

Feb 6, 2019 - 2 minute read - Comments - refactoringsplit-loopsplit-loop-refactoringloop-map-equivalencecodekotlinmultiparadigmfunctional-programmingfpobject-oriented-programmingobject-orientedoooop

We can combine the “Split loop” refactoring technique plus the “Loop / Map equivalence” when refactoring.

Given that it does not matter in which order we apply these operations, we can say that they have the associative property

Chart of the operations

Take the case of a loop doing two things. From there:

  • we can replace the loop for a map (including the two actions into a single map body)
  • we can split the loop into two loops

Take the case of two loops, doing one thing each. From there:

  • we can replace a loop for a map
  • we can replace both loops for maps

Take a map doing two things. From there:

  • we can split the map, into two maps, doing one thing each.

(We’re not specifying the inverse operations)

State diagram of the operations

Example

We want to print all substrings of a given string:

(State1: This uses a single loop, performing two actions)

fun printAllSubstrings(string: String){
  for (i in 0.rangeTo(string.length)) {
    val substring = string.substring(i)
    println(substring)
  }
}

From State1, we replace the loop for a map:

(State2: This uses a map, with two operations)

fun printAllSubstrings(string: String) {
    0.rangeTo(string.length).map {
        val substring = string.substring(it)
        println(substring)
    }
}

From State1, Refactor to split the loop:

(State3: This uses two loops, performing one action each)

fun printAllSubstrings(string: String){
  val substrings = mutableListOf<String>()
  for (i in 0.rangeTo(string.length)) {
    val substring = string.substring(i)
    substrings.add(substring)
  }
  for (substring in substrings) {
    println(substring)
  }
}

Collapse the first loop into a map:

(This uses a map and a loop)

fun printAllSubstrings(string: String) {
  for (substring in 0.rangeTo(string.length)
                     .map { string.substring(it) }) {
    println(substring)
  }
}

Extract the method to give it a name:

(This uses a map, a loop, and a method to explain the logic)

fun printAllSubstrings(string: String) {
  for (substring in allSubstrings(string)) {
    println(substring)
  }
}

private fun allSubstrings(string: String) = 
  0.rangeTo(string.length)
    .map { string.substring(it) }

Alternatively, use the method, with a map:

(This uses an explaining method, with a map)

fun printAllSubstrings(string: String) {
  allSubstrings(string)
    .map { println(it) }
}

private fun allSubstrings(string: String) = 
  0.rangeTo(string.length)
    .map { string.substring(it) }

Alternatively, from State3, we can also replace the loop for two maps:

(State4: This uses two maps)

fun printAllSubstrings(string: String){
  0.rangeTo(string.length)
    .map { string.substring(it) }
    .map { println(it) }
}

Self-Study in February 2019

Feb 1, 2019 - 3 minute read - Comments - self-study-aggregationfebruary2019acidaerospikeagileapaphyratul-adyaavailabilityawkawsbloatbrad-appletoncapcap-theoremcommitcommit-confcomparisonconsistencyconsistency-levelcpdatabasedirty-readdisenchantmentdocumentationdynamodbexecutable-documentationextreme-programmingfeedbackfuzzy-readgood-feedbackguidehelphonest-feedbackisolationjepsenjesuslclaura-lacarraleanlean-softwareliskovmakefilemicrosoftneil-greennikita-prokopovnon-repeatablepartitioningpaxospeoplepeople-managementpersonality-typephantomphantom-readpracticeprinciplequoterantread-committedread-uncommittedrepeatable-readserializabilityserializableslideslidesharesoftwarespanishspeedsql-databasestronger-serializabletonskytransactiontrickvaluexp

Amazon DynamoDB Transactions: How it Works

Explains how transactions work in DynamoDB

Tags: dynamodb, aws, help, transaction, serializable

Id: 7fb09cd4-2639-11e9-9377-0242ac110002 Read: Fri, 01 Feb 2019 15:53:20 +0000

Jepsen: Aerospike

I’ve read this analysis of Aerospike, that explains what kind of database it is, what CAP properties satisfies

Tags: cap, cap-theorem, jepsen, aphyr, aerospike, database, acid, ap, cp, consistency, availability, partitioning, paxos

Id: bd7151c6-2639-11e9-a38e-0242ac110002 Read: Fri, 01 Feb 2019 15:55:04 +0000

A Critique of ANSI SQL Isolation Levels

I’ve read this paper that explains the ANSI SQL isolation levels

Tags: non-repeatable, fuzzy-read, dirty-read, phantom, phantom-read, isolation, serializability, consistency, consistency, consistency-level, read-uncommitted, read-committed, repeatable-read, serializable, microsoft

Id: 01292b8c-263a-11e9-a7fe-0242ac110002 Read: Fri, 01 Feb 2019 15:56:58 +0000

Weak Consistency: A Generalized Theory and Optimistic Implementations for Distributed Transactions

An extended paper on ACID properties for SQL databases

Tags: liskov, atul-adya, stronger-serializable, consistency, consistency-level, isolation, database, sql-database, acid, transaction

Id: 4a1c6f7a-263a-11e9-8e08-0242ac110002 Read: Fri, 01 Feb 2019 15:59:00 +0000

No todo el mundo sabe o debe dar feedback

The author explains why some feedback is dangerous: either the way of giving it, or the message, or both.

In this case, she’s talking about the Commit Conf, but this is applicable to any situation

Para dar un buen feedback es importante:

  • Primero: agradecer el esfuerzo por la charla.
  • Segundo: resaltar algo positivo de ella. Seguro que algo cumple.
  • Tercero: decir cómo mejorarías un aspecto
  • Último: volver a dar las gracias o decir una frase buena que motive.

Dar un mal feedback es muy fácil:

  • Primero: no leerte la descripción ni el nivel de la charla
  • Segundo: te cabreas porque no es lo esperado y dudabas entre esa y otra charla
  • Tercero: dices lo que no te ha gustado sin rodeos.
  • Cuarto: además asumes cosas que no ha hecho y las escribes. Igual que yo he hecho en el Primero y Segundo.
  • Quinto: si además dices algo faltoso gana puntos.
  • Sexto: Utilizas esa tónica destructiva en todos.

Tags: laura-lacarra, commit, commit-conf, feedback, good-feedback, honest-feedback, spanish

Id: 20d8145e-3a92-11e9-8023-0242ac110003 Read: Wed, 27 Feb 2019 13:18:10 +0000

How to Deal with Difficult People on Software Projects

I’ve read this guide on dealing with difficult people.

There are many (48) personality types, including these types:

  • Product Managers
  • Designers
  • Project Managers
  • Development Managers
  • Developers
  • Quality Assurance

Tags: people, people-management, personality-type, guide, neil-green

Id: 95554892-3a92-11e9-9bbf-0242ac110003 Read: Wed, 27 Feb 2019 13:21:25 +0000

Software disenchantment

I’ve read this article about somebody disenchanted with the current state of the art of software: slow, bloated, not better than 10 years ago, or faster.

Tags: nikita-prokopov, bloat, rant, disenchantment, tonsky, comparison, speed, software

Id: 0078d58a-3a93-11e9-8f23-0242ac110003 Read: Wed, 27 Feb 2019 13:24:25 +0000

The Values and Principles of Agile Software Development

I’ve read the slides of this presentation by Brad Appleton, on Values, Principles, and Practices in an Agile environment.

Plenty of good quotes

Tags: brad-appleton, slideshare, slide, agile, practice, principle, value, xp, extreme-programming, quote, lean-software, lean

Id: 42cdde80-3a93-11e9-814c-0242ac110003 Read: Wed, 27 Feb 2019 13:26:16 +0000

Makefiles como dejar de memorizar comandos en docker – Developer Vago

I’ve discovered a new technique for Makefiles:\n\nUsing a common format (a DSL, in fact) to document the goal, then a new goal ‘help’ to print that documentation.

.PHONY: help
help: ## Print this help.
  @grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | awk 'BEGIN {FS = \":.*?## \"}; {printf \"\033[36m%-20s\033[0m %s\n\", $$1, $$2}'

when you run make help, then

Print this help.

Tags: makefile, jesuslc, documentation, executable-documentation, awk, trick, help

Id: d6a4b78c-3a93-11e9-88d7-0242ac110003 Read: Wed, 27 Feb 2019 13:30:24 +0000

Self-Study in January 2019

Jan 1, 2019 - 1 minute read - Comments - self-study-aggregationjanuary2019bookcycleebookframeworkgetting-things-donegtdlibrarymanagementmental-frameworkpersonal-productivitypomodoropomodoro-techniqueproductivitysearchtime-managementwork-cycle

Work cycles

I’ve read this Work Cycle framework to be more productive with your daily routine.

Suggests an alternative to Pomodoro technique, in which you are to write down the contents of the goal, then split in small chunks (periods) of time to complete the individual tasks, then debrief at the end of the period and at the end of the cycle.

An analogy could be a double-loop Pomodoro technique for tasks.

Tags: pomodoro, pomodoro-technique, framework, management, productivity, personal-productivity, gtd, getting-things-done, work-cycle, cycle, time-management, mental-framework

Id: f280c496-0df2-11e9-bf65-0242ac110002 Read: Tue, 01 Jan 2019 18:27:51 +0000

World Cat

Site to find books in public libraries

Tags: book, search, library, ebook

Id: 15ca63e4-0df8-11e9-b145-0242ac110002 Read: Tue, 01 Jan 2019 19:04:38 +0000

Books read in 2018Q4

Dec 31, 2018 - 9 minute read - Comments - bookreading2018Q4self-studyreading-club

Read this quarter:

Note: re+read means I’m re-reading this book. The (+) stands for one-or-more times, as in the regexes.

  • Como ganar amigos e influir sobre las personas; Carnegie (+)
  • Oliver Twist; Dickens
  • Building evolutionary architecture; Ford, Parsons
  • Selfie: How We Became So Self-Obsessed and What It’s Doing To Us; Storr. Just chapter 1: The dying self
  • Sota la cistella; Gasol

Como ganar amigos e influir sobre las personas; Carnegie (+)

I’ve re-read this classic book (How to win friends and influence people), by Carnegie.

Explains a few tricks on communication and leadership, such as:

  • The most important name to somebody is their own

Oliver Twist; Dickens

I’ve read this classic novel by Dickens, to try to understand the character of Oliver Twist, his adventures and misadventures.

I was interested in grokking how it compares to ‘El Lazarillo de Tormes’, a previous Spanish novel.

Building evolutionary architecture; Ford, Parsons

I’ve read this book on software architecture. On how a previous definition of architecture (‘Architecture is what needs to be defined upfront and/or is difficult to change’) is no longer valid and we should strive to approach ‘evolutionary architecture’, where -ilities (features) of the system are easier to change, where architecture changes to accommodate business requirements and where systems are designed with -ilities (features) in mind.

Selfie: How We Became So Self-Obsessed and What It’s Doing To Us; Storr

I’ve just read the chapter 1: The dying self

I’ve read this chapter relating the perfectionism with suicide.

Explains many stories of attempted or committed suicides, giving some insight into them and trying to define a pattern

I got interested in it by reading this article: Improving Ourselves to Death (from newyorker.com)

Sota la cistella; Gasol

I’ve read this book by pau Gasol on his experiences playing basketball professionally, with regards to leadership, motivation, career management, etc

One takeaway is ‘the important thing is not to reach there, but to stay there’.

He explains part of his professional successes, and failures as well. How some failures allowed him to progress further in his career, how he reached levels that he only dreamed in the past, how important it is to have a goal and work towards it.

backlog (partially sorted):

  • unsorted V
  • The Machine That Changed the World: The Story of Lean Production
  • Haskell Programming
  • Software Architecture in Practice
  • The five disfunctions of a team: a leadership fable; Lencioni
  • lucha por la desigualdad, la; Pontón; non-technical
  • psicología del dinero, la; Hammond; non-technical
  • Invirtiendo a largo plazo; García Paramés; non-technical, finance
  • Well-Grounded Java Developer, the; own-it
  • Learn You a Haskell for Great Good!; own-it
  • camino al 18J, el; Payne; non-technical
  • Cartas desde la revolución bolchevique; Sadoul; non-technical
  • Java Performance: The Definitive Guide
  • Why programmers work at night
  • Shogun: The Life of Tokugawa Ieyasu; Sadler; non-technical
  • Scrum and XP from the trenches, 2nd edition;
  • Els jueus i Catalunya; Villatoro; non-technical
  • El problema de los tres cuerpos; Liu; non-technical
  • Amazon Web Services in Action; own-it
  • Clojure Programming - Practical Lisp for the Java World
  • Mature optimization
  • XUnit Test Patterns
  • Let Over Lambda
  • The Haskell Road to Logic, Math and Programming
  • Types and Programming Languages
  • Fundamentals of Object-oriented Design in UML
  • Clojure for the brave and true
  • How to Solve It: A New Aspect of Mathematical Method
  • Conceptual Mathematics: A First Introduction to Categories
  • Understanding Computation: From Simple Machines to Impossible Programs
  • Programming in Haskell
  • Programming Languages: Application and Interpretation
  • Doing Math with Python
  • Perfect Software: And Other Illusions about Testing
  • Computability and Complexity - From a Programming Perspective
  • Thinking Forth: a language and philosophy for solving problems
  • Concepts, Techniques, and Models of Computer Programming
  • Bridging the Communication Gap; Adzic
  • Specification by Example; Adzic
  • Cucumber book, the; Adzic
  • Software Architecture for Developers; Brown
  • Object Design: Roles, Responsibilities, and Collaborations
  • RESTful Web APIs
  • RESTful Web Services Cookbook
  • Building Maintainable Software
  • Serverless - Patterns of Modern Application Design Using Microservices (Amazon Web Services Edition)
  • A Pattern Language; Alexander
  • Types and Programming Languages, TAPL; Pierce; own-it
  • Speed Reading Book: Read More, Learn More, Achieve More, the; Buzan
  • Cómo crear mapas mentales (Crecimiento personal); Buzan
  • First things first; Covey
  • What’s best next; Perman
  • problems of philosophy, the; Russell
  • Requiem for the American dream; Chomsky
  • sun also rises, the; Hemingway
  • travels, the; Polo; non-technical
  • Homo Deus: A Brief History of Tomorrow; Harari; non-technical
  • Books by Aristotle; non-technical
  • Books by Plato; non-technical
  • Books by Descartes; non-technical
  • The idea of culture; Eagleton; non-technical
  • Hereditary Intelligence; Galton; non-technical
  • Lean Software Development: An Agile Toolkit; Poppendieck (+)
  • Chaos Monkeys: Obscene Fortune and Random Failure; Garcia Martinez
  • Implementing Lean Software Development: From Concept to Cash; Poppendieck
  • Joel on Software; Spolsky
  • Death March; Yourdon
  • Psychology of Computer Programming, The; Weinberg
  • Introduction to General Systems Thinking; Weinberg
  • Lao Tzu : Tao Te Ching : A Book About the Way and the Power of the Way; Tzu, Le Guin; non-technical
  • Gay Science, the; Nietzsche; non-technical
  • Being Geek; Lopp
  • Finance for Freelancers; Retallick; non-technical, finance
  • Object-oriented software engineering: a use case driven approach; Jacobson
  • Patterns of Enterprise Application Architecture; Fowler; own-it
  • Romeo y Julieta; Shakespeare; non-technical
  • Computer Systems: A Programmer’s Perspective; Bryant, O’Hallaron
  • My Journey to Lhasa: The Classic Story of the Only Western Woman Who Succeeded in Entering the Forbidden City; David-Néel; non-technical
  • Cathedral and the bazaar, the ; Raymond
  • Coding dojo handbook, the; Bache; own-it
  • Making software; Oram and Wilson; own-it
  • Code complete; McConnell; own-it
  • Soft skills; Sonmez; own-it
  • DSLs in action; Ghosh; own-it
  • Purely functional data structures; Okasaki; own-it
  • Working effectively with unit tests; Fields (+); own-it
  • First Nazi, the; Ludendorff; non-technical
  • Greatest story ever told … so far; Krauss; non-technical
  • Master algorithm, the; Domingos; non-technical
  • Invention of Science, the; Wootton; non-technical
  • Tesla: Inventor of the electrical age; Bernard Carlson; non-technical
  • Psychology in minutes; Weeks; non-technical
  • Alan Turing: The Enigma; Hodges; non-technical
  • How to think more about sex; de Botton; non-technical
  • Piccolo manuale di persuasione; Taylor; non-technical
  • arte de la guerra, el; Sun Tzu; non-technical, own-it
  • Piccolo manuale di leadership Confuciana; Adair; non-technical
  • How to Stop Worrying and Start Living; Carnegie; non-technical
  • Uomo - Guida allo stile; Roetzel; non-technical
  • Unwritten Laws of Engineering: Revised and Updated Edition; King
  • Test-Driven JavaScript Development (Developer’s Library); Johansen
  • Test Driven Development: By Example; Beck
  • Arquitectura Java JPA Domain Driven Design; Alvárez, Peláez
  • End of loyalty, the; Wartzman; non-technical
  • Basic Economics; Sowell; non-technical
  • Introduction to Economic Analysis; McAfee; non-technical
  • Patterns of Software; Gabriel
  • Coders at work; Seibel
  • Clean architecture; Martin
  • How to Be a Stoic: Using Ancient Philosophy to Live a Modern Life; Pigliucci; non-technical
  • Introduction to Object-Oriented Programming, an; Budd
  • Gafas de la felicidad, las; Santandreu; non-technical
  • Ser feliz en Alaska; Santandreu; own-it, non-technical
  • Mochila para el universo, una; Punset; non-technical
  • Gods themselves, the; Asimov; non-technical
  • Panamá papers, the; Obermayer, Obermaier; non-technical
  • Originals; Grant; non-technical
  • Optimism over despair; Chomsky; non-technical
  • SCIENCE OF BREATH: A Practical Guide; Ballentine, Hymes; non-technical
  • Yoga Explained: A New Step-by-step Approach to Understanding and Practising Yoga; Mehta,‎ Arjunwadkar; non-technical
  • Wanderlust: A Modern Yogi’s Guide to Discovering Your Best Self; Krasno; non-technical
  • How to Think About Money; Clements; non-technical, finance
  • By Way of Deception; Ostrovsky; non-technical
  • Printemps des sayanim, le; Cohen; own-it, non-technical
  • Deep work; Newport; non-technical, own-it
  • Hooked: How to Build Habit-Forming Products; Eyal, Hoover; non-technical
  • Irresistible: The Rise of Addictive Technology and the Business of Keeping Us Hooked; Alter; non-technical
  • The Attention Merchants: The Epic Scramble to Get Inside Our Heads; Wu; non-technical
  • Willpower: Why Self-Control is The Secret to Success; Baumeister, Tierney; non-technical
  • Principles of Psychology, the; James; own-it, non-technical
  • Our mutual friend; Dickens; non-technical
  • Crucial Conversations: Tools for Talking When Stakes Are High, Second Edition; Patterson, Grenny, McMillan, Switzler; non-technical
  • Amusing Ourselves to Death - Public Discourse in the Age of Show Business; Postman; non-technical
  • Mastery; Greene; non-technical, own-it
  • Silence in the age of noise; Kagge; non-technical
  • Functional programming simplified; Alexander; own-it
  • Your money or your life; Dominguez, Robin; non-technical, finance
  • Batalla del Ebro, la; Reverte; non-technical
  • Historia de la guerra civil española; Rojo; non-technical
  • Lucha por el poder, la; Evans; non-technical
  • Revolución rusa, la; Pipes; non-technical
  • Holocausto, el; Rees; non-technical
  • Martín Lutero, renegado y Profeta; Roper; non-technical
  • Siglo de la revolución, el ; Fontana; non-technical
  • Història de la revolución rusa; Trotsky; non-technical
  • Dispossessed, the; Le Guin; non-technical
  • Left hand of darkness; Le Guin; non-technical
  • Lathe of heaven; Le Guin; non-technical
  • https://www.amazon.com/Schopenhauer-Cure-Novel-Irvin-Yalom/dp/0060938102/
  • https://www.amazon.com/How-Schopenhauer-Through-Mid-Life-Crisis-ebook/dp/B00QXNB5PC/
  • Books in general – Epstein
  • Affluent society, the; Galbraith; non-technical, finance
  • Philosophy of the Buddha; Bahm; non-technical
  • Tribe of mentors; guillem, non-technical, own-it
  • 5 dysfunctions of a team; non-technical
  • Ziglar’s Top Performance; non-technical
  • Pragmatic Programmer (+)
  • High Output Management; Grove; non-technical
  • First Break All the Rules; non-technical, guillem
  • Managing for happiness; Appelo; non-technical
  • Meditations; Marcus Aurelius; non-technical, own-it
  • How to be a stoic - Pugliucci; non-technical
  • Why budism is true; Wright; non-technical
  • 7 hábitos de la gente altamente productiva
  • art of readable code; guillem
  • Domain modeling made functional; guillem
  • Sketchbook handbook; guillem, own-it
  • Agile samurai, the; guillem
  • Miracle of Mindfulness, the; Hanh; non-technical, own-it
  • No mud, no lotus: The Art of Transforming Suffering; Hahn; non-technical
  • Lean Architecture: for Agile Software Development; Coplien, Bjørnvig
  • Agile IT Organization Design: For Digital Transformation and Continuous Delivery; Sriram Narayan
  • Philosophy of Software Design, a; Ousterhout
  • Hope in the Dark; Solnit
  • Agile!: The Good, the Hype and the Ugly; Meyer

unfinished (unsorted):

  • Working Effectively with Legacy Code (+); Feathers; own-it
  • Nonviolent communication (+); Rosenberg; own-it, non-technical
  • Introduction to Buddhism: Teachings, History and Practices, an; Harvey; non-technical, own-it
  • Effective Java; Bloch; own-it
  • Functional Programming Patterns in Scala and Clojure; own-it
  • Release It! - Design and Deploy Production-Ready Software; own-it
  • Refactoring (+); Fowler; own-it
  • Leprechauns of Software Engineering (+), the; Bossavit; own-it
  • Domain-Driven Design: Tackling Complexity in the Heart of Software; Vernon (+); own-it
  • Pragmatic Thinking and Learning: Refactor Your Wetware; own-it
  • Readings in Database Systems, 5th Edition; own-it
  • Structure and Interpretation of Computer Programs (SICP); Abelson, Sussmann, Sussmann; own-it
  • La Sociedad De Coste Marginal Cero (Estado y Sociedad); Rifkin; non-technical
  • Odisea; Homero; non-technical
  • Switch: How to Change Things When Change Is Hard; Heath, Heath; own-it, non-technical
  • Como leer un libro; Adler, van Doren; non-technical, own-it

next (2):

  • Who rules the world?; Chomsky; non-technical
  • Mundo nuevo, ahora, un; Tolle; own-it, non-technical
  • Continuous Delivery; Humble, Farley; own-it
  • Hombre multiorgásmico, el; Chía, Arava; own-it, non-technical

wip (2):

  • Thinking fast and slow; Kahneman; non-technical
  • Java Concurrency in Practice (JCIP); Goetz
  • Hombre en busca del sentido, el; Frankl; own-it, non-technical

done:

  • Como ganar amigos e influir sobre las personas; Carnegie (+); own-it, guillem
  • Oliver Twist; Dickens; own-it, non-technical
  • Building evolutionary architecture; Ford, Parsons; own-it
  • Selfie: How We Became So Self-Obsessed and What It’s Doing To Us; Storr. Just chapter 1: The dying self; own-it, non-technical
  • Sota la cistella; Gasol; own-it, non-technical

rejected:

  • Stanger in a strange land; Heinlein; own-it, non-technical