{guerz.lol}

the web dev playbook v.4

much less fog;
more forward

THE MINDSET:

six freeCodeCamp Certifications in order; each one it's own module.

a module opens when the one preceding it becomes deservedly earned once fully learned.

unlike previous iterations of my playbook, i did away with a weekly scheduled format. the one you see below grants myself the time necessary to fully digest the material. some things take longer than a week. that's not falling behind; that's awareness of one's of limits. remember, humility is a virtue.

THE MILESTONES:

  • June 9, 2027 — Front-End Developer
  • December 2028 — Web Development B.S. Full Sail University
  • June 9, 202? — Full-Stack Developer
1 · responsive web design 2 · javascript 3 · front end libraries 4 · python 5 · backend + apis 6 · data visualization

you are here — responsive web design review

STUDY: Responsive Web Design curriculum review
METHOD: systemmatic wall of taped index cards, enhanced with my highlighter format
SUPPORT: Kuliko AI index cards and generated quizzes • reviewing weak areas with Coach Gee (ChatGPT)
CHECKPOINT: claim the freeCodeCamp Responsive Web Design v9 Certification

module 1 — responsive web design · html / css foundations

the spine
fCC Responsive Web Design v9 Certification

semantic HTML & forms → box model → flexbox → typography, positioning & attribute selectors → responsive design & variables → grid → animations

every build shipped to guerz.lol's FCC Build Archive — rebuild-and-comment method, every line explained or it doesn't count

*absolutely zero forced pressure to cert exam. will take it when it's taken

module 2 — javascript · a real lane, not just glue

the spine
fCC JavaScript Algorithms & Data Structures Certification

git + github from the terminal for all real work, from day one of this module

build-it-cold shifts to JS: variables → arrays/objects/loops → DOM + events → fetch/JSON + async

*opens once module 1's cert is claimed — no earlier.

module 3 — front end development libraries · react / redux

the spine
fCC Front End Development Libraries cert — React, Redux, Sass

at least one real component-driven project shipped to guerz.lol

*opens once module 2's cert is claimed.

module 4 — scientific computing with python {the back half begins}

the spine
fCC Scientific Computing with Python Certification — Python fundamentals

straight into AI/LLM work

CLI tools, files/CSV/JSON, APIs from Python

Anthropic/OpenAI calls and local models via Ollama/LM Studio on the M4 24GB RAM

*opens once module 3's cert is claimed

module 5 — back end development & apis

the spine
fCC Back End Development & APIs Certification

a real API-backed project — routes, data, error handling

Flask stays the python-side option once python's in hand

*opens once module 4's cert is claimed

module 6 — data visualization · the last cert on the spine

the spine
fCC Data Visualization Certification — D3, data-driven DOM

a real data-viz project pulling from an API, live on guerz.lol

earning this one = FULL STACK DEVELOPER STATUS

*opens once module 5's cert is claimed // {goal line: june 9, 202?}

modules stay intentionally open — direction, not gospel. firms up at monthly reassessments. the cs/algorithms/data-structures lane is reserved (python-flavored) but doesn't start until 1–2 real python/ai projects exist. grind justified by use, not syllabus guilt. (+ any later certs deliberately added only at a real boundary, never for elegance.)

side quest — wordpress proficiency

foundations
PUBLISHING — block editor fluency, theme basics, skeleton posts in my style.

- 1–2 real posts a week at least

structure
INTEGRATION — pages vs posts, categories/tags, menus, site editor

- cross-post pipeline to BlueSky, Mastodon, FaceBook Pages, Threads, X

workflows
BLOGGUERZ — Obsidian → WordPress → social pipeline

- income-gated migration to a self-hosted blog.

minimum heartbeat: one wordpress interaction per week. never allowed to hijack the main spine.

rules · read these when overwhelmed

  1. one main thing at a time
  2. ship something visible, even if tiny
  3. reference sites are support, not a third curriculum
  4. build first, read second, watch third
  5. ugly but working > perfect but stuck
  6. playbook tracks reality — update it when things move
  7. the timeline flexes; the direction doesn't
  8. the certs are the ruler now — six fCC certs, free; front-end by 6.9.27, full stack when it's earned
  9. no re-sequencing the modules without Coach Bonabelle sign-off

definition of done (per module milestone)

— the concrete output exists and is visible, deployed or local.
— web-dev-playbook.html reflects what actually happened.
— at least one obsidian nightly report exists for the stretch.
— you can explain what you built in plain english.