this is amazing!
Codemaps: Understand Code, Before You Vibe It
61–70 of 123 posts
Re: Codemaps: Understand Code, Before You Vibe It
#62I 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 as a big Windsurf advocate, miles ahead of Cursor IMO but I've fully switched to Codex these days. The cloud environments are just such a nice feature. Still like Windsurf though their pricing is what drove me to not roll it out across my company.
cloud envs are good :)
1) did you compare codex cloud with devin?
2) how about the new claude code teleport feature from web to cli?
just wanted to pry for more opinions on what matters to you
Re: Codemaps: Understand Code, Before You Vibe It
#63Re: Codemaps: Understand Code, Before You Vibe It
#64Earlier quoted context omitted.
first mention i've heard of abacus.ai and IDE. what do you think stands out about them? you might struggle with Windsurf since you're so command line heavy. but pro tip - ask for command line work to be done inside of Windsurf's Cascade agent. they were first to the terminal-inside-aichat pattern and i really like how it's much better at command line stuff than i am (or can do the legwork to specify command line comm…
> first mention i've heard of abacus.ai and IDE. what do you think stands out about them? Their reasoning agent is better than anything else I've used, tbh. The inability to use it in a CLI environment is why I stopped using it. They have a router that they hook into that "intelligently" chooses models for you in a normal "chat" setting. The power comes with their DeepThink (or whatever) mode that has a VM hooked up…
ah yeah i have heard about their router. i wonder if GPT5 doing a router hurt it a bit.
Re: Codemaps: Understand Code, Before You Vibe It
#65Figuring out new codebases is definitely one of the most challenging and time-intensive things I have had to do in my jobs.
we obviously agree but one of the problems i had with onboarding as a key proposition is that onboarding "seems" like a onetime problem. i lacked the datapoints or anecdotes to convincingly pitch "onboarding = context switching", a more recurring problem as the size of your team and size of your codebase and size of your tenure grows, even if its technically the same codebase, you're "always" onboarding to wahtever it is you're working on or maintaining or putting out fires.
Re: Codemaps: Understand Code, Before You Vibe It
#66A 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 Python, Java, and Javascript (Angular flavoured Javascript, it if matters)?
Re: Codemaps: Understand Code, Before You Vibe It
#67Earlier quoted context omitted.
> AI will never know the why behind the architecture… That's true only if you don't provide that context. The answer is: Do provide that context. My experience is that LLM output will be influenced and improved by the why's you provide.
if you know that context, you don't need a codemap
As you just said, codemaps don't include the "why" behind the architecture. That's context you need to add.
Re: Codemaps: Understand Code, Before You Vibe It
#68Earlier quoted context omitted.
it takes longer to explain the context to the model than it does to just write the code based on the context I already understand, especially since code is more terse than natural language
But wouldn’t the context also be useful, in written form, to colleagues?
It absolutely is, yes.
Re: Codemaps: Understand Code, Before You Vibe It
#69A 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…
https://www.ensoftcorp.com/products/atlas is the Java/c oriented flavor I'm most familiar with. I've used them for Javascript before previously, although I'd have to do some digging to find the particular package I used. I am confident that you could find one with an npm/pypi search.
Re: Codemaps: Understand Code, Before You Vibe It
#70Figuring out new codebases is definitely one of the most challenging and time-intensive things I have had to do in my jobs.
we obviously agree but one of the problems i had with onboarding as a key proposition is that onboarding "seems" like a onetime problem. i lacked the datapoints or anecdotes to convincingly pitch "onboarding = context switching", a more recurring problem as the size of your team and size of your codebase and size of your tenure grows, even if its technically the same codebase, you're "always" onboarding to wahtever i…
Depends on how big the codebase is and how many people work on it and how often you need to switch to an unfamiliar context, but yes agreed, it's context switching, and is a regular thing. It is part of the job of software engineering, learning piles of code you were previously unfamiliar with.