Make the app/models more clear using namespaced models Read More

When the business logic of models becomes complex, it's very helpful to keep a consistent code structure that is agreed by team members. Read More

the routes will become complicated with the growth of your application, contain different namespaces, each with a lot of resources and custom routes, it would be better to split routes into different files according to the namespaces, which makes it easy to maintain the complicated routes. Read More

If you use rails generator to create scaffolds or controllers, it will also create some helpers, most of the helpers are useless, just remove them. Read More

Are you tired of going to schema.rb to find your table structures information? It would be better to list all the attributes of the model in the model itself. Read More

If you want to process something expensive as part of a web request, it will delay the response. If the job is not critical, it's wiser to move the expensive to a background queue and returns the response immediately. Read More

Ruby/Rails provides a lot of magic codes, especially for metaprogramming, they are powerful, less codes to implement more functions, but they are not intuition, you should write good comment for your magic codes. Read More

Like the simplify render in views, from rails 2.3, we can also simplify render in controllers. Read More

render is one of the often used view helpers, we can pass object, collection or local variables. From rails 2.3, more simplified syntax for render are provided. Read More

Trailing whitespace always makes noises in version control system, it is meaningless. We should remove trailing whitespace to avoid annoying other team members. Read More