Adam Bien, a veteran Java consultant, shares his philosophy of using zero external dependencies and sticking to Java standards (Jakarta EE, MicroProfile) to build systems that outlast trendy frameworks. He explains why Quarkus is his current runtime of choice — fast boot times, low cloud costs, and seamless migration from old Java EE projects. A key insight is that the Boundary-Control-Entity (BCE) pattern, dating to 1992, pairs exceptionally well with LLMs: because BCE and Java specs are well-documented and publicly available, LLMs can generate production-ready Java code with minimal context and near-zero hallucinations. He also discusses moving from a monolithic rules file to lean, task-specific skills for AI-assisted coding, using OpenTelemetry for observability, and running LLM inference locally with TornadoVM and Java 25 zero-dependency scripts.
Table of contents
TranscriptZero-Dependency Java: Why Boring Standards Outlive Trendy Frameworks [ 02:23 ]Porting Old Java EE to Quarkus Was Painless [ 04:05 ]Boundary-Control-Entity: A 1990s Pattern Retrofitted for the LLM Era [ 08:19 ]A Clean BCE Structure Helps LLMs Generate Production-Ready Java Code [ 11:18 ]From One Giant Cloud.md to Multiple Focused Skills [ 18:08 ]Reducing LLM Inference Costs by 80% with BCE and Standard APIs [ 21:04 ]Rethinking Metrics, Logs, and Dashboards for AI Native [ 26:56 ]Improve the Sovereignty of Your Applications by Designing Them Cloud-Agnostic [ 30:17 ]Run Things Locally Where Possible [ 33:36 ]About the AuthorSort: