Shai Almog

Skaffold is a cloud native open source framework from Google that lets SpringBoot devs build Kubernetes apps easily and deploy effortlessly!

We can see production disasters from miles away. Bad communication, missing skills, immature technological choices create ongoing disasters.

The book is about preventing failures, by preventing/lowering bugs. It classifies and organizes the terms we use to define a bug.

Just in time for Halloween failures in production are scarier than most movie monsters. Here’s a personal scary story of a production fail…

In this series, I’ll walk you through the process of debugging applications and finding issues within them.

Java Debug Wire Protocol (a.k.a. JDWP) was designed for testing internally. Opening it to production is a HUGE security and stability risk…

Recently a junior developer sent me an obfuscated stack trace and was pretty surprised when I instantly knew the problem and pointed him at the necessary change. To be fair, I had the advantage of being the person who put that bug there in the first place… But still the ability to glean information from a stack trace, even an obfuscated one, is a serious skill.

In the Debugger Checklist (Part I), I introduced some of the high level concepts and reviewed some of the common things you can do.

In this part, we’ll get down to the process. Again, it’s important to stress that this is boiled down and concentrated!

Win at debugging by following an organized process and leveraging the tools you already have!

We’re going to skip ahead to a point where you have a bug you can reproduce (consistently or otherwise) but you don’t understand or can’t prove the cause.

As developers, we’re all familiar with debuggers. We use debugging tools on a daily basis – they’re an essential part of programming. But let’s be honest. Usually, we only use the breakpoint option. If we’re feeling frisky, we might use a conditional breakpoint.

But guess what, the IntelliJ IDEA debugger has many powerful and cutting-edge features that are useful for debugging more easily and efficiently.