Minor correction: Satellites don't go in every direction; they orbit. Probes or spaceships are more appropriate terms.

As you say, we know what’s there. I need the author to tell me why it’s there, and perhaps what other alternatives were abandoned because they didn’t work.

You know, so I don’t waste a day finding out for myself why you didn’t just do ${obvious}.

The commit message lives with the code. The number of times in my career that a company has migrated, changed, consolidated, or otherwise made all those links in commit messages obsolete, well I don't quite yet need two hands. But I see a lot of dead ends to context in code bases.

From my memory banks after close to 20 years:

    SoyDecorator: CoffeeDecorator {
        price: Cents { price + 90¢ } // Soy adds 90 cents to the price
    }

I don't know if it's still the case, but there was an annoyance where you couldn't have a type with the same name as the package. But that is hardly a lack of namespaces.

Edit: or, rather, in my experience the author of the code often finds the bugs when explaining it to the person standing next to them. This goes away in the GitHub-style pull request.

A quick couple of examples: multi-selection and drag-n-drop, both all but broken on desktop.

https://www.youtube.com/watch?v=8BxDpOu3cD0&t=320

(It won the Oscar for Best Sound that year.)

We could discuss that aspect—sharing accounts on computers that don’t belong to me—but that’s why I’m often thwarted from reading content. I have the account, just not on me.