this is my meta rules for automation. impact , cost and frequency should decide how we prioritise and how we approach automation.
- one - just get it done if it is low impact, low risk and low cost
- two - thinking and documenting
- three - automate it.
- full automation
- break down the process. see if the sub process is automatable
Take an use case of form builder.
- Form, fields(types of supported)
- FE for the fields - automatable
- moving the field from single valued to multivalued
- lets say we want to start with column in same table to begin with. when multivalue move to another table.
- migrator changes,
- script for data migration
- are the above two things generatable if given the inputs.
- lets say we want to start with column in same table to begin with. when multivalue move to another table.
agents and sub agents
agent - DB agent sub-agent - field transformer
Referenced in:
All notes