Workshop

A focused workshop for a single engineering team. The format is half lecture, half pair-coding on a code base we agree on in advance — yours, a small sample, or the ProxyBuilder examples.

Who it is for

• Java engineering teams that ship cross-cutting concerns (logging, metrics, security, audit, multi-tenancy) and want to understand the trade-offs between runtime reflection and compile-time generation.
• Teams considering a move from a heavy AOP framework toward generated code for GraalVM, JPMS or startup-time reasons.
• Teams that need a working mental model of javax.annotation.processing before they start writing their own processor.

Sample two-day agenda

Day 1 — Runtime side

• 09:00 · The proxy problem in Java. Why interfaces, why dynamic.
• 10:30 · DynamicProxyBuilder: pre/post actions, security rules, metrics, virtual proxies.
• 13:30 · Pair exercise — wrap an existing interface in your codebase.
• 15:30 · Composing builder features. Where reflection costs you.
• 17:00 · Wrap-up and questions.

Day 2 — Compile-time side

• 09:00 · The annotation processing round. What javac actually does.
• 10:30 · The built-in @Static* annotations, generated source walk-through.
• 13:30 · Pair exercise — implement a custom @Audit annotation and processor.
• 15:30 · Method-decorator slots, processor options, JPMS implications.
• 17:00 · Migration patterns, retrospective, next steps.

What you get

• Day-by-day worked examples checked into a private fork or branch.
• A short report after the workshop: what you tried, what worked, what is ready to ship.
• Two follow-up office-hour calls of 45 minutes each, scheduled within six weeks.

Logistics

• Format: Remote over video, on-site at your office, or hybrid.
• Team size: Up to 12 participants. Above that, split or invest in a second day.
• Pricing: From €2,500 per day, team rate. Travel billed separately for on-site.
• Language: English or German.
• Lead time: Typically two to four weeks.