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.
First thought: 'i wonder what the app is made from'.
Followed by looking at the exe in a hex editor...
Oh that looks like edge .. renaming the file and the rest is HN history
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.
True, it can't compete with AWS/GCP/Azure if you're large scale. But most of us are not large scale, we just need a no frills experience instead of dealing with 27 nested panels just to spin up a VM.
Heroku runs on AWS though, doesn’t it? They just package it.
I don’t think it’s impossible for them to survive. Salesforce bought them more than 10 years ago and did little to support growth of Heroku. And yet they’re still around and people still ask „is there something new with comparable customer experience?” because they don’t mind paying more
on the other hand modern tech stacks can process insane amounts of req/s for typical websites/services in a single shared vserver core. not your 2010 ruby snoozefest anymore. plus I can't even remember when a few decade old droplets needed anything from me and still host some things just fine with zero issues or friction or nagging at all. DO is the number one pick for me in 2026 still when the problem fits a droplet style deployment, full stop.
I've never found cloud anything to beat the speed (and price) of a well placed server.
DO has always been a bit rich for my blood though, and even a low cost hetzner VPS has less cores than I remember seeing at the same price a decade ago. I could be wrong there though I usually use Vultr for their SYD region.
A slower background transcode usually doesn't matter, but a faster transcode that stops important processes running in the meantime might. This is usually fixable with effort, but sometimes it's nice to not have to configure everything to the nth degree.
I don't really buy it. The idea that somehow getting one less core but faster per core speeds per pricing bracket makes any difference in this imagined problem.
There are many different configurations of vps available with different numbers of cores, if you are picking the vps configuration specifically to have more cores than some transcoding software uses by default to avoid configuring a thread limit for that software then you are still configuring things to the nth degree just at the objectively wrong level of abstraction.
Risk to Netanyahu's career or wellbeing can do the trick because as we have seen lately Israel is willing to risk Israel's future and the Jewish communities safety across the world. It's not even as a part of grand strategy or anything, they are pushing to make criticizing Netanyahu a taboo.
I used to admire Israel as the only sane country in the middle east with great culture for entrepreneurship even if they had elements of atrocities(these could be fixed through civil progress in sane countries). I'm genuinely sad to see it has turned into a genocidal theocratic lunacy like the rest of the middle east and theocratic lunatics can do anything.
If the calculus skewed by arrogance and religious delusions is on the positive for the ruling class, they will use a nuke.
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!
reply