You don't really need to be asked if you're sure.

But software asks anyway.

Delete a file, send an email, close a tab, clear a form. At some point in the flow, a small dialog appears, politely checking that you understand the consequences of what you've just done. As if the system itself is not quite confident enough to proceed without your emotional reassurance.

It's a strange pattern when you stop to look at it. The system already knows what you clicked. It already knows what will happen next. It could simply do it. Instead, it pauses and asks you to confirm something it already understands better than you do.

The idea of “Are you sure?” predates most modern interfaces. It comes from a time when actions were harder to undo, when mistakes were more expensive, and when software genuinely needed to slow people down. Over time, undo systems improved, version histories appeared, and cloud storage made recovery almost trivial. But the question remained.

Undo systems now handle most of what these dialogs were originally designed to protect against.

So what we're left with is not safety, but theatre.

A simulation of caution that no longer reflects how systems actually behave.

The interesting part is how quickly this becomes invisible. Users learn to click through it without thinking. The dialog stops being a safeguard and becomes a rhythm. A pause that signals “something is about to happen” rather than “something needs reconsidering”.

We've replaced system-level resilience with user-level anxiety.

It shows up elsewhere too. The constant layering of confirmation steps, warning states, and “just in case” interruptions that exist not because the system is fragile, but because the design has inherited a fear of being wrong.

It feels related to broader patterns in interface design where old constraints continue to shape behaviour long after they've stopped applying. The history of graphical user interfaces is full of these kinds of inherited decisions.

And once you notice it, it becomes hard to unsee. Not because it's broken, but because it reveals something uncomfortable: the system is not protecting you as much as it is remembering a time when it had to.

Software still asks if you're sure because it once needed to.

It just never stopped.