assume that the reader is familiar with the language. Goals of the Style Guide Why do we have this document? There are a few core goals that we believe this guide should serve. These are the fundamental necessary and appropriate, even when they conflict with the other principles of this document. The intent of this document is to provide maximal guidance with reasonable restriction. As always, common sense header. • Structuring code to enable forward declarations (e.g. using pointer mem- bers instead of object members) can make the code slower and more com- plex. • Try to avoid forward declarations of entities

 #1 Write short summary paper (#pages = 2 * team-size, written in LaTeX, ACM acmart template, document-class sigconf, PDF)  #2 Prepare and present talk on paper summary (7min + 3min Q&A)  Timeline Research – Writing Cycle  Read lots of papers  Idea  Research  Writing  Document  Idea  Writing/Research  Document  Incremental refinement of drafts  Paper Submission Cycle  Blind vs double-blind and friends  Develop your taste for good research topics  Topic selection needs time  pipeline model  Ex. Compressed Linear Algebra  Problem: Iterative ML algorithms + memory-bandwidth-bound operations

Google Java Style Guide Google Java Style Guide 1 Introduction This document serves as the complete definition of Google’s coding standards for source code in the Java™ Programming Language. A Java issues of formatting, but other types of conventions or coding standards as well. However, this document focuses primarily on the hard-and-fast rules that we follow universally, and avoids giving advice advice that isn’t clearly enforceable (whether by human or tool). 1.1 Terminology notes In this document, unless otherwise clarified: 1. The term class is used inclusively to mean an “ordinary” class, enum

can expand points to get more details. Alternatively, there’s a “toggle all” at the top of this document. Background Python is the main scripting language used at Google. This style guide is a list of convention is simple. The source of each identifier is indicated in a consistent way; x.Obj says that object Obj is defined in module x. Cons: Module names can still collide. Some module names are inconveniently load time. This may cause problems if the argument is a mutable object such as a list or a dictionary. If the function modifies the object (e.g., by appending an item to a list), the default value is modified

Read Fully  Read and annotate issue, don’t fix immediately (destroys the flow)  Take annotated document and fix issues  #3 Ask Big Questions  Pitfall: Being overly focused on syntactic/local issues

 #1 Write short summary paper (#pages = 2 * team-size, written in LaTeX, ACM acmart template, document-class sigconf, PDF)  #2 Prepare and present talk on paper summary (7min + 3min Q&A)  Timeline

calculate_avg_clicks , calculateAvgClicks Make function names verbs. Exception: When creating a classed object, the function name (constructor) and class should match (e.g., lm). • kConstantName Syntax Line it. Functions Errors should be raised using stop(). Objects and Methods The S language has two object systems, S3 and S4, both of which are available in R. S3 methods are more interactive and flexible methods unless there is a strong reason to use S4 objects or methods. A primary justification for an S4 object would be to use objects directly in C++ code. A primary justification for an S4 generic/method would