2 ms·
> new column/truth source I think we need to be a bit more explicit in this part. Database columns are your system of record. If the code treats them as the s
by hinkley 5y ago
> new column/truth source
I think we need to be a bit more explicit in this part.
Database columns are your system of record. If the code treats them as the source of truth, you need to break that first. If your code is factored properly you only need a toggle in the retrieval code. If it's not factored properly, now you understand why some of your peers are pushy about separating data retrieval from data use - it concentrates any mutation to a point in time before first use where you can easily find it when surprises happen and where there can be no concurrency issues. If that's too daunting you can settle for the lesser solution of replacing use with a function call.
Once everything is using the new source of truth, you can put a toggle there. And after the migration you can decide if you want to keep them separate or fold them back together.