{"key":"full_stack_learning_path_2026_03_19","title":"Full Stack Learning Path","content":"Full stack learning path discussed on 2026-03-19. Use Angela Yu's course as the backbone, but focus effort on the highest-value sections and build real projects alongside it.\n\nPhase 1: Frontend Foundations\nFocus on HTML, CSS, Flexbox, Grid, responsive design, basic Bootstrap, and basic JavaScript.\nGoal: build pages that actually look decent, understand structure and layout, and stop being afraid of JavaScript basics.\nProjects: personal homepage, product landing page, simple interactive page with buttons, forms, and DOM changes.\nCheckpoint: can build a webpage from scratch without following line by line.\n\nPhase 2: JavaScript Core\nFocus on variables, arrays, objects, functions, loops, conditionals, DOM, events, async basics, and fetch/APIs.\nGoal: understand how interactive web pages actually work.\nProjects: vanilla JS to-do list, weather app using API, quiz app, calculator or habit tracker.\nCheckpoint: can read and write medium-sized JavaScript without feeling lost.\n\nPhase 3: Git, Terminal, and Workflow\nFocus on terminal basics, files and folders, git init/add/commit/status/log, and GitHub push/pull basics.\nGoal: stop treating tooling like magic.\nProjects: put practice projects into GitHub, make at least one repo per project, write simple README files.\nCheckpoint: can create a repo, commit changes, and push them without confusion.\n\nPhase 4: Backend\nFocus on Node.js, Express, routes, request/response, middleware, APIs, error handling, and environment variables.\nGoal: understand how the server side works.\nProjects: notes API, task API, contact form backend, simple journaling backend.\nCheckpoint: can build a backend that accepts, stores, and returns data.\n\nPhase 5: Database\nFocus on SQL, PostgreSQL, tables, relationships, joins, inserts/updates/deletes, and connecting backend to database.\nGoal: stop building apps that lose all their data on refresh.\nProjects: task tracker with PostgreSQL, habit tracker with user accounts, notes app with categories/tags.\nCheckpoint: can design a simple database schema and connect it to an app.\n\nPhase 6: Auth\nFocus on sessions, cookies, login/signup, password hashing, protected routes, auth vs authorization.\nGoal: build an app that feels like a real app, not just a demo.\nProjects: auth-based dashboard app, user-specific tasks or notes app.\nCheckpoint: users can sign up, log in, and only see their own data.\n\nPhase 7: React\nFocus on components, props, state, effects, forms, conditional rendering, API calls, and simple app structure.\nGoal: build a proper frontend for your backend apps.\nProjects: React frontend for task app, React dashboard for notes app, project tracker app.\nCheckpoint: can build a React frontend that talks to a backend API.\n\nPhase 8: Deployment\nFocus on environment variables, production vs dev, deploying frontend, deploying backend, database hosting basics, and domain/DNS basics later.\nGoal: get work online.\nProjects: deploy one full stack app, then deploy a second cleaner version later.\nCheckpoint: can send someone a link to something built.\n\nWhat to skip or downplay: jQuery, deep Web3/DApp material, legacy-feeling sections that do not help the actual goal, and polishing tutorial projects forever.\n\nBest project path in order: personal site, vanilla JS to-do app, weather/API app, Express notes API, PostgreSQL-backed task app, auth-based dashboard, React frontend for the dashboard, deploy the full stack version.\n\nWeekly study flow: 3-4 study sessions per week, 60-90 minutes each, with 2 sessions on course material and 1-2 sessions rebuilding or extending what was learned. Each week should include watching, coding, rebuilding from memory, and one small independent change.\n\nProgress indicators: can build without pausing every two minutes, can debug own mistakes, can explain what code is doing, and can change a project beyond the tutorial.\n\nMain instruction: do not aim to finish the whole course fast. Aim to finish the important sections, build real projects alongside them, keep notes on what is actually understood, and ask for help when blocked instead of silently spiraling.\n\nPhase 1 execution plan:\nThe goal of Phase 1 is not just to learn frontend in the abstract, but to get comfortable making pages on purpose.\nWhat to learn: HTML structure, semantic elements, headings, paragraphs, links, images, lists, forms, CSS selectors, colors, spacing, borders, typography basics, Flexbox, Grid, responsive layout, basic Bootstrap, and very basic JavaScript for interaction.\nWhat to build: personal homepage, product landing page, and a simple interactive page with buttons, form input, and DOM changes.\nHow to work: for each major section, watch the lesson, build along once, rebuild the same thing without following line by line, then change one thing independently.\nExamples of independent changes: different color palette, different layout, add a section, make it mobile-friendly, or add a button interaction.\nWeekly rhythm for Phase 1: 3 to 4 sessions per week, 60 to 90 minutes each, with 2 sessions on course content and 1 to 2 sessions rebuilding or improving your own version.\nSuggested learning order: HTML basics, CSS basics, Flexbox, Grid, responsive design, basic Bootstrap, and basic JavaScript DOM work.\nRules: do not copy blindly, do not chase perfection, do not move on if you cannot explain what the code is doing, and do not spend forever polishing one tutorial page.\nPhase 1 checkpoint: can build a simple webpage from scratch, style it so it does not look broken, make it work on desktop and mobile, and add a little JavaScript interaction without panicking.\nBest outcome by end of Phase 1: 3 small projects, 1 GitHub repo for each project if possible, and enough comfort with HTML/CSS/JS basics that Phase 2 does not feel impossible.\n\n---\n**2026-03-19 10:50:13 UTC | AI Update via MCP**","summary":"Full stack learning path discussed on 2026-03-19. Use Angela Yu's course as the backbone, but focus effort on the highest-value sections and build real projects alongside it.\n\nPhase 1: Frontend Foundations\nFocus on HTML, CSS, Flexbox, Grid, responsive design, basic Bootstrap, and basic JavaScript.\nGoal: build pages that actually look decent, understand structure and layout, and stop being afraid of JavaScript basics.\nProjects: personal homepage, product landing page, simple interactive page with buttons, forms, and DOM changes.\nCheckpoint: can build a webpage from scratch without following line by line.\n\nPhase 2: JavaScript Core\nFocus on variables, arrays, objects, functions, loops, conditionals, DOM, events, async basics, and fetch/APIs.\nGoal: understand how interactive web pages actually work.\nProjects: vanilla JS to-do list, weather app using API, quiz app, calculator or habit tracker.\nCheckpoint: can read and write medium-sized JavaScript without feeling lost.\n\nPhase 3: Git, Terminal, and Workflow\nFocus on terminal basics, files and folders, git init/add/commit/status/log, and GitHub push/pull basics.\nGoal: stop treating tooling like magic.\nProjects: put practice projects into GitHub, make at least one repo per project, write simple README files.\nCheckpoint: can create a repo, commit changes, and push them without confusion.\n\nPhase 4: Backend\nFocus on Node.js, Express, routes, request/response, middleware, APIs, error handling, and environment variables.\nGoal: understand how the server side works.\nProjects: notes API, task API, contact form backend, simple journaling backend.\nCheckpoint: can build a backend that accepts, stores, and returns data.\n\nPhase 5: Database\nFocus on SQL, PostgreSQL, tables, relationships, joins, inserts/updates/deletes, and connecting backend to database.\nGoal: stop building apps that lose all their data on refresh.\nProjects: task tracker with PostgreSQL, habit tracker with user accounts, notes app with categories/tags.\nCheckpoint: can design a simple database schema and connect it to an app.\n\nPhase 6: Auth\nFocus on sessions, cookies, login/signup, password hashing, protected routes, auth vs authorization.\nGoal: build an app that feels like a real app, not just a demo.\nProjects: auth-based dashboard app, user-specific tasks or notes app.\nCheckpoint: users can sign up, log in, and only see their own data.\n\nPhase 7: React\nFocus on components, props, state, effects, forms, conditional rendering, API calls, and simple app structure.\nGoal: build a proper frontend for your backend apps.\nProjects: React frontend for task app, React dashboard for notes app, project tracker app.\nCheckpoint: can build a React frontend that talks to a backend API.\n\nPhase 8: Deployment\nFocus on environment variables, production vs dev, deploying frontend, deploying backend, database hosting basics, and domain/DNS basics later.\nGoal: get work online.\nProjects: deploy one full stack app, then deploy a second cleaner version later.\nCheckpoint: can send someone a link to something built.\n\nWhat to skip or downplay: jQuery, deep Web3/DApp material, legacy-feeling sections that do not help the actual goal, and polishing tutorial projects forever.\n\nBest project path in order: personal site, vanilla JS to-do app, weather/API app, Express notes API, PostgreSQL-backed task app, auth-based dashboard, React frontend for the dashboard, deploy the full stack version.\n\nWeekly study flow: 3-4 study sessions per week, 60-90 minutes each, with 2 sessions on course material and 1-2 sessions rebuilding or extending what was learned. Each week should include watching, coding, rebuilding from memory, and one small independent change.\n\nProgress indicators: can build without pausing every two minutes, can debug own mistakes, can explain what code is doing, and can change a project beyond the tutorial.\n\nMain instruction: do not aim to finish the whole course fast. Aim to finish the important sections, build real projects alongside them, keep notes on what is actually understood, and ask for help when blocked instead of silently spiraling.\n\nPhase 1 execution plan:\nThe goal of Phase 1 is not just to learn frontend in the abstract, but to get comfortable making pages on purpose.\nWhat to learn: HTML structure, semantic elements, headings, paragraphs, links, images, lists, forms, CSS selectors, colors, spacing, borders, typography basics, Flexbox, Grid, responsive layout, basic Bootstrap, and very basic JavaScript for interaction.\nWhat to build: personal homepage, product landing page, and a simple interactive page with buttons, form input, and DOM changes.\nHow to work: for each major section, watch the lesson, build along once, rebuild the same thing without following line by line, then change one thing independently.\nExamples of independent changes: different color palette, different layout, add a section, make it mobile-friendly, or add a button interaction.\nWeekly rhythm for Phase 1: 3 to 4 sessions per week, 60 to 90 minutes each, with 2 sessions on course content and 1 to 2 sessions rebuilding or improving your own version.\nSuggested learning order: HTML basics, CSS basics, Flexbox, Grid, responsive design, basic Bootstrap, and basic JavaScript DOM work.\nRules: do not copy blindly, do not chase perfection, do not move on if you cannot explain what the code is doing, and do not spend forever polishing one tutorial page.\nPhase 1 checkpoint: can build a simple webpage from scratch, style it so it does not look broken, make it work on desktop and mobile, and add a little JavaScript interaction without panicking.\nBest outcome by end of Phase 1: 3 small projects, 1 GitHub repo for each project if possible, and enough comfort with HTML/CSS/JS basics that Phase 2 does not feel impossible.\n\n---\n**2026-03-19 10:50:13 UTC | AI Update via MCP**","status":"active","namespace":"general","namespace_name":"general","namespace_tier":"shared","tags":[]}