| Realistically, you only need to memorize a few: - rake test: run the entire test suite - rails s: run the rails server - rails c: opens up an IRB/pry session with your Rails app - rails g migration: create a new migration - rake db:migrate - Run new migrations - rake db:create - create the DB the first time - rake db:schema:load - generate the DB from schema.rb - rake db:setup - generate a new database from migrations - rake routes - Spit out the routes and path helpers Don't ever use rails generate model/controller. It generates so much garbage that you likely won't need. There are a bunch of other commands off of rake db:migrate but most aren't needing to be memorized. Our brains are only so large and dense and mine is particularly small, memorize what is important and memorize how to look up the rest. |
I really disagree on the bit about not using rails g for controllers, and especially models. If you include your fields and types in the generate command you are given the corresponding migration, fixture, and test file for said model. If most of what you need can be generated by a single command, that's a whole lot less to remember compared to the intricacies of manually creating migrations, fixtures, test files etc. The generate commands have gotten so solid throughout the years, you can even do polymorphic and other associations through them and skip manually writing out all those details at this point. A whole lot less to remember there.