Long Holiday Coming: What a Student Can Build in 3 Months

Every Kenyan university student gets roughly three months of holiday per year. Most students spend it sleeping, visiting relatives in shags, working a casual job at a supermarket, or scrolling their phone until their eyes hurt. By the time campus reopens, the holiday feels like it lasted three days, not three months.

Three months is 90 days. If you code for 6 hours a day and take weekends light, that is about 360 hours of practice. For context, most coding bootcamps compress their entire curriculum into 300 to 500 hours. You have a bootcamp-length runway in your hands, and it costs you nothing except discipline and data bundles.

The students who use this time are the ones who return to campus noticeably different. They speak about code with confidence. They have live projects on the internet. They have a GitHub profile with green squares stretching across the summer. Their classmates ask "what happened to you?" and the answer is simple: they used the three months instead of wasting them.

This plan assumes you are a beginner. If you already know HTML and CSS, start at week 5. If you already know JavaScript, start at week 9.

Weeks 1 to 2: HTML and CSS. Learn how web pages are structured and styled. Build three static pages: a personal profile, a restaurant menu, and a product landing page. Deploy all three on Netlify for free. These are not portfolio-worthy projects, but they teach you the fundamentals that everything else builds on.

Weeks 3 to 4: JavaScript Fundamentals. Variables, data types, functions, loops, arrays, objects, DOM manipulation. This is where the real programming starts. Build an interactive calculator and a simple quiz game. The frustration you feel during this phase is normal. Everyone hits it.

Weeks 5 to 6: Advanced JavaScript. Async programming, fetch API, working with JSON data, error handling. Build a weather app that pulls data from a free API. Build a currency converter. These projects teach you how real web applications work: they talk to external services and display dynamic data.

Weeks 7 to 8: React. Components, state, props, hooks, routing. Build a todo app with React (everyone's first React project) and then a more ambitious one: a blog reader that pulls posts from an API, or a recipe search tool. Deploy both.

Weeks 9 to 10: Backend with Node.js. Express server, REST APIs, connecting to a database (PostgreSQL or Supabase). Build an API for a simple application, then connect your React frontend to it. This is the moment you become a full-stack developer.

Weeks 11 to 12: Portfolio Project and Polish. Build one substantial project that combines everything: frontend, backend, database, API integration. Ideas: a campus marketplace, a study group finder, a budget tracker with M-Pesa-style transaction logging. Deploy it. Write a README. Add it to your portfolio site.

Build things that solve problems you or people around you actually have. Interviewers can tell the difference between a tutorial project and something you cared about.

1. Campus Meal Planner. A web app where students can plan their weekly meals on a budget. Input your weekly food budget in KES, and the app suggests affordable meal plans using ingredients available at local markets. Uses a database of common Kenyan foods and their approximate prices.

2. Hostel Review Board. A platform where university students review their hostels, bedsitters, and off-campus accommodation. Rating system, photo uploads, price comparisons by area. Every first-year student needs this. None of the existing campus websites provide it.

3. Study Group Matcher. Students input their course, available study times, and preferred study style (quiet library vs. group discussion). The app matches them with compatible study partners. Simple matching algorithm, clean interface, real utility.

4. Local Business Directory. A directory of small businesses near your campus: print shops, laptop repair, food joints, hairdressers. Each listing has hours, prices, M-Pesa till number, and student reviews. Approach five businesses and offer to list them for free as your test data.

5. HELB Repayment Calculator. A tool that takes your HELB loan amount, expected salary after graduation, and the current repayment rates, then shows you a month-by-month repayment schedule. Simple maths, real impact, and something every graduating student would use.

Coding at home is harder than coding at campus. There is no library. Your mother asks you to run errands. Your siblings want your phone. The TV is on. The neighbour's music is loud. Every distraction in Kenya is designed to stop you from concentrating.

Here is a daily routine that accounts for real life:

6:00 AM to 6:30 AM: Wake up. The house is quiet. This is your advantage. Do not waste it on your phone.

6:30 AM to 9:30 AM: Morning coding session. Three hours of focused work. No WhatsApp. No Instagram. Phone on silent in another room. This is your most productive window. Protect it.

9:30 AM to 10:00 AM: Break. Tea. Breakfast. Check your messages.

10:00 AM to 12:30 PM: Second coding session. Work on the harder parts of your project while your brain is still fresh.

12:30 PM to 2:00 PM: Lunch, errands, family time. Help with what needs helping. You are still at home, and home comes with obligations.

2:00 PM to 3:00 PM: Light coding or watching a tutorial. This hour is for learning new concepts, not building. Your afternoon energy is lower, so match the task to the energy.

3:00 PM onwards: You are done for the day. Rest. Socialise. Exercise. The temptation is to code until midnight, but that leads to burnout by week two. Six focused hours per day is enough to make massive progress over 12 weeks.

The hardest part of holiday coding is that nobody checks on you. There is no cohort. No lecturer. No deadline. Just you, your laptop, and the constant temptation to start tomorrow.

Three accountability systems that work:

1. The WhatsApp Check-in. Find one or two other students who are also learning to code. Create a group. Every evening, each person shares a screenshot of what they built or learned that day. No essay. Just a screenshot. The social pressure of not wanting to post "I did nothing today" keeps you going.

2. The GitHub Streak. Commit code to GitHub every day. The green contribution squares on your profile become a visual record of consistency. It is hard to skip a day when you can see the streak building. After 30 consecutive days, the streak itself becomes the motivation.

3. The Weekly Demo. Every Sunday, record a 2-minute screen recording of what you built that week. Post it on Twitter or LinkedIn. The act of demonstrating forces you to actually finish things instead of leaving projects half-done. It also starts building your professional presence online.

If you want structured accountability, a coding bootcamp during the holiday solves this completely. McTaba's 26-week marathon or the full-time intensive track puts you in a cohort with deadlines, code reviews, and mentors. The cost is KES 120,000 with M-Pesa instalments. If the budget is tight, start with Tech Foundations at KES 2,999.