Indeed, the correct term here is nullipotent.

I haven't tried this yet, but I wanted to say I think there's a lot of potential in this space. There's so much friction with the current popular solutions...and yet it's so hard to justify trying some of the newer and less popular ones.

I wish you luck because there are a lot of good ideas in here. Running locally and remote debugger are the most exciting to me.

I'd argue that Tenerife was due to taking off (in bad weather), not landing. But of course, a bunch of planes landing at the same airport without ATC sounds quite dangerous.

There were a lot of contributing causes, but it wouldn't have happened if not for the fact that Tenerife North airport was massively overcrowded due to Gran Canaria airport being suddenly closed (for unrelated reasons) and flights forced to divert.

The issue wasn't with landing specifically; I'm just using it as a general example of issues caused by havoc situations in aviation.

This sounds like a very nice compromise actually. I'm surprised it helped with abuse though, since there's a lot of email providers that are easier to create an account with than gmail.

It's trivial to defeat though, all you need is your own domain and an email provider that supports catch all email addresses.

A big part of handling abuse is to recognize that you cannot win - all you can do is better. And a big part of abuse is just raising the bar of sophistication required to abuse you. We went from "any random script kiddie with a gmail account gets infinite accounts easily" to "now someone has to use a custom email domain" (which is easy for us to just banhammer the domain), which both requires sophistication and money. And it makes the banhammer-swing more on par with the amount of effort they have to put in to evade it - banning the domain means go find another domain and pay another registrar fee.

Well, you have to go out of your way to prevent it. The sub-addressing complexity is on the email provider side; ticketmaster doesn't have to do anything for it to work except not reject valid email addresses.

In my experience, most but not all sites will accept "+" email addresses.

I think that's exactly correct. You either do split queries (with more latency) or you do a join (and risk Cartesian explosion). Most ORMs should do this for you.

Wouldn't it cause the cost of consoles to go up and the cost of games to go down, in a way that on average has no significant effect to consumers?

As long as it applies to all companies, why is it an issue?

Because you'd be paying for the games themselves, not also reimbursing the console manufacturers.

I think you misunderstand how the cut works and why they’re subsidized.

Take a look at PC games. Steam also takes a 30% cut, which is the same as what the console makers take. Steam doesn’t have to pay anyone back. The 30% is a pretty long standing cut and is about the lowest most incumbents have gone despite reductions in other costs.

The subsidizing of the console is pre-factored into that 30% cost. Historically console manufacturers have also reduced the amount of subsidization over the course of a generation without affecting the price of the games. The subsidizing is to get it into as many homes as possible, but even a few games purchased over the lifetime of a console would negate any subsidy.

There’s no precedence or indication other than wishful thinking that removing console subsidies wouldn’t remove that cut.

I don't think that's how it works... It's a checksum, not letting you check if each section is part of the key.

At worst, the key would have some portion less entropy since there's a lot of bits used for checksums.

Can you (or someone else) explain what the alternatives are? How can I write unit tests without mocks or fakes?

They might mean that rather than using a mock, use a real typed object/instance of a real thing and inject it into the unit that you’re testing. Admittedly, that might meet the definition of a fake/mock once you get down to the level of testing something that needs db access. Another way of interpreting that is that you can use in memory versions of your deps to mirror the interface of your dependency without needing to repeatedly, and possibly haphazardly mock certain functions of your dependency.

I strongly agree with this.

I would add that, at least for me, planning each day out is beneficial as well. When I don't have a plan for a day, I often will sit there, not really doing anything, and not sure what to start doing. This typically ends when I get distracted by something (maybe a question on Slack), and overall leads to some very unproductive days.

Even a simple high-level plan, like "today I want to get these tickets ready for review and work on this RFC", is incredibly helpful for me. A weekly plan may be even more effective, but I struggle to plan that far in advance.