4 ms·
Formatting is a very very distant minor gripe compared to what I think is the main reason this is a problem: versioning. That being said, if it works, it works
by Waterluvian 5y ago
Formatting is a very very distant minor gripe compared to what I think is the main reason this is a problem: versioning.
That being said, if it works, it works.
If it doesn't work, make a case for why and develop a _holistic_ understanding of the costs and benefits of changing the current process. Maybe you can change it, or maybe you learn why it doesn't change.
If it works, but it offends your sensibilities, perhaps this is an opportunity for self-growth.
- onphonenow 5y agoJust a note that many folks on platforms like dropbox / S3 etc turn on versioning of excel sheets if they are in paid status for this exact reason. It's not perfect, but it get's you a lot very very easily. Version - date changed - who edited. Add in the universal flexibility (both function and who can use it). You can hand an excel file off to admin temp staff all the way to the top 3 folks in the org in one file and they can all interact with it successfully in most cases. This makes this very powerful.
- Waterluvian 5y agoYeah. It's like git is baked into the file. I don't work with spreadsheets much but I completely understand why they're loved so much. They're data, code, presentation, versioning, etc. all in one file that has _very_ good support. Excel is for the people who want to actually get stuff done and find all tooling a distraction from what actually adds value to the company.
- stainforth 5y agoWhat does "are in paid status" mean?
- onphonenow 5y agoPaid plans either enable or give you longer version history 6 months minimum, some businesses bump that up to 1-2 years (it goes to 10 years with dropbox). Same with google. Paid plans you can make sure a copy of all sent messages is kept, set retention rules etc. So if folks use email for all their approval / business flows that can be helpful (ie, some orgs CEO might send an email say I approve - go ahead and sign it on big deals rather than shuffling paper or doing a proper e-signature. If so, you might want to keep an archive org level of your email flows
- itsdrewmiller 5y agoExcel has versioning now! But it doesn’t work when people email around hard copies instead of links to the shared file, which they still constantly do. >:-O
- dragonwriter 5y ago> email around hard copies I get what you mean but...
- gopher_space 5y agoOne of the problems with Excel at scale is that different departments within the same organization might use completely different approaches. Different people in the same department night. When you add versioning what you may end up with is an out-of-date "master" that's occasionally updated from the spreadsheets everyone is still passing around via email. The email thing happens because that's how people who use Excel handle versioning. They'll end up with nested folders of emailed spreadsheets they can refer to or import into their personal approach. This works well for them, especially since they might work offline frequently.
- sbierwagen 5y ago>instead of links to the shared file So you mean Excel 365, not desktop Excel?
- CRConrad 5y agoCould mean links in the form of SharePoint / OneNote location of a spreadsheet file to edit with desktop Excel.
- windowshopping 5y ago> If it works, but it offends your sensibilities, perhaps this is an opportunity for self-growth. I've had to learn this lesson. We have an internal microservice whose name is obsolete and no longer makes any sense whatsoever. Everyone is confused by the name until the original reasoning is explained, and they come to understand the original purpose of the service, now long since changed. It drives me up the wall. I have time and time again made a case for renaming it to accurately represent its modern purpose, which would take an engineer about a week of work - there's a lot of code and config that has to be switched over. The person running my division has shut me down on this over and over. It goes like this: Manager: Why do you feel this is a priority? Me: It confuses people and makes the code less self-explanatory. Manager: How much time is this costing engineers? Me: Well, about a minute every time I have to explain it to someone once a week. Manager: And it would take a week to update? This doesn't seem like a good trade. Me, mentally spluttering: But the name makes no sense!! It's the wrong name!! It's completely unrelated and has no meaning! Manager: Do you think you can work with it anyway? Me: sadly sighs. I think the manager is right, as much as it offends my sensibilities.
- Waterluvian 5y agoI've been doing this stuff for almost 10 years and I _still_ struggle with this lesson. I think it's a good sign. We have a deep desire for correctness. But I think while it's perfectly healthy to desire correctness, we all need to be able to do what you've demonstrated: accept that sometimes correctness is not a logical endeavour.
- deltaonefour 5y agoI actually don't have this problem. A lot of things programmers get hung up on is just OCD stuff that don't actually improve anything. I once named a function findGreatestCommonDenominatorGCDOfFraction(numerator: int, denominator: int) -> int and one programmer wanted me to rename it into GCD(x, y) because it was more elegant. While GCD feels more elegant it's actually less clear and less practical. The length and verbosity of the function name above typically has a zero cost because of auto complete and other features you should be using in your editor.