How to compare computer science programmes at Kenyan universities

University rankings in Kenya measure research output, not teaching quality. A university ranked number one for research may have a CS programme that has not updated its syllabus since 2015. Here is what to look at instead:

The unit list. Every accredited programme publishes its curriculum. Look at it. Does it include modern units like software engineering, web development, database design, and at least an introduction to AI or data science? Or is it stuck on COBOL, Turbo Pascal, and computer appreciation?

Programming languages taught. Python, Java, JavaScript, and C are standard. If the programme only teaches one language, or teaches languages nobody uses in industry, that is a red flag.

Lab infrastructure. Visit the campus if you can. Are the computer labs open and working? Do students have access to machines during free hours? A CS degree without functioning labs is a theory degree with a CS label.

Industry connections. Does the department bring in guest speakers from tech companies? Do they have partnerships for internships or attachment? Students at universities with strong industry links get opportunities that students at isolated universities do not.

The university brochure tells you what the programme promises. Current and former students tell you what it delivers.

Find students on LinkedIn or Twitter/X. Search for people who studied CS at the universities you are considering. Send a polite message: "I am considering CS at your university. Would you recommend the programme?" Most people are willing to share their honest experience.

Ask specific questions:

• Do lecturers teach from slides or do they demonstrate code live?
• Are assignments done individually or do they involve group coding?
• Did you feel prepared for your first tech job or internship?
• What did the programme not teach that you wish it had?
• Were the labs functional and accessible?

Patterns in answers tell you more than any ranking. If five students from the same university all say the labs were broken and the syllabus was outdated, believe them.

University prestige. In tech, your portfolio speaks louder than your university name. A developer who studied at a less-known university but has a strong GitHub and three deployed projects will get hired over a graduate from a prestigious university with nothing to show.

The exact syllabus. Every CS syllabus has gaps. No programme teaches everything the industry needs. You will fill gaps through self-study regardless of where you go. The question is whether the programme gives you a solid enough foundation to build on.

KUCCPS cluster points. Higher cut-off points reflect demand, not quality. A university with a lower cut-off might have a better CS department because fewer students have heard of it. Do your own research instead of using cut-off points as a proxy for quality.

Location (with one exception). Where the university is located matters less than the programme quality. The exception: proximity to Nairobi or another tech hub gives you easier access to meetups, hackathons, and internships. But a strong programme in Eldoret beats a weak one in Nairobi.

If you are choosing between two or three universities, score each on these five factors:

1. Syllabus relevance: Does the unit list include modern topics? (0 to 5)
2. Lab quality: Are labs functional, accessible, and adequate? (0 to 5)
3. Lecturer quality: Do lecturers have industry experience or current research? (0 to 5)
4. Graduate outcomes: Are recent graduates working in tech roles? (0 to 5)
5. Ecosystem access: Can you reach tech events, internships, and communities easily? (0 to 5)

Total each university out of 25. The numbers will not be precise, but the exercise forces you to evaluate systematically instead of going with gut feeling or what your friends chose.

If two universities score similarly, pick the one where you visited campus and felt you could study well. Environment affects performance more than people admit.