Obviously this has security implications, but I don't ordinarily search for anything sketchy on my iPhone so I'm personally not too worried about it.

Google Maps on the iPhone has a similar problem where a banner notification can block the section at the top that shows the next turn. If it's persistent (e.g., a calendar reminder), you have to try to swipe it away while driving without clicking on it by mistake. I guarantee multiple people have crashed because of this.

Whoever at Apple thinks that anything at all should override navigation for more than a couple of seconds without explicit user action is an idiot.

It is certainly true that they did a poor job communicating this change to users (I did not know that the default was “high” before they introduced it, I assumed they had added an effort level both above and below whatever the only effort choice was there before). On the other hand, I was using Claude Code a fair bit on “medium” during that time period and it seemed to be performing just fine for me (and saving usage/time over “high”), so it doesn't seem clear that that was the wrong default, if only it had been explained better.

(This is absolutely bonkers though – the experience of using an e-reader has basically not gotten better since 2008 when I got my first Kindle. There are still glaringly obvious usability issues which nobody has spent any time innovating on.)

I'm also not sure that anyone was claiming automobile technology itself was bad, just that in many places at many times it has been used in suboptimal and harmful ways.

Someday I should go buy some produce from each store at peak season and try them side by side.

I promptly went and fixed this before doing any more work, because I know if I was put in that situation I would refuse to do any more work until I could actually use the app properly. In general, if you wouldn't be able to solve a problem with the tools you give an LLM, it will probably do a bad job too.

At every place I have ever worked (as well as my personal life), the backlog was 10 times longer than anyone could ever hope to complete, and there were untold amounts of additional work that nobody even bothered adding to the backlog.

Some of that probably wouldn't materialize into real work if you could stay more on top of it – some of the things that eventually get dropped from the backlog were bad ideas or would time out of being useful before they got implemented even with higher velocity – but I think most companies could easily absorb a 300% increase or more in dev productivity and still be getting value out of it.

I'll note this only applies to new sessions though – if you do /clear and start working on something else it doesn't re-apply plan mode (I kind of wish it did)