As stated in the README of the git source code repository, Linus Torvalds came up with the name "git" and said that its meaning depended on your mood. It can stand for:

"global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.

"goddamn idiotic truckload of sh*t": when it breaks.

If you want to see for yourself just how accurate this is, just google something like "why do people hate git" and you'll find plenty of funny (and desperate) comments and stories.

If you're an SRE or DevOps engineer, you'll usually find yourself writing scripts to automate tasks. But a collection of scripts, probably written by different members of the team, with different standards and tools, will soon become unmaintainable and trigger conversations such as "Can the script do this?" or "How do I make this change?". Sometimes, you may even have those conversations with yourself because after a while you no longer understand your own code.

If you think of your scripts not so much as a set of commands run one after another but as command-line applications, which should meet certain standards and follow good coding practices, they'll become much more user-friendly and maintainable.

Disclaimers:

• This list should be specially useful for people writing scripts from scratch. If you're working on a big project as a developer, it's likely that many of the tools I'll describe (or some alternative) are already in use. But if the