aymandfire
Joined 3 years ago
Karma
89
Submissions
24
Member since
Aug 9
https://www.aymannadeem.com/about/
View on Hacker NewsRecent submissions
Comment · 1 month ago
This is pretty much exactly the flow we built Nuanced.dev around.
Comment · 1 month ago
Thank you! Baby was born in July, but we are actually back in the ER right now because she’s struggling :(
Propelcode looks awesome! So cool to see different people and perspectives shaping this space.
Comment · 1 month ago
oh interesting! I haven’t used vscode for anything meaningful since shortly after leaving GitHub (2023). I generally find it overwhelming but codex added the annotations too and I love it.
Comment · 1 month ago
hi I’m the author of the post. I think that’s basically the distinction I’m trying to make.
Historically, plan mode served two different roles:
1. making the agent’s instructions precise enough to execute 2. helping the human understand what was about to happen
I think #1 is less necessary as agents get better. #2 is going the other direction, it becomes more important as the model is able to do more on its own because larger chunks of work are happening with increasing complexity.
Where I’ve changed my mind is the interface for #2. I increasingly think an interactive, iterative workflow is closer to how people actually build understanding than being handed a long generated document, especially one they didn’t author themselves.
The human-understanding problem is very real though
Comment · 1 month ago
I see what you mean, but I’m saying something else, I think plan modes were solving two different problems:
1. giving the agent sufficiently precise instructions 2. helping the human understand what’s being built
I think #1 is increasingly going away as models get better. #2 is a separate problem, and I actually think it matters more as agents get more capable. I’m not arguing that human understanding should disappear with plan mode.
I’m also not pushing this on behalf of a model lab, I don’t represent one. These are lessons I learned from my own mistakes building Nuanced (https://www.nuanced.dev). We built around a very explicit plan-oriented workflow because that’s how I used to work. I spent years at GitHub writing ADRs, RFCs, and design docs, and I still really like writing because it’s how I clarify my own thinking.
What changed for me is that AI-generated plans don’t give me that same effect. The agent reads between the lines, generates a lot of detailed prose, and now I’m parsing decisions and assumptions I didn’t actually make.
So I still think human understanding deserves a first-class primitive. I’m just increasingly unconvinced that a big blob of generated text is the right one, especially as we move toward many agents working in parallel.
Comment · 1 month ago
I see what you’re saying. That’s actually why I built Nuanced (https://www.nuanced.dev), I wanted a better way for humans and agents to work through intent before the code got written.
but I think I overfit the interface to how I used to work without agents. when I was at GitHub, I wrote a lot of ADRs, RFCs, and design docs, and I liked that because writing is how I clarify my own thinking. with agents though, I’m often not doing the writing myself. I give the model a rough intent and it fills in a bunch of gaps, and then I get back a long, polished plan containing decisions I didn’t explicitly make.
That’s the part that feels broken to me. The plan can be detailed and technically correct, but still be hard to review because the important bits are buried and feel distant from my own thinking. All the assumptions and tradeoffs and questions may or may not be legitimate, but it’s hard for me to get into flow state and carefully check them.
So I still want the collaboration step. I’m just less convinced that generated prose à la plan mode is the right interface for it.
Comment · 1 year ago
Thanks! If you ever wanna trade notes or if we can be of any help, feel free to reach out at [email protected]!
Comment · 1 year ago
Hey, happy to chat about timeline estimates if you wanna shoot me an email at [email protected]
Comment · 1 year ago
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
Comment · 1 year ago
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. :)
Comment · 1 year ago
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