Live data from Hacker News

Codemaps: Understand Code, Before You Vibe It

cognition.ai

81–90 of 123 posts

Re: Codemaps: Understand Code, Before You Vibe It

#81
post #58

Out of nowhere Cognition with a banging product. Probably not 100% yet but the idea is so good I'll be surprised if within 6 months all the other IDEs aren't copying.

hey we been shipping!! https://cognition.ai/blog/swe-1-5 https://cognition.ai/blog/swe-grep https://cognition.ai/blog/devin-agent-preview-sonnet-4-5

Actually another piece of feedback, the "waves" release notes/videos were pretty cool. Might want to consider bringing them back.

Re: Codemaps: Understand Code, Before You Vibe It

#83

I really think more people should give Windsurf a go. It's really good. I'm a senior engineer and do a mix of agentic and regular coding and I really think people are looking past Windsurf. As the conversation shifted towards Cursor vs Claude code vs Codex people seem to have stopped mentioning it which is a shame. Source: user for 12 months - not a shill. Codemaps was a very pleasant surprise when it showed up.

I've used it, and I thought it was absolute trash. Goes crazy doing shit I don't want. I spend more time deleting crap I didn't want and reviewing and changing its code than I do just writing it myself. I know what you're going to say: I need to learn to use this groundbreaking technology that is so easy to use that my product manager will soon be doing my job but also is too hard for me a senior engineer, to find va…

Wholeheartedly agree.

Nothing my friends that heavily use AI for is groundbreaking at all. It's stuff they already entirely know how to do, describe in full detail what they want implemented, then double-check all of the results. I'm not convinced at all that they're doing architectural and long-term design thinking in this process. They're just "making the thing". I don't think they really care enough to do any of that hard thinking either. Not that they should be, considering the state of the industry and the lack of loyalty companies have to developers.

Re: Codemaps: Understand Code, Before You Vibe It

#84

Earlier quoted context omitted.

I've used it, and I thought it was absolute trash. Goes crazy doing shit I don't want. I spend more time deleting crap I didn't want and reviewing and changing its code than I do just writing it myself. I know what you're going to say: I need to learn to use this groundbreaking technology that is so easy to use that my product manager will soon be doing my job but also is too hard for me a senior engineer, to find va…

[flagged]

This isn't really a comment fit for Hacker News.

Re: Codemaps: Understand Code, Before You Vibe It

#86
Is this like an entire astro-turfing for AI thread? Can mods like ban these topics? This is clearly just like monetarily incentivized amoral behavior.

As far as I understand still working with this stuff regularly. None of the actual problems have yet to be solved at all. AI still produces garbage for anything complex. And if it doesn't, it's because you specified in full detail how it should do everything and heavily hand-held it and reviewed the results, taking more time than just doing it yourself.

And it's either that or they are flying by the seat of their pants with the thing and free-balling their way to a broken system.

Re: Codemaps: Understand Code, Before You Vibe It

#87
post #66

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…

It's been a few years, but I remember jetbrains IDEs had these, though I'm not totally sure it was built-in rather than a plugin. Personally I find automated diagrams are not that useful. You generally need to have some understanding of what's happening to know what to hide and collapse to tame the spaghetti. So it needs someone in the know to be explanatory, and as a tool it requires a similar amount of fiddling to just drawing some boxes in slideware.

Re: Codemaps: Understand Code, Before You Vibe It

#88

I really think more people should give Windsurf a go. It's really good. I'm a senior engineer and do a mix of agentic and regular coding and I really think people are looking past Windsurf. As the conversation shifted towards Cursor vs Claude code vs Codex people seem to have stopped mentioning it which is a shame. Source: user for 12 months - not a shill. Codemaps was a very pleasant surprise when it showed up.

I'm surprised that people still aren't discussing Github Copilot baked into VSCode. I pair agent mode + Sonnet 4 + Sequential Thinking + Tavily MCP servers and it works wonders. I recently prototyped the first version of our SaaS with this setup in a minimal amount of time. Also worth nothing, the pricing is extremely reasonable. Free credits + pay per use. I frequently max out the free tier and have never spent more…

I second this. As a previous AI skeptic. VS Code with Agent Mode is amazing. Perfect amount of control over what the AI is doing. For me its been a game-changer. I would describe it as letting the AI do lots of the work and me being the guiding hand.

I will say, it is extremely important to have a good AGENTS.md file and other .md files that the agent can refer to when it needs to. Also having tests is more important than ever.

And when you notice common hiccups, document it in the AGENTS.md.

Re: Codemaps: Understand Code, Before You Vibe It

#89
post #15

A feature like this isn't useful because knowing what connects to what, dependencies, etc. means nothing without business context. AI will never know the why behind the architecture, it will only take it at face value. I think technical design docs which have some context and reading the code is more than enough. This sits in the middle ground where it lacks the context of a doc and is less detailed than the code.

> because knowing what connects to what, dependencies, etc. means nothing without business context. AI will never know the why behind the architecture

since when has coding become so trivial that things are only useful if it helps with the "why" and "business context"?

Post reply on HN