Interpret
Read a short official source, predict the behavior, and trace an example before you run it.
Loading…
ENGINEERED BOOTCAMP
Public pilot · Cohort 01Build fluency by interpreting, producing, using, receiving feedback, and explaining—then carry every feature through Agile planning, the SDLC, CI/CD, cloud delivery, and maintenance.
20
core learning weeks
480
required core hours
2
real contingency weeks
5
evidence-based gates
THE LEARNING METHOD
Use the same kinds of cycles that build spoken-language fluency. Every day ends in authentic use and an explain-back, so passive recognition cannot masquerade as skill.
Read a short official source, predict the behavior, and trace an example before you run it.
Complete a guided example, hide it, and reconstruct the essential behavior without assistance.
Apply the concept to an authentic user story or defect instead of another isolated tutorial exercise.
Use compiler, test, CI, review, and runtime feedback to diagnose what your current model missed.
Explain what changed, why it works, one tradeoff, and one likely failure case in your own words.
SDLC + AGILE
Run a one-person Scrum-inspired cadence with a Product Goal, backlog, Sprint Goal, daily flow, Sprint Review, and Retrospective. Call it Scrum-inspired—not team Scrum—and use the artifacts to make work traceable.
TECH STACK
Learn one coherent full-stack system instead of collecting disconnected tools. Python remains a maintained production language throughout the program—not a footnote or temporary bridge to Java.
PRIMARY LANGUAGE
Build command-line, database, and Spring Boot applications while learning static typing, object design, testing, and refactoring.
SUPPORTING LANGUAGE
Keep Python production-grade through data validation, API smoke tests, automation, and one typed, tested capstone component.
DATA + API
Practice schemas, migrations, transactions, JDBC, REST contracts, validation, authentication, authorization, and integration tests.
FRONT END
Build accessible user journeys with typed components, state, routing, forms, service calls, authentication, and browser-facing tests.
DELIVERY
Author GitHub Actions checks, diagnose failures, build once, promote the same artifact, smoke-test releases, and prove rollback.
CLOUD + OPERATIONS
Map both clouds, use one approved no-cost lab, containerize the application, and operate Kubernetes locally without requiring a paid cluster.
You choose your operating system, editor, workspace, and approved no-cost deployment path. The core application remains portable, AWS and Azure are both taught, and local staging is always a valid fallback. You install and configure your own learner tools from official instructions.
ROADMAP / AUG 2026–JAN 2027
Weeks 0–2 are ready now. Later route sheets remain visibly planned until their resources, load, assessment boundaries, and acceptance criteria pass review.
WEEK 03 / Sep 14–20
Inheritance, polymorphism, interfaces, abstract classes, JUnit TDD, refactoring, and your first architecture decision record.
WEEK 04 / Sep 21–27
Plan, build, test, release, review, and retrospect on the Vendo-Matic Java CLI before completing a fresh task.
Gate 1
WEEK 05 / Sep 28–Oct 4
PostgreSQL, migrations, indexes, transactions, ERD decisions, Python seed-data validation, and a database CI service.
WEEK 06 / Oct 5–11
JDBC, JdbcTemplate, DAO design, Spring Boot REST, validation, unit tests, and real-database integration tests.
WEEK 07 / Oct 12–18
HTTP clients, JWT authentication, authorization, threat modeling, Python API smoke tests, and a Python CI job.
WEEK 08 / Oct 19–25
Release and defend the TEnmo API, respond to review, complete a retrospective, and handle a fresh change.
Gate 2
WEEK 09 / Oct 26–Nov 1
HTML and CSS foundations, JavaScript-to-TypeScript transfer, user journeys, and accessibility criteria.
WEEK 10 / Nov 2–8
React with TypeScript, components, props, state, events, hooks, value-based story slicing, and Node CI.
WEEK 11 / Nov 9–15
Routing, web services, forms, front-end authentication, Vitest, contract checks, and build artifacts.
WEEK 12 / Nov 16–22
Integrate TEnmo Web, run parallel full-stack CI, publish a release, respond to review, and complete a fresh task.
Gate 3
WEEK 13 / Nov 23–29
Use this genuinely unallocated week for remediation, shifted work, or rest. Do not add ordinary required content.
WEEK 14 / Nov 30–Dec 6
Map AWS and Azure, complete one no-cost provider lab, build a Docker image, and operate it on local Kubernetes.
WEEK 15 / Dec 7–13
Promote one versioned artifact through CD, smoke-test it, roll it back, diagnose a failure, and document an incident.
Gate 4
WEEK 16 / Dec 14–20
Define the Product Goal, backlog, architecture, threat model, schema, API skeleton, and Python contract.
Sprint 1
WEEK 17 / Dec 21–27
Use this genuinely unallocated holiday week for remediation, shifted work, or rest.
WEEK 18 / Dec 28–Jan 3
Build the Java back end and a useful typed, tested Python CLI or worker.
Sprint 2
WEEK 19 / Jan 4–10
Build the React front end and integrate it with the Java and Python components.
Sprint 3
WEEK 20 / Jan 11–17
Release a sanitized pilot in an approved no-cost environment and collect approved-user feedback.
Sprint 4
WEEK 21 / Jan 18–24
Ship a feedback-driven change, run an incident exercise, check accessibility and security, and complete a timed set.
Release candidate
WEEK 22 / Jan 25–31
Publish release notes and a recorded demo, trace the full lifecycle, complete the retrospective, and defend your decisions.
Gate 5
MASTERY GATES
GATE 1
Build, test, release, modify, and explain Vendo-Matic with fresh reviewer input.
GATE 2
Release and defend TEnmo with database, security, integration, and Python smoke-test evidence.
GATE 3
Integrate the React client and Java API through parallel CI and a tested release.
GATE 4
Diagnose CI/CD, promote a versioned image, smoke-test it, and roll it back safely.
GATE 5
Trace the full SDLC, respond to a live change, and defend the final product with an external reviewer.
PUBLIC PILOT
This first version is a public curriculum website. It does not save progress, grade work, install tools, provision cloud resources, sell access, or issue certificates. You keep your own evidence in GitHub and complete the pilot before a separate paid program is designed.
Your progress records, review notes, AI logs, sealed assessments, secrets, and personal data remain private. Only sanitized route sheets, starter inputs, templates, and the roadmap are public.