How to Balance Campus and a Part-Time Coding Program

Every student who asks about balancing campus and coding starts with the same question: "Do I have enough time?" The answer is almost always yes. A typical Kenyan university student has 15 to 20 hours of lectures per week. Add 10 hours for assignments, studying, and group projects. That is 30 hours. A week has 112 waking hours. You have margins.

The real question is: "Do I have enough energy?" Because after a 3-hour lecture on corporate finance, a group meeting where nobody did their part, and a 45-minute matatu ride back to your bedsitter, opening VS Code feels like lifting concrete blocks with your eyelids.

This is why most students who attempt both fail. They set ambitious schedules and run out of fuel by week three. The fix is not motivation. It is designing your schedule around your energy, not just your availability.

Take your semester timetable and print it. Or draw it in a notebook. Whatever makes it physical and visible. Now mark every lecture, tutorial, and lab session. These are fixed. Do not touch them.

Look at the gaps. Most Kenyan university timetables have at least two 2-hour breaks per day. Those are your coding slots. Not "free time." Coding slots. Treat them with the same respect you give lectures.

A realistic weekly schedule looks like this:

• Monday, Wednesday, Friday: 2-hour coding session between morning and afternoon lectures. Location: library or a quiet spot on campus.
• Tuesday, Thursday: 1.5-hour session in the evening after your last class.
• Saturday morning: 3-hour deep work session when the hostel is quiet and nobody is messaging the group chat.
• Sunday: Rest. You need it.

That is roughly 12 hours per week. Enough for a part-time bootcamp. Enough to make real progress.

Write it down. Tell someone. Set phone reminders. The moment you leave a coding session to "feel" instead of to "schedule," it stops happening.

Your degree comes first. Period.

During CAT weeks and final exams, close VS Code. Uninstall it if you have to. Focus entirely on your units. A coding programme is an investment. Your degree is the foundation that investment sits on. Do not crack the foundation trying to stack faster.

Good coding programmes understand this. McTaba, for example, allows part-time students to adjust their pace during exam periods. If your programme does not offer flexibility around campus exam schedules, that is a red flag worth noting before you enrol.

Here is the mental trick that helps: you are not quitting coding during exam weeks. You are pausing. There is a difference. Quitting means you lost. Pausing means you are managing competing priorities like an adult. You will pick it up the Monday after your last exam. Write yourself a note about exactly where you stopped so you can resume without wasting an hour trying to remember what you were building.

Kenyan universities give you roughly three months of holiday per year. Some give more, especially during strikes or delayed semesters. While everyone else is complaining about boredom in Nyeri or Kisumu, you have a runway.

Three months of full-time coding, say 6 hours a day, is equivalent to roughly 5 months of part-time work during the semester. If you are in a bootcamp, this is when you accelerate. If you are self-taught, this is when you build your biggest projects.

Plan your holiday before it starts:

• Week 1: Travel home, settle in, set up your workspace.
• Weeks 2 to 10: Code. Build projects. Complete course modules. This is your sprint.
• Weeks 11 to 12: Polish your portfolio. Deploy your projects. Rest before the next semester.

The students who use holidays to code arrive back at campus ahead of their cohort. The students who do not spend September catching up on what they could have finished in July.

Not every coding programme is designed for university students. Some run Monday to Friday, 9 AM to 5 PM. That does not work if you have lectures. Here is what to look for.

Part-time or evening schedules. Sessions in the evening (after 5 PM) or on weekends. McTaba's part-time track runs across 6 months with flexible scheduling that accommodates students.

Self-paced elements. Programmes that let you work through content at your own speed during the week and check in with mentors during scheduled sessions.

Cohort model. This is important. Self-paced without a cohort means you are alone. A cohort gives you classmates who are at the same stage, pushing through the same challenges. When you are tempted to skip a session, the fact that your cohort mate will be there keeps you showing up.

Pause-friendly policies. Can you pause for two weeks during exams? Can you rejoin without starting over? If the programme says no, it is not built for students.

Project-based curriculum. Programmes that are lecture-heavy drain your energy because you already spend 15+ hours per week listening to lectures at campus. The best coding programmes make you build things during the session, not just watch someone else code.

There will be a week, probably around month two, when you want to quit one or both. You bombed a CAT. You cannot figure out why your React component keeps crashing. Your roommate is going out and you are debugging. Your parents call and ask why you are spending money on "extra courses" when you are already paying tuition.

This is normal. Every student who has done this hit the same wall.

What separates those who make it from those who drop: they did not make a permanent decision during a temporary feeling. They went to bed. They woke up. They opened VS Code again. Not because they felt inspired. Because it was Tuesday and their schedule said code at 10 AM.

If you genuinely cannot manage both in a given semester, drop back to coding 4 hours per week instead of 12. Do not stop completely. Even two sessions a week keeps the skill alive. Stopping completely means you have to rebuild momentum from zero, and that restart cost kills more students' coding journeys than the actual difficulty of the material.

You are doing something hard. That does not mean you are doing it wrong.