New model Asset

On Friday, Mathias and I created a new model Asset. In the last posts we did a refactoring for using a Resource (polymorphic) instead of User in Candidature and Vancancy models. A resource can be an User or an Asset.

Today I finished the "Meaningful Names" chapter of Clean Code. Then, solved an error in the application  translate_german_words and finished the refactoring applying this chapter. At the moment, I can see three clear consequences of using meaningful names:

- A developer can read the code easier, like an story.

- You can see easier the repeated code.

- I guess, that it will be useful to make smaller functions or methods (next chapter)

My next task in Voluntary will be apply Edit multiple to create a nested resources table for each vacancy.

Also, I'll continue reading Clean Code and refactoring the application translate_german_words.