🔖 Bookmarks

Optimize your Ruby on Rails application's performance by identifying and rectifying missing or inefficient Postgresql indexes through insightful SQL queries.

Within almost 15 years of our history we collected a quite vast collection of tools and techniques that help us to provide the best performance to our clients projects.

Better Specs is a collection of best practices developers learned while testing apps that you can use to improve your coding skills, or simply for inspiration.

In this article, I break down the difference between system specs and feature specs in RSpec and Rails, and walk you through refactoring your feature specs to system specs.

The only Ruby on Rails newsletter you will every need!

A first look at Strada, the last missing piece of Hotwire. Let's explore how it unlocks native components driven by the web in Turbo Native apps.

This article explores a dynamic nav component I built using the current_page? helper method, plus Rails' conditional class helpers. The result? A simple, dynamic navbar component, with different styling based on current page. Plus I threw in the ViewComponent version too 😉

This week I want to tell you about the form_with Rails helper. It was introduced in Rails 5.1, and the goal of this helper was to unify the form_for and the form_tag helpers. form_for requires a model instance or a scope and puts the attributes into a hash, so usually when you needed a form in the past where you didn’t want to put them scoped into a hash, you used form_tag.

Introduction Postgres queue tech is a thing of beauty, but far from mainstream. Its relative obscurity is partially attributable to the cargo cult of “scale”. The scalability cult has decreed that there are several queue technologies with greater “scalability” than Postgres, and for that reason alone, Postgres isn’t suitably scalable for anyone’s queueing needs. The cult of scalability would rather we build applications that scale beyond our wildest dreams than ones that solve real problems beyond our wildest dreams.

This is an updated version of the post I wrote about MRKS in the past.

Here’s an important distinction to make in life.

Introduction Hey there, fellow web adventurers! 😄 Building web applications can be a wild...

How I used artificial intelligence and async programming to transform interesting conversations into blog posts.

Syntactical sugar to avoid comparison operators

Career changers have a lot more to offer than meets the eye—especially in tech!

How to plan and execute the refactoring of you Ruby application

Choosing the right web framework for your project is a crucial decision. In this article, we'll take a look at Ruby on Rails and three pros and cons for the framework from a developer's perspective.

Building out a basic Ruby API client using the http gem, tested with webmock.

Recently for RelationKit.io I wanted to build a system to help show other users on the same account if another person is on the same page as them to avoid embarrassing duplicate replies on support tickets. While thinking about how to build this, I wondered if I could use Turbo to build it without any custom JavaScript and the answer is a resounding yes.

How to help your team discover the right product using your technical know-how.

Are you tired of writing clean, maintainable code? Do you yearn for spaghetti code that's...

You don’t need a sophisticated caching mechanism to improve your application’s performance. All you need is a basic understanding of the HTTP specification.

This week I will show you how to make dependent dropdowns with Hotwire! I will use a toy app as an example. This app will have a page where addresses can be created. The address will consist of a country, a state, a city, and a postcode. Except for the postcode, we will have a list of options coming from the database and when the user selects the country, we load the states for the selected option. When the user selects the state we will load the cities in that state. Let’s start by generating a Rails app, the necessary models and a scaffold for the address:

Upgrade your Ruby or Rails application confidently, even with low test coverage, by implementing the strategies and best practices outlined in this blog post.

Here is one strategy to move a client from providing your team with a list of requirements to working on the root problem together.