the language has many powerful features, but this power brings with it complexity, which in turn can make code more bug-prone and harder to read and maintain. The goal of this guide is to manage this complexity all of the individual rules. By bringing these ideas to the fore, we hope to ground discussions and make it clearer to our broader community why the rules are in place and why particular decisions have been unittests and small .cc files containing just a main() function. Correct use of header files can make a huge difference to the readability, size and performance of your code. The following rules will

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. Suppress warnings if they are inappropriate so that other issues Inheritance with properties can be non-obvious if the property itself is not over- ridden. Thus one must make sure that accessor methods are called indirectly to ensure methods overridden in subclasses are called reflection, modification of system internals, etc. Pros: These are powerful language features. They can make your code more compact. Cons: It’s very tempting to use these “cool” features when they’re not abso-

Being overly focused on syntactic/local issues  Is the overall idea clearly communicated and does it make sense?  Are there missing pieces, missing experiments, missing related work? Scientific Reading for top-tier conferences/journals (act as filter)  Make the paper useful for others (ideas, evidence, code)  #4 Easily Readable: Quality ∝ Time  Make it easy to skim the paper  paragraph labels, self-explanatory articles  Use guarded spaces for references that should not appear on a new line  Clear References  Make sure there are no unclear “it” or “this” references  Add descriptive nouns  Titles and Names

primarily for statistical computing and graphics. The goal of the R Programming Style Guide is to make our R code easier to read, share, and verify. The rules below were designed in collaboration with avg_Clicks • FunctionName GOOD: CalculateAvgClicks BAD: calculate_avg_clicks , calculateAvgClicks Make function names verbs. Exception: When creating a classed object, the function name (constructor) and around their if clauses, you should, too. If their comments have little boxes of stars around them, make your comments have little boxes of stars around them, too. The point of having style guidelines is

values  Don’t hide important information Experiments and Result Presentation Don’t limit range to make you look good If there are multiple relevant parameters, show them all For log-scale you can’t types and tables  Consistency: use consistent colors and names for same baselines  Labeling  Make the plots self-contained  Simplifies skimming and avoids join with text Experiments and Result Presentation

graphics)  #3 Mindset: Quality over Quantity  Aim for top-tier conferences/journals (act as filter)  Make the paper useful for others (ideas, evidence, code)  Example (my own theses/books)  Seminar (~bachelor) Technology, WS 2020/21 Writing the Paper (and more Experiments)  Easily Readable: Quality ∝ Time  Make it easy to skim the paper  paragraph labels, self-explanatory figures (close to text), and structure

byte order mark Good: use escapes for non-printable characters, and comment if necessary. Tip: Never make your code less readable simply out of fear that some programs might not handle non-ASCII characters