My guess it's just the emergent behavior that results when a company doesn't provide developers time to fix bugs.
If their week is already booked full just trying to keep up with the roadmap deadlines, a bug ticket feels like being tossed a 25lb weight when you're drowning.
You could say: "but have pride in your work!"
But if your company only values shipping, not fixing, that attitude doesn't make it through the first performance review.
I'm not sure what this is representing here. Is it a way to encode a clickable link to chat with `bank` about `service/payments` with a few additional args attached?
As a heavy LaTeX user (phd student; can't escape it), I'm convinced that there is a small enough subset of LaTeX that actually gets used day-to-day that someone could figure out a way to shim it into something like Markdown.
And then, for the LaTeX that you can't shim in, just have some escape hatch that sends fragments out to a renderer.
If I could only have:
* Math mode
* Citations and Bib files
* Labels and References
Then I'd be willing to go through a lot of extra pain to get all the weird tables and precise image placements that are inevitable in a 2-column ACM format.
EDIT: Having just investigated Pandoc, which many here are talking about, I realize this might be exactly what I've been looking for :)
I think this behavior is the better route because it accommodates both crowds. The line-wrap folks can just press enter twice; no biggie. But the console and vim users of the world can continue using line-breaks the way that work best for their environment.
On the flip side, making a single enter start a new paragraph wouldn't really help the GUI users (what's the difference between one line break and two, really?) but it would really hurt the console users of the world
One interesting aspect of LLMs is that each one, weights frozen, can be thought of as a single developer whose work you have already evaluated.
The cost of finding, evaluating, and negotiating with a new human is tremenous.