Earlier quoted context omitted.
> I hate that. When I program my computer, I specify all the steps to accomplish something. If it's too verbose, then I abstract it in a function. > I even add comments to make sure that a human reader easily and completely understands what I do. Yeah, honestly, any single time I read a maths-related paper I feel like I would be better off with an example, well-written, implementation in any programming language. The…
Because mathamaticians have thousands of years of history where they learned how to write math in a way that is readable to other mathamaticians. Software engineering is a very different activity from the math that mathamaticians do. It makes sense that it has a different standard for what mathematicians do. There are undoubtadly ways to improve mathematics, but it seems highly arrogant to say that your <100 year old…
Even if a domain is over 1000 years old, some domains have only existed for about 150-200, which means that before, the world did not have the benefit of those lenses. Now that we have them, it is only natural to mix and match to see if easy insights come out.
Is there not also a risk of arrogance to demanding that another field understand everything about yours before attempting to share knowledge? It suggests that the time of day is so limited, and you have business of such importance, that you will not hear ideas below a threshold. That seems like a fine strategy for accruing quality up to a point, but it can run into local maxima more easily.