Organizing filesystems

This page describes Chris's practices for organizing filesystems. These are the result of over a decade of iteration, so there might be some wisdom baked in. But use whatever works for you.

Principles

• Own your work
• Back up your work

Which filesystems

• Laptop
• Google Drive. Good for collaboration. Don't use your university email address.

Layout

At a top level, I think it makes sense to distinguish your doctoral work from your previous professional work and from your future as an academic, if that's your thing. Here's a partial example of Chris's laptop filesystem.

~/Documents
├── Academic
│   ├── Career
│   │   └── 2019 Job Search
│   ├── Consulting
│   ├── Identity
│   │   └── CV
│   ├── Network
│   ├── Research
│   │   ├── Grants
│   │   │   ├── 2022 NSF CS for All
│   │   │   └── 2022 NSF CAREER
│   │   ├── Projects
│   │   │   ├── 2022 NSF CS for All
│   │   │   ├── Making With Code
│   │   │   ├── Minecraft Utopia
│   │   │   └── Unfold Studio
│   │   └── Publications
│   │       ├── 2021 AERA identity as interface
│   │       ├── 2021 CS Teaching Book Chapter
│   │       ├── 2022 CSCL Minecraft
│   │       └── 2022 Encyclopedia CT
│   ├── Service
│   │   ├── Letters
│   │   ├── Reviewing
│   │   └── NSF
│   └── UB
│       ├── Admin
│       ├── Service
│       │   └── Advising
│       └── Teaching
└── PhD
    ├── Admin
    ├── Coursework
    └── Research

A few notes. Research is organized into Grants, Projects, and Publications.