Keep your Rails app competitive with Oaken & ActiveRecord::AssociatedObject
Hey everybody, this week I did an impromptu talk with the Turkish Ruby meetup.
I'm basically speedrunning a walkthrough of both ActiveRecord::AssociatedObject and then Oaken.
I'm showing pretty much all the code too, so you're well-equipped to evaluate the gems as possible dependencies.
I'll write more about what's going on in here, but here's the video if you just want to dive in:
More on ActiveRecord::AssociatedObject
For a long time, it seems the only options the Rails community has come up with for extra model "conventions" are: Service Objects and everything-is-actually-perfect-why-can't-you-just-configure-vanilla-perfectly — while all the configuration that comes with these two is fun and all, that's not what I'm here for.
Instead, Associated Object is a term I'm introducing to recut our model layer complexity in a different way.
Once you learn the lightweight convention, it's then easier to decompose features automatically — and it's still compatible with other approaches, like Service Objects.
I'm not intending this to be a wholesale solution to every Model Out There, but a start to hopefully different ideas getting more airtime.
Garrett Dimon has been using it and just wrote up their experience this week. You should definitely check that out too.
More on Oaken
You've got a Rails app? It's got data in it? Oh Yeah? And tests with test data too?
Well, Thomas thinks you should check out Oaken for this:
We also covered Oaken in depth last week too.
Wrap Up
Thanks for reading and watching! If you want me to give an impromptu presentation at your meetup, hit me up!
I'm also available for company presentations, please reach out and we can jump on a call to find what content I could cover that would fit your team and budget.
PS. I've been doing the newsletter for a while, but I'm not sure if it's still useful to people. Can you please reach out and let me know what you're learned and what you've liked?