# Helping devs understand concerns faster

**URL:** <https://discuss.rubyonrails.org/t/helping-devs-understand-concerns-faster/74619>\
**Category:** A May Of WTFs\
**Created:** [May 8, 2020, 6:21pm UTC](https://discuss.rubyonrails.org/t/helping-devs-understand-concerns-faster/74619 "2020-05-08T18:21:01Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![joallard](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/joallard/32/990_2.png) [@joallard](https://discuss.rubyonrails.org/u/joallard)\
**Post date:** [May 8, 2020, 10:41pm UTC](https://discuss.rubyonrails.org/t/helping-devs-understand-concerns-faster/74619/9 "2020-05-08T22:41:35Z")

</div>

Well, yes, Module::concerning does create a module extending ActiveSupport::Concern.

They’re all concerns, which are basically just fancy modules.

---

_[View the full topic](https://discuss.rubyonrails.org/t/helping-devs-understand-concerns-faster/74619)._