How to balance coding and classes without failing either

You have more free hours in first year than you think. Between lectures, you have gaps: mornings without classes, long lunch breaks, free afternoons, weekends. The issue is that these gaps get filled by default activities: scrolling, socialising, napping, or just sitting around.

None of those are bad. But if coding matters to you, it needs a slot that is not "when I have time." It needs a slot that is as fixed as your Tuesday 10 AM lecture.

The system is simple: decide when you code, write it down, and protect it. Everything else is discipline, which gets easier once the habit is established.

Three sessions per week, ninety minutes each. That is four and a half hours, which is less time than you probably spend on your phone daily.

Session 1 (weekday evening): Learn new material. Follow your course, tutorial, or textbook.

Session 2 (weekday evening): Practise. Solve exercises using what you learned in session one.

Session 3 (weekend morning): Build. Work on your current project.

Slot these around your lectures, not instead of them. Look at your timetable, find three gaps that are at least ninety minutes long, and claim them. Tell your friends those slots are taken.

If you only have two reliable slots per week, that works too. Two sessions sustained over a semester beats five sessions in week one followed by nothing.

The semester-by-semester coding plan breaks down what to cover in each session across the year.

When continuous assessment tests (CATs) or end-of-semester exams arrive, your coursework takes priority. Do not try to maintain your full coding schedule during exam weeks. You will do both badly.

Instead, scale down:

• During CAT weeks: Drop to one session. Use it to practise something small, like a code challenge. Fifteen to twenty minutes is fine. The goal is to keep the habit alive, not to make progress.
• During exam weeks: Stop coding entirely. Study for your exams. Resume the week after. A two-week break does not erase what you learned. A failed unit creates problems that last semesters.

The students who burn out are the ones who refuse to pause. Pausing is part of the system, not a failure of it.

Sometimes you will have a coding project you are excited about and an assignment you are not. The temptation to skip the assignment and keep coding is real.

Do the assignment first. Always.

A bad grade on a university assignment stays on your transcript permanently. An unfinished side project can be picked up next week. The cost of skipping coursework is concrete and lasting. The cost of pausing your project is temporary.

That said, if your course includes programming assignments, treat those as both coding practice and coursework. They count twice. CS students especially can use course assignments as the "learn" portion of their coding schedule, freeing up self-study time for projects.

Schedules are easy to write and hard to follow. Two things help:

A coding partner. Find one person who is also learning. Agree to meet at the same time each week. You do not need to work on the same thing. Just being in the same room (or on the same video call) at a fixed time creates accountability. When you feel like skipping, knowing someone is expecting you changes the calculation.

A visible streak. Track your sessions. A simple note on your phone, a calendar with marked days, or your GitHub contribution graph. The longer the streak, the harder it is to break. After three weeks of consistency, it starts to feel automatic.

Browse the full coding cluster for community options, study group guides, and project ideas that make practice more engaging than tutorials.