There's something deeply ironic about computer science students feeling like machines. We study systems, optimization, efficiency—and then we run ourselves at 100% CPU until we crash. No error handling. No graceful degradation. Just... overheating.

Your situation: Capstone (production), Advanced AI (research), Thesis (synthesis), Job hunt (transition). That's four massive cognitive loads running concurrently. No wonder you feel like a zombie.
The CS approach to survival:
1. Parallel processing with priority interrupts. Not everything needs to run simultaneously. What has the nearest deadline? What can be paused? What can be deprecated?
2. Garbage collection. You need to clear memory. Sleep, exercise, social breaks. The brain is a cache—it needs flushing.
3. Refactor your schedule. If your current system is crashing, the code isn't the problem; the architecture is. Redesign.
4. User testing. Ask friends what's working for them. Steal their strategies. Open source your mental health.
Remember: You're building skills for a lifetime, not just surviving a semester. The specific syntax of Advanced AI will fade. The ability to manage impossible workloads under pressure? That stays.
You're not breaking. You're compiling. The output will be worth it.