I often use https://pgexercises.com/ to refresh my knowledge

For a company like google or facebook where everything is done "in house" this could be feasible. They had to create a lot of tooling to accommodate theirs engineers. But for a smaller company using tools like git, intellij, VScode, jenkins, etc and the tools for deploying your application doesn't the size and the complexity (number of files and their structure) eventually becomes a problem ? What's the size of their repo ? And at which point it becomes too much for most software to handle ?

Nice explanation

I always force myself to write good commit message. But I often ask myself if it is really useful or if I'm just too tight and want things to look good.

This standard might be useful for library maintainers in the cases stated here: https://www.conventionalcommits.org/en/v1.0.0-beta.2/#why-us...

Like having everyone using the same guidelines (code style) when writing code. This might also be useful if everyone use it.