←back to thread

261 points david927 | 4 comments | | HN request time: 0s | 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 #
Cthulhu_ ◴[] No.43159227[source]
On a smaller scale it reminds me of the original concept of Light Table, which let go of the abstraction of individual files in favor of editing your code in a tree like structure. It's a shame this concept seems to have died out, I'd be curious about alternatives to plain file based UX.
replies(2): >>43161519 #>>43162735 #
1. jtwaleson ◴[] No.43162735[source]
Cool. My long-term vision for software development would be to make a new programming environment that structures code in ASTs and stores it in a database rather than file based. However, that will have to come later. First this :)
replies(3): >>43164347 #>>43165441 #>>43169752 #
2. rozap ◴[] No.43164347[source]
a friend/old coworker of mine played with that idea in datalog and wrote about it. https://petevilter.me/post/datalog-typechecking/ it had some pretty cool implications.
3. Cerium ◴[] No.43165441[source]
Sometimes I daydream that we moved beyond text files and had a format with a UUID per line.

Version control could reliably track movement between files, we could identify copy and paste (and prompt when refactoring), and code coverage changes would be accurate.

4. vincnetas ◴[] No.43169752[source]
You should check Unison language. Each Unison definition is identified by a hash of its syntax tree. So if two unrelated functions have identical AST this means they that from language perspective it's the same function.

https://www.unison-lang.org/docs/the-big-idea/