Skip to content

Commit

Permalink
Add follow-up user quote
Browse files Browse the repository at this point in the history
  • Loading branch information
kaspth committed Dec 15, 2023
1 parent 6f84bd9 commit 6006c84
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -163,10 +163,16 @@ end

## Testimonials

Here's from a user and how they started:

> We're running `ActiveRecord::AssociatedObject` and `ActiveJob::Performs` (via the associated object) in 3 spots in production so far. It massively improved how I was architecting a new feature. I put a PR up for review and a coworker loved how organized and easy to follow the large PR was because of those 2 gems. I'm now working on another PR in our app where I'm using them again. I keep seeing use-cases for them now. I love it. Thank you for these gems!
>
> Anyone reading this, if you haven't checked them out yet, I highly recommend it.
And here's how they were liking it about a month later:

> Just checking in to say we've added like another 4 associated objects to production since my last message. ActiveRecord::AssociatedObject + ActiveJob::Performs is like a 1-2 punch super power. I'm a bit surprised that this isn't Rails core to be honest. I want to migrate so much of our code over to this. It feels much more organized and sane. Then my app/jobs folder won't have much in it because most jobs will actually be via some associated object's _later method. app/jobs will then basically be cron-type things (deactivate any expired subscriptions).
- [@natematykiewicz](https://github.com/natematykiewicz)

## Risks of depending on this gem
Expand Down

0 comments on commit 6006c84

Please sign in to comment.