A deep dive into Rails' `before_action` mechanism, explaining why it exists and how it works internally. Controller actions often need shared preconditions like authentication, account lookup, and authorization. `before_action` lets controllers declare these prerequisites cleanly, keeping action methods focused on their specific work. The post covers the internal callback machinery (`AbstractController::Callbacks`, `ActiveSupport::Callbacks`, `process_action`), why callback helpers should be private, how callback order creates dependency chains, inheritance from `ApplicationController`, `skip_before_action` and `prepend_before_action`, conditional callbacks with `only`/`except`, a common `redirect_to` vs `return` gotcha, and a practical debugging path for when actions don't run as expected.
