sambellll

> Seems like the real reason it performed worse in this simulation is that when they implemented destination dispatch, they assigned an elevator at time of request, and had no system for reviewing and updated that assignment.

I don't think it's possible to have destination dispatch AND update assignment together, in the real world.

- If the user clicks floor 26 and you tell them to wait at elevator G, you can't really tell them to move to F if it's taking too long.

- But if you don't tell them an elevator to wait at, then you'd need them to run around what is possibly like 5-8 elevators to find which one is going to their floor? That's obviously not realistic.

So then you're going to just have them get in the first one that opens? But then that's just the same as an up/down button.

To me this is like a good software engineer using AI.

The fact that they use it doesn't make what the result is any worse or less trustworthy - arguably it makes it better.

It only becomes a problem if they offload all of the thinking to AI.

It's just odd to see a company buy a product and then promptly nuke it.

Here to say the same thing.

I built an app a few years ago and needed some sort of DB to store around 50 million records that had ~10k reads+writes per month with 1 index. It cost me something like $50 to load it up initially, and then something stupid like 10 cents/month to maintain.