New Year Wishes for Minimalist Java 25 Developers by Agent zSmith 📎
May your 2026 be as clean as your pom.xml:
🎊Wishing you a year where:
Your main() method stays simple and your classpath stays empty.
You forgot the import statements.
You never have to explain why you don't need Spring for a REST endpoint.
Your JAR files remain measured in kilobytes, not megabytes.
May your code compile faster than others can download their node_modules.
🥂 Here's to a year of:
jshell experiments
that actually make it to production
Records
that replace your boilerplate
Pattern matching
that makes your switch statements beautiful
Virtual threads
that make your concurrent code readable
String templates
that end your StringBuilder nightmares
May your dependencies be few, your JDK be current, and your NullPointerExceptions be... well, actually helpful now!
"🎆 In 2026, may you write code so clean that even the JVM garbage collector gets bored."
Happy New Year! May your builds be fast, your tests be green, and your stack traces be short!
The wishes were generated by zSmith, a Java 25 zero-dependency agent:
import airhacks.zsmith.agent.boundary.Agent;
void main() {
var newYearAgent = new Agent(
"""
As a marketing specialist,
you focus on humorous wording
for specific occasions,
such as New Year's.
"""
).withTemperature(0.1f);
var response = newYearAgent.chat("""
Write New Year wishes for
all the Java developers out
there who write simple Java 25 code
without any external dependencies.
""");
IO.println(response);
}
"React over Angular? ...and WebStandards, JSR-375 and REST, Reactive Programming vs. CompletableFuture, Blocking @Asynchronous calls, Interceptors with EntityManager, AMQP and data masses, To Framework Or Not To Framework, Unit Testing Primefaces, Multi-Threaded JAX-RS 2.0 Clients, Java EE "vs." .NET, Dynamic entities, Data encryption, Working offline with JPA, Sample Projects, Industry trends, Conferences and Co., Server Side Rendering with Java EE 7, Naming CRUD in BCE, Java 9 Logging interface, Generic REST client, React.js / Polymer examples, Session replication challenges""
adambien.blog/roller/abien/entry/react_over_angular_reactive_programming
Ask questions during the show via twitter mentioning me: https://twitter.com/AdamBien (@AdamBien),using the hashtag: #airhacks or built-in chat at: airhacks.tv. You can join the Q&A session live each first Monday of month, 8 P.M at airhacks.tv
From Energy Sector to Cape Dwarf--airhacks.fm podcast 📎
constructions.cloud provides a curated collection of Java-based AWS deployment examples using CDK infrastructure-as-code. The repository contains production-ready patterns for building serverless applications on AWS.
The collection includes repositories covering common AWS patterns:
Foundation & Setup
CDK development environment configuration and foundational templates
Serverless Compute
Lambda implementations from minimal POJO examples to Quarkus-powered HTTP APIs
AI Integration
Bedrock Agent Core implementations including runtime agents and MCP gateway patterns
Storage & CDN
S3 integration examples and CI/CD pipelines with CloudFront distribution
Each repository follows the bce.design architecture with minimal dependencies.
The Quarkus examples replace traditional microservices with serverless HTTP APIs. The POJO examples handle AWS events (S3, SQS, EventBridge) without framework overhead.
Live From Oredev 2025: Real World (Enterprise) Java: Zero Bloat, Max Productivity 📎
Escape outdated JDK 1.X practices from the 90s with practical, modern Java development.
This session provides concrete Java 21+ techniques that eliminate bloat, increase productivity, and streamline
your business logic.
Structuring efficient monoliths and microservices
Streamlined testing approaches
Logging and error handling
Implement data-oriented programming
Remoting and caching
Persistence strategies
Documentation and Javadoc
Build and CI
Replace external dependencies with built-in functionality
Adapting code structure for LLM-driven development
"JASPIC for securing Java EE 7 applications, Thoughts on lambdas and more functional Java, Thoughts on AWS lambdas, The size of ReactJs -- and possible optimisations, Thoughts on custom servlet login module, How to handle transactions in Thin WARs, Primefaces as "one stop" solution, REST as communication "protocol" between Thin WARs, WebSockets vs. Long Polling, JSONObject as DTO and inheritance issues, Microservices and Jenkins, Opinions on Docker Swarm, Threads and EJBs, Is MVC dying (everywhere), Programmatically deploy and undeploy Java EE applications" adambien.blog/roller/abien/entry/ear_use_cases_jsf_modularization
Ask questions during the show via twitter mentioning me: https://twitter.com/AdamBien (@AdamBien),using the hashtag: #airhacks or built-in chat at:
airhacks.tv. You can join the Q&A session live each first Monday of month, 8 P.M
at airhacks.tv
Silesia JUG: "10x Speed, 1x Complexity: Live Coding Java with LLMs" Afterglow 📎
During the 2.5-hour Silesia JUG session "10x Speed, 1x Complexity: Live Coding Java with LLMs", I was asked many good, critical and insightful questions about Java, productivity, maintainability LLMs, agents and best practices.
Quarkus Essentials MicroProfile Template with BCE 📎
A new Quarkus template is now available that provides an essential foundation for building MicroProfile applications using the Boundary-Control-Entity (BCE) architecture pattern. Available at github.com/AdamBien/quarkus-microprofile.
Key Features
BCE Architecture: The code is structured into distinct layers - boundaries (REST endpoints), control logic, and entities. This promotes maintainability while keeping the codebase minimalistic.
MicroProfile-Only: The template includes only JAX-RS for REST endpoints and CDI for dependency injection. No external dependencies.
Modular Structure:
service: Core Quarkus application with BCE structure
service-st: Separate system tests module
Technical Foundation
Built on Quarkus for fast startup and low memory footprint. The BCE pattern is the simplest way to organise your code, scaling to complex enterprise applications.
Introducing BCE.design: A straightforward, business-domain-first architecture. 📎
Arguably the oldest architecture pattern, BCE/ECB is described in countless articles and books,
and is supported by most (all) design (drawing? 😊) tools.
Boundary Control Entity (BCE/ECB) is built on a simple structure that focuses on the business domain. A component is a (Java) package or module (e.g. ESM in Web Components) that focuses on a real business concept.
Each component comprises a maximum of the following layers:
This session showcases the next set of top-rated and unique Java code snippets—demonstrating tasks like running Java apps without compilation, handling emojis, launching dev servers, and more—using only plain Java, javac, and VS Code, with no builds or external dependencies.
Beautiful LLM Code, Serverless, BCE, Asynchronous--Questions and Topics for the 139th airhacks.tv 📎
"Follow up JSF modularization, Beautiful Java EE frontends, JWT Authentication With Java EE, Java EE CRUD
Code Generators / bootstrap Frameworks, Are there still use cases for EARs?, Serialising a dynamic subset of
fields / properties, JPA with WildFly, Testing @asynchronous methods, Fat WARs -- if you really need them,
Use Cases and experiences with Java EE Batch, Multitenancy with JPA, Opinions about Multiple WARs, one
server, one DB"
adambien.blog/roller/abien/entry/ear_use_cases_jsf_modularization
Ask questions during the show via twitter mentioning me: https://twitter.com/AdamBien (@AdamBien),using the hashtag: #airhacks or built-in chat at:
airhacks.tv. You can join the Q&A session live each first Monday of month, 8 P.M
at airhacks.tv
Dynamic Container Images with Quarkus--airhacks.fm podcast 📎