Don't Repeat Yourself or how to shorten experience of fast-moving life.

Using Nest.Js /Flutter.Js makes the development process faster in 700 times. There is a commonly accepted principle in the modern software development approach: Don't do it twice.
SafeValue must use [property]=binding: But If you really want to do something twice, you'd better think twice. The idea is to abandon a situation when useless templates are heaping over and devour hours of priceless time. Don't Repeat Yourself (DRY)- demands wicky, and you know what does it mean. As a developer, you should be aimed at reducing the repetition of software patterns, replace them using data normalization or with abstractions to avoid redundancy. (see http://g.co/ng/security#xss)
How's it working?
SafeValue must use [property]=binding: Once on a sunny day, we got a big and very interesting project and began to work on it. When we got to the splitting requirements, we found out the identical behavior for some parts of the application. Naturally, there are a few ways to solve it, depending on some requirements. So, let's talk about them. (see http://g.co/ng/security#xss)
Server solution
SafeValue must use [property]=binding: As usual, you deal with a lot of CRUD operations in each project. In computer programming, Create, Read, Update, and Delete (CRUD) are the four essential functions of persistent storage. Thus, to define and separate repeated code, we decided to make our library. Its main task is to create base CRUD operations. On the way, we were faced with the need to spend a massive amount of time in developing this library, and we hate this idea. Our credo is to spend as much time as it really needs to do a job, not an hour more. We value our own and our customer's time. So, we decided to use the Nest.Js and the @nestjsx / crud package to create a simple CRUD library. (see http://g.co/ng/security#xss)
Why we use Nest.Js?
SafeValue must use [property]=binding: Because it's cool and have a very cool libraries with a very cool features which allows us to save a lot of hours of developing and prevent to fix thousands of bugs. Tons of the frameworks appeared recently, but the Nest.Js is the best because of its architecture with no doubt. For CRUD generation functionality we use the @nestjsx / crud package. Look at Its capabilities, they are very interesting:
  • easy installation and configuration;
  • independence from the DBMS;
  • powerful query language with the ability to filter, paginate, sort, load links, and nested entities, caching, etc .;
  • package for generating requests to the front-end;
  • easy redefinition of controller methods;
  • small config;
  • support for swagger documentation.
Here be prepared to be surprised: Thanks to this technology, we’ve spent dozens of times less time. Yes, guys, dozens of times less time. (see http://g.co/ng/security#xss)
Client solution
SafeValue must use [property]=binding: Inspired by outstanding development time saving, we decided to use for the client application (it should have been a mobile application) the Flutter. We already told you about the wonderful features of that Mobile UI Framework‎ so that we will be shorter here: it is a modern Google's Mobile App SDK to make cross-platform applications. Thanks to it's quick and easy compatibility on the Nest.Js, we decided to make a few essential abstract components that we can reuse almost on all pages. What is really great that we found new in this project is a fantastic time saving, simple, and convenient development process, and... We didn't do it twice. (see http://g.co/ng/security#xss)