Bootcamp Survival: The Reading List That Saves Your Cohort
Bootcamp week 4.
Half the cohort already burned out on YouTube tutorials.
The instructor said "just read the docs."
Cool. Which docs? Where? In what order? On what device? The instructor moved on to the next concept before answering any of that.
This is the reading list that saves your cohort.
Table of Contents
- The Bootcamp Documentation Gap
- The Week-by-Week PDF Stack
- Why Mentors Should Hand Out a PDF Kit
- A Real Cohort Story
- The "Read 30 Pages a Day" Discipline
- Build Your Bootcamp Shelf
The Bootcamp Documentation Gap
Bootcamps are great at: pace, structure, peer support, accountability.
Bootcamps are bad at: teaching you how to read technical material like a working engineer.
You leave bootcamp able to follow tutorials. You don't necessarily leave knowing how to read API docs end-to-end and figure out something new.
That gap is what kills bootcamp grads in their first job. The senior says "the docs cover this" and you panic.
The reading list below is what closes the gap during bootcamp, not after.
The Week-by-Week PDF Stack
Most bootcamps follow a similar arc. Here's the reading list mapped to that arc.
Weeks 1-2: HTML / CSS Foundations
| URL to bundle | |
|---|---|
| MDN HTML reference | developer.mozilla.org/en-US/docs/Web/HTML |
| MDN CSS reference | developer.mozilla.org/en-US/docs/Web/CSS |
| Flexbox guide (CSS-Tricks) | css-tricks.com/snippets/css/a-guide-to-flexbox/ |
| Grid guide (CSS-Tricks) | css-tricks.com/snippets/css/complete-guide-grid/ |
Generate each via OfflineDocs. Same from-url method we use for GitHub READMEs.
Weeks 3-5: JavaScript
| URL | |
|---|---|
| MDN JavaScript guide | developer.mozilla.org/en-US/docs/Web/JavaScript/Guide |
| MDN JavaScript reference (Built-ins) | developer.mozilla.org/en-US/docs/Web/JavaScript/Reference |
| You Don't Know JS (the book series) | github.com/getify/You-Dont-Know-JS |
The MDN JS guide is the canonical learning text. Read it cover-to-cover before week 5.
Weeks 6-8: Frontend Framework (React / Vue / Svelte)
Whichever your bootcamp uses, generate the PDF:
- React: see the React docs offline guide
- Vue: see the Vue docs offline guide
- Svelte: see the Svelte handbook PDF guide
Read the conceptual core (React's "Learn", Vue's "Essentials", Svelte's "Tutorial").
Weeks 9-11: Backend
| URL | |
|---|---|
| Node.js docs | nodejs.org/docs/latest/api/ |
| Express docs | expressjs.com/en/4x/api.html |
| (Or Python: see Python stdlib workflow) | |
| HTTP fundamentals (MDN) | developer.mozilla.org/en-US/docs/Web/HTTP |
| REST principles (some canonical write-up) | varies |
The "HTTP fundamentals" reading is non-obvious but critical. Most bootcamp grads can write Express handlers without truly understanding HTTP. Read MDN's HTTP section. It'll level you up.
Weeks 12+: Database + Deployment
| URL | |
|---|---|
| Postgres tutorial | see the Postgres workflow |
| Git documentation | git-scm.com/doc |
| Docker basics | docs.docker.com/get-started/ |
| Whichever cloud (Vercel / Heroku / AWS basics) | varies |
Why Mentors Should Hand Out a PDF Kit
If you teach bootcamp or mentor bootcamp students, here's a free idea:
Generate a "Day 1 reading kit." 5-7 PDFs. Hand to every new student.
Pre-generated. Pinned to canonical versions. Tested by you.
Now the new student has a coherent starting point. They don't waste week 1 trying to figure out what to read. They open the PDFs you gave them.
This is the same playbook as team training materials, just for an educational context.
A Real Cohort Story
I mentored a bootcamp cohort of 12 last year.
Halfway through, I noticed the top 3 students in the cohort had something in common: they were all reading docs end-to-end on weekends, on tablets. Not tutorials. Docs.
The other 9 were stuck in the YouTube → "what do I build?" → forgot-half-of-it loop.
For the second half of the bootcamp, I made the top-3 habit explicit. Generated PDF reading lists. Required at least 2 hours of weekend doc-reading per week.
The cohort's outcomes shifted noticeably. More grads landed jobs faster. The ones who landed jobs got positive feedback in code review specifically about "reading the docs first." That trait is rare in junior devs and immediately visible.
This connects to the broader personal dev library habit — a reading habit that compounds.
The "Read 30 Pages a Day" Discipline
Here's the simple rule that worked:
30 pages. Every day. Of something technical and structured. Not blog posts. Not Twitter. Not videos. Pages of docs or a book.
That's roughly an hour of reading. Doable.
Compounded over 12 weeks of bootcamp, that's 2,500+ pages of structured technical reading. By the end of the program, you've absorbed substantially more than the cohort that didn't.
The 30 pages a day habit, more than anything else, is what separates the senior-juniors from the actually-juniors at month-12.
Build Your Bootcamp Shelf
offlinedocs.ai/new → paste each docs URL → generate.
20 minutes of generation work this week. A reading list that lasts your whole bootcamp.
Pick one PDF a week. Read it. Mark it up. Talk to your cohort about it.
By demo day, you'll be the person in the cohort who gets the docs in a way the others don't.
That difference shows up in interviews. Hiring managers can tell.
Ready to Get Started?
Start creating your Offline Docs Now! Reduce screen time and save your eyes.