This doesn’t sound like an Excel problem it sounds like a management/software upkeep/bus factor problem.
I’m going to be the odd man out and say that Excel isn’t even that bad: I use it a lot for RPG simulations and engineering simulations, and not just because CSV is normalized. It can be part of the tech stack, but not in a mission critical way. There’s really no tool like it especially if you are doing simulations.
100%, excel is great for spreadsheets and garbage as a database, yet so many people keep using it as a database. I’m currently pushing for my department to transition their many “excel databases” to proper databases and I’m getting mass surprised Pikachu face because no one else knows they’re not the same.
Indeed, I’m pushing for SQL but work in a field that sees Excel as a huge improvement over past practices. They’re about one step removed from writing on toilet paper.
My original career was in a much more data intensive field, so I’ve become “that guy” regarding proper data storage and hygiene. Case in point: we sit directly next to IT. Every time we talk about data collection, I’ll get up on my SQL soap box and one of the IT folks will let out a comical groan.
This doesn’t sound like an Excel problem it sounds like a management/software upkeep/bus factor problem.
I’m going to be the odd man out and say that Excel isn’t even that bad: I use it a lot for RPG simulations and engineering simulations, and not just because CSV is normalized. It can be part of the tech stack, but not in a mission critical way. There’s really no tool like it especially if you are doing simulations.
100%, excel is great for spreadsheets and garbage as a database, yet so many people keep using it as a database. I’m currently pushing for my department to transition their many “excel databases” to proper databases and I’m getting mass surprised Pikachu face because no one else knows they’re not the same.
Well if you’re trying to use Excel as a database, get them behind SQL Server or something. Hell, Access is a step up.
Using Excel outside of simulation proofs is not a wise business decision, because it means (going off my experience) institutional knowledge
Indeed, I’m pushing for SQL but work in a field that sees Excel as a huge improvement over past practices. They’re about one step removed from writing on toilet paper.
My original career was in a much more data intensive field, so I’ve become “that guy” regarding proper data storage and hygiene. Case in point: we sit directly next to IT. Every time we talk about data collection, I’ll get up on my SQL soap box and one of the IT folks will let out a comical groan.