How can I balance heavy weekly coding labs in my CS major while keeping up with long-form history research papers?

The best way to handle this is to stop trying to force your brain to switch between coding and writing on the same day, as these tasks require fundamentally different types of cognitive energy. Since you find it impossible to break out of a coding flow state, you should lean into that intensity rather than fighting it. Instead of forcing yourself to write history papers on Friday nights when you are already drained from debugging, try dedicating specific days to deep work in one domain. For example, if you have a heavy lab due on Thursday, treat your Monday and Tuesday as your coding sprint days, then shift entirely to history research on Wednesday and Saturday mornings. By batching your tasks, you avoid the mental fatigue that comes from constantly swapping between logic-heavy syntax and narrative-driven analysis. Imagine you have a research paper due next week; instead of waiting until the weekend, try blocking out a two-hour window on Wednesday morning specifically for outlining your primary sources before you even touch your Python editor. If you get stuck in a debugging loop, don't let it bleed into your writing time; set a hard stop for the lab work and physically change your environment, perhaps by moving to a different spot in the library to signal to your brain that it is time for history. You might also find it helpful to use your commute or short gaps between classes to listen to audio versions of your history readings, which keeps the material fresh without requiring the heavy lifting of active writing. Finally, try drafting your history paper in smaller, low-stakes chunks throughout the week rather than saving the heavy lifting for your exhausted weekend self. Balancing these two worlds is all about respecting the different rhythms of your brain, so be patient with yourself as you find the schedule that keeps you productive without leading to total burnout.