Java Full Stack
Lab Curriculum.

BUG FOUND: Java graduates who know syntax but cannot fix a Spring Boot service in production.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. Java OOP, collections, and exception handling applied to real service code.
2. Spring Boot controllers, services, and repositories; dependency injection.
3. JPA entities, relationships, and transaction basics.
4. REST API design: request/response, validation, and error codes.
5. Maven/Gradle builds, Git, and reading application logs.
6. Frontend basics for a full-stack app: forms, API calls, and rendering lists.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: IntelliJ/Eclipse, Spring logs, Postman, JUnit, database console.

• BUG #1: Service crashes on startup — find the misconfigured bean / property, fix it, prove a clean boot.
• BUG #2: JPA transaction rollback bug loses an order — reproduce, fix transaction boundaries, add a test.
• BUG #3: API timeout under a large payload — find the slow query / loop, fix it, show before/after timing.
• BUG #4: Null handling breaks a payment flow — find the null path, add validation and a safe fallback, test edge cases.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Trace a request through controllers, services, and database in a monolith; draw the call flow.
• Refactor a duplicated service method safely, with tests covering both old callers.
• Add a new endpoint (validation, service logic, persistence, tests) in unfamiliar code, reviewed by a mentor.
• Debug a failing integration test: decide whether the fault is in app code, test data, or configuration.

$ step-04 ship // weeks 8–9 — Shipping Features: capstone — deploy a Java full-stack application with API documentation, a demo, and a test report.

$ ship → PROOF — exact output: deployed Java application URL, API documentation, source repo with tests, and a test report showing pass/fail before and after fixes.

$ run --lab java-full-stack → ✓ SHIPPED, job-ready