boem@lemmy.world to Technology@lemmy.worldEnglish · 7 months agoHow a Microsoft Excel Spreadsheet From Hell Slowed Williams' F1 Cars For Yearswww.thedrive.comexternal-linkmessage-square46fedilinkarrow-up1242arrow-down111
arrow-up1231arrow-down1external-linkHow a Microsoft Excel Spreadsheet From Hell Slowed Williams' F1 Cars For Yearswww.thedrive.comboem@lemmy.world to Technology@lemmy.worldEnglish · 7 months agomessage-square46fedilink
minus-squareAleric@lemmy.worldlinkfedilinkEnglisharrow-up25arrow-down1·edit-26 months agodeleted by creator
minus-squarekingthrillgore@lemmy.mllinkfedilinkEnglisharrow-up8·edit-27 months agoWell 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
minus-squareexpr@programming.devlinkfedilinkEnglisharrow-up3arrow-down1·7 months agoIf you’re working with csv data, https://www.visidata.org/ >>>>> excel (assuming you’re comfortable with terminal UIs, anyway). You can very rapidly slice and dice data and for formulas and such, you can just write Python.
deleted by creator
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
deleted by creator
If you’re working with csv data, https://www.visidata.org/ >>>>> excel (assuming you’re comfortable with terminal UIs, anyway). You can very rapidly slice and dice data and for formulas and such, you can just write Python.