TIL 5/27/2026

A developer successfully set up user authentication for a Rails application using the Devise gem, generating migration files and configuring sign-out routes. The project initially encountered high token costs when using Claude Code for file modifications, as the AI was re-reading entire files for each change. The developer pivoted to a hybrid approach, writing basic controller and view code manually with a study buddy tool while reserving Claude for targeted bug fixes when credits become available.

Spin up from FirstDraft Co-pilot. It's been a while since I've done this, so I'll outline the process. - Include devise gem on gemfile - bundle install devise gem - run rails generate file from co-pilot with users line - check generated migration file - run rails db:migrate - Change config.sign out via = :get on the config/initializers/devise.rb file - Spin up app, check that /users/sign up and /users/sign in screens work - First go through was successful - I began working off of Claude Code window to help run the rest of the files - Files ran, and routes began to be built out, but I learned that tokens ran out quickly because Claude was re-reading the whole file and making changes which is very expensive. - Next step was to get claude to recommend a path forward build out habit route , then leverage first draft study buddy to help me build out that code. - New plan of attack - write out as much code using study buddy, build out the basic RCAV functionality by hand - Leverage Claude Claude once credits are available to work out bugs.