S3, Amazon’s Simple Storage Service, is a cheap, scalable, highly available, and overall great solution for storing huge bits of data and and thus reducing your database size. For awhile now, we’ve realized that our database is on its path to becoming expensive and unmanageable due its massive size. So we decided to migrate some of that data over to S3.
In this article I explain the approach we took to make any attribute
We have been switching our local development setup slowly, but successfully to docker with NFS for speed. Almost everyone at the company is developing on a Mac system and so with the new Catalina release, everyone either pressed the “Update” button, or, like me, woke up to a new OS, got their cup of coffee, and typed in
Standard Ruby on Rails best practices suggest that we should define our validations on the model object. RoR gives you the tool, aka DSL (domain specific language), to implement these validations. For simple situations, say a sign up form, this works really well, but what about more complicated scenarios? What if your model serves several different controllers? Or what if, for example, different types of users could submit different values to the same model? Do we want to use messy
if blocks to check the
user type and apply the correct set of validations? Probably not. So whats the solution? Enter Dry-schema.
Iceland is a breathtaking place in the truest sense of the word. Behind every tall mountain facing the ocean, past every volcanic field, and across every waterfall there is another wonder waiting to be seen. If you’ve ever read Norse mythology, you’d appreciate how the landscape fueled creation of the characters and their stories.
It was a cold, snowy day in December when I decided to see the mountains of Annapurna and Machupuchare in Nepal… Nah, it was actually in the middle of October, and the weather was great! Not all stories worth writing about, need to be heroic. So, with no further lallygagging, here is my sweet tale of Nepal!
I wanted to create a responsive react navbar from scratch. I’m going to do this without using any CSS libraries just because I wanted to see if I can… I also wanted to refresh my memory on React. So here we go.
So you have a bunch of jobs lined up in Sidekiq.
But for some reason (user action, etc) you don’t need those jobs to execute anymore. So what do you do?
In Trailblazer 2.1, we are introduced to a new concept: Activity.
Unlike Trailblazer 2.0, where Operation was king, activities have taken over as the main orchestrator of business logic. Good old operations are still there, but now they act as a wrapper around activities. Its one and the same, except activities are more powerful! Don’t worry though, its super easy to pick up and its backward compatibility makes switching a breathe.