Bookmark collect, February 2016 #2

This sticks out, so far :) Avdi Grimm's article about the law of demeter, reading it including all commetsn until the end will take a bit of time but is exactly what explains a lot of things that imho we do wrong in lots of software we write, I am working on improving myself around it. For the completeness here is the paper initially laying out the law of demeter.

Various

• HTTP2 spec
• HTTP2 FAQs, answers all my questions about it
• "Managing Side Effects In React + Redux Using Sagas"
• "Rediscovering the Joy of Design"
• I should read this "The Top Mistakes Developers Make Using Ember & Rails"

Software crafting

• From the C2 wiki: Cyclomatic complexity
• "Distributed code review system for Git repos"
• It was just open in one tab and is always a good read, the 8thlight blog
• Uncle Bob: "Why is Estimating so Hard?"
• Simple rules for architecturing software, by Uncle Bob
• "spaCy is a library for industrial-strength natural language processing"
• A subtitle is: "Most Developers Don’t Know How to Test"
• High velocity team
• "Q&A with Vasco Duarte on the #NoEstimates Book"
• Book: Fifty Quick Ideas To Improve Your User Stories
• Avdi Grimm writes good stuff
• Book about requirements and user stories
• A post triggered by a tweet "Well Crafted Code, Quality, Speed and Budget"
• "Does test-driven development (TDD) really improve software quality?"

Ruby

• Some looking under the hood of Ruby about unless, very insightful to me.
• How to get most out of #rails logging
• "How Ruby Executes Your Code"
• A timer faker we use in our tests
• Book: Programming Ruby, The Pragmatic Programmer's Guide
• Very helpful: delegates
• Probably had that already, the Ruby QuickRef