Systems | Development | Analytics | API | Testing

Imagine your Node.js app is like a super-fast sports car. The "loader" is its transmission — that crucial part that gets the engine's power to the wheels, making everything run smoothly. If that transmission starts acting up, your speedy app will just sputter and stop. So, it's simple: a good loader means your app flies, a bad one means it's stuck in neutral. In this post, we'll explore how to improve your Node.js app's performance with its loader. But first, what exactly is this loader thing?

In part one of this series, we walked through how to use Showcase in a Rails app. It's now time to read some Ruby code written by experienced Rails developers. To do this without getting lost, we'll choose one feature of the showcase engine and analyze how it works: rendering a preview of a component. Let's get started!

When you build Elixir applications, you'll likely encounter scenarios where you need to handle large datasets efficiently. Whether you're importing user data from a CSV file, updating thousands of product prices, or synchronizing data from external APIs, performing operations one record at a time can quickly become a performance bottleneck. In this two-part tutorial, we'll start by exploring Ecto's powerful batch update and advanced insert capabilities for handling bulk data operations.

Reading a lot of code from very senior engineers is probably one of the best ways to level up as a Ruby on Rails developer. By doing so, we can learn new tips and techniques that we can reuse in our jobs. Thanks to open source, we can read code written by the best developers from all over the world, and for free! However, reading code from a Ruby gem or a Rails engine for the first time without being guided can be daunting. There are so many files; how do we even know where to start?

In part one of this series, we explored how Angular Signals shift the reactive model away from the RxJS-centric approach we’ve relied on for years. We walked through the core API signal(), computed(), and effect() primitives, and demonstrated how they simplify state management by removing the need for subscriptions, teardown logic, and deeply nested observables. We also introduced a minimalist CartService that held cart items in a private signal and exposed a computed total price.