Tooling: IntelliJ, jshell, and the Build Pipeline
You've made it to the end of the bridge. Post 1 gave you the static-type mindset, post 2 the object model and collections, post 3 dependency management — and now the part nobody warns Python developers about: in Java, the toolchain is a bigger part of the job than the language. In Python, the interpreter is the toolchain. You write app.py , run python app.py , and you're done. Packaging, docs, profiling, and the REPL are afterthoughts you bolt on later. In Java, the equivalent surface is a whole pipeline of small, sharp tools that ship with the JDK — plus an IDE culture and a build-pipeline culture that Python simply doesn't have. This post walks the full loop: edit → compile → run → debug, the REPL you didn't know Java had, the CLI toolkit, the IDE everyone actually uses, and the build pipeline that turns source into a shippable artifact. Lab honesty, stated up front. Everything shown as terminal output below is real output from this lab machine (Temurin JDK ...