How do you get multithreaded code right? The first step is to see if you can avoid using threads at all! The other day I was adapting an email course …
Global settings can cause havoc when threads are introduced. Learn when and how to use Ruby's thread-local variables instead.
In which we put some fears about thread-safety to the test, and to rest.
In this episode, we'll move logging into a dedicated, low-priority thread.
In previous episodes, we got the Tapas::Queue class under test, using a couple of different thread-testing techniques. Now that it has tests, it's time to refactor. The steps of this …
Today's episode introduces the concept of thread-local variables, and shows how they can be put to use in an ActiveRecord-like library.
In this episode we'll explore a novel technique for testing multithreaded code. The lockstep library can be found here: https://github.com/avdi/lockstep
Working with threads is hard enough, but getting them under test is even trickier. In this episode we start to look at techniques for verifying the logic of multithreaded code.
Today's is another threading episode. This time around, we tackle the subject of "atomicity", and learn about the false assumption at the root of many threading bugs.
Today we learn about the concept of a "recursive mutex" as we help a turtle-racing league update their software systems.