Ah, yes. Easily adoptable by coworkers + low repeatability = no need to change. Stick with spreadsheets.
Ah, yes. Easily adoptable by coworkers + low repeatability = no need to change. Stick with spreadsheets.
I agree that spreadsheet use in engineering is one of the most complicated use cases, but I submit for your consideration another very complicated use case: laboratory software ( https://en.m.wikipedia.org/wiki/Laboratory_information_management_system ) LIMS do what Excel can but with the added benefits of being more controlled, secure, user friendly and faster because they’re built upon the back of a modern database. In my experience with engineer built worksheets, the engineer that built them is typically the only one who knows how to use them. This is job security for that engineer, but isn’t scaleable for others’ use. In the lab software, a scientist builds the methods, and lab technicians use those methods over and over again daily. Each step of each use of the method is recorded with the inputs, the results, who performed it and exactly when. The workflows are built-in and the calculations are comparable to those used in engineering.
If an Excel sheet is that big, it should be replaced with a proper database, which most likely would run on Linux. I think you’re right, though, about the lack of planning around the practicalities.
Ooooh. So close. Care for a third try?
“Sir? Sir! It is well past time for you to begin your day. Yes, sir, I am well aware work, as you put it ‘sucks ass’, but never the less, it is time to rise and shine. I will be back tomorrow at the same time.”
Do you cut it in spring so it’s long in winter?
Begrudgingly given upvote. Sigh.
I use Thunderbird on a Debian desktop and a client on my phone Fairmail https://email.faircode.eu/