Introducing Guava

A better way to debug

·

2 min read

Problem Statement:

We have all experienced a production bug firing via Sentry, a critical integration test that just started failing, or worst of all, a customer reaching out saying something is broken. The issue always appears out of thin air and goes along the lines of "it worked yesterday but today it's not."

Usually, the bug report indicates that some old function written years ago by someone else is no longer working. You have no idea how the code works and where the bug could be. You have to spend hours trying to understand the code, then hours recreating the bug before being able to patch it.

By some estimates, engineers spend up to 50% of their day debugging these types of issues.

For the amount of effort and time we spend debugging production issues, there is a woeful lack of tools available. Developer tools only focus on developing new code and publishing new features—not maintaining and debugging it. AI copilots like GitHub and Microsoft help write new code but not maintain the old. IDEs help write and format new code. Monitoring tools like Sentry or New Relic alert us about issues but do absolutely nothing to help fix them.

The Solution:

This is why we are introducing Guava. A fully integratable platform that automates the debugging process to save you time and sanity. The only thing you have to do is link your bug and your codebase!

Guava analyzes the production bug and then your code to quickly provide likely suspects that caused production errors. This gives engineers top hits on where to start their investigation of the bug.

Guava provides explanations about how your code works so that you don't spend hours trying to understand it.

Guava knows that production bugs do not occur in an isolated codebase. A production bug can occur in any of the services between the frontend and the database. Thus, it hunts through your entire stack, like an experienced engineer, searching for the culprit.

Guava displays critical information for debugging in a centralized place. It shows highlights such as what code was deployed and when it was deployed. It shows how widespread the issue is and how impactful the bug is.

With Guava, you can fix real-time, customer-impacting, production bugs faster. Spend less time debugging and more time building! With Guava, you finally have an answer to "It worked yesterday, but today it's not!"

https://guavas.xyz/