We’re taking a walk down memory lane to see which topics, trends and posts interested you in 2018.
As part of our 2019 resolutions, we’ve decided we want to write more about the topics that interest you, our beloved audience. And in order to do that, we took a deep look into the top topics and posts that interested you throughout 2018.
We made a list, checked it twice, and found out who’s mention-worthy (and who’s not). So without further ado, we present to you the top posts of 2018:
The most popular post of 2018 was a beginner’s crash course in Java Virtual Machine (JVM) architecture and Java bytecode 101.
In the post, we cover the architecture of the JVM, give an overview of how it works, as well as go deeper into bytecode with the help of javap. We sum it up with explaining how you can “Write Once, Run Anywhere” with Java.
CI/CD practices encourage frequent code integration in development, speed up preparations for new releases and automate deployments. While the tools have improved over time, the data we use to evaluate them didn’t change much at all.
On the bright side, there are better ways to face and overcome the challenge of maintaining high quality code within a CI/CD workflow. How? We’ll let Tali Soroker answer that one.
2018 was an important year for us as a company, as we started working on our .NET solution. That led to some interesting posts about what Java and C# can learn from each other.
One of the top posts that caught your attention was Tali Soroker’s deep dive into their respective Virtual Machines. In this post, Tali lays out the top similarities (and differences!) between the CLR and the JVM.
4. If You’re Planning to Write Java Code in 2020 – Here Are the Top 5 Predictions You Can’t Afford to Miss
Although 2019 is just kicking off, there’s no better time to plan towards the future, especially when it comes to your software.
As part of our own transformation towards the future, we’ve gathered some of the interesting and relevant 2020 predictions of our field and bundled them up to a list of the top 5 predictions for 2020 that you can’t afford to miss.
One of our more controversial posts came from David Levanon, Backend Group Lead on OverOps’ R&D team. In it he explained in detail why he decided to delete his IDE, and why it was the best choice he ever made.
If you’re considering deleting your Java IDE, David has some useful tips as well as some warnings, since it’s a hard choice that might not suit every developer.
Now, this is a story all about how, our production code got flipped-turned upside down. And we’d like to take a minute – to tell you about – how OverOps on OverOps kicks bugs bu**s 🍑.
How can you avoid the risks of mishandled errors? By understanding the negative impact of swallowed exceptions, and learning how to fix them.
Alex Zhitnitsky walks us through the complete process of finding and handling swallowed exceptions; from identifying that there’s an issue and down to implementing a continuous reliability approach across our entire environment.
Moving towards a CI/CD workflow means that we’re adding automation to our process, which is great, but we need to make sure we keep the quality of the code intact.
In this post we define the critical steps along the development lifecycle, and identify how we can improve our workflow and code, before promoting it to production.
Shahar Valiano, a C++ engineer on the microagent team, developing OverOps’ low level JVM agent, is a big Linux fan. That’s why he got very excited when he was tasked with porting the OverOps agent to native Alpine Linux.
In his post, Shahar covers his experience in setting up an Alpine Linux workstation for C++ and Java development, as well as share some tips, know-hows and resources.
No year is complete without our annual top Java libraries post, and 2018 was no different. This year we crowned a new Java library as the most popular one, and were able to examine some interesting trends within the developer community.
This year, we took a slightly different approach and looked not only at the top, but also at the top bottom libraries as well, trying to predict where they’ll be in 2019.
In the heat of battle, when an application breaks and customers are feeling the burn, who is ultimately responsible for identifying and fixing the issue?
We closed 2018 with a bang, trying to solve the question of accountability between developers and operations, and discovered the uprising trend of shared accountability between the two functions.