Because Excel's flexibility encourages bad behaviour that will come back to bite you. Input data should be separate from your calculations, and you should neve

Because Excel's flexibility encourages bad behaviour that will come back to bite you. Input data should be separate from your calculations, and you should never deal with single cells in your results (fix your formula or input data instead). Yes, Excel actually has a mode that supports that workflow: the Unified Get & Transform Experience[0] (just rolls off the tongue, right?). And it's basically drag-and-drop Pandas. But I've only ever seen one person use it (after repeatedly bugging him about how we will need to repeat this analysis and how surely there must be a better way). And even then it's very easy to screw up and introduce bugs whenever the input data is replaced. Wanted to make a graph and only included the populated data region? Referred to the aggregation row somewhere in some stats sheet? Too bad! Also, Colin's post ends up recommending SQL Workbench/J, which seems to be much closer to MySQL Workbench than Excel. [0]: https://support.office.com/en-us/article/unified-get-transform-experience-ad78befd-eb1c-4ea7-a55d-79d1d67cf9b3 https://support.office.com/en-us/article/unified-get-transfo...