News for hackers. Stuff that matters.
Re:Beyond file trees: why AI coding assistants need smarter ... by aymandfire on Tuesday January 28, 2025 @03:02PM (#42857232)
When debugging code, experienced developers don't read every file—they follow execution paths and understand system architecture. But today's AI coding tools try to read all files and get bogged down in unnecessary details.

With context windows limited to 200K tokens, cramming in random files isn't just inefficient, it's impossible for large codebases. If you’re debugging a failing test, you only need to understand the relevant files in the call chain. It's not about more context, it's about relevant context. That's what Nuanced provides through static analysis and machine learning.

Re:Beyond file trees: why AI coding assistants need smarter ... by billconan on Tuesday January 28, 2025 @03:13PM (#42857358)
Maybe show us an example of this graph in the blog post?
Re:Beyond file trees: why AI coding assistants need smarter ... by millgrove on Tuesday January 28, 2025 @03:14PM (#42857370)
Function calls are definitely one part of adding context, but lots of others that codegen tools are probably missing. Have you guys considered post-mortems, pagerduty outputs, slack threads focused on specific issues, etc.?
Re:Beyond file trees: why AI coding assistants need smarter ... by aymandfire on Tuesday January 28, 2025 @08:57PM (#42860612)
Yeah! We actually did an experiment where we provided AI tools with memory profiler outputs, Sentry exception reports, and telemetry from Datadog.
Re:Beyond file trees: why AI coding assistants need smarter ... by aymandfire on Tuesday January 28, 2025 @08:59PM (#42860621)
Will share results soon.
Re:Beyond file trees: why AI coding assistants need smarter ... by sylvainkalache on Wednesday January 29, 2025 @03:43PM (#42870898)
I would love to see the results; where will you share?