Hacker News Reader

Utilizing “Brute Force” as a testing and verification strategy.

Maybe it's a parallel to "if it runs, it works" :)

works on my box

"if you’re not seeing enough resistance, in most cases, you can just keep driving downward until you do" -> "Many have said similar about their code" -> "works on my box"

How does this make sense or have any coherency?

User-side tests are the only tests that really matter.

Everything else you do is there just to reduce the odds of users tests catching anything. But you don't get any certainty before that step... that happens after your software is on production and people depend on it.

(Of course, that's a worldview that can be either very beneficial or incredibly harmful depending on what you are creating. It's not good to see it applied to bridges, but I believe the OP did it in jest.)

That's why we call it big test, not production.