How a Feature Dictionary Can Uplift the Modern ML Architecture

In enterprise ML architectures, it's wise to maintain the outputs of the feature jobs in a sharable format without encoding. These features can be later cherrypicked, encoded, and fed into an ML model that needs it. This approach has several advantages. When features are readily available, the journey from a'business question' to'scientific answer' becomes much more simple. With the availability of feature pool, when a data scientist wants to do a new experiment, he/she does not have to start from the raw data. Instead he/she can start with the available features. This can avoid a lot of unoptimised runs. In the cases where they need more data-features, it can go as a request to the engineering team to optimally build whatever new is requested. And when they are confident to take the model to production environment, the model promotion will involve only minimal components.