HackerTrans
トップ新着トレンドコメント過去質問紹介求人

aymandfire

no profile record

投稿

The unbearable slowness of AI coding

joshuavaldez.com
137 ポイント·投稿者 aymandfire·11 か月前·102 コメント

[untitled]

1 ポイント·投稿者 aymandfire·11 か月前·0 コメント

Show HN: Nuanced – Help AI understand code structure, not just text

nuanced.dev
34 ポイント·投稿者 aymandfire·昨年·13 コメント

[untitled]

1 ポイント·投稿者 aymandfire·昨年·0 コメント

Beyond file trees: why AI coding assistants need smarter context

nuanced.dev
11 ポイント·投稿者 aymandfire·昨年·6 コメント

Nuanced: As AI writes more code, we need better tools to trust it

nuanced.dev
8 ポイント·投稿者 aymandfire·2 年前·1 コメント

コメント

aymandfire
·昨年·議論
Thanks! If you ever wanna trade notes or if we can be of any help, feel free to reach out at [email protected]!
aymandfire
·昨年·議論
Hey, happy to chat about timeline estimates if you wanna shoot me an email at [email protected]
aymandfire
·昨年·議論
Hey! Coming soon. We're also working on a swe-bench test: https://github.com/nuanced-dev/nuanced/issues/10

In the interim, this is a test I did with Sonnet 3.5 + Cursor, showing how it impacted explanations (not solutions): https://github.com/nuanced-dev/nuanced/issues/31
aymandfire
·昨年·議論
Hi there! Like I said in the post, we're actively developing support for JS/TS next, and are building toward a language-extensible project. We started with an open-source Python tool. :)
aymandfire
·昨年·議論
Totally agree, working on publishing that soon! We're also working on a swe-bench test: https://github.com/nuanced-dev/nuanced/issues/10

In the interim, this is a test I did with Sonnet 3.5 + Cursor, showing how it impacted explanations: https://github.com/nuanced-dev/nuanced/issues/31
aymandfire
·昨年·議論
Will share results soon.
aymandfire
·昨年·議論
Yeah! We actually did an experiment where we provided AI tools with memory profiler outputs, Sentry exception reports, and telemetry from Datadog.
aymandfire
·昨年·議論
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.
aymandfire
·2 年前·議論
At Nuanced, we're building tools that make AI-generated code more reliable.

As AI writes more code, we need better tools to trust it and technologies that ensure our human understanding keeps pace with this rapid development.

While everyone else races to ship new features with AI, we're focused on addressing gaps in AI coding tools and ensuring those features are reliable and maintainable rather than code that works today but becomes a liability tomorrow.

We're starting with an AI-powered Python language server that makes AI-generated code more reliable by understanding your entire system—using a deeper semantic understanding of code than LLMs have today, but also artifacts outside of code such as commit histories, configs, and team patterns.

We're a team of ex-GitHub engineers and researchers who've scaled some of the world's largest developer platforms. I'm Ayman (https://www.aymannadeem.com/about/), and before founding Nuanced, I spent seven years at GitHub where I helped build Semantic(https://github.com/github/semantic), an open-source library for parsing and analyzing code across languages—and scaled security systems to detect anomalous code patterns across millions of repositories. Our team’s deep experience in static analysis and large-scale system design shapes our approach to the AI reliability challenge today.

We've all been on-call at 2 AM, untangling complex service dependencies, and more recently, we've seen firsthand how AI accelerates development—both the wins and the wounds.

If you're building an AI coding tool and any of this sounds interesting to you—we should talk!

Read more at https://nuanced.dev/blog/the-reliability-gap