lot of clutter. Use namespaces according to the policy described below. Terminate namespaces with comments as shown in the given examples. See also the rules on Namespace Names. 8 Unnamed Namespaces • INT_MAX Comments Though a pain to write, comments are absolutely vital to keeping our code read- able. The following rules describe what you should comment and where. But re- member: while comments are very variables is much better than using obscure names that you must then explain through comments. When writing your comments, write for your audience: the next contributor who will need to understand your code

Line length Parentheses Indentation Blank Lines Whitespace Shebang Line Comments Classes Strings Files and Sockets TODO Comments Imports formatting Statements Access Control Naming Main Important Note link￿ Maximum line length is 80 characters. Exceptions: • Long import statements. • URLs in comments. Do not use backslash line continuation. Make use of Python’s implicit line joining inside parentheses joining. x = ('This will build a very long long ' 'long long long long long long string') Within comments, put long URLs on their own line if necessary. Yes: # See details at # https://www.example.com

type (@interface). 2. The term comment always refers to implementation comments. We do not use the phrase “documentation comments”, instead using the common term “Javadoc.” Other “terminology notes” will makes the code easier to read and understand, although Unicode escapes outside string literals and comments are strongly dis- couraged. Tip: In the Unicode escape case, and occasionally even when actual ends, the indent returns to the previous indent level. The indent level applies to both code and comments throughout the block. (See the example in Section 4.1.2, Nonempty blocks: K & R Style.) 4.3 One

use them 10. General Layout and Ordering 11. Commenting Guidelines: all comments begin with # followed by a space; inline comments need two spaces before the # 12. Function Definitions and Calls 13. Function Guidelines Comment your code. Entire commented lines should begin with # and one space. Short comments can be placed after code preceded by two spaces, #, and then one space. # Create histogram of frequency tines). Function Documentation Functions should contain a comments section immediately below the function definition line. These comments should consist of a one-sentence description of the function;

Criticism  Different Kinds of Feedback  Casual discussion of early ideas  Comments on paper drafts  Reviewer comments (good and bad)  Example Compressed Linear Algebra  SIGMOD Reviewer 2 (REJECT) seriously consider all feedback (in doubt agree), and answer with facts / ideas how to address the comments  Revision (conditional accept): address all revision requests Structure of Scientific Papers

Understanding (see above) + strengths and weaknesses  #3 Write summary, strong/weak points, detailed comments (incl reading) Scientific Reading What? How? What’s Wrong? 6 706.015 Introduction to Scientific say something nasty … (ignore good parts, focus on weaknesses)  Silent but deadly (low scores, no comments)  The Natives are Restless (recommend full rewrite by native English speaker)  The Referee Moves