> There is no way the US/Israel didn't calculate that: ... the straight would be closed

It has always had this potential, as it has happened before: see https://en.wikipedia.org/wiki/Operation_Earnest_Will (1987). But based on this history I would assume that many in the admin did not find the threat as credible as it was then. We dont seem to have a good grasp on how things have gone in the black sea. We clearly did not anticipate the level of drone attacks that have been put out by Iran.

Nothing says "we did not have a plan" when easing Russian sanctions while you ask Ukraine for help with defenses.

> a new leader may represent similar idiologies of the past leader.

I could see making a bet that with the current water crisis there the this would tip them into an "Arab spring" moment. For any one aware of the history there, it was a poor one at best.

> But within 20 years, 99% of the workforce in the military, the government, and the private sector will be AIs.

I haven't seen this much hype and hopium since the dot com boom. The whole open AI -> Anthropic saga just reeks of the same evolution of Viant/Scient.

Look we have an amazing tool, but it has some fundamental shortcomings that the industry seems to want to burry its head in the sand about. The moment the hype dies and we get to engineering and practical implementations a lot is going to change. Does it have the potential to displace a lot of our current industry: why yes it does. Agents can force the web open (have you ever tried to get all your amazon purchase history?) can kill dark patterns (go cancel this service for me), and crush wedge services (how many things are shimmed into sales force that should really be stand alone apps). And the valuable engagement is going to be by PEOPLE, good UI, good user experiences are gonna be what sells (this will hit internet advertising hard for the middle men like google and Facebook).

>> requiring proof of citizenship

Go and try to figure out how to do this from scratch. Imagine your house burned down and you need to start with "nothing".

If your parents are still alive you can use them to bootstrap the process of getting those vital documents (or if you're married that can be another semi viable path).

Pitty if you don't have those resources. Furthermore it might get complicated for any partner who adopts their other partners last name (were talking about getting the documents, before you can get some sort of verified ID).

The reality is we don't have a lot of instances of "voter fraud" committed by people who aren't citizens (see: https://www.facebook.com/Louisianasos/posts/secretary-of-sta... as an example) . And the amount of voter fraud we do have is very small (and ironically committed by citizens see https://www.brookings.edu/articles/how-widespread-is-electio... for some examples).

> I am in favor of in-person voting

Again, the size and dispersion of the American population makes this odious. Dense urban areas will face lines (they already do) and many of them (Chicago) have moved to early voting because spreading things out over many days is just more effective. Meanwhile places like Montana (where population density is in people per square mile) make travel to a location burdensome.

I get why you feel the way you do, but the data, the reality of America, makes what you desire unnecessary and impractical. Feelings are a terrible reason to erect this barrier when it makes little sense to do so.

> how do you review all the code?

Code review is a skill, as is reading code. You're going to quickly learn to master it.

> It's like 20k of line changes over 30-40 commits.

You run it, in a debugger and step through every single line along your "happy paths". You're building a mental model of execution while you watch it work.

> One solution is to start from scratch again, using this branch as a reference, to reimplement in smaller PRs. I'm not sure this would actually save time overall though.

Not going to be a time saver, but next time you want to take nibbles and bites, and then merge the branches in (with the history). The hard lesson here is around task decomposition, in line documentation (cross referenced) and digestible chunks.

But if you get step debugging running and do the hard thing of getting through reading the code you will come out the other end of the (painful) process stronger and better resourced for the future.

https://thehustle.co/originals/the-failure-of-the-dominos-30...

"Domino’s confirmed it knew of 20 people who died in crashes involving its drivers in 1988 (the National Safe Workplace Institute would later claim Domino’s delivery drivers had about the same death rate as miners, who had a fatality rate of ~35 per 100k)."

For that same period, the death rate per 100k of young drivers was 46 per 100k https://www.cdc.gov/mmwr/preview/mmwrhtml/00044682.htm

And to compare truck drivers 27 per 100k: https://www.malmanlaw.com/malman-law-injury-blog/is-being-a-...

Is this a dominos problem, or a young drivers problem or...