Note for "Some Remarks on Writing Mathematical Proofs"

John M. Lee is a famous mathematician, who bears the reputation of writing the classical book "Introduction to Smooth Manifolds". In his article, "Some Remarks on Writing Mathematical Proofs", he gives us concrete and complete suggestions about how to write mathematical proofs in a concise and unambiguous way. In my opinion, most of them are quite pertinent and enlightening. In the following, I‘ll list some key points from this article and some comments are also appended.

  • Identify your audience: know your audience is and what they already know.

    Comment: this is very important! For audience at the beginner level, explanations should include minute details, which are similar to the annotations in a traditional Chinese book and usually their text length largely exceeds the original text. Don‘t be afraid that the explanations may look naive and trivial in the eyes of expert. Actual examples are also recommended to be provided. Vivid illustrations are quite helpful for the ease of understanding. For professional mathematicians, the writing should presented in a rather formal and abstract way for the purpose of clarity and brevity. We should use well-defined and unambiguous mathematical symbols to describe facts by starting from definitions, then lemmas, theorems etc. and gradually unfolding the complete logical network.

  • Write in paragraph form
  • Avoid most abbreviations like "s.t.", "w.r.t", etc. However, "e.g." and "i.e." are still acceptable.

    They are suitable for handwritten in a notebook or on a blackboard, but not suitable for a formal mathematical writing.
  • State what you‘re proving, i.e. restate the theorem to be proved in a formal way before the proof starts.
  • Label your theorems by using the following keywords (generally speaking, they all mean the same thing, that is a mathematical statement to be proved from assumptions and previously proved results):
    • Theorem: an important proposition.
    • Proposition: a result that is interesting in its own right, but not as important as a theorem.
    • Lemma: a result that might not be interesting in itself, but is useful for proving another theorem.
    • Corollary: a result that follows easily from some theorem, usually the immediately preceding one.

    For handwritten mathematics, underline these keywords with an emphasizing effect.

  • Show where your proofs begin and end

    The proofs start with Proof and end with \(\Box\). In \(\LaTeX\), this is done automatically by various predefined mathematical environments. Handwritten mathematics should also follow the same convention.
  • Why is it true?

    Every mathematical statement in a proof must be justified in one or more of the following six ways:

    • by an axiom;
    • by a previously proved theorem;
    • by a definition;
    • by a hypothesis (including an inductive hypothesis or an assumption for the sake of contradiction);
    • by a previous step in the current proof;
    • by the rules or logic.

    Comment: we can see the logical rigorousness in mathematical proofs.

  • Include more than just the logic

    Mathematical proofs are not simply stacking formulas. The formulas should be concatenated by meaningful and logical descriptions.
  • Include the right amount of detail

    Knowing the audience is a precondition.
  • Writing mathematical formulas
    • Every mathematical symbol or formula should have a definite grammatical function as part of a sentence. Therefore, if they end a sentence or a clause, a punctuation mark must be followed.

      Read aloud each sentence is a good way to check.

    • Do not begin a sentence in a paragraph with a mathematical symbol. For example, "\(l\) and \(m\) are parallel lines" is not good, write "The lines \(l\) and \(m\) are parallel" instead.
    • Avoid writing two in-line formulas separated only by a comma or other punctuation mark. For example, "If \(x \neq 0\), \(x^2>0\)" is not good, write "If \(x \neq 0\), then \(x^2>0\) instead.
    • Do not connect words with symbols. For example, "If \(x\) is an function \(\in X\)" is not good.
    • Symbols for logical terms like \(\exists\) (there exists), \(\forall\) (for all), \(\wedge\) (and), \(\vee\) (or), \(\neg\) (not), \(\Rightarrow\) (implies), \(\Leftrightarrow\) (if and only if), \(\ni\) (such that), \(\because\) (because) and \(\therefore\) (therefore) should only be used in handwritten mathematics. In formal mathematical writing, they should be replaced with English words.

      Exception: \(\Rightarrow\) and \(\Leftrightarrow\) can be used to connect complete symbolic statements. For example:

      We will prove that \((a) \Leftrightarrow (b)\).

时间: 2024-08-23 13:29:29

Note for "Some Remarks on Writing Mathematical Proofs"的相关文章

Linearizability(also known as strict or atomic consistency)

In concurrent programming, an operation (or set of operations) is atomic, linearizable, indivisible or uninterruptible if it appears to the rest of the system to occur instantaneously. Atomicity is a guarantee of isolation from concurrent processes.

为什么深度神经网络难以训练Why are deep neural networks hard to train?

Imagine you're an engineer who has been asked to design a computer from scratch. One day you're working away in your office, designing logical circuits, setting out AND gates, OR gates, and so on, when your boss walks in with bad news. The customer h

没有银弹:软件工程的本质性与附属性工作

NO SILVER BULLET: ESSENCE AND ACCIDENTS OF SOFTWARE ENGINEERING It's adapted from berkeley . If you want to know more, you visit the orignal articlehere. if you want to understand this article more clear please  first read this chinese article here.

paper reading(1) - Combining Sketch and Tone for Pencil Drawing Production

目录 Combining Sketch and Tone for Pencil Drawing Production paper content understanding algorithm understand report outlines paper writing strategies note Abstract Introduction Related Work Combining Sketch and Tone for Pencil Drawing Production paper

不具备数学和算法知识能否成为优秀的开发人员(2)

Knowledge of algorithms has very little to do with programming skill.  As some random dude* on the internet once said:  "When in doubt, use brute force."  Let's unpack what this means. A good programmer knows how to implement a dictionary algori

两种不同的思维方式

学计算机网络有两种不同的思维方式,一种是自顶向下,一种是自底向上. 自顶向下是先学应用层,从网站.ftp.telnet.email等网络应用开始讲解,然后到运输层.网络层.数据链路层.物理层,从人们最熟知的内容开始,然后逐步引导人们到达自己陌生的二.三.四层只至物理层.这种方式是容易被学生接受的,因为先从学生熟知的网站开始,符合人类的认识特点:从感性思维到理性思维. 但是自底向上却是先讲物理层.数据链路层.网络层.运输层.应用层,这么讲下来,多数中国老师习惯这么讲解,结果学生们都给整晕了,最后都

Professional C# 6 and .NET Core 1.0 - 40 ASP.NET Core

本文内容为转载,重新排版以供学习研究.如有侵权,请联系作者删除. 转载请注明本文出处:Professional C# 6 and .NET Core 1.0 - 40 ASP.NET Core ----------------------------------------------------------------------- What's In This Chapter? Understanding ASP.NET Core 1.0 and Web Technologies Using

Property Finder – a Cross-Platform Xamarin MonoTouch Mobile App

Developers are now finding themselves having to author applications for a diverse range of mobile platforms (iOS, Android, Windows Phone, …), each of which have their own ‘native’ development languages, tools and environment. There is an ever growing

写出好的 commit message

为什幺要关注提交信息 加快Reviewing Code的过程 帮助我们写好release note 5年后帮你快速想起来某个分支,tag或者 commit增加了什么功能,改变了哪些代码 让其他的开发者在运行 git blame 的时候想跪谢 总之一个好的提交信息,会帮助你提高项目的整体质量 基本要求 第一行应该少于50个字. 随后是一个空行 第一行题目也可以写成:Fix issue #8976 喜欢用 vim 的哥们把下面这行代码加入 .vimrc 文件中,来检查拼写和自动折行 autocmd