zlacker

>>todsac+(OP)
> "None of the database guides I followed had warned me about the dangers of exposing a docker containerized database to the internet."

This prompts a reflection about, as an industry, we should make a better job in providing solid foundations.

When I check tutorials on how to drill in the wall, there is (almost) no warning about how I could lose a finger doing so. It is expected that I know I should be careful around power tools.

How do we make some information part of the common sense? "Minimize the surface of exposure on the Internet" should be drilled in everyone, but we are clearly not there yet

>>rpadov+Q2
> When I check tutorials on how to drill in the wall, there is (almost) no warning about how I could lose a finger doing so. It is expected that I know I should be careful around power tools.

I think the analogy and the example work better when the warning is that you should be careful when drilling in walls because there may be an electrical wire that will be damaged.

>>johnch+q6
To your point, guides don't warn too much about electrical wires because code and practices makes it really hard to do. Code requires metal plates where electrical wires go through studs so you can't drill into them, and every stud finder in existence these days also detects AC behind them.

We didn't make the guides better, we made the tradespeople make it so any novice can't burn down the house by not following a poorly written tutorial.

>>malfis+I8
> We didn't make the guides better

That sucks, because that means anything built not to that standard (which I guess is a US one?) could lead the person to hurt themselves/the house.

One doesn't exclude the other, and most likely both are needed if you're aiming to actually eliminate the problem as well as you can.