Connecting thoughts

The most important part of making OpenAI’s batch processing API work in the real world is building a reliable polling system. This post explains why that’s necessary, and what else you’ll need to handle: token limits, partial failures, and retries.

After saving millions of records in SolidTelemetry, a database-backed OpenTelemetry implementation for Rails apps, we could see how the performance of a page degraded to the point of unusability. Discover how we made the page 22x faster.

Why we choose Ruby on Rails for intelligent applications development and how Rails helps us strategically integrate and try out the latest improvements in the AI field.

A recap of the Ruby Argentina meetup in Buenos Aires on May 14, 2025: Rails multi-tenancy, Service Objects, networking & community.

On March 12th, another Ruby Argentina meetup occurred. We learned new things, met new people, and had some fun. Here’s a recap.

“Let’s talk about” is a space where anyone in the company can pitch a topic, share it with the team, and help expand everyone’s knowledge. In this post, Diego shares a review of trusted sites that he uses to inquire into how the CSS rules work.

“Let’s talk about” is a space where anyone in the company can pitch a topic, share it with the team, and help expand everyone’s knowledge. In this post, Agustin and Lucas share their experience with GraphQL.

Welcome to the fifth issue of “This week in #devs”, a series of posts where we share articles, thoughts, and conversations that happen in our #devs channel on Slack.

Tree structures are a common way of organizing hierarchical data. In this post, we’ll explore existing solutions for Ruby on Rails, their benefits, drawbacks, and when to use them.

Welcome to the fourth issue of “This week in #devs”, a series of posts where we share articles, thoughts, and conversations that happen in our #devs channel on Slack.

Welcome to the third issue of “This week in #devs”, a series of posts where we share articles, thoughts, and conversations that happen in our #devs channel on Slack.

Welcome to the second issue of “This week in #devs”, a series of posts where we share articles, thoughts, and conversations that happen in our #devs channel on Slack.

This week we had to refactor a feature in one of the Ruby on Rails apps we’re maintaining. While at it, we discovered it was leaking memory, making the memory usage ramp up exponentially. With our expertise and the help of some tools, we were able to identify the root cause and fix the issue. Read on to learn more about how we approached this problem.

Over the last couple of months, I’ve been investing a lot of time in improving my testing skills. I spent most of this time in going back to the basics, trying to start from scratch with every little concept one takes for granted. Trying to see everything through a child’s eyes. And today I’m rediscovering fixtures.

In our last couple of posts, we’ve been reviewing common problems with long-living RSpec test suites and contrasting them against Minitest and the four-phase testing strategy. There are situations where migrating to Minitest is safer and possible, but what can we do if we are still using RSpec and changing it is not an option?

This sentence is wrong but funny. Minitest has always been great. In our last post, a situation made me think if I should be critical about how I test (and testing in general) and if I should do something about it. This is what happened next.

Delayed Job doesn’t have a mechanism for defining unique jobs. Enqueing a time-consuming or resource-intensive job multiple times could be harmful if not treated accordingly. Introducing Delayed::UniqueJob, a Ruby gem for defining unique jobs in Delayed Job.

I have been fascinated by Deno’s remote import since I discovered it. Experiment with me on how to make a remote require for Ruby based on Deno’s remote import.

We will explore Ruby’s division behavior and analyze several alternatives to obtain a true division.

In Flutter, dialogs don’t automatically share the context with the parent widget. We found out while implementing providers. Learn how to solve the problem.

Even though our primary focus is Ruby on Rails, we’re developing one Flutter application. In this project, we implemented a Skeleton Screen to enhance the app’s professional appearance during data loading. What is a Skeleton Screen and how did we implement one?

Ruby on Rails remains a great framework for developing web applications. Thanks to its maturity and philosophy, one can build MVPs in a fast, efficient, and scalable way. Discover why Rails continues to be a great and influential framework to this day.

For years we had to manually compare values in our validations. Rails 7 added the comparison validator to ActiveModel. Read on and discover, as we just did, how it works.

This is one of the most frequently asked questions from people who want to build an MVP with Ruby on Rails.

Moving your functions from a component to a separate file can improve readability and organization, but what happens when the data you need is outside the scope? In this article I will show you how I solved this problem with function currying.

On 14th September, another la_plata.rb meetup occurred. We had some fun and learned some new things. Here’s a recap.

APIs allow us to communicate with third-party software in order to use their services and data. In today’s software, it’s almost impossible not needing to use one, one way or another. What if they are hostile?

We’ve been using the audited gem for a couple of projects, but the lack of a built-in view to display the changes challenged us to write our engine. We are happy to introduce audited-ui.

Quality Assurance takes a key role in software development. In this post, we’ll share our Quality Assurance process that allows us to deliver quality software.

Strong Parameters are typically used in Ruby on Rails for mass assignments, but in this article, we explore an additional use for this feature.

Service objects is a Ruby on Rails pattern widely used. In this post, I’ll show you one example I stumbled upon recently. What’s wrong with it and how did we fix it?

Nowadays, technology is evolving at an unprecedented rate, presenting us with new challenges and opportunities. One challenge is adapting to new architectures, and in this post, we will explore how we did QA Automation on a serverless architecture.

Slider panels are widely used nowadays. In this post, we’ll build a fully functional custom React slider panel with Tailwind. Ideal for overlay menus, navigation, content lists, or even forms or configuration panels!

Overcomplicated props, ingrowing learning curves, and eventual technical debts are symptoms that appear as new requirements emerge on a project. Design Systems evolve outgrowing our components, leading toward their end. How can we ensure that our components thrive against the design challenges we encounter daily?

Last week we published the case study of one of our first projects. After 10 years in the archive, I found and brought this old Ruby on Rails 4.0 application back to life.

Finding a good balance between design and development is one key aspect to take into account while developing an MVP. Visually appealing products have a bigger impact on the market than one built from a template. But, is it the right choice for your project?

Build a custom React slider panel with Tailwind CSS. This post guides you through creating a flexible, component ideal for menus, navigation, or forms.

There’s a lot of criticism of Ruby and Ruby on Rails. In this post, we will try and debunk four widespread myths about Ruby.

There are five interdependent forces in every software project that can drive it to success or to utter failure. Read on if you want to learn about how they work and how to wield them.

Ruby on Rails is our main tool for building MVPs and big web applications. People say it’s old, dead, slow, that it’s not relevant anymore. Wrong! Here’s why.

Status updates are often regarded as monotonous, repetitive, and useless. But for us, they’re the most powerful and simple tool we have to deactivate all sorts of communicative issues the main way to build successful and enjoyable relationships with our clients.

Communication is a key aspect of our culture and development process. Do you want to know why and how?

Do you have a Ruby or Rails application in production for more than 4 or 5 years? Has the test suite crumbled to pieces because of too many broken or flaky tests that no one has time to fix? Do you feel your app needs a lot of love that no budget will ever be able to sustain? Read on to know what we do in these cases.

Learn SINAPTIA’s methodology for taking over existing projects, from initial onboarding and roadmap creation to efficient development and fast delivery of new features or maintenance.

We are a fully remote company, and as such we understand the downsides of working remotely. How do we effectively do it?

What to expect before, during, and after building an MVP with us. Deep dive into the process: from the discovery phase to launch!

Discover what an MVP is and how to build one effectively. This guide helps you validate product ideas, prioritize features, and launch quickly to gather essential user feedback.

Our approach to building modern React frontends within a Ruby on Rails monolith makes use of the best of both worlds.

In this episode of our Docker in development series, discover various alternatives and tips to optimize your Docker images, reducing their size and improving efficiency.

In this episode of our Docker in development series, learn how to perform everyday tasks within your Docker containers, including running rake tasks and managing databases.

In this episode of our Docker in development series, we’ll guide you through the process of dockerizing a Ruby on Rails application step-by-step.

Explore the benefits of Docker for development, with practical tips for Ruby on Rails and React projects. Learn how it streamlines setup and ensures consistent environments.