I built Callgraph.io, a web app designed to visualize the code flow of complex databases and system softwares to help developers understand the source code.
The problem: I spend a lot of time diving into massive, complex codebases—particularly database like Valkey, PostgreSQL, RocksDB. Trying to trace execution paths for things like query parsing or B+ tree implementations across thousands of lines of C, C++, or Go can get overwhelming quickly. I constantly found myself lost in a maze of tabs and IDE windows just trying to hold the execution context in my head.
The Solution: I wanted a bird's-eye view. With, Callgraph.io I mapped the codebase of several databases and system softwares to create interactive visualizations of the execution flow. It makes it significantly easier to understand the relationship between different source files and functions. I also added a "one-click AI insight" feature to get a quick summary of what a function does, among other tools.
This is primarily aimed at engineers who are at the beginning of their journey into database internals, rather than seasoned experts.
I and my wife live in the city for work. While most people flock to the city and settle there as an upgraded life, we always felt empty here. Our dream is to buy a piece of land at our village and come back to our roots. I dont enjoy farming that much but my wife does. I however like the bliss of living close to nature. There is a river that flows nearby and taking a dip in that fills me with so much joy that I could never find anywhere in the city.
For the uninitiated, could you share your perspective on how feasible quantum computing is? Isnt it built on quantum entanglement which seems to break universal speed limit? Is this a feasible engineer or just a scientists imagination?
I think its impossible for the Herokus and the digital oceans of the world to survive in the cloud world. They might be able to create better experience for customers but noone can match the networking that AWS, GCP and Azure can provide. Low latency will always win over better developer experience.
Tried freelancing for a bit. Thought being my own boss might give me better mental health. I couldn't have been more wrong. The better part of my time was spent on convincing the clients, what is built is what they had described.
I built Callgraph.io, a web app designed to visualize the code flow of complex databases and system softwares to help developers understand the source code.
The problem: I spend a lot of time diving into massive, complex codebases—particularly database like Valkey, PostgreSQL, RocksDB. Trying to trace execution paths for things like query parsing or B+ tree implementations across thousands of lines of C, C++, or Go can get overwhelming quickly. I constantly found myself lost in a maze of tabs and IDE windows just trying to hold the execution context in my head.
The Solution: I wanted a bird's-eye view. With, Callgraph.io I mapped the codebase of several databases and system softwares to create interactive visualizations of the execution flow. It makes it significantly easier to understand the relationship between different source files and functions. I also added a "one-click AI insight" feature to get a quick summary of what a function does, among other tools.
This is primarily aimed at engineers who are at the beginning of their journey into database internals, rather than seasoned experts.
I'd really appreciate your feedback!