When you start working on an existing rail project, then what steps do you take to understand the code? Where do you start? What do you use to get a high level view before drilling into controllers, models, assistants and ideas? Do you have any specific techniques, tricks or tools that help in speeding up the process?
Please, "Learn Rail and Ruby" (do not reply to one of the responses) He did not receive a lot of response to his question, so I thought I would ask again and go a little further ). I am very comfortable with my code. It is sorting others who makes me head and take a long time to mess me up.
Look at the model If the app was written well, then you should give it a picture of your domain model, where this interesting argument should remain. I also look at the models' tests.
The way the controllers / ideas were implemented should just by using the Rail app and seeing the URL.
Unfortunately, there are many opportunities where there is a lot of logic in the controllers and ideas. This means that you have to take a look at those directories, unfortunately, tests for these layers are very less clear.
Comments
Post a Comment