Ruby Weekly
Issue 271 — November 5, 2015
No DSLs, broken up into components and plugins, and the end results look slick.

John Backus
A good introduction to using mutation testing in Ruby using mutant. Mutation testing shows you which changes don’t break your tests, thus highlighting which of your tests are not up to par.

Christophe Limpalair
He's definitely not a fan of commented out code.  Sponsored
Line-by-line coverage reports stats help spot gaps where bugs hide. Get notified when coverage changes on your projects. Can't use cloud services? Check out Coveralls Enterprise. Always be free for open-source, and we are looking for skilled devs to join the revolution.

Owen Ou, an engineer at Heroku, shares the story behind how they upgraded some legacy production Ruby code from ActiveRecord 2.3.18 to 4.2.4.

Starr Horne
A simple look at the journey of a program as it’s lexed, parsed and compiled into bytecode that MRI’s VM can then execute.

Rubinius, Inc. has announced its first Rubinius-based product, a tool for analyzing the performance and structure of live, production Ruby apps.

Michal Kulesza
No, it’s not the same as a complete, designed professional service, but grabbing and managing your own metrics may none-the-less be useful to do.


In brief