Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Codemaps: Understand Code, Before You Vibe It

cognition.ai

Post reply on HN
Print view View original

101–110 of 123 posts

Re: Codemaps: Understand Code, Before You Vibe It

#101

Post by conartist6 »

latexr wrote: post #98
conartist6 wrote: post #96

Earlier quoted context omitted.

You read the same response I did, right? And you... thought it was... literally about sawdust? ...and you took offense? I'm so confused...

Seems like you haven’t understood my comment, but I’m unsure how to clarify it for you. Perhaps start by not assuming that expressing disagreement means taking offence? Not everything needs to be emotionally charged. Again, steel man.

Just checked again to give you the benefit of the doubt, and I still see the same thing. I read the long post as a thoroughly steelmanned response. Nobody has yet engaged with the philosophical content of that post. You cried foul for reasons I still can't understand. Would you tell us what you thought about the post on an intellectual level?

I eat meat but I'm one of those people who is ethically opposed to consuming AI content. An AI-vegan you might say.

I've had a shouting fight with someone who tried to spoon feed an AI summary to me in a regular human conversation.

But. I know that people are going to sneak AI content into what I consume even if I do everything within my power to avoid it.

The question is straightforward if immensely complex. Do I have a right to not be fed AI content? Is that even a practical goal? What if I can't tell?

Re: Codemaps: Understand Code, Before You Vibe It

#102

Post by szjanikowski »

bigiain wrote: post #66
gnarlouse wrote: post #37

A few things to point out after reading and thinking about this: - Another AI firm building products focused on Fortune 500 scale problems. If you're not at a F500, this tool isn't necessarily a good fit for you, so YMMV. - static analysis tools that produce flowcharts and diagrams like this have existed since antiquity, and I'm not seeing any new real innovation other than "letting the LLM produce it". They say it's…

> static analysis tools that produce flowcharts and diagrams like this have existed since antiquity Today I am apparently on of xkcd's "Lucky 10,000". Does anyone have any recommendations for such tools? Ideally open source, but that's not a hard requirement. (Although "Enterprise - if you have to ask the price you can't afford it" options will not work for me.) I'm particularity interested tools that work with Pytho…

We are building https://noesis.vision/ a similar tool to extract the system architecture from the source code according to the patterns. We are now in beta for .NET.

After working with the topic for multiple months I can tell you that introductions for new-joiners are not the only use case for this kind of extracted knowledge. Many ppl in the organizations need insights into the software structure as they either impact decisions shaping this structure (e.g. analysts) or depend on the decisions about this structure (e.g. testers, or support agents)

It's all the matter of giving access to reliable architecture knowledge structured by a consistent ontology. Garbage in / garbage out - the higher the knowledge quality, the better the output - both for human and agentic knowledge consumers.

Re: Codemaps: Understand Code, Before You Vibe It

#104

Post by latexr »

conartist6 wrote: post #101
latexr wrote: post #98

Earlier quoted context omitted.

Seems like you haven’t understood my comment, but I’m unsure how to clarify it for you. Perhaps start by not assuming that expressing disagreement means taking offence? Not everything needs to be emotionally charged. Again, steel man.

Just checked again to give you the benefit of the doubt, and I still see the same thing. I read the long post as a thoroughly steelmanned response. Nobody has yet engaged with the philosophical content of that post. You cried foul for reasons I still can't understand. Would you tell us what you thought about the post on an intellectual level? I eat meat but I'm one of those people who is ethically opposed to consumin…

> I read the long post as a thoroughly steelmanned response.

Steel manning means engaging with the strongest interpretation of the argument. The original comment clearly used sawdust not as sawdust specifically but as a substitute for something harmful or inappropriate. It’s not even about eating. So spending half a comment on “ackchyually, sawdust is good for you” (this is a caricature for brevity) is nitpicking something which doesn’t matter and derails the rest of the comment which is based on it.

Steel manning would’ve meant engaging in good faith, understanding “eating sawdust” isn’t meant literally but as a random choice for “something bad”, and replying to the latter, not the former.

In other words (I’m explaining it three times to drive the point home), steel manning means not nitpicking the exact words of someone’s argument but making the effort to respond to their meaning. It’s addressing the spirit of the comment above its letter (https://en.wikipedia.org/wiki/Letter_and_spirit_of_the_law). Sometimes the difference between those isn’t obvious, but I’m arguing that in this case it is.

> I eat meat but I'm one of those people who is ethically opposed to consuming AI content.

Eating meat or being vegan has nothing to do with the original comment. Again, it’s not even about eating, that was clearly a random example which could be substituted by a myriad other things. When you describe your eating habits you’re already engaging with a derailed, straw manned version of the argument instead of the original point the person was making.

Re: Codemaps: Understand Code, Before You Vibe It

#106

Post by tleyden5iwx »

soco wrote: post #97
BinaryIgor wrote: post #93

Well, interesting idea, but can you trust that it generates it properly? Because if it doesn't, then your understanding of the code will be incorrect, even worse than lack of knowledge; and if you do need to check all the things it has generated for you, as a description - doesn't it defeat the purpose of the tool?

Arguably, if you vibe code you don't really care about the code, thus even less about the diagram. So you'll vibe something, get a diagram of something to show your boss, and you can move on.

Yeah but there are a lot of vibe engineers, and we care about the code, because we have to own it

Re: Codemaps: Understand Code, Before You Vibe It

#107

Post by dilawar »

szjanikowski wrote: post #102
bigiain wrote: post #66

Earlier quoted context omitted.

> static analysis tools that produce flowcharts and diagrams like this have existed since antiquity Today I am apparently on of xkcd's "Lucky 10,000". Does anyone have any recommendations for such tools? Ideally open source, but that's not a hard requirement. (Although "Enterprise - if you have to ask the price you can't afford it" options will not work for me.) I'm particularity interested tools that work with Pytho…

We are building https://noesis.vision/ a similar tool to extract the system architecture from the source code according to the patterns. We are now in beta for .NET. After working with the topic for multiple months I can tell you that introductions for new-joiners are not the only use case for this kind of extracted knowledge. Many ppl in the organizations need insights into the software structure as they either impa…

Love what you are trying to do here.

Will evaluate it on a couple of PHP codebases I maintain at work.

Is there a way to contribute to the project?

Re: Codemaps: Understand Code, Before You Vibe It

#108

Post by GuB-42 »

kps wrote: post #43
apstls wrote: post #42

Sounds very cool. I wanted to try this out, so I opened Windsurf for the first time in ages and clicked the "Upgrade Available" button, which sent me to: https://windsurf.com/editor/update-linux Did you install using apt or apt-get? If so... 1. Update package lists sudo apt-get update 2. Upgrade Windsurf sudo apt-get upgrade windsurf Whle `apt-get upgrade windsurf` will technically upgrade Windsurf, instructing users…

So `apt-get upgrade $PACKAGE` has ridiculous semantics that no one would expect, and the actual syntax for upgrading a package is in neither the man page nor the command help.

I have been using Debian for literally decades and I didn't even know "apt-get upgrade $PACKAGE" existed. It is weird, it doesn't appear in the documentation, it doesn't work with the "apt" command, it means it is probably a relic of the past left there for compatibility reasons and you probably shouldn't use it.

My guess is that someone or some LLM hallucinated this command, "apt-get upgrade" is for upgrading your system, not for upgrading a single package, and it takes no extra argument.

For upgrading a single package, just do "apt install $PACKAGE". It is the same command as for installing. The semantics is rather clear to me, upgrading is like installing the new version on top of the old version. It also makes no sense to install a package you already have or to upgrade a package you don't have, but if you want to be sure, for example because you don't know if you already have the package installed or not, there are the --no-upgrade and --only-upgrade options.

Re: Codemaps: Understand Code, Before You Vibe It

#110

Post by GuB-42 »

Lvl999Noob wrote: post #95
swyx wrote: post #52

Earlier quoted context omitted.

hiya! team noticed your comment and agreed - and it is fixed. - const CodeSnippetTwo = `sudo apt-get upgrade windsurf`; + const CodeSnippetTwo = `sudo apt-get install windsurf`;

Why not use apt?

apt-get has a more stable interface and is more suitable for scripts and instructions intended to be followed to the letter.

apt is better for interactive use and by people who are not just blindly following instructions.

Here there are arguments for both. As commands intended to be copy-pasted in a terminal, using apt-get makes sense as it is the safest choice. But it is also intended for humans, it is not a script, so maybe apt would be better. To me, both ways make sense.

Post reply on HN