[wyldfire]

> Everyone literally laughed at me, thought was a grade A moron.

A note for anyone else in a similar situation - a good team doesn't ridicule someone for questions like these. A responsible leader should have cited a time in the past that they did a restore or a spot check, and no one should have laughed. The laughter sounds like masked fear or embarrassment.

This goes for any team. "How do we know this function of our job does what we think it does?" You should have an answer. Now, I've only worked in R&D software and not in IT. But IMO IT teams should work the same way in this regard.

[yosito]

> a good team doesn't ridicule someone for questions like these

A good team won't ridicule any questions. If you're on a team that ridicules your questions, that's a huge red flag. Get out as soon as possible!

[908B64B197]

> A responsible leader should have cited a time in the past that they did a restore or a spot check, and no one should have laughed. The laughter sounds like masked fear or embarrassment.

... or assigned the engineer asking questions the task of figuring it out!

[amatecha]

Right? I regularly ask seemingly-rhetorical questions "just to make sure", and this approach helps me catch tons of otherwise-unnoticed issues. Being curious and vocal is a valuable approach in any technical business, IMO.

[Cthulhu_]

Yeah, they didn't even doubt themselves for a second, instead of challenging their own beliefs or at least showing the person that the backups were working before laughing.