Please turn JavaScript on
A Java geek icon

A Java geek

Receive updates from A Java geek for free, starting right now.

We can deliver them by email, via your phone or you can read them from a personalised news page on follow.it.

This way you won't miss any new article from A Java geek. Unsubscribe at any time.

Site title: A Java geek

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.16 / day

Message History

My conference participation has dropped sharply since I left DevRel for a regular office engineering job. In 2023, I was proud to have had 70 talks; I’ll finish this year with 4, including one online and one quickie. It has one beneficial side effect, though. Because I go to so few, I take the time to attend. Last Tuesday, I was lucky to attend and talk at the Porto TechHub conf...

Read full story
I love Claude Code, but I use it so much that I regularly exhaust my weekly quota before the week ends. When that happens, I usually switch to other free-tier CLIs, e.g., Google Antigravity, GitHub Copilot, and, just last week, Mistral’s Vibe. I really wanted to try Vibe to evaluate the feasibility of moving away from Claude Code in favor of a more sovereign solution. Vibe only ...

Read full story
I used Dropbox for decades, then switched to Google Drive. Both worked for most of my files. One file never fit, though: my KeePass password database. It’s the file I need on every device and the file I want to keep private the most. After one annoyance too many, I moved it to Syncthing over Tailscale. The rest stays on Google Drive, for now. This post describes why and how. The...

Read full story
Nobody runs a SecurityManager in production. The usual reason given is that it does not survive a load test, and every guarantee in this series was bought with a check: a constraint on each call, an audit before each load, a principal set on each thread, a digest on each grant. Part 1 declared constraints on a remote call. Part 2 vetted code before a client loaded it. Part 3 and...

Read full story
If you have built an application with an interactive map, you know what you are in for. You pick a tile provider such as Google or Mapbox, or a self-hosted stack like GeoServer or Martin, and your frontend requests thousands of small image or vector tiles as the user interacts with the map. A server processes each request: it reads from a database, renders the tile, maybe caches...

Read full story