Java 21 Language Core Intensive
Syntax refresh, records, pattern matching, and virtual threads with weekly mentor reviews on your exercises.
JPY 98,000
ViewMixed metrics—some from satisfaction surveys, some from delivery logs—so you can see how the studio operates week to week.
Transparent scope: repositories, rubrics, and office hours—without promising outcomes we cannot measure.
Every sprint ends with something linkable: PRs, ADR drafts, or profiling notes you can attach to a portfolio.
Feedback targets your diff, not generic slides—timed so it lands before the next assignment opens.
Sequences spell prerequisites, expected hours, and what we deliberately skip so you can plan around gaps.
1,180
Pull requests reviewed across Surge Fluxon cohorts since 2019—each tied to a rubric, not anonymous clicks.
Build Java services with structured feedback, cohort accountability, and self-paced options when midnight coding fits better than live labs.
Horizontal rhythm instead of numbered circles; each beat has a deliverable.
Tooling, repo access, and honesty about prerequisites.
Small features with rubrics referencing hiring panels.
Mentor passes land before the next slice unlocks.
Narrate trade-offs for interviews and internal RFCs.
A rotating slice of the catalog—filters on the full listing page go deeper.
Syntax refresh, records, pattern matching, and virtual threads with weekly mentor reviews on your exercises.
JPY 98,000
ViewControllers, validation, OpenAPI, and deployment hygiene for services your team can operate overnight.
JPY 148,000
ViewLayered testing strategy from pure units to consumer-driven contracts without brittle suites.
JPY 72,000
ViewExecutors, structured concurrency, and backpressure patterns for services that behave under load.
JPY 168,000
ViewVaried lengths and formats—experience-first, tied to specific modules on this site.
The Spring Boot APIs for Production module on OpenAPI and Problem Details changed how our squad writes consumer-facing errors—clients finally get consistent JSON shapes.
— Leo Tanaka , Backend engineer · Osaka logistics API team
Concurrency lab’s structured task scope exercise made shutdown behavior visible; I borrowed the worksheet for our on-call primer.
Gradle Enterprise Builds: scan reading—not glamorous, but it funded our cache node.
OCA study studio’s timed mode exposed that I hemorrhaged minutes on generics; the whiteboard clinic fixed that faster than rereading guides. Still wish one mock exam had even hairier wildcard questions.
Bootcamp on-call simulation felt close to our incident retro format—useful stress, not theater. Client in enterprise integration.
Data Access with JDBC and jOOQ clarified when ORM magic hurt us; batch insert benchmark embarrassed an N+1 we defended for too long.