Show HN: Codemap – one-page interactive map of any Go repository

Posted by peter_retief 2 days ago

Comments

Comment by stigok 2 days ago

I like this! It would be great if it was a hosted solution where I could just add any repository to the URL, like https://pkg.go.dev/ does for the godocs.

Comment by quibono 2 days ago

Possibly silly question, but is this aimed at Go repos only because of some structural reason, or because this was the author's intention?

I can see this approach being useful across non-Go repositories too.

Comment by peter_retief 2 days ago

Just Go for now. .. useful across non-Go repositories too. yes

Comment by quibono 2 days ago

Also, just for posterity, in terms of similar solutions that I know of there's Whiteboard [0] and T3's Guide view [1]

[0] https://dev.fast/

[1] https://github.com/pingdotgg/t3code

Comment by order-matters 2 days ago

why Go

Comment by peter_retief 2 days ago

What I am using

Comment by joe-esquibel 2 days ago

Whats the validation strategy that you used for this? I run a similar project and I found that golden repos were needed to prevent drift. Have you stress tested this to find any limits? I compared my go work to ctags and treesitter for proof of functions found and list precision and recall.

Comment by peter_retief 1 day ago

[flagged]

Comment by int0x21 2 days ago

I got inspired and "vibe coded" a Perl version :) https://github.com/interrupt21h/perl-codemap

Comment by peter_retief 1 day ago

I will add a link..

Comment by baalimago 2 days ago

Interesting! It would be cool to see this as a cli tool to allow agents to efficiently inspect codebases

Comment by dmoose 2 days ago

I took a bit different approach assuming that agents can use the language servers to get structure and just trying to keep them honest. With this in a hook a lot of stuff is caught quickly without wasting a lot of context. https://github.com/dmoose/gochecks

Comment by lukasschwab 2 days ago

Agents are pretty savvy with the `go doc` and `go list` builtins, especially if you nudge them!

Comment by slantedview 2 days ago

This is really cool. I could see adding this alongside the godocs to my open source projects.

Comment by 2 days ago

Comment by RamblingCTO 2 days ago

> Every Go package in github.com/peterretief/yggstore, what it builds on, and the functions in each of its files. Tests are left out.

it's a cool idea, but reads super sloppy, sorry. There is literally no effort in this.

Comment by peter_retief 2 days ago

It is just the idea, for me to navigate my project code, free to use and change

Comment by gchamonlive 2 days ago

It's ironic you didn't put any effort into calling out the lack of effort put in the project. Btw, the project README is fine, this is AIslop hysteria.

Comment by RamblingCTO 2 days ago

And what would effort look like, besides inspecting code and the result to find the message I quoted, huh?

Comment by gchamonlive 2 days ago

Idk, the project looks good to me, you are the one making claims and not backing them up properly. To me you just disagree with this specific aesthetic choice and are lazily extrapolating to the rest of the project just in case the comment could catch some upvotes.

Comment by RamblingCTO 1 day ago

specific aesthetic means raw claude slop w/o changing anything about it? that's no lazy extrapolation my dude. I'm just saying it lowers the value of the project, bc I can assume that it's probably not gonna be touched any further (without throwing shade on op, I think it's a cool idea. it's just way behind it's potential bc of the claude copy and the claude design in the report). it's a few commits made by claude, I assume there was no real work on the side of op. that lowers my felt value of the project. that's neither lazy nor unfair, it's the last 2 years of vibecoding? if op decides to clean it up, I'd be happy to explore it actually. I kinda do measure projects by human effort. I don't know why you're throwing shade bc you seem to disagree.

Comment by peter_retief 1 day ago

In my 20+ years of coding I have produced way worse slop that Claude wrote here.

Ironically this tiny utilty was produced to make keeping up with Ai code a little easier.

my advice to you is to write code that manages Ai, I dont think Ai is going away any time soon...

Comment by RamblingCTO 1 day ago

> Ironically this tiny utilty was produced to make keeping up with Ai code a little easier.

which is fine. I just think we're losing something important when we reduce friction and effort. and for me--totally personal preference--keeping raw claude output is just that. I don't wanna throw too much shade on you or your project tho, that wasn't my intention. I'm just fed up with the moronic way of how claude writes, designs, etc.

Comment by peter_retief 1 day ago

I don't totally disagree with you and have been feeling a bit guilty of posting this work as my own when in fact it is generated by Claude, even though I try and make it clear that much of the code is generated.

I have never been able to produce this volume of work so it is very tempting to let it all hang out, so to say

The concepts are all mine and I am really happy to be able to give back to the open source community albeit a small gesture.