 #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 PVLDB 8(12) 2015  #15.4 Milos Nikolic, Mohammed Elseidy, Christoph Koch: LINVIEW: incremental view maintenance for complex analytical queries. SIGMOD 2014  #15.5 Yannis Klonatos, Christoph Koch

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 a virtual function inline is to place its definition in the class, either for convenience or to document its behavior, e.g., for accessors and mutators. Names and Order of Includes Use standard order

Details in this Guide link￿ This style guide contains many details that are initially hidden from view. They are marked by the triangle icon, which you see here on your left. Click it now. You should see 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

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

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