DRY says that any information must not be held twice or more than once. This means, that in the database every information should be held once, the source code must not have double sections.
For us it means: That you do it one time right with Ruby on Rails.
Instead of complicated configuration files
or different names of database columns, Ruby on Rails simply gives rules about what to call something.
For example, the variable name for the identification number id is
instead of idx, idNr, id_nr etc.
The MVC architecture describes the programming paradigm used in Rails. There is a data layer defined by the model and a display of the data described by the view.
The controller is the programming glue to connect the data model with the display.
With our Test-First approach, we can eliminate potential sources of error. By testing the specification, we are able to identify in time whether the specification is consistent.
Our quality control ensures with the tests that the software quality has a high standard.
In Ruby on Rails, data is usually treated as a resource and is displayed, created, edited, updated or deleted by means of the URL via actions.
This standardization of the software enables us to offer interfaces (API) for third parties more easily.
The KISS principle tells us that in Ruby on Rails we should take the simplest and most effective solution. One of these principles is convention before configuration and DRY.
We at HanseHype take the KISS principle seriously and thereby deliver high software quality.
We at HanseHype GmbH provide you with customized solutions for the start of your project.