Inside a 26-Week Dev Marathon: What You Build Month by Month

Some bootcamps promise to make you job-ready in 8 or 12 weeks. That works for people who can study full-time, 40 to 60 hours per week. For working professionals who can give 15 to 20 hours per week, that pace is not realistic.

Twenty-six weeks gives you the same total hours of learning as a 12-week full-time program, but spread across a schedule that lets you keep your job. It also gives your brain time to absorb. Coding concepts need repetition and practice to stick. Cramming everything into 8 weeks means you memorize patterns without understanding them. Twenty-six weeks means you have time to struggle with a concept, sleep on it, and come back the next day with clarity.

The marathon metaphor is intentional. This is not a sprint. The students who finish are the ones who pace themselves, not the ones who try to do everything at once in the first month.

The first month is about building a foundation you can actually stand on. You start with HTML and CSS, then move into JavaScript and TypeScript. By the end of month 1, you can build a static website from scratch, style it properly, and add interactivity.

Week 1: Setup, tooling, HTML basics, CSS basics. You build your first web page. It will not win any design awards, and that is fine. The point is the workflow: write code, save, see the result in a browser.

Week 2: CSS layouts (Flexbox, Grid), responsive design. Your pages start looking professional. You learn to build layouts that work on phones and laptops.

Week 3: JavaScript fundamentals. Variables, functions, loops, DOM manipulation. You make things happen on the page: click a button, show a menu, validate a form. This is where coding starts feeling like coding.

Week 4: TypeScript introduction. Why types matter. How TypeScript prevents bugs. You convert a JavaScript project to TypeScript and see the difference. You also set up Git properly and start version-controlling your work.

By the end of month 1, you have 1 to 2 deployed projects. Simple, but live on the internet.

Month 2 is when the shift happens. You stop thinking in pages and start thinking in components. React changes how you build user interfaces, and it takes a few weeks for the mental model to click.

Weeks 5 to 6: React fundamentals. Components, props, state, hooks. You rebuild things you already know how to build in HTML/CSS/JS, but now using React. This feels redundant at first. It is not. The component model is how modern applications are built, and you need to internalize it through repetition.

Weeks 7 to 8: Next.js. Routing, server-side rendering, API routes. You build a multi-page application with real navigation. GitHub Copilot becomes part of your workflow here. You start using it to autocomplete boilerplate, suggest code patterns, and speed up repetitive tasks. Learning to use AI tools as a developer is not optional in 2026.

By the end of month 2, you have built 3 to 4 projects total. Your applications look and feel like real products. The code is structured, typed, and version-controlled.

Month 3 is the hardest month. This is where the dropout risk is highest, and it is where the program earns its value.

Until now, everything has been visual. You write code and see results on a screen. Back-end development is different. You write code that runs on a server, processes data, and sends responses that have no visual component. It is abstract, and that abstraction frustrates people who were thriving with front-end work.

Weeks 9 to 10: Node.js and Express. APIs. You build your first server. You create endpoints that receive data, process it, and return results. You connect a front-end to a back-end for the first time. Two separate things talking to each other. It feels like magic when it works and like madness when it does not.

Weeks 11 to 12: PostgreSQL and Supabase. Databases. You design tables, write queries, and store real user data. Your applications now persist information. Close the browser, open it again, and the data is still there. This is the difference between a demo and a real application.

Week 13: Authentication. Login, signup, protected routes, user sessions. Your apps now have real users with real accounts. This week ties front-end, back-end, and database together into a full-stack application.

By the end of month 3, you understand how web applications actually work from end to end. The difficulty spike is real, but so is the understanding you gain.

Month 4 is where McTaba's curriculum diverges from most bootcamps. Two things happen: AI features become part of what you build, and you learn the African Stack.

Weeks 14 to 15: AI integration. You have been using GitHub Copilot and Claude as coding assistants since month 2. Now you build applications that have AI features. RAG-based search, AI-powered user interfaces, integrating language models into your projects. You are not just using AI to code. You are building products that use AI.

Weeks 16 to 17: The African Stack. M-Pesa integration using the Daraja API: STK push, payment confirmation, transaction status. USSD menu design. WhatsApp Business API for notifications and customer interaction. These are the tools that make products work in Kenya and East Africa. A developer who can integrate M-Pesa payments is immediately more hireable in this market than one who cannot.

By the end of month 4, you can build a full-stack application with AI features that accepts M-Pesa payments and sends WhatsApp notifications. That is not a tutorial exercise. That is a product.

The final stretch is about building. You have the skills. Now you apply them to production-grade capstone projects that become the centerpiece of your portfolio.

Weeks 18 to 20: Your first capstone project. You design, build, and deploy a complete application from scratch. The idea is yours (with guidance). The code is yours. The deployed product is yours. Your mentor reviews your code, gives feedback, and pushes you toward professional-grade quality.

Weeks 21 to 23: Your second capstone. This one is harder. More complex features. Better architecture. You apply everything from the first capstone plus the feedback you received. The goal is visible improvement between project 1 and project 2.

Weeks 24 to 26: Portfolio polish and career preparation. You clean up all your projects, write documentation, ensure everything is deployed and working. You build a developer portfolio site. You prepare to talk about your projects in interviews: what you built, what decisions you made, what you would do differently.

By week 26, you have 8 production-grade apps at live URLs. A GitHub profile with real commit history. A portfolio you can hand to any employer and say: "I built these."

Bootcamp marketing shows the beginning (excitement) and the end (portfolio, job readiness). Nobody markets the middle. The middle is where you sit with a database error at 9pm on a Wednesday, tired from work, wondering if you should have just stayed in your current career.

The middle is hard. Week 10 is hard. Week 13 is hard. The transition from "I can see what my code does" (front-end) to "I have to trust that my code is doing the right thing behind the scenes" (back-end) is a genuine cognitive shift. People who breezed through month 1 and 2 sometimes struggle deeply in month 3.

This is normal. Not a sign of failure. The students who finish are not the ones who found it easy. They are the ones who found it hard and kept going anyway. If you are reading this during month 3 and thinking about quitting, you are exactly where everyone else was at this stage. The other side of that difficulty is competence.