Indeed, and isn’t it wonderful that in Coda we have so many choices? Love this platform.
To put a finer point on my comment, I don’t necessarily regard dynamic tables as good or bad in either an operational or archival context; they can be used for both static or dynamically-changing information and it’s nice to have a consistent canvas for building clever solutions. Like a good all-purpose cleaner.
And I am certainly guilty of racing into projects without any regard for the lifecycle of data. It increasingly seems that for every solution, there is a sort of “archive debt” that must be repaid [eventually]. As in life, we are free to finance these debts or race a little slower and not accumulate debt so quickly.
The test to determine if a solution will accrue interest on this debt is pretty simple -
Must the data used to address operational tasks be preserved to meet (i) analytics requirements, or (ii) provenance requirements?
An affirmative answer to either question seems to suggest the there are interest charges and the data lifecycle must be attended to in some way.