Burnout, balance and studying smarter in Computer Science

Nobody warns you properly about first year. Sure, people say "uni is a big adjustment" but they don't tell you what it actually feels like to have six modules, all with coursework, running at the same time, on top of four final exams, while you're living away from home for the first time, trying to make friends, and suddenly realising that the way you studied at school just doesn't cut it anymore.

By the time exam season came around, I was done. Six modules worth of coursework across the year, and then straight into four exams over the summer with barely any time to breathe. First year was genuinely harder than I expected and I think I spent most of it just trying to keep my head above water. By the end I had nothing left. No motivation, couldn't focus, couldn't really see the point of sitting down to revise because my brain had just checked out.

But I got through it. And second and third year have looked completely different. Here's what actually helped. 

Recognising burnout before it floors you

The tricky thing about burnout is that it creeps up. You don't just wake up one day unable to function. It's weeks of pushing through tiredness, skipping breaks because you feel behind, telling yourself you'll rest after this deadline. In Computer Science especially, there's this unspoken grind culture where everyone seems to be building side projects at 2am and pulling all nighters like it's a badge of honour. It's not sustainable and most people quietly crash. Signs worth paying attention to: you're staring at code and nothing is registering, every task feels disproportionately heavy, you've stopped doing things you normally enjoy. That's your signal to actually stop, not push harder. 

What helped me

Honestly, what turned things around wasn't some productivity hack. It was getting out of my room. I was living in halls at the time and there were events running fairly regularly that I started actually showing up to. At first I went just to get out of my head for an hour, but they ended up being some of my favourite memories of first year. I tried scrapbooking at one of them, which I never would have done by myself, met people I wouldn't have crossed paths with otherwise, and just felt normal again for a bit. It sounds small but when you've been staring at a screen and drowning in deadlines, that kind of thing genuinely resets you.

Then summer term arrived and with it a completely different energy. The sun was actually out, the mornings weren't cold and grey anymore, and campus came alive in a way that made it easier to breathe. I did the campus run which was a great way to just move and be outside, and there was a fair at the Vale with loads of games and activities that reminded me uni isn't just about grinding through work. Those things mattered more than I gave them credit for at the time. The wellbeing support and events available were genuinely good and I wish I had leaned into them earlier in the year rather than waiting until I was already on my knees. If you're reading this in first year, don't wait. Go to the events, talk to people, use what's there.

Studying smarter, not harder

This one took me a while to genuinely believe because it sounds like something you put on a motivational poster. But there's a real difference between time spent studying and effective studying.

A few things that actually made a difference for me:

• The Pomodoro Technique: Four periods of 25 minutes of focused work, divided by 5 minutes breaks and ending with a 30 minute-break. Your brain retains more from one focused hour than three distracted ones.
• Past papers over re-reading notes: In Computer Science, doing is almost always better than passively reviewing. Get into the problems early, not just the week before exams.
• Understanding over memorising: This is especially true for Computer Science. If you understand why an algorithm works, you can reconstruct it. If you've just memorised it, one curveball in the exam and it's gone.
• Side projects: They helped me more than I expected, not just for my CV but for actually cementing concepts. I got into the habit of building small things tied to whatever I was studying at the time, even for the more theory heavy modules. If we'd covered something in class I'd find a way to apply it to something practical, even if the end result was rough and basic. It made the material stick in a way that re-reading lecture slides never did. What surprised me most was that two years later, when I started my final year project, I kept finding myself drawing on things I'd built or figured out back then. Stuff I didn't even think I'd retained. It's one of those things where you don't realise how much it's paying off until it does.
• Basics matter more than you think: Sleep being the obvious one, but eating properly too. I used to skip meals constantly during busy periods, telling myself I didn't have time, and it just made everything worse. Concentration gone, energy gone, sitting there trying to debug something when your body has nothing to run on. It catches up with you faster than you'd think. Something small that actually helped was rewarding myself while studying rather than setting some big unrealistic goal and waiting until I reached it to feel good. I'd keep my favourite snack nearby and treat myself after a solid chunk of work. It sounds silly but it made sitting down to study something I didn't dread as much. Small wins add up and your brain needs something to work towards, even if it's just a biscuit. 

The bigger picture

Computer Science is a tough degree and the culture around it can make you feel like you should always be doing more. What I've learned is that the students who thrive long term aren't the ones who grind the hardest, they're the ones who figure out how to sustain themselves. Use the support around you, take the breaks, go to the events, talk to people. It doesn't make you less serious about your degree. It's what makes it survivable, and actually enjoyable. If first year has been rough, it gets better. And if you're in the thick of it right now, you're not alone