I've been working on this app for a few months now, and I think it's at a stage where I can share it with everyone.
I built this app because AI-assisted coding is here to stay. With the right harness, AI can handle many things that were previously difficult. It can even perform PR reviews, in many ways better than humans. However:
> Code is only the visible part of a program. The real program is the understanding behind it: why it's built this way, how it maps to the business, and what breaks when you change it. That understanding lives in people, not in files.
Every day I slog through reviewing quite a few PRs containing dozens of file changes, and the only thing I had were file diffs. I struggled to build a complete picture of how all those different pieces connected. I'd jump between files and functions in my IDE, trying to piece together how they all fit.
So I built this tool to avoid hopping between different files and functions. You give it a PR, and it calculates the blast radius in the form of impacted or new user journeys. In those user journeys, you can see what was changed. You don't need to hop between different files, and for each step in the journey, you can go directly to the code. It provides full context in one single view.
A lot of the time I thought, "Okay, why do I need to build this thing? Claude can do it." Still, I was never happy with Claude's output, and I always found myself reaching for this tool. At some point I thought, "Why not just build it properly and share it with everyone?" This tool has helped me immensely with my understanding of the codebase.
Visualising code as a city is not the main goal of this tool, but I wanted to try it anyway. I think it's pretty cool. Sometimes, looking at the size, height, and width of a building gives me a feeling that maybe that class needs some refactoring.
I put a lot of effort into this. I do intend to sell it commercially, but before that, I wanted to see if people find it useful. Would love your feedback.
I've been working on this app for a few months now, and I think it's at a stage where I can share it with everyone.
I built this app because AI-assisted coding is here to stay. With the right harness, AI can handle many things that were previously difficult. It can even perform PR reviews, in many ways better than humans. However:
> Code is only the visible part of a program. The real program is the understanding behind it: why it's built this way, how it maps to the business, and what breaks when you change it. That understanding lives in people, not in files.
Every day I slog through reviewing quite a few PRs containing dozens of file changes, and the only thing I had were file diffs. I struggled to build a complete picture of how all those different pieces connected. I'd jump between files and functions in my IDE, trying to piece together how they all fit.
So I built this tool to avoid hopping between different files and functions. You give it a PR, and it calculates the blast radius in the form of impacted or new user journeys. In those user journeys, you can see what was changed. You don't need to hop between different files, and for each step in the journey, you can go directly to the code. It provides full context in one single view.
A lot of the time I thought, "Okay, why do I need to build this thing? Claude can do it." Still, I was never happy with Claude's output, and I always found myself reaching for this tool. At some point I thought, "Why not just build it properly and share it with everyone?" This tool has helped me immensely with my understanding of the codebase.
Visualising code as a city is not the main goal of this tool, but I wanted to try it anyway. I think it's pretty cool. Sometimes, looking at the size, height, and width of a building gives me a feeling that maybe that class needs some refactoring.
I put a lot of effort into this. I do intend to sell it commercially, but before that, I wanted to see if people find it useful. Would love your feedback.