←back to thread

261 points david927 | 3 comments | | HN request time: 0.019s | source

What are you working on? Any new ideas that you're thinking about?
Show context
jtwaleson ◴[] No.43157056[source]
I'm creating an infinite canvas that has all your organization's code and documentation on it. If you zoom in, you can see the code, if you zoom out you see the big picture. By giving everything a place on the map, it becomes easier to figure out your way through the landscape and understand the systems. Different modes can you show you different things: code age, authorship (bus-factor, is the person still with the company etc), languages used, security issues. There's time-travel, think Gource for all software in your company, and maybe the most fun: a GeoGuessr for code. Select the repos for your team (or if you feel confident, of the entire org), you get a snippet and have to guess where it is. The plan is for LLMs + tree-sitter to analyze all the code and show relations to other systems, databases etc.

I had the idea 2 years ago, but starting building in earnest 2 months ago. Spending all my time on it now, minus 3 or 4 days per week of earning money. Currently looking for a GTM/sales-oriented cofounder in NL.

replies(20): >>43157073 #>>43157136 #>>43157178 #>>43157780 #>>43158134 #>>43158368 #>>43158505 #>>43158526 #>>43158634 #>>43158984 #>>43159227 #>>43159992 #>>43160392 #>>43161555 #>>43161560 #>>43162756 #>>43164555 #>>43172370 #>>43196913 #>>43256135 #
1. koliber ◴[] No.43157780[source]
This sounds lovely. I am a spatial thinker so this is right up my alley.

How do you deal with different kinds of groupings and connections? For example, some things could be connected because they are “integrations”, or because they deal with notifications, or because they’re available only in the enterprise plan. Not all related things are related in the same way.

replies(1): >>43157957 #
2. jtwaleson ◴[] No.43157957[source]
Still a lot of thinking to be done here to be honest. I've built a very fast canvas with zoom-to-code, parsing the git history, code age overlays etc, but understanding the architecture and connections is the next big thing I have to figure out. Plenty of ideas though!
replies(1): >>43158893 #
3. jasdi ◴[] No.43158893[source]
Might be useful - https://schem.io/