75-day sprint
Lv 10 XP🔥 0

75 days to the end of the year

Your full AI engineer roadmap as a daily sprint, Sunday October 18 to Thursday December 31, 2026. Fifteen real-world projects with pilot users, all 23 chapters of Hands-On LangChain, a ByteByteGo article every day, spaced revision, and something to present every week. Bonus work is marked in gold, for days when you have extra time. Plan on about 3 focused hours a day, plus 50 minutes on every seventh day.

–today
–days until Dec 31
15 + 1projects + bonus
23book chapters
75 + 150core + bonus articles
Level1Intern0 XP

Five phases

Each phase ends with a review day and a gate to pass before moving on.

The method

Ten rules that turn tutorials into skills and repos into CV evidence.

  1. One project at a time, 3–4 new skills maxSmall enough to finish, big enough to matter.
  2. Number targets before codeWrite the targets into the README first. "Recall@5 is 84%" beats "it works".
  3. Measured by a committed scriptEvery repo has an eval or bench script that prints the scoreboard.
  4. Each project feeds the nextOutputs become inputs, so the small projects add up to two capstones.
  5. Every core skill appears at least twiceThe second use is where it sticks. See the skill matrix.
  6. The book lands just before it's neededEach chapter is scheduled a few days before the project that applies it.
  7. One system design article every dayTen minutes of ByteByteGo matched to what you're building.
  8. Real users, real dataEvery project names a real person who uses it and real data it runs on.
  9. Revise on a schedule, present everythingTen minutes of spaced recall daily, and every project shown to a named audience.
  10. Time-box, then move onIf a target is still missed at the deadline, record the number and why, then continue.

A day in the sprint

Build 2 h
Book 30 min
Article
Revise
Bonus

On days without a book chapter, the 30 minutes go back to building. Python depth is on demand: when a project's Python tag matches the problem in front of you, open its card.

Read (5 min)Study the article's diagram first, then the text.
Note (3 min)One-line takeaway in notes/bytebytego.md.
Connect (2 min)Where does it show up in today's project?

Day by day

Every day has a build task, a core article, and two bonus articles; book days add a chapter with a reading note. A day counts as complete when its build, book, core article, and revision are ticked, plus the weekly review and share on every seventh day.

Projects

Each project has a real-world brief, a scoreboard for your measured results, and a presentation for a named audience. P16 is a bonus project.

Revise, present, and illustrate

Learning sticks when you recall it on a schedule and explain it to someone else. Everything here is built into the day-by-day plan and earns XP.

Every day · 10 minSpaced revisionRecall the chapters from 3 and 10 days ago and the articles from 7 and 21 days ago.
Every 7th day · 30 minWeekly reviewRe-explain the week from your notes without looking, and make flashcards for the gaps.
Every 7th day · 20 minShare one artifactA diagram, a post, or a 60-second video for others.
Every projectPresent itA demo, diagram, or lesson to a named audience.
End of every phaseLive show and tellDemo to 2–3 people and collect feedback. Days 14, 30, 52, 62, and 75.

Presentation kit

Tools for illustrating

For spaced revision, any flashcard app works; Anki is free and schedules reviews for you.

Capstones for your CV

Each capstone is assembled from finished small projects and tested by real pilot users. Fill every highlighted placeholder with a measured result only.

Real-world pilot plans

Nizam pilot: legal and compliance users

  1. Day 12 Message 3 potential pilot users: lawyers, compliance officers, or law students.
  2. Day 17 Collect at least 30 of their real questions for the eval set.
  3. Day 22 First live session: they try Nizam and rate 10 answers.
  4. Day 30 Phase show and tell with the pilot group.
  5. Days 53–62 They move to the live AWS URL.
  6. Day 71 15-minute usability sessions on the Next.js UI.

Raddad pilot: one real small business

  1. Day 25 Find one clinic, restaurant, or store willing to pilot.
  2. Day 36 Build the tools on their real FAQs, hours, and booking rules.
  3. Day 39 Turn their real customer questions into 30 test conversations.
  4. Day 41 Demo to the owner and collect a rating.
  5. Day 52 Phase show and tell with the owner.
  6. Day 58 Deploy for the business, with Langfuse tracking quality.

Anonymize customer data, get written permission before using anyone's messages, and never put real personal data in a public repo.

Skill coverage

Which project trains which skill. Dashed gold dots are the bonus project.

Your resource stack, rated

Relevance: how much the skill matters for AI engineer roles. Importance: how much your CV needs it now. Strength: resource quality at your level.

Python, when you need it

Not scheduled. When a project's Python tag matches the problem in front of you, open the card, learn just that, and get back to building.

Bonus Optional

Everything here is extra, for days when the core work is done and you have energy left. Each item earns XP and counts toward the Legend level.

Bonus learning

    Bonus projectP16 Raddad Console

    A Next.js admin dashboard for Raddad with a handoff inbox, Langfuse-linked conversations, analytics, and sign-in. It's in the Projects section.

    Bonus articles150 extra ByteByteGo reads

    Two per day in the day-by-day plan, chosen from the same theme as that day's work.

    Weekly bonusRe-read what your capstones lean on

    Chapters 8–9 for Nizam, and 13–14 and 18–20 for Raddad.

    2027 specializations

    Achievements