BellSoft

@bellsoftware

Delivering #LibericaJDK: supported, @Java standard compatible binaries. Among Top-5 @OpenJDK contributors.

San Jose, CA

BellSoft
@bellsoftware
3h
Martin Ladecký’s Spring I/O talk covers secret hygiene for Java and cloud-native systems, including credentials that can survive in Docker layers and build history. Liberica JDK gets a high five for zero CVEs too. Thanks, Martin ✋ Full talk:
BellSoft
@bellsoftware
4h
Pasha Finkelshteyn (@asm0di0) went through a few AI coding setups before finding one he could trust. At JRush Episode 8, he’ll show the approaches he tested, the one he kept, and the changes that made AI-generated code fit into his own development standards. The stream is free.
BellSoft
@bellsoftware
Sep 18
Baruch Sadogursky built a software factory with AI agents that shipped a real MVP in three days. 💥 The setup brought together rival coding agents, shared context, and review gates to see what happens when AI agents work as a team. @jbaruch is Head of Developer Relations at
1
BellSoft
@bellsoftware
Sep 18
Rebase can save you from repeatedly pulling the same gigabytes. A base-image patch doesn't always need a full rebuild. @dchuyko and @cat_edelveis wrote up where Docker and Buildpacks stand on it:
Rebuild vs Rebase Container Images: Docker and Buildpacks
From bell-sw.com
BellSoft
@bellsoftware
Sep 17
Sometimes, you end up being responsible for vulnerable code you didn't even write. A vulnerable JDK. A compromised package. An outdated base image. Third-party components become part of your product the moment they are shipped with it. Under the CRA, if an actively exploited