From what I've seen, there are cars (telsa's) driving in a circle and you grab the next one available. Right now someone is driving it but at some point it's supposed to be autonomous. I think when the tunnel was first built you could drive your own car through it but as far as I'm aware they're not doing that anymore (I think it was just a publicity thing before the tunnels were close enough to completion to use).
But that's not a fair statement. Police did their work for centuries but it was nowhere near "fine" by modern standards and today there's a hundred ways more to commit crime
I feel like that requires a lot of coordination that I, in the midst of development, don't necessarily have. Taking my WIP and trying to build a story around it at each step requires a lot of additional effort, but I can see how that would be useful for the reviewer.
We can agree that we don't need those additional steps once the PR is merged, though, right?
I have literally never met a developer who does this (including myself). 99% of all PRs I have ever created or reviewed consist of a single commit that "does the thing" and N commits that fix issues with/debug failure modes of the initial commit.
You never design a solution which needs multiple architectural components which _support_ the feature? I do, and would make little sense to merge them as separate PRs most of the time as that would mean sometimes tests written on the inappropriate level, also a lot more coordination and needs a lot more elaborate description then just explain how the set of components work in tandem to provide the user value.
