1. Spring and Java

>> On Default Values for Primitive-Like Classes [openjdk.org]

One of the thorniest problems standing between us and value classes: what happens when a value object never gets explicitly initialized? A deep exploration of how primitive-like classes might nominate their own default values, and what that means across the language, the JVM, and the runtime. Good stuff for the weekend.

>> The VibeSec Reckoning [martinfowler.com]

As AI-assisted coding moves into the mainstream, prompting an LLM toward “secure” output isn’t, of course, enough. Security has to be structural and enforced mechanically in the harness.

Also worth reading:

Webinars and presentations:

Time to upgrade:

2. Pick of the Week

>> How to break a Monolith into Microservices [martinfowler.com]

Next »
Java Weekly, Issue 649
« Previous
Java Weekly, Issue 647