One good practice is to write code iteratively, testing every time we make a new small feature or improvement, and always write code thinking of all the features we envision for our service.
Thinking about the service roadmap allows you to prepare the service for future improvements, reducing the amount of code wasted or replaced later on.
For instance, in terms of security:
- Is our service secure? Is it prepared for some types of malicious attacks?
- Is our service private? Should it have some kind of authentication or authorization mechanism?
Luckily, our frameworks allow our code to be composed and allow us to add layers of security later. For example, using Express or Hydra, we can add a precedent routing function that will run ...