ENGINEERED BOOTCAMP / RESOURCES

Use proven tools. Build the skill yourself.

Follow official documentation and established free platforms. The bootcamp gives you a route, starter inputs, and evidence templates; it does not replace the tools you are learning or automate your work.

STARTER DOWNLOADS

Take the route into your own workspace.

Environment decision worksheet

Compare constraints, official support, risks, and a fallback before you install learner tools.

Download .md →

Cohort calendar

Import the fixed 2026–2027 pilot schedule into a calendar application.

Download .ics →

Diagnostic instructions

Use the complete 75-minute Python-to-Java diagnostic route.

Download .md →

Python reference input

Read this supplied behavior, then reproduce it in Java during the diagnostic.

Download .py →

Supplied pytest cases

Run these tests unchanged before writing your Java equivalent and JUnit cases.

Download .py →

FREE LEARNING SOURCES

Learn from the maintainers and established communities.

Open each selected unit from its route sheet. Confirm that access is still free before beginning, and never copy a platform solution into your course or portfolio repositories.

Java and testing

Python

Back end and data

Front end

SDLC, Agile, and delivery

Containers, Kubernetes, and cloud

DAY-0 DIAGNOSTIC

Translate tested Python behavior into Java.

Use Python as a known language and Java as the new language. The reference implementation and tests are supplied inputs—not an answer to the Java task.

01Close assistants and generated-code tools for one uninterrupted 75-minute block.
02Predict the pytest cases, run them, and trace one success path plus one exception path.
03Reproduce all three observable behaviors in Java 17, using explicit loops for the score summary.
04Write JUnit cases for every supplied example plus one additional boundary per function.
05Record one type contrast, one error-handling contrast, and a two-minute explain-back. Stop when the clock ends.

SDLC + AGILE TEMPLATES

Keep evidence lightweight and traceable.

Adapt these Markdown templates inside your own repositories. You fill them from your observations and decisions; an assistant does not author your evidence for you.

Definition of Done

.md

Set the quality bar that every Increment must meet.

Download template →

User story

.md

Turn a user need into a small slice with testable criteria.

Download template →

Defect report

.md

Record reproducible behavior, impact, and acceptance for a fix.

Download template →

Pull request

.md

Connect the change to its story, tests, CI, risks, and evidence.

Download template →

Architecture decision

.md

Capture context, options, choice, tradeoffs, and consequences.

Download template →

Retrospective

.md

Turn evidence from a Sprint into one concrete improvement.

Download template →

PORTABLE ENVIRONMENT

Choose where you work.

Use Windows, macOS, Linux, a dev container, a codespace, or a suitable remote workspace. Meet the required versions and standard project commands without committing personal absolute paths or making one editor, machine, or cloud provider mandatory.

Compare the grounded tradeoffs →

CLOUD SAFETY

Set the budget to $0.

Verify the current free offer before creating a resource, use alerts and tags where available, keep databases private, inventory everything you create, and stop or delete billable resources after capturing evidence. Use local staging when no hosted path is both safe and free.

Start Week 0 →Return to the roadmap