All table columns should also have unit in names, whether in charts, tables, database or variable names.
Oh yes. That would mitigate a lot of stupidity. Imagine if math in programming and Excel had to have both a) always visible/known units, b) unit propagation and c) unit checks. So if A is seconds and B is kilograms, the compiler/spreadsheet wouldn't let you write C = A + B.
Very similar to Hungarian notation: https://en.m.wikipedia.org/wiki/Hungarian_notation
I have marked up 100+ page reports, checking every number, in red pen and doing the math on a handheld calculator, checking the page references for all referred equations.
The best habit I had, from reviewing others' work, is to give my own work the same treatment.
This is the only way I got a long engineering report out in a reasonable amount of time: by catching my own mistakes by actually printing it out and going through it with a fine tooth comb.
It takes time, but not as long as you would think in many cases.
I've seen others just kind of skim a document and read a few words and see the shape of the equations, then sign off on it for non safety parts. Even then, you can easily lose lots of money on simple mistakes.
I've also seen inherited spreadsheets that went through several hands, with magical things added, that the past two people using it never checked.
Some people never learn to really go through and check.
I have seen where too many layers of checklists and verification just make people assume another layer will catch errors and then nobody checks thoroughly.
> I have seen where too many layers of checklists and verification just make people assume another layer will catch errors and then nobody checks thoroughly.
Yes, my experience is that few people are willing to do this. The important question then is how to find people willing to redo the work independently.
I haven't found anyone who seems interested in doing this or able to dedicate time to this.
Taking laborious manual procedures and automating them so as to flush out all the details that were overlooked or gotten incorrect is what I do at the moment.
I'm a theoretical fluid dynamicist. When doing math I'll typically check the dimensions, order of magnitude, bounds, functional dependencies (anything missing or something there that shouldn't be?), overall trends of an equation, and limiting cases. For solutions to equations it's useful to also plug the apparent solution back into the equation. Another check ideally comes after waiting a while so that my mind is fresh. Sometimes what I did seems dumb by then.
Coding up the math is useful too. I've found that I can never add too many assertions. I might have caught the error described in the article as I often use assertions to check bounds.
Peer review isn't as reliable as I'd like. When it comes to math, most people seem to "rubber stamp" it. I can recall reviewing a paper that had math problems that were fairly obvious to me. For some reason I got the reports from the other reviewers, and I was the only one to notice...