Checklist

CMU systems-grind survival checklist

A defensive workflow for Carnegie Mellon students surviving a famously brutal CS and design load, where a single systems lab can eat a weekend and you are context-switching between a debugger and a portfolio critique.

Built for Carnegie Mellon University · CS and design students managing rigorous studio and systems work.

Progress

0 of 12 tasks complete

Triage the impossible week

At CMU the honest question is what to drop, not how to do it all, so rank ruthlessly before the week buries you.

Score every deliverable by points-per-hourList the week's labs, problem sets, and studio deadlines, estimate hours for each, and rank by points earned per hour so low-yield work does not steal your debugging time.~35 minSpend your late days deliberatelyDecide in advance which assignment gets a grace day if you have one, instead of spending it in a panic on whatever happens to be due first.~20 minBatch tasks by context, not by deadlineGroup all of one course's work into a single block so you stop paying the reload cost of jumping between a kernel debugger and a design crit ten times a day.~25 min

Engineer the debugging session

The long debugging cycle is where CMU hours vanish, so attack it with method instead of flailing at the symptom.

Write the bug down before you touch codeState the expected behavior, the actual behavior, and the smallest input that reproduces it, so you are debugging one known thing rather than a vague feeling that it's broken.~20 minBisect with version control, not guessesUse git bisect or your last green commit to find the change that broke it, instead of rereading the whole file hoping the bug jumps out.~40 minSet a 45-minute stuck timerWhen a single bug crosses 45 minutes with no progress, write your current hypothesis, take it to a TA or peer, or walk away; staring longer rarely pays at this workload.~15 min

Protect the studio and portfolio track

Design deadlines do not wait for the systems lab to finish, so move the creative work forward in parallel, not after.

Get an ugly draft in front of eyes earlyPut a rough version of the studio piece up for informal critique days before the deadline, because feedback on a draft beats a polished thing nobody saw until it was graded.~60 minKeep a versioned portfolio archiveCommit each iteration of the design work so you can show progression and roll back a direction that stopped working without losing the earlier one.~30 minReserve one uninterrupted creative blockProtect a single long block with notifications off for the studio work, since design thinking does not survive being sliced into ten-minute gaps between debugging.~90 min

Recover before the next wave

CMU breaks people who never reset, so close each cycle with a deliberate recovery and a sharper plan.

Bank the bug-and-fix in a personal logRecord each hard bug and the fix that worked so the next systems lab reuses the solution instead of rediscovering it from scratch.~25 minSchedule real sleep into the next weekBlock protected sleep hours on the calendar like a deadline, because sustained sleep debt is what actually tanks performance over a CMU semester.~15 minRe-rank the next week from the new realityRedo the points-per-hour triage with what you now know is hard, so each week's plan is calibrated rather than optimistic.~25 min

Common mistakes

Trying to complete every assignment fully instead of triaging by points per hour
Context-switching between a debugger and a studio crit so often that neither gets real focus
Debugging by rereading the whole file instead of bisecting to the change that broke it
Grinding a single bug for hours past the point where a TA could have unblocked you in minutes
Treating sleep as the buffer that absorbs every overrun until performance quietly collapses

Pro tips

Batch a course's work into one block to avoid paying the context-switch reload cost
Write expected-versus-actual and a minimal repro before you start fixing any bug
Use git bisect against your last green commit to localize a regression fast
Put an ugly studio draft up for critique early; feedback beats polish nobody saw
Block protected sleep on the calendar so the semester does not run on debt

FAQ

How should I start the CMU systems-grind survival checklist?

Start with the first phase, then run one timed Study Spaces sprint before adding more tasks. The goal is execution, not a perfect plan.

What should I do if I fall behind?

Copy the remaining tasks, pick the highest-score or highest-deadline item, and restart with one focused block.

How often should I review progress?

Review after each sprint and once at the end of the week so the next session starts with a clear first task.

Browse resources

Use it now

Turn this page into a live sprint

Start the matching room for Carnegie Mellon University, then use the sprint plan as the first task and recap script.

CMU systems-grind survival checklist
Focus target: Carnegie Mellon University
Block 1 (25 min): closed-book recall or one timed practice set.
Break (5 min): mark confusing items without opening a new task.
Block 2 (25 min): correct misses and write the next first step.
Done: one score/error note plus one queued task for tomorrow.

Start Carnegie Mellon University roomResource list Compare methods