Ruby Weekly
Issue 335 — February 9, 2017
Kjell-Magne Øierud
Rather than saving the current state of a system, you save events. The state of the system at any point in time can then be rebuilt by replaying these events.

Richard Schneeman
From last year, several handy tips on figuring out where methods are defined, opening a project’s dependencies, returning a ‘debugged’ gem to its pristine version, and more.

Sergey Dolganov
A look at the ways in which you could judge Ruby gems based on their metadata, and how an attempt to do so led to a new site called Ossert.

Bugsnag  Sponsored
The most practical way to improve software quality for your users. Automatically detect errors, and get the diagnostic data needed to reproduce and fix critical bugs. Getting started is easy with Bugsnag’s Ruby gem. Start your free trial.


Brian J Cardiff
An hour long Google tech talk about Crystal, a Ruby-esque language with type inference and native code compilation. Warning: audio quality isn’t great.

Brad Grzesiak
An explanation of the benefits of having a Maybe type and why it would never work in Ruby.

Andrei Beliankou and Contributors
An epic list of practical, Ruby natural language processing resources from folks that work with it every day.

Tomas Valent
“Think twice before using PUT in your routes,” says Tomas. When it comes to HTTP verbs if you PUT your faith in the wrong spot you may have to PATCH your app later.


In brief