I ran this on the repo I have open and after I filtered out the non code files it really can only tell me which features we worked on in the last year. It says more about how we decided to split up the features into increments than anything to do with bugs and “churn”.

And that’s where my suspicion stems from.

An equivalent original human piece of work from an expert level programmer wouldn’t be able to do this without all the context. By that I mean all the all the shared insights, discussion and design that happened when making the compiler.

So to do this without any of that context is likely just very elaborate copy pasta.

Depends what we mean by specialist. If it frontend vs backend then maybe. If it general dev vs some specialist scientific programmer or other field where a generalist won’t have a clue then this seems like a recipe for disaster (literal disasters included).

Social movements don’t just happen from grassroots these days. They’re seeded by foreign states. A simpler solution would be require ids for social media posting. If you don’t provide an id you get a limited number of views.

And I don’t see anything wrong with a preventative system in principle, we should be able to join up social services information with policing, because we have had cases where a mass murderer has been known to multiple services.

Edit: probably not ids but a token that verifies my nationality would be enough.

https://andrewlock.net/working-with-stacked-branches-in-git-...

Another commenter posted this link which was a bit more succinct

https://blog.hot-coffee.dev/en/blog/git_update_refs/

There isn’t much to it though, you just go to the branch and run git rebase with the update refs flag.