I've never worked with anybody else that uses it, so my uses have settled on things that don't require much interaction with other workflows: taking my own note

I've never worked with anybody else that uses it, so my uses have settled on things that don't require much interaction with other workflows: taking my own notes in org-mode, and general text editing/viewing (config files, batch files, plain text files, logs, etc.). I do use a Perforce minor mode to simplify checking files out and examining file history. I have a helper function to paste image from clipboard into org document (save as timestamped png file somewhere sensible document-relative, insert link into document), so it's somewhere safe and I can add per-image notes and so on. I do this when I'm building up sets of screen grabs to later paste into Teams/Jira/Confluence/Slack and the like. That's about it. Main remaining annoyance that I'd like to fix is a way of exporting an org section as Markdown, so I can paste anything interesting into Slack and have the formatting come out sensible. For programming, professionally I've never used it all that much. It's much simpler all round to use whatever the rest of the team is using, which these days typically means Visual Studio or Visual Studio Code, and both are workable. I get enough value out of the zero-effort code browsing/code completion/integrated debugger/etc. that I don't mind dealing with the not-quite-as-nice editing experience and ropey UI. I can always (and often do) load a file into Emacs if I have some specific editing task I'd like to do. (In the past I have used it a bit for working with stuff like MEL/MaxScript and proprietary/in-house stuff that's generally poorly supported by text editors. Not too hard to cobble together something workable in Emacs. I haven't had to do this recently though.)