[wesnerm2]

Git IS heavily used outside of software engineering.

Marketers and documentation writers use markdown and git for building websites and books.

Data scientists use git for their notebooks.

Operations use git for their deployment scripts.

Git isn't the best for office documents. Revision marking (aka, change tracking), document comparisons, and merging are all available in Office suites. Git isn't really used here because there features predate Git, operated on binary files or complex XML documents (neither of which are conducive to diffs).

Git isn't good for databases or data lakes. The files are huge and typically aren't modified (CSV) or are binary/compressed (Parquet).

[p-e-w]

> Marketers and documentation writers use markdown and git for building websites and books.

In the software industry, sure. Outside of it, I'm willing to bet that 95% of marketers have no idea what Git is.

And Markdown? This again seems highly specific to the tech/open source/blogging microcosm. In the "real world" it's all Microsoft Word, or DTP tools for people who are closer to the printing process.

[vertere]

It seems like broader adoption of Markdown (or similar lightweight markup) would greatly help with broader adoption of git.

[bjourne]

> Git IS heavily used outside of software engineering.

How many of these use git correctly?

[dagw]

How many people in software engineering are using git 'correctly', and what is 'correctly' for that matter? At the last place I worked different projects in different offices had all developed their own git workflows and none of us could agree on who was "Doing it Wrong".