Deep Work for UW Engineering: Why the Pomodoro Timer Fails CSE 143
You're in the basement of the Paul G. Allen Center. You have 48 hours to finish your CSE 143 project. You set a timer for 25 minutes. 15 minutes in, you finally hold the entire logic structure in your head... and the timer goes off.
Why Standard Pomodoro Fails Engineering
The classic 25/5 split works for history flashcards or responding to emails. But for Computational Thinking (CSE) or Thermodynamics (AA 260), the "loading time" for your brain is massive. It takes 20 minutes just to load the context. If you break every 25 minutes, you never reach peak efficiency.
The "Odegaard Protocol": 90-Minute Blocks
For UW STEM majors, we use the Ultradian Rhythm method (often called "Deep Work").
- Block 1 (90 mins): Pure coding/solving. No phone. Notification blockers on.
- The "Walk": (20 mins): Walk from Allen Center to Red Square and back. No phone. Let the background process in your brain solve the bug.
- Repeat: Maximum 3 cycles.
Freshman Tip: Don't try to do this in your dorm. Go to the quiet floor (3rd floor) of Odegaard or a breakout room in the Allen Center. Environmental cues trigger focus.
Applying This to Specific Classes
CSE 142/143: Use the first block to diagram your code (write comments, plan structure) without typing a line of code. Use the second block for implementation.
PHYS 121: Use a full block for problem sets. Do not switch context. Physics requires "momentum" (pun intended).
Using NoteNest for Engineering
Don't just record lectures. In engineering, the diagram on the whiteboard IS the lecture.
- Snap the circuit diagram or free body diagram.
- Voice note your understanding of why the professor simplified the equation.
- Let NoteNest link it to the relevant textbook chapter automatically.