Blog

In the midst of the global COVID-19 pandemic, many tech companies are finding themselves working remotely and under-prepared. Some tech companies like GitLab - the largest all-remote company in the world, have no physical offices and roughly 400 employees so working remotely is business as usual. Other companies, like Twitter, just told all it's 5000 workers in 35 offices around the world to work from home.

Recall a meeting where multiple individuals of a team started getting into a heated discussion. As it escalated, you envisioned ways you could escape unscathed. Maybe you were someone who was strong in their beliefs and became frustrated when others didn’t see your point. Perhaps, it started as a brainstorming session with a ton of ideas thrown out but no solution was agreed upon. Regardless of the situation, we have all been a part of the dreaded “unproductive” meeting.

About 4 months ago, I was given the opportunity to architect a greenfield react project with staggering amounts of complexity. I had only heard of hooks in passing before this project, but knew they were the new hotness in the world of front-end react development. Hooks could purportedly remove the need for redux as a state management tool, cut boilerplate code in half, and improve performance significantly. I thought to myself, "These claims are obviously exaggerated. Surely a production grade application with a feature rich front-end needs class components, right?"

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.