Should I learn frameworks before I finish learning the language?

Learn the language basics first (variables, functions, loops, objects). Once you can write small programmes confidently, start a framework. You do not need to master the language before touching a framework. Practical framework work deepens your language knowledge faster than more exercises.

Is it worth doing online courses alongside my degree?

Yes, selectively. One focused course per semester (freeCodeCamp, The Odin Project, or a specific framework tutorial) is enough. Do not stack three courses at once. The goal is depth in one area, not shallow exposure to many.

Will these gaps close as syllabi update?

Slowly. Kenyan university curricula update on multi-year cycles, and technology moves faster. By the time Git enters the syllabus, the industry will expect something newer. Closing gaps yourself is not a workaround; it is a permanent part of a tech career.

What Kenyan computer science degrees do not teach, and how to fill the gap yourself | Campus

What Kenyan computer science degrees do not teach, and how to fill the gap yourself

Kenyan CS degrees teach theory well: algorithms, data structures, discrete maths. What they skip is the tooling that jobs require: Git, modern frameworks, deployment, and working on a team codebase. You graduate knowing how a sorting algorithm works but not how to ship a feature. Fill the gaps yourself, starting in first year, using free resources and side projects.

What the degree does cover well

Before listing the gaps, acknowledge what the degree gives you. These foundations are real and valuable:

Problem-solving with algorithms and data structures. This is the backbone of technical interviews at serious companies. The degree drills it.
Understanding how computers work. Operating systems, networking, computer architecture. These topics seem abstract but become critical when you debug production systems.
Mathematical thinking. Discrete maths, linear algebra, probability. These show up in machine learning, security, graphics, and database design.
One or two programming languages in depth. Typically C, Java, or Python. The syntax matters less than the concepts, which transfer to any language.

The degree is not useless. It gives you a floor that self-taught developers often lack. The problem is what it leaves out.

The gaps: what employers expect and the syllabus skips

Version control (Git). Every software team uses Git. Most Kenyan CS syllabi do not teach it at all, or mention it once in a third-year unit. Start learning it in first year.

Modern frameworks. The job market wants React, Next.js, Django, Flutter, or similar. Your degree teaches the language (JavaScript, Python, Dart) but not the framework. You have to close this gap on your own.

Building and deploying real applications. Course assignments are isolated exercises: write a function, implement an algorithm. Real software involves connecting a frontend to a backend, talking to a database, handling authentication, and deploying to a server. None of that is typically in the syllabus.

Working on a shared codebase. In industry, you work on code other people wrote. You review their code. They review yours. You merge changes and resolve conflicts. University assignments are solo, which builds no teamwork muscle.

Developer tools. Terminal commands, package managers (npm, pip), environment variables, Docker, CI/CD. These are daily tools for working developers and entirely absent from most Kenyan CS curricula.

How to fill the gaps without overloading yourself

You do not need to learn everything at once. Pick one gap per semester and work on it alongside your coursework.

First year: Learn Git. Push your assignments to GitHub. That single habit builds a portfolio and teaches version control simultaneously. The semester plan has step-by-step instructions.

Second year: Learn one framework (React if you want frontend, Django or Express if you want backend). Build one project with it. A simple CRUD app, a personal blog, or a tool for a campus club.

Third year: Before attachment, learn deployment (Vercel, Railway, or a VPS). Build something that runs on the internet, not just on your laptop. Also: contribute to someone else's project (open source or a friend's codebase) to practise reading and modifying code you did not write.

Fourth year: Your final-year project is a chance to combine everything: a framework, a database, deployment, and version control. Make it something an employer can visit in a browser.

The thread through all four years: protect your coding time and build things that work, not just things that compile.

What to do this week

Identify which gap from the list above is most relevant to you right now.
Pick one free resource (freeCodeCamp for frameworks, GitHub Docs for Git) and complete the first lesson.
Push one assignment or project to GitHub this week, even if it is small.
Ask a second or third-year CS student which skills they wish they had started learning earlier.

Frequently Asked Questions

Should I learn frameworks before I finish learning the language?: Learn the language basics first (variables, functions, loops, objects). Once you can write small programmes confidently, start a framework. You do not need to master the language before touching a framework. Practical framework work deepens your language knowledge faster than more exercises.
Is it worth doing online courses alongside my degree?: Yes, selectively. One focused course per semester (freeCodeCamp, The Odin Project, or a specific framework tutorial) is enough. Do not stack three courses at once. The goal is depth in one area, not shallow exposure to many.
Will these gaps close as syllabi update?: Slowly. Kenyan university curricula update on multi-year cycles, and technology moves faster. By the time Git enters the syllabus, the industry will expect something newer. Closing gaps yourself is not a workaround; it is a permanent part of a tech career.