I remember one time I heard about a project that had nearly 100 different excel sheets talking to each other to create a system that handled 10s of millions rows to manage complex logistics. Not only did it work great for a few years, but it was done by a single madman person.
The issue came up that things started to slow down/glitch out and the original person who created it left the company, leaving this magical organization of sheets and voodoo to be migrated to a "real database" and app all the while data integrity was degrading by the scone.
We eventually re-built the whole thing as a real app and migrated over the data, but it always impressed me that a bunch of sheets were able to work that way, but it was also disturbing that much data semi-critical was being handled that way.
I remember one time I heard about a project that had nearly 100 different excel sheets talking to each other to create a system that handled 10s of millions rows to manage complex logistics. Not only did it work great for a few years, but it was done by a single
madmanperson.The issue came up that things started to slow down/glitch out and the original person who created it left the company, leaving this magical organization of sheets and voodoo to be migrated to a "real database" and app all the while data integrity was degrading by the scone.
We eventually re-built the whole thing as a real app and migrated over the data, but it always impressed me that a bunch of sheets were able to work that way, but it was also disturbing that much data semi-critical was being handled that way.
Exactly my point, displaying relationships in excel sheets can be a drag. Thank you for this real life use case, Brad.