First Two Weeks Checklist
A checklist for your first two weeks in the lab. Don’t worry about finishing everything on a strict schedule — the items marked Must do are the priority. Everything else is a stretch goal that can slide into the following week if needed.
Week 1: Get Set Up
Administrative (Day 1) — Must do
Computing Setup (Days 1-3) — Must do
Communication (Day 2) — Must do
-
#general- Announcements#computing- Technical help#papers- Literature discussion#random- Social
Orientation (Days 3-5) — Must do
Stretch goals for Week 1
End of Week 1 Goals
By Friday, you should have:
- ✅ Computing access requested or approved
- ✅ Git and GitHub configured
- ✅ Joined Teams and the GitHub org
- ✅ Met with Dr. Rashid and received your reading list
- ✅ Know who to ask for different types of help
Week 2: Start Working
Computing (Days 6-7) — Must do
First Code (Days 7-9) — Must do
Reading — Must do
- Coding Standards - Lab code style (especially the “Why Base R + data.table?” section)
- Your First Project - Includes a “What is targets?” introduction
Reading — When you’re ready
- Targets Pipeline Guide - Full reference (skim for now, reference later)
- Project Consistency - Relevant when you start writing up results
End of Week 2 Goals
By Friday, you should be able to:
- ✅ Log into Longleaf and run R
- ✅ Clone, modify, and push to a GitHub repo
- ✅ Run a
targetspipeline - ✅ Render a Quarto document to PDF
- ✅ Understand the basics of the lab’s coding conventions
Questions to Ask
In your first meeting with Dr. Rashid:
- What project will I be working on?
- Who is my day-to-day mentor?
- What are the short-term and long-term goals?
- What background reading should I prioritize?
- When is my first presentation expected?