What Happens in Week One of a Coding Bootcamp?

Most bootcamps send a pre-work package before the program starts. This usually includes installing a few pieces of software and completing some introductory reading or exercises. Do this. Students who show up on day one without completing the pre-work spend the first two days catching up while everyone else moves forward.

At minimum, you should have a working laptop with a code editor installed (usually Visual Studio Code), a web browser (Chrome or Firefox), and a stable internet connection. Some programs also ask you to install Git, Node.js, and create accounts on GitHub and Slack or Discord. Follow the instructions exactly. If something fails during installation, screenshot the error and bring it to day one. That is what the first session is for.

If your bootcamp did not send pre-work, prepare anyway. Install VS Code. Create a GitHub account. Open your terminal or command prompt and type a few commands. The less unfamiliar everything is on day one, the more you can focus on the actual content.

Day one rarely involves much code. It is mostly orientation. Meet the instructors. Meet your cohort. Learn how the program is structured: where to find assignments, how to submit work, when sessions happen, how to ask for help.

Then comes the environment setup. This is the part that trips up the most people. Setting up a development environment means getting VS Code configured, making sure Git is working, cloning a repository, running a local server, and confirming everything connects. If you have never used a terminal before, this feels alien. You are typing commands into a black screen and hoping something happens. Things will break. Error messages will appear in red. This is normal.

Do not compare yourself to anyone else in the cohort during setup. Some people have used terminals before. Some have not. The person who finishes setup in 20 minutes is not smarter than the person who takes 2 hours. They just have more prior exposure to these tools. By week 3, that gap closes.

The first real code you write in a bootcamp is usually HTML. You open a text file, type some tags, save it, and open it in a browser. A heading appears. A paragraph appears. You change the text, refresh the browser, and the change shows up. That loop, write code, save, see the result, is the foundation of everything that follows.

Some programs start with JavaScript fundamentals instead: variables, strings, numbers, console.log. You type something like console.log("Hello, Nairobi") and see the text appear in the browser console. It feels small. It is small. But it is the beginning of a completely new way of thinking about problems.

The code itself is not hard in week one. You will not struggle with <h1>My Page</h1>. What you might struggle with is understanding why the tools work the way they do. Why do I need a terminal? Why does Git exist? What is a local server? These conceptual questions take time to settle. Do not expect them to make complete sense on day one. They will click over the coming weeks as you use the tools repeatedly.

The hardest part of week one is not the code. It is the language. In a single session, you might hear: repository, clone, commit, push, pull, merge, branch, terminal, CLI, node, npm, package, dependency, local, remote, server, client, DOM, and API. If you have never written code before, every single one of these words is new.

This is overwhelming. It is supposed to be. You are learning a new professional vocabulary alongside new tools and new concepts. Nobody absorbs all of it in week one. You absorb enough to keep going, and the rest fills in through repetition.

A practical tip: keep a notebook (physical or digital) where you write down every new term and its meaning in your own words. Not the textbook definition. Your own understanding. "Git = a system that saves versions of my code so I can undo things" is more useful to you right now than a formal definition. Update these entries as your understanding deepens.

In the chaos of setup and orientation, it is easy to treat the social part of week one as background noise. Do not make that mistake. The people in your cohort are the people you will learn with, struggle with, and build projects with over the next several months.

Introduce yourself. Learn names. Exchange phone numbers or join the group chat. When you are stuck at 9pm on a Tuesday trying to figure out why your code is not working, your cohort mate who solved the same problem two hours ago is your fastest lifeline. Not Google. Not Stack Overflow. The person sitting (or logged in) next to you.

In online programs, this social connection requires more effort because you are not physically in the same room. Make the effort anyway. Respond in the chat. Turn your camera on during sessions. Ask questions out loud, not just in text. The students who engage with their cohort from week one are consistently the ones who finish the program.

The amount of reading. Coding is not all typing. In week one, you will read installation guides, documentation, error messages, and instructions. A lot of reading. If you expected to spend 100 percent of your time writing code, adjust that expectation. Professional developers spend significant time reading documentation and other people's code.

Error messages. Your code will produce errors. Red text will fill your screen. This is not failure. It is feedback. Learning to read error messages and use them to fix problems is one of the most important skills you will develop. In week one, those red messages feel personal. By month 3, you will scan them calmly and know exactly where to look.

How slow it feels. You might spend 45 minutes on something that seemed like it should take 5. A missing semicolon. A file saved in the wrong folder. A Git command typed slightly wrong. This slowness is frustrating, but it is exactly how learning works. Speed comes later, from repetition.

Imposter syndrome. Someone in your cohort will ask a question using vocabulary you have never heard. Someone will finish an exercise faster than you. You will wonder if you belong here. You do. That person who seems ahead is also struggling with something you will find easy. Everyone's knowledge has gaps in different places.

By Friday of week one, you will have a working development environment, a GitHub account with at least one repository, and a small project or exercise completed. You will know the names of a few people in your cohort. You will have heard about 50 new terms and understood maybe 30 of them. You will feel tired.

That is exactly where you should be. Week one is not about mastery. It is about setup, orientation, and the first step. The real learning starts in week 2 when you begin building things that are slightly beyond your comfort zone.

The most important thing you can do at the end of week one is show up for week two. Forty percent of people who think about quitting a bootcamp think about it in the first two weeks. The material is not hard yet. The adjustment is. If you get through week one and come back for week two, you have cleared the first and most psychological hurdle.