Archived 2026-10-01. Superseded by the three-course series — SWE 101 → SWE 102 → SWE 103. Kept for the reasoning it records; it is no longer the plan.

Weeks 1–52+. Your original 15 phases, re-sequenced for job relevance and mapped onto notes that already exist. Roughly 2–4 h/week — the Tuesday slot, plus whatever Saturday has left.

This track continues past employment. It always was going to. Treating it as a prerequisite for applying is what pushed the original plan to 52 weeks before a single CV went out.


What got cut, and why

Not a criticism of the scheme — it’s a well-built beginner-to-senior curriculum. It’s just aimed at someone who isn’t you.

OriginalWeeksVerdict
Phase 1 — what is software / SDLC / types of engineer1Cut. You are one, across twelve projects. One evening skimming SDLC vocabulary for interviews, not a week.
Phase 2–3 — computational thinking, complexity2–3Folded into DSA. Big-O and recursion get learned through problems, not before them.
Phase 4–7 — variables, loops, functions, OOP4–7Cut. Four weeks on material nextvibe and the Java projects already prove. The single largest saving in the plan.
Phase 5 — Git, Linux, tooling13–14Cut to a checklist. You use these daily; git/ and linux/ are written. Skim for gaps only.
Phase 10 — testing30–32Compressed to 1 week. gees-arise/learning/07-testing and the strictenv/json-healer banks show this is owned.
Phase 12 — DevOps38–41Compressed to 1 week. nextvibe/socioboom/gees-arise all have deployment notes; the vault’s own CI/CD is yours.
Phase 15 — projects49–52Moved to week 3 and made the flagship. Projects are not the graduation ceremony.

Net saving: about 20 weeks, all of it spent proving things already proven.


The re-sequenced order

Re-ordered on one principle: what gets asked in an interview and what makes the flagship better comes first. Depth-for-its-own-sake comes after the offer.

#TopicWeeksReadWhy here
1Software design — modularity, coupling/cohesion, SOLID, patterns, DI, layering, clean architecture3patterns · best practices · structuring a backendFirst because it improves the flagship while you build it, and code-quality questions start at junior level
2Architecture & system design4fundamentals · building blocks · the roundMoved from week 45. It’s an interview round from junior upward — cannot be at the end
3Databases, deep — internals, indexes, transactions, MVCC, query plans3the course (01–10) · bankYou use Postgres daily without seeing underneath. EXPLAIN ANALYZE is the highest-value single skill here
4Networking & web4the course · bank”What happens when you type google.com” is still asked. Also underpins every latency question
5Security2web security · crypto · bankMoved from week 42. Small, high-yield, and prompt injection is an AI-engineering interview question
6Backend consolidation — API design, authz, caching, rate limiting, jobs, versioning2backend · authMostly consolidation of what you’ve shipped — reconstruct, don’t relearn
7AI engineering depth — RAG, agents, evals, cost/latency, structured output4the track, Part II especially 12-evalsNot in the original scheme at all, and it’s half your target role
8Testing & quality1practices · bankCompressed — gap-fill only
9DevOps & deployment1devops · CI/CDCompressed — gap-fill only
10Concurrency & distributed systems5the 15-note courseKept deep, moved late. Genuinely valuable, rarely decisive for a first offer
11CS spine — OS, complexity, architectureongoingOS · theory · architecturePost-offer. This is the “understand why software is built this way” objective, and it has no deadline

≈ 29 weeks of foundation, running under a 28-week hire track, then item 11 continues indefinitely.


System design exercises

Your list, kept as-is — it’s the right list. One per fortnight from week 12, out loud, on the board, 45 minutes, before reading anything.

URL shortener → chat app → notification system → payment system → social feed → ride-sharing → video platform

Then compare against the notes. The gap between your answer and the note is the actual lesson; write only that gap in the notebook.

Do the payment system one carefully — you built a payments ledger in nextvibe and a direct-debit sandbox in Java. That’s a design question you can answer from experience rather than theory, and interviewers can hear the difference.


The design exercise from your scheme

Design a banking system. Don’t code it. Think about entities, relationships, responsibilities, interfaces, data, failures, security, scalability.

Keep this exactly as written. It’s the best single exercise in the original document, and “don’t code it” is the instruction that makes it work.

↑ Back to SWE 101 — Archive