We love reading, watching, and listening in order to constantly update our skills and learn new perspectives. Here are some of the exciting pieces we learned from this month.
Digging Into Turbo with Ruby on Rails 7
This article provides a nice intro to Turbo. The author goes over the high points of frames and streams, and gets you up and running quickly with a simple To Do app.
Minitest vs. RSpec in Rails
At The Gnar, the vast majority of the rails applications we build are tested with RSpec. However, it’s a good practice to periodically evaluate what other tools are available, and besides, it’s fun to play with new tools. This article includes a rundown of different testing strategies, an introduction to TDD/BDD, and provides a comprehensive comparison between Minitest and RSpec from configuration through execution. RSpec still has our 🧡.
VISIWIG: click + page graphics
If you have a website but you’re not at the stage where you’d like to hire your own graphic designer, there are a lot of tools and libraries that can help spice up your content with unique graphics and backgrounds. Visiwig provides tools for generating basic background patterns, as well as a set of high-quality icons. And they're free. The same creator also created https://www.svgbackgrounds.com, which provides even more free SVG patterns.
You’ve heard good things about Typescript. But Hypescript lets you write Typescript…inside of Typescript. It’s a lightweight implementation of typescript available from within Typescript’s own Type Checking System. It’s Inception. Typeception. DDUUUUUUNNNNNN.
How to Track Down Memory Leaks in Ruby
Memory leaks - hopefully you never run into this problem, but if when you do this article might come in handy! This is the first in a series of posts about managing memory leaks in Ruby. This post covers how memory is allocated in Ruby (including improvements in Ruby 3.1) as well as garbage collection. It includes an example that demonstrates how to create your very own memory leak, and how to use the
GarbageCollection) module to uncover memory leaks in Ruby code. TL;DR - use an Application Performance Monitoring (APM) tool in prod.