CSCI 699, 30098D
M/W 10-11:50pm, SAL 227A/Zoom
Instructor: Barath Raghavan
Office Hours: Th 9-10am
In this course we will aim to understand how to formulate a research agenda in Computer Science, examine trends that exist within areas of CS, and identify fruitful and problematic research directions. We will examine barriers to scientific research advancement and how to avoid them when possible, and practice thinking meta-systematically ("thinking outside of the box") when approaching selection of research problems and developing research solutions.
The course will explore the hybrid nature of Computer Science -- its existence at the intersection of mathematics, engineering, statistics, and other disciplines -- and how to evaluate progress in CS research, and identify fruitful avenues of future study. Our focus will not be on any one area of CS, so as a result we will examine research agendas in a variety of areas of CS.
The course will involve discussion, presentation, and group work during class. In addition, in groups of one or two, students will work on an independent project to describe the past and potential-future research in an area of CS, possibly one that is of interest to the student(s) for future study such as in a dissertation, postdoc, or faculty position.
Computer Science research is diverse in both topic and method, building upon a wide array of adjacent disciplines and also having a rich body of practice of its own. Your task is to develop a research agenda in an area of CS and present this agenda in a variety of forms: 1) as a research whitepaper surveying prior work and describing a future agenda, 2) as a grant one-pager that describes why such work should be funded, 3) as a 30-minute research presentation, 4) as a 10-minute general audience presentation, and 5) as a popular-science article. Even if you choose to work on your own, you'll be paired up and will be providing peer feedback on a regular basis. (To this end, you will need to make a complete draft of each milestone available to your partner five days in advance of each deadline, to allow them time to give you feedback and for you to make edits.)
Per-class assignments will focus on assigned readings and responses to those readings. For each class's assignment, add your responses to an appropriately titled section of your Google Doc, with your most recent additions at the top of the doc. Each day's assignment is due at the start of class that day.
Details of grading will be provided in class. Grades will be determined as follows:
25% Reading responses
25% Peer feedback
10% Paper Presentation
40% Project
Date | Class Notes | Reading Due | Assignment Due |
---|---|---|---|
M 1/10 Welcome |
Notes | - | - |
W 1/12 Areas |
- |
|
|
M 1/17 Holiday |
- | - | - |
W 1/19 Foundations |
- |
|
|
M 1/24 Ideas |
|
|
|
W 1/26 Systems |
Notes |
|
|
M 1/31 Stepping Stones |
- |
|
|
W 2/2 Nebulosity |
|
|
|
M 2/7 Meta-rationality |
|
||
W 2/9 Writing |
Notes |
|
|
M 2/14 | Project Updates | Milestone 1: Progress update. | |
W 2/16 Community |
|
|
|
M 2/21 Holiday |
- | - | - |
W 2/23 |
- | Project updates | Milestone 2: Progress update. |
M 2/28 Eras |
- |
|
|
W 3/2 Society |
- |
|
|
M 3/7 Society |
|
||
W 3/9 The (Meta) Thing from The Future |
- |
|
|
M 3/14 Holiday |
- | - | - |
W 3/16 Holiday |
- | - | - |
M 3/21 Theories |
- |
|
|
W 3/23 | - | - | - |
M 3/28 | - | Project Checkins | - |
W 3/30 Advice |
- |
|
|
M 4/4 | - | Project Updates | Milestone 4: Progress update. |
W 4/6 | - | - | - |
M 4/11 | - | Project Updates | - |
W 4/13 | - | - | - |
M 4/18 Mock Program Committee |
- | - | - |
W 4/20 Mock Program Committee |
- | - | - |
M 4/25 | Guest: David Chapman | - | - |
W 4/27 | Project presentations | - |
In addition to the assigned readings in the schedule above, this is an incomplete list of papers to consider for presentation in class; this list is incomplete and will be expanded: