I'm processing data and writing in a database, that is used by my colleague, a designer, working on data viz.
How can I efficiently, say, add a new column for my colleague to use in their visualization?
I have a "production" output which they uses, and a "staging" output that I use to check my result, they also have a "production" visualization (website for instance) and a "staging" viz.
I'm thinking of 2 options:
- Add new column into my staging output,
- once I'm happy with my dev, launch this new feature (new column) into production,
- then write some sort of release note to warn my colleague that this new column is available,
- and let them do their part of dev/staging/production for their visualization.
- Add this new column into my staging output,
- warn my colleague that this new column is available,
- wait for them to do their part of the dev
- once we're both happy with our dev, launch the new column and the new visualization in production
Each method seem to have cons, so I can't make my mind about what to do:
- A bit slow, my colleague has to wait for me to launch my feature to start working on their visualization
- If I'm removing a column I need to be extra careful that nobody is using it, since it's in production
- We need to deploy in sync
- My colleague is working on changing data. Say I need to change the name of the column I'm using during my development phase, my colleague needs to update the source of their visualization.