The author also suggests simulating flood walls. That is also a very .. local suggestion.

Deleting data is also a very easy way to not get GDPR compliance issues. Data is a cost and a risk, and should be minimised to what is actually relevant. Storage is the least part of the cost.

Not an issue if you're not building SaaS

Depends on your jurisdiction I suppose. If you are in EU it's a question if you have PII or not - if you are a SaaS or not is totally irrelevant.

I disagree. I find accepting extra random bytes in places to be just as harmful. I prefer APIs that push back and tell me what I did wrong when I mess up.

It is a reference to Torvalds making an appearance on the LTT youtube channel, intentionally getting the LTT meaning wrong.

If nothing else, the history recap is absolutely brilliant.

No, but both demand and space to grow stuff are very much limitations in that space. They are not even close to being that for programming.

Right, what is needed is something trie-like, with the root being the most fine-grained call.

Nothing stops you from doing both renade and merge commits.

Except perhaps crappy gui options in GitHub. I really wish they added that option as a button.

I wish github created automation for this flow like they have for other variants.

But they have, with pull requests. When you merge a pull request it is done via the "subtree" merge strategt, which preserves partial commits and also does not flatten them.

There is no button to rebase, and then merge with a merge commit no-ff.

The images would be published by Grok, which is part of Twitter. They are responsible for what they themselves publish. Hence Twitter is the obvious choice of where to direct the subpoena.