10

Watched 10 videos

Watched 10 Videos from start to finish
7/10

Spread the word 1 time

Referred 1 Member to Drifting Ruby

50

50 times Chatter Box

Make 50 comments to videos or replies to other comments
12/50

10

Share the love 10 times

Liked 10 episodes
6/10

30

Welcome back 30 times

You've visited Drifting Ruby on 30 different days
15/30

Suggested 1 episode

Helped the community by suggesting 1 episode

Vote Suggestion 1 time

Helped the community by voting on suggestions 1 time

Watched 1 video

Watched 1 Video from start to finish

Earned on 3/7/2019

Subscribed for 1 month

Learning and showing your support for 1 Month

Earned on 3/4/2019

3

Subscribed for 3 months

Learning and showing your support for 3 Months

Earned on 3/4/2019

6

Subscribed for 6 months

Learning and showing your support for 6 Months

Earned on 3/4/2019

12

Subscribed for 12 months

Learning and showing your support for 12 Months

Earned on 3/4/2019

18

Subscribed for 18 months

Learning and showing your support for 18 Months

Earned on 6/2/2019

24

Subscribed for 24 months

Learning and showing your support for 24 Months

Earned on 12/2/2019

1 time Chatter Box

Make 1 comment to videos or replies to other comments

Earned on 3/4/2019

10

10 times Chatter Box

Make 10 comments to videos or replies to other comments

Earned on 3/4/2019

Share the love 1 time

Liked 1 episode

Earned on 3/4/2019

marklar PRO said over 2 years ago on users DataTables :
Would you be able to share some sample code for your solution to this?

marklar PRO said over 2 years ago on users In-depth Look into ActiveStorage :
Do you know if it's possible (or advisable) to use ActiveStorage with Rails 5.1.6? In the Rails guides it states: > After upgrading your application to Rails 5.2 http://guides.rubyonrails.org/active_storage_overview.html#setup So I wonder whether it would be ill advised to add ActiveStorage as a gem to 5.1.6.

marklar PRO said over 2 years ago on users In-depth Look into ActiveStorage :
Yikes, it sounds like it's not the best idea for a simple plug and play solution with 5.1.6 then. Thanks for taking the time to reply and thanks for the great video.

marklar PRO said 10 months ago on users Refactoring Models :
When I try this approach I get a **Circular dependency detected while autoloading constant** error when I run my app with foreman with resque. I do **not** get the error when I simply run `rails server`. In [this issue](https://github.com/resque/resque-scheduler/issues/646) it states: > You have to make sure all classes can be loaded without this circular autoloading. There is a bug in your application, it is not resque-schedule issue. >The classes can load fine in some ordering, but in others not. This is why you are getting this problem only occasionally. Sometimes the order your classes are loaded are different, and in those cases you get an exception. You need to make sure your classes can be loaded correctly in any order. Do you see how this problem could be created from using namespaced concerns? Thanks for the help.

marklar PRO said 10 months ago on users Refactoring Models :
It appears this is a common problem as seen [here](https://github.com/rails/rails/issues/14401), [here](https://github.com/rails/rails/issues/36054) and [here](https://stackoverflow.com/questions/37507321/rails-namespacing-concerns-based-on-model-name). The solution is to move your namespaced concern out of the `concerns/` directory and under the `models` directory as per [this answer](https://stackoverflow.com/a/50889849/1299792). This is the same directory structure [they are using at Basecamp](https://twitter.com/dhh/status/964864438938492930)