A 12 Week Self Study Plan for Kenyan Beginners

This plan is realistic, not optimistic. Twelve weeks of self-study will not make you a senior developer. It will not guarantee you a job. What it will do is take you from "I have never written a line of code" to "I can build a full-stack web application and deploy it." That is a meaningful skill, and it is the foundation everything else builds on.

The plan assumes 10 to 15 hours of study per week. That is roughly 1.5 to 2 hours on weekday evenings after work or school, plus 3 to 4 hours on Saturday and Sunday. If you can do more, you will progress faster. If you can only manage 8 hours, the plan stretches to 15 or 16 weeks instead of 12. That is fine. Consistency matters more than speed.

You need a computer (any laptop made in the last 5 to 7 years works), an internet connection for downloading resources and watching tutorials, and a code editor (VS Code, which is free). You do not need a powerful machine, a second monitor, or a computer science degree. If you need help setting up, read our computer setup guide first.

One more thing: you will feel lost and frustrated multiple times during this plan. That is not a sign that you are doing it wrong. It is a sign that you are learning. Every developer who came before you felt the same way. Push through the discomfort, build the projects, and come back to confusing concepts later. They click eventually.

This block gives you the foundation of every website: structure (HTML), styling (CSS), and basic interactivity (JavaScript).

Week 1: HTML fundamentals. Learn the basic HTML elements (headings, paragraphs, links, images, lists, divs), how to structure a page, and how to create forms. Resource: freeCodeCamp's Responsive Web Design certification, the HTML section. By the end of week 1, you should be able to write a basic HTML page from scratch without copying from a tutorial.

Week 2: CSS fundamentals. Learn how to style elements (colors, fonts, spacing, borders), the box model, Flexbox for layout, and basic responsive design with media queries. Resource: freeCodeCamp's Responsive Web Design, the CSS section. Also watch Kevin Powell's CSS tutorials on YouTube for visual explanations. By the end of week 2, build a simple personal profile page with HTML and CSS.

Week 3: JavaScript basics. Learn variables (let, const), data types (strings, numbers, booleans), conditionals (if/else), loops (for, while), and functions. Resource: freeCodeCamp's JavaScript Algorithms and Data Structures certification, the first few sections. By the end of week 3, you should be able to write a function that takes inputs and returns results.

Week 3 project: Build a personal portfolio page using HTML, CSS, and a tiny bit of JavaScript (maybe a dark mode toggle or a form validation). Keep it simple. The goal is to apply what you learned, not to create something impressive. Host the HTML file locally and show it to someone. That is your first "app."

Kenya-specific note: If your internet is unreliable, download freeCodeCamp's curriculum for offline use or save the relevant YouTube playlists using a tool like youtube-dl during off-peak hours. Many Kenyan learners study at night when data is cheaper on some carriers.

This is where things get harder and where most self-taught learners drop off. JavaScript has depth, and this block covers the parts that actually matter for building applications.

Week 4: Arrays and Objects. Learn array methods (map, filter, find, reduce), working with objects, destructuring, and the spread operator. These are not optional features. You will use array methods in virtually every React component and every backend function you write. Resource: freeCodeCamp's JavaScript certification, continued. Also try JavaScript.info (the Modern JavaScript Tutorial), which has excellent explanations.

Week 5: DOM manipulation and events. Learn how to select elements (querySelector), modify the page (innerHTML, classList, createElement), and handle user events (click, submit, input). This is where JavaScript connects to the web page. Build a to-do list app that adds, removes, and marks items as complete using vanilla JavaScript. No frameworks yet.

Week 6: Async JavaScript. Learn callbacks, promises, and async/await. Understand how to fetch data from an API using the fetch() function. This is the concept that trips up the most beginners, so take your time. Build a small app that fetches data from a public API (like the Pokemon API, or the REST Countries API) and displays it on a page.

Week 6 project: Build a weather app or a country information app that fetches data from a free public API. The user should be able to search for something, and the app should display the results. Use only HTML, CSS, and vanilla JavaScript. No React, no frameworks. This project proves you understand how the web actually works before adding abstractions on top.

If week 6 feels brutal, that is expected. Async JavaScript is the hardest part of the fundamentals for most people. Rewatch explanations, try different resources, and practice writing fetch calls until they feel natural. Once async clicks, everything else in web development becomes much easier.

React is the most widely used frontend framework, and it is what most job listings ask for. This block introduces component-based thinking, which is a genuinely different way of building interfaces.

Week 7: React fundamentals. Learn components (function components only, skip class components), JSX, props, and conditional rendering. Resource: the official React tutorial at react.dev. It is excellent and interactive. Also, set up a React project with Vite: npm create vite@latest my-app -- --template react.

Week 8: State and effects. Learn useState for managing component state, useEffect for side effects (like fetching data), and how React renders and re-renders components. Build small interactive components: a counter, a form with validation, a toggle. Understand the difference between props (data passed down) and state (data managed internally).

Week 9: Building a real React app. Learn React Router for multi-page navigation, lifting state up, and how to structure a React project with multiple components in multiple files. Rebuild your week 6 API project in React. Compare the vanilla JavaScript version with the React version. Notice how React handles the same problem differently.

Week 9 project: Build a multi-page React application that fetches data from an API. Something like a movie search app (using the TMDB API), a recipe finder, or a news aggregator. It should have at least three pages, a search feature, and proper component structure. Deploy it to Vercel (see our deployment guide).

React has a steep learning curve in the first week. The mental model is different from vanilla JavaScript, and JSX feels strange at first. Push through. By week 9, you will understand why React is popular and how it makes complex interfaces manageable.

Frontend is half the picture. This block gives you enough backend knowledge to build complete applications.

Week 10: Node.js and Express basics. Learn what a server is, how to create one with Express, how to handle GET and POST requests, and how to send JSON responses. Build a simple REST API with two or three endpoints. Resource: The Odin Project's Node.js path, or the freeCodeCamp backend curriculum.

Week 11: Databases. Learn basic SQL (SELECT, INSERT, UPDATE, DELETE), how to set up a PostgreSQL database with Supabase (free), and how to connect your Express API to the database. Build an API that stores and retrieves data from a real database instead of a local array. Read our databases for beginners guide alongside this week's study.

Week 12: Putting it all together. Connect your React frontend to your Express + PostgreSQL backend. Add user input (forms that save data), display data from the database, and deploy the full stack. Frontend to Vercel, backend to Railway or Render. This is your capstone project.

Week 12 project: Build a full-stack application. Ideas: a bookmark manager where users can save and categorize links, a simple blog where you can create and display posts, or a personal expense tracker. The app should have a React frontend, a Node.js/Express backend, and a PostgreSQL database. Deploy both parts so anyone with a URL can use it.

This week is ambitious. You might not finish deployment by the end of week 12, and that is okay. The goal is to understand how all the pieces connect. If it takes you until week 14 to get everything deployed, you are still ahead of most self-taught learners who never build a full-stack project.

Having a plan for what to study each week is not enough. You need a plan for what to do each day. Here is a realistic daily structure for someone studying 1.5 to 2 hours on weekday evenings.

First 15 minutes: Review. Look at what you learned yesterday. Skim your notes. Try to recall the key concepts without looking at the material. This spaced repetition is what makes learning stick.

Next 30 to 45 minutes: Learn. Watch a tutorial section, read a chapter, or work through a lesson on freeCodeCamp. Take minimal notes. Focus on understanding the concepts.

Last 45 to 60 minutes: Code. This is the most important part. Write code. Not copying from a tutorial, but actually writing your own code based on what you just learned. Try the exercises. Build the small projects. Break things and fix them. If you spend your entire session watching tutorials without coding, you are not actually learning.

Weekend sessions (3 to 4 hours): These are for the week's project and for tackling concepts that did not click during the week. Longer sessions let you get into a flow state where you are building something meaningful. Use Saturday for project work and Sunday for filling gaps or getting ahead on next week's material.

One practical tip for Kenyan learners working full-time: do your study session at the same time every day. If you code from 7pm to 9pm every weekday, it becomes a habit within two weeks. If you study "whenever you have time," you will skip more days than you study. Consistency is the only thing that matters for self-study.

After 12 weeks, you can build web applications. That is a real, valuable skill. But you are not job-ready yet, and being honest about that matters.

Job-readiness typically requires 6 to 12 months of consistent practice beyond the basics. That means building more complex projects, learning TypeScript (see our TypeScript guide), understanding testing, getting comfortable with Git workflows, and practicing technical interview skills.

Here is what to focus on after completing this plan:

• Build two to three portfolio-worthy projects. Not to-do apps. Real applications that solve real problems. A project that someone would actually use demonstrates far more than a tutorial clone.
• Learn TypeScript. Most employers expect it now. You have enough JavaScript knowledge to start.
• Contribute to open source. Even small contributions (fixing typos in docs, improving error messages, adding tests) show employers that you can work in a real codebase.
• Start networking. Join Nairobi tech meetups, developer Discord communities, and follow developers on Twitter/X. Relationships lead to opportunities.

If you find that self-study is not working (and it does not work for everyone, there is no shame in that), a structured program can accelerate the process significantly. McTaba's Full-Stack Software & AI Engineering program (KES 120,000) covers everything in this plan plus TypeScript, testing, AI integration, and portfolio projects, with mentorship and code review. Or start with Tech Foundations: Before You Code (KES 2,999) to see if structured learning fits you better.