Jakob Löhnertz on foojay.io - Friends Of OpenJDK

How to find dead code in your Java services

Tue, 07 Nov 2023 10:40:48 +0000

When building solutions, the code we write can last many years. While casually browsing legacy code, we might wonder; is this still used? The missing documentation or outdated tests do not help us answer this. When asking around, nobody really knows. Let’s try to delete it, shall we? Then, chaos ensues: it turns out it is still used to support some legacy users, in case of emergency, or by that one forgotten integration everyone still uses.

Embracing Java 17: Here’s What We Learned at Picnic

Mon, 30 May 2022 08:10:20 +0000

Java 17? Count us in! At Picnic, we’re more than a grocery delivery company.

There’s a lot of tech behind the scenes that enables us to provide the affordable, sustainable service our customers have come to expect — and the back end of most of that tech is written in Java.

So when the new Java 17 release was announced, we were excited to get started.

Having moved to Java 11 within the quarter after its release, we stepped it up a gear this time and are proudly running Java 17 in production in the same quarter it was released — we like to move fast!

Quest to the OS: Java Native Memory

Fri, 08 Apr 2022 04:19:05 +0000

As developers we want to spend most time on new features and improvements, providing value to our users or customers. However, all software inevitably contains bugs and other defects. A lot can be done to catch defects before software reaches production (something Picnic’s automated fulfillment center team has previously written about) but some defects are likely to go undetected until the software is in the hands of users.

One such case happened when Picnic’s Distribution Systems team started to get notified that one of its deployments, the Fulfillment Service, was regularly killed and restarted by our Kubernetes cluster. This particular deployment houses many of the planning algorithms employed by Picnic, such as its truck scheduling algorithm.