My solution to most things, make it a chore.

Like, if you don’t buy it, you can’t drink it. If you have it, put it in an inconvenient place so you you won’t see it or bother getting it.

Try making a list without copying every time you add something. Mutability matters then. Imagine copying 10000 elements, or copying 10000 references to items every time something were to be added or changed.

It probably makes sense if the program they came from is a badcase, but at least ours don’t go over board. It’s always a “you are probably doing something wrong, but we will allow it if you want to” or a “please confirm you want to do this thing that may have huge consequences”. With what they were learning, they were not touching anything related to the latter. So they probably were doing something wrong.

I was on-site for users learning our new program. Watched them do something, a dialog came up, and faster then i could catch what it was, they closed it. Dialogs are warnings or confirmations you know, and they did not know what it was…

So yeah, sometimes I do think there should be a wait time on the OK button.

If Reddit back in the day had asked a few dollars for me to stick with using 3rd party apps using the API I would have. But they did the opposite, so here I am. First time actually donating to something, a measily $2 dollars a month, but hopefully a start to fund some of the free stuff I use.