Eggs demand is rather inelastic[0]: price has to go up by a lot for demand to go down. Per your link Cal-Maine Food doubled the revenue while selling roughly the same amount of eggs. Expenditure wouldn't double and so you would expect a drastic increase in profit.
> small egg producers may have had issues with avian flu keeping their fairly priced products off the shelves.
They didn't had the product though! This is main part of the reason price went up in 2022. It's either that or no eggs on the shelves.
> But if there are a bunch of children milling about an elementary school in a chaotic situation with lots of double parking, 17 mph is too fast, and the Waymo should have been driving more conservatively.
UK driving theory test has a part called Hazard Perception: not reacting on children milling around would be considered a fail.
Team X is responsible for feature Foo; feature Foo is slow; team X introduces Foo-preload, metrics go up, person responsible gets a bonus.
Multiply that by tens (or even hundreds) of teams and your app startup (either on desktop or mobile) is now a bloated mess. Happened to Office, Facebook iOS and countless others.
One solution is to treat startup cycles as a resource similar to e.g. size or backend servers.
> good example in the book explaining why a tick size is needed.
> Say that the current bid in the market is $20. If you want to buy at that price, you will be placed last in the list of orders. But since the sorting order is first by price, then by arrival time, you could get first in line by putting in an order with a price only slightly better than $20 (say $20.00000001).
I don't buy the argument.
Removing tick (or at least reducing it 100x) would put more emphasis on price discovery instead of speed.