ENGINEERED BOOTCAMP / ENVIRONMENT

Choose an environment that fits your constraints.

You are choosing a workable starting point, not a permanent identity. Keep the computer and supported operating system you already have when they pass the checks below; change only for a named constraint.

Sources reviewed Aug 27, 2026 · recheck before useNo universal winner

DECISION RULE

Keep the outcomes fixed and the environment flexible.

You must be able to run the required Java, Python, Git, test, and CI workflows and later meet a container or Kubernetes path. You may use Windows, WSL, macOS, Linux, or a suitable remote Linux workspace. Your editor, shell, and cloud provider remain your choices unless an assessment names a compatibility target.

PYTHON BASELINE

Use Python 3.14 for this pilot. Python currently lists 3.14 in bugfix status, with regular binary releases, while 3.12 is in its security-only, source-release phase. This keeps the Windows, macOS, Linux, and remote routes current without making you compile CPython during setup. Check Python version status ↗

GROUNDED COMPARISON

Match facts to your situation.

Read every option that survives your constraints. Treat each “good fit” statement as a decision aid, then verify the linked product facts for your exact version and architecture.

WINDOWS NATIVE

Windows native

CHOOSE IT WHEN

Choose this when Windows is already supported on your computer, you need Windows-first applications, or you cannot enable a virtualized Linux environment.

FACTS TO USE

You can use an official Java distribution directly on Windows, so WSL is not required for the first Java modules. Java setup ↗
You can also install and manage an official Python runtime directly on supported Windows versions. Python on Windows ↗
You can run GitHub Actions jobs on hosted Windows runners when you need to check Windows-specific behavior. GitHub runner reference ↗

WATCH FOR

Translate POSIX examples instead of pasting them unchanged: use the Windows Maven Wrapper script and Windows path syntax. Check Docker Desktop requirements before the container module because its Linux-container path depends on a supported virtualization backend.

VERIFY BEFORE YOU COMMIT

Confirm your Windows version, CPU architecture, install permissions, and whether virtualization is available. Choose PowerShell or Command Prompt and use that choice consistently in your notes.

Open the Windows native path →

WINDOWS / LINUX

Windows + WSL 2

CHOOSE IT WHEN

Choose this when you want to keep Windows applications while doing course work in a Linux shell and Linux file system.

FACTS TO USE

You get a Microsoft-managed virtual machine with a full Linux kernel and full system-call compatibility; WSL 2 is the current default WSL architecture. Microsoft WSL comparison ↗
You get better file performance when Linux command-line projects stay in the WSL file system instead of a mounted Windows drive. Microsoft file-system guidance ↗

WATCH FOR

Do not split one project casually across Windows and Linux toolchains. Keep a WSL project under a path such as /home/your-name/project, and check memory, virtualization, and organizational restrictions before committing to this route.

VERIFY BEFORE YOU COMMIT

Confirm that WSL 2 is supported and updated, that you may enable virtualization, and that your editor can open the Linux-side project without moving it to C:\.

Open the Windows + WSL 2 path →

MAC

macOS

CHOOSE IT WHEN

Choose this when you already have a supported Mac and want to keep your host setup, shell, and desktop applications in one environment.

FACTS TO USE

You can obtain Java builds for both macOS x64 and macOS AArch64. Cross-platform JDK setup ↗
You can follow Python's dedicated macOS installation and package-management path. Python on macOS ↗
You must still match container images to CPU architecture: linux/amd64 and linux/arm64 are different targets unless you use emulation or a multi-platform image. Docker multi-platform builds ↗

WATCH FOR

Identify whether your Mac is Intel or Apple silicon before downloading tools. During the container module, check that every required image supports your architecture and read the current Docker Desktop terms.

VERIFY BEFORE YOU COMMIT

Open About This Mac and record the macOS version and chip, or run uname -m. Confirm that the exact Java, Python, and later Docker releases support both values.

Open the macOS path →

LINUX HOST

Linux

CHOOSE IT WHEN

Choose this when Linux is already your supported host and you are comfortable managing packages, permissions, services, and device support yourself.

FACTS TO USE

You can install Docker Engine directly with platform-specific instructions for Docker-supported Linux distributions and architectures. Docker Engine platforms ↗
You can run the bootcamp's local Kubernetes path on Linux, macOS, or Windows when the host meets minikube's CPU, memory, disk, network, and driver requirements. minikube requirements ↗

WATCH FOR

A distribution derived from a supported distribution is not automatically vendor-tested. Confirm your exact distribution and version, and do not weaken host security or grant broad Docker access merely to bypass a permissions error.

VERIFY BEFORE YOU COMMIT

Record the distribution, release, CPU architecture, available memory and disk, and whether you have approved sudo access. Match each later install guide to that exact distribution.

Open the Linux path →

BROWSER / REMOTE

GitHub Codespaces

CHOOSE IT WHEN

Choose this when your local computer is locked down, short on resources, or shared across locations and reliable internet access is an acceptable dependency.

FACTS TO USE

You can open a cloud-hosted Linux development container from a browser or supported editor regardless of your local operating system. Codespaces overview ↗
You receive a metered allowance on eligible personal plans; after the allowance, usage is blocked or billed according to your payment method and budget settings. GitHub included usage ↗

WATCH FOR

Treat internet access, account access, storage retention, port forwarding, and usage limits as hard constraints. A codespace is a Linux environment; it does not reproduce Windows- or macOS-specific behavior.

VERIFY BEFORE YOU COMMIT

Check your current included usage and set a stop-usage budget before starting. Open, stop, restart, and reconnect to one disposable codespace before storing course work there.

Open the GitHub Codespaces path →

STEP-BY-STEP DECISION

Decide before you install.

STEP 01
Write constraints
List your current computer, required workplace software, accessibility needs, install permissions, reliable-internet access, budget, and any need to work offline.
STEP 02
Inventory the host
Record the operating-system version, CPU architecture, memory, free disk, virtualization support, and whether you may use administrator or sudo privileges.
STEP 03
Eliminate poor fits
Remove any option that fails a non-negotiable constraint. Do not keep an option because somebody calls it the professional choice.
STEP 04
Read current support
Open the official Java, Python, Docker, and minikube pages for your exact OS and architecture. Record the page and the date you checked it.
STEP 05
Choose one boundary
Select one primary shell and one project file system. If you choose WSL, keep Linux-tool projects in WSL; otherwise keep each project in your host file system.
STEP 06
Name a fallback
Choose a second viable route now—for example, Windows native if WSL is blocked, or Codespaces if the local host cannot meet a later container requirement.
STEP 07
Record the decision
Write your choice, rejected alternatives, source-backed reasons, risks, fallback, and the condition that would make you reconsider.
STEP 08
Prove the fit
In Week 0, install the required tools yourself from official instructions, reopen the shell, run the checks below, and keep the observed output.

COMMAND TRANSLATION

Verify the same outcome in your shell.

Run commands yourself and keep the exact output. Select the Python launcher that resolves to your required interpreter, then use it consistently inside the project virtual environment.

OUTCOME

macOS / LINUX / WSL

WINDOWS POWERSHELL / CMD

Java runtime

java --version

Java compiler

javac --version

Python runtime

python3 --version or python --version

python --version or py --version

Git

git --version

Maven Wrapper test

./mvnw test

.\mvnw.cmd test

pytest in your active virtual environment

python -m pytest

python -m pytest or py -m pytest

KEEP YOUR CHOICE

Continue when every hard check passes.

□ You can run the required Java, Python, Git, and test commands.
□ Your workspace survives a new shell and a computer restart.
□ Your repository contains no personal absolute paths or secrets.
□ You have a feasible local or remote path for Docker and minikube later.
□ Your budget, access, and offline needs fit the route you selected.

CHANGE YOUR CHOICE

Switch only when a hard check fails.

Try one bounded troubleshooting pass using the exact error and the official guide. Move to your recorded fallback when your OS or architecture is unsupported, required privileges are unavailable, local resources cannot meet the later container path, or remote cost and connectivity violate your constraints. Record the failed check; do not restart from preference alone.

Download decision worksheet Continue to Week 0 →

Keep the outcomes fixed and the environment flexible.

PYTHON BASELINE

Continue when every hard check passes.

□ You can run the required Java, Python, Git, and test commands.

□ Your workspace survives a new shell and a computer restart.

□ Your repository contains no personal absolute paths or secrets.

□ You have a feasible local or remote path for Docker and minikube later.

□ Your budget, access, and offline needs fit the route you selected.

Switch only when a hard check fails.

Keep the outcomes fixed and the environment flexible.

Match facts to your situation.

Windows native

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

Windows + WSL 2

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

macOS

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

Linux

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

GitHub Codespaces

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

Decide before you install.

Write constraints

Inventory the host

Eliminate poor fits

Read current support

Choose one boundary

Name a fallback

Record the decision

Prove the fit

Verify the same outcome in your shell.

Continue when every hard check passes.

Switch only when a hard check fails.

Keep the outcomes fixed and the environment flexible.

Match facts to your situation.

Windows native

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

Windows + WSL 2

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

macOS

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

Linux

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

GitHub Codespaces

CHOOSE IT WHEN

FACTS TO USE

WATCH FOR

VERIFY BEFORE YOU COMMIT

Decide before you install.

Write constraints

Inventory the host

Eliminate poor fits

Read current support

Choose one boundary

Name a fallback

Record the decision

Prove the fit

Verify the same outcome in your shell.

Continue when every hard check passes.

Switch only when a hard check fails.