Blog

Continuing the JVM blog series, this is part 3 of a JVM adventure.  This post doesn't require you have the knowledge covered in my previous blogs Part 1 and Part 2, however, I still highly suggest you read them so that you will have a better understanding of materials covered here.

Whether you are a young developer or a seasoned professional, one of the hardest parts of software development is finding a juicy project to work on. Hackathons are the solution to that problem.

Checkout the latest hackathon that Callibrity participated to learn more.

This is part 2 of my previous blog, if you haven't read the previous one, I strongly suggest you read that before diving into this blog.

In this blog, we will take a further look of JVM garbage collection (GC) - the available garbage collectors given by JVM or more precisely HotSpot JVM.

Senior Software Developer, Jack Merideth was selected as a speaker at Stir Trek in 2019. He recaps his experience as a first-time speaker himself, and shares some of his favorite talks in this blog post.

One of the greatest tools in the functional programmer’s tool belt is the notion of composure. It’s a pattern that allows you to take two things and combine them, like LEGO pieces or the segmented tracks of a train set, and join them together in a myriad of ways with different structures or pathways each time.

Most software engineers have heard of Java or JVM garbage collection (GC) but probably not all of us have paid much attention to it, so we rely a lot on the default settings. Especially for me, being an engineer from a non-JVM language background, the majority of my time was spent on C/C++ development. I didn't get into how garbage collection works until I started working in a position in the IT industry.