---
title: "The Java platform engineer roadmap"
chapter: "00"
---

# The Java platform engineer roadmap

Java is a language, a standard library, a virtual machine, a toolchain, and a
large ecosystem. A strong Java engineer understands how source code becomes a
reliable running system.

## Explain it like I am five

You write instructions in Java. The compiler turns them into **bytecode**, a
portable instruction format. A **JVM** reads that bytecode and runs it on the
actual computer. The same well-built application can run on many operating
systems because each system has a suitable JVM.

## JDK, JVM, and runtime

| Term | Plain meaning |
|---|---|
| JDK | Development kit: compiler, runtime, debugger, profiler, packaging tools |
| JVM | Virtual machine that loads, verifies, optimizes, and executes bytecode |
| Java SE | Standard language, JVM, and core API specification |
| OpenJDK | Open-source implementation project for Java |
| JAR | Archive containing classes, resources, and metadata |

## Current version strategy

Oracle's support roadmap lists Java 25 as an LTS release. Java 26 is a
short-lived non-LTS feature release. Use a supported LTS baseline for most
long-lived production systems unless the organization deliberately follows
every six-month release.

This fieldbook teaches Java 25 LTS while keeping certification-focused examples
compatible with Java 21 where practical. Preview features are labeled; do not
silently depend on previews in production.

## The learning loop

1. Read a small concept.
2. Predict what code does before running it.
3. Compile with warnings enabled.
4. Write a focused test.
5. Inspect bytecode, threads, memory, or I/O when behavior is unclear.
6. Explain the result in simple language.

## Evidence a strong engineer produces

- Small cohesive types with explicit invariants.
- Tests for success, boundaries, concurrency, and failure.
- Reproducible builds and pinned toolchains.
- Profiles from JFR or an equivalent tool before performance changes.
- Clear ownership of threads, files, sockets, and executors.
- Upgrade, security-patch, dependency, and rollback plans.

## Feynman check

Can you explain the path `Source.java → javac → Source.class → class loader →
bytecode verifier → interpreter/JIT → machine code`? That path is the backbone
of this fieldbook.