When communicating over Slack my colleagues would send me a ticket number in Jira or a link to some code snippet on GH. When I have to share the same (or similar) stuff — I can easily provide the exact link to the ticket, with its description, I can quickly retrieve some relevant data from that ticket, if I'm adding some notes. When I'm sharing a link to a code snippet, I can easily retrieve the fully-qualified namespace and the name of the function, so the url is not some arbitrary incantation that my teammates have to guess about before clicking on it — it contains the exact piece of information they may like to see even before opening it.
When someone shares 'some incantation' with me, I don't even hesitate — I delegate the task to Emacs, and it is smart enough to recognize that a piece of plain text like "XYZ-146" is a Jira ticket, that "RFC-6364" is a document, that a github url is a link to a PR — with a single keystroke I can browse the jira ticket, read RFC document, explore the changes in the PR. I can invoke an LLM on the spot to summarize the points of the RFC document, to give me some insight to add a comment to the PR review.
All that without a hassle, all that done with simple keystrokes, all in one place. I can easily copy relevant information into my notes, I can grab stuff from my notes and share with my colleagues, easily converting Org-mode markup into Markdown without even blinking. The flow is there. And that flow also contributes to the general well-being of my teammates. I can assure you, they are happier with me using Emacs, even though most of them don't even know anything about it.
> the value proposition of emacs simple is no longer there
My main point from the get-go was that most people don’t even realize what a ‘value proposition’ there is.