A Java Geek weekly 93

Writing for Developers

I started this blog as a hobby seventeen years ago, in April 2008. At the time, I had no clue about technical writing. I’m pretty sure it was not even a thing back then: the only content aimed at developers was technical documentation. Since then, the landscape has changed a lot, to the point that companies hire for technical writer positions.

I was curious to compare what I learned by doing to the structured approach of a book. I ordered the book last year when it was still being written. It was published only early this year, and I was already reading (and reviewing!) DuckDB in action. I put it on the top of my reading pile list; I finally finished it: here’s my review.

We’ve Issued Our First IP Address Certificate

TIL that you can generate certificates for IP addresses. It would make a lot of sense if you could issue certificate across domains & IP addresses.

Most RESTful APIs aren’t really RESTful

So what? It’s weird that some consider REST some kind of boon that will solve all problems? If a true REST API rely on runtime discovery, how would client deal with such a system? Without external stable documentation, there can be no benefit. I’d love to be proven wrong: counter-examples are welcome.

Security researcher exploits GitHub gotcha, gets admin access to all Istio repositories and more

Pre-commit hooks for the win! Or perhaps an enterprise-wide proxy could do the job before it would reach the outside?

State of Vite and Vue 2025
European Cloud Modules

Europe shouldn’t depend on other countries, but a "sovereign" cloud is a far away goal. The post gives some ideas to help progress.

Introducing OpenCLI

I hope this initiative gains traction. We need more standards to make integrations easier.

How to Prepare a Strong Tech Resume: Tips and Step-By-Step Guide from a Recruiter

I wish I had these guidelines a couple of months ago.

CTOs Reveal How AI Changed Software Developer Hiring in 2025

The main benefit of AI might be that finally interviews will focus on the thinking process instead of the balancing of a red-black tree.

How Quarkus works with OpenTelemetry on OpenShift

I’ve invested a lot of time in OpenTelemetry, but I must admit that my knowledge of OpenTelemetry and Quarkus integration is lacking.

Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity

When developers are allowed to use AI tools, they take 19% longer to complete issues—a significant slowdown that goes against developer beliefs and expert forecasts. This gap between perception and reality is striking: developers expected AI to speed them up by 24%, and even after experiencing the slowdown, they still believed AI had sped them up by 20%.

Who could have imagined?

Bootify

TIL:

Best developer experience for starting #SpringBoot apps ‐ best practices included.

OpenTelemetry Injector Debian/RPM package

The OpenTelemetry Injector Debian/RPM package (opentelemetry-injector) installs OpenTelemetry Auto Instrumentation agents, the libotelinject.so shared object library, and default/sample configuration files to automatically instrument applications and services to capture and report distributed traces and metrics to the OpenTelemetry Collector.

The idea is amazing, but the documentation doesn’t mention where the package is published, and I couldn’t find it by myself. The project doesn’t show any release either.

Nicolas Fränkel

Nicolas Fränkel

Nicolas Fränkel is a technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.

Read More
A Java Geek weekly 93
Share this