The strange case of Wisper and Ruby blocks behaving like Procs

Here’s a good one that took a few hours to debug.

TLDR

Lesson of the day: do not return out of a wisper ‘on’ block — doing so will
terminate early and other listeners will…

Using blocks in Rails views

I like using blocks / closures in Ruby as they give the pattern to extract “around” actions. As in you want to execute an some arbitrary lines of code (the block) but make sure that what happens before and after are consistent.

Sidekiq Pro — Programatically get status of all batches

Sidekiq Pro comes with a nice web interface for managing your batch jobs, but here at Reverb we’re never satisfied with nice web interfaces :)

Five quick ways to think about code separation

Here are some concepts to keep in mind while refactoring. Some of these have overlap but they often can be helpful in deciding where to draw boundaries between classes.

1. Functional/Immutable vs Imperative/Mutating State

A Simple Swift Closure

One of the things I like about Swift is the concise code, especially when it comes to working with closures. Take this example for instance:

Let’s say we’re trying to create a guitar using the make and model.