Yes, but it is precisely because they are trying to get a slice of the pie from large studios that whatever happens to indie devs with their changes are just collateral damage

The title is actually perfect, but requires some context, after which you might appreciate its tongue-in-cheek beauty:

The author studied at CMU, where the proudly-paraded slogan for an introductory functional programming classes is "Functions are values", which has an almost cult-like status - appearing on their TA hoodies, laptop stickers, and so on.

Other classes soon caught on, first with the imperative programming class declaring that "Functions are pointers", then the introductory discrete math class's "Functions are tuples", and even "Functions are relations" from the databases class.

So viewed in this lens, passing up the opportunity to title it what it was would have been unthinkable.

Overleaf (https://overleaf.com/) is pretty popular for this, and also tracks things like edit history

Unfortunately, it doesn't allow you to bring your own editor, so I have to put up with its half-assed implementation of Vim.

It doesn't work super well during live collaboration, but Overleaf does allow git access to the underlying document: https://www.overleaf.com/learn/how-to/Using_Git_and_GitHub

> Many LaTeX tricks only get passed down from advisors to students, or from collaborators to collaborators.

Which is a great point on why the average quality of LaTeX homework submissions by undergraduates without any research experience usually makes for a less-than-ideal grading experience. And this is not about the nit-picky mistakes, but the visually glaring ones.

Wish I knew about autoref earlier, it also increases the area spanned by the hyperlink generated to the entirety of "Figure 1" instead of just "1" in the case of ref.

Interesting explanation on how it developed historically. I've seen mathbf used in some books, but I guess old conventions are hard to change.

Ah, I guess that's what happens when you do both Markdown and LaTeX in the same document! Thanks for pointing it out, I've also been pretty sloppy with hyphen and em-dash in normal writing. Maybe someone could write a similar post for online HTML content in the future?

Should be fixed now. First time hearing about Muphry's Law, definitely gave me a chuckle!

Works now. I do very little writing that requires math, although I did have occasion to present Muller’s Recurrence for a discussion on floating point arithmetic. The tip "Expressions Should Be Punctuated Like Sentences" is a good one, and generalizes somewhat to inline code or any inline figure or table in writing.

> First time hearing about Muphry's Law

It was probably a mipsrint.

Nope.

I knew that, was just playing the joke back. I guess it misfired. Or maybe not.

I missed it.

Thanks for flagging the image issue, I think there's an issue with the responsive image serving code that doesn't work consistently across browser. Temporarily disabling that for now & pushing a new update.

Also, you are right about using \mathrm{d}x. Another friend also just flagged it to me as well, I will update the post regarding this!

Refreshing might help (my guess is it might be due to img fallback issue), thanks for flagging this and I'll be investigating!