The Agile Manifesto clearly expresses the instances of opinionated expression. There is not any kind of hedging; only clear trade-offs, such as giving value to "working software over detailed & lengthy documentation. Ruby on Rails even defines it very strongly as the omnipresent "convention over configuration" precept. As and when the choice comes, the Rails always come to select a method that needs you to type just a few characters.
Most practices or methods of software development started off a mind-set or philosophy. That is right about the individual teams as it turns true for programming languages and software startups as well as corporate "everybody knows" cultural assumptions. It may not be possible for some to agree on it, but, a strongly shared opinion provides a group with its own reliability, veracity and integrity.
In actual fact, strong opinions by Rails are so much that it gets vogue to know if the trade-off is useful or not.This core decision, in a global sense, brings with it some evidently excellent aspects such as:
It has got less code, which means just a few bugs, a code that can be easily maintained
As soon as the conventions are comprehensible to developers, they can give good output as there is no need of boilerplate code, either at the initial stage or while maintaining the software.
The developer who is quite anew to a specific Rails project could become faster since the conventions are very common to all Rails projects.
Similar to code styling, the details too don't have any importance. It just matters when all get agreed, and when the Rails conventions have similarity.
No comments:
Post a Comment