to bail out vs to back out

In a CS context, I have often come across the expression to back out meaning to say that a function is returned from before performing its actual task, as in this imaginary code comment:

double divide(double dividend, double divisor) {   if (divisor == 0) {     return 0; //divisor is zero => back out early   }   return (dividend / divisor); } 

Now I recently came across the expression to bail out in just the very same context. I know that to bail somebody out generally means to provide funds to get someone out of a difficult financial situation, so I was wondering if the writer confused to back out and to bail out or if to bail out really has this meaning, too.

Has any one ever heard or read a native speaker of English say or write to back out of a function? Or, if you’re a native speaker, would you say to bail out is also correct here?

When reverting back to humanoid after being polymorphed, can a character have remaining movement speed in that turn?

A hag transforms my character into a frog, which gives my character a movement speed of 20 feet. Let’s say that as a humanoid I would have had a speed of 30 feet instead. I use the frog’s full movement, before the hag uses a reaction to strike me with an Attack of Opportunity.The hit does nough damage to revert back to my original form.

Do I now have 10 feet of movement remaining this turn, since I only used up 20 of my maximum speed?

Related

How do changes to your speed affect your available movement?

This question doesn’t answer my question, since it doesn’t a) give a clear yes or no to my question, and b) specifically address the context of having different shapes during a turn.

Unauthorized backups, how to seize back data? [migrated]

It appears that someone at my company (likely using stolen admin credentials) had set up backups for the whole org on G Suite using Backupify and Spinbackup. We need to secure the data. Unfortunately the login for Backupify seems to be something other than a company email.

How do we legally seize our data from these backup services and make sure nobody else has access to it?

(Of course it’s likely that whoever set up these has a copy of all data already but that’s a separate problem)

[ Insurance ] Open Question : If parents take out whole life insurance on their kids, then die first, shouldn’t someone get some cash back for the years of payments made?

The cover page says each child was insured for $ 5K, ‘whole life paid up at age 65’ with number of years payable at 54 (for the child that was 11 when the policy started) with annual premiums of $ 53.30. Isn’t the purpose of ‘whole life’ policies that it’s like an investment? Parents are most likely to die first, so of course their payments would stop before the kids ever reach 65. Is the policy worthless when payments stop? This seems like a bad, ill-advised deal if no one gets money back.   It doesn’t make sense to me that any LONG TERM policy should cancel just because a person was unable to make payments for a temporary period of time, like after getting laid off from work, disabled, death of a spouse, etc. It would be no wonder insurance companies make so much money if they get to keep all the money they taken in for many years from people who will never file a claim before they stop making payments for whatever reason.  

Am I the only one who can’t help but constantly think back on all the horrible security nightmares (and potential ones) from my past? [closed]

I’m not going to go into any specifics here, because I’ve learned that “certain” open source projects are extremely sensitive about any criticism and will defend any kind of madness by blaming the user for not fully reading and comprehending the often extremely cryptic and ambiguous manual, while not putting any blame on the software for allowing the insecure configuration in the first place.

You may think I’m joking, but even 15-20 years later, I still have actual nightmares about things which happened, or could have happened, or may have happened without me ever finding out, in the past, due to bad security, either by myself and others (affecting me).

A huge issue with security is not realizing one’s own limitations and having a big ego. You know how it is: you are 15-16 and you are totally an “1337” cracker, aren’t you? Everyone else is stupid and you know everything. You couldn’t possibly misconfigure or misunderstand anything, right? That manual only seems to verify what you already knew… yes, that seems to be correct… yes, now let’s put it live! It’s rock-solid!

… and then it turns out that somebody has been remotely connecting from across the world to your ultra-sensitive database for the last eight months and saved all your private information to blackmail you perpetually. Because it allowed any password as long as they guessed the default admin account. Which was supposed to only be accessible from 127.0.0.1.

The most frustrating part is perhaps that, now that I know about many of these things, I find it utterly impossible to educate others about it. They are just as deaf to my advice as I would’ve been to advice from others back when I thought it was a good idea to enable that stupid mode which bypasses all passwords, because even though I read the manual, I read it horribly wrong!

I actually remember saying to myself: “Well, they can’t mean that ANY password goes, because that would defeat the entire purpose of having passwords in the first place, so I can safely conclude that they didn’t mean this.”

They meant it.

Not one day goes by without me thinking back on all these stupid decisions, and while I know very well that it does me no good, I can’t help but be bombarded with these memories and thoughts. It’s easy to laugh at it now and shake one’s head, but when I saved the config that fateful day and reloaded the service in question, I was 100% convinced that my database was fully locked down and that I was the only person in the world who would ever be able to access it, because I had read the manual as I was always instructed to do.

The above vague story is just one out of many such cases which I’ve experienced or heard of. Somehow, these experiences make me fully understand how there can be almost daily news of major critical databases exposed to the Internet with no password. They were simply set up by people who just didn’t understand what they were doing, and I consider it unfair to put all the blame on them.

I think a lot of software is made with a strange attitude to security, where you are harshly punished for not knowing everything about the software, as the developers (but nobody else) does.

Ways to bring the party back together

I’m part of an open-world campaign that continues after the events of SKT (we finished and still wanted to play with our characters). Lately, it’s like our dm is running 3-4 campaigns at the same time because we are all currently doing separate stuff. Some of the players, myself included, want to bring the party back together because its boring to not play for an hour while other people are doing their things. Our dm specifically said that he is not going to try to bring the party back together, no matter how annoying it is, and that it is up to us to meet up. That brings me to the question. How can I convince the players who want to do their own thing to come back to the party?