How a four-week micro-course fits around a semester

A micro-course covers one specific skill in four to six weeks. Where a full course or bootcamp covers an entire stack over months, a micro-course teaches one topic: M-Pesa integration, deployment, prompt engineering, or a specific framework. You go in with a clear goal and come out with a specific ability.

The format works for university students because it fits into the gaps your semester already has. You do not need to pause your degree, clear your schedule, or sacrifice a holiday. You need a few hours per week for one month.

The trade-off: depth is limited. A four-week course on React will not make you a React expert. But it will take you from "I have never used it" to "I can build a basic app and keep learning on my own." That jump is often the hardest part, and a structured course with deadlines and mentors makes it happen faster than self-study.

Map your free hours first. Before enrolling, write down your class schedule and study blocks. Identify the gaps. If you have three hours on Tuesday afternoon, two hours on Thursday evening, and three hours on Saturday morning, that is eight hours: enough for any micro-course.

Treat it like a unit. Block the time in your calendar. Do not treat it as optional. If you would not skip a lecture, do not skip a micro-course session. The students who complete these courses are the ones who schedule them like class, not like a hobby.

Choose the right timing. Start a micro-course at the beginning of a semester when your workload is lighter, or during a period between CATs. Do not start one the week before exams. Check your academic calendar and pick a four-week window that has no major assessments.

Communicate with the course. If the micro-course has a mentor or cohort, let them know your schedule constraints upfront. Good programmes accommodate student schedules. If a session conflicts with a class, ask whether recorded material is available.

Pick a skill your degree does not teach. The gaps in Kenyan CS degrees are well documented: deployment, API development, specific frameworks, version control workflows. A micro-course that covers one of these gaps adds immediate value to your skillset.

Pick something you can apply immediately. A micro-course on M-Pesa integration is useful if you are about to build a project that accepts payments. A micro-course on machine learning is less useful if you have not yet learned Python basics. Match the course to where you are now, not where you want to be eventually.

Prioritise project-based courses. If the course does not require you to build something, you will forget most of it within a month. Look for courses where the final deliverable is a working project you can add to your portfolio.

Check for mentorship. A micro-course with code review and mentor feedback is worth more than a video series you watch alone. The feedback loop is what accelerates learning beyond what you can do with free tutorials.

Ship the project. If the course produced a project, deploy it. Push it to GitHub. Add it to your portfolio. A completed micro-course project is a legitimate portfolio piece.

Use the skill in your next project. Knowledge decays if you do not use it. Within a month of completing the course, apply the skill in a personal project, a freelance gig, or a club contribution. This cements what you learned.

Add it to your CV and LinkedIn. Certificates add value when paired with demonstrated skill. List the course and link to the project it produced.

Consider the next gap. One micro-course per semester is sustainable. Over four years, that is eight targeted skills added to your degree. The cumulative effect is significant.