Connecting thoughts

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.

Welcome to the first 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.

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.

I’ve used RSpec for years, and until recently I had to work with a colleague that never really tested before. This process made me think if I should be critical about how I test and if I should (or shouldn’t) do something about it.

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.

We’ve been working with a boat marketplace for a year now. One of the most interesting challenges we faced during this time was reimplementing their broken search engine. This is how we did it.

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.

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.

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.

Psittacism signifies repetitive speech in the manner of a parrot. Can APIs suffer from it and what are their consequences?

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.

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.

I’ve been working on docker exclusively since 2018. Besides its many benefits, it could be tiresome to type longer commands every single time. How do I do it without losing my mind?

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?

What is Hybrid and Dynamic Database Multitenancy and how to successfully achieve it with Ruby on Rails (> 6.0) and PostgreSQL? Our experience implementing a hybrid and dynamic database multitenancy system for one of the projects we’re involved in.

A custom horizontal slider using React hooks to have full control over the design and behavior of the component. No more limitations!

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.

Ruby on Rails is our main tool for building MVPs and big web applications. There’s a wide array of myths about it online: that it’s old, or dead, or slow, that it’s not relevant anymore. We revisit our tech choice every year and we still chose Ruby on Rails. Here’s why.

When maintaining Ruby on Rails applications, it’s always recommended to run the latest versions of the framework so it receives security patches and performance boosts from newer versions. In this post, we’ll see our way of upgrading Ruby on Rails applications.

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

Based on Ruby on Rails examples, the core idea should apply to other languages and frameworks.

Continuing our Docker in development series, in this episode we will see alternatives so we can optimize our images.

Continuing our Docker in development series, in this episode we’ll dockerize a Ruby on Rails application.

In this series, we will explore the motivation and benefits of using docker in development. We are going to give everyday tips that helped us move forward using it, focused on Ruby on Rails and React development.