5 Things to Read

• Future JavaScript: what is still missing?
  • Since ES6, released in 2015, ECMA has adopted a policy of yearly major releases for Javascript. To keep up with the whole package every year is hard and wearying, specially if you don’t use the language often or deeply. Axel Rauschmayer has one of the best blogs on Javascript, and has listed some features in the road of the Javascript language, from capacity of comparing values by value to proposals on pipeline operators.
• How do you review test automation code?
  • Thread on the Ministry of Testing Club on how to review automation code. Here are my two cents on the discussion
• How to teach Git
  • Although I find that hands-on, trying-and-error learning is crucial, images and diagrams are great to understand algorithms and tools - specially when they are built under the Unix mindset of modularity. Rachel Carmena does a great work on diagramming basic Git commands here. Bonus: In my first two months of using Git, I struggled due lack of understanding on how things work. Then I saw this presentation by Scott Chacon and life simply became better.
• Applying the Prime Directive beyond the retrospective
  • Norm Kerth said “Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”; and this goes well beyond the fortnightly meeting we do.
• Can’t U See
  • I love finding small UI problems: Misalignments, inconsistencies in fonts and sizes, typos, etc. This “game” gives you two similar images and ask you to pick the correct one. Real testing fun :D