Refactoring and evolving models
One central idea of our Pragmatic Data Platform is to produce clean code with a clean structure, according to the least surprise principle, which, in turn, promotes quicker development, high maintainability, and reduces developer stress.
Why? Because databases are the longest-lived applications in any company, and they need to be managed for a long time. Therefore, our pipelines will need to change and adapt to business changes and changes in the source systems, and sometimes to changes for compliance or other legal reasons.
Maybe counterintuitively, the more success our data product has, the more requests we will get to add more functionalities. The time and cost of all the changes are directly affected by the quality of the code where the change must be applied.
In this long journey, we will have two activities that will keep our project relevant:
- Evolution: This involves adding new functionalities and keeping the existing ones working...
