Confusing Git Terminology (jvns.ca)

Article summary

The article discusses the confusing terminology used in Git, a version control system. The author highlights various terms and concepts that can be unclear, such as 'detached HEAD state', 'fast-forward', and 'ours' and 'theirs' during merging or rebasing. The article aims to explain these terms and provide clarity for users. The author also notes that Git's terminology can be confusing due to its complex and nuanced nature.

Main themes

• Git terminology
• documentation quality
• version control complexity
• command-line interface
• alternative documentation
• user experience
• system abstractions

What commenters say

• Git's terminology is confusing and can be a barrier to understanding the system.
• The official documentation for Git is often unhelpful and assumes prior knowledge.
• Writing clear and concise documentation is a challenging task that requires a deep understanding of the subject matter.
• Some users find Git's complexity and nuance to be a strength, allowing for powerful and flexible version control.
• The command-line interface for Git can be difficult to use and prone to errors.
• Alternative documentation sources, such as crowdsourced resources, can be more helpful than official documentation.
• Git's abstractions can be 'leaky', making it difficult to use the system without understanding its internal workings.
• The introduction of new commands, such as 'switch' and 'restore', can provide a more sensible interface for users.