moc · fullstack · learning-path

Full-Stack Developer Learning Path

01 Maps/Full-Stack Developer Learning Path.md

Full-Stack Developer Learning Path

This path combines the Burmese-language libraries of Ei Maung and Saturngod with the evidence-driven agent workflow in Spec Map Build Prove Learn. Follow it by building one evolving project rather than only reading.

Stage 0 — computation and tools

Learn: logic, variables, control flow, functions, collections, basic Python, terminal, Linux, and Git.

Resources: Saturngod's Programming Basic, Ei Maung's Ubuntu: Linux for You, and Git and Version Control.

Proof: create a command-line program that reads data, validates it, writes a result, has tests, and lives in a clean Git repository.

Stage 1 — how the web works

Learn: semantic HTML, CSS layout, responsive design, browser behavior, HTTP, forms, accessibility, and basic security.

Resources: Saturngod's HTML, Ei Maung's Bootstrap - On Point, and Web Fundamentals.

Proof: build a responsive, keyboard-usable site with real loading/error/empty states and inspect it at mobile and desktop widths.

Stage 2 — programming in the browser

Learn: JavaScript types, functions, modules, objects, asynchronous work, DOM/events, network requests, and error handling.

Resources: Ei Maung's JavaScript - On Point and Professional Web Developer 2023.

Proof: build a no-framework application that calls an API, validates input, persists useful local state, and handles failures visibly.

Stage 3 — data and backend foundations

Learn: relational modeling, SQL, constraints, indexes, transactions, HTTP APIs, authentication versus authorization, validation, and server-side architecture.

Resources: Saturngod's Database Basic, Ei Maung's API - On Point, PHP - On Point, Laravel - On Point, Databases, and API Design.

Proof: deliver a documented CRUD API with a relational schema, migrations, authorization checks, invalid-case tests, pagination, and useful errors.

Stage 4 — component frontends

Learn: component boundaries, one-way data flow, state, effects, routing, forms, server/client rendering, and frontend testing.

Resources: Ei Maung's React - On Point and Rockstar Developer 2025.

Proof: connect a React/Next interface to the Stage 3 API and verify loading, empty, error, permissions, responsive layout, and accessibility.

Stage 5 — design and software engineering

Learn: UML as a communication tool, design patterns as named tradeoffs, requirements, architecture, delivery, testing, code review, deployment, and observability.

Resources: Saturngod's UML Basic, Design Pattern, Software Engineering, Developer Intern, Ei Maung's Rockstar Developer, and Software Delivery Map.

Proof: write an architecture decision, ship through CI, document rollout/rollback, review a peer-sized diff, and investigate one production-like failure using evidence.

Stage 6 — AI-assisted and agentic engineering

Learn: precise product direction, repository guidance, context boundaries, vertical slices, tool safety, automated and browser verification, evaluation, and durable feedback loops.

Resources: Ei Maung's Vibe Coding, Agentic Coding, n8n, Agentic Fullstack Development Webinar, and AI Engineering Map.

Proof: use Spec Map Build Prove Learn to deliver a bounded feature with a product brief, permission envelope, tests, browser evidence, diff review, and one persistent improvement to repository guidance.

Optional mobile branch

Saturngod's current work emphasizes SwiftUI, Flutter, Laravel APIs, React, and Next.js. Apply the same fundamentals: model data and invariants first, separate UI state from domain behavior, verify accessibility and device layouts, and keep APIs contract-driven.

Study rhythm

For each stage:

  1. Predict and build before reading the complete solution.
  2. Read only the section needed to unblock the project.
  3. Explain the mechanism in a Concept Note.
  4. Add tests or visible evidence.
  5. Record mistakes in Learning Log.
  6. Finish the stage with a demonstrable artifact, not a reading percentage.

Knowledge connections