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.

▲

philippta 2 days ago | parent | next [-]

To add to that, a lot of business context is stuck in people‘s heads. To reach the level of a human engineer, the coding agent would have to autonomously reach out and ask them directed questions.

▲

CharlesW 2 days ago | parent | prev | next [-]

> 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.

▲

asdev 2 days ago | parent | next [-]

if you know that context, you don't need a codemap

	▲	CharlesW 2 days ago \| parent \| next [-]
		As you just said, codemaps don't include the "why" behind the architecture. That's context you need to add.
	▲	baq 2 days ago \| parent \| prev [-]
		this is possible if you have a couple two-pizza teams. beyond that, good luck.

▲

dingnuts 2 days ago | parent | prev [-]

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

▲

fizx 2 days ago | parent | next [-]

Definitely, iff you have to provide the context with every task. If agent memory worked better and across your whole team, then providing context might be much easier

▲

Jaxan 2 days ago | parent | prev [-]

But wouldn’t the context also be useful, in written form, to colleagues?

	▲	CharlesW 2 days ago \| parent [-]
		It absolutely is, yes.

▲

swyx 2 days ago | parent | prev | next [-]

you might be surprised how much business context leaks into a codebase and that's plenty to work on :)

https://deepwiki.com/search/vimfnfnname-lets-you-call-neov_e...

but also how much you kinda dont need it when you're just debugging code

https://windsurf.com/codemaps/87532afd-092d-401d-aa3f-0121c7...

	▲	asdev 2 days ago \| parent \| next [-]
		agree that AI can kinda infer business context sometimes. in my experience, it doesn't work that well. a lot of the time, debugging isn't a logic issue, but more of a state exploration issue. hence you need to add logging to see the inputs of what's going on, just seeing a control flow isn't super useful. maybe codemaps could simulate some inputs in a flow which would be super cool, but probably quite hard to do.
	▲	thedelanyo 2 days ago \| parent \| prev [-]
		[dead]

▲

Closi a day ago | parent | prev | next [-]

> AI will never know the why behind the architecture, it will only take it at face value.

There is no reason to believe that at some point in the future AI will know the business context for apps when they are vibecoded (because the prompts should contain the business context).

▲

nsonha a day ago | parent | prev [-]

> 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"?