ABCsteps module path
Lessons 01-05 · Beginner
Module A: Engineering Foundations
Start from absolute zero. Learn how code, editors, AI assistance, terminal commands, and GitHub fit together as one working practice.Treat this module as a five-step proof path: open the first lesson, build each artifact, and keep evidence reviewable.
- Module path
- 5 lessons
- Milestone
- A
- Proof mode
- Public
Operating ecosystem
Real tools, real company surfaces, truthful boundaries.
This module teaches skill patterns used across product, cloud, and AI teams. Logos are ecosystem references only: no affiliation, interview access, hiring promise, salary promise, or placement guarantee.
Module proof ladder
Five lessons become five inspectable artifacts.
Each module is designed as a visible chain: learn the skill word, build the lab, write the proof line, and keep the result reviewable. Company and platform logos are context for the ecosystem, not a hiring shortcut.
Module signal
By the end of Module A, a learner should be able to explain the module project, name the tools used, and point to evidence another engineer can inspect.
Ecosystem references only: no affiliation, endorsement, interview access, hiring preference, salary outcome, or placement guarantee.
Lesson 01 · AI pair
AI-Assisted Code: Your First App
Skill signal: AI-assisted coding
Proof artifact: Build and inspect a simple browser game.
Show the prompt, the generated change, the bug you found, and the final working browser demo.
Lesson 02 · Editor
Set Up VS Code Like a Developer
Skill signal: Editor workflow
Proof artifact: Set up VS Code and modify a real interface.
Show a before-and-after diff, explain which file changed, and describe why the change was safe.
Lesson 03 · 3D rendering
Build Your First 3D Scene
Skill signal: 3D scene model
Proof artifact: Create a small Three.js scene and adjust it safely.
Show the scene, camera, light, and interaction change separately so another engineer can inspect the rendering path.
Lesson 04 · CLI habit
How Developers Actually Work: The Terminal
Skill signal: Command line basics
Proof artifact: Use shell commands to inspect and run a local project.
Show the command you ran, the output you read, and the fix you made after interpreting the terminal result.
Lesson 05 · Repository
Your Developer Passport: GitHub
Skill signal: GitHub portfolio
Proof artifact: Create a repository and publish the first project.
Show a clean repo with meaningful commits, a short README, and a working project path.
After this module
Finish the five-lesson proof before choosing support.
A module page should not push a learner into support early. The right sequence is public reading, visible artifacts, then support only when live accountability, doubt review, or project feedback would change the work.
Public
Read the module in order
Start at lesson 01. Do not skip ahead until the first lab artifact is visible.
Open lesson 01Proof
Keep the milestone reviewable
The module is complete when Publish a small working app and its GitHub repository. can be explained, run, and reviewed.
Open lesson 05
Recorded
Recorded support
Use recorded walkthroughs, study pack, WhatsApp Q&A, and final review when self-reading needs a guided layer.
Open recorded support
Live
Live Cohort
Use cohort only when scheduled online classes, peer pressure, and live Q&A would change consistency.
Open CohortPrivate
1:1 Mentorship
Use mentorship only when a real project, career move, or technical decision needs private founder review.
Open MentorshipProfessional
Architecture Review
Use architecture review for a specific codebase, stack, vendor, or deployment decision; it is not beginner lesson support.
Open Architecture ReviewInstitution
Workshop
Use workshops when a college, school, bootcamp, or team needs a shared AI engineering class.
Open WorkshopsAI-Assisted Code: Your First App
Use an AI coding assistant to build a small game while learning what the tool is doing, where it helps, and where human judgment still matters.
Lab: Build and inspect a simple browser game.
Team surfaces
Show the prompt, the generated change, the bug you found, and the final working browser demo.
Set Up VS Code Like a Developer
Set up a professional editor, understand project files, and use AI assistance to modify an existing app deliberately.
Lab: Set up VS Code and modify a real interface.
Team surfaces
Show a before-and-after diff, explain which file changed, and describe why the change was safe.
Build Your First 3D Scene
Use Three.js concepts to understand scenes, cameras, lighting, and how AI can help scaffold visual experiments.
Lab: Create a small Three.js scene and adjust it safely.
Team surfaces
Show the scene, camera, light, and interaction change separately so another engineer can inspect the rendering path.
How Developers Actually Work: The Terminal
The terminal is a precise control surface. Learn the commands developers use to inspect projects and run tools.
Lab: Use shell commands to inspect and run a local project.
Team surfaces
Show the command you ran, the output you read, and the fix you made after interpreting the terminal result.
Your Developer Passport: GitHub
Publish a project on GitHub, understand commits, and begin building a portfolio that shows actual work.
Lab: Create a repository and publish the first project.
Team surfaces
Show a clean repo with meaningful commits, a short README, and a working project path.