do not share static data, use namespaces instead. For a header myproject/foo_bar.h, for example, write namespace myproject { namespace foo_bar { void Function1(); void Function2(); } } instead of namespace the waters, and, as always, consistency with related functions may require you to bend the rule. Write Short Functions Prefer small and focused functions. We recognize that long functions are sometimes is happening without having to first figure out exactly which overload is being called. You may write a function that takes a const string& and overload it with another that takes const char*. class

limit range to make you look good If there are multiple relevant parameters, show them all For log-scale you can’t start at 0 [J. Sommer, M. Boehm, A. V. Evfimievski, B. Reinwald, P. J. Haas: MNC: separated responsibilities)  Project  Pick from a given list of papers / groups of papers  #1 Write short summary paper (#pages = 2 * team-size, written in LaTeX, ACM acmart template, document-class

is very rarely correct to do nothing in response to a caught exception. (Typical responses are to log it, or if it is considered “impos- sible”, rethrow it as an AssertionError.) When it truly is appropriate fragment is capitalized and punctuated as if it were a complete sentence. Tip: A common mistake is to write simple Javadoc in the form /** @return the customer ID */. This is incorrect, and should be changed

nment, etc. 2 Cons: pylint isn’t perfect. To take advantage of it, we’ll need to sometimes: a) Write around it b) Suppress its warnings or c) Improve it. Decision: Make sure you run pylint on your code guidelines as functions. Decora- tor pydoc should clearly state that the function is a decorator. Write unit tests for decorators. Avoid external dependencies in the decorator itself (e.g. don’t rely on criteria: • not externally visible • very short • obvious A docstring should give enough information to write a call to the function with- out reading the function’s code. A docstring should describe the function’s

limitations  #1 Skimming (see above)  #2 Understanding (see above) + strengths and weaknesses  #3 Write summary, strong/weak points, detailed comments (incl reading) Scientific Reading What? How? What’s it harder to read  #2 Carefully Trim Down Draft  Write unlimited paper, then select, and revise  Write and revise section by section as you write  #3 Never Excuse Missing Content by “lack of space”

separated responsibilities)  Project  Pick from a given list of papers / groups of papers  #1 Write short summary paper (#pages = 2 * team-size, written in LaTeX, ACM acmart template, document-class  Example DEEM 2021, PVLDB 2022 Structure of Scientific Papers [Simon Peyton Jones: How to write a great research paper, MSR Cambridge] [Eamonn Keogh: How to do good research, get it published 26x or reduced memory requirements. Structure of Scientific Papers [Simon Peyton Jones: How to write a great research paper, MSR Cambridge] 21 706.015 Introduction to Scientific Writing – 01 Introduction