Similarly, I don't read the whole file a function is in while editing it in an IDE, why should a coding agent get the whole file polluting its context by default?

In software there's a lot more emphasis on post-hoc fixes rather than up front validation, in my experience.

If Blockbuster had kept pouring money into the new service, maybe it would have lost it all - I see no reason to think Blockbuster's movie rental franchise business would have 'transferrable skills' to allow it to succeed at streaming.

If it had been trying to pivot into a pizza delivery business (perhaps more transferable, in terms of locating franchises etc) would Icahn still have been 'killing' it?

My point is, maybe it was already dead and Icahn just prevented it from wasting a lot of money on the way down the drain.

I've seen a lot of 'fixes' for 10 year old 'garbage' that turned out to be regressions for important use cases that the author of the 'fix' wasn't aware of.

Now that photos and videos can be faked, we'll have to go back to the older system.

Reviewers wanting to pull and run many PRs makes me think your automated tests need improvement.

I think the sensible option is making death a taxable event, rather than borrowing (with perhaps exceptions for the family farm, but not for the family billion dollar business).

And the second best solution is eliminating the step-up basis, which without deemed disposition at death is just a free gift of capital gains tax rebates to heirs of the most wealthy.

I.e. investors have assigned roughly zero probability to CrowdStrike bearing the full cost of this incident, and set the market price accordingly.

It was always fun to hit the interviewer with this, it’s exponentially faster than the memoization they were usually expecting.

Work that is unattractive would presumably still be incentivized by higher wages.