It suddenly starts talking about URLs, but it never really sets up the idea that we're using some kind of URL lookup service as an example. The way it introduces the memory limit feels similarly strange. At some point, it just says that we have 8GB of memory, but it does that halfway through the explanation, not as part of the setup of the problem we're actually solving.

i guess the problem is that once a teamp goes through the process of figuring out good UX for a certain flow, which can take time, that UX then becomes trivial to copy.

I'm legally blind, so I have my own bias here, but I think people really over-rely on sight. If you do want to listen to something while walking around a city, I can highly recommend bone conduction headphones, that keep your ears unblocked.

Being visually impaired, though, I'm grateful for cyclists who use their bell. It's immediately clear. For some reason, my brain takes slightly longer to process someone yelling "on your left!" or similar, than just a quick "ring ring".

I wonder whether at some point we'll get a translation model, that translates relatively vague requests into sound architectural decisions, with some embedded knowledge of the environment you're building in, and that can ask clarifying questions when there are multiple options with different tradeoffs.