Would not be surprised if it's getting confused about a wallet sponsorship

That would make it impure

It's what happens when content is url encoded and not decoded again later. It's easy to do by accident because you can't tell if a string is already url encoded in any general way, so the processes responsible for sending and receiving need to agree on how/when to encode and decode (i.e. they both have the power to break it for the other)

Just use a password manager

IMO every datetime should be in utc, and variables for datetimes should either be suffixed "Utc" or have a type indicating their time zone (DateTimeOffset or UtcDateTime etc). Conversion to local time happens at the last possible second (e.g. in the view model or an outbound http request parameter). Of course that doesn't solve the problem of interoperating with other ~~morons~~ programmers who don't follow these rules, but it keeps things a lot neater locally.

Scheduling based on regional time conventions (holidays, weekends, etc) is just not great though.

It's a great book. It's just got some fantastic competition.

IntelliJ IDEA isn't really more generic than PyCharm. It's a Java IDE built on the generic IntelliJ platform. You can load different language plugins in both.

Alright buddy. Here's your "whole carrot dipped in ranch" salad.

Try to stay on topic instead of resorting to analogies.

Failure to comprehend abstraction while arguing against math education. Yep, that checks out.

Assuming you mean a boss at the end of act 2 / beginning of act 3, Balthazar

I got pushed off the ledge a few times. What worked for me was, while the first character was stuck in dialogue, the rest of my party would sneak in and position advantageously before starting the fight mid-dialogue on my own terms. It was indeed bullshit, but not nearly as bullshit as me reloading for 20 mins convincing a boss to kill themselves, so I think the game and I can call it even.

I also completed a few tough early fights with 2 mage hands and a cliff, so really, I'm pro-shoving all the way.

Let's name the goats Alice and Bob. You pick at random between Alice, Bob, and the Car, each with 1/3 chance. Let's examine each case.

• Case 1: You picked Alice. Monty eliminates Bob. Switching wins. (1/3)

• Case 2: You picked Bob. Monty eliminates Alice. Switching wins. (1/3)

• Case 3: You picked the Car. Monty eliminates either Alice or Bob. You don't know which, but it doesn't matter-- switching loses. (1/3)

It comes down to the fact that Monty always eliminates a goat, which is why there is only one possibility in each of these (equally probable) cases.

From another point of view: Monty revealing a goat does not provide us any new information, because we know in advance that he must always do so. Hence our original odds of picking correctly (p=1/3) cannot change.

In the variant "Monty Fall" problem, where Monty opens a random door, we perform the same analysis:

• Case 1: You picked Alice. (1/3)
  • Case 1a: Monty eliminates Bob. Switching wins. (1/2 of case 1, 1/6 overall)
  • Case 1b: Monty eliminates the Car. Game over. (1/2 of case 1, 1/6 overall)
• Case 2: You picked Bob. (1/3)
  • Case 2a: Monty eliminates Alice. Switching wins. (1/2 of case 2, 1/6 overall)
  • Case 2b: Monty eliminates the Car. Game over. (1/2 of case 2, 1/6 overall)
• Case 3: You picked the Car. (1/3)
  • Case 3a: Monty eliminates Alice. Switching loses. (1/2 of case 3, 1/6 overall)
  • Case 3b: Monty eliminates Bob. Switching loses. (1/2 of case 3, 1/6 overall)

As you can see, there is now a chance that Monty reveals the car resulting in an instant game over-- a 1/3 chance, to be exact. If Monty just so happens to reveal a goat, we instantly know that cases 1b and 2b are impossible. (In this variant, Monty revealing a goat reveals new information!) Of the remaining (still equally probable!) cases, switching wins half the time.

Meta fine. Meta drama bad. subredditdrama, shit__say, etc.