I was compelled to explain in a large training session that Excel and MathCAD are not, Not, NOT acceptable tools for performing QL-1 nuclear safety calculations.

I absolutely hate that I have to keep explaining this to degreed engineers doing safety-critical work.

I am going to die on this hill whether I want to or not.

This just makes me want to cry.

Excel is suitable only for tasks less important than Girl Scout cookie sales tracking. Do not bet anything more valuable than a box of Thin Mints on Excel.

@arclight
Excel is not a spreadsheet. Excel is a full-featured virtual machine running a smalltalk-inspired REPL whose display layer happens to resemble a spreadsheet.

Something like a third of the world’s money goes through Excel every single day, and the reason you don’t think Excel is a Real Programming Language is because if we admitted that, we’d have to admit that most of the most important software in the world was written by underpaid women in pink collar jobs, and we can’t have that.

@mhoye @arclight

A major problem with #Excel isn't anything to do with sex or age.

It's to do with domain applicability. "Everything is a nail."

The number of times that I've seen people do database work laboriously in Excel when _there's a database tool right there in Microsoft Office_ is depressing. I haven't yet personally seen someone do word processing or mail merge in Excel, but I would not be at all surprised by it.

Too often the problem is that of using only one tool everywhere.

@arclight @JdeBP @mhoye yes, but most of the time, those people are « business experts » in their domain. 10 years ago, I bought a stack of the « Manga Guide to Databases » and lend it to those business people to help them model their business data, and then to help us integrate/migrate those to relational database backends or ERP. It also eased the dialog with IT people as they better understood relational concepts and SQL.
@jrjsmrtn @JdeBP The context of this thread is well-trained, well-resourced (mechanical and nuclear) engineers intentionally using Excel when technically appropriate tools are available. If business domain experts are anything like engineers, they view themselves as subject-matter-experts-who-code, not as programmers. Asa result, all the developer guidance about testing, code review, version control, etc. never reaches them. "Why are you telling me this; I'm not a programmer." Yes, yes, you are.
@JdeBP @arclight ? I am a programmer, I was also at the time, a system integrator to be precise. I never said I was not :-)
@jrjsmrtn @JdeBP I was referring to the people you were giving the Manga Guide to Databases to.