A lie is your own creation. You can tweak it to make it more palatable. You can't do that with the truth - you didn't make it, you can only use what it already is.
This is not about mistakes in the Git-managed code. This is about mistakes in the Git commands themselves. Anything that involves merging/rebasing/conflict resolution can potentially be botched. These mistakes are usually fixable, but:
Fixing it requires some Git proficiency behind the level of the common Git user.
If you don't catch it in time, and only find the mistake when it's deep in your layers of Git history - well, good luck.
The way the word is used in Hebrew isn’t that meaning of vain. It is vain in the sense of “vanity.” Emptiness of speech, lying, etc.
This. The word used in the original Hebrew is "shav" (שוא) - which can mean either "vain" or "false" - and the original meaning of the commandant is to not swear in God's name on something that's not true. Of course, the religious leadership immediately thought "well, we're obviously not going to refrain from lying, and refusing to invoke God's name just because we're lying is going to make it suspicious, so let's just say we are not supposed to invoke his name at all"
No. Just... don't. I don't know if you are trying to absolve humanity from their sins, or if you are just participating in the great tradition of declaring your enemies as inhuman so that you can kill them guilt-free - but either way, don't.
Actually, James wouldn't mind marrying her, but he has one condition she's refusing to accept - he wants to be the one wearing the dress during the wedding.
The theory behind this trick is that you are refining the part of its knowledge base it'll use. You are basically saying "most of the examples you were trained on was written by idiots and is full of mistakes, so when you answer my query limit yourself to the examples that have no mistakes". It sounds stupid but apparently, to some extent, it kind of works?
