in turn can make code more bug-prone and harder to read and maintain. The goal of this guide is to manage this complexity by describing in detail the dos and don’ts of writing C++ code. These rules exist keep the code base manageable while still allowing coders to use C++ language features produc- tively. Style, also known as readability, is what we call the conventions that govern our C++ code. The term term Style is a bit of a misnomer, since these conventions cover far more than just source file formatting. Most open-source projects developed by Google conform to the requirements in this guide. Note

Introduction This document serves as the complete definition of Google’s coding standards for source code in the Java™ Programming Language. A Java source file is described as being in Google Style if and herein. Like other programming style guides, the issues covered span not only aesthetic issues of formatting, but other types of conventions or coding standards as well. However, this document focuses primarily notes Example code in this document is non-normative. That is, while the examples are in Google Style, they may not illustrate the only stylish way to represent the code. Optional formatting choices made

Lines Whitespace Shebang Line Comments Classes Strings Files and Sockets TODO Comments Imports formatting Statements Access Control Naming Main Important Note Displaying Hidden Details in this Guide To help you format code correctly, we’ve created a settings file for Vim. For Emacs, the default settings should be fine. Python Language Rules Lint link￿ Run pylint over your code. Definition: pylint pylint is a tool for finding bugs and style problems in Python source code. It finds problems that are typically caught by a compiler for less dynamic languages like C and C++. Because of the dynamic nature

quality, constructive feedback and recommendations, widen own horizon  Lots of similarities to code reviews in OSS  Learning by What NOT to Do  Accept if no time to review  The Goldilocks Method 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 begin{enumerate} … \end{enumerate}  Figures and Tables  Captions below figures, above tables  Code  \begin{verbatim} … \end{verbatim}  Theorem, Definition, Examples  Refine theorem environments

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 the entire Syntax Line Length The maximum line length is 80 characters. Indentation When indenting your code, use two spaces. Never use tabs or mix tabs and spaces. Exception: When a line break occurs inside "dates", ylab = metric, main = (paste(metric, " for 3 samples ", sep = ""))) Do not place spaces around code in parentheses or square brackets. Exception: Always place a space after a comma. GOOD: if (debug)

 Overview  Ensure reproducibility of research results and conclusions  Common problem: “All code and data was on the student’s laptop and the student left / the laptop crashed.”  Create value 12/2019, towards faculty-specific RDM policies Reproducibility and RDM “Ensure that research data, code and any other materials needed to reproduce research findings are appropriately documented, stored Technology, WS 2021/22 RDM in Practice @DAMSLab  Code and Artifacts  Apache SystemDS: https://github.com/apache/systemds (OSS)  Complete code history, src/bin releases (SystemDS 2.2.0 in Oct 2021)

top-tier conferences/journals (act as filter)  Make the paper useful for others (ideas, evidence, code)  Example (my own theses/books)  Seminar (~bachelor), 5 months, 446 pages  Diploma (~master),